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.)
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.
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?
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...