We have a 2 node CCM 7.1 and Unity Conection 7.1.
Last week we were doing some maintenance and I noiced that when the Publisher was off line that calls to the main number were not getting through to Unity.
Calls to other DDI's were working fine via the Subscriber and I confirmed that the Gateway was using dial-peers for both servers for the main number.
I thought I found the solution yesterday as the port configuration for servers in Unity had an old IP for the subscriber but after changing that and reseting the port group the problem still seems to persist ( we gave it a couple of minuets with the switchport to the Publisher shutdown ).
Where else can I check?
Make sure your CUCM group assigned to all the VM elements have both servers listed and on CUC side that you have both servers configured, and as far as I can remember, it asks you to restart some services when addidng/modifying servers on CUC side.
if this helps, please rate
|Registration||Registered with Cisco Unified Communications Manager 172.16.10.10|
|Device is trusted|
So the ports are in the "DP-RRCA" dev pool
the dev pool has the "CMG-RRMA-RRCA" Call manager group
the call manager group has the two CM's 172.16.10.10 and 10.137.0 10
Can you check these settings in CUC for the "Secondary" server config;
Step 32 On the Edit Servers page, do the following substeps if the Cisco Unified CM cluster has secondary servers. Otherwise, skip to Step 33.
Enter the order of priority for the Cisco Unified CM server. The lowest number is the primary Cisco Unified CM server, the higher numbers are the secondary servers.
IP Address or Host Name
Enter the IP address (or host name) of the secondary Cisco Unified CM server.
Enter the TCP port of the Cisco Unified CM server that you are integrating with Cisco Unity Connection. We recommend that you use the default setting.
Enter the TLS port of the Cisco Unified CM server that you are integrating with Cisco Unity Connection. We recommend that you use the default setting.
Click Cisco Unified Communications Manager.
"Every fool's got a reason to feelin' sorry for himself" - Springsteen
I looked again at the servers and the Subscriber had priority 0 the same as the Publisher
I have changed it to 1 and reset the port group.
Will test it in a little while when the staff have gone home.
Well it did not work at first, took a minuet or two to hop over . I am not sure how long it should take ?
It may have been ok last week when I changed the subscriber server entry in Unity from the old IP to the new one (which should have been done by the company moving the ssytem last septembre!) .. Perhaps I did not give it enoug time but we were runnign out the door.
Anyway having the correct priority can't be a bad thing.