Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3118
  • Last Modified:

External Lync clients can't join meetings - get kicked out with "You have left the call"

My users connecting remotely (ie. from home) from their Lync clients installed on their PC are unable to join any meetings.  It tries to connect, but then gives the status "You have left the call."

Internally (ie. in the office) it works fine. Additionally, the Lync Web App clients also works fine, internally and externally.

Some details on my enviroment:

Edge - Lync 2013

Front End Pools - one 2010 Enterprise (albeit one server), one 2013 Enterprise (two servers)

A standalone Lync 2010 A/V server exists as well.

Meet and dialup records internally point to 2010 pool. Externally, they point to 2013 access edge.

SRV records on external DNS are _sip._tls 443 and _sipfederationtls._tcp 5061, both point to access edge.

SRV records on internal DNS are _sipinternaltls._tcp 5061 to sip (which is an "A" record with IP for 2013 FE pool), and _sip._tls 5061 to access (which is an "A" record with the internal IP of the edge server).

Any thoughts on how to troubleshoot this would be most appreciated. Thanks.

Ron Piecyk
*****Email Removed - MIT 1-29-14****
0
ronpiecyk
Asked:
ronpiecyk
  • 3
  • 2
1 Solution
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Do you have a load balancer?

Jeff
TechSoEasy
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Also, check out this forum post for troubleshooting steps:
http://rdsrc.us/twHrF4

Jeff
TechSoEasy
0
 
ronpiecykAuthor Commented:
Thanks Jeff. No load balancer, not using NAT - interfaces are directly on the internet (have public IPs assigned to them), firewall is Windows firewall and all required ports opened.
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Then it's time to start logging:
http://technet.microsoft.com/en-us/library/gg558599.aspx

Jeff
TechSoEasy
0
 
ronpiecykAuthor Commented:
Problem resolved. Wound up being that my external DNS records for A/V edge and Web Conferencing edge did not match what was in the topology (IP addresses were incorrect). Simple.

Thanks all for the input.
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now