none
Unable to integrate on-premises Lync 2010 to Office 365 hosted UM RRS feed

  • Question

  • Hello everyone

    I am looking for a solution to make our voicemail working again after the recent move to Office 365.  We have a fully functional Lync environment with edge  server and it is connected to a couple of analogue PSTN lines using an audiocodes MP-118 Gateway. We don't have a PABX system. I was able to integrate this setup to the on-premises exchange UM. We recently migrated our exchange mailboxes to O365 and I followed the procedure to integrate on-premises lync to Hosted UM but no luck. I think the 'Outlook Voice Access" number is causing the issue. Since we don't have a PABX I am not sure what number I should use for Outlook Voice Access.  I was using a fake number in the on-premises setup. Can anyone please help me to resolve this issue or suggest a workaround?

    Thanks

    MS



    • Edited by MS-Tech-001 Thursday, January 15, 2015 5:33 AM
    Thursday, January 15, 2015 5:27 AM

All replies

  • Hi,

    Naturally if you use a fake number then you won't be able to call your Subscriber Access number from the PSTN. A common mistake when configuring hosted UM with on premises Lync is not matching the 'routing number' in your hosted UM dial plan to the number of your Subscriber Access contact object on premises - these two numbers should be the same. Typically the number used for this is a spare number on your DDI range. You can use a fake number if you desire, it wont be accessible externally, but is required to map the hosted UM service to a contact object down in Lync.

    You mention that you had previously used on premises UM without issue, you should ensure that the legacy contacts objects and configuration for this has been removed to ensure it doesn't impact your new hosted configuration.

    If you can point me to the guide that you followed, I might be able to identify anything that's missing from the process.

    Additionally, what is the error that Lync reports, and have you been able to look at a client side trace with snooper?

    Kind regards
    Ben


    Note: If you find a post informative, please mark it so using the arrow to the left. If it answers a question you've asked, please mark the thread as answered to aid others when they're looking for solutions to similar problems or queries.

    Lync | Skype | Blog: Gecko-Studio

    Friday, January 16, 2015 1:38 PM
  • Thanks for the reply Ben. I did clean-up all legacy contact objects.  I mainly followed  this doc:

    http://www.lynclog.com/2012/02/lync-2010-on-prem-cloud-um-integration.html

    When I call voice mail from Lync client I get "Call failed due to network issues"

    I tried both client side and server side logs but couldn't establish what is causing the issue.

    • Edited by MS-Tech-001 Wednesday, January 21, 2015 3:16 AM
    Wednesday, January 21, 2015 3:04 AM
  • Hi MS,

    I've had similar issues when moving voicemail to 365 using a "fake" number (i.e. +666 as opposed to an externally accessible one) - dialling the short number doesn't work. However pressing and holding 1 on the Lync dial pad does connect to voicemail. Not sure if this will work for you or whether it answers your question but may be another piece in the puzzle...

    Cheers

    Jon

    Wednesday, January 28, 2015 2:52 PM