For what-its-worth I had a Class-4 softswitch doing this a couple of months ago
(Diversion Header without user) and when calls formatted in that way hit a
Cisco IOS device [recent Cisco UC5xx -- IOS based Call Manager Express] the
Cisco device rejected them as malformed.
--
Peter Childs - Voice Engineer
Internode/Agile
On 06/06/2012, at 4:29 PM, Bharat S wrote:
Hi Tarun,
I do see user info is optional, but didn't happen to see a
Diversion Header with SIP URI specifying only the hostport. As per RFC 5806,
the diversion information is added MUST contain the Request-URI of the
request prior to the diversion. And Request-URI as per RFC 3261 is set to value
of To Header ( userinfo@hostport) in case of initial request, right? So don't
you think the SIP URI in Diversion Header should also contain userinfo?
-Bharat
________________________________
From: Tarun2 Gupta <[email protected]<mailto:[email protected]>>
To: Bharat S <[email protected]<mailto:[email protected]>>; SIP
<[email protected]<mailto:[email protected]>>
Sent: Wednesday, June 6, 2012 11:30 AM
Subject: RE: [Sip-implementors] Question on Diversion Header Syntax
Hi Bharat
The user info is an optional part. See RFC 3261 for ABNF of a SIP URI.
Regards,
Tarun Gupta
Aricent
-----Original Message-----
From:
[email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Bharat S
Sent: Wednesday, June 06, 2012 11:01 AM
To: SIP
Subject: [Sip-implementors] Question on Diversion Header Syntax
Hi All,
A quick question to understand if the below format for Diversion
header is acceptable
Diversion: <sip:[2001:12:12:5::26]>;reason=unconditional;count=1
Is the user portion mandatory or is it acceptable to just have the hostport in
the SIP-URI of Diversion Header?
Many Thanks,
Bharat
_______________________________________________
Sip-implementors mailing list
[email protected]<mailto:[email protected]>
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
===============================================================================
Please refer to http://www.aricent.com/legal/email_disclaimer.html
for important disclosures regarding this electronic communication.
===============================================================================
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
