cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Bookmark
|
Subscribe
|
4706
Views
15
Helpful
6
Replies

SIP Third-Party phone - SNOM

edguidry
Level 1
Level 1

Hello, purchased a SNOM for demo purposes.  Attempting to integrate with CUCM 10.5.  Has anyone worked with this before?  Meanwhile, I will search on the SNON wiki.

Thanks,
Eddie

2 Accepted Solutions

Accepted Solutions

Anoop Krishnan
Level 1
Level 1

I had configuring Avaya phones with Cisco CUCM , but i guess the process is same for all Non-Cisco SIP phones, please go through the following guide, it might help you to configure

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/9_0_1/ccmcfg/CUCM_BK_CDF59AFB_00_admin-guide-90/CUCM_BK_CDF59AFB_00_admin-guide_appendix_01100111.pdf

Regards, 

Anoop

View solution in original post

Hi,

The snippet you mentioned means that the request is coming to a CUCM server that is not a part of call manager group "02-05-03-cmg". 

Can you possibly do one thing?

Go to System >> Server in CCMWebadmin webpage.

Click on each server and check the pkid value in the address bar of the browser and you shall see the pkid "7c543a0b-d736-45b6-8438-3b977022957b" for one of the CUCM server.

Make a new CMgroup that has just this server and assign it to the SIP device you are trying to register and see if it registers fine.

Please rate and mark correct if helpful.

Regards,

Hitesh

View solution in original post

6 Replies 6

edguidry
Level 1
Level 1

The model is M325.  Cordless with base station.

Hello.   attached is the trace from the CallManager.  The IP for SIP phone base is 10.20.10.130.    Call Manager pub is 10.110.10.11.   I rebooted the base at 6:52 CST and kicked off a SIP registration at 6:53 CST.  I would appreciate anyone who reviews the trace.  This part of trace is interesting:

63453501.007 |06:53:12.958 |AppInfo  |SIPStationD(19) - setDefaultOptions: INFO - user agent 5
63453501.008 |06:53:12.958 |AppInfo  |SIPStationD(19) - Convert UserId "2750" to deviceName
63453501.009 |06:53:12.958 |AppInfo  |SIPStationD(19) - deviceType=336, mSIPAuthorizationHeaderPtr->user_pass=2750
63453501.010 |06:53:13.165 |AppInfo  |Device=SEP000413621763 in DB already but cannot register. isDeviceNameAllowedToRegister=CallManager Pkid(7c543a0b-d736-45b6-8438-3b977022957b) is not a member of Call Manager Group(02-05-03-cmg) (isCallManagerMemberOfDevicePool)
63453501.011 |06:53:13.165 |AppInfo  |CcmdbStationRegistrationProfileBuilder::getBasicRegistrationProfile::init() - failed rc(2)
63453501.012 |06:53:13.165 |AppInfo  |SIPStationD(19) - sendRegisterResp: non-200 response code 500, ccbId 2730719, expires 4294967295, warning Device Config Issue
63453501.013 |06:53:13.165 |AppInfo  |SIPStationD(19) - DevStat-StopClose: Device Config Issue

Hi,

The snippet you mentioned means that the request is coming to a CUCM server that is not a part of call manager group "02-05-03-cmg". 

Can you possibly do one thing?

Go to System >> Server in CCMWebadmin webpage.

Click on each server and check the pkid value in the address bar of the browser and you shall see the pkid "7c543a0b-d736-45b6-8438-3b977022957b" for one of the CUCM server.

Make a new CMgroup that has just this server and assign it to the SIP device you are trying to register and see if it registers fine.

Please rate and mark correct if helpful.

Regards,

Hitesh

Hitesh.  Thanks!  I found that I was using the Pub for SIP registration and in this cluster the Pub does not do call control.  I pointed to a Sub and all is good.  Thanks to you and Anoop for your input.

Eddie

Anoop Krishnan
Level 1
Level 1

I had configuring Avaya phones with Cisco CUCM , but i guess the process is same for all Non-Cisco SIP phones, please go through the following guide, it might help you to configure

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/9_0_1/ccmcfg/CUCM_BK_CDF59AFB_00_admin-guide-90/CUCM_BK_CDF59AFB_00_admin-guide_appendix_01100111.pdf

Regards, 

Anoop

Thanks for the info.  Cleared up some things.  I am struggling now with the SIP registration.  I have done what your document outlines but the SIP registration is failing.  Attached is the SIP log from the phone.