Comments on: Configuring MS Exchange Server 2007/2010 Unified messaging with 3CX Phone System

By: Stefan Walther

Stefan Walther — Fri, 05 Mar 2010 08:27:14 +0000

Hello,

reg. Exchange 2010 and MWI. You have to set the WMI in the Phone to look at the exchange status and not more to the 3CX PBX.
I will relook into it and see if we can make a way that you dont have to change the Phones to a new MWI Server.

Plz open a ticket at support.3cx.com and ask for Stefan in it.
Thx

By: Nick Galea

Nick Galea — Fri, 05 Mar 2010 05:35:13 +0000

We have tested MWI and it works in 2010 but not in 2007 (Exchange 2007 does not support MWI). Please open up a support ticket via the 3Cx support portal so our support dept can help you.

By: Gerryvs

Gerryvs — Thu, 04 Mar 2010 18:06:37 +0000

I’ve made a test setup with 3cx and Exchange 2010 Unified Messaging, Voice mail works fine, but the MWI seems to be a different story.

The Exchange server is having troubles letting 3CX know that the MWI indicator should be switched on for an extension. The events logged in Exchange are :

An error occurred while sending MWI notification ’1/4 (unread/read)’ for mailbox ‘user1(f3e478e3-5b11-417e-a3c6-36e06786e9d2)’ associated with UM extension ’406′. The target selected was ‘My-3cx’. A different target will be attempted. Additional information: Microsoft.Exchange.UM.UMCommon.MwiTargetException: An error occurred while attempting to deliver an MWI message using target Zoe-PB-0001. —> Microsoft.SpeechServer.SipPeerException: A SIP NOTIFY message has failed. —> ResponseCode=405 ResponseText=Method Not Allowed
Microsoft.Rtc.Signaling.FailureResponseException: The requested operation failed.
at Microsoft.Rtc.Signaling.SipAsyncResult.ThrowIfFailed()
at Microsoft.Rtc.Signaling.Helper.EndAsyncOperation[T](Object owner, IAsyncResult asyncResult)
at Microsoft.Rtc.Signaling.RealTimeEndpoint.EndSendMessage(IAsyncResult asyncResult)
at Microsoft.SpeechServer.Core.TelephonyManager.SendNotifyMessageCallback(IAsyncResult result)

— End of inner exception stack trace —
— End of inner exception stack trace —

followed by event :

The Unified Messaging server failed to deliver the MWI notification ’1/4 (unread/read)’ for the UM-enabled mailbox ‘User1(f3e478e3-5b11-417e-a3c6-36e06786e9d2)’ associated with UM extension ’406′. Additional information: Microsoft.Exchange.UM.UMCommon.MwiNoTargetsAvailableException: There are no more targets available to send an MWI message for user User1

Any ideas ?

Best Regards,
Gerry

By: Nick Borg

Nick Borg — Thu, 04 Mar 2010 10:51:30 +0000

Check event viewer and exchange logs. You will see why this is happening. Could be virtualization problem yes.

By: Nick Galea

Nick Galea — Thu, 04 Mar 2010 10:20:52 +0000

Not particularly in my opinion. It does offer voice recognition though but probably it wont work in Sweden.

By: Koen Zomers

Koen Zomers — Thu, 04 Mar 2010 10:18:31 +0000

I have this configured in my test lab for a while now. Every now and then I encounter a timeout when 3CX tries to connect to Exchange 2010. This was the same when being connected to Exchange 2007. The transfer fails in that case. When trying again directly after that, it does work. Anyone encountered the same problem and perhaps knows a resolution? I’m guessing it might have something to do with my lab being virtualized using Hyper-V.

By: Jim

Jim — Tue, 02 Mar 2010 22:16:15 +0000

Hi,

Are there any advantages of using Microsoft Exchange as Auto Attendant instead of the Digital Receptionist in 3CX?