This is what we see in the debug log regarding CNXCC:

Nov 24 10:26:25 kamailio /usr/sbin/kamailio[37945]: DEBUG: {1 2334 INVITE c70a26ae946c48ac9e7043b303d1f573} cnxcc [cnxcc_mod.c:1539]: ki_set_max_credit(): Setting up new call for client [ae4b751c3@sip.domain.it], max-credit[50.000000], connect-cost[5.000000], cost-per-sec[1.000000], initial-pulse [1], final-pulse [1], call-id[c70a26ae946c48ac9e7043b303d1f573]
Nov 24 10:26:25 kamailio /usr/sbin/kamailio[37945]: DEBUG: {1 2334 INVITE c70a26ae946c48ac9e7043b303d1f573} cnxcc [cnxcc_mod.c:1470]: set_ctrl_flag(): Flag set!
Nov 24 10:26:25 kamailio /usr/sbin/kamailio[37945]: DEBUG: {1 2334 INVITE c70a26ae946c48ac9e7043b303d1f573} cnxcc [cnxcc_redis.c:364]: redis_get_int(): Got INT value: concurrent_calls=0i
Nov 24 10:26:25 kamailio /usr/sbin/kamailio[37945]: DEBUG: {1 2334 INVITE c70a26ae946c48ac9e7043b303d1f573} cnxcc [cnxcc_redis.c:69]: redis_get_or_create_credit_data(): credit_data with ID=[ae4b751c3@sip.domain.it] DOES NOT exist in the cluster, creating it...
Nov 24 10:26:25 kamailio /usr/sbin/kamailio[37945]: DEBUG: {1 2334 INVITE c70a26ae946c48ac9e7043b303d1f573} cnxcc [cnxcc_redis.c:105]: redis_insert_credit_data(): Inserting credit_data_t using ID [ae4b751c3@sip.domain.it]
Nov 24 10:26:25 kamailio /usr/sbin/kamailio[37945]: DEBUG: {1 2334 INVITE c70a26ae946c48ac9e7043b303d1f573} cnxcc [cnxcc_mod.c:1148]: __get_or_create_credit_data_entry(): Credit entry didn't exist. Allocated new entry [0x7f9442efd448]
Nov 24 10:26:25 kamailio /usr/sbin/kamailio[37945]: DEBUG: {1 2334 INVITE c70a26ae946c48ac9e7043b303d1f573} cnxcc [cnxcc_mod.c:1265]: __alloc_new_call_by_money(): New call allocated for client [ae4b751c3@sip.domain.it]

The values reported by the function appear to be right but then in the Redis DB everything is set to 0.

Is there any other modules that is able to disconnect active calls and block new ones based on a credit limit?
We found some alternatives but they all depend on external software that would complicate implementing the solution.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.