Issues with some people connecting to external Lync conference
-
jueves, 28 de junio de 2012 5:37
hi all, we recently rolled out Lync and so far things have been pretty smooth. One issue we came across was an external company hosted a Lync Online Meeting and at least 30-40 people from our company connected to this Lync Online Meeting. We are running Lync Enterprise Edition and running CU5 updates (have all the Lync server updates but haven't applied the CU6-June 2012 updates)
It seem that the first 30 or so people could connect to the meeting with no issues but all sudden more people from our company tried to join and they couldn't join the external meeting. people getting the error: "An error occured during the online meeting. When contacting your support team, reference error ID 403 (source ID 239)." I looked at the Lync Client log and put it into Snooper and I see SIP 403 Forbidden error (see graphic)...I see error:
ms-diagnostics
: 1027;reason="Cannot route this type of SIP request to or from federated partners";source
The host left the meeting up so I can do some testing....the meeting has been over for a few days and I still get this error.
On our end, we have Open Federation (we allow anyone to federate with us). There is another weekyl meeting I have with an external company and I'm able to connect via Online Meeting just fine.
I cannot figure out why some users got in and some people couldn't...The other company says everything was fine and our company was the only one having issues (not sure if that was true or not but that is what I've been told). Any ideas why some people could connect and some people could not?
Todas las respuestas
-
jueves, 28 de junio de 2012 6:12
Hi,
Are you sure the users who are getting the 403 Forbidden have been enabled for federation?
Get-CsUser "username" | ft samaccountname,externalaccesspolicy
Thanks,
JamesMCITP: Lync/Exchange 2010/Server Administrator 2008
rogersau.blogspot.com < Unified Comms Blog
-
jueves, 28 de junio de 2012 14:47
thanks for the response Rogersau,
when I run that command, the people are set for Allow Federation+Public+Outside Access. I had two people test by connecting to another external company web link and it worked fine (they had ExternalAccessPolicy = Allow Federation+Public+Outside Access). One concern i had (although I couldn't find anything yet) that could a external site limit the number of connections from a particular company? For example, I know in a conference - you can set the number of max participates in a conference but I was wondering if there is some other setting that may thorttle the number of connections between two sites...just a thought.
-
viernes, 29 de junio de 2012 12:09Moderador
Yes, just as you said. You can double check the maximum meeting size with your partner.
And make sure the domain federation is enabled and configured correctly for the individual user.
In addition, Lync introduces a Meeting Lobby for all your meetings. Depending on how the organizer has set up the meeting, you’ll be able to either join the meeting immediately or wait in the lobby until a meeting presenter admits you. You can be admitted only by a presenter or an organizer.
Please also note, the meeting organizers control whether participants can present during a meeting. Each meeting can be set up to limit presenters to any one of the following:
- Organizer only Only the meeting organizer can present.
- People from my company All internal users can present.
- Everyone including people outside my company (there are no restrictions) Everyone who joins the meeting can present.
- People I choose The meeting organizer specifies which users can present by adding them to a list of presenters.
Noya Lau
TechNet Community Support
- Propuesto como respuesta Noya LauModerator jueves, 05 de julio de 2012 13:06
- Marcado como respuesta clay28 sábado, 07 de julio de 2012 5:17
-
viernes, 10 de agosto de 2012 3:51
I just want to let you know we had the company setup another conference and it worked fine. I never was able to get down to the root cause of the issue..I'm pretty sure it wasn't on our side.
- Marcado como respuesta clay28 viernes, 10 de agosto de 2012 3:52

