C6901 registration rejected 12.5 cluster

jean-philippe airaudi · ‎05-20-2023

Hi Folks,

Cucm cluster is 12.5.10000.22 mixed mode

1 pub /6 subs

After CM_Group changes, we are facing issues with only c6901 device that are not able to register to the servers listed in the new CM-Group.

CTL and configuration files are downloaded from tftp server but phones send registration request to the old primary server all the time.

The only way to get registered is to put the old sub server into cm-group.

We can see dbreplication configuration error in rtmt and traces shows us some dns errors but dns is working fine ( it is hospital cluster , dns had been checked and it is up and running ).

When the old server is part of the cm_group , hostnamed are fully resolved so we dont think dns pb.

Other phones than c6901 are not facing the issue...

Some ideas ??

Thanks

Nithin Eluvathingal · ‎05-20-2023

Since you see error on DB, First you must fix it. Then try registering the phones. If you can run utils dbreplication status, wait for some time then run utils dbreplication runtimestate and share the output we can guide you on fixing the DB errors.

Else follow the below guide and you can do it yourself. https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/200396-Steps-to-Troubleshoot-Database-Replicati.html

jean-philippe airaudi · ‎05-21-2023

Hi Nithin Eluvathingal,

Thanks for all,

We already check this part and database status is 2 as expected.

It is very strange that rtmt is showing this status error.

The next step, is to analyse cnf files to see if updates are occuring when we move from old cm_group to New cm_group.

As I said c6901 phones are continuously trying to get registered from old cm-group primary server.

We can see it in wireshark traces.

As soon as we put old primary server into cm_group everything is working fine.

CIsco TAC is asking us to upgrade firmware's phone : they send us some "shadow file" ( not visible from Cisco web site download)

I hope this can be the solution....

I will do the update next week.

Have a nice day.

Jean-Philippe

Nithin Eluvathingal · ‎05-21-2023

Your DB status may be 2 but there could be error in DB table. Can you run utils dbreplication status, wait for some time then run utils dbreplication runtimestate and share the output.

Rejected can also be due to firmware issues.

jean-philippe airaudi · ‎06-10-2023

Hi Nithin Eluvathingal,

we had made some lab tests : we had updated from 12.5.10000.22 to 12.5.1.18100-14 (SU7a).

IP Phone 6901 was able to get registered moving from CM-Group back and forth without any problem.

It seems that it is the solution and as we are working since many weeks to prepare the real update ( Hospital cluster), we are considering that this is the way we need to go.

We also keep going investigate with Cisco TAC : we had sent our diagnostic .

We are wainting for their replies.

Have a nice day

Best regards

Jean-Philippe