Even though the SfB client will allow the user select this join method, it will produce a generic error as shown here: If this holds true for you, the best solution is user awareness, and fortunately once they click on the “Call me at” option (radio button), they will see a choice of numbers as shown here:Īnother challenge with this feature is that if the end-user is not configured on the back-end server (Lync Server 2013 used here), the end-user experience is confusing. I have yet to determine if this is a SfB system configuration but I have seen it in the field several times. This screen shot shows one of the first sources of confusion – the “Call me at” drop-down box of numbers appears blank: When the user launches a Skype meeting, they are presented with some options to join the audio portion of the meeting as shown below. This could be their cell phone, desk phone, or any manually specified phone number – provided the user is enabled for it, and as the Enterprise Voice feature set has been deployed. participants) to join the audio portion of the call by having the SfB server call out to whatever number the user specifies. In Microsoft Skype for Business (SfB) and Lync, it allows end-users joining a SfB conference call (i.e. If you are not familiar with it, the ability to join a conference using the “Call me at” option it is a powerful communication feature. In this post I will address that question and some common end-user challenges with using this feature.

What configuration does a Lync user require to be enabled for the ‘Call me at’ conference feature?

A scenario I have come across several times and usually forget the answer to is:

Skype for business conference settings