Summary:ASTERISK-08094: iax.conf and sip.conf bindaddr don't listen on every interface
Reporter:Eric Romang / DCLUX (eromang)Labels:
Date Opened:2006-11-09 03:45:06.000-0600Date Closed:2011-06-07 14:08:16
Versions:Frequency of

As described into :


"bindaddr:  If multiple IP addresses are available in the same system, this option may be set to bind Asterisk to a single interface."

If I understand, if you have multiple IP adresses and you want that asterisk lisen on each IP, you don't put into the config bindaddr, or you could put bindaddr= ?

I have test with this test :

eth0 inet addr:80.92.xxx.xxx  Bcast:80.92.xxx.xxx  Mask:
eth0 inet addr:80.92.bbb.bbb  Bcast:80.92.xxx.xxx  Mask:
lo:0 inet addr:80.92.yyy.yyy  Mask:

If I don't put bindaddr or put bindaddr= into the iax.conf file,
the registration and calls only works on eth0 and eth0:0, but not on lo:0

If you put bindaddr=80.92.yyy.yyy into the iax.conf file, the registration will work on lo:0

The conclusion is that the bindaddr= or missing bindaddr into the iax.conf dont listen on every interface a server, and don't listen on interface lo:0

Why listen on lo:0 ? Using LVS (Linux Virtual Server) need to have VIP declared on loopback.

This bug is also on sip.conf, 1.2 TRUNK, 1.4.beta3, 1.4 TRUNK

Comments:By: Eric Romang / DCLUX (eromang) 2006-11-09 03:47:31.000-0600

Correction :

eth0 inet addr:80.92.xxx.xxx Bcast:80.92.xxx.xxx Mask:
eth0:0 inet addr:80.92.bbb.bbb Bcast:80.92.xxx.xxx Mask:
lo:0 inet addr:80.92.yyy.yyy Mask:

By: Eric Romang / DCLUX (eromang) 2006-11-09 05:13:12.000-0600


Another bug founded into the 1.2.13

lo:0 inet addr:80.92.yyy.yyy Mask:

If you put into sip.conf bindaddr=80.92.yyy.yyy, sip registration don't work
But if you put into sip.conf bindaddr=80.92.yyy.yyy on the 1.4 beta 3, sip registration work


By: Anthony LaMantia (alamantia) 2006-11-13 14:08:53.000-0600

please show the output, of netstat -an,
when you set bindaddr=, also after looking at the code you should be able to have 2 bindaddr statments inside of your iax.conf problem and the connections will still be managed correctly by the channel, you may also want to try this and report back if this solves the problem for you.

By: Anthony LaMantia (alamantia) 2006-11-14 17:44:05.000-0600

** poke eromang **

By: Anthony LaMantia (alamantia) 2006-11-17 15:23:19.000-0600

(lost contact with reporter)
if you are still having problems please reopen this bug report.