On Thu, 21 Mar 2013 16:02:17 -0700, Michael L. Young wrote:
> Let me try to understand this. With bindaddr set as "bindaddr=::", upon
> starting Asterisk, you are fine and all your IPv4 peers connect
> properly. Therefore, dual stack is working at this point. ...
You minunderstand. When I start Asterisk with "bindaddr=::", the netstat
output shows that it's using udp6, which usually means that the service
is running in dual stack mode, but this is apparently not the case. On my
system, it really is only listening on IPv6. That's why I said that,
despite appearances, as soon as I reload SIP (or restart Asterisk) with
this setting, I lose contact with my entire list of IPv4-only peers,
while Asterisk gives warnings about the network being unreachable (the
IPv4 network).
I've also tried using multiple bindaddr lines with a mix of IPv4 and IPv6
addresses, but then the service ends up binding only to the last address.
Therefore, it looks to me like the version of Asterisk that I'm running
is only capable of running in single stack mode, supporting either IPv4
or IPv6, but not both at the same time.
> Upon issuing a "sip reload", your peers lose their ability
> to communicate with Asterisk? Is that correct?
That's right.
> What does "netstat -lpn |grep 5060" show after the reload?
udp6 0 0 :::5060 :::* 9898/asterisk
> These "network unreachable" warnings are from Asterisk or your peers?
>From Asterisk. They look like this for two of my IPv4 SIP devices:
[Mar 21 23:24:18] NOTICE[9931]: chan_sip.c:26242 sip_poke_noanswer: Peer
'1000' is now UNREACHABLE! Last qualify: 110
[Mar 21 23:24:18] NOTICE[9931]: chan_sip.c:26242 sip_poke_noanswer: Peer
'patton' is now UNREACHABLE! Last qualify: 20
I also get errors for connections to SIP servers for which I have
"register" entries in the [general] section of sip.conf. The errors for
one of them, sip.xs4all.nl, which is IPv4 only, look like this:
[Mar 21 23:24:14] ERROR[9931]: netsock2.c:263 ast_sockaddr_resolve:
getaddrinfo("sip.xs4all.nl", "(null)", ...): No address associated with
hostname
[Mar 21 23:24:14] WARNING[9931]: acl.c:582 resolve_first: Unable to
lookup 'sip.xs4all.nl'
Anyway, as soon as I reload sip without "bindaddr=::", these errors stop.
> What version of Asterisk are you using?
Version 1.8.13.1.
> Asterisk 1.8.0 had IPv6 support in it. Therefore, every minor version
> released since would still have IPv6 support in it.
That's good to know, so maybe it's just my minor version that has a bug
that prevents it from running in dual stack mode. That's what my question
was about in the first place.
Cheers,
Jaap
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
http://www.asterisk.org/hello
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
