Summary: | ASTERISK-24679: Wrong IAX2 context chosen due to netmask | ||
Reporter: | Marco Paland (mpaland) | Labels: | |
Date Opened: | 2015-01-13 04:52:51.000-0600 | Date Closed: | 2015-02-07 11:17:30.000-0600 |
Priority: | Minor | Regression? | No |
Status: | Closed/Complete | Components: | Channels/chan_iax2 |
Versions: | 13.1.0 | Frequency of Occurrence | Constant |
Related Issues: | |||
Environment: | Debian | Attachments: | |
Description: | 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! | ||
Comments: | By: Matt Jordan (mjordan) 2015-01-13 08:08:39.119-0600 We require a complete debug log to help triage the issue. This document will provide instructions on how to collect debugging logs from an Asterisk machine for the purpose of helping bug marshals troubleshoot an issue: https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information By: Matt Jordan (mjordan) 2015-01-27 12:33:55.991-0600 Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested. Further information can be found at http://www.asterisk.org/developers/bug-guidelines By: Marco Paland (mpaland) 2015-02-07 11:17:30.778-0600 I close this, because the observed behavior might be correct if no explicit username is set. |