i am not sure if this is related but, there are cases when if a user adds credit, it does not reflect on cnxcc.active_clients
after the next call. somehow, cnxcc saves the old credit and does not update it

Kelvin Chua


On Thu, Aug 28, 2014 at 10:24 PM, Carlos Ruiz Díaz <carlos.ruizdiaz@gmail.com> wrote:
Hi Kelvin,

this is an interesting scenario. I will have to reproduce it myself in order to reply you properly.

Answering your question, yes, it should be updated to 200. Let me check ASAP.

Regards,
Carlos




On Thu, Aug 28, 2014 at 4:31 AM, Kelvin Chua <kelchy@gmail.com> wrote:
hi carlos,

i have a serial forking scenario to several providers as failover. and i used cnxcc_set_max_credit to control the session credit/time.

just wanted to make sure it does what i think it should do so i made a little experiment.
the logic goes this way.
1. cnxcc_set_max_credit -> $100, cost per second -> $1
2. call will fail, try the next provider
3. cnxcc_set_max_credit -> $200, cost per second -> $2

what i am expecting to see is, if i do

kamctl kamcmd cnxcc.active_clients

i would see $200 as the max_amount. but in kamailio 4.1.5, i still see $100, should it
be updated to $200? is there an override in cnxcc_set_max_credit when called twice or after failure_route?

Kelvin Chua

_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users




--

_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users