09 Sep Microsoft Teams and Skype for Business Audio Conferencing known issues
Audio Conferencing that Microsoft uses as the audio-conferencing provider has current issues that are being tracked and actively investigated and will be potentially resolved when the feature is updated in future releases of Office 365.
For now, use this as a reference when you are troubleshooting potential issues with getting Audio Conferencing set up and working for the people using the Skype for Business or Microsoft Teams apps in your organization.
Microsoft Teams known issues:
| Issue | Behavior/Symptoms | Known workaround |
|---|---|---|
| PSTN callers with the same “From” number are shown as the same user in meeting roster. | When multiple PSTN callers join a meeting, and their caller IDs are masked as a single number, they will show up as a single caller in the meeting roster. | No workaround. |
| Meeting Info panel is not showing up intermittently. | Meeting Info panel may not show in Teams client when users are trying to look up for conference bridge phone numbers or conference ID. | Look at meeting details or Outlook calendar to view conference bridge phone numbers or conference ID. |
| Meeting invites from Outlook Add-in show garbage characters in PSTN coordinates for non-US locales. | When scheduling private meetings using Outlook Add-in for Microsoft Teams on a computer with non-US locales, PSTN coordinates may contain garbage characters. | No workaround. |
| Dial out needs to use 5 digits or more. | Users trying to dial out from a meeting need to type in 5 or more digits, even though dial plan normalization rule is available to normalize short digit dialing to E.164. | Dial out by typing the full DID number or local number format instead of internal extension number. |
| Dial out control is not showing up intermittently. | Dial out control may not be visible from the Meeting Info panel. | No workaround. |
| Static conference ID not supported for Microsoft Teams meetings. | If the admin overrides the default setting from dynamic conference ID to static conference ID, this setting doesn’t take effect for Microsoft Teams meetings. | No workaround. |
| PSTN meeting coordinates are no available for Skype for Business on-premises users | If the user is a Skype for Business on-premises user, assigned with Skype for Business Online, Audio Conferencing, and Teams licenses, all meetings scheduled using Teams will not include PSTN meeting coordinates. | No workaround. |
Skype for Business Known issues:
Issue: Entry and exit notifications are turned on when a meeting starts, but they’re turned off shortly after the meeting starts.
Behavior/Symptoms: By default, entry and exit notifications are disabled for meetings where participants join from both Skype for Business apps and when they dial in. You can enable the announcements in the Skype Meeting Options in the Skype for Business app. 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 app, the notifications will be turned off. When turned off, the notifications can be enabled back using Skype Meeting Options in the Skype for Business app.
Currently there is not workaround for this issue.
Issue: If a user is provisioned the first time by being assigned an E5 license, it might be possible for the Audio-Conferencing welcome email to not be delivered to the user if the mailbox isn’t enabled.
Behavior/Symptoms: If this happens, you can always resend the audio-conferencing information of the user using Audio conferencing in the Skype for Business admin center or using PowerShell. See Enable or disable sending emails when Audio Conferencing settings change.
Note: In order to resend the audio-conferencing PIN to the user, the PIN has to be reset. This can also be done by using Audio conferencing in the Skype for Business admin center or by using PowerShell.
Currently there is not workaround for this issue
Issue: Audio conferencing calls could take up to 24 hours to show in the usage reports.
Behavior/Symptoms: We’re looking forward to making improvements on this area in future service updates.
Currently there is not workaround for this issue
Issue: When a caller dials in to 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 app stating that the user is waiting in the lobby.
Behavior/Symptoms: This is currently by design, but we’ve taken the feedback in regard to supporting this capability in future service updates.
Currently there is not workaround for this issue.
Issue: PSTN meeting coordinates are not available for Skype for Business on-premises users
Behavior/Symptoms: If the user is a Skype for Business on-premises user, assigned with Skype for Business Online, Audio Conferencing, and Teams licenses, all meetings scheduled using Teams will not include PSTN meeting coordinates.
Currently there is not workaround for this issue.
Thank you.
Sorry, the comment form is closed at this time.