Messages

1

Mitel MiVoice Business/MCD/3300 / Re: Integrating Mitel, Lync and Exchange 2010 UM together

« on: September 29, 2011, 05:29:37 AM »

why not have two trunks? Licensing is one reason - if you only have a limited no of sip trunk licenses they effectively have to be split between the two trunks. the MCD would not allow me to assign more than the remaining no of sip licenses to a new trunk. Yeah I know - they dont cost much but I like to make the most use of what we have!

The other reason is just vanity - it seams like the neatest solution to just have one trunk to lync. But I know that is a very weak justification! I'll work on the wireshark captures and see where that gets me but my time on this aspect of the project is running out so I guess I will end up settling for the two trunk method! 

2

Mitel MiVoice Business/MCD/3300 / Re: Integrating Mitel, Lync and Exchange 2010 UM together

« on: September 28, 2011, 12:40:46 PM »

ok - I have been lookingf at the UM logs on exchange when a diverted call comes in from the two paths:

If I call a busy extension and it gets diverted using the direct sip trunk to exchange I get a message on the exchange server as follows:

Code: [Select]

A call was received with the following parameters:
Calling Party: "sip:5956@100.0.1.2",
Called Party: "sip:6159@exchangeserver.my.domain",
Diversion Information: ""<username>" <sip:5965@100.0.1.2>;reason=user-busy;counter=1",
Referred-By Header: "",
Call ID "3868999760-92479639@100.0.1.2".Notice how the diversion information is set correctly.

If I do the same but via a trunk connecting to Lync the Diversion information is not set. Any ideas how I can rectify this or is this not related?

Thanks,

Sam

3

Mitel MiVoice Business/MCD/3300 / Integrating Mitel, Lync and Exchange 2010 UM together

« on: September 28, 2011, 09:55:14 AM »

Hi,

Has anyone got all three of these working well together? The problem I am facing is that I can get our 3300 (4.1) integrated with Exchange using SIP - the VM functions all work and MWI works.

I can get the 3300 integrated with Lync via a different Sip trunk  with calls passing between them just fine

Lync and UM also works fine

The problem is if I try to configure everything so calls to both mitel and Lync users go to exchange using just a single trunk to lync.

ie: mitel->lync->Exchange um

in this configuration I can dial the exchange um SA number from a mitel handset - exchange answers and recognises the extension I am calling from and prompts me to log in. However when I set up the call re-routing on the mitel system to re-route calls to the same SA number if an extension is busy or unavailable the exchange server answers with a generic prompt asking for my mailbox number rather than with the user's greeting and prompting for a message.

On the mitel side I have a system speed call that dials the SA number which is routed via the lync sip trunk.

Hope that makes sense? any help would be appreciated - or is what I am doing impossible and I have to just go with two sip trunks - one to exchange for UM for mitel extensions and one to lync for lync extensions?

Cheers,

Sam

4

Mitel MiVoice Business/MCD/3300 / Re: Calls to Lync over SIP are showing as Busy

« on: September 27, 2011, 12:06:20 PM »

Thanks for the reply,

I think I have missed a critical info resource.... what is MOL?

It is the routing of normal Mitel extensions that I have only half working via the Lync mediation server... allows me to pick up messages but not leave them. Same programming but using the second trunk direct to exchange UM works fine. i'll work on it some more but it's almost like the call re-routing stuff breaks when going via Lync.

For instance - I have two SIP trunks configured on MCD - Lync and Exchange

extensions 5xxx are on the MCD and 6xxx on lync
Exchange SA is configured as 6959

Call re-routing first alternate is set to 6959

using the ARS Route form to I enable exchange UM and dialling 6959 correctly takes me to the sa and the call re-routing works (I can leave a message)

If I then swap the ARS Rout to use the Lync Trunk then dialling 6959 correctly takes me to the SA and recognises my extension and I am asked to log in as before. But the call re-routing rings, then plays the unobtainable tone.

Anyway if anyone has any ideas - would be appreciated. I suppose I could go down the dual-trunk route as you suggest but I'm willing to spend a couple more days on this to see if I can get away with just one trunk to Lync.

5

Mitel MiVoice Business/MCD/3300 / Re: Calls to Lync over SIP are showing as Busy

« on: September 27, 2011, 10:00:22 AM »

Hi,

I have been having similar issues... the only way I got this to work is to leave the registrar and sip proxy FQDN or IP address settings empty on the network elements page - I am not sure this is correct as all the articles I found on the web show these settings confgured.

Has anyone actually got an official guide for this setup?

I spent a week on this and so far have managed to get RCC and enterprise voice (sip trunk between mitel and Lync) working but I cannot get Mitel using Exchange UM without creating a second sip trunk directly to the exchange server. If I go via Lync then it recognises the extension and allows me to log in to play back messages but forwarding calls to the SA number to allow callers to leave a message doesnt work (it does if I connect a sip trunk directly to exchange) I just get an unavailable tone.

Also with Mitel and lync tied in - If I set a user to be RCC enabled then you seem to loose the ability to be able to call their lync extension from the mitel - obviously the RCC functions all work but even selecting the computer as the preferred device doesnt allow calls to/from mitel. Not sure if this is expected behaviour or not.

Any help much appreciated as this is driving me nuts.

Cheers,

Sam

P.s. using MCD 4.1