Your voice media packets should be strict priority queued, and the signalling packets should be in a separate class with bandwidth assigned. Media packet marking of EF is correct, and signalling is IP precedence 3 (cs3), though AF31 is still used by older code versions.
What brand of phones and servers are you using? Cisco gear will mark the packets correctly, so you can bypass the ingress policy map, and just match on DSCP for your egress map. If your equipment does not mark then you are on the right track, but just need to separate media and signalling, as well as defining a strict priority queue.
I did a quick browse to the Altigen web site, but didn't turn up any QOS info. After you determine the markings Altigen uses you can then set up the appropriate class maps to match on the DSCP or IP Precedence used. One for the media (voice)packets, and one for signalling (call setup).
Priority 7500 is kb/s, or 7.5mb/s. How much of the 1.5mb are you planning on using for voice? You need about 100 kb per call for G711 uncompressed calls. If you want to allow 8 calls use priority 800, and the signal class should be about 32.
Will there also be data traffic? Hopefully there is some Call Admission Control that will limit the number of calls that can be placed. They may also support RSVP which is another way of approaching QOS. RSVP is supported by Cisco, but requires different configuration.
Please use the pulldown menu to rate useful posts.
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...