Mitel 3300 MCD and Exchange 2010

[simon.croak]

Hi All,

I have a strange issue I'm hoping someone on this forum has come across before.

I'm trying to setup exchange 2010 UM with our 3300 MCD.

I have followed the Mitel “Configure MCD 4.0 UR3 for use with Microsoft Exchange 2010” document that I was able to get from the Edocs website.

Everything seams to be working from the SIP trunk side of things. But subscriber access number or auto attendant don't seam to be working....I'll explain.

I currently have an ACD route setup with number 320 (1 digits to follow) pointing down the SIP trunk route.

When I setup my extension (5508) to call forward no answer to 3200 and then call 5508 from another phone I get the correct Exchange prompt to leave a message. I can leave a message and it gets delivered to my mailbox no problem.

If I call 3200 from my extension (or any other internal extension) to try and log into my mailbox I get "dead air".

If I call 3201 from my extension to try and get the auto attendant I also get "dead air".

I've been told the reason that I get the prompt when my extension is forwarded to 3200 is because the SIP packet contains a "Forwarded From" extension. But how do I fake this when I need to dial the subscriber access number?

I've read somethings (mostly on this forum) about a speed dial number. But I've tried a few different S/C's but nothing has changed.

If anyone reading this has Mitel MCD to Exchange 2010 setup correctly please let me know how you did it.

Cheers

Simon

[tscht28]

Hi Simon,

I have exchange 2010 UM & 3300 MCD working accept we doe not use the ACD method for routing our calls to voicemail.  I have performed this integration a couple of times (Exchange 2007 and now Exchange 2010) and I have never experienced the dead air issue you described.

I did run into a couple of challenges though and found the following commands useful: CCS TRACE ENABLE CONTINUOUS to see what digits are being sent to the Exchange Server when you dial your subscriber access number. 

You can also change the logging level on your Exchange server using the following PS commands:  Get-EventlogLevel "ExchangeServerNameHere\MSExchange Unified Messaging" (displays current logging levels).   

Followed by: Set-EventlogLevel "ExchangeServerNameHere\MSExchange Unified Messaging\UMCore" -level <Lowest | Low | Medium | High | Expert>.  I suggest the High setting, but change it back to the default setting you got when you ran the get-EventlogLevel command from above.

I am happy to share any sip peer profile settings or UM Dial plan configuration if that will help you, but not sure if they will help.

TS

[simon.croak]

Hi TS,

Thanks for the reply.

You mention that you don't use ACD. How do you get calls to the Exchange system?

I've found out that the "Dead Air" isn't actually dead air. It's the exchange system "Waiting" for more information I believe. If i dial 3201 (The exchange auto attendant) wait for the "dead air" and then dial another internal extension number I actually get transferred to that extension!

Thanks for the info about the logs. I'll try changing the logging level and see what I find.

I'm interested to see how you route calls to exchange in the mean time though.

Cheers

Simon

[tscht28]

Hi Simon,

I am curious to know what you are trying to accomplish with the ACD in the scenario you described.  What subscriber Access numbers do you have defined in your UM Dial Plan?

With our SIP configuration, We have 16 sip trunks licenses on the sip trunk (to mimic the 16 copper trunks we had to our old ActiveVoice voicemail system) and currently have two subscriber access numbers (one from our 2007 UM server coexistence and one for our 2010 UM server).

Our subscriber access number points to a Mitel S/C number.  The S/C actual number is configured in ARS and points to a route defined to our sip trunk.  We assign a call reroute alternative to the S/C and also configure the call reroute first alternative to number to dial the S/C on Busy/No Answer.

It seems by our description of what happening that Exchange is not receiving all the digits it needs to complete the call.  In Exchange 2007 with the UMCore logging set to high you would see a log similar to this:  The Unified Messaging server has received a call from "5507", with user extension "3200" "5508".  Unfortunately Microsoft changed their logging detail in 2010 and we no longer see this detail.

I am happy to share additional configuration details if needed.

TS

[LoopyLou]

He said ACD but think he meant ARS.

[simon.croak]

Hi Guys,

Thanks for your replies. I've managed to turn on UM debugging, and I have posted the full "conversation" below. It seams like it should be working to me especially with the "The telephone interface is starting activity" messages.

