Posts

Showing posts from October, 2016

Summary of CUCM Supported Codecs

I just thought to put a summary list of CUCM supported codecs


G.711: It has two versions, A-Law & Mu-Law. You can disable CUCM support for G711 using the service parameter G.711 mu-law Codec Enabled or G.711 a-law Codec EnabledG.722: This is wideband codec that is always preferred by CUCM over G.711, unless Advertise G.722 Codec enterprise parameter is Disabled.
Enterprise Parameter Setting Phone (Product-Specific) Parameter Setting Phone Advertises G.722 Advertise G.722 Codec Enabled Use System Default Yes Advertise G.722 Codec Enabled Enabled Yes Advertise G.722 Codec Enabled Disabled No Advertise G.722 Codec Disabled Use System Default No Advertise G.722 Codec Disabled Enabled Yes Advertise G.722 Codec Disabled Disabled No
When users use a headset that supports wideband, they can enable Wideband Headset feature from the phone settings for better quality. On the phone navigate to Settings > User Preferences > Audio…

MoH Combined with other Media Resources

As we mentioned earlier MOH uses G711 is the only supported codec by default (other codecs can be enabled from IPVMS service parameters). Let’s assume the following scenario, HQ-Region (which contains HQ-Phones, HQ-Servers, HQ-MediaResources) and BR1-Region (which contains BR1-Phones, BR1-MediaResources). In case HQ-Region to BR1-Region codec definition is G729 (and vice versa) and MOH Server at HQ site should be used by BR1-Phones, then how MOH will work?? NOTE: Here we are assuming that BR1 Phones are registered with HQ CUCM, i.e. no trunks are available between sites. The simple way is to enable G729 codec for MOH Server from IPVMS service parameters. The other way is through XCODER. When MoH is invoked CUCM will realize that MOH is using G711 while the inter-region configuration should use G729. Therefore, it will invoke XCODE based on MoH MRGL. MOH MRGL can be assigned to MOH Device Pool; else MOH will pick XCODE from the null group. NOTE: When CUCM invoke MOH, new call negotiat…

Inter-Cluster Music on Hold (MoH)

Image
You need to enable the network infrastructure to support multicasting including multicast routing and PIM MMoH can't be transcoded, doesn't support E-LCAC/RSVP and doesn't support MTP MMoH isn't supported on ICT video calls
The concept of Intercluster MoH is similar to Intracluster MoH. The same two steps:
Stop the current media streamStart new stream with MoH server
In the scenario of ICT, the holder phone will select the source audio file, while SIP/H323 trunk will select the MoH server. Therefore, we will always have the holdee phone and MoH server in two separate clusters.
Stop the Current Media Stream
To disable the current media stream in SIP protocol, an SDP INVITE message is sent from the holder cluster with C=IN IP4 0.0.0.0 and a=inactive. The holdee cluster will respond with 200OK including a=inactive. This is always Early Offer regardless of the trunk configuration