#3 – Port 5062 was not opened between the Edge server and FE / SBA servers The Edge server for this environment was recently moved with the internal interface’s IP address was changed and since the server is not joined to the domain, the internal DNS A record which servers such as the front-end server uses to reach the Edge server was not updated. #2 – The DNS record of the Edge server’s internal interface was not correct The Edge server’s external interface IPs were all NAT-ed but the topology for the environment did not have the external IP address configured: #1 – A/V Edge service NAT was not configured While this type of issue can be caused by many reasons, this environment I had to troubleshoot the issue in had 3 contributing misconfigurations:
Using the Skype for Business client would show the call in the Connecting call… status then disconnect: A user would be able to successfully authenticate as well as see the call come in but when they pick up with their handset, they would not hear any audio and the call would disconnect within 10 seconds. I was recently asked by a client to troubleshoot an issue with their Lync Server 2013 environment where users connecting remotely via the Edge server are unable to establish voice calls.
0 kommentar(er)
