SIP Trunk with multiple connections
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-04-2022 10:24 AM
Currently, we have one physical connection to our carrier. Instead of adding a new physical connection to our CUBE, they would like to use the same physical link and I configure either sub-interfaces or a secondary IP address.
I'm leaning towards a secondary IP address configuration.
My question: when traffic is forwarded internally from the CUBE to CUCM, will it use the IP address the traffic was destined to from the carrier as the source address or will it use the primary IP address for all traffic? It's my understanding that the CUBE does not support BIND statement.
Open to any suggestions
- Labels:
-
WAN
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-04-2022 10:49 AM
The way ive done it is I get the routable secondary SIP handoff then add it to my:
voice service voip
ip address trusted list
voice class server-group 100
ipv4 1.1.1.1 port 5060 preference 1
ipv4 1.1.1.2 port 5060 preference 2
I have two dial peers with the session targets. If Dial Peer 1 pointing to server 1 fails Dial Peer 2 will send to the second SIP. These are both egress dial-peers.
As long as you are able to communicate to both IPs from the cube you will able to create the dial peer. I test the failover dial peer by just remove the route to the primary SIP address and only allowing the secondary address routable on the network.
