02-13-2015 11:17 AM - edited 03-17-2019 01:58 AM
We use CUBE to peer with our vendor across a SIP trunk to handle incoming calls for our contact center.
On our end, in the DMZ, we're using CUBE. On the vendor's end, they are using a Sonus session border controller.
(Internally, on our enterprise network, we have a SIP trunk set up between CUCM and CUBE to pass on the incoming calls from our external vendor)
Our vendor is moving their equipment to a data center in a geographically disparate data center. They will be changing the IP addresses we are peering with.
Aside from making the appropriate access-list changes on our firewall and updating the ip address trusted list on our CUBE, are there any other changes we need to make make in CUBE or on our CUCM Publisher since it is just our external vendor that will be using different IP's for their session border controller?
John
Solved! Go to Solution.
02-13-2015 12:35 PM
It will be transparent to CUCM as he has no idea of the other end, he only speaks to your CUBE, all the changes will be done in the CUBE that you mention, ip address trusted list is not necessary if you already have their IP in a dial-peer, doesn't hurt to add, but not strictly required
02-13-2015 12:35 PM
It will be transparent to CUCM as he has no idea of the other end, he only speaks to your CUBE, all the changes will be done in the CUBE that you mention, ip address trusted list is not necessary if you already have their IP in a dial-peer, doesn't hurt to add, but not strictly required
04-27-2015 01:45 PM
Thank you.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide