Microsoft claims to be going “mobile first, cloud first,” so you might think that using mobile phones with their telephony system would be a priority.
You make your request and get a new certificate back and believe. It works, but it’s like talking to someone on the moon. Scenario: Its time to replace your Skype for Business certificates on your Front End Pools because they are expiring or you have encountered new requirements for your certificates. However, while this is good enough for features like persistent chat (which also isn’t implemented on the mobile clients, and with the advent of Microsoft Teams, probably never will be), the latency from your phone to the RDP server to the Skype servers to your caller and back is just too much for voice.
#WHAT IS MY SKYPE FOR BUSINESS CALL IN NUMBER ANDROID#
The only thing I’ve gotten to work so far is using Skype for Business as a published RemoteApp in the Microsoft Remote Desktop client for either Android or iOS. Knowing that answering Skype for Business calls on Android phones or iPhones is impossible also might lead one to ask, “Well, if I can’t do it that way, is there a workaround?” It doesn’t work because Microsoft hasn’t implemented that feature (yet?). While this begs some questions (like why do response group calls ring on mobile clients if you know you can’t answer them), hopefully this post will prevent you wasting any more time trying to figure out why this doesn’t work. The official fix is to use the desktop version of the app.
At the time of this blog post, Microsoft doesn’t actually support response groups on mobile clients. A call will ring in on the mobile client, but when you try to answer it, you get no audio. If your organization uses Skype for Business response groups, you may have noticed something weird if you also use the Skype for Business mobile Android or iOS clients.