Issue publishing Lync using UAG
-
Monday, September 10, 2012 11:41 PM
Have a VERY simple scenario here that simply refuses to work, wondering if anyone has seen similar behavior.
Internally lync is accesible using Lync.contoso.com
UAG is configured to publish lync as "Lync.contoso.com"
I have configured a trunk to be used ONLY for publishing Lync. The trunk has it's own hostname but this name is not being used. I have configured the trunk and then published lync using the wizard. Pretty straightforward stuff.
When user connects to a meeting through UAG externally, the user joins the meeting and when admited my the organizer the user is dropped after a 4-5 second delay. No error, no warning and the external user never gets lync presence. Internally everything works correctly. Additionally, if connected using a VPN and connecting to the meeting as an anonymous user it works internally. Clearly it appears something is going on with UAG but I can not track it down. Anyone else seen this behavior?
Steve Angell - IAM Practice Director http://www.InfraScience.com)
All Replies
-
Wednesday, September 12, 2012 10:48 AM
Just to very you configured things correctly. The Lync Web Services role on your internal Lync Front-end Server (pool) should listen on port 8080 en 8443. So in fact, make sure that port 80 and 443 on the ouside internet is being forwarded to 8080 and 8443 for the apporpiate URL's. Also check whether you have configured the simple URL's correctly.
Boudewijn Plomp, BPMi Infrastructure & Security
- Edited by Boudewijn Plomp Wednesday, September 12, 2012 11:19 AM
-
Wednesday, September 12, 2012 9:33 PM
Thank you for your response Boudewijn,
Yes, I do understand the ports and have successfully published with TMG many times, in this instance the customer has purchased UAG and wants to utilize UAG. When connecting to a meeting anonymously they are connected and placed in the lobby. It isn't until the moderator admits them that they are dropped completely. If you are the external user, you join the meeting, are admitted to the meeting and you can see other participants but you are never able to hear or talk to participants. Then after a few seconds the external user is dropped from the call.
Regards,
Steve Angell - IAM Practice Director http://www.InfraScience.com)

