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

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.

New Member

Third Party SIP Phone registration

I have a Polycom Soundstation IP 6000 that I'm trying to register to our CUCM 8.x server.  Registration keeps getting rejected and I can't figure out what's going on.  I've configured a digest user and associated the name on the phone configuration page.  When looking at the trace files, I see the phone trying to register but I don't see any rejection error messages being sent by CUCM.  I'm sure this is something simple that I am missing.  Below is the output from my trace.

REGISTER sip:172.16.95.245:5060 SIP/2.0

Via: SIP/2.0/UDP 172.16.101.255;branch=z9hG4bK3cbd66316433E898

From: "299" <sip:172.16.95.245@172.16.95.245>;tag=E4C1F90F-33B89DFE

To: <sip:172.16.95.245@172.16.95.245>

CSeq: 2 REGISTER

Call-ID: 46867d3a-a986247d-72be99b4@172.16.101.255

Contact: <sip:172.16.95.245@172.16.101.255>;methods="INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER"

User-Agent: PolycomSoundStationIP-SPIP_6000-UA/3.0.4.0061

Authorization: Digest username="polycom1", realm="ccmsipline", nonce="VseOAqA6w4Hx97MRe2laVKlB28JbATjj", uri="sip:172.16.95.245:5060", response="4d8ba00249e1786c05222a81afb46bef", algorithm=MD5

Max-Forwards: 70

Expires: 3600

Content-Length: 0

|1,100,213,1.181^172.16.101.255^*

09:19:01.701 |//SIP/Stack/Info/0x0/ccsip_spi_get_msg_type returned: 2 for event 1|1,100,213,1.181^172.16.101.255^*

09:19:01.701 |//SIP/Stack/Transport/0x0/context=(nil)|1,100,213,1.181^172.16.101.255^*

09:19:01.701 |//SIP/Stack/Info/0x0/Checking Invite Dialog|1,100,213,1.181^172.16.101.255^*

09:19:01.701 |//SIP/Stack/Info/0xb45537c0/*****CCB found in UAS Request table. ccb=0xb45537c0|1,100,213,1.181^172.16.101.255^*

09:19:01.701 |//SIP/Stack/Transport/0x0/Subsq Transaction Address 172.16.101.255,Port 5060, Transport 1, SentBy Port 5060|1,100,213,1.181^172.16.101.255^*

09:19:01.701 |//SIP/Stack/Transport/0x0/Subsq Transaction Address 172.16.101.255,Port 5060, Transport 1, SentBy Port 5060|1,100,213,1.181^172.16.101.255^*

09:19:01.701 |//SIP/Stack/Transport/0xb45537c0/Sending INFO Response to the transport layer|1,100,213,1.181^172.16.101.255^*

09:19:01.701 |//SIP/Stack/Transport/0xb45537c0/msg=0xb4589540, addr=172.16.101.255, port=5060, sentBy_port=5060, is_req=0, transport=1, switch=0, callBack=(nil)|1,100,213,1.181^172.16.101.255^*

09:19:01.701 |//SIP/Stack/Transport/0xb45537c0/Proceedable for sending msg immediately|1,100,213,1.181^172.16.101.255^*

09:19:01.701 |//SIP/Stack/Transport/0xb45537c0/switch transport is 0|1,100,213,1.181^172.16.101.255^*

09:19:01.701 |//SIP/Stack/Transport/0x0/Posting send for msg=0xb4589540, addr=172.16.101.255, port=5060, connId=0 for UDP|1,100,213,1.181^172.16.101.255^*

09:19:01.701 |//SIP/SIPHandler/ccbId=0/scbId=0/sip_stop_timer: type=SIP_TIMER_REMOVE_TRANSACTION value=32000 retries=0|1,100,213,1.181^172.16.101.255^*

09:19:01.701 |//SIP/SIPHandler/ccbId=0/scbId=0/findTrunkInfoByAddr: Cannot find the SIP Trunk with Name=172.16.101.255, Source Port=5060, IpAddress Type=0|1,100,213,1.181^172.16.101.255^*

09:19:01.701 |//SIP/SIPHandler/ccbId=91/scbId=0/findDevicePID: Routed to SIPStationInit|1,100,213,1.181^172.16.101.255^*

09:19:01.701 |//SIP/Stack/Event/0xb45537c0/

ccsip_api_register_ind return value : SIP_SUCCESS

|1,100,213,1.181^172.16.101.255^*

09:19:01.701 |//SIP/Stack/States/0xb45537c0/0xb45537c0 : State change from (STATE_IDLE, SUBSTATE_NONE) to (SIP_STATE_INCOMING_REGISTER, SUBSTATE_NONE)|1,100,213,1.181^172.16.101.255^*

09:19:01.702 |CcmCcmdbHelper::getProcessConfigGivenProcessnodeParamnameService - Value of DeviceMobilityMode from process config table is (0)|*^*^*

