Dale, I guess its looks different in sip forum..
Because i have not seen a single packet in original format who is taking "%3A" in userpart..However i am again sending you the Request line which is actually quested in uri's. Request-Line: INVITE sip:[email protected]<sip%[email protected]>SIP/2.0 Request-URI: sip:[email protected] <sip%[email protected]> Whereby in TO header(of the same INVITE) I do not have the “1” in user part as below. To: sip:[email protected] <sip%[email protected]> Thanks, Nitin Kapoor On 18 March 2010 13:52, WORLEY, DALE R (DALE) <[email protected]> wrote: > _______________________________________ > From: [email protected] [ > [email protected]] On Behalf Of Nitin Kapoor > [[email protected]] > > To: sip:[email protected] <sip%[email protected]> < > sip%[email protected] <sip%[email protected]>> > > _______________________________________________ > > In general, a SIP element should not consider the value of the To header. > However, the To header is required to conform to a specific syntax, and > this To header does not. The basic structure for this type of To header is > "display-name <SIP-URI>". However, if display-name is not quoted, it is > restricted to being a "token", and "token" may not contain ":" or "@". The > text between <...> is supposed to be a SIP URI, but the ":" is replaced by > "%3A", and there is no escaping defined for that position. See section 25.1 > of RFC 3261 for the details. > > So until you correct the To header (who is generating it?) there is no > reason to expect any SIP element to accept the request. > > Dale > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
