Un-top-posting... >> ----- "trebaum" <treb...@telepaths.org> wrote:
>>> 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 >>> > On Mar 29, 2010, at 1:18 PM, Tim Nelson wrote: > >> Why not add a route to your system for each of the three IPs you'll be >> registering to with their associated interfaces? On Mon, 29 Mar 2010, trebaum wrote: > I thought about that, but there are a couple issues with that. > Currently the physical interface has a single gateway (the only way to > change this is to add more physical interfaces), and that gateway is > what does the routing to the specific peers. Being that all of the > traffic is going to a single point, and I can't specify what interface > the traffic is originating from (in *), when it gets to the default gw > all of the traffic looks the same. I don't have the skills, but I'd bet a beer somebody who knows iptables well could come up with something to mangle the source IP address based on the destination IP address. -- Thanks in advance, ------------------------------------------------------------------------- Steve Edwards sedwa...@sedwards.com Voice: +1-760-468-3867 PST Newline Fax: +1-760-731-3000 -- _____________________________________________________________________ -- 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
