This is the Q&A from "Technical Services Virtual Boot Camp - CUCM Media Resources - Transcoder, MTP OOB, In- Band DTMF & MoH and Trace Snippets, Session 5".
A: MOH is unicast by default. Unless the Multicast Checkbox is checked at all three places which is MRG/AUDIO source/ MOH server.
A: Where ever we use supplementary services such as hold resume etc G711ulaw and mitigating DTMF mismatches as well. MTP are of three types primarily:
A: There is no third party MOH server which is supported. We cannot add another MOH server in call manager. If you are referring to the flash streaming MOH, then that is configured by configuring telephony service and uses the AFWB process on the IOS.
A: The MRGL on the DEVICE POOL and the PHONE if have different contents, get merged together and call manager process of Media resources lookup list consolidates it together, in the hierarchy of device to device pool approach . This is similar to a consolidation of partitions happens when line and device CSS are different. here the lookup list for the MEDIA manager consolidates in that way.
A: Yes that is correct, the default would be used once all is exhausted, consider this as a accumulation of three MRGL device > device pool > default list.
A: ANN is not always used in ringbacks, but when you get announcements like " your call cannot be completed as dialed" etc and areas where ringback or reorder tone needs to be generated, there is when the ann gets invoked. it needs to be in any mrg.
A ringback most of the times gets played by the flash memory of the phone itself. the SCCP message to the phone which the CUCM sends instructs it s to play the ringback rather than invoking ringback always from ANN.
A: We need to understand that bitrate(region setting) is different than Bandwidth ( locations setting). What region setting only tells that the maximum which is supported is g711ulaw. Next come in the setting of audio codec preference list introduced in later version which can govern that if available on either side which codec is preferred.
A: There are various pointers which govern which codec would be used. There is even a service parameter which is the default inter and intra-region codec which comes into play incase there is no specific audio bitrate selected between the two test regions.
A: USER A shares the audio source ID and the MRG/MRGL on phone B selects the MOH server to stream the MOH provided the file exists on its server‑ and there can be various situations where this behaviour would change and depends on case to case scenario‑.
A: Two endpoints whose region settings of bit rate specifically set to g729 would govern only the maximum bit rate allowed as g729, but thats not it. Each endpoints also specifies the codec it supports, and these media caps shared with Media Exchange layer ‑then decides whether or not there is a codec mismatch and invoke any codec mismatch mitigating device accordingly.‑ Also do not that the audio codec preference list also plays a huge part in negotiating a codec in a pool of matching caps‑ if you are familiar with the concept of SETS, its the intersection of the capabilities of the two endpoints and that forms pool of matching codec‑.
A: this document highlights in details of a custom MOH to upload:
A: Any file which conforms to the requirement of above document can be used as a MOH audio: source.http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/8_5_1/ccmfeat/fsmoh.html#wp1105626
A: NO they are not both same. A hardware MTP supports a single codec and mitigates packetization. however A Transcoder is of two types primary. One of the type is regular transcoder which is G711ulaw to any codec conversion other is universal transcoder which is any codec to any codec and needs PVDM3 explicitly.‑
A: Same flavour of G729 with different packetization can be mitigated through hardware MTP‑.
A: It depends if its a PVDMX64 PVDMX32 etc. its best to use the DSP calculator added later in the slides.
A: Not at all. MTP usages was shared in one the slides, we can touch the MTP slide again if requested. There are a host of reasons why a MTP is required. ‑To summarize, supplementary services(hold-transfer-conf initiation, dtmf mismatches, faststart, earlyoffer(depends), etc‑.
A: You are absolutely correct. between CUCM and UCCX the relaying of the DTMF is always OOB and is a JTAPI message.
A: An analog phone VG224 supports inband and out of band pulse of 8-12 pps.
A: Payload type does not have anything to do with the type of digit pressed.
A: The tool is notepad ++ its a freeware.
A: Tool alternatives are Jedit, wingrep, translator x.
A: Having MGCP and h323 on the same gateways is not supported, however it is possible to have a gateway with E1's/T1's, and also have a ITSP. but again its not a supported environment. Also to add to it a common misconception about cube is that its only sip, basically when both inbound and outbound dial-peers are voip its more of a cube arrangement and it can have h323 on both ends and you would be having a ITSP.
A: This is not the microsoft notepad, it's a tool used not just by tac but also programmers to code better and is a freeware.
A: Any media resource (ANN, MOH, MTP,) which is not in any MRG is part of the default list.
A: This is not supported. A Single Voice gateway which has the MGCP process running, you would be expected to bind the MGCP interface. Think about having a single media/signalling interface catering to two different ccm-managers .can that be possible? not quite. The best way to get a deep dive on this is is understanding MGCP though the Cisco Voice and Gatekeepers book which covers how exactly a MGCP gateway registers.