[asterisk-bugs] [Asterisk 0016561]: Ignores bindaddr on reload
Asterisk Bug Tracker
noreply at bugs.digium.com
Thu Dec 2 12:20:43 CST 2010
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=16561
======================================================================
Reported By: blanchae
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 16561
Category: Channels/chan_iax2
Reproducibility: always
Severity: minor
Priority: normal
Status: new
Asterisk Version: Older 1.6.1 - please test a newer version
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2010-01-06 16:44 CST
Last Modified: 2010-12-02 12:20 CST
======================================================================
Summary: Ignores bindaddr on reload
Description:
chan_iax2.c: Ignoring bindaddr on reload
This bug was noted on
* FreePBX : 2.5.1
* Asterisk Source Version : 1.6.0.6
* Dahdi Source Version : 2.1.0.4+2.1.0.2
* Libpri Source Version : 1.4.9
* Addons Source Version : 1.6.0.1
With IAX2 and the iax_general_custom.conf file. bindaddr=xxx.xxx.xxx.xxx
is ignored on reload. It defaults back to address 0.0.0.0 which is any
interface.
======================================================================
----------------------------------------------------------------------
(0129277) blanchae (reporter) - 2010-12-02 12:20
https://issues.asterisk.org/view.php?id=16561#c129277
----------------------------------------------------------------------
It appears that the "failed to load on reload" is normal. Still have the
problem where it doesn't bind properly.
Okay, correct me if I'm wrong but the purpose of this command is to direct
IAX2 out a specific port. If I have two NIC cards (eth0 and eth1) in my
server then I should be able to bind IAX2 to just one of them by issuing
the command "bindaddr=192.168.103.254" (eth0)in
/etc/asterisk/iax_general_custom.conf (assuming that this file is included
in iax.conf).
What happens is that IAX2 will still go out eth1. This is easily verified
by using iptables to drop IAX2 traffic on eth1, IAX2 clients fail to
register. Strangely, SIP doesn't have this problem when using bindaddr.
Test conditions: laptop on 192.168.102.0 network (voice), using both Adore
IAX softphone client and Xlite SIP softphone client (for comparison) to
register to 192.168.103.254 (eth0) server. Server's eth1 is on
192.168.102.0 network (data). Both protocols have bindaddr=192.168.103.254
(server's voice interface). SIP works as expected and the server responds
on the voice interface, IAX2 does not.
This might be a routing problem in Linux as packet sniffing
192.168.102.254 indicates eth1's mac address. Strangely dropping SIP on
eth1 doesn't affect SIP registration. So SIP works fine regardless but IAX2
doesn't.
Issue History
Date Modified Username Field Change
======================================================================
2010-12-02 12:20 blanchae Note Added: 0129277
======================================================================
More information about the asterisk-bugs
mailing list