• ×
    Information
    Windows update impacting certain printer icons and names. Microsoft is working on a solution.
    Click here to learn more
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
  • ×
    Information
    Windows update impacting certain printer icons and names. Microsoft is working on a solution.
    Click here to learn more
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
Guidelines
The HP Community is where owners of HP products, like you, volunteer to help each other find solutions.
HP Recommended

Hi, I have a quick query regarding the use of polycom VVX phones in a Lync 2013 / Exchange 2007 Unified Messaging environment.

 

Any calls going via the Lync edge server from a VVX phone to a 2007 Unified Messaging enabled users voicemail will fail.

 

I believe this is due to ICE negotiation and have read "Exchange 2007 is not supported when connection requires ICE negotiation. Exchange 2007 only supports legacy ICE ver. 6 and the VVX only supports ICE ver.19."

 

My question is whether this can be changed on the VVX (if this is the cause), if another viable work around exists, or if indeed this is just flat out not supported - in which case, where is this written?

 

The error generated incidentally is as below.

 

Thanks in advance for any guidance or suggestions.

 

Event Type: Warning
Event Source: Microsoft Exchange Speech Engine
Event Category: Telephony Application Host
Event ID: 32768
Date:  27/10/2014
Time:  14:09:41
User:  N/A
Computer: CLAW
Description:
The Telephony Manager declined a call with Call Id '33bec0687a46c9f4727851f0a883aec4' for the following reason in component telephony session: 'The SDP media description received from the remote SIP peer could not be parsed.'. 
 
Further trace information for support personnel follows:
 
Microsoft.SpeechServer.Core.InvalidMediaException: The SDP media description received from the remote SIP peer could not be parsed. ---> System.ArgumentException: Unable to parse the following SDP message 'v=0
o=- 1414418981 1414418981 IN IP4 10.240.14.10
s=Polycom IP Phone
c=IN IP4 10.240.14.10
b=AS:512
t=0 0
a=sendrecv
m=audio 2266 RTP/SAVP 9 112 0 8 18 127
a=crypto:13 AES_CM_128_HMAC_SHA1_80 inline:GUfClYQfdoJe6FDRp8W17q8l2A7uhhUR6kQGgtSR|2^31|1:1
a=x-bypassid:2433785e-e5d7-4d4b-8fa1-290e606ed2e5
a=rtpmap:9 G722/8000
a=rtpmap:112 G7221/16000
a=fmtp:112 bitrate=24000
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:127 telephone-event/8000
a=ice-pwd:QB69WIT5kkGMI6/Ci58QZ29n
a=ice-ufrag:+sAH
a=rtcp:2267
a=candidate:1 1 UDP 2130706431 10.240.14.10 2266 typ host
a=candidate:1 2 UDP 2130706430 10.240.14.10 2267 typ host
a=candidate:2 1 TCP-PASS 6619135 80.194.196.109 53874 typ relay raddr 10.240.14.10 rport 43629
a=candidate:2 2 TCP-PASS 6619134 80.194.196.109 53874 typ relay raddr 10.240.14.10 rport 43629
a=candidate:3 1 UDP 16777215 80.194.196.109 53565 typ relay raddr 10.240.14.10 rport 2766
a=candidate:3 2 UDP 16777214 80.194.196.109 56912 typ relay raddr 10.240.14.10 rport 2767
a=candidate:4 1 TCP-ACT 7012351 80.194.196.109 53874 typ relay raddr 10.240.14.10 rport 43629
a=candidate:4 2 TCP-ACT 7012350 80.194.196.109 53874 typ relay raddr 10.240.14.10 rport 43629
a=candidate:5 1 TCP-ACT 1684733951 10.240.14.10 43629 typ srflx raddr 10.240.14.10 rport 43629
a=candidate:5 2 TCP-ACT 1684733950 10.240.14.10 43629 typ srflx raddr 10.240.14.10 rport 43629
'. ---> System.ArgumentException: A candidate in the SDP message had an unrecognized transport field: '2130706431'.
   at Microsoft.SpeechServer.Common.MediaDescription.ParseMediaTransportType(String field)
   at Microsoft.SpeechServer.Common.MediaDescription.ParseCandidate(String record)
   at Microsoft.SpeechServer.Common.MediaDescription.ParseAttribute(String record)
   at Microsoft.SpeechServer.Common.MediaDescription.Parse(String sdpMessage, Boolean isOffer)
   at Microsoft.SpeechServer.Common.MediaDescription..ctor(String sdpMessage, Boolean isOffer, Boolean throwIfFailed)
   --- End of inner exception stack trace ---
   --- End of inner exception stack trace ---
   at Microsoft.SpeechServer.Core.MediaNegotiation..ctor(LoggingContext loggingContext, ContentDescription rtcRemoteMediaOffer)
   at Microsoft.SpeechServer.Core.TelephonySessionInbound.CreateMediaNegotiation(ContentDescription rtcMediaDescription, SessionInfo sessionInfo, CallInfo callInfo, IPEndPoint sipPeerEndpoint)
   at Microsoft.SpeechServer.Core.TelephonySessionInbound.Initialize(SessionInfo sessionInfo, SessionReceivedEventArgs e, CallInfo callInfo, EventSerializer serializer, SpeechSession speechSession, Boolean isTlsConnection)
   at Microsoft.SpeechServer.Core.TelephonySessionInbound..ctor(SessionInfo sessionInfo, SessionReceivedEventArgs e, CallInfo callInfo)
   at Microsoft.SpeechServer.Core.TelephonyManager.CreateSession(Int32 inviteReceivedTickCount, SessionReceivedEventArgs e)
   at Microsoft.SpeechServer.Core.TelephonyManager.SignalingSessionReceived(Object sender, SessionReceivedEventArgs e)
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

 

1 REPLY 1
HP Recommended

Hello BenD,

welcome to the Polycom Community.

To my knowledge Exchange 2007 is currently not supported.

 

This issue is caused by unsupported media error coming from the Exchange 2007 server. The Exchange 2007 UM is using a legacy ICE stack ver 6.

 

PC Client supports both ICE version 6 and 19. Polycom UC Software only support ICE version 19.

 

At present we will not support legacy ICE version 6 so the only solution is to upgrade Exchange 2007 to the latest Exchange 2010 or later.

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

------------------------------------------------
Notice: I am an HP Poly employee but all replies within the community are done as a volunteer outside of my day role. This community forum is not an official HP Poly support resource, thus responses from HP Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge.
If you need immediate and/or official assistance for former Poly\Plantronics\Polycom please open a service ticket through your support channels
For HP products please check HP Support.

Please also ensure you always check the General VoIP , Video Endpoint , UC Platform (Microsoft) , PSTN
† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the <a href="https://www8.hp.com/us/en/terms-of-use.html" class="udrlinesmall">Terms of Use</a> and <a href="/t5/custom/page/page-id/hp.rulespage" class="udrlinesmall"> Rules of Participation</a>.