Hi, Actually, I am facing issue with the request having P-Served-User in my request. Remote node is failing for that request with my below mentioned value telling Parser error for the below example. sip:+ACE34610520436;cic=+7...@tqf01.test.abc;sescase=term;regstate=unreg Moreover another thing is observed if the request is sent when there is no ; before the @ in PServedUser-value section this header then No parsing issue in that Remote end. The below example is getting parsed succesfully in remote end sip:+ace346105204...@tqf01.test.abc;sescase=term;regstate=unreg Now as per ABNF of P-Served-User in RFC 5502 The augmented Backus-Naur Form (BNF) (RFC 5234 [6]) syntax of the P-Served-User header field is as follows: P-Served-User = "P-Served-User" HCOLON PServedUser-value *(SEMI served-user-param) served-user-param = sessioncase-param / registration-state-param / generic-param PServedUser-value = name-addr / addr-spec sessioncase-param = "sescase" EQUAL "orig" / "term" registration-state-param = "regstate" EQUAL "unreg" / "reg" EQUAL, HCOLON, SEMI, name-addr, addr-spec, and generic-param are defined in RFC 3261 Now if we refer RFC 3261 name-addr = [ display-name ] LAQUOT addr-spec RAQUOTaddr-spec = SIP-URI / SIPS-URI / absoluteURI SIP-URI = "sip:" [ userinfo ] hostport uri-parameters [ headers ] userinfo = ( user / telephone-subscriber ) [ ":" password ] "@" SIP-URI = "sip:" [ userinfo ] hostport uri-parameters [ headers ] userinfo = ( user / telephone-subscriber ) [ ":" password ] "@"user = 1*( unreserved / escaped / user-unreserved )user-unreserved = "&" / "=" / "+" / "$" / "," / ";" / "?" / "/" unreserved = alphanum / markescaped = "%" HEXDIG HEXDIG alphanum = ALPHA / DIGIT password = *( unreserved / escaped / "&" / "=" / "+" / "$" / "," )hostport = host [ ":" port ]host = hostname / IPv4address / IPv6referencehostname = *( domainlabel "." ) toplabel [ "." ]domainlabel = alphanum / alphanum *( alphanum / "-" ) alphanumtoplabel = ALPHA / ALPHA *( alphanum / "-" ) alphanum The following is an example of a P-Served-User header field: P-Served-User: <sip:u...@example.com>; sescase=orig; regstate=reg So my understanding from above grammar that the header value [sip:+ACE34610520436;cic=+7...@tqf01.test.abc;sescase=term;regstate=unreg] has not violated the ABNF.. Can you please confirm if my understanding is correct ?Can you kindly advice if there is any issue with my first example?
Thanks & Regards, Sourav _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
