Transcoder Configuration

Mi a New Transcoder

2Q EiQd/Lis.t.Transm{ie.rs

Transcoder: New

States; Ready

T:raiÈ|codar Type MAC fettress* Description Dévies Pool' Spécial toad Inforinatton f * isdisaîss requireri item

Click Insert.

jOssco Madta Terminaison pDsrrtHofdware |001 D7B0D1011

(Leave blank to use defauS)

A window similar to this appears.

A window similar to this appears.

SadiJttÄMMJiatßiadaii

Dependency Records

Transcoder Configuration

SadiJttÄMMJiatßiadaii

Dependency Records

Transcoder; MTP00107BP010Î.1 (MTPQQ107BOQ1011) Registration: Unknown IP Address:

Statu?: Insert somplrtsd

Transeottsr Typ» MAC Aeldrsss*

|00107B0D1011

Cisco Media Termination Paint Hardware

Description

Device Pool*

Special Load Information

Derail«

3 (View datais) (Laave blank to use defaul :)

Note: In the Transcoder Configuration window the Registration status is Unknown. The Registration status needs to read Ready. You need to troubleshoot this.

Click the Reset button in order to ensure that the Transcoder is reset.

Once the Cisco CallManager server has finished resetting the device, it is registered on the switch.

Verify that the port is configured for transcoding and display any active transcoding sessions with the show port voice active <mod_num/port_num> transcode command.

AV-foO'i-l (enable) show port \oioc ¡iclivc 5'2 transcode

Another method of verification that the port is properly configured is by using the show port <mod_num/port_num> command.

In this case the port type is listed as MTP. It can also perform transcoding. \V-h?lW-l (enable) show port 5,2

I'oil Vmie Mains \ l.m Duplex Speed l_\pe

Verify

en.ihled M full -MTP

You can now make calls between phones that use different codecs. You are also able to use additional phone services that require an MTP from the WS-X6608 such as call holding, call transfer, and call park.

Music On-Hold

The integrated Music On Hold (MOH) feature allows users to place on-net and off-net users on hold with music that is streamed from a streaming source. The Music On Hold feature allows two types of hold:

• Network hold, which includes transfer hold, conference hold, and call park hold Cisco CallManager supports two types of MoH transport mechanisms:

Unicast MoH consists of streams sent directly from the MoH server to the endpoint requesting an MoH audio stream. A unicast MoH stream is a point-to-point one-way audio Real-Time Transport Protocol (RTP) stream between the server and the endpoint device. Unicast music on hold uses a separate source stream for each user or connection. As more endpoint devices go on hold via a user or network event, the number of MoH streams increases. Thus, if twenty devices are on hold, then twenty streams of RTP traffic are generated over the network between the server and these endpoint devices.

Multicast MoH consists of streams sent from the MoH server to a multicast group IP address that endpoints requesting an MoH audio stream can join as needed. A multicast MoH stream is a point-to-multipoint one-way audio RTP stream between the MoH server and the multicast group IP address. Multicast music on hold conserves system resources and bandwidth because it enables multiple users to use the same audio source stream to provide music on hold. Thus, if twenty devices are on hold, then potentially only a single stream of RTP traffic is generated over the network.

The MoH feature requires the use of a server that is part of a Cisco CallManager cluster. You can configure the MoH server in either of the following ways:

Coresident deployment ,

In a coresident deployment, the MoH feature runs on any server (either publisher or subscriber) in the cluster that is also running the Cisco CallManager software. Because MoH shares server resources with Cisco CallManager in a coresident configuration, this type of configuration drastically reduces the number of simultaneous streams that an MoH server can send.

Standalone deployment

A standalone deployment places the MoH feature on a dedicated server within the Cisco CallManager cluster. The sole function of this dedicated server is to send MoH streams to devices within the network. A standalone deployment allows for the maximum number of streams from a single MoH server.

You can set up the source for MoH in any of the following ways:

• MoH from an audio file on the Cisco CallManager or MoH server

• Unicast MoH from an audio file

• Multicast MoH from an audio file

• MoH from a fixed music source (via sound card)

• Unicast MoH from a fixed source

• Multicast MoH from a fixed source

MoH can be generated from an audio file stored on the MoH server. Audio files must be in one of the following formats:

• G.711 A-law or mu-law (recorded at a sampling rate of 8 KHz)

You can create these files with the Cisco MoH Audio Translator service, which transcodes and formats audio source files (such as .wav or ,mp3 files) into the appropriate MoH source file for the specified codec type(s). The MoH server requests these files based on the audio sources configured and loads them into memory during initialization or when the audio sources are requested. When an MoH event occurs, the configured audio source file is streamed to the requesting device on hold.

Basic MoH

The basic operation of MoH in a Cisco IP Telephony environment consists of a holder and holdee. The holder is the endpoint user or network application placing a call on hold, and the holdee is the endpoint user or device placed on hold.

The MoH stream that an endpoint receives is determined by a combination of the User Hold MoH Audio Source of the device placing the endpoint on hold (holder) and the configured media resource group list (MRGL) of the endpoint placed on hold (holdee). The User Hold MoH Audio Source configured for the holder determines the audio file that will be streamed when the holder puts a call on hold, and the holdee's configured MRGL indicates the resource or server from which the holdee will receive the MoH stream.

Basic MoH and MoH Call Flows

In simplest terms, the holder's configuration determines which audio file to play, and the holdee's configuration determines which resource or server will play that file. As illustrated by the example below, if phones A and B are on a call and phone B (holder) places phone A (holdee) on hold, phone A will hear the MoH audio source configured for phone B (Audio-source2). However, phone A will receive this MoH audio stream from the MRGL (resource or server) configured for phone A (MRGL A).

BR1 SITE HQ SITE

BR1 SITE HQ SITE

BR1 MRG HQ MRG

IOS Conf 6608 Conf

IOS XCODER 6608 XCODER

MOH Server MOH Server

BR1 MRG HQ MRG

IOS Conf 6608 Conf

IOS XCODER 6608 XCODER

MOH Server MOH Server

BR1 MRGL HQ MRGL

BR1 MRG HQ MRG

HQ MRG BR1 MRG

Because the configured MRGL determines the server from which a unicast-only device will receive the MoH stream, you must configure unicast-only devices with an MRGL that points to a unicast MoH resource or media resource group (MRG). Likewise, a device capable of multicast should be configured with an MRGL that points to a multicast MRG.

MoH Configuration Settings

You can configure the settings for MRGLs and User and Network Hold Audio Sources in several places within Cisco CallManager Administration, and you can configure different (and potentially conflicting) settings in each place. To determine which User and Network Audio Source configuration setting to apply in a particular case, Cisco CallManager interprets these settings for the holder device in the following priority order:

• Directory or line setting (Devices with no line definition, such as gateways, do not have this level.)

• Device setting

• Device pool setting

• Cluster-wide default setting

When attempting to determine the audio source for a particular holder, Cisco CallManager first looks at the User Audio Source configured at the directory or line level. If this level is not defined, then Cisco CallManager looks at the User Audio Source configured on the holder device. If this level is not defined, then Cisco CallManager looks at the User Audio Source configured for the device pool of the holder device. If this level is not defined, then Cisco CallManager looks at the cluster-wide default audio source ID configured under the Cisco CallManager system parameters. (By default, this audio source ID is set to 1, which is the SampleAudioSource.) Cisco CallManager also interprets the MRGL configuration settings of the holdee device in the following priority order:

• Device setting

• Device pool setting

• System default MoH resources

When attempting to determine the MRGL for a particular holdee, Cisco CallManager looks at the MRGL configured at the device level. If this level is not defined, then Cisco CallManager looks at the MRGL configured for the device pool of the holdee device. If this level is not defined, then Cisco CallManager uses the system default MoH resources. System default MoH resources are those resources not assigned to any MRG, and they are always unicast.

Codec Selection

If you need multiple codecs for MoH deployment (based on the Device Pool and Region of the MOH Server and remote site phones), configure them in the IP Voice Streaming Media App service parameter under Cisco CallManager Service Parameters Configuration. Select the desired codec types from the Supported MoH Codecs list under the Clusterwide Parameters section. By default, only G.711 mu-law is selected. To select another codec type, click on it in the scrollable list. For multiple selections, hold down the CTRL key and use the mouse to select multiple codecs from the scrollable list. After making your selection, click the Update button and restart the IP Media Streaming App service.

Parameter Name

Parameter Value

Suggested Value

Supported MQH CodecsH

Ip Type-of-Service to Cisco CailManager*

Parameter Value

Was this article helpful?

0 0

Post a comment