Response Group Phones Delay When Edge Server is Enabled
I had an interesting problem today. The client had existing Lync setup and Edge server ready to go. I’m not sure who set it up, but I was told that this was going to be an easy job. Well, it was not that easy…..
As soon as I turned on the Edge server at one of my client’s office, receptionist complained that she started having delays when she picks up the phone.
Later, I found out that she was not the only one with this problem. The problem was with the people who were part of the Response Group.
I found many complaints about this on the Internet, but it seems that nobody had a solution for this issue. People are saying that this is a problem and Microsoft knows about this. Well, I was not happy about this and I did not know how to say to the owner that the receptionist and the others would have to work with this delay, so I kept digging.
Firewall is turned off, no antivirus or antispyware program running. I found somewhere on the Internet that I had to turn off Web Proxy Filter for the TCP 443 traffic. When I checked it, it was not enabled.
Long search pointed me to the Edge server. The server was setup correctly. At some point, I was checking the routes and noticed something that could be a problem.
This company had multiple subnets, but the route in Edge server was done only for their server’s subnet.
This is the setup:
192.168.1.0 – Servers
192.168.2.0 – Desktops
172.16.1.0 – DMZ
The persistent route was setup:
When I tried to ping 192.168.1.111
When I try to ping 192.168.2.111
Everything looks good. After that, I decided to run tracert command
This is the tracert for 192.168.1.111
But look what happened when I run tracert for 192.168.2.111
As you can see, the 192.168.2.0 network is going to the DMZ interface instead of the LAN interface.
I added the route of 192.168.2.0 and tested again.
Trace route is okay now. After that I tested the phones and everything worked great. There were no more delays.
The conclusion is that Lync Edge server has to have routes for all internal subnets.Follow @ikravchenko