So I realize the error in my question/request.  The section I was thinking of 
using for the binding IP address, is, itself, the wrong place to do such a 
thing.  It would need to be in the register statement... something like the 
following...

register => user:pass:fro...@targetpeer

I do realize that this functionality doesn't currently exist.  Requests will be 
made in the appropriate places.  Thanks for the help.

:)

~ T

On Mar 29, 2010, at 12:03 PM, trebaum wrote:

> Is there anyway to get the following scenario to work...
> 
> I have 3 IAX trunks that I want to setup to peer with other * boxes.  I have 
> 1 physical interface, eth0.  I also have 2 sub interfaces, eth0:1 & eth0:2.  
> I want to setup a single IAX trunk on each of the interfaces.  All 3 
> interfaces are going to have separate publicly routable IPs, and for this 
> purpose, let's say that because of operational restrictions, I cannot just 
> setup all 3 physical interfaces.
> 
> What would really be nice, is if in the entries for each of the trunks to be 
> able to use the bindaddr setting per trunk.  This would allow me to be able 
> to connect trunk1 from eth0, trunk2 from eth0:1, trunk3 from eth0:2.
> 
> Thanks
> 
> ~ T
> 
> 
> -- 
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> New to Asterisk? Join us for a live introductory webinar every Thurs:
>               http://www.asterisk.org/hello
> 
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users


-- 
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
               http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Reply via email to