Plantronics + Polycom. Now together as Poly Logo

Polycom Trio 8800 - Dialing issues with CUCM

adivac730
Occasional Visitor

Polycom Trio 8800 - Dialing issues with CUCM

OK I got a RealPresence Trio 8800 that is registered to my Cisco Call Manager 10.5.2

 

I can dial our internal 5 digit extensions, but when someone answers the phone gets a busy tone.

 

I also have busy tones when trying to dial outside calls.  Not sure what type of info I need to give to help out with this.

 

 

Message 1 of 8
7 REPLIES 7
SteffenBaierUK
Polycom Employee & Community Manager

Re: Polycom Trio 8800 - Dialing issues with CUCM

Hello adivac730,

welcome to the Polycom Community.

It is always useful to include the currently used UC Software version as issues experienced or a question asked may already be addressed in a newer release.

This also allows yourself and others to check against current software release notes, Administrator Guides or FAQ post’s.

The above is also stated in the "Read First"

Therefore the Polycom VoIP FAQ contains this post here:

Question: How can I find out my SIP or UC Software Version of my Phone?
Resolution: Please check here

 

Please utilize below FAQ to troubleshoot your issue:

 

Jan 19, 2012 Question: How to troubleshoot Polycom VoIP related Issues?

Resolution: Please check => here <=


Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.

Best Regards

Steffen Baier

Polycom Global Services

----------------
The title Poly Employee & Community Manager is a community setting and does not reflect my role. I am just a simple volunteer in the community like everybody else. All posts and words are my own & do not represent the views of Employer.

----------------

Notice: This community forum is not an official Poly support resource, thus responses from Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge. If you need immediate and/or official assistance please open a service ticket through your proper support channels.
Please also ensure you always check the VoIP , Video Endpoint , Skype for Business , PSTN or RPM FAQ's
Message 2 of 8
adivac730
Occasional Visitor

Re: Polycom Trio 8800 - Dialing issues with CUCM

I have looked thru the docs you provided.  The phone has registered fine.  Just have very weird dialing issues.

 

UC Software Version 5.4.4.7776

Message 3 of 8
SteffenBaierUK
Polycom Employee & Community Manager

Re: Polycom Trio 8800 - Dialing issues with CUCM

Hello adivac730,

Following the previous outlined FAQ will enable you to log the issue. You can then share the logs with us.

 

  • Settings > Logging > Global Log Level Limit > Debug
  • Settings > Logging > Log File Size (Kbytes) > 512
  • Settings > Logging > Module Log Level Limits > SIP > Debug

If you are unable to do this then you need to open a support ticket.

In order to raise a support ticket you need to work with your Polycom reseller as they need to do this for you.

If this is some sort of an Internet discounter please post either your phone's MAC address or your Polycom devices serial so I can look up who would be able to support you.

Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.

Best Regards

Steffen Baier

Polycom Global Services

----------------
The title Poly Employee & Community Manager is a community setting and does not reflect my role. I am just a simple volunteer in the community like everybody else. All posts and words are my own & do not represent the views of Employer.

----------------

Notice: This community forum is not an official Poly support resource, thus responses from Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge. If you need immediate and/or official assistance please open a service ticket through your proper support channels.
Please also ensure you always check the VoIP , Video Endpoint , Skype for Business , PSTN or RPM FAQ's
Message 4 of 8
adivac730
Occasional Visitor

Re: Polycom Trio 8800 - Dialing issues with CUCM

