We have CAC enabled (Cloud Topology) all our subnets are associated with network site ID, edge’s public IPs are also assigned with Network ID and bandwidth policy.
All internal calls and outgoing federated calls are ok, however incoming federated call are breaking with following message: “Could not complete the call because the network is busy”.
Monitoring server is showing insufficient Bandwidth Diagnostic ID 5 for calls that failed.
PDP logs not showing much:
TL_VERBOSE(TF_DIAG) 36E0.3728::01/31/2011-17:12:17.712.000155e2 (PDP,RelayConn.SetLocalLocalAction:protocol.cs(80))(00000000037A9C05)Local Relay Failed!
TL_VERBOSE(TF_DIAG) 36E0.3728::01/31/2011-17:12:17.712.000155e3 (PDP,RelayConn.SetLocalLocalAction:protocol.cs(95))(00000000037A9C05)Local-Local action: FAIL!
Thanks for any help!!!
Have you installed at Minimum the CU4, because MS has fixed some CAC issues with at least CU4. If the IP Internal and External from the Edge, is not in the Network site configuration, you will have Problems with external users. It depend also, where the user homed central site, branch office. So you have to configure CAC for enough bandwidth form edge to
the other users or server, also to the Mediation server. You can prove your Settings also with the CAC reports on the Monitoring server.
regards Holger Technical Specialist UC
- 편집됨 Holger Bunkradt 2012년 3월 18일 일요일 오후 2:09
I know this thread is a little old, but I had the same problem and what fixed it for me was enabling the alternate audio and alternate video path options under the region settings. This then allowed media calls from the internet to complete correctly instead of getting the network is busy message.