thanks a lot, Saúl.
On 12 July 2013 18:10, Saúl Ibarra Corretgé <[email protected]> wrote: > > On Jul 12, 2013, at 10:14 AM, samuel wrote: > > > Hi folks, > > > > 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. > > 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). > > > > Could anyone confirm whether above assumption is right? > > > > 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. > > > 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? > > > > We ran into some problems with devices which reused the call-id, or sent a > very late re-INVITE and this creates accounting issues. > > > Regards, > > -- > Saúl Ibarra Corretgé > AG Projects > > > > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users >
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
