I would check the console

rpazosvargas · ‎12-13-2008

hi,

I have an 1760 SRST and 7902 Ip phone, they are register/unregister continuosly!

Does anyone know what is happening?

This is code that is showing:

Dec 14 01:49:43: %IPPHONE-6-UNREGISTER_ABNORMAL: ephone-7:SEP000D28AF15C6 IP:10.60.0.10 Socket:2 DeviceType:Phone has unregistered abnormally.

Dec 14 07:49:43: CLOSED Skinny socket 2 for de-registered phone

Dec 13 17:41:52: %IPPHONE-6-REG_ALARM: Name=SEP000D28AF15C6 Load=CP79020101SCCP030610A.zup Last=Initialized

Dec 13 17:41:52: %IPPHONE-6-REGISTER_NEW: ephone-7:SEP000D28AF15C6 IP:10.60.0.10 Socket:2 DeviceType:Phone has registered.

Dec 13 17:42:33: %IPPHONE-6-REG_ALARM: Name=SEP0016C8D52EB6 Load=CP79020101SCCP030610A.zup Last=CM-aborted-TCP

Dec 13 17:42:33: %IPPHONE-6-REGISTER_NEW: ephone-6:SEP0016C8D52EB6 IP:10.60.0.14 Socket:3 DeviceType:Phone has registered.

Dec 13 17:42:43: %IPPHONE-6-REG_ALARM: Name=SEP0011BB248B80 Load=CP79020101SCCP030610A.zup Last=CM-aborted-TCP

Dec 13 17:42:43: %IPPHONE-6-REGISTER_NEW: ephone-4:SEP0011BB248B80 IP:10.60.0.7 Socket:4 DeviceType:Phone has registered.

Dec 13 17:43:48: %IPPHONE-6-UNREGISTER_ABNORMAL: ephone-2:SEP000D28AF15D0 IP:10.60.0.13 Socket:1 DeviceType:Phone has unregistered abnormally.

Dec 13 17:43:48: %IPPHONE-6-UNREGISTER_ABNORMAL: ephone-5:SEP000D28AF164D IP:10.60.0.12 Socket:5 DeviceType:Phone has unregistered abnormally.

Dec 13 17:44:19: %IPPHONE-6-REG_ALARM: Name=SEP000D28AF16F9 Load=CP79020101SCCP030610A.zup Last=CM-aborted-TCP

Dec 13 17:44:19: %IPPHONE-6-REGISTER_NEW: ephone-3:SEP000D28AF16F9 IP:10.60.0.5 Socket:1 DeviceType:Phone has registered.

Dec 13 17:44:24: %IPPHONE-6-REG_ALARM: Name=SEP000D28AF164D Load=CP79020101SCCP030610A.zup Last=Initialized

Dec 13 17:44:25: %IPPHONE-6-REGISTER_NEW: ephone-5:SEP000D28AF164D IP:10.60.0.12 Socket:5 DeviceType:Phone has registered.

Dec 13 17:44:35: %IPPHONE-6-UNREGISTER_ABNORMAL: ephone-6:SEP0016C8D52EB6 IP:10.60.0.14 Socket:3 DeviceType:Phone has unregistered abnormally.

Dec 13 17:45:23: %IPPHONE-6-UNREGISTER_ABNORMAL: ephone-7:SEP000D28AF15C6 IP:10.60.0.10 Socket:2 DeviceType:Phone has unregistered abnormally.

Dec 13 17:45:36: %IPPHONE-6-REG_ALARM: Name=SEP000D28AF15C6 Load=CP79020101SCCP030610A.zup Last=Initialized

Dec 13 17:45:36: %IPPHONE-6-REGISTER_NEW: ephone-7:SEP000D28AF15C6 IP:10.60.0.10 Socket:2 DeviceType:Phone has registered.

Dec 13 17:47:14: %IPPHONE-6-UNREGISTER_ABNORMAL: ephone-4:SEP0011BB248B80 IP:10.60.0.7 Socket:4 DeviceType:Phone has unregistered abnormally.

Dec 13 17:47:50: %IPPHONE-6-UNREGISTER_ABNORMAL: ephone-3:SEP000D28AF16F9 IP:10.60.0.5 Socket:1 DeviceType:Phone has unregistered abnormally.

Dec 13 17:48:07: %IPPHONE-6-UNREGISTER_ABNORMAL: ephone-7:SEP000D28AF15C6 IP:10.60.0.10 Socket:2 DeviceType:Phone has unregistered abnormally.

Dec 13 17:48:43: %IPPHONE-6-REG_ALARM: Name=SEP000D28AF16F5 Load=CP79020101SCCP030610A.zup Last=CM-aborted-TCP

Dec 13 17:48:43: %IPPHONE-6-REGISTER_NEW: ephone-1:SEP000D28AF16F5 IP:10.60.0.3 Socket:1 DeviceType:Phone has registered.

Dec 13 17:49:25: %IPPHONE-6-REG_ALARM: Name=SEP0011BB248B80 Load=CP79020101SCCP030610A.zup Last=CM-aborted-TCP

Dec 13 17:49:26: %IPPHONE-6-REGISTER_NEW: ephone-4:SEP0011BB248B80 IP:10.60.0.7 Socket:2 DeviceType:Phone has registered.

Dec 13 17:51:57: %IPPHONE-6-UNREGISTER_ABNORMAL: ephone-4:SEP0011BB248B80 IP:10.60.0.7 Socket:2 DeviceType:Phone has unregistered abnormally.

Thanks for your help

Rolando

Nicholas Matthews · ‎12-14-2008

The CM-Aborted-TCP cause shows that CME stopped receiving keepalives from the phone. This can be caused by a few things:

-High CPU on the router, and it does not respond correctly

