none
Multiple Lync Servers connecting to one o365 tenancy RRS feed

  • Question

  • Here is the design,

    We have a Lync 2010 enterprise pool in our head office which currently provides our users with voicemail off of our own Exchange 2010 server, we also have remote offices deployed with standard edition Lync 2010 servers whose users get their voicemail off of our Exchange server in our head office as well.

    Here is where the problem starts, we are currently migrating our exchange enviroment to Office 365, In doing that we have successfully configured some test users in our head office with their voicemail being hosted by the o365 enviroment (Yaaay!!).  Now we are trying to test some users in our remote offices, however they are registered to the standard edition front end server in their offices, we follow the exact same procedures as we did to the users in the head office and the voicemail is not working. 

    As a test we registered the user to the enterprise pool in our main office and everything started to work fine, the only part of the settings which seem to be related to the registrar server were the Exchange UM contact so I created a new contact on the registrar server for that location and assigned the number from this new contact to the UM Dial plan on our o365 tenancy.  I also ensured that I added this Exchange UM contact to our Hosted voicemail policy as we had to do with the original contact.

    Here is the error I am seeing when I look at the logging on this error..

    15007; reason="Exchange Unified
    Messaging server did not respond to request"; source="OurServer.OurCompany.com";
    dialplan="Hosted__exap.um.outlook.com__OurCompany.onmicrosoft.com";
    umserver="exap.um.outlook.com"; appName="ExumRouting"

    Hopefully somebody out there has some ideas on this!

    Thanks,

    Thursday, July 25, 2013 10:12 PM

All replies

  • Hi,there

    Would you please verify if you create the Exchange UM dial plan work with TLS?You need to configure it with  Transport TLS and Port 5061.

    Regards,

    Sharon


    ××××××××××××××××××××××××××××××××××××××××××××××××××××××××××××××××××××××× Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question.

    Friday, July 26, 2013 9:31 AM
    Moderator
  • Here is the error I am seeing when I look at the logging on this error..

    15007; reason="Exchange Unified
    Messaging server did not respond to request"; source="OurServer.OurCompany.com";
    dialplan="Hosted__exap.um.outlook.com__OurCompany.onmicrosoft.com";
    umserver="exap.um.outlook.com"; appName="ExumRouting"

    Hopefully somebody out there has some ideas on this!

    Thanks,

    Does federation properly work for the STD edition servers in the branch offices?

    Do the branch servers have their own edge servers? 

    Can branch FE servers resolve and reach internal edge interface(s) of the edge pool designated for federation?

    Can the edge servers resolve and reach STD edition servers (on port 5061) in branch offices?


    • Edited by Adminiuga Friday, July 26, 2013 1:12 PM quote trim
    Friday, July 26, 2013 1:12 PM
  • @ Sharon - As I mentioned all we do is move the user from one Registrar server to the other.  The Exchange UM dial plan does not change.

    @Adminiuga -

    1. I will have to find somebody to test this with as it has never been tested

    2. No, they rely on the one Edge pool

    3. Yes

    4. Yes

    Friday, July 26, 2013 3:48 PM
  • Just thought I would bring this back to the top to see if anybody has any input..
    Tuesday, October 1, 2013 11:54 PM