CUCM 9.1 and third party call center integration over SIP trunk
I have a question regarding a failover of SIP trunks to a third party call center.
We have setup the integration and works fine. However we are trying to setup Survivability once the SIP trunk to the third party fails, we would like to route calls to CUCM hunt groups.
Here is a brief facts of the current setup.
- All calls from the Agent phones is routed via the contact center, this was asked for the purpose of Reporting.
- All calls to the Agents is routed via the contact center, this was asked for the purpose of Reporting.
What we are hoping to achieve is if the SIP trunks fail or the contact center fails, we would like to be able to fail to CUCM hunt groups. And calls for any local extension or hunt groups to go directly.
Well, there is no easy way to do this automatically as SIP trunk indicates the call goes via a route pattern --> route list --> route group and your only redundancy would be to have another route group pointing somewhere else, obviously a route group needs to point to GW/Trunk and not a hunt pilot, so your only option would be to hairpin the call through a trunk or GW of some kind, i.e. build a GW with dial-peers that loop back to CUCM and then trigger the hunt pilot, for example if the call center destination is 2000, the dial-peer with destination-pattern 2000 would be triggered and re-directed back to CUCM, you would translate the call as it enters CUCM (via dedicated CSS on the trunk pointing to TP) and then the hunt pilot would be matched.
I should have mentioned, the survivability is not just for hunt groups. Basically to call any other extension on the cluster or outbound calls directly to the local gateway, without going via the contact center.
Great to see Carlo already tested this.
Will it be any chance of a call looping around? And if there is it will be detected by CUCM?
I will give this a shot, creating a SIP trunk to CUCM itself.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.