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!

Compression licenses on vMCD 1

Status
Not open for further replies.

Billz66

Technical User
Feb 21, 2010
2,078
AU
Am I correct in assuming that there is never a requirement for a compression license when using a vmcd ?

( note this is a vmcd with sip trunks and ip handsets only - no clustering to any physical controllers)

If I never did anything I'd never done before , I'd never do anything.....
 
Bill,

I think you are right, if everything is IP (Users and Trunks) there shouldn't be the need of adding compression licenses to the vMCD. Compression will be made by changing zones.

Have a look at the latest vMCD Eng. Guidlines for further information on Compression.

However.... if you look at the Eng. Guidelines for vMCD Rel. 4.2 (Page 20 "Licensing") it says that P/N 54000650 3300 ICP: 8 Compression licenses, is an optional license for vMCD.

I've never been able to understand why they were offering compression licenses for vMCD, there's no E2T...

Regards,

Daniel

 
vMCD still provides paging, MOH and conferencing so those calls will terminate on the vMCD and will require compression licenses if you want those legs to be compressed. No different than the physical servers.

@dan, there is no 'E2T' but there is a 'B2E', which is the equivalent and is used for the above functions.
 
B2E stands for 'Buffer to Ethernet' and is the equivalent to an E2T (Ethernet to TDM) conceptually. You'll see 'B2E' in some of the software logs when using the MCD-ISS or MiCD. When you see that, think E2T.

The job of the E2T is to take the ethernet packets and strip out the raw data an put it on the TDM bus, the B2E does the same, but instead of a TDM bus, there is a series of data buffers that get passed around, simulating that TDM bus. Same goes for the reverse direction.

The important thing to note from the original question is that for MCD-ISS, MiCD or vMCD, there are still some types of calls that can terminate on the MCD depending on your programming. If you use it for one of those functions, then you'll need compression licenses to ensure that those legs of the calls are compressed. Conversely, you would never required T38 licenses on one of those systems since a fax call would never terminate on the MCD.
 
so basically if i dont care about MOH , RADS or embedded vmail calls , everything else can be compressed without the use of a lisense.



If I never did anything I'd never done before , I'd never do anything.....
 
...or paging and conferencing, then yes.

If you have a narrow link between your sets and your controller, then you may still want them as even something like a transfer will cause a short 'burst' of uncompressed music from the controller to the set. If you have enough of these at the same time, it can cause quality problems. There are also some scenarios with SIP trunks that require some tones to be played out from the controller, but again, just bursts. Something you'll have to figure out and see if it's worth the gamble.

Also note that a music key and MOH use the same resources, so if you have people that like to listen to the music on their phones, then take that into account.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top