Even with this config, I can't see how it is possible.
You only have 2 ports at the branch, so if those ports are busy and attempt to set up a third would be rejected by the branch router, regardless of where the call cam from. The call set up is less than 0.5kb so there is no way this is causing the problem.
That will stop the 0.5kB of call controll traversing the wan links.
If you are you using CM in the HO you would use locations for call admission controll only allowing two g.729 calls for each location /region.
If you are using a h.323 gw you could set max-con on the dial-peers to two therfor only 2 calls could be made to each location.One dial-peer for each loaction with the correct dial-plan 111X 112X 113X etc etc.
Sure it might take some time but it works.
From my eperience LLQ works well.
You could turn on cRTP and reduce the BW even more to around 12kbps or pehaps up the sampling rate to 30 or 40ms =25pkts per second around 24k with cRTP for less overhead and processing on the router though this probably isnt required their just ideas for you.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...