Un-top-posting...
>> - "trebaum" 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 foll
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 si
- "trebaum" 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:pas
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
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