11-14-2012 04:29 AM - edited 03-16-2019 02:11 PM
Hi people,
Does anybody knows something like this ReasonForOutOfService=23
A reset on Cisco IP phone 9971 when it is a Call ou Conference?
CallId:d824bd26-e6f9156e-6727c604-6075c34e@10.x.196.xx | |
16:42:10 LastOutOfServiceInformation DeviceName=SEPD824XXXXE6F9 DeviceIPv4Address=10.x.196.xx IPv4DefaultGateway =10.x.196.xx DeviceIPv6Address= IPv6DefaultGateway= ModelNumber=CP-9971 NeighborIPv4Address=10.x.193.y NeighborIPv6Address= NeighborDeviceID=WSPXW0X.acme.com.br NeighborIPortID=GigabitEthernet3/0/32 DHCPv4Status=1 DHCPv6Status=3 TFTPCfgStatus=1 DNSStatusUnifiedCM1=4 DNSStatusUnifiedCM2=4 DNSStatusUnifiedCM3=3 VoiceVLAN=230 UnifiedCMIPAddress=10.x.196.xx LocalPort=50306 TimeStamp=1352832130 ReasonForOutOfService=23 LastProtocolEventSent= LastProtocolEventReceived=Rcvd:SIP/2.0 200 OK Cseq:41602 REGISTER CallId:d824bd26-e6f91593-0a5aee69-7955c4b6@10.x.196.xx |
Best regards
Daniel
12-20-2012 10:33 AM
Hi Daniel,
Did you ever identify the root cause of that alert?
TIA,
Amir
06-06-2014 09:56 AM
Hi,
Not yet. But stopped happening without explanation. For a while I suspected the firewall checkpoint, but cannot prove.
Best regards,
Daniel
06-06-2014 10:01 AM
Ah - the worst kind of resolution as it leaves you with no answer. : )
Amir
06-04-2014 09:18 AM
Hi Daniel,
The post is very old now, but...
Did you manage to get the information for this Reason code ?
I have seen this at an other customer as well.
Kind regards,
Jos
06-05-2014 10:13 PM
Hi Jos
Are you also getting the reason code 23??
Reason Code 23 means:
SourceIPAddrChanged - (SIP Only) The device has been unregistered because the IP address in the Contact header of the REGISTER message has changed. The device will be automatically re-registered. No action is necessary.
Thanks
Sanjay
06-06-2014 09:47 AM
Hi Sanjay,
thanks for your response.
It looked like our reasoncode 23 was a different one.
i used the following link to find the info:
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/err_msgs/9_x/ccmalarms901.html
the log showed:
Jun 03 14:28:07 CUCM01 local7 3 : 11164: CUCM01 Jun 03 2014 12:28:07 UTC : %UC_-3-LastOutOfServiceInformation: .....[ReasonForOutOfService=23]
but this does not match, the cause code was 6 in a other trace part.
and the reason code mentioned above can't be found.
6 ConnectivityError - Network communication between the device and Unified CM has been interrupted. Possible causes include device power outage, network power outage, network configuration error, network delay, packet drops, and packet corruption. It is also possible to get this error if the Unified CM node is experiencing high CPU usage. Verify that the device is powered up and operating, verify that network connectivity exists between the device and Unified CM, and verify that the CPU utilization is in the safe range (you can monitor this via the CPU Pegging Alert in RTMT).
regards, Jos
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