Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - tscht28

Pages: [1] 2
1
Mitel released the following document: Configure the Mitel LBG 3.2.0.9 with Microsoft Lync 2010.  Document id: 11-5159-00074.

Here are the requirements:
Mitel 3300 MCD – Mxe Platform 10.2.0.26_2  (MCD 4.2.x.x)
Mitel Live Business Gateway 3.2.0.9
Microsoft Lync 2010 4.0.7577.0

There may be additional updates to the original document.

The Mitel LBG will provide the Remote Call Control (RCC) needed to allow those with Mitel phones to use the "Click to Call/Click To Answer" functionality that those who use the Lync client enjoy.

HTH

2
Mitel MiVoice Business/MCD/3300 / Re: Mitel 3300 MCD and Exchange 2010
« on: February 08, 2013, 06:44:44 PM »
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

3
Mitel MiVoice Business/MCD/3300 / Re: Mitel 3300 MCD and Exchange 2010
« on: February 08, 2013, 01:41:36 PM »
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

4
Mitel MiVoice Business/MCD/3300 / Re: Mitel 3300 MCD and Exchange 2010
« on: February 07, 2013, 03:33:49 PM »
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

5
Mitel MiVoice Business/MCD/3300 / Re: Mitel 3300 MCD and Exchange 2010
« on: February 01, 2013, 10:38:28 AM »
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





6
I know that this thread is old, but I had Exchange 2007/2010 Coexistence working until we decommissioned our 2007 UM server recently.   I still have a lot of the configuration documented.  Let me know if I can help.

TS

7
Mitel MiVoice Business/MCD/3300 / Re: Mitel 3300 MCD and Exchange 2010
« on: January 28, 2013, 03:57:36 PM »
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

8
I have followed the guide and I have tried tweaking the form options in the SIP Peer Profile without any luck.  I have done traces from the MS OCS environment, but not from the MCD, do you recommend a specific SIP trace?  The error I receive on the MS OCS side is 486 Busy Here.

9
Update:  While researching this problem, I came across a document that talked about enabling the DPNSS feature called:  EARLY_TX_CHAN_CONN.  Our feature was disabled and after enabling it, 3 party conference calling capabilities went from 0 percent completion to between 33 & 50 percent completion.  This feature also fixed MOH issue between our Mitel Desk phone and MS communicator soft phones.   Definitely a step in the right direction, but still need help bumping up our 3 party call percentage rate.

10
Mitel MiVoice Business/MCD/3300 / OCS 2007R2 - 3 party conference calls
« on: January 13, 2012, 02:08:10 PM »
I have a problem whenever we attempt to place conference calls between two Microsoft Enterprise Voice users (communicator softphone users) and an external number (Cell phone/Landline) the external callee answers the call, but then the callee is immediately dropped.  All other features with our Mitel integration work without any problems.  We are using 10.0.3.30 on our Mitel and our OCS build is OCS 2007 R2 CU6.

11
Thanks for the reply, yes I want the name of the person I am calling to display on my desk phone.  In our case the OCS Enterprise Voice user has a entry in the Mitel Tel Dir, but this name still does not display on my phone when I call them.  The MS KB reference only deals with called made form the OCS environment (which works fine) to the Mitel PBX not the reverse.  Do you have this working in your environment?

12
Thanks for the Reply, but we already have OCS EV user names displaying when they call a Mitel desk phone.  I am looking at from the other direction, where the Mitel desk phone is initiaing the call.  The MS KB only address the OCS EV user initiating the call. 

13
We have deployed OCS 2007 R2 and Exchange UM with our Mitel 3300. When a call is placed from a Mitel Deskphone (SS4015 or SS4025) to an OCS Enterprise Voice user, the OCS Enterprise Voice user's name is not displayed on the Mitel desk phone.  The reverse works fine - OCS Enterprise Voice user calls a Mitel deskphone, OCS user's name appears fine.  Is there any way to associate the OCS EV users name with a name in the Mitel 3300???

14
Mitel MiVoice Business/MCD/3300 / Mitel 3300 and Exchange 2007 UM
« on: January 19, 2010, 05:31:07 PM »
We recently implemented Exchange Unified messaging, but we have one small problem.  When the Exchange UM server answers, the voicemail box greeting has all ready started playing - so usually the name of the person is cut off.  Is there a way to build in a delay or pause before the 3300 reroutes the call to the UM server?

15
After working many hours on this, it turns out not to be a Mitel issue.  Microsoft released a patch to fix this, this is the MS artile on it: http://support.microsoft.com/kb/972721/.  I had the patch installed, but the key to making this work is the XML file that is referrenced in the article.



Pages: [1] 2