TS - I wonder. What happens if you call YOUR ARS route directly from an extension?

Anyway the logs:

Ext 5508 is my desk phone. Number 3200 is the number defined in exchange as the Subscriber Access Number in the Dial Plan (And the ARS route):

Msg #1:

Code: [Select]

A call was received with the following parameters:
Calling Party: "sip:5508@10.159.6.14",
Called Party: "sip:3200@10.159.207.23",
Diversion Information: "",
Referred-By Header: "",
Call ID "654690576-98448750"
Msg #2:

Code: [Select]

The Unified Messaging server has received a call from "5508", with user extension "" and a call ID of "654690576-98448750".

Msg #3:

Code: [Select]

The telephone interface is starting activity "Type: Microsoft.Exchange.UM.UMCore.Menu, ID: 0callDiscriminator" for the call with ID 654690576-98448750.
Msg #4:

Code: [Select]

The telephone interface is starting activity "Type: Microsoft.Exchange.UM.UMCore.Menu, ID: 0100" for the call with ID 654690576-98448750.
Msg #5:

Code: [Select]

The telephone interface is starting activity "Type: Microsoft.Exchange.UM.UMCore.Menu, ID: 0infoGreetingMenu" for the call with ID 654690576-98448750.
Msg #6:

Code: [Select]

The telephone interface is starting activity "Type: Microsoft.Exchange.UM.UMCore.Menu, ID: 0101" for the call with ID 654690576-98448750.
Msg #7:

Code: [Select]

The telephone interface is starting activity "Type: Microsoft.Exchange.UM.UMCore.Menu, ID: 0104" for the call with ID 654690576-98448750.
Msg #8:

Code: [Select]

The Unified Messaging server has ended a call with ID "654690576-98448750" because the user at the far end disconnected.
Msg #9:

Code: [Select]

Call data: UnAuthenticatedPilotNumber,654690576-98448750,WBEXCHANGE3,95c1b748-57e4-4879-9302-12498a1a73d7,WB UM Dial Plan,2013-02-06T22:50:28-08:00,0,00:00:05,3e7217b8-5b84-4436-9741-c369aaff2ee8,Mitel 3300 MCD,"5508","",Direct,Answer,None,"",0,0,0,0,0,0,0,0,0,g7221,0,0,42,-1,-1,-1,-1,-1,-1
Thanks again guys.

Simon

[tscht28]

Hi Simon,

When I call my ARS Route directly from my extension, I get my mailbox name and then I am asked enter my PIN.  This should be the expected behavior as your calling digits are carried into the SubscriberAccess Attendant.  Your posted messages also looks correct, even msg #9.  This message indicates that you did not enter your mailbox; otherwise, you would have received this message: The Unified Messaging server successfully authenticated user "Exch2010 TestUser".

Please keep in mind per my last post that our Exchange Subscriber Access number and ARS route differ as we use a system speedcall, but this achieves the same thing.

I also created a SA that matched my ARS route and it worked correctly. I feel it may be related to your configuration. If you would like to post your Class of Service Assignment, SIP Profile, Digit Mod, and your Trunk Service Assignment for your ExchangeUM SIP Trunk.  I would be happy to compare the settings.

TS

[simon.croak]

Hi TS,

Thanks so much for your time on this.

I have attached the information you have requested. I've PDF'ed all the forms hope that's OK.

Cheers

Simon

[tscht28]

Hi Simon,

Here are my recommended changes.  Your Trunk Service Assignment and DigitMod forms look good. I hope this helps and look forward to your next post.

TS

[simon.croak]

Hi TS,

Unfortunately I did all those changes and it hasn't helped.

I wonder if we can compare exchange setups? How would you like to PM me your email address so I can send you screenshots of my setup?

Cheers

Simon

[tscht28]

Hi Simon,

Sorry that did not do the trick.  Try changing next two SIP Peer attributes one at time:

Allow Using Update for Early Media Renegotiation - Yes
Avoid Signaling Hold to the Peer - Yes

I will send you my info.

TS

[dstern]

We had a similar issue and changed the setting in the SIP peer profile "Renegotiate SDP To Enforce Symmetric Codec" to Yes.