Article ID: 2693118 - View products that this article applies to.
When you dial in to a Skype for Business Online (formerly Lync Online) meeting, you may receive one of the following error messages:
To resolve this issue, use one of the following methods, as appropriate for your situation.
Resolution 1Check the following DNS record:
_sip._tls.domainIn this record, the placeholder domain represents the name of your destination server. This record is necessary to guide the ACP's servers to the correct destination server. Without this record, the ACP's server can't find the correct destination, and the user is put on hold indefinitely.
This record should be configured as follows:
For more information about how to configure the necessary DNS records for Skype for Business Online, go to the following Microsoft websites:
Record Type: SRV Record name: _sip Protocol: _tls Weight: 1 Priority: 100 Port: 443 Destination Host: sipdir.online.lync.com
(http://community.office365.com/en-us/w/lync/ensuring-your-network-works-with-lync-online.aspx): Ensuring your network works with Skype for Business Online
(https://support.microsoft.com/kb/2566790/ )Troubleshooting Skype for Business Online DNS configuration issues in Office 365
Resolution 2Verify the formatting of the telephone numbers that are found in the user’s Skype for Business Online settings. To do this, follow these steps:
Configure dial-in conferencing
Set up dial-in conferencing so people can join meetings by phone
Resolution 3Wait for the conference organizer to unlock the conference, or have the organizer add the user to the conference through the Lync client.
Resolution 4Make sure that the meeting organizer’s Skype for Business Online account and the ACP account are configured in the same geographic region. For example, if your Office 365 organization is based in North America, you must use an ACP account that's configured for North America and can't use an ACP account that's configured for the United Kingdom. You can contact your ACP to verify that your account was created in the appropriate region.
This issue may occur if one of the following conditions is true:
Still need help? Go to the Office 365 Community
Article ID: 2693118 - Last Review: April 30, 2015 - Revision: 13.0