[Solved] Call failed due to network issue Microsoft lync when bothendpoints are internal
While working on Microsoft Lync I have faced "Call failed due to network issue" while making audio/video calls to the users. In my environment I have successfully implemented Lync for IM, audio video conference, Auto Attend, voice mail. But calling was the issue in different scenarios.
I was not able to able to make calls due to " call failed due network issue" in below scenario,
1. if user is connected Lync from home via Internet and other user is in office network
I was able to make calls if,
1. If I connected to the Office network via Remote Access VPN & other users is in office network
2. If both user are connected to Lync server via internet through Lync edge server.
But call fails if both users in the different network i.e. in office or at home
In my network we have five location & user logs in to the Lync server from different five location via site 2 site vpn or from home via Internet.
Below are the network details of five offices,
Server Network - 192.168.1.0/24
Office 1 - 192.168.1.2/24
Office 2 - 192.168.3.0/24
Office 3 - 192.168.4.0/24
Office 4 - 192.168.5.0/24
Office 5 - 192.168.6.0/24
My Microsoft Lync front end server is in the 192.168.1.0/24 network along with my archiving, monitoring, SQL Server & Edge server Internal facing network card.
TO resolve you have to add routes for your internal network on your Lync Edge server,
My Edge server IP's are
1. Internal
192.168.1.10 Mask 255.255.255.0
No gateway
DNS - Internal DNS server
2. External Facing Network
IP - 10.10.12.10 Mask 255.255.255.0
Gateway - 10.10.12.1
DNS - 4.2.2.2 & 8.8.8.8
My gateway for Internal network traffic for my Edge server is (192.168.1.0/24) is 192.168.1.1 so that it can communicate with the Lync front end server. Same way you need add routes for your other network i.e. offices on your edge server as shown below,
Open Command Prompt on Edge Server & add routes
route add -p 192.168.1.0 mask 255.255.255.0 192.168.1.1
route add -p 192.168.2.0 mask 255.255.255.0 192.168.1.1
route add -p 192.168.3.0 mask 255.255.255.0 192.168.1.1
route add -p 192.168.4.0 mask 255.255.255.0 192.168.1.1
route add -p 192.168.5.0 mask 255.255.255.0 192.168.1.1
Gateway will be the same for all other network traffic. Once you add persistent route restart Edge server & try to make calls.
I was not able to able to make calls due to " call failed due network issue" in below scenario,
1. if user is connected Lync from home via Internet and other user is in office network
I was able to make calls if,
1. If I connected to the Office network via Remote Access VPN & other users is in office network
2. If both user are connected to Lync server via internet through Lync edge server.
But call fails if both users in the different network i.e. in office or at home
In my network we have five location & user logs in to the Lync server from different five location via site 2 site vpn or from home via Internet.
Below are the network details of five offices,
Server Network - 192.168.1.0/24
Office 1 - 192.168.1.2/24
Office 2 - 192.168.3.0/24
Office 3 - 192.168.4.0/24
Office 4 - 192.168.5.0/24
Office 5 - 192.168.6.0/24
My Microsoft Lync front end server is in the 192.168.1.0/24 network along with my archiving, monitoring, SQL Server & Edge server Internal facing network card.
TO resolve you have to add routes for your internal network on your Lync Edge server,
My Edge server IP's are
1. Internal
192.168.1.10 Mask 255.255.255.0
No gateway
DNS - Internal DNS server
2. External Facing Network
IP - 10.10.12.10 Mask 255.255.255.0
Gateway - 10.10.12.1
DNS - 4.2.2.2 & 8.8.8.8
My gateway for Internal network traffic for my Edge server is (192.168.1.0/24) is 192.168.1.1 so that it can communicate with the Lync front end server. Same way you need add routes for your other network i.e. offices on your edge server as shown below,
Open Command Prompt on Edge Server & add routes
route add -p 192.168.1.0 mask 255.255.255.0 192.168.1.1
route add -p 192.168.2.0 mask 255.255.255.0 192.168.1.1
route add -p 192.168.3.0 mask 255.255.255.0 192.168.1.1
route add -p 192.168.4.0 mask 255.255.255.0 192.168.1.1
route add -p 192.168.5.0 mask 255.255.255.0 192.168.1.1
Gateway will be the same for all other network traffic. Once you add persistent route restart Edge server & try to make calls.
