Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

Third party SIP devices register - unregister on the Call Manager

I have an issue with a numbers of wireless DECT phones connected to a Call Manager System version: The phones are created as third party (basic) devices.

The DECT phones are connected to a POLYCOM/KIRK KWS 8000 wireless server and the phones are also created here. The SIP status in the GUI indicates 200 => OK. The DECT phones connect to DECT bases around the premises. I have gone carefully through the setup on both the Kirk Wireless Server and Cisco Call Manager.

Unfortunatley I experience that the DECT phones registered on the Call Manager keeps unregistrering in a random pattern which properly started when changing from a 1500 server to a KWS8000 Some phones stays registered for several minutes and then un-register others bounce back and forth between register and unregister state. I assume that when the phones are able to regisiter in the first place the authentification is ok otherwise the DECT phone would never be able register in the first place but would be rejected.

However, the Call Manager trace indicates the following:

| AlarmClass: CallManager, AlarmName: DeviceUnregistered, AlarmSeverity: Error AlarmMessage: , AlarmDescription: Device unregistered., AlarmParameters: DeviceName:SEP000770983031, IPAddress:, Protocol:SIP, DeviceType:336, Description:DECT3065, Reason:10, AppID:Cisco CallManager, ClusterID:CM1-Cluster, NodeID:CUCM1,

392664521| 2013/08/08 12:32:00.762| 001| SdlSig   | DeviceLineUnregister                 | restart0                     | LineControl(1,100,148,7248803) | SIPStationD(1,100,75,2020698)   | (1,100,185,1).6015626-(SEPD877F2417635:| [R:NP - HP: 0, NP: 0, LP: 2, VLP: 0, LZP: 0 DBP: 0]

392664522| 2013/08/08 12:32:00.762| 001| SdlSig   | DeviceUnregistered                   | restart0                     | LineControl(1,100,148,7248803) | LineControl(1,100,148,7248803) | (1,100,185,1).6015626-(SEPD877F2417635:| [R:NP - HP: 0, NP: 0, LP: 2, VLP: 0, LZP: 0 DBP: 0]PID=(1, DeviceName=SEP000770983031

392664523| 2013/08/08 12:32:00.762| 001| Stopping |                                       |                               | LineControl(1,100,148,7248803) | LineControl(1,100,148,7248803) |                                         | NumOfCurrentInstances: 259

392664524| 2013/08/08 12:32:00.762| 001| SdlSig   | LineUnregisterInd                     | wait                         |

I see a whole lot of these data in the log and If I am not mistaken the reason code 10 is DeviceUnregistered - The device has explicitly unregistered. Possible causes include a change in the IP address or port of the device. No action is necessary; the device will re-register automatically.

But the problem is that the unregistration happens again and again and makes the DECT phones useless.

In the  DECT phone handset logs I cannot see any errors (although I am not very familiar with the Polycom/Kirk Handsets). The log is attached in this message.

Any ideas how I can proceed in trouble shooting this issue? 


Hey !!!  I have same Issue !!

Hey !!!



I have same Issue !!!

New Member



I need your help in understanding on how to integrate the Polycom Kirk wireless 6000 server with Cisco call manager.

Can you provide me the integration document and is the server compatible  with CUCM version 11.



Hello SathyaI have this

Hello Sathya

I have this document attached in the post; It is for a CUCM 8 version and not for CUCM 11, the baseline could differ a bit but this document may bring you a good step further.

BR Brian

New Member

Thanks Brian

Thanks Brian

Hey HassanIn the end we did

Hey Hassan

In the end we did conclude that it was the Call Manager version that did not support DECT phones/KWS8000. We did upgrade the Call Manager and the unregister the issue was solved. 


CreatePlease to create content