'Re: [SR-Users] Any ideas on how to implement prepaid calling function which is persistent after rest'

[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sr-users
Subject:    Re: [SR-Users] Any ideas on how to implement prepaid calling function which is persistent after rest
From:       Daniel-Constantin Mierla <miconda () gmail ! com>
Date:       2018-04-24 17:36:00
Message-ID: b99fbd15-6a5d-e00c-1a78-7eed2c704304 () gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]

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@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

[Attachment #5 (text/html)]

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>Hello,</p>
    <p>isn't cnxcc capable of storing its information in a Redis server
      and use it from there after restart?</p>
    <p>Cheers,<br>
      Daniel<br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 23.04.18 04:43, Kit Lim wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CABFs-W6FDA-whvJ8Lg5vQ=cJ50jkBxyfjC7z0kFgr_km3ythag@mail.gmail.com">
      <div dir="ltr">Hi Everyone,
        <div><br>
        </div>
        <div>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).</div>
        <div>* http_async_client.so - to communicate with the backend DB</div>
        <div>* dialog.so - mainly use to detect the 200 ok answer in
          relation to invite, and the end of the call</div>
        <div>* cnxcc.so - to release the call when the allowable talk
          time is reached</div>
        <div><br>
        </div>
        <div>The flow is as below:-</div>
        <div><br>
        </div>
        <div>Invite -- &gt; http to backend DB to ask for talk time</div>
        <div>          &lt;-- DB returns value</div>
        <div>200 ok (answer) ---&gt; http backend DB to update that the
          call has answered</div>
        <div>          &lt;-- DB returns ok</div>
        <div>dialog end or Cnxcc terminate --&gt; http backend DB to
          update that the call has hangup</div>
        <div><br>
        </div>
        <div>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.</div>
        <div><br>
        </div>
        <div>How to I make the system resilience to failures/restarts.</div>
        <div><br>
        </div>
        <div>Appreciate any good suggestions. </div>
        <div><br>
        </div>
        <div>regards</div>
        <div>CK</div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Kamailio (SER) - Users Mailing List
<a class="moz-txt-link-abbreviated" \
href="mailto:sr-users@lists.kamailio.org">sr-users@lists.kamailio.org</a> <a \
class="moz-txt-link-freetext" \
href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a>
 </pre>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
Daniel-Constantin Mierla
<a class="moz-txt-link-abbreviated" \
href="http://www.twitter.com/miconda">www.twitter.com/miconda</a> -- <a \
class="moz-txt-link-abbreviated" \
href="http://www.linkedin.com/in/miconda">www.linkedin.com/in/miconda</a> Kamailio \
World Conference - May 14-16, 2018 - <a class="moz-txt-link-abbreviated" \
href="http://www.kamailioworld.com">www.kamailioworld.com</a></pre>  </body>
</html>

[Attachment #6 (text/plain)]

_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

[prev in list] [next in list] [prev in thread] [next in thread] 