RFC 3263:Session Initiation Protocol (SIP): Locati...
RFC-Ref

IP address


Click on the red underlined text to get to the source

... For the first aspect, proxy 1 specifically needs to determine the IP address, port, and transport protocol for the server in domain ...
... client) may need to perform DNS processing to determine the IP address, port, and transport protocol ...


... URI is not rewritten with the result of the DNS lookup), they only result in an IP address, port and transport protocol ...
... proxy not identified by a SIP URI, but rather, by a hostname or numeric IP address. In that case, a temporary URI, used for purposes of this specification, is constructed. That URI ...
... proxy>, where <proxy> is the FQDN or numeric IP address of the next-hop proxy. As a result, in all cases, the ...
... SIPS URI in DNS to determine the IP address, port, and transport of the host ...
... We determine the transport protocol, port and IP address of a suitable instance of TARGET in Sections 4.1 and 4.2. ...
... transport protocol is specified, but the TARGET is a numeric IP address, the client SHOULD use UDP for a SIP URI ...
... port is specified, and the target is not a numeric IP address, the client SHOULD perform a NAPTR ...
... Determining Port and IP Address ...
... Once the transport protocol has been determined, the next step is to determine the IP address and port. ...
... If TARGET is a numeric IP address, the client uses that address. If ...
... If the TARGET was not a numeric IP address, but a port is present in the URI ...
... AAAA record lookup of the domain name. The result will be a list of IP addresses, each of which can be contacted at the specific port from the URI ...
... If the TARGET was not a numeric IP address, and no port was present in the URI ...
... lookup of the domain name. The result will be a list of IP addresses, each of which can be contacted using the transport protocol determined previously, at the default port for that ...


... In these cases, the server examines the value of the sent-by construction in the topmost Via header. If it contains a numeric IP address, the server attempts to send the response to that address, using the transport protocol ...
... tries to send the response to each element on the resulting list of IP addresses, using the port from the Via, and the transport protocol ...


... property that they resolve to the specific element that inserted them. However, if they are constructed with just an IP address, for example: ...
... SRV provides a way to fix this. Instead of using an IP address, a domain name that resolves to an SRV record ...



Google
Web
RFC-Ref