0227135313|sip  |0|00|Trying to send data to Destination 172.31.8.12 on socket 197
0227135313|sip  |0|00|>>> Data Send to 172.31.8.12:5060
0227135313|sip  |0|00|    INVITE sip:22655@172.31.8.12:5060;user=phone SIP/2.0
0227135313|sip  |0|00|    Via: SIP/2.0/UDP 172.31.19.35;branch=z9hG4bK85e9e9c564109AC5
0227135313|sip  |0|00|    From: "22893" <sip:22893@172.31.8.12>;tag=E2F881A2-4BA4E548
0227135313|sip  |0|00|    To: <sip:22655@172.31.8.12;user=phone>
0227135313|sip  |0|00|    CSeq: 1 INVITE
0227135313|sip  |0|00|    Call-ID: 282b524e-418d205b-9bcf0469@172.31.19.35
0227135313|sip  |0|00|    Contact: <sip:22893@172.31.19.35>
0227135313|sip  |0|00|    Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER
0227135313|sip  |0|00|    User-Agent: PolycomRealPresenceTrio-Trio_8800-UA/5.4.4.7776
0227135313|sip  |0|00|    Accept-Language: en
0227135313|sip  |0|00|    Supported: replaces,100rel
0227135313|sip  |0|00|    Allow-Events: conference,talk,hold
0227135313|sip  |0|00|    Max-Forwards: 70
0227135313|sip  |0|00|    Content-Type: application/sdp
0227135313|sip  |0|00|    Content-Length: 472
0227135313|sip  |0|00|    
0227135313|sip  |0|00|    v=0
0227135313|sip  |0|00|    o=- 1488225193 1488225193 IN IP4 172.31.19.35
0227135313|sip  |0|00|    s=Polycom IP Phone
0227135313|sip  |0|00|    c=IN IP4 172.31.19.35
0227135313|sip  |0|00|    b=AS:2048
0227135313|sip  |0|00|    t=0 0
0227135313|sip  |0|00|    a=sendrecv
0227135313|sip  |0|00|    m=audio 2242 RTP/AVP 115 99 9 102 0 8 18 101
0227135313|sip  |0|00|    a=rtpmap:115 G7221/32000
0227135313|sip  |0|00|    a=fmtp:115 bitrate=48000
0227135313|sip  |0|00|    a=rtpmap:99 SIREN14/16000
0227135313|sip  |0|00|    a=fmtp:99 bitrate=48000
0227135313|sip  |0|00|    a=rtpmap:9 G722/8000
0227135313|sip  |0|00|    a=rtpmap:102 G7221/16000
0227135313|sip  |0|00|    a=fmtp:102 bitrate=32000
0227135313|sip  |0|00|    a=rtpmap:0 PCMU/8000
0227135313|sip  |0|00|    a=rtpmap:8 PCMA/8000
0227135313|sip  |0|00|    a=rtpmap:18 G729/8000
0227135313|sip  |0|00|    a=fmtp:18 annexb=no
0227135313|sip  |0|00|    a=rtpmap:101 telephone-event/8000
0227135313|sip  |0|00|<<< End of data send
0227135313|sip  |0|00|listener: Received packet from 172.31.8.12:5060
0227135313|sip  |0|00|listener: Received packet from 172.31.8.12:5060
0227135313|sip  |0|00|<<<Data Received UDP
0227135313|sip  |0|00|    SIP/2.0 100 Trying
0227135313|sip  |0|00|    Via: SIP/2.0/UDP 172.31.19.35;branch=z9hG4bK85e9e9c564109AC5
0227135313|sip  |0|00|    From: "22893" <sip:22893@172.31.8.12>;tag=E2F881A2-4BA4E548
0227135313|sip  |0|00|    To: <sip:22655@172.31.8.12;user=phone>
0227135313|sip  |0|00|    Date: Mon, 27 Feb 2017 19:53:14 GMT
0227135313|sip  |0|00|    Call-ID: 282b524e-418d205b-9bcf0469@172.31.19.35
0227135313|sip  |0|00|    CSeq: 1 INVITE
0227135313|sip  |0|00|    Allow-Events: presence
0227135313|sip  |0|00|    Content-Length: 0
0227135313|sip  |0|00|    
0227135313|sip  |0|00|<<<Data Received UDP
0227135313|sip  |0|00|    SIP/2.0 401 Unauthorized
0227135313|sip  |0|00|    Via: SIP/2.0/UDP 172.31.19.35;branch=z9hG4bK85e9e9c564109AC5
0227135313|sip  |0|00|    From: "22893" <sip:22893@172.31.8.12>;tag=E2F881A2-4BA4E548
0227135313|sip  |0|00|    To: <sip:22655@172.31.8.12;user=phone>;tag=1760240849
0227135313|sip  |0|00|    Date: Mon, 27 Feb 2017 19:53:14 GMT
0227135313|sip  |0|00|    Call-ID: 282b524e-418d205b-9bcf0469@172.31.19.35
0227135313|sip  |0|00|    CSeq: 1 INVITE
0227135313|sip  |0|00|    Allow-Events: presence
0227135313|sip  |0|00|    Server: Cisco-CUCM10.5
0227135313|sip  |0|00|    WWW-Authenticate: Digest realm="ccmsipline", nonce="6Z32wd++d8L/PHDr5iuYxp4pQEORMkrT", algorithm=MD5
0227135313|sip  |0|00|    Content-Length: 0
0227135313|sip  |0|00|    
0227135313|sip  |0|00|Trying to send data to Destination 172.31.8.12 on socket 197
0227135313|sip  |0|00|>>> Data Send to 172.31.8.12:5060
0227135313|sip  |0|00|    ACK sip:22655@172.31.8.12:5060;user=phone SIP/2.0
0227135313|sip  |0|00|    Via: SIP/2.0/UDP 172.31.19.35;branch=z9hG4bK85e9e9c564109AC5
0227135313|sip  |0|00|    From: "22893" <sip:22893@172.31.8.12>;tag=E2F881A2-4BA4E548
0227135313|sip  |0|00|    To: <sip:22655@172.31.8.12;user=phone>;tag=1760240849
0227135313|sip  |0|00|    CSeq: 1 ACK
0227135313|sip  |0|00|    Call-ID: 282b524e-418d205b-9bcf0469@172.31.19.35
0227135313|sip  |0|00|    Contact: <sip:22893@172.31.19.35>
0227135313|sip  |0|00|    Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER
0227135313|sip  |0|00|    User-Agent: PolycomRealPresenceTrio-Trio_8800-UA/5.4.4.7776
0227135313|sip  |0|00|    Accept-Language: en
0227135313|sip  |0|00|    Max-Forwards: 70
0227135313|sip  |0|00|    Content-Length: 0
0227135313|sip  |0|00|    
0227135313|sip  |0|00|<<< End of data send
0227135313|sip  |0|00|Trying to send data to Destination 172.31.8.12 on socket 197
0227135313|sip  |0|00|>>> Data Send to 172.31.8.12:5060
0227135313|sip  |0|00|    INVITE sip:22655@172.31.8.12:5060;user=phone SIP/2.0
0227135313|sip  |0|00|    Via: SIP/2.0/UDP 172.31.19.35;branch=z9hG4bK46872df86D3B6BBB
0227135313|sip  |0|00|    From: "22893" <sip:22893@172.31.8.12>;tag=E2F881A2-4BA4E548
0227135313|sip  |0|00|    To: <sip:22655@172.31.8.12;user=phone>
0227135313|sip  |0|00|    CSeq: 2 INVITE
0227135313|sip  |0|00|    Call-ID: 282b524e-418d205b-9bcf0469@172.31.19.35
0227135313|sip  |0|00|    Contact: <sip:22893@172.31.19.35>
0227135313|sip  |0|00|    Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER
0227135313|sip  |0|00|    User-Agent: PolycomRealPresenceTrio-Trio_8800-UA/5.4.4.7776
0227135313|sip  |0|00|    Accept-Language: en
0227135313|sip  |0|00|    Supported: replaces,100rel
0227135313|sip  |0|00|    Allow-Events: conference,talk,hold
0227135313|sip  |0|00|    Authorization: Digest username="pcom", realm="ccmsipline", nonce="6Z32wd++d8L/PHDr5iuYxp4pQEORMkrT", uri="sip:22655@172.31.8.12:5060;user=phone", response="4c1b70ff61a519bdc3cd998a4896a2a2", algorithm=MD5
0227135313|sip  |0|00|    Max-Forwards: 70
0227135313|sip  |0|00|    Content-Type: application/sdp
0227135313|sip  |0|00|    Content-Length: 472
0227135313|sip  |0|00|    
0227135313|sip  |0|00|    v=0
0227135313|sip  |0|00|    o=- 1488225193 1488225193 IN IP4 172.31.19.35
0227135313|sip  |0|00|    s=Polycom IP Phone
0227135313|sip  |0|00|    c=IN IP4 172.31.19.35
0227135313|sip  |0|00|    b=AS:2048
0227135313|sip  |0|00|    t=0 0
0227135313|sip  |0|00|    a=sendrecv
0227135313|sip  |0|00|    m=audio 2242 RTP/AVP 115 99 9 102 0 8 18 101
0227135313|sip  |0|00|    a=rtpmap:115 G7221/32000
0227135313|sip  |0|00|    a=fmtp:115 bitrate=48000
0227135313|sip  |0|00|    a=rtpmap:99 SIREN14/16000
0227135313|sip  |0|00|    a=fmtp:99 bitrate=48000
0227135313|sip  |0|00|    a=rtpmap:9 G722/8000
0227135313|sip  |0|00|    a=rtpmap:102 G7221/16000
0227135313|sip  |0|00|    a=fmtp:102 bitrate=32000
0227135313|sip  |0|00|    a=rtpmap:0 PCMU/8000
0227135313|sip  |0|00|    a=rtpmap:8 PCMA/8000
0227135313|sip  |0|00|    a=rtpmap:18 G729/8000
0227135313|sip  |0|00|    a=fmtp:18 annexb=no
0227135313|sip  |0|00|    a=rtpmap:101 telephone-event/8000
0227135313|sip  |0|00|<<< End of data send
0227135313|sip  |0|00|listener: Received packet from 172.31.8.12:5060
0227135313|sip  |0|00|<<<Data Received UDP
0227135313|sip  |0|00|    SIP/2.0 100 Trying
0227135313|sip  |0|00|    Via: SIP/2.0/UDP 172.31.19.35;branch=z9hG4bK46872df86D3B6BBB
0227135313|sip  |0|00|    From: "22893" <sip:22893@172.31.8.12>;tag=E2F881A2-4BA4E548
0227135313|sip  |0|00|    To: <sip:22655@172.31.8.12;user=phone>
0227135313|sip  |0|00|    Date: Mon, 27 Feb 2017 19:53:14 GMT
0227135313|sip  |0|00|    Call-ID: 282b524e-418d205b-9bcf0469@172.31.19.35
0227135313|sip  |0|00|    CSeq: 2 INVITE
0227135313|sip  |0|00|    Allow-Events: presence
0227135313|sip  |0|00|    Content-Length: 0
0227135313|sip  |0|00|    
0227135313|sip  |0|00|listener: Received packet from 172.31.8.12:5060
0227135313|sip  |0|00|<<<Data Received UDP
0227135313|sip  |0|00|    SIP/2.0 180 Ringing
0227135313|sip  |0|00|    Via: SIP/2.0/UDP 172.31.19.35;branch=z9hG4bK46872df86D3B6BBB
0227135313|sip  |0|00|    From: "22893" <sip:22893@172.31.8.12>;tag=E2F881A2-4BA4E548
0227135313|sip  |0|00|    To: <sip:22655@172.31.8.12;user=phone>;tag=22519890~6b498150-9c31-4bc3-bd35-92b1547fb0a8-49882082
0227135313|sip  |0|00|    Date: Mon, 27 Feb 2017 19:53:14 GMT
0227135313|sip  |0|00|    Call-ID: 282b524e-418d205b-9bcf0469@172.31.19.35
0227135313|sip  |0|00|    CSeq: 2 INVITE
0227135313|sip  |0|00|    Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
0227135313|sip  |0|00|    Allow-Events: presence
0227135313|sip  |0|00|    Server: Cisco-CUCM10.5
0227135313|sip  |0|00|    Send-Info: conference, x-cisco-conference
0227135313|sip  |0|00|    Remote-Party-ID: "Andrija Divac - 22655" <sip:22655@172.31.8.12>;party=called;screen=yes;privacy=off
0227135313|sip  |0|00|    Contact: <sip:22655@172.31.8.12:5060>;+u.sip!devicename.ccm.cisco.com="SEP5006AB80F968";video
0227135313|sip  |0|00|    Content-Length: 0
0227135313|sip  |0|00|    
0227135315|sip  |0|00|listener: Received packet from 172.31.8.12:5060
0227135315|sip  |0|00|<<<Data Received UDP
0227135315|sip  |0|00|    SIP/2.0 503 Service Unavailable
0227135315|sip  |0|00|    Via: SIP/2.0/UDP 172.31.19.35;branch=z9hG4bK46872df86D3B6BBB
0227135315|sip  |0|00|    From: "22893" <sip:22893@172.31.8.12>;tag=E2F881A2-4BA4E548
0227135315|sip  |0|00|    To: <sip:22655@172.31.8.12;user=phone>;tag=22519890~6b498150-9c31-4bc3-bd35-92b1547fb0a8-49882082
0227135315|sip  |0|00|    Date: Mon, 27 Feb 2017 19:53:14 GMT
0227135315|sip  |0|00|    Call-ID: 282b524e-418d205b-9bcf0469@172.31.19.35
0227135315|sip  |0|00|    CSeq: 2 INVITE
0227135315|sip  |0|00|    Allow-Events: presence
0227135315|sip  |0|00|    Reason: Q.850;cause=47
0227135315|sip  |0|00|    Server: Cisco-CUCM10.5
0227135315|sip  |0|00|    Content-Length: 0
0227135315|sip  |0|00|    
0227135315|sip  |0|00|Trying to send data to Destination 172.31.8.12 on socket 197
0227135315|sip  |0|00|>>> Data Send to 172.31.8.12:5060
0227135315|sip  |0|00|    ACK sip:22655@172.31.8.12:5060;user=phone SIP/2.0
0227135315|sip  |0|00|    Via: SIP/2.0/UDP 172.31.19.35;branch=z9hG4bK46872df86D3B6BBB
0227135315|sip  |0|00|    From: "22893" <sip:22893@172.31.8.12>;tag=E2F881A2-4BA4E548
0227135315|sip  |0|00|    To: <sip:22655@172.31.8.12;user=phone>;tag=22519890~6b498150-9c31-4bc3-bd35-92b1547fb0a8-49882082
0227135315|sip  |0|00|    CSeq: 2 ACK
0227135315|sip  |0|00|    Call-ID: 282b524e-418d205b-9bcf0469@172.31.19.35
0227135315|sip  |0|00|    Contact: <sip:22893@172.31.19.35>
0227135315|sip  |0|00|    Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER
0227135315|sip  |0|00|    User-Agent: PolycomRealPresenceTrio-Trio_8800-UA/5.4.4.7776
0227135315|sip  |0|00|    Accept-Language: en
0227135315|sip  |0|00|    Max-Forwards: 70
0227135315|sip  |0|00|    Content-Length: 0
0227135315|sip  |0|00|    
0227135315|sip  |0|00|<<< End of data send

Message 5 of 8
SteffenBaierUK
Polycom Employee & Community Manager

Re: Polycom Trio 8800 - Dialing issues with CUCM

Hello adivac730,

The issue is:

 

0227135315|sip  |0|00|    SIP/2.0 503 Service Unavailable
0227135315|sip  |0|00|    Via: SIP/2.0/UDP 172.31.19.35;branch=z9hG4bK46872df86D3B6BBB
0227135315|sip  |0|00|    From: "22893" <sip:22893@172.31.8.12>;tag=E2F881A2-4BA4E548
0227135315|sip  |0|00|    To: <sip:22655@172.31.8.12;user=phone>;tag=22519890~6b498150-9c31-4bc3-bd35-92b1547fb0a8-49882082
0227135315|sip  |0|00|    Date: Mon, 27 Feb 2017 19:53:14 GMT
0227135315|sip  |0|00|    Call-ID: 282b524e-418d205b-9bcf0469@172.31.19.35
0227135315|sip  |0|00|    CSeq: 2 INVITE
0227135315|sip  |0|00|    Allow-Events: presence
0227135315|sip  |0|00|    Reason: Q.850;cause=47
0227135315|sip  |0|00|    Server: Cisco-CUCM10.5
0227135315|sip  |0|00|    Content-Length: 0

I suggest you check => here <=


Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.

Best Regards

Steffen Baier

Polycom Global Services

----------------
The title Poly Employee & Community Manager is a community setting and does not reflect my role. I am just a simple volunteer in the community like everybody else. All posts and words are my own & do not represent the views of Employer.

----------------

Notice: This community forum is not an official Poly support resource, thus responses from Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge. If you need immediate and/or official assistance please open a service ticket through your proper support channels.
Please also ensure you always check the VoIP , Video Endpoint , Skype for Business , PSTN or RPM FAQ's
Message 6 of 8
Rebar
Occasional Visitor

Re: Polycom Trio 8800 - Dialing issues with CUCM

Has this been resolved?

If so, what is the resolution?

Message 7 of 8
Rebar
Occasional Visitor

Re: Polycom Trio 8800 - Dialing issues with CUCM

I use the following digitmap on my SS IP 7000

 

[2-9]xxxT|**x.T
9,[2-9]xxxxxx
9,1[2-9]xxxxxxxxx

 

and

digit timeout

3|3|3|3|3|3|3|3

Message 8 of 8