![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||
Solution Type Technical Instruction Sure Solution 2203183.1 : How to Configure Session-agent for DNS to Use A-record, SRV Record and NAPTR Record to Determine the Transport Address
In this Document
Created from <SR 3-12917062391> Applies to:Acme Packet 3820 - Version S-Cx6.3.0 and laterInformation in this document applies to any platform. GoalThis document outlines the procedure to configure session-agent for DNS to use A-record , SRV Record and NAPTR record to determine the transport address. SolutionThe transport address consists of 3 parts: The simplest and most static manner in which to determine the transport address (IP address and port) of a Session-agent is to configure the ip-address, transport-method and port objects directly. If however the network uses DNS, then depending on the level of information configured, the SBC will use one of three DNS lookups to determine the transport address. Firstly, if the transport-method (e.g. UDP) and port (e.g. 5060) are configured, but ip-address is left as 0.0.0.0 the SBC will determine the IP address of the Session-agent via the result of a 'DNS A-record lookup' using the configured hostname as the query name. Secondly, if the transport-method (e.g. UDP) is configured, but ip-address and port are set to 0.0.0.0 and 0 respectively, the SBC will determine the port of the Session-agent via the result of a 'DNS SRVrecord' lookup using the configured hostname prepended with _sip._udp as the query name. An A-record lookup will follow to determine the IP address. Lastly, should the transport-method be set to UDP+TCP, and ip-address and port are set to 0.0.0.0 and 0 respectively, the SBC will determine the transport type of the Session-agent via the contents of the DNS NAPTR-record response service field (e.g. SIP+D2U for UDP). Follow-on SRV-record and A-record lookups will determine port and IP address respectively. References<NOTE:1987579.1> - Theory of a Sesssion AgentAttachments This solution has no attachment |
||||||||||||||||
|