[asterisk-bugs] [JIRA] (ASTERISK-24679) Wrong IAX2 context chosen due to netmask
Matt Jordan (JIRA)
noreply at issues.asterisk.org
Tue Jan 27 12:35:35 CST 2015
[ https://issues.asterisk.org/jira/browse/ASTERISK-24679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Jordan updated ASTERISK-24679:
-----------------------------------
Assignee: (was: Matt Jordan)
> Wrong IAX2 context chosen due to netmask
> ----------------------------------------
>
> Key: ASTERISK-24679
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-24679
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Channels/chan_iax2
> Affects Versions: 13.1.0
> Environment: Debian
> Reporter: Marco Paland
> Severity: Minor
>
> I have the following iax.conf:
> {code}
> [general]
> bindport=4569
> bindaddr=192.168.3.1
> allow=all
> jitterbuffer=yes
> forcejitterbuffer=no
> ; ------------------------------
> [trunk-han]
> host=192.168.1.15
> type=friend
> qualify=yes
> trunk=yes
> disallow=all
> allow=g722
> allow=g726
> allow=alaw
> allow=ulaw
> context=from-trunk-han
> deny=0.0.0.0/0.0.0.0
> permit=192.168.1.0/255.255.255.0
> [trunk-bre]
> host=192.168.2.1
> type=friend
> qualify=yes
> trunk=yes
> disallow=all
> allow=g722
> allow=g726
> allow=alaw
> allow=ulaw
> context=from-trunk-bre
> deny=0.0.0.0/0.0.0.0
> permit=192.168.2.0/255.255.255.0
> {code}
> Trunks are connected via VPN tunnels, trunk-bre is not active, but it doesn't matter. The above conf seems to be working so far.
> The problem:
> Set permit to {code}permit=192.168.0.0/255.255.0.0{code} on both trunks (whole intranet allowed).
> Then incoming call on trunk-han which originates at 192.168.1.15
> But the call of trunk-han is processed in the from-trunk-bre context, even if trunk-bre is not connected!
> It should/must be processed in from-trunk-han context!
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list