[SR-Users] Any ideas on how to implement prepaid calling function which is persistent after restart

Daniel-Constantin Mierla miconda at gmail.com
Tue Apr 24 19:36:00 CEST 2018


Hello,

isn't cnxcc capable of storing its information in a Redis server and use
it from there after restart?

Cheers,
Daniel


On 23.04.18 04:43, Kit Lim wrote:
> Hi Everyone,
>
> My project involves keeping track of the allowable duration for the
> caller to talk, and keeping track of the status of the call with the
> back end database.  Currently i have implemented using the following
> modules (aside from the default modules in the sample config script).
> * http_async_client.so - to communicate with the backend DB
> * dialog.so - mainly use to detect the 200 ok answer in relation to
> invite, and the end of the call
> * cnxcc.so - to release the call when the allowable talk time is reached
>
> The flow is as below:-
>
> Invite -- > http to backend DB to ask for talk time
>           <-- DB returns value
> 200 ok (answer) ---> http backend DB to update that the call has answered
>           <-- DB returns ok
> dialog end or Cnxcc terminate --> http backend DB to update that the
> call has hangup
>
> My problem is that if there is a need to restart the kamailio config
> there is no 'graceful' way to hangup all the calls and inform the
> backend, or deny any new calls from coming in. If kamailio is
> restarted then cnxcc would have forgotten that there is a maximum talk
> time allowed to be called or recover from the restart.
>
> How to I make the system resilience to failures/restarts.
>
> Appreciate any good suggestions. 
>
> regards
> CK
>
>
> _______________________________________________
> Kamailio (SER) - Users Mailing List
> sr-users at lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20180424/7882399c/attachment.html>


More information about the sr-users mailing list