[asterisk-bugs] [JIRA] (ASTERISK-30435) ipv6 client can't qualify/register if 1st bind address is ipv4 and vice versa
tootai (JIRA)
noreply at issues.asterisk.org
Tue Feb 21 08:46:03 CST 2023
tootai created ASTERISK-30435:
---------------------------------
Summary: ipv6 client can't qualify/register if 1st bind address is ipv4 and vice versa
Key: ASTERISK-30435
URL: https://issues.asterisk.org/jira/browse/ASTERISK-30435
Project: Asterisk
Issue Type: Bug
Security Level: None
Components: Channels/chan_iax2
Affects Versions: 18.16.0, 20.0.1
Environment: Linux Debian 11 Linux Ubuntu 22
Reporter: tootai
Severity: Major
If bind address in iax conf looks like
port 4569
bindaddr 1.2.3.4
bindaddr [2001:db8::1] ; or without [ ]
registration of ipv6 client as well as qualify will fail, peer is always chown as UNREACHABLE but an only ipv6 client can connect as user.
If we put ipv4 bindaddr after the ipv6 one, same append to ipv4 client.
This means that both protocols can't be used at the same time
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list