It helps if you are careful to indicate what text is quoted and what sources it is quoted from.
> Date: Thu, 30 Oct 2014 17:03:01 +0530 > From: Vikas Kumar1 <vikas.kum...@globallogic.com> > > 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. However, the following text is *not* from RFC 3261. It resembles the text at http://www.3cx.com/pbx/sip-uri/ > 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.? I do not know of any system that restricts the use of ports in To and >From headers. In any case, SIP systems do not (or should not) examine the To and From headers in any detail, as they do not affect the processing of messages. (In RFC 2543, To and From headers were examined, which has led to all sorts of compatibility problems. But my impression is that modern SIP systems have generally given up on being backward compatible with RFC 2543.) There is a practical difficulty if a SIP system forbids ports in To and From: Generally, when an INVITE is constructed, the "URI to call" is copied into the To header and the request-URI. If a port is forbidden in the To header, any port on the URI must be removed when it is put into a To header, which might make the To header deceptive. Dale _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
