12-18-2017 09:10 AM - edited 03-17-2019 11:48 AM
Hi all,
We are facing some issues on the CUCM Sub 01, we have some Subscribers on same cluster. Only on phones that are registered to Sub01 we are unable to use speed dials ("Speed Dial not configured" message pops up). (We are using CUCM 10.5.2)
I have already checked the dbreplication and it seems to be working properly on all servers in the cluster:
admin:utils dbreplication runtimestate
Server Time: Mon Dec 18 10:56:52 CST 2017
Cluster Replication State: Replication status command started at: 2017-10-24-11-18
Replication status command COMPLETED 681 tables checked out of 681
Last Completed Table: devicenumplanmapremdestmap
No Errors or Mismatches found.
Use 'file view activelog cm/trace/dbl/sdi/ReplicationStatus.2017_10_24_11_18_15.out' to see the details
DB Version: ccm10_5_2_16900_10
Repltimeout set to: 300s
PROCESS option set to: 1
Cluster Detailed View from CUCM-REF211-PUB01 (11 Servers):
PING DB/RPC/ REPL. Replication REPLICATION SETUP
SERVER-NAME IP ADDRESS (msec) DbMon? QUEUE Group ID (RTMT) & Details
----------- ---------- ------ ------- ----- ----------- ------------------
CUCM-REF211-PUB01 10.34.47.197 0.019 Y/Y/Y 0 (g_2) (2) Setup Completed
CUCM-REF211-MOH01 10.34.47.195 0.351 Y/Y/Y 0 (g_3) (2) Setup Completed
CUCM-REF211-SUB01 10.34.47.198 0.115 Y/Y/Y 0 (g_4) (2) Setup Completed
CUCM-REF211-SUB02 10.34.47.199 0.293 Y/Y/Y 0 (g_5) (2) Setup Completed
CUCM-REF075-MOH02 10.35.2.1 5.713 Y/Y/Y 0 (g_6) (2) Setup Completed
CUCM-REF075-SUB05 10.35.2.2 5.336 Y/Y/Y 0 (g_7) (2) Setup Completed
CUCM-REF075-SUB06 10.35.2.3 5.481 Y/Y/Y 0 (g_15) (2) Setup Completed
CUCM-REF075-TFTP02 10.35.2.6 5.453 Y/Y/Y 0 (g_9) (2) Setup Completed
CUCM-REF211-SUB03 10.34.47.200 0.239 Y/Y/Y 0 (g_10) (2) Setup Completed
CUCM-REF211-SUB04 10.34.47.201 0.438 Y/Y/Y 0 (g_11) (2) Setup Completed
CUCM-REF211-TFTP01 10.34.47.202 0.260 Y/Y/Y 0 (g_12) (2) Setup Completed
admin:
I have forced some devices to register on any other subscriber and they are able to use the speed dial configuration, but once I register it back to Sub 01 same problem pops up (unable to use SD).
What may be causing that kind of behavior?
Any help would be so appreciated.
Thanks so much in advance.
Regards, Cesar Arcos
12-18-2017 08:13 PM
12-19-2017 10:42 AM
Hi Mohammed,
I have compared Sub01 config with Sub02 and its exactly the same on them both, so I could assume that is not the problem. :(
12-19-2017 10:38 PM
Can you generate CUCM traces when hit SD and see whats happening.
12-27-2017 10:45 AM
Finally after some days, some errors appeared on the SD database (what is weird because those errors were not present at the very beggining), so we reconstructed it.
Thanks to all for the support.
12-27-2017 01:11 PM
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: