Just wondering if anyone has any suggestions. I have deployed a Lync Front End for a client and set up Exchange 2007SP2 with UC for the voicemail features. There are also several VVX 500 phones which I have updated with the latest software. I am able to dial into voicemail from outside the organisation and from any Lync client within the organisation. Voicemails are accessible through Outlook - but using the Messages button or dialling direct to the Subscriber Access line from VVX 500 units disconnects straight away.
I have run a wireshark capture on the same network segment as the phone, collected snooper logs from the Front End server and have also gone through the Exchange event logs. This is what I have discovered so far:
Looking at SIP traffic, the voicemail request resolves to the Exchange 2007 server correctly, but Exchange responds with "SIP/2.0 415 Unsupported Media Type" and the front end returns "SIP/2.0 480 Temporarily Unavailable - Failed to route to Exchange Server" back to the handset.
Exchange application event logs lodges the following:
The Telephony Manager declined a call with Call Id '0dd0f095c1df1940206ef3c4c9b0f257' 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=- 1375155153 1375155153 IN IP4 192.168.1.46 s=Polycom IP Phone c=IN IP4 192.168.1.46 b=AS:512 t=0 0 a=sendrecv m=audio 2226 RTP/SAVP 9 112 0 8 18 127 a=crypto:3 AES_CM_128_HMAC_SHA1_80 inline:laNesH4dzGC04/wDylaiFTSOZOy8V+p65raLjWRC|2^31|1:1 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=rtcp:2227 a=candidate:1 1 UDP 2130706431 192.168.1.46 2226 typ host a=candidate:1 2 UDP 2130706430 192.168.1.46 2227 typ host a=candidate:2 1 TCP-ACT 1684733951 192.168.1.46 2226 typ srflx raddr 192.168.1.46 rport 2226 a=candidate:2 2 TCP-ACT 1684733950 192.168.1.46 2226 typ srflx raddr 192.168.1.46 rport 2226 a=ice-pwd:LqHX11xQkVdINwwC0FpaTQOd a=ice-ufrag:F1vz m=video 2228 RTP/SAVP 109 34 a=crypto:4 AES_CM_128_HMAC_SHA1_80 inline:gPnDkNMimdcaXfzxiMGWvcbN4seI6jXVHTqKXLeF|2^31|1:1 a=rtpmap:109 H264/90000 a=fmtp:109 profile-level-id=42800d a=rtpmap:34 H263/90000 a=fmtp:34 CIF=1;QCIF=1;SQCIF=1 a=rtcp:2229 a=candidate:1 1 UDP 2130706431 192.168.1.46 2228 typ host a=candidate:1 2 UDP 2130706430 192.168.1.46 2229 typ host a=candidate:2 1 TCP-ACT 1684733951 192.168.1.46 2228 typ srflx raddr 192.168.1.46 rport 2228 a=candidate:2 2 TCP-ACT 1684733950 192.168.1.46 2228 typ srflx raddr 192.168.1.46 rport 2228 a=ice-pwd:LqHX11xQkVdINwwC0FpaTQOd a=ice-ufrag:F1vz '. ---> 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) *******************
Any assistance would be greatly appreciated. Many thanks.
welcome back to the Polycom Community.
It is always useful to provide the current software version as other users may not be familiar what you class as current software or if this post is found via the community search in weeks or moths to come this would not be clear to anyone.
In addition it is useful to provide information on how you have provisioned the phone.
Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.
Polycom Global Services
Thanks for the reply.
All the VVX 500 phones are running software version 184.108.40.20664.
I have read through the Deploying Polycom® UC Software for use with Microsoft® Lync™ Server 2010 guide and followed the relevant portions yes.
I am using the base profile set to Lync on all the phones. The phones were manually provisioned.
I'm definitely investigating the Exchange infrastructure to determine if that is the root of this issue - but I was just checking to see if anyone had experienced this before or had any suggestions. As I mentioned, all other Lync devices and clients connect to voicemail without issue - its just the VVX 500 phones that don't.
using the base profile you should not need to configure anything manually.
Using the PIN authentication the phone would just subscribe so your above comment would possibly need more clarification.
Please be aware of the following when utilizing UCS 4.1.0 or later:
The use of Polycom UC Software versions 4.1.X (“Software”) requires the purchase of a separate Software license for every device that will use the Software in a Lync environment. You may not install, access, or use the Software in a Lync environment on more devices than are listed on your license until additional licenses have been purchased and authorized by Polycom. These licenses should be purchased from the same company from which you purchased the devices. You may operate devices against a Lync server for trial purposes for up to 30 days without purchasing a license. Use of the Software is subject to the terms and conditions of the End User License Agreement.
Polycom reserves the right to audit your deployment to verify that you have sufficient licenses to match the number of devices being used.
I would suggest you work with your Polycom reseller and/or Polycom support directly.
Polycom Global Services
When I said "manually provisioned" I was referring to not utilising a provisioning server for the deployment.
Okay, I'll explore other avenues for support. Thanks.
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.