Benefits from multiple Callmanagers in a multi-site network?
I am administering a multi-site environment connected via VPN. Currently, the remote site depends on a single Callmanager at the main site. The PRI is also located at the main site. This means that all of the call processing and paths for the remote site come across the VPN to the single Callmanager. The remote site suffers, at time, from terrible reliability and quality issues.
Would placing a secondary Callmanager at the remote site improve their reliability and quality issues? I'm not sure if it will because the calls are still at the mercy of the VPN and PRI being hosted at the main site. I've implemented voice VLAN's and QoS on both sides of the VPN, but that hasn't seemed to help. Our main site has multiple T1 connections with all of the traffic load balanced across them. This being the case, our provider says there is no way to reserve bandwidth for the VPN because of our T1 implemenatation. The provider adds that with this configuration there's no way to dictate which T1 the call packets will travel in on. Our option would be to reconfigure our data setup.
I would appreciate any input on this, especially on adding the secondary call processor at the remote site. My boss believes that just by adding this that there qualtity and reliability will improve.
These are the paths to get to each CCX logs through CLI. They may be helpful if you are having issues accessing RTMT or downloading logs through it.
If you want to download them you have to prefix "file get " and you can add one of the options (re...