asked on Lync 2013 Integration with Exchange 2010 (Unified Messaging)
Hello,
We are in the process of deploying and testing Lync 2013 in our environment. We have it set up and working in that IM is working, internal and external calls are working, etc. We still need to get Voicemail and Auto-attendants working, which I gather requires the use of Exchange. Our Exchange server is 2010 (SP3 RU 9) and doesn't have UM configured at all. Almost all articles I can find involve integrating 2013 to 2013 or 2010 to 2010. Is there a how-to for how to configure UM and have it work between Exchange 2010 and Lync 2013?
The best I could find was this but he already had Lync 2010 up and going, which meant he already had UM going as well. Need to be able to configure from scratch: http://blog.montopolis.com/2013/02/08/exchange-2010-um-integration-with-lync-2013/
We are in the process of deploying and testing Lync 2013 in our environment. We have it set up and working in that IM is working, internal and external calls are working, etc. We still need to get Voicemail and Auto-attendants working, which I gather requires the use of Exchange. Our Exchange server is 2010 (SP3 RU 9) and doesn't have UM configured at all. Almost all articles I can find involve integrating 2013 to 2013 or 2010 to 2010. Is there a how-to for how to configure UM and have it work between Exchange 2010 and Lync 2013?
The best I could find was this but he already had Lync 2010 up and going, which meant he already had UM going as well. Need to be able to configure from scratch: http://blog.montopolis.com/2013/02/08/exchange-2010-um-integration-with-lync-2013/
ExchangeMicrosoft ApplicationsMicrosoft Server Apps
Last Comment
street9009
ASKER
Yes, I saw those articles as well. The first step (https://technet.microsoft.com/en-us/library/gg398106.aspx) describes a utility that's only available in Exchange 2013.
Sorry? Which utility?
exchucutil.ps1 has been around since 2007... and the mention of 2013 is only relevant as it handles UM completely differently to EX2010, as you no longer have a UM server.
I'd take the time to read through it all and you''ll see it's all you should need to get setup...
exchucutil.ps1 has been around since 2007... and the mention of 2013 is only relevant as it handles UM completely differently to EX2010, as you no longer have a UM server.
I'd take the time to read through it all and you''ll see it's all you should need to get setup...
ASKER
I did manage to get UM set up on the Exchange server with help from another article. But, like most Microsoft articles, I can't follow these for how to get it working with Lync.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
This one was better: blog.schertz.name/2010/11/
ASKER
It's all set up, but almost none of it is working. When I first dialed our Auto Attendent, it would ask for me to speak a name or dial an extension. The name always failed so I tried to dial an extension. It attempts but ultimately also fails. I now have it configured to only let you dial an extension and when you attempt that, it says "The call cannot be transferred. Returning to main menu." twice before silence.
Voicemail also won't call my phone to let me record a message, either. When I click "Call the Play on Phone number to play or record a greeting for this call answering rule...", if I accept the default value ("user@domain") it just appears to time out. If I dial my extension, I get "The number cannot be dialed because it does not comply with the policy of your organization".
I've read to disable REFER support for the first problem and to check the "Enable dialing of extensions" (or similar) for the second but neither worked.
Voicemail also won't call my phone to let me record a message, either. When I click "Call the Play on Phone number to play or record a greeting for this call answering rule...", if I accept the default value ("user@domain") it just appears to time out. If I dial my extension, I get "The number cannot be dialed because it does not comply with the policy of your organization".
I've read to disable REFER support for the first problem and to check the "Enable dialing of extensions" (or similar) for the second but neither worked.
Can you confirm the configuration of your dial plan please?
ASKER
General: Allow users to configure call answering rules is checked, VoIP security is Secured.
Subscriber access tab: Defaults are selected (two phone numbers are added here).
Dial Codes: 1 in the country/region code. Rest are blank.
Features: Allow callers to transfer to users and to send voice messages are checked. Callers can contact users within this dial plan. Matched name selection method is None.
Dialing Restrictions: Allow calls to users within the same dial plan and allow calls to extensions are checked.
Dialing Rule Groups: Blank
Settings:
I think that's everything.
Subscriber access tab: Defaults are selected (two phone numbers are added here).
Dial Codes: 1 in the country/region code. Rest are blank.
Features: Allow callers to transfer to users and to send voice messages are checked. Callers can contact users within this dial plan. Matched name selection method is None.
Dialing Restrictions: Allow calls to users within the same dial plan and allow calls to extensions are checked.
Dialing Rule Groups: Blank
Settings:
Dial by name primary method: First Last
Dial by name secondary method: Last First
Audio codec: MP3
Operator extension: blank
Logon failures before disconnect: 3
Maximum call duration: 120
Maximum recording duration: 20
Recording idle time-out: 5
Input failures before disconnect: 3
Default language: English (US)
I think that's everything.
Does your Number of digits in caller extension match your PBX solution?
ASKER
Our extensions are 3 digits, yes. We have Lync set up so that if you dial 390 on a phone, it translates to me. That does work.
https://technet.microsoft.com/en-us/library/gg398193.aspx