Dial-in conferencing troubleshooting and known issues

This article is for customers who are using Microsoft as their dial-in conferencing provider. It does not apply to customers who are using a third-party audio conferencing provider (ACP).

Dial-in conferencing using Microsoft as the dial-in conferencing provider is a new feature for Skype for Business Online. There are current issues that are being tracked, actively investigated and will be potentially resolved when the feature is updated in future builds in Office 365 and Skype for Business Online.

For now, use this as a reference when you are troubleshooting potential issues with getting dial-in conferencing set up and working for the people in your organization.

Troubleshoot dial-in conferencing

The following table lists some of the common issues you might come across and their solutions.

Issue

Solution

Entry and exit notifications are turned on when a meeting starts but they’re turned off shortly after the meeting starts.

By default, entry and exit notifications are disabled for meetings where participants join from both Skype for Business clients and when they dial in. You can enable the announcements in the Skype Meeting Options in the Skype for Business client. For a meeting where all participants dial in and join a meeting, entry and exit notifications are enabled by default as the participant roster isn't available to any participant. When a meeting has started with only participants calling in, the entry and exit notifications will be turned on, but when a participant joins using a Skype for Business client, the notifications will be turned off. When turned off, the notifications can be enabled back using Skype Meeting Options in the Skype for Business client.

During back-to-back meetings or when you’ve scheduled two meetings at the same time, sometimes you might see an “!UNINVITED!” meeting attendee on the meeting participants list.

This indicates that it might be possible for participants from the previous meeting to be present in your current meeting or that participants from both meetings have been mixed. This is likely to happen because a previous meeting wasn’t ended using the End Meeting option. The presence of this participant in the roster doesn’t fully guarantee that the mentioned participants are indeed in the current meeting. To prevent this from happening end the previous meeting using the End Meeting option or you can remove the uninvited attendee from the list in the new meeting. See End or exist a Skype for Business meeting.

You can use Dynamic conference IDs to prevent this from happening but they aren't available to users that are using a third-party audio conferencing provider.

Caution: This also applies to users that use a third-party audio conferencing provider.

If a user is provisioned the first time by being assigned an E5 license, it might be possible for the dial-in conferencing welcome email to not be delivered to the user's if the mailbox isn't enabled.

If this happens, you can always resend the dial-in conferencing information of the user using Dial-in conferencing in the Skype for Business admin center or using PowerShell. See Enable or disable sending emails when dial-in conferencing settings change.

Note: In order to resend the dial-in conferencing PIN to the user, the PIN has to be reset. This can also be done by using the Dial-in conferencing in the Skype for Business admin center or using PowerShell.

The following is the list of known issues for dial-in conferencing.

Known issue

Comments

Joining a meeting from one device and transferring the call to a second device will leave the first device connected to the meeting.

When a user has joined a meeting from one device, for example a laptop then transfers the call that is connected to the meeting to another device, for example a mobile phone, the transfer succeeds, but the first device remains connected to the meeting instead of being disconnected once the transfer is complete. We are investigating this issue and are actively finding a solution. Once we find the solution, the fix will be included in a future Office 365 service update.

Dial-in conferencing calls could take up to 24 hours to show in the usage reports.

We’re looking forward to make improvements on this area in future service updates.

If a dial-in meeting is scheduled from Outlook web app, the Find a local number and Forgot your dial-in PIN? links aren't available and don't work.

The Find a local number page for a user can be accessed by clicking on the link of any other meeting that was scheduled in the Outlook desktop client or by manually entering it in a browser with the following format: https://dialin.lync.com/<domain of the tenant>/<user alias>, i.e. https://dialin.lync.com/contoso.com/useralias

We are investigating this issue and are actively finding a solution. Once we find the solution, the fix will be included in a future Office 365 service update.

When a caller dials into a conference bridge after the meeting has been locked by a Skype for Business user, there isn't a notification in the Skype for Business client stating that the user is waiting in the lobby.

This is currently by design, but we’ve taken the feedback in regard to supporting this capability in future service updates.

See Also

Set up dial-in or PSTN conferencing for Skype for Business

Share Facebook Facebook Twitter Twitter Email Email

Was this information helpful?

Great! Any other feedback?

How can we improve it?

Thank you for your feedback!

×