For those who are interested, the problem is being caused by IAX using the wrong
outside IP address as it's source address.
(Multi-homed firewall with numerous virtual interfaces). The workaround was to
add additional definitiions to the other servers, so the connection will be
trunked from the originating (incorrect) address.
Apparently there is a patch against CVS HEAD which allows the definition of the
source address on a per-peer basis.
=========================================Rod Bacon
Empowered Communications
Ground Floor, 102 York St. South Melbourne
Victoria, Australia. 3205
Phone: +613 99401600 Fax: +613 99401650
FWD: 512237 ICQ: 5662270
=========================================
Rod Bacon wrote:> I am having trouble getting trunking to work between a couple of my
> servers.
>
> All servers are running 1.0.9 stable version, and are working perfectly.
> All have a Zaptel card of some description, so timing is not a problem.
> Each server has a definition for each other server, using RSA auth, and
> qualify=yes (just so I can see ping times). trunk=yes is on globally,
> AND in each peer/friend definition.
>
> IAX2 SHOW PEERS shows a (T) next to each server, indicating that a trunk
> will be established.
>
> Servers on the same LAN segment seem to trunk OK. (IAX2 TRUNK DEBUG
> shows meaningful info).
>
> Conenctions where 1 server is behind a firewall works fine, but trunking
> does not seem to work. The only other difference is the codec. On the
> remote servers (the ones behind the firewalls), I'm running G729 (the
> Intel one). The LAN-based servers all talk to each other using G.711.
>
> Anyone have any ideas?
>
>
> _______________________________________________
> --Bandwidth and Colocation sponsored by Easynews.com --
>
> Asterisk-Users mailing list
> Asterisk-Users@lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
> To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-users
>
>