Summary: | ASTERISK-25013: DNS Tests: NAPTR Nominal - Correct Preference | ||||||||
Reporter: | Matt Jordan (mjordan) | Labels: | |||||||
Date Opened: | 2015-04-24 11:41:09 | Date Closed: | 2015-06-11 18:42:18 | ||||||
Priority: | Major | Regression? | |||||||
Status: | Closed/Complete | Components: | Tests/testsuite | ||||||
Versions: | Frequency of Occurrence | ||||||||
Related Issues: |
| ||||||||
Environment: | Attachments: | ||||||||
Description: | h2. Correct Preference
h3. Goal Ensure that when multiple NAPTR records with the same order are returned, that the one with the lowest preference is chosen first h3. Procedure # Set up the following DNS records for test.internal: {noformat} ; order pref flags service regexp replacement IN NAPTR 50 50 "s" "SIP+D2T" "" _sip._tcp.test.internal. IN NAPTR 50 90 "s" "SIP+D2U" "" _sip._udp.test.internal. {noformat} # Enable NAPTR lookups for outbound SIP calls. Allow both UDP and TCP transports to be used for the outgoing call. # Place an outbound SIP call to sip:test.internal # Ensure that a NAPTR lookup of test.internal occurs # Ensure that an SRV lookup occurs for _sip._tcp.test.internal h3. Notes It is unknown whether the DNS engine in Asterisk will try to optimize by performing simultaneous SRV lookups of both _sip._tcp.test.internal and _sip._udp.test.internal instead of going sequentially. If the domains are looked up in parallel, then this test cannot determine if the correct preference is being honored simply by monitoring SRV record lookups. The test would have to be expanded in the following way: Add distinct SRV records for _sip._tcp.test.internal and _sip._udp.test.internal. Each of the domains pointed to by those SRV records should be distinct A records. Ensure that the outgoing SIP request ends up being sent to the IP address retrieved from the A record lookup of the domain pointed to by the _sip._tcp.test.internal SRV record. | ||||||||
Comments: |