Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

MCD 4.2 Compression?

Status
Not open for further replies.
Oct 13, 2011
2
US
I recently installed a clustered 4.2 system. We used one Mxe III and five Cxi II's as survivable gateways. I have the correct licensing in place for compression, but do not completely understand how it is implemented or functions. While researching some different topics I have seen some references to zones and compression. I did not create any zones when building my cluster.

Any Explanation of MCD and Compression Would Help
 
Have you checked the online help as this does explain in detail the compression zones
basically if you use anything other than zone 1 then compression is enabled you will need to math the zone number on the other controller(s) and route accordingly

Share what you know - Learn what you don't
 
The general idea is that traffic between different Zones are compressed, and one of the reasons this is not done, compression licences are used for every TDM call across Zones. 8 Licenses is 8 active calls, every call above 8 will go back to G711.
 
As other have said compression zones are setup. You have compression in side a zone or on calls between zones. IP sets themselves handle the compression which I believe doesn't require any licensing. The compression licenses within the controller are for when the 3300 controller needs to do the compression ie. a call in/out on a PRI or from a TDM set to an IP set in a compressed zone. In general when you put compression licenses on the controller you need to also add a DSP module to do the compression. However there are times when enough DSP resources are available to cover the needs of the compression licenses ( ie adding more compression licenses to a system that has them ).

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.
 
Zones are setup to emulate physical boundaries. So if you have two IP phones physically isolated on the network, then you may want to put them in their own zone, and enable compression between that zone and any other zone. That would mean that when a call is made to/from one of those phones, compression will be the preferred codec.

As for licensing. The IP phones carry their own, so calls between them can be compressed (based on the zones) and they will not count against your system compression licenses. The compression licenses that you purchase (and require the system DSP support to use) are for any IP calls who's leg _terminates_ on the controller. The controller is defaulted to Zone 0 (or is it 1?), regardless it's the first zone. Depending on the zoning rules you have setup, compression is applied based on those rules, just like if an IP to IP phone call was being made.

I say "who's leg terminates" because it's not isolated to PRI/TDM trunks, it also applies to IP phone legs into a conference, an IP phone using MOH, or a group page. Any case where an IP device is streaming to the controller.

Hope that helps.
 
simply put, you need compression licenses on all MCD controllers where IP phones will have some sort of TDM function during use.

Clearly you wouldn't assign compression licenses to a controller that will only ever do conferencing and has all IP phones geopgrahically local or not across a WAN. If you had remote phones though I'd suggest adding DSP and compression to the controller.

Hope this helps
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top