:)<br><br><div class="gmail_quote">On Thu, Mar 21, 2013 at 10:27 PM, Jaap Winius <span dir="ltr"><<a href="mailto:jwinius@umrk.nl" target="_blank">jwinius@umrk.nl</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Thu, 21 Mar 2013 12:21:44 -0700, Michael L. Young wrote:<br>
<br>
> How are you determining that it is not listening on IPv4?<br>
><br>
> bindaddr=:: should allow you to support dual stack.<br>
<br>
That's what I thought would happen. When I set bindaddr=:: and use<br>
'netstat -lpn |grep 5060' it shows:<br>
<br>
udp6 0 0 :::5060 :::* 9898/asterisk<br>
<br>
Services like this usually also support IPv4 and as much is suggested by<br>
this comment in the sip.conf that comes with my Asterisk package:<br>
<br>
; (Note that using bindaddr=:: will show only a single<br>
; IPv6 socket in netstat. IPv4 is supported at the same<br>
; time using IPv4-mapped IPv6 addresses.)<br>
<br>
However, the moment I reload my sip.conf with bindaddr=::, my entire list<br>
of IPv4-only peers loses contact with Asterisk with warnings about the<br>
network being unreachable. So, it would appear that the version of<br>
Asterisk that I'm using is operating with a single stack socket.<br>
<br>
Cheers,<br>
<br>
Jaap<br>
<br>
<br>
--<br>
_____________________________________________________________________<br>
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
New to Asterisk? Join us for a live introductory webinar every Thurs:<br>
<a href="http://www.asterisk.org/hello" target="_blank">http://www.asterisk.org/hello</a><br>
<br>
asterisk-users mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br>
</blockquote></div><br>