[asterisk-bugs] [JIRA] (ASTERISK-18353) SIP registration doesn't use round-robin DNS.

[Olle Johansson (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-18353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206090#comment-206090 ] 

Olle Johansson commented on ASTERISK-18353:
-------------------------------------------

Btw, I do not agree that with round robin DNS we should try all of the addresses. We should only try one but will get different ones every time we look it up. SRV is DNS the solution that has both load balancing and fail over defined.
                
> SIP registration doesn't use round-robin DNS.
> ---------------------------------------------
>
>                 Key: ASTERISK-18353
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-18353
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/General
>    Affects Versions: 1.8.5.0
>         Environment: Asterisk 1.8.5.0, Fedora 15
>            Reporter: David Woodhouse
>            Severity: Minor
>
> When there are multiple IP addresses in DNS for a given host, chan_sip only seems to try one of them, repeatedly. It doesn't fall back to the others.
> This is especially noticeable when RFC3484 puts an IPv6 address top in the list but the server doesn't respond on that address (which is a bug, but happens).
> But it's true even for purely Legacy IP setups; if there are multiple servers listed in round-robin, it should try them all before failing.
> But it doesn't. It just tries the *same* host again:
> [Aug 27 10:44:43] NOTICE[16688]: chan_sip.c:12654 sip_reg_timeout:    -- Registration for '01799xxxxxx at c.speechless.aaisp.net.uk' timed out, trying again (Attempt #1782)
> Really destroying SIP dialog '12474a89554cf44a1c33b0cf07c70413@[2001:8b0:10b:1:240:f4ff:fe28:959d]' Method: REGISTER
> Retransmitting #1 (no NAT) to [2001:8b0:0:30:225:90ff:fe05:11ac]:5060:
> (This is for registration; presumably the same problem exists elsewhere.)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira