Hi all,

We are in a coexisting mode With Lync server 2010 and 2013.For now i have moved my user to the New Lync 2013 servers.Sign in from internal and external network Works fine,but strugling With Meeting.

I created NEW Meeting to internal and external domain users,but when external/internal users click on the meeting link they only get up Lobby and waiting to be admit in.From my side i cannot see users in the lobby.

It should be working by default,but this somehow fails,any ideas?

t

Hi Off2work,

Please try using Meet Now and check if you can see these users in lobby.

I found a similar case, looks like you are experiencing the same symptom.

https://social.technet.microsoft.com/Forums/office/en-US/feb1ecf2-e5a8-4e2b-890d-54cde37d96f3/scheduled-meeting-and-participants-stuck-in-lobby?forum=lyncconferencing

In addition, you can try to modify the meeting options as the following screenshot and check if the users can join the meeting or verify if the Lync conferencing service is available.

 

Best regards,

Eric

Have Have now tested by creating a new tester user in the new pool and meeting has same issue.Now both can sign in,but when any one of us sends message it doesnt appear for the other.Also when try to share screen or other application,the sharing part gets An error occurred during the screen presentation.Both are logged in from Internal network.Same issue if both try to login from external network.Any ideas on how to troubleshoot further?

Also when i og into Meeting options,change settings and choose remember settings i get error as shown below:

Hi Eric and thanks for reply.

When using meet now i get a server error occured.Please contact Your support system.

When i try to change Meeting options i get error as Attached in previews Message.

did you adjust your meet url's at all when you deployed Lync 2013?  Please investigate your DNS for the meet URL's.  Curious if it is related to that ... something is screwy with scheduling.  At the least..

• Edited by Greg Seeber 14 hours 55 minutes ago

HI Greg and thanks for reply,

meet,dialin is still ponting to legacy(2010 servers) .This is working fine for users in Lync 2010 environment.Its when moved to 2013 servers this problem occures.

did you adjust your meet url's at all when you deployed Lync 2013?  Please investigate your DNS for the meet URL's.  Curious if it is related to that ... something is screwy with scheduling.  At the least..

• Edited by Greg Seeber Tuesday, March 24, 2015 4:26 PM

did you adjust your meet url's at all when you deployed Lync 2013?  Please investigate your DNS for the meet URL's.  Curious if it is related to that ... something is screwy with scheduling.  At the least..

• Edited by Greg Seeber Tuesday, March 24, 2015 4:26 PM

Hi all,

have now noticed one thing and it is that when i run get-csconferencedirectory i get the following info:

My Research tells me that Backcompatsite-userservices-1 could be the one causing the issue,since it this was used in OCS 2007(We had 2007 and 2010 coexistence at one time).

It is safe to delete this ServiceID or is it used by 2010 and 2013 environment?As far as i can see both environment are using their own conferencedirectory ID.

Thanks!

No one can help me With this? :(

So we made the decision and removed Backcompat site ID,restarted front end,web Conference services on all FE server.Voila it worked!

Case closed