Hello,

We are having the following issue: when our lync users are outside of our network, just connected to their home internet or a public WiFi  and not on VPN, they cannot place calls to other Lync users inside our network. They get a poor network connection message on the call window. But they are able to make calls from Lync to external numbers without a problem.

Inside our network, Lync to Lync calls work perfectly fine, the same for calls from Lync to external numbers.

Does anybody know what could be the cause of our issue? Perhaps I'm missing a setting on our Edge server. What should be the first thing I should check on my Lync servers?

Thanks for any help!

Have you opened up ports on your firewall from your internal clients to the edge on UDP/3478 and TCP/443?  This sounds like you might have a problem there.  Can you internal clients properly route to this subnet and resolve the pool name of your edge pool? 

Ports and protocols poster, check out in A/V section client traffic to edge showing UDP/3478 and TCP/443: http://www.microsoft.com/en-us/download/details.aspx?id=39968 

I do have ports UDP/3478 and TCP/443 open in my firewall for my internal and external users. My internal clients can resolve the pool name of my edge server pool. 

This could be something sitting on clients blocking the traffic. If it's something to do with ports, then you won't get the same treatment for the PSTN calls dialing from outside as the P2P calls. It will ring the PSTN number, but the call won't connect. Check the windows firewall and any antivirus application that installed on the client PCs.

 

I figured out what was going on. My internal clients were not able to communicate with my Edge server's internal NIC. This was due to the internal NIC on the Edge server not having a default gateway set (only the external NIC has a default gateway). I fixed the problem my adding an IP route for my internal cllient's subnet on the Edge server. 

Thanks everyone for your help and advice!

• Marked as answer by Rarakane 14 hours 34 minutes ago

I figured out what was going on. My internal clients were not able to communicate with my Edge server's internal NIC. This was due to the internal NIC on the Edge server not having a default gateway set (only the external NIC has a default gateway). I fixed the problem my adding an IP route for my internal cllient's subnet on the Edge server. 

Thanks everyone for your help and advice!

• Marked as answer by Rarakane Monday, March 30, 2015 4:48 PM

I figured out what was going on. My internal clients were not able to communicate with my Edge server's internal NIC. This was due to the internal NIC on the Edge server not having a default gateway set (only the external NIC has a default gateway). I fixed the problem my adding an IP route for my internal cllient's subnet on the Edge server. 

Thanks everyone for your help and advice!

• Marked as answer by Rarakane Monday, March 30, 2015 4:48 PM

I figured out what was going on. My internal clients were not able to communicate with my Edge server's internal NIC. This was due to the internal NIC on the Edge server not having a default gateway set (only the external NIC has a default gateway). I fixed the problem my adding an IP route for my internal cllient's subnet on the Edge server. 

Thanks everyone for your help and advice!

• Marked as answer by Rarakane Monday, March 30, 2015 4:48 PM