01-28-2022 12:44 PM - edited 01-28-2022 12:50 PM
ccm02test:Jan 27 11:24:00 ccm02test Jan 27 2022 16:24:00.191 UTC : %UC_CALLMANAGER-3-EndPointUnregistered: %[DeviceName=SEP2834A2FFFFA1][IPAddress=1.1.2.2][Protocol=SIP][DeviceType=685][Description=Adam Pawlowski 8861][Reason=6][IPAddrAttributes=0][LastSignalReceived=SIPConnControlInd][MRAStatus=0][AppID=Cisco CallManager][ClusterID=CCM01TEST-Cluster][NodeID=ccm02test]: An endpoint has unregistered ccm02test.log:Jan 27 11:24:00 ccm02test : : 762: ccm02test Jan 27 2022 16:24:00.189 UTC : %UC_CALLMANAGER-3-EndPointUnregistered: %[DeviceName=SEP2834A28FFFA1][IPAddress=1.1.2.2][Protocol=SIP][DeviceType=685][Description=Adam Pawlowski 8861][Reason=6][IPAddrAttributes=0][LastSignalReceived=SIPConnControlInd][MRAStatus=0][AppID=Cisco CallManager][ClusterID=CCM01TEST-Cluster][NodeID=ccm02test]: An endpoint has unregisteredThe UCM shows a socket error, regarding the connection being closed, before it tears down the device registration:
tvcs: UTCTime="2022-01-27 16:11:55,757" Module="developer.sip.transport" Level="DEBUG" CodeLocation="ppcmains/sip/siptrnsp/SipSockMap.cpp(384)" Method="SipSockMap::closeSocketAndFreeEntry" Thread="0x7f5e10fbb640": LocalId="459358807" LocalAddr="['IPv4''TCP''1.1.2.2:26979']" RemoteAddr="['IPv4''TCP''1.1.2.60:5060']" Type="SIP_SOCKTYPE_TCP_OUTG" Detail="Closing Socket" Reason="Manually forced disconnect"In a wireshark trace, this is a FIN coming from the Expressway towards the UCM.
2022-01-27T10:07:38.996-05:00 tvcs: UTCTime="2022-01-27 15:07:38,995" Module="developer.sip.transport" Level="INFO" CodeLocation="ppcmains/sip/siptrnsp/siptrnspsfsm.cpp(4334)" Method="::SIPTRNSP_doStunTimeoutSocketClose" Thread="0x7f5e10fbb640": freeing cucm socket connection
Disabling STUN keepalive in the Expressway C does not fix this. The workaround in the bug does. You can change the name of the Expressway C entry , under Devices -> Expressway -C , in your UCM, to FQDN instead of hostname. This is assuming you let it auto populate.
The phones and Jabber have their socket open to the Expressway - E so they don't reflect that they've lost registration. Attempting to place a call from them results in maybe it working briefly if it's currently registered, but otherwise a fast busy.
As others are moving to CSR 14 I figured I'd post this to save some trouble and hair pulling if this comes up in search.
Sorry for posting this in edit blocks but the community kept giving me blob conversion errors (?) and eating my post.
01-28-2022 01:33 PM
Thank you for your sharing this @Adam Pawlowski This is exactly what we saw when we where on CM14SU1 for a short period on our pre-production system and TAC never could find the reason for this, so in the end we rolled back to 12.5SU5. Will check the details on the bug note and try to upgrade once more. Again a big thank you, appreciate you taking the time to share this!
02-01-2022 02:53 AM
Follow up on this. We upgraded our pre-production system yesterday again to CM 14 and put the workaround in-place. With this we're not seeing the same issues we had back in late 2021 when we last tried this version on this system. Again a BIG thank you @Adam Pawlowski for taking the time to share this with the community.
02-01-2022 07:44 AM
Superstar @Anthony Holloway suggested I take another crack at posting with some follow up on the alarm code and reason. I have some cheat sheets and crib notes on various reason codes, but I often forget that I can go right to the source on these, like I did in this case.
Alarms like EndPointUnregistered have detail information available in the serviceability section of the UCM:
I'm guilty of forgetting this is here, and then searching "reason code" or something on the forums and hoping I get the right answer. In this case I didn't find much of anything for 6 and assumed it was related to the TCP connection closing after I saw what was happening.
Breaking out the telescope to read what it means from the search above:
In this case I guess I can infer that 'ConnectivityError' generally includes socket errors, connection closing, or being closed. If the device had actually unregistered and sent an alarm itself, another number could possibly have been used here. But with this being MRA the devices don't actually know they've lost registration. Jabber also was logged with a reason of 6 in this scenario.
11-10-2022 09:54 AM
Excellent post. The fix is converting expressway C hostname to FQDN.
Once the Cs were updated to FQDN in CUCM, no more disconnected calls from MRA phone, in this case an 8845.
Prior to change calls outbound from 8845 would connect, media established on both sides but roughly 10 seconds in, 8845 would drop call. Then fast busy on further outbound attempts. Call would still show connected on called device.
Thanks again for this very helpful post Adam Pawlowski.
01-18-2024 02:34 AM
Hello, I have same issue with Cisco Jabber for PC and mobile phone client, but no problem with DX70 with MRA. Your fix solution cannot help me, no idea why. Expressway 15.0, CUCM 14 SU3. May be anybode knows how to fix this issue?
02-08-2024 05:19 AM
I have the same issue on CP7821 and CP8851 phones. Phones register through MRA but then unregister after about 30 sec. The status messages of the phone show 'Reset-Restart'.
02-08-2024 05:48 AM
Changing the name of expressway C in CUCM does not resolve my problem...
02-08-2024 07:10 AM
02-08-2024 07:44 AM
Hi Adam,
thanks for your reply. I opened a TAC case for this. They had me remove the CUCM configuration on the expressway C and reconfigure it. After that, the phones stay registered.
We still have problems using Jabber over MRA though. On the expressway C, I see that the user is authorized, but the Jabber client goes back to the login screen after that.
02-09-2024 06:00 AM
04-15-2024 03:26 AM - edited 04-16-2024 01:25 AM
So Refresh was not enough at EXP-C? OR didi you even do, i didn't 1st and learned that it need to be done.
EXP-C go to Configuration > Unified Communications > Unified CM servers and click Refresh servers.
Step 2 For Unity Connection, go to Configuration > Unified Communications > Unity Connection servers and click Refresh
servers (if exists). Seem to be easy to spot as EXP-C seem to show old SW version info until Saved or Refreshed.
04-16-2024 05:53 AM
08-23-2024 04:58 AM
same here dint helped it , i am using MRA for webex app phone service and MRA Registration Flaps for every 40 seconds and evens calls drops in this time frame, can anyone suggest
06-14-2024 03:33 AM
New update: (maybe this help)
last day, I was on a project and got an error as this:
external jabber calls on the expressway goes on Preservation mode after 40 seconds, then its disconnected.
I did these two steps and the problem was solved:
1- changed the expressway core hostname to full FQDN in cucm >> device >> expressway-c
2- set DNS + domain name to CUCM + CUP (ssh to them >> set network dns.. + set network domain..) (I forgot to do this..)
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