Hi Ranjit, Please be aware that the Diversion header never made it through the IETF standardisation process, which makes its use proprietary. Some manufacturers, among which Microsoft, use it however. The IETF-way of doing this would be to make use of the request history as per RFC4244. Cheers, Frabj
________________________________ From: Avasarala Ranjit-A20990 [mailto:[EMAIL PROTECTED] Sent: 2007-Aug-29 21:04 To: [EMAIL PROTECTED]; [email protected]; [EMAIL PROTECTED] Subject: [Sip] 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
