[Serusers] handling multiple INVITE statements
iqbal at gigo.co.uk
Wed Aug 17 12:25:23 CEST 2005
Second BYE I dont get, so thats all good, as for the rejection, the UA
seems to reject it, i.e I dont get a second call etc, but SER still
account for it, should ser also reject
Nils Ohlmeier wrote:
>According to RFC3261 the second INVITE (with a different branch value) for the
>same (early) dialog should be rejected with 482 Loop Detected. So if you are
>dealing with good UA's it should be no problem. Otherwise the UA is broken.
>The second BYE should not appear, as the BYE should be routed according to
>routing informations within the BYE, and thus not be duplicated because of
>several ursloc entries. If the INVITE and BYE gets duplicated because of
>something else then usrloc, you should prevent the duplication for all
>in-dialog requests (e.g. re-INVITE's too).
>On Tuesday 16 August 2005 22:23, Iqbal wrote:
>>I am getting 2 INVITE per call, which is correct in my setup.
>>I have IP phone ---> ser---> asterisk----ser----ip phone for various setups
>>So when ip phone makes a call, to a internal extension, the call goes
>>out via ser (INVITE 1) into asterisk, which then maps this internal
>>extension to a external number and hence issues a DIAL sip/xxx statement
>>(INVITE 2). All well and good
>>Now should this not give two BYE's anyhow it gives one.
>>The other thing is what to do with the two INVITES, should I be taking
>>the INVITE from asterisk, or from SER, I think the former, BUT the BYE
>>seems to match the tag for asterisk INVITE
>>Serusers mailing list
>>serusers at lists.iptel.org
More information about the sr-users