| Summary: | ASTERISK-25009: DNS Tests: SRV Priority | ||||||
| Reporter: | Matt Jordan (mjordan) | Labels: | |||||
| Date Opened: | 2015-04-24 11:33:56 | Date Closed: | 2015-05-22 10:34:55 | ||||
| Priority: | Major | Regression? | |||||
| Status: | Closed/Complete | Components: | Tests/testsuite | ||||
| Versions: | Frequency of Occurrence | ||||||
| Related Issues: |
| ||||||
| Environment: | Attachments: | ||||||
| Description: | h2. Priority
*Goal:* To ensure that when multiple SRV records are returned, that records with the greatest priority (meaning smallest number) are chosen before others. h3. Procedure: # Set _sip._udp.test.internal to have the following records {noformat} ;; Priority Weight Port Target IN SRV 0 1 5060 main.test.internal. IN SRV 1 1 5060 backup.test.internal. {noformat} # Disable NAPTR lookups for this test. Only allow UDP transport to be used. # Place an outbound SIP request to sip:test.internal. # Ensure that an SRV lookup of _sip._udp.test.internal is performed. # Ensure that this results in an A and/or AAAA lookup of main.test.internal. h3. Notes It is unknown whether the DNS engine in Asterisk will try to optimize by performing simultaneous lookups of both main.test.internal and backup.test.internal instead of going sequentially. If the domains are looked up in parallel, then this test cannot determine if the correct priority is being honored simply by monitoring A/AAAA record lookups. The test would have to be expanded in the following way: Add distinct A records for both main.test.internal and backup.test.internal. Ensure that the outgoing SIP request ends up being sent to the IP address retrieved from the A record lookup of main.test.internal and not the IP address retrieved by an A record lookup of backup.test.internal | ||||||
| Comments: | |||||||