What you can see in the logs is that instead of translating my extension to my SIP address, the SfB server is trying to ring at 7089 number which does not resolve at a user and eventually a BYE is being sent back. In this scenario, I dialed to the Auto Attendant during Business Hours and selected option #4 in the menu navigation which supposed to transfer to me to extension 7089 which is my UM extension. Scenario #1: Menu Navigation Enabled During Business Hours Once we were able to reproduce the problem, we decided to take some logging on the Front-End’s to determine why there is a different behavior between typing an extension manually and choosing a menu selection for transfer a call to the exact same extension. Calling to the Auto Attendant on Non-Business hours where Menu Navigation is disabled result in a Voice command instructing you to type the actual extension of the user, once the extension was entered the call was transferred successfully.Setting Enabling Business hours menu navigation with different prompt options which result in Extension transfer stopped working.What was even weirder was the fact the if we switched the Auto Attendant to Off Business Hours when there is no menu navigation but just an option to enter a user extension, it did worked and the call was successfully transferred to the Lync user. On Lync 2013 everything worked as expected and all calls were transferred to the right extension once the business hours menu navigation was on.Īfter upgrading to Skype for Business Server 2015, it turned out that during business hours when the Menu navigation was played, calls were not being transferred to Lync users, but just looping the Exchange auto attendant play message instead. In order to achieve this, we are using the Exchange Online Auto Attendant features which allow you to transfer calls to Lync Users based on the user UM extension and the matching SIP address. In my company we have integration between Exchange Online and Skype for Business Server 2015 On-Premises and one of the management requirements is to have granular Auto Attendant features with Menu navigation.
I’ve recently encountered a problem after upgrading my production environment Skype for Business Server 2015 with normalizing extension numbers coming from the Exchange Online Auto Attendant. Update: Microsoft released CU 1 for Skype for Business which resolve the issue described below:
0 kommentar(er)
