[asterisk-users] Asterisk, IAX, Sub interfaces
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
Re: [asterisk-users] Asterisk, IAX, Sub interfaces
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
Re: [asterisk-users] Asterisk, IAX, Sub interfaces
- 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 Why not add a route to your system for each of the three IPs you'll be registering to with their associated interfaces? Tim Nelson -- _ -- 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
Re: [asterisk-users] Asterisk, IAX, Sub interfaces
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. ~ T On Mar 29, 2010, at 1:18 PM, Tim Nelson wrote: - 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 Why not add a route to your system for each of the three IPs you'll be registering to with their associated interfaces? Tim Nelson -- _ -- 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
Re: [asterisk-users] Asterisk, IAX, Sub interfaces
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
