<div dir="ltr">thanks a lot, Saúl.<br><div><div class="gmail_extra"><br><br><div class="gmail_quote">On 12 July 2013 18:10, Saúl Ibarra Corretgé <span dir="ltr"><<a href="mailto:saul@ag-projects.com" target="_blank">saul@ag-projects.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im"><br>
On Jul 12, 2013, at 10:14 AM, samuel wrote:<br>
<br>
> Hi folks,<br>
><br>
> We were recently playing around with call control application and came across the parameter call_token_avp. There's an explanation in the README file and the code does exactly what is written: select whether 2 INVITEs with same Call-ID belongs to the same call.<br>
> In the code, it seems as the call is being rated again (it's removed from user_calls structure and the setup is being called again).<br>
><br>
> Could anyone confirm whether above assumption is right?<br>
><br>
<br>
</div>If 2 calls arrive at callcontrol with different tokens, the second one will be rejected, that is, call_control() will return a negative code. In our configurations we reply with 400 Duplicated CallID in that case.<br>
<div class="im"><br>
> Besides, what is the use case behind this parameter? In which case is it necessary to use the token to indicate that the second INVITE belongs to the same call? Migh it be controlling retransmissions of the same INVITE?<br>
><br>
<br>
</div>We ran into some problems with devices which reused the call-id, or sent a very late re-INVITE and this creates accounting issues.<br>
<br>
<br>
Regards,<br>
<br>
--<br>
Saúl Ibarra Corretgé<br>
AG Projects<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
</blockquote></div><br></div></div></div>