[SIPForum-discussion] Why Dialog Id contains both local tag and remote tag?

Perttu Ahvenainen mosseahvenainen at gmail.com
Tue May 24 16:46:16 UTC 2011


Hello,

Calling party does not put remote tag to initial invite(remote-tag). Instead
it puts tag to its from header (local-tag). So that`s the need for
local-tag. See RFC3261 section 8.

Perttu Ahvenainen

2011/5/24 Ramakrishnan R <ram65.vidya at gmail.com>

> The calling party creates the 'call-id'. That is unique, and is good enough
> identification too. The 'remote-tag' is needed for forking proxies to
> identify the responses from multiple end points. But I am not able
> understand the need for 'local-tag'. Can any one explain this?
>
> Regards,
> Ramki
>
>
>
> On Tue, May 24, 2011 at 3:46 PM, Perttu Ahvenainen <
> mosseahvenainen at gmail.com> wrote:
>
>> Hello,
>>
>> SIP dialog is a active dialog between two endpoints. Thats why
>> identification of a dialog has to also be "signed" with both endpoints and
>> dialog represents peer-to-peer SIP relationship between those two endpoints.
>>
>> -Perttu Ahvenainen
>>
>> 2011/5/22 Ramakrishnan R <ram65.vidya at gmail.com>
>>
>>>
>>> Dialog ID is defined as "call-id + local-tag + remote-tag".
>>>
>>> Is "remote-tag" alone not sufficient ? Why "local-tag" is also needed?
>>>
>>> Any insights?
>>>
>>> Thanks & regards,
>>>  Ramakrishnan
>>>
>>>
>>> _______________________________________________
>>> This is the SIP Forum discussion mailing list
>>> TO UNSUBSCRIBE, or edit your delivery options, please visit
>>> http://sipforum.org/mailman/listinfo/discussion
>>> Post to the list at discussion at sipforum.org
>>>
>>>
>>
>
> _______________________________________________
> This is the SIP Forum discussion mailing list
> TO UNSUBSCRIBE, or edit your delivery options, please visit
> http://sipforum.org/mailman/listinfo/discussion
> Post to the list at discussion at sipforum.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20110524/1b26b724/attachment-0002.html>


More information about the discussion mailing list