locked
Skype for Business 2019 and Exchange Server 2016 - auto attendants not working RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    We recently upgraded from Skype for Business 2015 to Skype for Business 2019.  The new 2019 pool was created and we migrated users across.

    Everything works perfectly, apart from Exchange 2016 subscriber access and auto attendants.

    As soon as we move the Exchange UM Contacts to the new pool (Move-CsExUmContact) the calls fail to the auto attendants and subscriber access numbers.  Move them back to the 2015 pool and they work again.

    We currently have everything running on Skype for Business 2019, except for the Exchange UM Contacts.  Mediation server, Edge server, all users, common area phones, analogues device etc etc are all on 2019.

    All other Exchange integrations, including missed call notifications and voicemail, work fine even with Skype for Business 2015 removed from our topology.  Exchange is configured - UMIPGateways, Dialplans etc for the new 2019 pool

    We running the latest CU's on all products, and all updates installed.

    Has anyone got auto attendants working with Skype for Business 2019 and Exchange 2016?

    Any suggestions on possible solutions/things to check?

    Thanks!


    • Edited by DJL Friday, May 17, 2019 7:34 PM
    Friday, May 17, 2019 7:34 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi DJL,

    Please refer to this KB:

    https://support.microsoft.com/en-us/help/4480742/call-failures-and-500-server-internal-error-after-migration-to-2019

    I did some internal research, and it seems a Skype for Business 2019 server issue even if a fresh installation, I’m afraid currently the workaround is using “Move-CsExUmContact” to move the objects to an earlier supported server as the KB said. 

    Hope it would be fixed in the next CU.

    Thanks for your understanding.

    Best Regards,
    Shaw Lu

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    • Marked as answer by DJL Monday, May 20, 2019 4:55 PM
    Monday, May 20, 2019 1:38 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi DJL,

    Please refer to this KB:

    https://support.microsoft.com/en-us/help/4480742/call-failures-and-500-server-internal-error-after-migration-to-2019

    I did some internal research, and it seems a Skype for Business 2019 server issue even if a fresh installation, I’m afraid currently the workaround is using “Move-CsExUmContact” to move the objects to an earlier supported server as the KB said. 

    Hope it would be fixed in the next CU.

    Thanks for your understanding.

    Best Regards,
    Shaw Lu

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    • Marked as answer by DJL Monday, May 20, 2019 4:55 PM
    Monday, May 20, 2019 1:38 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks Shaw Lu, much appreciated.

    Good to know Microsoft are aware of the issue and it's not just us

    Monday, May 20, 2019 4:55 PM