cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
520
Views
0
Helpful
1
Replies

Csf profiles and desk phones took a long time to register.

Arvin
Level 1
Level 1

Hi Team,

We have some csf device profiles and some desk phones taken a very long time to register with cucm. Though this is not happening atm I'm trying to figure out the root cause. Upon doing a troubleshooting on wireshark nothin noted, when pinged the device from the registered cucm subscriber, ping was successful. Cucm cluster is fine, CPU memory is not at full usage which is good. Could anybody advise on this issue please. 

One example is a csf device which took 30min to register when user was onsite and when tried logging in from home it took over an hour.

Logs when connected from onsite :

Reason for out of service - last time config mismatch 

String name="DeviceName">CSFu0024173</String>
Line 8502: 65122299.004 |15:28:15.707 |AppInfo |GenAlarm: AlarmName = LastOutOfServiceInformation, subFac = KeyParam = , severity = 3, AlarmMsg = DeviceName : CSFu0024173
Line 8533: 65122299.007 |15:28:15.708 |AppInfo |LastOutOfServiceInformation - Information related to the last out-of-service event Device Name:CSFu0024173 Device IPv4 Address:10.2.1.57 / 0 IPv4 default gateway:10.2.1.254 Device IPv6 Address: IPv6 default gateway: Model Number:CSF Neighbor IPv4 Address: Neighbor IPv6 Address: Neighbor Device ID: Neighbor Port ID: DHCPv4 Status:1 DHCPv6 Status:3 TFTP Configuration Status:1 DNSv4 Status on Unified CM 1:1 DNSv4 Status on Unified CM 2:1 DNSv4 Status on Unified CM 3:3 Voice VLAN:0 CUCM IP Address:uc-cmucm2-s1.hbs.net.au Local Port:62949 Time Stamp:1678339695 Reason For Out Of Service:101 UNKNOWN_PARAMNAME:ReasonForOutOfServiceText:LastTimeConfigMismatch UNKNOWN_PARAMNAME:ActiveInterface:Wired Last Protocol Event Sent:Sent:SIP/2.0 200 OK Cseq:101 REFER CallId:2f9d8700-40916e6f-18fec1-b9196e0a@10.110.25.185 Last Protocol Event Received: App ID:Cisco CallManager Cluster ID:HeritageCluster Node ID:uc-cmucm2-s1
Line 8534: 65122299.008 |15:28:15.708 |AlarmErr |AlarmClass: Phone, AlarmName: LastOutOfServiceInformation, AlarmSeverity: Error, AlarmMessage: , AlarmDescription: Information related to the last out-of-service event , AlarmParameters: DeviceName:CSFu0024173, DeviceIPv4Address:10.2.1.57 / 0, IPv4DefaultGateway:10.2.1.254, DeviceIPv6Address:, IPv6DefaultGateway:, ModelNumber:CSF, NeighborIPv4Address:, NeighborIPv6Address:, NeighborDeviceID:, NeighborPortID:, DHCPv4Status:1, DHCPv6Status:3, TFTPCfgStatus:1, DNSStatusUnifiedCM1:1, DNSStatusUnifiedCM2:1, DNSStatusUnifiedCM3:3, VoiceVLAN:0, UnifiedCMIPAddress:uc-cmucm2-s1.hbs.net.au, LocalPort:62949, TimeStamp:1678339695, ReasonForOutOfService:101,

—-------

When Csf connected from home :

Reason code 14

GenAlarm: AlarmName = LastOutOfServiceInformation, subFac = KeyParam = , severity = 3, AlarmMsg = DeviceName : CSFu0024173
Line 65193: 66445711.007 |18:13:56.869 |AppInfo |LastOutOfServiceInformation - Information related to the last out-of-service event Device Name:CSFu0024173 Device IPv4 Address:10.2.25.237 / 0 IPv4 default gateway:192.168.0.1 Device IPv6 Address: IPv6 default gateway: Model Number:CSF Neighbor IPv4 Address: Neighbor IPv6 Address: Neighbor Device ID: Neighbor Port ID: DHCPv4 Status:1 DHCPv6 Status:3 TFTP Configuration Status:1 DNSv4 Status on Unified CM 1:1 DNSv4 Status on Unified CM 2:1 DNSv4 Status on Unified CM 3:3 Voice VLAN:0 CUCM IP Address:uc-cmucm2-s1.hbs.net.au Local Port:4294967295 Time Stamp:1678349635 Reason For Out Of Service:14 UNKNOWN_PARAMNAME:ReasonForOutOfServiceText:cm-closed-tcp UNKNOWN_PARAMNAME:ActiveInterface:Wired Last Protocol Event Sent: Last Protocol Event Received:Rcvd:SIP/2.0 200 OK Cseq:103 REGISTER CallId:c58eed8d-30450002-00005e26-00001f68@10.2.25.237 App ID:Cisco CallManager Cluster ID:HeritageCluster Node ID:uc-cmucm2-s1
Line 65194: 66445711.008 |18:13:56.869 |AlarmErr |AlarmClass: Phone, AlarmName: LastOutOfServiceInformation, AlarmSeverity: Error, AlarmMessage: , AlarmDescription: Information related to the last out-of-service event , AlarmParameters: DeviceName:CSFu0024173, DeviceIPv4Address:10.2.25.237 / 0, IPv4DefaultGateway:192.168.0.1, DeviceIPv6Address:, IPv6DefaultGateway:, ModelNumber:CSF, NeighborIPv4Address:, NeighborIPv6Address:, NeighborDeviceID:, NeighborPortID:, DHCPv4Status:1, DHCPv6Status:3, TFTPCfgStatus:1, DNSStatusUnifiedCM1:1, DNSStatusUnifiedCM2:1, DNSStatusUnifiedCM3:3, VoiceVLAN:0, UnifiedCMIPAddress:uc-cmucm2-s1.hbs.net.au, LocalPort:4294967295, TimeStamp:1678349635, ReasonForOutOfService:14, UNKNOWN_PARAMNAME:ReasonForOutOfServiceText:cm-closed-tcp, UNKNOWN_PARAMNAME:ActiveInterface:Wired, LastProtocolEventSent:, LastProtocolEventReceived:Rcvd:SIP/2.0 200 OK Cseq:103 REGISTER CallId:c58eed8d-30450002-00005e26-00001f68@10.2.25.237 , AppID:Cisco CallManager, ClusterID:HeritageCluster, NodeID:uc-cmucm2-s1,
Line 65207: Contact: <sip:4220e743-eb6f-6643-7a6f-acc0b2cb1fd1@10.2.25.237:55559;transport=tcp>;+u.sip!devicename.ccm.cisco.com="CSFu0024173"

1 Reply 1

Andrew Skelly
Level 7
Level 7

Have you checked with your ISE team (or whomever supports authentication within your network)?  If you know the switch and port number that the physical phone is connecting to you can run a "show auth session" command with the port number to see if it is authenticating on the network.  That would be my first starting point.

Please rate helpful posts by clicking the thumbs up!