[SIPForum-discussion] Diversion & Remote Party ID

[Vikas Singhal (vsinghal)]

Hi Pankaj,

Diversion Header and Remote Party id are different headers.


Remote Party id:  Identifies a party and is added by the trusted network entities.

   Different types of party information can be provided, e.g., calling,

   or called party, and for each type of party, different types of

   identity information, e.g. subscriber, or terminal, can be provided.

   Since a party may not wish to reveal some or all of this information

   to an untrusted entity, the party can request a specific level of

   privacy for each. The intermediary also has the ability to specify a

   required level of privacy.





Diversion header : The Diversion header allows implementation of feature logic
based on from whom the call was diverted.


Role of "reason" in diversion header to convey why message is diverted e.g. user-busy, no-answer etc.

It is recommended to include reason in diversion header. But it may work without "reason". Check diversion header RFC :  http://tools.ietf.org/id/draft-levy-sip-diversion-08.txt.

Regards,
Vikas

From: discussion-bounces at sipforum.org [mailto:discussion-bounces at sipforum.org] On Behalf Of pankaj singh
Sent: Sunday, January 13, 2013 11:02 AM
To: discussion at sipforum.org
Subject: [SIPForum-discussion] Diversion & Remote Party ID

Hi,

I Am wondering, is Diversion and Remote Party ID are Same? In Diversion Header what is role of Branch "reason", Can Diversion Header works with-out "reason" branch? Need you suggestion here.

Thanks,

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20130115/ad137b0f/attachment-0002.html>