Yealink Forums
T48G UC Edition Message (Voicemail) - Printable Version

+- Yealink Forums (http://forum.yealink.com/forum)
+-- Forum: IP Phone Series (/forumdisplay.php?fid=4)
+--- Forum: T4x Series (/forumdisplay.php?fid=31)
+--- Thread: T48G UC Edition Message (Voicemail) (/showthread.php?tid=10973)



T48G UC Edition Message (Voicemail) - abeggled - 10-22-2015 06:11 AM

I'm unable to dial in my voicemail from my t48g. Not by clicking the Message button, nor by dialing "99" my voicemail number.
With other phones or the lync client everything is working as expected.

Exchange UM is logging these events:
The Microsoft Exchange Unified Messaging Call Router service rejected the call for the following reason: 15605;source="SRV013.xxxx.xx.xxxxx.net";reason="Invalid SIP header." Microsoft.Exchange.UM.UMCore.InvalidSIPHeaderException: The Microsoft Exchange Unified Messaging service on the Mailbox server received "INVITE" request with an invalid SIP header "USER-AGENT" with value "".
at Microsoft.Exchange.UM.UcmaPlatform.UcmaSignalingHeader.FromSignalingHeader(Signa​lingHeader h, String context)
at Microsoft.Exchange.UM.UcmaPlatform.UcmaCallInfo.<get_RemoteHeaders>b__0(SignalingHeader x)
at Microsoft.Exchange.UM.UMCommon.ExtensionMethods.ConvertAll[TInput,TOutput](IEnumerable`1 inputCollection, Converter`2 converter)
at Microsoft.Exchange.UM.UcmaPlatform.UcmaCallInfo.get_RemoteHeaders()
at Microsoft.Exchange.UM.UMCore.CafeRoutingContext..ctor(PlatformCallInfo callInfo, UMADSettings config)
at Microsoft.Exchange.UM.UcmaPlatform.UcmaCallRouterPlatform.TryHandleIncomingCall(​CallReceivedEventArgs`1 args, Exception& error, Boolean& isDiagnosticCall)
at Microsoft.Exchange.UM.UcmaPlatform.UcmaUtils.<>c__DisplayClassf.<ProcessPlatformRequestAndReportErrors>b__d()



RE: T48G UC Edition Message (Voicemail) - James_Yealink - 10-22-2015 05:51 PM

Hello,

Please try a reset and check again.
If problem persist, please provide us phone configuration file and syslog.

Thanks,


RE: T48G UC Edition Message (Voicemail) - abeggled - 10-24-2015 01:54 AM

Thanks, the reset did the trick.