Hi Lachlan Follett,
Did this issue occur when you schedule meeting using OWA?
If this issue didn’t occur when you schedule meeting using OWA, we suggest you update Office 2016 to the latest, then check if the issue persists.
If this issue also occur in OWA, run the following command to check dial in conferencing access number and scope it to the contact object’s registrar pool:
Run Get-CsDialInConferencingAccessNumber ,then using the identity above I ran: Set-CsDialInConferencingAccessNumber –Identity <Existing Dialing Conf> –ScopeToSite
Then please also check if there are any event IDs in SFB FE server application log.
Hope this reply is helpful to you.
Regards,
Alice Wang
Please remember to
mark the replies as an answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact
tnmff@microsoft.com.