[Sip-implementors] Escaped characters in lower case or upper case

2011-11-03 Thread Tarun2 Gupta
Hi All While sending a SIP request with escaped characters, should these be sent in Upper case or lower case. For eg, ';' should be escaped as '3B' or '3b'? Can you point out the ABNF regarding this? We are getting an interop issue wherein a server is rejecting escaped characters in lower case.

Re: [Sip-implementors] Reg: Replace Header in REFER Message

2011-11-03 Thread Paul Kyzivat
On 11/3/11 3:10 PM, prakash k wrote: > Hi All, > > In "Replaces:" whether the order is mandatory, ( what is meant is) followe > by callid information ,to-tag should come first then only from-tag > > > as per RFC 3891 > > ABNF > >Replaces= "Replaces" HCOLON callid *(SEMI replaces-p

Re: [Sip-implementors] RFC 6337 and 3GPP TS 24.610: resuming from hold

2011-11-03 Thread Paul Kyzivat
On 11/3/11 1:10 PM, Brett Tate wrote: > Howdy, > > RFC 6337 and 3GPP TS 24.610 > (http://www.3gpp.org/ftp/Specs/html-info/24610.htm) appear to be in conflict > concerning resuming from hold. However, it may just be a poor interpretation > of 3GPP TS 24.610 when a sendonly offer (from X) is answ

[Sip-implementors] Reg: Replace Header in REFER Message

2011-11-03 Thread prakash k
Hi All, In "Replaces:" whether the order is mandatory, ( what is meant is) followe by callid information ,to-tag should come first then only from-tag as per RFC 3891 ABNF Replaces= "Replaces" HCOLON callid *(SEMI replaces-param) replaces-param = to-tag / from-tag / early

[Sip-implementors] RFC 6337 and 3GPP TS 24.610: resuming from hold

2011-11-03 Thread Brett Tate
Howdy, RFC 6337 and 3GPP TS 24.610 (http://www.3gpp.org/ftp/Specs/html-info/24610.htm) appear to be in conflict concerning resuming from hold. However, it may just be a poor interpretation of 3GPP TS 24.610 when a sendonly offer (from X) is answered with inactive (by Y). 3GPP TS 24.610 sectio