09:19:01.702 |CcmCcmdbHelper::getProcessConfigGivenProcessnodeParamnameService - Value of DeviceMobilityMode from process config table is (0)|*^*^*

09:19:01.707 |GetMaxCallForDevice: cannot find entry in ProductSupportsFeature table for product 273 and protocol 11feature SUPPORTS_FEATURE_RESTRICT_MAX_CALLS|*^*^*

09:19:01.707 |GetMaxCallForDevice: cannot find entry in ProductSupportsFeature table for product 273 and protocol 99feature SUPPORTS_FEATURE_RESTRICT_MAX_CALLS|*^*^*

09:19:01.707 | SIPSecurity::decrypt hex password = "eca7d4ee66e70bdaac7d849fda77f0756de140425fc368b8fca0d4cf398c492e" , ecnrypted len 32 |*^*^*

09:19:01.707 |getMaxAuthnameLenFromModel: cannot find entry in ProductSupportsFeature table for model 374 and protocol 11 feature SUPPORTS_FEATURE_MAXIMUM_AUTHNAME_LENGTH|*^*^*

09:19:01.707 |getMaxAuthnameLenFromModel: cannot find entry in ProductSupportsFeature table for model 374 and protocol 99 feature SUPPORTS_FEATURE_MAXIMUM_AUTHNAME_LENGTH|*^*^*

09:19:01.707 |SIPSecurity::verifyAuthResponse: cred.username=polycom1, cred.password=456, auth_hdr.realm=ccmsipline, aut_hdr.nonce=VseOAqA6w4Hx97MRe2laVKlB28JbATjj|*^*^*

09:19:01.707 |getMaxAuthnameLenFromModel: cannot find entry in ProductSupportsFeature table for model 374 and protocol 11 feature SUPPORTS_FEATURE_MAXIMUM_AUTHNAME_LENGTH|*^*^*

09:19:01.707 |getMaxAuthnameLenFromModel: cannot find entry in ProductSupportsFeature table for model 374 and protocol 99 feature SUPPORTS_FEATURE_MAXIMUM_AUTHNAME_LENGTH|*^*^*

09:19:01.707 |getMaxCallForDeviceFromModel: ProductSupportsFeature table entry for model 374 and feature SUPPORTS_FEATURE_MULTIPLE_CALL_DISPLAY has deviceprotocol = 11 maxcalls = 16|*^*^*

09:19:01.707 |<MN::Directory Number><MV::299>|1,100,213,1.181^*^*

09:19:01.707 |EndPointTransientConnection - An endpoint attempted to register but did not complete registration Connecting Port:5060 Device name:SEP0004F2E446B1 Device IP address:172.16.101.255 Protocol:SIP Device type:374 Reason Code:7 Registering SIP User:172.16.95.245 App ID:Cisco CallManager Cluster ID:StandAloneCluster Node ID:MaplesCCMPUB|AlarmSEP0004F2E446B1^*^SEP0004F2E446B1

09:19:01.708 |//SIP/Stack/Info/0x0/ccsip_spi_get_msg_type returned: 3 for event 42|1,100,213,1.181^172.16.101.255^*

09:19:01.708 |//SIP/Stack/Info/0xb45537c0/Response Container Holder is above threshold...trimming|1,100,213,1.181^172.16.101.255^*

09:19:01.708 |//SIP/Stack/Info/0xb45537c0/Associated container=0xb3c177f0 to REGISTER Response 404|1,100,213,1.181^172.16.101.255^*

09:19:01.708 |//SIP/Stack/Transport/0xb45537c0/Sending INFO Response to the transport layer|1,100,213,1.181^172.16.101.255^*

09:19:01.708 |//SIP/Stack/Transport/0xb45537c0/msg=0xb4589540, addr=172.16.101.255, port=5060, sentBy_port=5060, is_req=0, transport=1, switch=0, callBack=0xa106e72|1,100,213,1.181^172.16.101.255^*

09:19:01.708 |//SIP/Stack/Transport/0xb45537c0/Proceedable for sending msg immediately|1,100,213,1.181^172.16.101.255^*

09:19:01.708 |//SIP/Stack/Transport/0xb45537c0/switch transport is 0|1,100,213,1.181^172.16.101.255^*

09:19:01.708 |//SIP/Stack/Transport/0x0/Posting send for msg=0xb4589540, addr=172.16.101.255, port=5060, connId=0 for UDP|1,100,213,1.181^172.16.101.255^*

09:19:01.708 |//SIP/SIPHandler/ccbId=0/scbId=0/sip_stop_timer: type=SIP_TIMER_REMOVE_TRANSACTION value=32000 retries=0|1,100,213,1.181^172.16.101.255^*

09:19:01.708 |//SIP/SIPHandler/ccbId=0/scbId=0/sip_start_timer: type=SIP_TIMER_REMOVE_TRANSACTION value=32000 retries=0|1,100,213,1.181^172.16.101.255^*

