Re: Crash File Detected issue

marcoantonio.vazquez · ‎11-01-2017

Hi community,

I have a problem with CP 8865, sometimes when users are on a call their phones reset, even when the phone is on hook, checking phone logs we realized we have the next out of service codes,

[17:56:51 01/11/17] DeviceTLInfo DeviceName=SEP00C1B1FDBCA2 IPv4Address=10.90.166.117 IPv6Address=CTL_Signature=Not InstalledCTL_TFTP_Server=N/AITL_Signature=E5 8F 7C E8 46 E3 F0 5C 16 99 C9 87 E8 BC 17 B1 F2 DC DA C5 ITL_TFTP_Server=091402CU49.infonavit.netStatusCode=3

[17:56:57 01/11/17] DeviceName=SEP00C1B1FDBCA2 DeviceIPv4Address=10.90.166.117/24 IPv4DefaultGateway=10.90.166.1 DeviceIPv6Address= IPv6DefaultGateway= ModelNumber=CP-8865 NeighborIPv4Address=10.90.101.109 NeighborIPv6Address= NeighborDeviceID=SEP706E6D11B5EE.infonavit.net NeighborPortID=SW PORT DHCPv4Status=1 DHCPv6Status=3 TFTPCfgStatus=1 DNSStatusUnifiedCM1=0 DNSStatusUnifiedCM2=0 DNSStatusUnifiedCM3=0 DNSv6StatusUnifiedCM1=0 DNSv6StatusUnifiedCM2=0 DNSv6StatusUnifiedCM3=0 VoiceVLAN=31 UnifiedCMIPAddress=10.90.4.79 LocalPort=50464 TimeStamp=1509491243001 ReasonForOutOfService=25 LastProtocolEventSent=Sent:REFER sip:10.90.4.79 SIP/2.0 Cseq:1000 REFER CallId:00c1b1fd-bca20005-6c9b68dc-5abf2912@10.90.101.6 LastProtocolEventReceived=Rcvd:SIP/2.0 200 OK Cseq:173 REGISTER CallId:00c1b1fd-bca20003-722876c5-1f10f830@10.90.166.117 ReasonForOutOfServiceText=LastTimeInitialized

[17:57:01 01/11/17] DeviceName=SEP00C1B1FDBCA2 DeviceIPv4Address=10.90.166.117/24 IPv4DefaultGateway=10.90.166.1 DeviceIPv6Address= IPv6DefaultGateway= ModelNumber=CP-8865 NeighborIPv4Address=10.90.101.109 NeighborIPv6Address= NeighborDeviceID=SEP706E6D11B5EE.infonavit.net NeighborPortID=SW PORT DHCPv4Status=1 DHCPv6Status=3 TFTPCfgStatus=1 DNSStatusUnifiedCM1=0 DNSStatusUnifiedCM2=0 DNSStatusUnifiedCM3=0 DNSv6StatusUnifiedCM1=0 DNSv6StatusUnifiedCM2=0 DNSv6StatusUnifiedCM3=0 VoiceVLAN=31 UnifiedCMIPAddress=10.90.4.79 LocalPort=0 TimeStamp=1509580621033 ReasonForOutOfService=114 LastProtocolEventSent=Sent:REFER sip:10.90.4.79 SIP/2.0 Cseq:1000 REFER CallId:00c1b1fd-bca20005-6c9b68dc-5abf2912@10.90.101.6 LastProtocolEventReceived=Rcvd:SIP/2.0 200 OK Cseq:101 REGISTER CallId:00c1b1fd-bca20003-377d45be-33300994@10.90.166.117 ReasonForOutOfServiceText=Crash File Detected

ReasonForOutOfService=25

ReasonForOutOfServiceText=LastTimeInitialized

ReasonForOutOfService=114

ReasonForOutOfServiceText=Crash File Detected

We want to know what exactly do these codes mean?

Our CUCM version is 11.5.1.13900-52

Firmware version is sip8845_65.11-7-1-17

Greetings.

Rajan · ‎11-01-2017

Hi,

Reason code 25 means:

25 RegistrationSuccessful - The device has initialized and is unaware of any previous connection to the Cisco Unified CM

reason code 114 is missing in the documentations. I do see a defect opened for some missing reason codes but still i dont see 114 anywhere.

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvb63000/?referring_site=bugquickviewredir

HTH
Rajan
Pls rate all helpful posts

marcoantonio.vazquez · ‎11-13-2017

Hi Rajan,

Thanks for your answer, we have been working on it and we realized when a call establishes codec OPUS is used between our phones, we found some bugs related with this codec, it includes crash file detected and drop of calls.

Regardless og this bug we´ll continue monitoring this issue.

Thanks.

marcoantonio.vazquez · ‎11-13-2017

FYI.

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCve01459/?referring_site=bugquickviewredir

Caleb.Jameson1 · ‎04-08-2021

We are receiving the same issue but we are NOT using OPUS at all.

Kaloyan · ‎04-09-2021

Hello,

I see that you are using an old firmware from 2017. There are many fixed bugs related to 88XX crashes since then. You may consider upgrading your phones with the latest 12.8 firmware (cmterm-8845_65-sip.12-8-1-0101-482) firmware https://software.cisco.com/download/home/286286015/type/282074288/release/12.8(1)SR1.