Hi All, As per RFC 3261, To and From header must not have ports in request or response.
19.1.2 <http://tools.ietf.org/html/rfc3261#section-19.1.2> Character Escaping Requirements dialog reg./redir. Contact/ default Req.-URI To From Contact R-R/Route external port (1) o - - o o o However, below part indicates that To header field MAY contain a SIP or SIPS URI. 8.1.1.2 To The To header field first and foremost specifies the desired "logical" recipient of the request, or the address-of-record of the user or resource that is the target of this request. This may or may not be the ultimate recipient of the request. The To header field MAY contain a SIP or SIPS URI, but it may also make use of other URI schemes (the tel URL (RFC 2806 [9]), for example) when appropriate. All SIP implementations MUST support the SIP URI scheme. A SIP-URI is the SIP addressing scheme that communicates who to call via SIP. The SIP URI resembles an e-mail address and is written in the following format: SIP-URI = sip:x@y:Port where x=Username and y=host (domain or IP) Note: If you do not specify a port, the default sip port will be assumed (5060). This is shown in the first two examples below. If you have changed the default sip port to something else then you need to specify it in the SIP-URI (third example below). Examples: sip:joe.bloggs@212.123.1.213 sip:supp...@phonesystem.abc.com sip:22444...@phonesystem.def.com:6000 Please, Let me know whether the ports are optional or restricted in To and FROM header.? -- Thanks & Regards, Vikas Kumar _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
