How to Enable Attendees from other Organizations to join your Lync Meetings using their own Lync Client
This guide explains how to help other organizations attendees (guests) to join your Lync Meeting conferences using their Lync client application.
- You must have a hosted Lync 2013 account with Sherweb.
- Your guests must have the Lync service (on-premise or hosted) running for their organization, with the Lync 2010 or 2013 client software installed on their PCs.
Creating the “sip” DNS record
1. The organization from which the guest users are joining the Lync Meeting conference should have a specific SRV record created in its DNS zone.
For example, the domain example.com would need the following record:
_sip._tls.example.com SRV service location:
priority = 0
weight = 0
port = 443
svr hostname = sip.mylync2013.com
Note: the creation procedure depends on the server used.
Joining the Lync Meeting with Lync client
2. When the guest user from the other organization clicks on the web link to join the Lync Meeting on a PC running Lync client, he or she will be prompted to accept the certificate for sip.mylync2013.com. The user should click on Connect to ensure the communications are encrypted.
3. Depending on the Lync Meeting settings, the guest may be admitted to a virtual lobby to wait for the meeting organizer to let him or her in.
a. If the requested DNS record is not present, the guest attempting to access the meeting from a computer where the Lync Client is installed sees the following error:
Cannot sign in the Lync Attendee because of a problem connecting to the server. Reference error ID 102 (source ID 238)
b. The guest still has the option to use the Lync Web App by copy-pasting the Lync Meeting URL to a web browser address bar and suffixing it with ?SL=1 . This will force the system to use the browser instead of the Lync client.
All Lync 2013 accounts