[asterisk-users] sip.conf and bindaddr issue

Felix Salfelder felix at salfelder.org
Tue Jul 10 04:13:45 CDT 2012


On Tue, Jul 10, 2012 at 10:24:18AM +0200, Olle E. Johansson wrote:
> The Asterisk SIP channel has no knowledge about interfaces and can't
> bind to a specific interface for communication.

Thanks for the reply.

in the meantime i've found a sort of workaround.

[general]
host = dynamic
; take some local, static address
bindaddr = 192.168.1.1
; and don't use that address very much
localnet = 192.168.0.0/255.255.0.0
; ...

[sip_out]
; pretend nat
nat = route
; ...

i'm not sure about all implications. for example, incoming connections
must be handled with iptables, and in the first second of a call (from
sip_out) theres no sound. i can live with that for a while.

> In fact, it's a well known bug that if you have multiple interfaces
> with different IP networks, Asterisk will send from the wrong IP on
> some of the interfaces.

couldn't find much about it on the net. anyway, if it's well known:
what would be the downside of just (silently, implicitly) taking the
right adress? like when when resolving the peer-host, take a look into
the routing table...?

regards
felix



More information about the asterisk-users mailing list