Can I just add a caveat here that as this was never a SIP WG item, only
an author draft, you take the answers as you find them.
The standards track SIP solution for this problem is the History-Info
header, documented in RFC 4244 (with some content extras in RFC 4458).
Note also that the Diversion header is also NOT IANA registered, and
there is nothing therefore that prevents an alternative usage of the
same character string coming along in the future with different
semantics.
regards
Keith
________________________________
From: Brett Tate [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 30, 2007 1:08 PM
To: [email protected]; [EMAIL PROTECTED]
Subject: RE: [Sipping] [Reg] Diversion Header
Per the section 5 BNF representation, only parameter values that
have non token characters need the quotes. Thus the use of the quotes
for the privacy and screen values within the examples is not needed.
________________________________
From: Vinay Pande (vipande) [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 29, 2007 3:31 PM
To: Avasarala Ranjit-A20990; [EMAIL PROTECTED];
[email protected]; [EMAIL PROTECTED]
Subject: RE: [Sipping] [Reg] Diversion Header
The examples mentioned in section 7.1 and voice-mail /
ISUP examples of sec 9.2 / sec 10 in draft-08
<http://tools.ietf.org/id/draft-levy-sip-diversion-08.txt> show that
the reason, counter and other headers need not be in quotes. Only the
screen and privacy parameter values are shown in quotes.
Sec 9.2
SIP/2.0 302 Moved Temporarily
Via: SIP/2.0/UDP p1.isp.com
Via: SIP/2.0/UDP alice-pc.isp.com
Contact: [EMAIL PROTECTED]
From: sip:[EMAIL PROTECTED]
To: <sip:[EMAIL PROTECTED]>;tag=uas1
Call-ID: [EMAIL PROTECTED]
CSeq: 1 INVITE
Diversion:
<sip:[EMAIL PROTECTED]>;reason=do-not-disturb
Sec 10.3.5:
|--INVITE
tel:+19195551004---->
| Diversion:
<tel:+19195551002>
|
;reason=user-busy
|
;screen="yes"
|
;privacy="off"
| Diversion:
<tel:+19195551001>
|
;reason=unconditional
|
;screen="yes"
|
;privacy="full"
Thanks,
Vinay
________________________________
From: Avasarala Ranjit-A20990
[mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 29, 2007 12:04 PM
To: [EMAIL PROTECTED]; [email protected];
[EMAIL PROTECTED]
Subject: RE: [Sipping] [Reg] Diversion Header
Hi Subhodeep
The correct syntax would be: Diversion:
...;reason="user-busy";privacy="full"
Regards
Ranjit
________________________________
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Thursday, August 30, 2007 12:31 AM
To: [email protected]; [EMAIL PROTECTED]
Subject: [Sipping] [Reg] Diversion Header
Hi,
I need some clarification regarding the encoding syntax
of SIP Diversion header parameters reason & privacy .
I am aware that Diversion header is replaced by
History-Info, but I need to support Diversion header for some network
implementation.
diversion-reason = "reason" "="
( "unknown" | "user-busy" |
"no-answer" |
"unavailable" | "unconditional" |
"time-of-day" | "do-not-disturb" |
"deflection" | "follow-me" |
"out-of-service" | "away" |
token | quoted-string )
diversion-privacy = "privacy" "=" ( "full" | "name"
|
"uri" | "off" | token |
quoted-string )
I like to know which is the correct syntax for the
diversion-privacy & diversion-reason parameter i.e.
Diversion: ...;reason="user-busy";privacy="full"
or,
Diversion: ...;reason=user-busy;privacy=full
Cheers,
Subhodeep
_______________________________________________
Sip mailing list https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip
