Plantronics + Polycom. Now together as Poly Logo

Polycom Trio 8800 - SIP/2.0 488 Not Acceptable Here when application sharing in a conference

Highlighted
Occasional Visitor

Polycom Trio 8800 - SIP/2.0 488 Not Acceptable Here when application sharing in a conference

User agent: Polycom/5.9.1.10906

 

We establish an Audio/Video conference involving the Trio device and all is well. Whilst in the conference, a user starts an RDP session. Intermittently, the RDP session fails to establish on the Trio device with a 488 response, ms-diagnostics code 24009.

 

We have captured the following Invite, followed by 488 Response.

 

INVITE

sip:helen.smith@domain.co.uk;gruu;opaque=app:conf:applicationsharing:id:LS8KM237;transport=tls SIP/2.0
p-asserted-identity: "10FA.4.26.FC" <sip:10FA.4.26.FC@domain.com>,<tel:+442039770890>
via: SIP/2.0/TLS 10.253.190.55:56959;branch=z9hG4bK41f3a723B9D50182;ms-received-port=56959;ms-received-cid=105ED00
from: "10FA.4.26.FC" <sip:10FA.4.26.FC@domain.com>;tag=41348C6C-292F0359;epid=64167f4ef028
to: <sip:helen.smith@domain.co.uk;gruu;opaque=app:conf:applicationsharing:id:LS8KM237>
cseq: 1 INVITE
call-id: b4c3a241130c05393a8cd8ccb34ef028
contact: <sip:10FA.4.26.FC@domain.com;opaque=user:epid:GR8Ox3xB8VyNl644R12n_wAA;gruu>
allow: INVITE,ACK,BYE,CANCEL,OPTIONS,INFO,MESSAGE,SUBSCRIBE,NOTIFY,PRACK,UPDATE,REFER
user-agent: Polycom/5.9.1.10906 PolycomRealPresenceTrio-Trio_8800-UA/5.9.1.10906
accept-language: en
ms-subnet: 10.253.190.0
allow-events: conference,talk,hold
supported: replaces
supported: ms-safe-transfer
supported: ms-bypass
supported: ms-dialog-route-set-update
supported: 100rel
supported: gruu-10
ms-endpoint-location-data: NetworkScope;ms-media-location-type=intranet
MS-Conversation-ID: AdXU8DFlOTdiNmNjYWVkOWYxZDhmNA==
max-forwards: 70
content-type: application/sdp
content-length: 3031

v=0
o=- 1580116253 1580116253 IN IP4 10.253.190.55
s=Polycom IP Phone
c=IN IP4 10.253.190.55
b=AS:25000
t=0 0
a=sendrecv
a=x-mediabw:applicationsharing-video send=25000;recv=25000
a=x-devicecaps:audio:send,recv;video:send,recv:applicationsharing:send,recv
m=video 42004 RTP/SAVP 122 123
a=crypto:25 client AES_CM_128_HMAC_SHA1_80 inline:YZrJjTW+PY7wHUTX7OB3PT1PN6t+YoIbieZDTSpz|2^31
a=rtcp-fb:* x-message app send:src,x-pli recv:src,x-pli
a=rtcp-rsize
a=label:applicationsharing-video
a=x-ssrc-range:3402303795-3402303894
a=x-mediasettings:applicationsharing-video=required
a=rtpmap:122 X-H264UC/90000
a=fmtp:122 packetization-mode=1;mst-mode=NI-TC
a=rtpmap:123 x-ulpfecuc/90000
a=recvonly
a=ice-pwd:4fH5BPVJk0TkSJJCDF1OSN2q
a=ice-ufrag:Wvha
a=rtcp:42005
a=candidate:1 1 UDP 2130706431 10.253.190.55 42004 typ host
a=candidate:1 2 UDP 2130706430 10.253.190.55 42005 typ host
a=candidate:2 1 TCP-PASS 6619135 80.247.58.216 51236 typ relay raddr 10.253.190.55 rport 42008
a=candidate:2 2 TCP-PASS 6619134 80.247.58.216 51236 typ relay raddr 10.253.190.55 rport 42008
a=candidate:3 1 UDP 16777215 80.247.58.216 57515 typ relay raddr 10.253.190.55 rport 42006
a=candidate:3 2 UDP 16777214 80.247.58.216 54173 typ relay raddr 10.253.190.55 rport 42007
a=candidate:4 1 TCP-ACT 7012351 80.247.58.216 51236 typ relay raddr 10.253.190.55 rport 42008
a=candidate:4 2 TCP-ACT 7012350 80.247.58.216 51236 typ relay raddr 10.253.190.55 rport 42008
a=candidate:5 1 TCP-ACT 1684733951 10.253.190.55 42008 typ srflx raddr 10.253.190.55 rport 42008
a=candidate:5 2 TCP-ACT 1684733950 10.253.190.55 42008 typ srflx raddr 10.253.190.55 rport 42008
m=applicationsharing 42003 TCP/RTP/SAVP 127
a=crypto:26 AES_CM_128_HMAC_SHA1_80 inline:u4S0RgBZIX0kPEpNuONJ0I4HhJMTe7CIj8isNuQe|2^31|1:1
a=crypto:27 AES_CM_128_HMAC_SHA1_80 inline:PK3BiC77LEWPavG0LLZ7dSqZGBqmaw9tCRi13qZD|2^31
a=setup:active
a=connection:existing
a=mid:1
a=x-applicationsharing-session-id:1
a=x-applicationsharing-role:viewer
a=x-applicationsharing-media-type:rdp
a=x-applicationsharing-contentflow:recvonly
a=rtpmap:127 x-data/90000
a=ice-pwd:4fH5BPVJk0TkSJJCDF1OSN2q
a=ice-ufrag:Wvha
a=rtcp:42003
a=candidate:1 1 TCP-PASS 2120548095 10.253.190.55 42003 typ host
a=candidate:1 2 TCP-PASS 2120548094 10.253.190.55 42003 typ host
a=candidate:2 1 TCP-ACT 2120941567 10.253.190.55 42003 typ host
a=candidate:2 2 TCP-ACT 2120941566 10.253.190.55 42003 typ host
a=candidate:3 1 TCP-PASS 6619135 80.247.58.216 52324 typ relay raddr 10.253.190.55 rport 42002
a=candidate:3 2 TCP-PASS 6619134 80.247.58.216 52324 typ relay raddr 10.253.190.55 rport 42002
a=candidate:4 1 TCP-ACT 7012351 80.247.58.216 52324 typ relay raddr 10.253.190.55 rport 42002
a=candidate:4 2 TCP-ACT 7012350 80.247.58.216 52324 typ relay raddr 10.253.190.55 rport 42002
a=candidate:5 1 TCP-ACT 1684733951 10.253.190.55 42002 typ srflx raddr 10.253.190.55 rport 42002
a=candidate:5 2 TCP-ACT 1684733950 10.253.190.55 42002 typ srflx raddr 10.253.190.55 rport 42002

Response from Skype Conferencing Server

 

SIP/2.0 488 Not Acceptable Here
via: SIP/2.0/TLS 10.253.190.55:56959;branch=z9hG4bK41f3a723B9D50182;ms-received-port=56959;ms-received-cid=105ED00
content-length: 0
from: "10FA.4.26.FC"<sip:10FA.4.26.FC@domain.com>;tag=41348C6C-292F0359;epid=64167f4ef028
to: <sip:helen.smith@domain.co.uk;gruu;opaque=app:conf:applicationsharing:id:LS8KM237>;epid=167F09B3BC;tag=59761506f
cseq: 1 INVITE
call-id: b4c3a241130c05393a8cd8ccb34ef028
server: RTCC/6.0.0.0 applicationsharing
ms-diagnostics: 24009;source="PR22SFEP02.pool-resource.local";reason="Error parsing SDP: Failure negotiating SRTP encryption for media";component="ASMCU"
ms-diagnostics-public: 24009;reason="Error parsing SDP: Failure negotiating SRTP encryption for media";component="ASMCU"
ms-endpoint-location-data: NetworkScope;ms-media-location-type=intranet
ms-application-via: ms-udc.cdr%3Dfd71d429f9d7357b074d3adeb6469ab4%3A7%3Barch%3Dfd71d429f9d7357b074d3adeb6469ab4%3A7%3Bconvhist%3D0%3A7;ms-pool=cspool22.pool-resource.local;ms-application=http%3A%2F%2Fwww.microsoft.com%2FLCS%2FUdcAgent;ms-server=PR22SFEP02.pool-resource.local

 

The one thing I observe is what looks like a malformed a=crypto attribute in the Video SDP block - notice the additional "client" parameter which would normally be associated with cryptoscale:

 

m=video 42004 RTP/SAVP 122 123
a=crypto:25 client AES_CM_128_HMAC_SHA1_80 inline:YZrJjTW+PY7wHUTX7OB3PT1PN6t+YoIbieZDTSpz|2^31

 

Has anyone else seen this? And how do I get it fixed?

Message 1 of 2
1 REPLY 1
Highlighted
Polycom Employee & Community Manager

Re: Polycom Trio 8800 - SIP/2.0 488 Not Acceptable Here when application sharing in a conference

Hello @SamBrereton ,

 

Welcome to the Poly Community.

 

I had a quick look in our internal database and could not find any related issues with the combination of the provided error messages.

 

I would initially suggest you get the Trio on a currently supported software like UC Software 5.9.2 Rev AA and re-test.

 

The next step would be getting this into support if this can be replicated in a manner to allow us to try and troubleshoot.

 

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

End Customers are usually unable to open a ticket directly with Poly support. Available End User Poly services offerings are detailed here

 

I can see the device in question was sold via GECDF-ScanSource UK Ltd back in 31/07/2018 so they can open a ticket for you.

 

Please be aware from a Poly perspective the device is out of warranty.

 

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

Best Regards

Steffen Baier

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

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 2