Anyhow i have resolved the issue by doing a digits manipulation. Thanks everyone to help me on this.
Regards, Nitin Kapoor On 18 March 2010 13:52, WORLEY, DALE R (DALE) <dwor...@avaya.com> wrote: > _______________________________________ > From: sip-implementors-boun...@lists.cs.columbia.edu [ > sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of Nitin Kapoor > [nitinkapo...@gmail.com] > > To: sip:7139229...@64.245.120.88 <sip%3a7139229...@64.245.120.88> < > sip%3a7139229...@64.245.120.88 <sip%253a7139229...@64.245.120.88>> > > _______________________________________________ > > 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 mailing list https://www.ietf.org/mailman/listinfo/sip This list is essentially closed and only used for finishing old business. Use sip-implement...@cs.columbia.edu for questions on how to develop a SIP implementation. Use dispa...@ietf.org for new developments on the application of sip. Use sipc...@ietf.org for issues related to maintenance of the core SIP specifications.
