Hab’s Blab

Setup Unified Messaging (UM) at a client site with integration with Skype for Business and CUCM, everything was working great and then it just stopped.

I checked the event viewer on all the systems an found the error Event ID 1423

The Microsoft Exchange Unified Messaging service on the Mailbox server encountered an error while trying to process the message with header file “C:\Program Files\Microsoft\Exchange Server\V15\UnifiedMessaging\voicemail\dd4174e6-d96d-48d2-a0a5-54a2d9805888.txt”. Error details: “Microsoft.Exchange.UM.UMCore.SmtpSubmissionException: Submission to the Hub Transport server failed. The operation will be retried. —> Microsoft.Exchange.Net.ExSmtpClient.UnexpectedSmtpServerResponseException: Unexpected SMTP server response. Expected: 220, actual: 500, whole response: 500 5.3.3 Unrecognized command

at Microsoft.Exchange.Net.ExSmtpClient.SmtpTalk.CheckResponse(ServerResponseInfo response, Int32 expectedCode)

at Microsoft.Exchange.Net.ExSmtpClient.SmtpTalk.Command(SmtpChunk[] chunks, SmtpCommandType command, Int32 expectedCode)

at Microsoft.Exchange.Net.ExSmtpClient.SmtpTalk.StartTls(Boolean useAnonymousTls)

at Microsoft.Exchange.Net.ExSmtpClient.SmtpClient.Submit()

at Microsoft.Exchange.UM.UMCore.SmtpSubmissionHelper.SubmitMessage(MessageItem message, String senderAddress, Guid senderOrgGuid, String recipientAddress, OutboundConversionOptions submissionConversionOptions, InternalExchangeServer smtpServer)

at Microsoft.Exchange.UM.UMCore.SmtpSubmissionHelper.SubmitMessage(MessageItem message, String senderAddress, Guid senderOrgGuid, String recipientAddress, OutboundConversionOptions submissionConversionOptions, String requestId)

— End of inner exception stack trace —

Server stack trace:

at Microsoft.Exchange.UM.UMCore.SmtpSubmissionHelper.SubmitMessage(MessageItem message, String senderAddress, Guid senderOrgGuid, String recipientAddress, OutboundConversionOptions submissionConversionOptions, String requestId)

at Microsoft.Exchange.UM.UMCore.SmtpSubmitStage.InternalDoSynchronousWork()

at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)

at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)

Exception rethrown at [0]:

at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg, Boolean bProxyCase)

at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed, MessageData& msgData)

at Microsoft.Exchange.UM.UMCore.SynchronousPipelineStageBase.SynchronousWorkDelegate.EndInvoke(IAsyncResult result)

at Microsoft.Exchange.UM.UMCore.SynchronousPipelineStageBase.EndSynchronousWork(IAsyncResult r)”

I browsed to the directory C:\Program Files\Microsoft\Exchange Server\V15\UnifiedMessaging\voicemail and found all the voicemail txt and wave files were located there and have not yet been submitted to the transport service.

1. Opened up the Exchange 2013 ECP
2. Browsed to Mailflow -> Receive Connectors
3. Noticed that someone had recently added a new Receive Connector for Internal Relays,
4. I opened up the Internal Relays Receive Connector and clicked on Security and found that only Transport Layer Security (TLS) and Anonymous Users were selected
5. Checked the box for Exchange Server Authentication and clicked Save
6. Restarted the Exchange UM Service

Voicemails were now sent to their appropriate mailboxes and MWI was working on both Skype for Business clients and Cisco Phones.

Share on Facebook

Tweet

Follow us