Archive for the ‘Media Resources’ Category

MoH Scenarios

Posted: August 12, 2006 by cciestudy in Media Resources

A. Unicast G711 everywhere

1. Create region for MoH. G711 with all other regions.

2. Do not enable multicast in audio source, server, MRG

3. Enable only G711 in service parameter (Default)

B. G711 multicast everywhere

1. Create region for MoH. G711 with all other regions.

2. Enable multicast in audio source, server, MRG. Set hop count to 5.

3. Enable only G711 in service parameter (Default)
4. Enable multicast in infrastructure (igmp snooping in switches, pim sparse-dense in routers)

C. G711 multicast everywhere, remote site uses MoH from local SRST flash

1. Create region for MoH. G711 with all other regions.

2. Enable multicast in audio source, server, MRG. Set hop count to 1.

3. Enable only G711 in service parameter (Default)
4. Enable multicast in HQ and Remote LAN infrastructure (igmp snooping in switches, pim sparse-dense in routers), Disable multicast in WAN infrastructure.

5. Enable SRST MOH feature from flash.

6. Enable loopback interface in SRST router for PSTN users to hear MoH.

D. G711 multicast at HQ, G711 unicast at Remote

1. Create region for MoH. G711 with all other regions.

2. Enable multicast in audio source, server, MRG. Set hop count to 1.

3. Enable only G711 in service parameter (Default)
4. Enable multicast in HQ and Remote LAN infrastructure (igmp snooping in switches, pim sparse-dense in routers), Disable multicast in WAN infrastructure.

5. Create two MRG, one with multicast enabled for HQ and one with no mulitcast for BR1.

E. G711 unicast at HQ site, G729 unicast at remote

1. Enable Service parameter for G711 and G729

2. Use the HQ device pool for MOH server (assuming HQ device pool uses g729 for remote)

3. Do not enable multicast

F. G711 multicast at HQ, g729 multicast at remote

1. Enable Service parameter for G711 and G729

2. Use the HQ device pool for MOH server (assuming HQ device pool uses g729 for remote)

3. Enable multicast in audio source, server, MRG

4. Enable multicast in infrastructure

G. g729 unicast at remote using transcode

1. Enable only G711 in service parameter

2. Put MoH server in HQ device pool (assuming HQ uses G729 for remote)

3. Add a transcoder to MRGL of MoH server

I. HQ uses G711 multicast, remote uses G729 unicast, all PSTN uses hear tone on hold

1. Use HQ device pool for MoH server

2. Enable multicast on Audio source and server.

3. Create 2 MRG, one with multicast, one without multicast

4. Enable g711 and g729 in the service parameter

5. Create a third MRG and MRGL with no MOH and apply that directly to gateways

Advertisements

MoH server using Trancoder

Posted: August 12, 2006 by cciestudy in Media Resources

If the remote device does not support the codec of the MOH stream, then MOH server can trigger a transcoder. You would need to configure a MRGL with transcoder resource in the MoH servers device pool. In this case, CCM does not use the trancoder of the remote device. It will only use the transcoder of MOH server.

MRGL for gateways

Posted: July 15, 2006 by sankar in Media Resources

Make sure you always specify MRGLs for Gateways. They dont default to the device pool to get the MRGL. (unlike phones, where if you set the MRGL to none, they default to the device pool)

MoH Folders

Posted: June 27, 2006 by cciestudy in Media Resources

1. Folder to drop new audio files

C:\Program Files\Cisco\MOH\DropMOHAudioSourceFilesHere

2. Folder were all converted music files are stored

C:\Program Files\Cisco\TFTPPath\MOH

3. After you add the music on hold audio stream in Callmanager admin, it will move the audio files to

C:\Program Files\Cisco\TFTPPath and

C:\Program Files\Cisco\MOH

MOH settings for Multicast

Posted: June 17, 2006 by sankar in Media Resources

a. Enable Multicast on audio source (Play cont. also)

b. Enable Multicast on MOH audio server, Increment by ip address rather than port, set hops to greater than number of hops required to reach the phone.

c. Enable Multicast on MRG group.

d. To receive g729 MOH, set service parameter in IP Voice media service and add g729 annex A setting

e. Enable these commands on the following equipment

  i. Wan routers :

           ip multicast-routing

           int fa0/0.2

           ip pim sparse-dense-mode

    ii. 6500 switch – enable igmp (main site)

             set igmp enable

    iii. 3550 switch (remote site)

             ip igmp snooping vlan <voicevlan>

Software Conference

Posted: June 17, 2006 by cciestudy in Media Resources

As per this link

http://www.cisco.com/en/US/partner/products/sw/voicesw/ps556/products_configuration_example09186a0080114c64.shtml 
Software conference devices only support G.711 codecs. Cisco CallManager 4.0 and later also support G.729 codecs. Still, the default codec is G.711. However, if the Meet-Me conference is initiated by a phone that has a G.711 codec, G.729 devices are not able to join the meeting unless there is a transcoder involved. A transcoder is needed to handle the translation from one codec to the other one. A similar issue arises with Ad-Hoc conferences. If the phone that initiates the conference tries to include a phone with a different codec, it fails. An error message is displayed on the traces. Hardware conference devices can provide transcoding for G.711, G.729, and G.723 codecs.

This did not work in the lab. After changing the region to use G729 and trying to do a conference, getting a fast busy. Also event viewer is reporting the error

Error: MtpNoMoreResourcesAvailable – No more MTP resources available.
App ID: Cisco CallManager
Cluster ID: StandAloneCluster
Node ID: 10.1.1.1

NM-HDV transcoding and conferencing

Posted: June 11, 2006 by sankar in Media Resources

* NM-hdv has 5 PVDM SIMM slots

* Each pvdm has 3 dsps

* Each dsp can handle 4 calls (g729,g711)

* Each dsp can handle 4 transcoding sessions (g729,g711)

* If using GSM, each dsp can handle 3 transcoding sessions

* Each dsp can handle 1 conference session.

* max capacity for transcoding (g729,g711) on a NM-HDV is (4 per DSP) * 3 DSPs per SIMM * 5 SIMMs per module = 60 sessions.

* max capacity for conferencing on a NM-HDV is (1 per DSP) * 3 DSPs per SIMM * 5 SIMMs per module = 15 sessions.