----- Original Message ----- > From: "Jaap Winius" <jwin...@umrk.nl> > To: asterisk-users@lists.digium.com > Sent: Thursday, March 21, 2013 5:27:37 PM > Subject: Re: [asterisk-users] Asterisk 1.8 and dual stack support > > That's what I thought would happen. When I set bindaddr=:: and use > 'netstat -lpn |grep 5060' it shows: > > udp6 0 0 :::5060 :::* 9898/asterisk > > Services like this usually also support IPv4 and as much is suggested > by > this comment in the sip.conf that comes with my Asterisk package: > > ; (Note that using bindaddr=:: will show only a single > ; IPv6 socket in netstat. IPv4 is supported at the same > ; time using IPv4-mapped IPv6 addresses.) > > However, the moment I reload my sip.conf with bindaddr=::, my entire > list > of IPv4-only peers loses contact with Asterisk with warnings about > the > network being unreachable. So, it would appear that the version of > Asterisk that I'm using is operating with a single stack socket.
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. Upon issuing a "sip reload", your peers lose their ability to communicate with Asterisk? Is that correct? What does "netstat -lpn |grep 5060" show after the reload? These "network unreachable" warnings are from Asterisk or your peers? What version of Asterisk are you using? Asterisk 1.8.0 had IPv6 support in it. Therefore, every minor version released since would still have IPv6 support in it. Michael -- _____________________________________________________________________ -- 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
