shikamarunara Thu, 08/02/2007 - 07:49

I think the only thing you can set up is a bindle for both of the NICs, then configure the SIP trunk to point at the assumed IP address for that group. However, this would only work for redundancy (i.e; one fails, the other takes over.)


abartolomeu Thu, 08/02/2007 - 07:59

Actually I'm using one interface for everything except for this specific SIP trunk. For this trunk I need to use the other. How do I allow this?

abartolomeu Thu, 08/02/2007 - 08:21

It's only a solution design's issue. It's a front-end/back-end topology.

shikamarunara Thu, 08/02/2007 - 08:30

I don't think segmenting a SIP trunk to a different interface solves anything. If you're concerned with redundancy, you can solve that with a NIC bundle. In fact, I'm pretty sure that this is going to cause a LOT more trouble than it will fix.


Majdi Harb Thu, 08/02/2007 - 08:33

so are you going to configure private IP on the local interface (first NIC) for say IP phones and a public IP on the outside interface (second NIC) for SIP trunk to be reachable by internet without being behinfd NAT?


abartolomeu Thu, 08/02/2007 - 08:58

It's not for redundancy.

Both NIC's are private but one "belongs" to the front-end and the other to the back-end.


This Discussion