09:19:01.708 |//SIP/Stack/States/0xb45537c0/0xb45537c0 : State change from (SIP_STATE_INCOMING_REGISTER, SUBSTATE_NONE) to (STATE_IDLE, SUBSTATE_NONE)|1,100,213,1.181^172.16.101.255^*

09:19:10.163 |Cnf Received: processnodeservice U 66c9cf09-914e-4025-a2fc-73a554b50db5, size(1198) tracelevel(1/127) usercategories(1309183/393216) |0,0,0,0.0^*^*

09:19:10.169 |ProcessCnf N: processnodeservice U 66c9cf09-914e-4025-a2fc-73a554b50db5, size(1198) tracelevel(1/127) usercategories(1309183/393216) |0,0,0,0.0^*^*

09:19:10.169 |doGroupReset: checking for group reset on table processnodeservice|0,0,0,0.0^*^*

09:19:10.169 |DbChangeNotify::SendDbChangeProcessConfig|0,0,0,0.0^*^*

09:19:12.377 |dBProcs - setPkidOfClusterId() starts|*^*^*

09:19:12.377 |setClusterPkId to 195a3d67-4470-4f89-a1b9-b4c159043416|*^*^*

09:19:12.377 |dBProcs::configSdlLinks()|*^*^*

09:19:12.377 |configCHAC: 172.16.95.246 already in CHAC|*^*^*

09:19:12.377 |configCHAC: 172.16.95.245 already in CHAC|*^*^*

09:19:33.723 |//SIP/SIPHandler/ccbId=0/scbId=0/wait_SIPTimer: TimerExpired type=SIP_TIMER_REMOVE_TRANSACTION value=32000 retries=0|1,100,213,1.181^172.16.101.255^*

09:19:33.723 |//SIP/Stack/Info/0xb45537c0/Removing call id 5b|1,100,213,1.181^172.16.101.255^*

09:19:33.723 |//SIP/Stack/Info/0x0/Context for key=[90] removed.|1,100,213,1.181^172.16.101.255^*

09:19:33.723 |//SIP/SIPHandler/ccbId=0/scbId=0/sip_stop_timer: type=SIP_TIMER_REMOVE_TRANSACTION value=32000 retries=0|1,100,213,1.181^172.16.101.255^*

09:19:33.723 |//SIP/Stack/Info/0xb45537c0/****Deleting from UAS Request table.|1,100,213,1.181^172.16.101.255^*

09:19:33.723 |//SIP/Stack/Info/0xb45537c0/Deleting from table. ccb=0xb45537c0 key=46867d3a-a986247d-72be99b4@172.16.101.255172.16.95.245E4C1F90F-33B89DFE|1,100,213,1.181^172.16.101.255^*

09:19:33.723 |//SIP/Stack/Info/0xb45537c0/****Deleting from UAS Response table.|1,100,213,1.181^172.16.101.255^*

09:19:33.723 |//SIP/Stack/Info/0xb45537c0/There are 0 events on the internal queue that are going to be free'd|1,100,213,1.181^172.16.101.255^*

09:19:33.723 |//SIP/Stack/Info/0xb45537c0/Freeing ccb b45537c0|1,100,213,1.181^172.16.101.255^*

09:19:43.064 |//SIP/SIPUdp/wait_UdpDataInd: Incoming SIP UDP message size 541 from 172.16.101.255:[5060]:

REGISTER sip:172.16.95.245:5060 SIP/2.0

Via: SIP/2.0/UDP 172.16.101.255;branch=z9hG4bKcfabcc022044C025

From: "299" <sip:172.16.95.245@172.16.95.245>;tag=1600C659-F826B020

To: <sip:172.16.95.245@172.16.95.245>

CSeq: 1 REGISTER

Call-ID: b83f2ebc-7e3301f7-dc152b46@172.16.101.255

Contact: <sip:172.16.95.245@172.16.101.255>;methods="INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER"

User-Agent: PolycomSoundStationIP-SPIP_6000-UA/3.0.4.0061

Max-Forwards: 70

Expires: 3600

Content-Length: 0

3 REPLIES
New Member

Re: Third Party SIP Phone registration

Hello Charles,

Please find attached a PDF document which provides you steps to configure a 3rd party SIP phone. Could you please verify the configuration to make sure everything is correct. Many a time, it is a simple configuration issue.

If it still fails, please collect detailed CM sdi/sdl traces, while enabling 'SIP stack trace' and 'SIP call processing trace' on the trace configuration page.

Cheers,

Vajrender

Third Party SIP Phone registration

HI Vajrender;

I want to thank you because you solved my problem ........

New Member

Re: Third Party SIP Phone registration

Hi Charles,

Did you get this to work? i am having same issue.

Thanks

Mohammed

4173
Views
5
Helpful
3
Replies
CreatePlease to create content