Summary:ASTERISK-16451: [patch] sip.conf lacks documentation for IPv6
Reporter:Olle Johansson (oej)Labels:
Date Opened:2010-07-28 10:29:28Date Closed:2010-08-10 16:20:13
Versions:Frequency of
Environment:Attachments:( 0) doc.diff
Description:There is only documentation for IPv6 based ACLs, but not how to configure, what you can do and what we don't support. This needs to be documented clearly.

Questions like these needs to be answered:
- Can I bind to multiple IPv4 and IPv6 addresses?
- Can I define both an IPv4 and IPv6 address for a device?
- How does Asterisk handle the case of dual records (a/aaaa) in host name lookups?
- How does Asterisk handle SRV records with hosts that only has IPv4 or IPv6 in different preferences?
- Does STUN support IPv6?
- Can I specify externIP both for IPv4 and IPv6?
Comments:By: Simon Perreault (sperreault) 2010-08-02 10:59:46

I uploaded a diff that hopefully fixes this issue.

By: Mark Michelson (mmichelson) 2010-08-03 11:17:46

Ship it!

By: Simon Perreault (sperreault) 2010-08-03 11:35:05

Committed in r280706.

(Am I supposed to be able to close this bug?)

By: Paul Belanger (pabelanger) 2010-08-03 11:56:33

svnbot will do it automatically, if you commit message is formatted properly.

For example:
Update documentation for IPv6 and SIP.

(closes issue ASTERISK-16451)
Reported by: oej
     doc.diff uploaded by sperreault (license 252)
Tested by: sperreault

By: Simon Perreault (sperreault) 2010-08-03 11:57:34

Got it, thanks!

By: Paul Belanger (pabelanger) 2010-08-03 11:58:38

Each issue will have a 'Commit message template' section, which will generate the message for you.  If you have permission to see it.

By: Simon Perreault (sperreault) 2010-08-03 11:59:31

Nope, I don't see it. I suppose I don't have enough karma.

By: Leif Madsen (lmadsen) 2010-08-03 13:51:57

sperreault: you should see it now -- I just updated you to 'developer' status! :)

By: Simon Perreault (sperreault) 2010-08-03 13:59:38


So to close this issue, what should I do? I only see a "Delete Issue" button...

By: Leif Madsen (lmadsen) 2010-08-03 14:30:04

Just below "Users Monitoring This Issue" and "Notes" you'll see "Commit Issue Template". You can click on the + button which will allow you to build the commit template that would close this issue with svnbot.

Then modify your commit message to include that template at the end of the commit message, and this issue should be closed automatically.

By: Digium Subversion (svnbot) 2010-08-03 14:53:05

Repository: asterisk
Revision: 280777

U   branches/1.8/configs/sip.conf.sample

r280777 | simon.perreault | 2010-08-03 14:53:05 -0500 (Tue, 03 Aug 2010) | 8 lines

Better documentation related to IPv6.

(closes issue ASTERISK-16451)
Reported by: oej
     doc.diff uploaded by sperreault (license 252)
Tested by: mmichelson



By: Digium Subversion (svnbot) 2010-08-03 14:58:57

Repository: asterisk
Revision: 280779

_U  trunk/
U   trunk/configs/sip.conf.sample

r280779 | simon.perreault | 2010-08-03 14:58:57 -0500 (Tue, 03 Aug 2010) | 15 lines

Merged revisions 280777 via svnmerge from

 r280777 | simon.perreault | 2010-08-03 15:53:07 -0400 (Tue, 03 Aug 2010) | 8 lines
 Better documentation related to IPv6.
 (closes issue ASTERISK-16451)
 Reported by: oej
       doc.diff uploaded by sperreault (license 252)
 Tested by: mmichelson



By: Paul Belanger (pabelanger) 2010-08-06 17:00:30

Re-opening: We should add some information about how asterisk will bind IPv4 and IPv6 to a single socket.  I assumed asterisk would be listening to both udp and udp6 :::5060 when I ran netstat, however that was not the case.

<pabelanger> Hmm, cannot bind asterisk to both IPv4 and IPv6 at the same time. Tried udpbindaddr=:: but no luck
<kpfleming> did you actually try contacting it over IPv4, or are you assuming that from netstat (or similar) output?
<pabelanger> kpfleming: yes, looking at netstat
<kpfleming> that is probably misleading
<pabelanger> Hmm
<pabelanger> let me fire up a call
<kpfleming> it only opens a single socket, but the socket accepts both IPv4 and IPv6 packets
<pabelanger> I was not aware that was possible...  Is there a benefit to only opening one socket?
<kpfleming> yes... the code only supports one socket :-)
<pabelanger> hehe
<kpfleming> changing chan_sip to support multiple UDP sockets is a huge job
<kpfleming> so it accepts IPv4 connections on that socket, and the addresses appear in chan-sip as IPv4-mapped IPv6 addresses
<pabelanger> Ok, thanks for the explanation.  Will see about documenting that some where, in-case people do the same thing I just did via netstat
<pabelanger> IPv4 worked btw

By: Russell Bryant (russell) 2010-08-10 16:20:12

This got resolved.