-Phone has issues sending keepalives/registering (bug)

-Network layer connectivity

I would start by checking the 'show proc cpu hist' to make sure you're not running high CPU. Then, update the 7902 phones to the latest firmware possible. I found CSCec21459 which can explain some odd 7902 TCP timeout problems, but it's a pretty old bug and hopefully your firmware isn't that old.

If these phones are over the WAN, try putting a few of them on the LAN, and enable QoS for TCP port 2000 on both WAN routers.

If your CPU is fine, and your phones are on the latest firmware, get a packet capture. You'll need to see who's not responding correctly.

Stephen Keller · ‎01-29-2009

I am experiencing the same problem. Phones are losing keepalives and unregister from UC manager. i am curious if you were able to resolve this issue. clearly phones are unregister from the servers and registering to the router only to start recieving keepalives again and then registering back to the server. right now i am looking at the switchport configs - i am curious if you made a solution.

Nicholas Matthews · ‎01-29-2009

This was pretty rampant in 12.4(11)XW2-through XW5 or so. There was a UC520 high CPU bug causing it - I'd check there first.

Check your 'show proc cpu hist' to make sure your CPU isn't spiking.

3 main causes:

-network failure

-high cpu

-bug

1) Can't tell you, you'll need to inspect your devices

2) 'show proc cpu hist'

3) Upgrade to 12.4(22)T and see if it helps

hth,

nick

divine007 · ‎10-30-2013

Hello All,

have th thesame issue am using a 2811, Version 12.4(13r)T

Oct 30 09:32:47.969: %IPPHONE-6-UNREGISTER_ABNORMAL: ephone-31:SEP0022FB7351DA IP:192.168.40.136 Socket:1 DeviceType:Phone has unregistered abnormally.

Oct 30 09:33:40.969: %IPPHONE-6-UNREGISTER_ABNORMAL: ephone-9:SEP64A0E7F6896B IP:172.17.136.18 Socket:16 DeviceType:Phone has unregistered abnormally.

Oct 30 09:35:36.264: %IPPHONE-6-REGISTER: ephone-9:SEP64A0E7F6896B IP:172.17.136.18 Socket:1 DeviceType:Phone has registered.

Oct 30 09:37:20.968: %IPPHONE-6-UNREGISTER_ABNORMAL: ephone-9:SEP64A0E7F6896B IP:172.17.136.18 Socket:1 DeviceType:Phone has unregistered abnormally.

Oct 30 09:37:50.251: %IPPHONE-6-REG_ALARM: 10: Name=SEP64A0E7F6896B Load= SCCP42.8-4-2S Last=TCP-timeout

Oct 30 09:37:50.251: %IPPHONE-6-REGISTER: ephone-9:SEP64A0E7F6896B IP:172.17.136.18 Socket:9 DeviceType:Phone has registered.

Some ephones are working well,but for this one

JustinDike · ‎08-19-2014

Hello,

I'm having the same problems on a UC520 (version 12.4 (11r)XW3)

I'm planning on doing the upgrade as soon as possible (device is currently unsupported), but could there be anything else causing these issues that I could look into in the meantime?

We have ~50 phones, but only 14 seem to be throwing this error. Log is as of this morning, and the highest CPU spike over the last 24 hours was shown to be around 50%.

30084857: Aug 19 03:02:19.670: %IPPHONE-6-REG_ALARM: Name=SEP00211BFC9D7E Load=8.1.17 Last=Halt+7372016c

30084858: Aug 19 03:02:19.878: %IPPHONE-6-UNREGISTER_ABNORMAL: ephone-26:SEP00211BFC9D7E IP:10.1.1.28 Socket:40 DeviceType:Phone has unregistered abnormally.

30084859: Aug 19 03:02:19.878: %IPPHONE-6-REGISTER: ephone-26:SEP00211BFC9D7E IP:10.1.1.28 Socket:42 DeviceType:Phone has registered.

30084860: Aug 19 03:04:07.233: %IPPHONE-6-REG_ALARM: Name=SEP00211BFC86C1 Load=8.1.17 Last=Halt+7372016c

30084861: Aug 19 03:04:07.441: %IPPHONE-6-UNREGISTER_ABNORMAL: ephone-20:SEP00211BFC86C1 IP:10.1.1.26 Socket:41 DeviceType:Phone has unregistered abnormally.

30084862: Aug 19 03:04:07.441: %IPPHONE-6-REGISTER: ephone-20:SEP00211BFC86C1 IP:10.1.1.26 Socket:40 DeviceType:Phone has registered.

30084863: Aug 19 03:05:59.602: %IPPHONE-6-REG_ALARM: Name=SEP00211BFC8750 Load=8.1.17 Last=Halt+7372016c

30084864: Aug 19 03:05:59.806: %IPPHONE-6-UNREGISTER_ABNORMAL: ephone-16:SEP00211BFC8750 IP:10.1.1.32 Socket:39 DeviceType:Phone has unregistered abnormally.

Thanks for any help you can provide!

Brian Meade · ‎08-19-2014

What is the CPU/memory utilization when this happens? What's the network topology between the phones and CME?

JustinDike · ‎08-19-2014

The phones un-registered/re-registered within the last hour, and CPU usage doesn't show to be any higher than 30%.

Topology is ipv4. Six interfaces setup for switchport voice vlan100 for VoIP phones. The issue seems to be only limited to the last interface (FastEthernet0/1/7) as it switches from up to down and back to up within a few seconds, but this doesn't occur during the same time as the phone errors. Happens hours before or after.

Brian Meade · ‎08-20-2014

I would check the console logs on the phone's webpage when this happens. Might be worth setting up a packet capture as well. It sounds more like a network issue then a CPU/mem issue on CME.

IPPHONE UNREGISTER_ABNORMAL