Как установить музыку в cucm
В этой статье я расскажу, как настроить телефонную станцию Cisco CUCM в качестве Music on Hold (MoH) медиа сервера. Music on Hold – это аудио поток, проигрываемый абоненту, в случае если вызов поставлен вами на удержание.
MoH server может быть настроен как unicast или multicast .
Multicast конфигурация экономит как ресурсы самого сервера, так и полосу пропускания сети, поскольку задействуется только один аудио поток, другими словами, потоки MoH передаются от MoH сервера на multicast групповой адрес, к которому по необходимости подключаются конечные устройства. Учтите, что для работы multicast MoH требуется поддержка передачи мультикаста на сетевом уровне. Для Unicast каждый вызов, поставленный на удержание, требует своего отдельного аудио потока, что при большом количестве абонентов, использующих функцию MoH может сказаться на уменьшении производительности MoH server -а и полосы пропускания сети передачи данных.
Требования к используемым музыкальным файлам для MoH сервера:
Частота дискретизации – 8, 16, 32 или 48 кГц.
Стерео или моно
Загрузка WAV файла на CUCM. Это делается через WEB- интерфейс CM Administration в разделе Media Resources > MOH Audio File Management . 
Далее нажмите кнопку Upload File , и укажите расположение вашего файла. 
Загрузка может занять некоторое время, поскольку происходит не только загрузка файла, но и его автоматическая конвертация в форматы нужных кодеков. 
После успешной загрузки и конвертации необходимо сконфигурировать MOH audio source в разделе Media Resources > Music On Hold Audio Source. В этом разделе указывается имя источника музыки. 
Нажмите Add New 
Здесь вам необходимо указать stream number, audio source name и multicast and repeat play back настройки 
Теперь необходимо включить MOHсервер через меню Media Resources > Music On Hold Server. В случае, если вы используете несколько Region-ов, то Вам необходимо выбрать тот DevicePool, который поддерживает Region, взаимодействующий со всеми другими регионами с использованием G711 кодека.
Дополнительно, чтобы работал сервис MoH, вам необходимо проверить активацию сервиса CiscoIP Voice Media Streaming App (IPVMA) в разделе Cisco Unified Serviceability > Tools > ServiceActivation. Отмечу, что MoH server будет автоматически создан при активации сервиса Cisco IP Voice Media Streaming Application. 
Финальным шагом будет нажатие кнопки Save и применение конфигурации через нажатие ApplyConfig
Как установить музыку в cucm
The help desk software for IT. Free.
Track users’ IT needs, easily, and with only the features you need.
rburch 
Как установить музыку в cucm
Принципы MOH Audio-Source Selection
- Если VGK_phone1 ставит на Hold PTR_phone2, то у PTR_phone2 будет играть 1-Sample с сервера ptr01gtw01_moh
- Если PTR_phone2 ставит на Hold VGK_phone1, то у VGK_phone1 будет играть 2-Sample с сервера vgk01gtw01_moh
Настройка MOH: MOH Audio Files
- 16-bit Pulce Code Modulation (PCM) .wav file
- Stereo/Mono
- Sample rates 48, 32, 16, or 8 kHz
Настройка MOH: MOH Audio Sources
Media Resources > Music On Hold Audio Source > add
Настройка MOH: MOH Server
Настройка MOH: проверка MOH Service Parameters
- IP VoiceMedia Streaming App service
— Supported MOH codecs (G.711, G729A, wideband)
— QoS for MOH (signaling and audio)
— Packet size forG.711,G.729, and wideband (20 ms) - Cisco CallManager service
— Suppress MOH to Conference Bridge (True)
— DefaultNetworkHoldMOH AudioSource ID(1)
— DefaultUser Hold MOHAudio Source ID (1)
— Duplex Streaming Enabled (False)
Feature Configuration Guide for Cisco Unified Communications Manager, Release 10.5(2)
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
- Getting Started
- Silent Monitoring
- Ad Hoc Conferencing
Book Title
Feature Configuration Guide for Cisco Unified Communications Manager, Release 10.5(2)
Music On Hold
View with Adobe Reader on a variety of devices
Results
Chapter: Music On Hold
Music On Hold
Music On Hold Overview
Use the integrated Music On Hold (MOH) feature to place on-net and off-net users on hold with music from a streaming source. This source makes music available to any on-net or off-net device that you place on hold. On-net devices include station devices and applications that an interactive voice response (IVR) or call distributor places on hold, consult hold, or park hold. Off-net users include those users who are connected through Media Gateway Control Protocol (MGCP) or Skinny Call Control Protocol (SCCP) gateways, Cisco IOS H.323 gateways, and Cisco IOS Media Gateway Control Protocol gateways. The system also makes the Music On Hold feature available for Cisco IP POTS phones that connect to the Cisco IP network through Foreign Exchange Station (FXS) ports on Cisco IOS H.323 or MGCP and for Cisco MGCP or SCCP gateways.
Start Cisco Unified Communications Manager to create a media resource manager. Music On Hold server registers to the media resource manager with its music on hold resources. Music On Hold server is a software application that provides music on hold audio sources and connects a music on hold audio source to multiple streams.
When an end device or feature places a call on hold, Cisco Unified Communications Manager connects the held device to a music resource. When the held device is retrieved, it disconnects from the music on hold resource and resumes normal activity.
Caller-Specific Music On Hold
For SIP calls that a phone receives over the SIP trunk, Cisco Unified Communications Manager can use a different MOH audio source.
An external application, such as the Cisco Unified Customer Voice Portal (CVP) contact center solution, determines the most appropriate MOH audio source based on the caller ID, dialed number, or IVR interaction when a call is received from the public switched telephone network (PSTN).
Increased Capacity of IP Voice Media Streaming Application and Expanded MOH Audio Source
Cisco IP Voice Media Streaming application is installed automatically when you install Cisco Unified Communications Manager. Activate this application to enable the Music On Hold (MOH) feature.
With this release, the capacity of Cisco Unified Communications Manager to support unique and concurrent MOH audio sources, while the Music On Hold service is running on the MOH server, is increased from 51 to 501. The MOH audio sources are numbered from 1 to 501 with the fixed MOH audio source remaining at the number 51.
The fixed MOH device cannot use an audio source that connects through a USB MOH device, because Cisco Unified Communications Manager does not support USB when running on VMware. Use of the fixed MOH USB device is not supported on VMware. However, provision the external sound device for use with deployments that utilize Cisco Unified Survivable Remote Site Telephony (SRST) multicast MOH.
You can configure each MOH audio source to use a custom announcement as an initial greeting and/or an announcement that is played periodically to callers who are hearing the music. Cisco Unified Communications Manager provides 500 custom announcements that you can use on one or multiple MOH audio sources. These announcements are not distributed between the Cisco Unified Communications Manager servers within a cluster. You have to upload these custom announcement files to each server that provides the MOH and announcement services. You must also upload each custom music file for MOH audio sources to each server.
Performance Impact of Media Devices with Services
The Cisco IP Voice Media Streaming application runs as a service for four media devices—annunciator (ANN), software conference bridge, Music On Hold (MOH), and software media termination point. Activate this service on a Cisco Unified Communications Manager server as coresident with call processing. When you activate this service, ensure that you configure these media devices for limited capacity to avoid any impact on the call processing. The default settings for the media devices are defined based on this coresident operation. You can adjust these settings by reducing the use of one or more media devices to increase other settings.
For example, if you are not using software media termination point devices, you can choose the Run Flag setting for the SW MTP to False , select System > Service Parameters > Cisco IP Voice Media Streaming App service > MTP Parameters , and add the MTP Call Count setting to Media Resource > MOH Server > Maximum Half Duplex Streams configuration. Depending on the call traffic, you can modify the default settings. However, monitor the server performance activity for CPU, memory, and IO wait. For higher capacity clusters, such as the ones using 7500 user OVA configuration, it is possible to increase the default media device settings for Call Count by 25%.
For installations where you expect high usage of the media devices, such as Music On Hold, or where high call volumes require higher number of media connections, activate the Cisco IP Voice Media Streaming application service on one or more of the Cisco Unified Communications Manager servers which do not have call processing activated. Activating this service limits the impact of media device usage to other services, such as call processing. Then, you can increase the configuration settings for maximum number of calls for the media devices.
When you activate Cisco IP Voice Media Streaming application as co-resident with Cisco Unified Communications Manager service, it can impact call processing performance. To increase the capacity settings for Music On Hold or annunciator from the default settings, it is suggested to activate Cisco IP Voice Media Streaming application on a server without activating Cisco Unified Communications Manager.
The CPU performance is impacted by MOH when active callers are on hold or when multicast MOH audio streams are configured.
Dedicated MOH server, 1000 held calls, 500 MOH sources with greeting and periodic announcements.
25–45% (7500 user OVA configuration)
Native call queuing with dedicated MOH server and annunciator server, 1000 queued calls, 500 MOH sources with greeting and periodic announcements. An annunciator can play up to 300 simultaneous greeting announcements.
25–45% (7500 user OVA configuration)
Dedicated MOH server, 500 held calls, 500 MOH sources with greeting and periodic announcements.
15–35% (7500 user OVA configuration)
When Cisco IP Voice Media Streaming application is co-resident with Cisco Unified Communications Manager on 2500 OVA (moderate call processing).
MOH: 500 held callers, 100 MOH sources, and 48 to 64 annunciator callers.
When Cisco IP Voice Media Streaming application is a dedicated server on 2500 OVA.
MOH: 750 held callers, 250 MOH sources, and 250 annunciator callers.
When Cisco IP Voice Media Streaming application is co-resident with Cisco Unified Communications Manager on 7500/10K OVA (moderate call processing).
MOH: 500 held callers, 250 MOH sources, and 128 annunciator callers.
When Cisco IP Voice Media Streaming application is a dedicated server on 7500/10K OVA.
Reduce annunciator to 300 for two MOH codecs.
These recommendations are specific to MOH/ANN devices. If you combine these devices with the software media termination point (MTP) and call forward busy (CFB) devices, reduce the limits to provide streams.
Configuration Limitations for Capacity Planning
The Cisco IP Voice Media Streaming application and Self Provisioning IVR services use a media kernel driver to create and control Real-time Transfer Protocol (RTP) streams. This media kernel driver has a capacity of 6000 streams. These streams allow the media devices and IVR to make resource reservations.
These reservations are based on the following capacity calculations:
(Call Count service parameter) * 3
Where 3 indicates total of receiving (RX) and transmitting (TX) calls for endpoint and 1 for .wav file.
Software Conference Bridge
(Call Count service parameter) * 2
Where 2 indicates total streams of RX and TX endpoints.
Software Media Termination Point
(Call Count service parameter) * 2
Where 2 indicates total streams of RX and TX endpoints.
((Maximum Half Duplex Streams) * 3) + (501 * 2 * [number of enabled MOH codecs])
(Maximum Half Duplex Streams) is a configuration setting on the MOH device configuration administration web page.
3 indicates total steams of RX, TX, and greeting announcement .wav file.
501 indicates the maximum number of Music On Hold (MOH) sources.
2 indicates music .wav stream and possible multicast TX stream.
[number of enabled MOH codecs] is based on how many MOH codecs are enabled in the Cisco IP Voice Media Streaming application service parameters.
Self Provisioning IVR Service
Where 500 indicates callers, and 2 indicates total streams from RX and TX streams.
Hence, to enable MOH to support a maximum of 1000 callers, use the following equation: 1000 * 3 + 501 * 2 * 1 = 4002 driver streams with one enabled codec and 1000 * 3 +501 * 2 * 2 = 5004 with two enabled codecs. Reduce the remaining devices and deactivate the Self Provisioning IVR service to limit total reservations to 6000, which allows the MOH device to make these reservations. It may also require that you do not activate the Self Provisioning IVR service on the same server with Cisco IP Voice Media Streaming application.
If configuration settings of the media devices exceed the capacity of the media device driver, the media devices that register with the device driver first will be able to reserve their required stream resources. The media devices that register later are restricted to fewer than requested stream resources. The later registered media devices result in logging some alarm messages and automatically reducing the call count for the restricted media device.
A media kernel driver with a capacity of 6000 streams might not support that many simultaneous media device connections.
Music On Hold Prerequisites
Before you configure multicast, ensure that you configure MOH server and audio sources. If you want to use fixed audio source, configure it before you configure multicast.
Make sure to decide whether you are going to do unicast or multicast Music On Hold
It is crucial to plan the capacity of the deployed and configured hardware and ensure that it can support the anticipated call volume of the network. You need to know the hardware capacity for MOH resources and consider the implications of multicast and unicast MOH in relation to this capacity. Ensure that network call volumes do not exceed these limits. When MOH sessions reach these limits, an additional load can result in poor MOH quality, erratic MOH operation, or loss of MOH functionality.
If you use multicast MOH and the devices that listen to multicast MOH streams are not in the same IP network, you must enable multicast routing in the IP network. Take care when you enable the multicast routing to avoid the potential flooding of parts of the network with wrongly sent multicast packets (specially, across WAN links). Disable multicasts on interfaces on which the multicast MOH packets are not required and use the Max Hops parameter.
For detailed information on planning your Music On Hold deployment, including server capacities, refer to the Music On Hold capacities topics in the Cisco Collaboration System Solution Reference Network Design .
Music On Hold Configuration Task Flow
Before you begin
Procedure
Configure Music On Hold server. See Configure Music On Hold Server.
Stream Music on Hold from Music On Hold data source files that are stored on their disks or external audio source.
Configure MOH audio. See Music On Hold Audio Source Configuration, and perform the following subtasks:
- Upload an MOH audio file. See Upload Audio File for Music On Hold.
- Convert MOH Files. See Convert Music On Hold Files.
- Configure MOH audio source. See Configure Music On Hold Audio Source.
Upload a Music On Hold audio file to make it available for use as a Music on Hold audio source.
Convert the Music On Hold file to the appropriate formats for use by the Music On Hold server.
To place on-net and off-net users on hold (end user hold or network hold) with music streamed from a streaming source.
(Optional) Configure fixed MOH audio source. See Configure Fixed Music On Hold Audio Source.
Configure the fixed MOH audio source in addition to the file stream sources.
Configure Media Resource Group. See Add MOH to Media Resource Group.
Define logical groupings of media servers.
Configure Media Resource Group list. See Configure Media Resource Group List.
Specify a list of prioritized media resource groups.
(Optional) Enable secured MOH through SRTP. See Enable Secured Music On Hold through SRTP.
When you enable the Cisco Unified Communications Manager cluster or system for security, the MOH server registers with the Cisco Unified Communications Manager as an SRTP-capable device.
Configure multicast by performing the following subtasks:
- Plan MOH Server capacity. See Plan Music On Hold Server Capacity.
- Verify Music On Hold service parameters. See Configure MOH Service Parameters.
- Configure multicast Music On Hold audio sources or fixed MOH audio source. See Configure Multicast Music On Hold Audio Sources/Fixed MOH Audio Source.
- Configure multicast Music On Hold server. See Configure Multicast Music On Hold Server.
- Configure a multicast-enabled media resource group. See Configure a Multicast-Enabled Media Resource Group.
- Configure multicast Music On Hold over H.323 intercluster trunks. See Configure Multicast Music On Hold over H.323 Intercluster Trunks.
(Optional) Reset or restart a Music On Hold server. See Reset or Restart a Music On Hold Server.
Reset or restart a music on hold server for changes to take effect, if required.
(Optional) Synchronize Music On Hold server. See Synchronize Music On Hold Server.
Apply configuration to the selected music on hold servers.
Activate Cisco IP Voice Media Streaming
The Cisco IP Voice Media Streaming Application service must be Activated in order to use Music On Hold.
During installation, Unified Communications Manager installs and configures a default Music On Hold audio source. Music On Hold functionality can proceed by using the default audio source.
Procedure
From Cisco Unified CM Administration, choose Tools > Service Activation .
Choose a server from the Server drop-down list.
Under CM Services , make sure the Cisco IP Voice Media Streaming App service is Activated . If the service is deactivated, check the service and click Save .
Configure Music On Hold Server
Before you begin
The Cisco Unified Communications Manager MOH server is automatically added when the Cisco IP Voice Media Streaming Application service is activated.
Procedure
From Cisco Unified CM Administration, choose Media Resources > Music On Hold Server .
Click Find and select the Music On Hold server that you want to update.
Select the Host Server .
Enter a descriptive Music On Hold Server Name along with a Description .
Select the Device Pool you want to use for this server.
Configure server capacity by configuring the following fields:
- Maximum Half Duplex Stream —Set this to the maximum number of devices that can be on unicast music on hold that is streamed from this music on hold server at any given time. You can use the following formula to calculate the maximum:
Note (Server and deployment capacity) – ([Number of multicast MOH sources] * [Number of enabled MOH codecs]) - Maximum Multi-cast Connections —Set this to a value that is greater than or equal to the number of devices that might be placed on multicast MOH at any given time.
(Optional) To enable multi-casting, check the Enable Multi-cast Audio Sources on this MOH Server check box, and configure the multicast IP address ranges.
Configure the additional fields in the Music On Hold Server Configuration window. For help with the fields and their settings, see the online help.
Music On Hold Server Fields for Music On Hold
Displays the registration information of the device.
Displays the IPv4 address.
Displays the IPv6 address.
Device is trusted
If the device is trusted, a green checkmark appears.
Displays the IP address of the existing host server.
Music On Hold Server Name
Enter a unique name for the MOH server. The name can comprise up to 15 characters. You can form the name by using letters, numbers, spaces, dashes, dots (periods), and underscores.
Enter a description for the MOH server. The description can include up to 50 characters. Ensure that this field does not contain ampersand (&), double quotes (“), brackets ([]), less than (<), greater than (>), or the percentage (%).
Choose a device pool for the Music On Hold server from the drop-down arrow and choose a device pool from the list that appears.
Use locations to implement call admission control (CAC) in a centralized call-processing system. CAC enables you to regulate audio quality and video availability by limiting the amount of bandwidth that is available for audio and video calls over links between locations. The location specifies the total bandwidth that is available for calls to and from this location.
From the drop-down list, choose the appropriate location for this MOH server.
The Hub_None location field indicates that the locations feature does not keep track of the bandwidth that this MOH server consumes. The Phantom location field indicates a location that enables successful CAC across intercluster trunks that use H.323 or SIP protocol.
To configure a new location, use the System > Location menu option.
Maximum Half Duplex Streams
Enter a number in this required field for the maximum number of unicast Music On Hold streams that this Music On Hold server supports. This value determines the maximum number of devices that can be on unicast Music On Hold that is streamed from this Music On Hold server at any given time. Valid values range from 0 to 1000.
Maximum Multi-cast Connections
Enter a number in this required field for the maximum number of multicast Music On Hold streams that this Music On Hold server supports. This value determines the maximum number of devices that can be on multicast music on hold that is streamed from this Music On Hold server at any given time. Valid values range from 1 to 999999.
Fixed Audio Source Device
Enter the device name of the fixed audio source device. This device serves as the per-server override that is used if the server has a special sound device installed.
Use Trusted Relay Point
From the drop-down list, enable or disable whether Cisco Unified Communications Manager inserts a trusted relay point (TRP) device with this media endpoint. Choose one of the following values:
Off —Disables the use of a TRP with this device.
On —Enables the use of a TRP with this device.
A trusted relay point (TRP) device designates an Media Transfer Protocol (MTP) or transcoder device that is labeled as Trusted Relay Point.
Cisco Unified Communications Manager places the TRP closest to the associated endpoint device if more than one resource is needed for the endpoint (for example, a transcoder or RSVPAgent).
If both TRP and MTP are required for the endpoint, TRP is used as the required MTP.
If both TRP and RSVPAgent are needed for the endpoint, Cisco Unified Communications Manager first tries to find an RSVPAgent that can also be used as a TRP.
If both TRP and transcoder are needed for the endpoint, Cisco Unified Communications Manager first tries to find a transcoder that is also designated as a TRP.
Use this required field to choose a run flag for the Music On Hold server. To do so, click the drop-down arrow and choose Yes or No. Choosing No disables the music on hold server.
Enable Multicast Audio Sources on this MOH Server
Check or uncheck this check box to enable or disable the multicast of audio sources for this Music On Hold server.
If this MOH server belongs to a multicast media resource group, a message asks you to enable multicast on this MOH server or to update the specified media resource groups either by removing this MOH server or by changing the multicast field of each listed group.
Base Multicast IP Address
If multicast support is needed, enter the base multicast IP address in this field. Valid IP addresses for multicast range from 224.0.1.0 to 239.255.255.255.
IP addresses between 224.0.1.0 and 238.255.255.255 are in the reserved range of IP multicast addresses for public multicast applications. Use of these addresses may interfere with existing multicast applications on the Internet. We strongly recommend using IP addresses that are in the range that is reserved for administratively controlled applications on private networks (239.0.0.0 – 239.255.255.255).
Base Multicast Port Number
If multicast support is needed, enter the base multicast port number in this field. Valid multicast port numbers include even numbers that range from 16384 to 32766.
Increment Multicast on
Click Port Number to increment multicast on port number.
Click IP Address to increment multicast on IP address.
Use multicast by incrementing IP address as the preferred method in firewall situations. This results in a unique IP address for each multicast audio source and helps to avoid network saturation.
This field designates Music On Hold audio stream number that is associated with a particular multicast audio source. Only audio sources that are defined as allowing multicasting appear.
Audio Source Name
This field designates the name of the audio source that is defined to allow multicasting.
For each multicast audio source, enter the maximum number of router hops through which multicast packets should pass. Valid values range from 1 to 127.
Using high values can lead to network saturation. This field also gets identified as Time to Live.
Music On Hold Audio Source Configuration
Upload Audio File for Music On Hold
Procedure
From Cisco Unified CM Administration, choose Media Resources > MOH Audio File Management .
Click Upload File .
Click Choose File and browse to the file you want to upload. Once you’ve selected the file, click Open .
The Upload Result window shows the result of the upload. The uploading procedure uploads the file and performs audio conversions to create codec-specific audio files for MOH. Depending on the size of the original file, processing may take several minutes to complete.
Click Close to close the Upload Result window.
Repeat this procedure if you want to upload additional audio files.
When you import an audio source file, Cisco Unified Communications Manager processes the file and converts the file to the proper formats for use by the Music On Hold server. Followoing are examples of valid input audio source files:
16-bit PCM .wav file
Sample rates of 48 kHz, 44.1 kHz, 32 kHz, 16 kHz, or 8 kHz
MOH audio source files do not automatically propagate to other MOH servers in a cluster. You must upload an audio source file to each MOH server or each server in a cluster separately
Convert Music On Hold Files
When you import an audio source file, Cisco Unified Communications Manager processes the file and converts the file to the proper formats for use by the Music On Hold server.
16-bit PCM .wav file
Sample rates of 48 kHz, 44.1 kHz, 32 kHz, 16 kHz, or 8 kHz
Before you begin
What to do next
Configure Music On Hold Audio Source
Use this procedure to configure Music On Hold audio sources. You can configure audio streams and associate uploaded files to an audio stream. You can configure up to 500 audio streams.
If a new version of an audio source file is available, perform the update procedure to use the new version.
Procedure
From Cisco Unified CM Administration, choose Media Resources > Music On Hold Audio Source .
Do either of the following:
- Click Find and select an existing audio stream.
- Click Add New to configure a new stream.
From the MOH Audio Stream Number , select an audio stream.
Enter a unique name in the MOH Audio Source Name field.
Optional. Check the Allow Multi-casting check box if you want to allow this file to be multi-casted.
Configure the audio source:
- Check the Use MOH WAV file source radio button and from the MOH Audio Source File , select the file you want to assign.
- Check the Rebroadcast External Multicast Source radio button and enter the multicast source IP Address details.
In the Announcement Settings for Held and Hunt Pilot Calls section, assign the announcements that you want to use for this audio source.
Configure the remaining fields in the Music On Hold Audio Source Configuration window. For help with the fields and their settings, see the online help.
Audio Source Fields for Music On Hold
MOH Audio Stream Number
Use this field to choose the stream number for this MOH audio source. Click the drop-down arrow and choose a value from the list. For existing MOH audio sources, the value appears in the MOH Audio Source title.
MOH Audio Source File
Use this field to choose the file for this MOH audio source. Click the drop-down arrow and choose a value from the list.
MOH Audio Source Name
Enter a unique name in this field for the MOH audio source. This name includes up to 50 valid characters, such as letters, numbers, spaces, dashes, dots (periods), and underscores.
Check this check box to specify that the selected MOH audio source allows multicasting.
MOH Audio Source File Status
This pane displays the following information about the source file for the selected MOH audio source:
Блог инструктора Cisco Дмитрия Бенды (CCSI#33268)
суббота, 3 сентября 2011 г.
Использование аппаратных медиа-ресурсов для CUCME
SMA-Mos4a-R3#sh call active voice compact
A/O FAX T Codec type Peer Address IP R:
Total call-legs: 4
1 ANS T28 g711alaw VOIP P88462057001 10.200.104.11:17774
2 ORG T28 g711alaw VOIP P78469735050 91.218.111.140:40784
3 ORG T28 g711alaw VOIP P 10.200.15.229:2000
5 ORG T28 g711alaw VOIP P 10.200.15.229:2000
0 1 28.3.1 UP 1 USED xcode 1 27 1003 1203
0 1 28.3.1 UP 1 USED xcode 1 26 1200 1005
Total number of DSPFARM DSP channel(s) 1
debug voip ccapi inout
000311: May 29 08:52:40.789: ccConferenceCreate: ret1=0, codecMask1=2, bytes1=160, negot1=1, dtmf1=0
ret2=0, codecMask2=2, bytes2=160, negot2=1, dtmf2=6,
INVITE sip:084957257660@192.168.251.14:5060 SIP/2.0
Date: Mon, 27 Aug 2012 11:58:26 GMT
Call-Info: ;method=»NOTIFY;Event=telephone-event;Duration=500″
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
From: «Nikolaev S.L.» ;tag=64416edd-2714-4f01-97d8-6d5908214519-28517748
Allow-Events: presence, kpml
P-Asserted-Identity: «Nikolaev S.L.»
Supported: timer,resource-priority,replaces
Supported: X-cisco-srtp-fallback
Supported: Geolocation
Min-SE: 1800
Remote-Party-ID: «Nikolaev S.L.» ;party=calling;screen=yes;privacy=off
Content-Length: 216
User-Agent: Cisco-CUCM7.1
To:
Contact:
Expires: 180
Content-Type: application/sdp
Call-ID: 80ee2280-3b160e2-9d-34fba8c0@192.168.251.52
Via: SIP/2.0/TCP 192.168.251.52:5060;branch=z9hG4bK11c5fa14a4b
CSeq: 101 INVITE
Session-Expires: 1800
Max-Forwards: 70
v=0
o=CiscoSystemsCCM-SIP 2000 1 IN IP4 192.168.251.52
s=SIP Call
c=IN IP4 192.168.251.53
t=0 0
m=audio 16858 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=ptime:20
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
Насколько я понял, SCCP телефоны хотят только OOB DTMF, SIP trunk хочет In-band (RFC-2833), а MTP должен перекодировать одно в другое?
Часть конфига маршр-ра:
voice rtp send-recv
!
voice service voip
address-hiding
allow-connections h323 to h323
allow-connections h323 to sip
allow-connections sip to h323
allow-connections sip to sip
redirect ip2ip
sip
history-info
g729 annexb-all
!
voice class codec 1
codec preference 1 g729r8
codec preference 2 g711alaw
codec preference 3 g711ulaw
!
!
!
!
voice-card 0
dspfarm
dsp services dspfarm
!
!
application
service MVA http://192.168.251.52:8080/ccmivr/pages/IVRMainpage.vxml
.
.
interface FastEthernet0/0
description $ETH-LAN$$ETH-SW-LAUNCH$$INTF-INFO-FE 0/0$
ip address 192.168.251.53 255.255.255.240
duplex auto
speed auto
h323-gateway voip interface
h323-gateway voip bind srcaddr 192.168.251.53
!
interface FastEthernet0/1
no ip address
shutdown
duplex auto
speed auto
!
ip forward-protocol nd
no ip http server
ip http access-class 23
ip http authentication local
no ip http secure-server
ip http timeout-policy idle 60 life 86400 requests 10000
!
ip route 0.0.0.0 0.0.0.0 192.168.251.49
!
control-plane
!
mgcp fax t38 ecm
!
sccp local FastEthernet0/0
sccp ccm 192.168.251.52 identifier 1 version 7.0
sccp
!
sccp ccm group 1
bind interface FastEthernet0/0
associate ccm 1 priority 1
associate profile 101 register mtp04c5a43f7e99
associate profile 100 register mtp04c5a43f7e98
associate profile 99 register cfb04c5a43f7e98
!
dspfarm profile 101 transcode
codec g711ulaw
codec g711alaw
codec g729ar8
codec g729abr8
codec gsmamr-nb
codec ilbc
codec pass-through
maximum sessions 6
associate application SCCP
!
dspfarm profile 99 conference
codec g711ulaw
codec g711alaw
codec g729ar8
codec g729abr8
codec g729r8
codec g729br8
maximum sessions 2
associate application SCCP
!
dspfarm profile 100 mtp
codec g711ulaw
maximum sessions software 20
associate application SCCP
!
dial-peer voice 5769 voip
service mva
incoming called-number 5769
dtmf-relay rtp-nte digit-drop h245-signal h245-alphanumeric cisco-rtp
codec g711ulaw
no vad
!
dial-peer voice 5770 voip
destination-pattern 5770
session target ipv4:192.168.251.52
dtmf-relay h245-signal rtp-nte h245-alphanumeric cisco-rtp
codec g711ulaw
no vad
!
!
gateway
timer receive-rtp 600
conf-1 Device:mtp001b54ca9aa2 TCP socket:[18] REGISTERED in SCCP ver 18/18
actual_stream:48 max_stream 48 IP:10.27.120.7 * 65463 Conference Dixieland keepalive 0
Supported codec:
G711Ulaw
G711Alaw
G729
G729a
G729b
G729ab
max-mtps:2, max-streams:0, alloc-streams:0, act-streams:0
c2821#
c2821#sh dspfarm dsp all
SLOT DSP VERSION STATUS CHNL USE TYPE RSC_ID BRIDGE_ID PKTS_TXED PKTS_RXED
0 3 28.3.1 UP N/A FREE conf 1 — — —
0 3 28.3.1 UP N/A FREE conf 1 — — —
0 4 28.3.1 UP N/A FREE conf 1 — — —
0 4 28.3.1 UP N/A FREE conf 1 — — —
0 5 28.3.1 UP N/A FREE conf 1 — — —
0 5 28.3.1 UP N/A FREE conf 1 — — —
Total number of DSPFARM DSP channel(s) 6
c2821#
voice call send-alert
voice call carrier capacity active
!
voice service pots
no direct-inward-dial isdn
!
voice service voip
allow-connections h323 to h323
redirect ip2ip
!
voice class codec 1
codec preference 1 g711ulaw
codec preference 2 g711alaw
!
voice class custom-cptone leavetone
dualtone conference
frequency 400 800
cadence 400 50 200 50 200 50
!
voice class custom-cptone jointone
dualtone conference
frequency 600 900
cadence 300 150 300 100 300 50
!
!
voice register global
!
!
!
!
voice-card 0
dsp services dspfarm
sccp ccm group 1
bind interface GigabitEthernet0/1.7
associate ccm 1 priority 1
associate profile 1 register HW_CFB
!
dspfarm profile 1 conference
codec g711ulaw
codec g711alaw
codec g729ar8
codec g729abr8
codec g729r8
codec g729br8
maximum sessions 6
conference-join custom-cptone jointone
conference-leave custom-cptone leavetone
associate application SCCP
telephony-service
sdspfarm units 2
sdspfarm tag 1 HW_CFB
conference hardware
max-ephones 58
ephone-template 1
conference drop-mode local
conference add-mode creator
conference admin
softkeys hold Join Newcall Resume Select
softkeys idle Cfwdall ConfList Dnd Join Newcall Pickup Redial RmLstC
softkeys seized Endcall Redial Meetme Cfwdall Pickup
softkeys alerting Callback Endcall
softkeys connected ConfList Confrn Endcall Hold Join Park RmLstC Select Trnsfer
softkeys ringing Answer Dnd
keep-conference
ephone-dn 29 dual-line
number 27000
conference meetme
preference 1
no huntstop
!
!
ephone-dn 30 dual-line
number 27000
conference meetme
preference 2
no huntstop
!
!
ephone-dn 31 dual-line
number 27000
conference meetme
preference 3
no huntstop
ephone 1
conference drop-mode creator
conference add-mode creator
conference admin
device-security-mode none
mac-address 001D.54CA.9AA2
ephone-template 1
type 7941
button 1:25
!
СПАСИБО
c2821#sh run | sec sccp
tftp-server flash:cvm41sccp.9-1-1TH1-16.sbn
tftp-server flash:jar41sccp.9-1-1TH1-16.sbn
tftp-server flash:/Phones/7911-7906/cvm11sccp.9-1-1TH1-16.sbn
tftp-server flash:/Phones/7911-7906/jar11sccp.9-1-1TH1-16.sbn
tftp-server flash:/Phones/7941-7961/cvm41sccp.9-1-1TH1-16.sbn
tftp-server flash:/Phones/7941-7961/jar41sccp.9-1-1TH1-16.sbn
tftp-server flash:/8.4/cvm41sccp.8-4-1-23.sbn
tftp-server flash:/8.4/jar41sccp.8-4-1-23.sbn
tftp-server flash:/mk-sccp.jar alias Russian_Federation/td-sccp.jar
tftp-server flash:/mk-sccp.jar alias Russian_Russia/mk-sccp.jar
tftp-server flash:/tc-sccp.jar alias Russian_Russia/tc-sccp.jar
tftp-server flash:/Locale/ru-mk-sccp.jar
tftp-server flash:/Locale/ru-tc-sccp.jar
tftp-server flash:/Locale/ru-td-sccp.jar
tftp-server flash:jar11sccp.8-3-3ES2.sbn
tftp-server flash:cvm11sccp.8-3-3ES2.sbn
tftp-server flash:7941-7961-sccp.8-4-2S.tar
tftp-server flash:7906-7911-sccp.8-4-2S.tar
tftp-server flash:cmterm-7941_7961-sccp.9-3-1-1.cop.sgn
tftp-server flash:cvm41sccp.9-3-1TH2-5.sbn
tftp-server flash:jar41sccp.9-3-1TH2-5.sbn
sccp local GigabitEthernet0/1.7
sccp ccm 10.27.120.7 identifier 1 version 7.0
sccp
sccp ccm group 1
bind interface GigabitEthernet0/1.7
associate ccm 1 priority 1
associate profile 1 register HW_CFB
keepalive retries 5
c2821#
c2821#sh sccp
SCCP Admin State: UP
Gateway Local Interface: GigabitEthernet0/1.7
IPv4 Address: 10.27.120.7
Port Number: 2000
IP Precedence: 5
User Masked Codec list: None
Call Manager: 10.27.120.7, Port Number: 2000
Priority: N/A, Version: 7.0, Identifier: 1
Trustpoint: N/A
Conferencing Oper State: ACTIVE — Cause Code: NONE
Active Call Manager: 10.27.120.7, Port Number: 2000
TCP Link Status: CONNECTED, Profile Identifier: 1
Reported Max Streams: 48, Reported Max OOS Streams: 0
Supported Codec: g711ulaw, Maximum Packetization Period: 30
Supported Codec: g711alaw, Maximum Packetization Period: 30
Supported Codec: g729ar8, Maximum Packetization Period: 60
Supported Codec: g729abr8, Maximum Packetization Period: 60
Supported Codec: g729r8, Maximum Packetization Period: 60
Supported Codec: g729br8, Maximum Packetization Period: 60
Supported Codec: rfc2833 dtmf, Maximum Packetization Period: 30
Supported Codec: rfc2833 pass-thru, Maximum Packetization Period: 30
Supported Codec: inband-dtmf to rfc2833 conversion, Maximum Packetization Period: 30
TLS : ENABLED
c2821#sh telephony-service
CONFIG (Version=8.6)
=====================
Version 8.6
Max phoneload sccp version 17
Max dspfarm sccp version 18
Cisco Unified Communications Manager Express
For on-line documentation please see:
http://www.cisco.com/en/US/products/sw/ . _home.html
protocol mode default
ip source-address 10.27.120.7 port 2000
ip qos dscp:
ef (the MS 6 bits, 46, in ToS, 0xB8) for media
cs3 (the MS 6 bits, 24, in ToS, 0x60) for signal
af41 (the MS 6 bits, 34, in ToS, 0x88) for video
default (the MS 6 bits, 0, in ToS, 0x0) for serviceservice directed-pickup
service dnis dir-lookup
service dss
load 7911 SCCP11.9-1-1SR1S
load 7941 SCCP41.9-3-1-1S
max-ephones 58
max-dn 192
max-conferences 16 gain -6
dspfarm units 2
dspfarm transcode sessions 0
dspfarm 1 HW_CFB
dspfarm 2
conference hardware
privacy
no privacy-on-hold
hunt-group report delay 1 hours
hunt-group logout DND
max-redirect 10
cnf-file location: flash:
cnf-file option: PER-PHONE
network-locale[0] RU (This is the default network locale for this box)
network-locale[1] US
network-locale[2] US
network-locale[3] US
network-locale[4] US
user-locale[0] RU (This is the default user locale for this box)
user-locale[1] US
user-locale[2] US
user-locale[3] US
user-locale[4] US
srst mode auto-provision is OFF
srst ephone template is 0
srst dn template is 0
srst dn line-mode single
moh flash:music-on-hold.au
time-format 24
date-format dd-mm-yy
timezone 51 Central Pacific Standard Time
secondary-dialtone 9
call-park system redirect
transfer-pattern 1
transfer-pattern 2
keepalive 30 auxiliary 30
timeout interdigit 5
timeout busy 10
timeout ringing 120
timeout transfer-recall 20
timeout ringin-callerid 8
timeout night-service-bell 12
caller-id name-only: enable
system message Rosreestr 27
web admin system name root password ********
web admin customer name mikle password *******
edit DN through Web: enabled.
edit TIME through web: enabled.
background save interval 10 minutes
Log (table parameters):
max-size: 1000
retain-timer: 30
create cnf-files version-stamp Jan 01 2002 00:00:00
transfer-system full-consult
transfer-digit-collect new-call
multicast moh 239.10.16.4 port 16384
route 10.27.120.5
10.27.120.240
local directory service: enabled.
Extension-assigner tag-type ephone-tag.
«c2821#sh dspfarm dsp all
SLOT DSP VERSION STATUS CHNL USE TYPE RSC_ID BRIDGE_ID PKTS_TXED PKTS_RXED
0 3 28.3.1 UP N/A FREE conf 1 — — —
0 3 28.3.1 UP N/A FREE conf 1 — — —
0 4 28.3.1 UP N/A FREE conf 1 — — —
0 4 28.3.1 UP N/A FREE conf 1 — — —
0 5 28.3.1 UP N/A FREE conf 1 — — —
0 5 28.3.1 UP N/A FREE conf 1 — — —
Total number of DSPFARM DSP channel(s) 6
0 3 28.3.1 UP N/A FREE conf 1 — — —
0 3 28.3.1 UP N/A FREE conf 1 — — —
0 4 28.3.1 UP 1 USED conf 1 136 2725 2726
0 4 28.3.1 UP 1 USED conf 1 138 2284 2276
0 4 28.3.1 UP 1 USED conf 1 140 1434 1426
0 4 28.3.1 UP N/A FREE conf 1 — — —
0 5 28.3.1 UP N/A FREE conf 1 — — —
0 5 28.3.1 UP N/A FREE conf 1 — — —
Iphone, софт-фон и телефон. Дружба с CUCM. — То измена, то зазада. — ЖЖ
Сегодня мы будем подключать с CUCM различные устройства по протоколу SIP.
Для начала произведем необходимые настройки в самом CUCM.
Нам надо будет сконфигурировать пользователя для авторизации на нашей АТС.
User Management -> End User. Add New.
Указываем имя пользователя, PIN и самое главное — Digest Credentials
Если вы выгружаете пользователей из LDAP — то все гораздо проще и Digest Credential настраивать не надо, это будет пароль пользователя из LDAP.
Теперь создадим телефон в CUCM.
Device — Phone. Add new.
Мас адрес можно указывать любой, он не важен для процесса регистрации, главное следите, что-бы для разных устройств они не совпадали.
Самое главное указать в поле Digest User — нашего созданного пользователя.
Сохраняем настройку, и прикрепляем к телефону номер. Все, настройка CUCM закончена.
Для начала подключим телефон Cisco SPA 502G.
Включаем телефон в сеть (не забудте убрать из DHCP все упоминания про option 150, иначе телефон захочет подключаться к вашему CUCM по SCCP протоколу, но не сможет этого сделать в принципе, мда — безысходность). Смотрим в настройках телефона полученный адрес, идем на него через браузер. Получаем админский доступ.
В секции Ext 1 надо внести следующие настройки.
Активировать линию, указать адрес нашего CUCM в поле Proxy, отметить что нужна регистрация.
В блоке Subscriber Information указываем:
Display Name имя для отображения
User ID — телефонный номер линии
Password — Digest Credential нашего пользователя.
Use Auth ID YES — использовать авторизацию по имени.
Auth ID — имя пользователя, настроенного в CUCM.
В блоке Audio Configuration указываем предпочитаемый кодек. И. все. Жмем Submit All Changes. После этого аппарат перегрузится.
Убеждаемся что аппарат зарегистрировался.
на самом аппарате
И на CUCM
Можно звонить.
Теперь настроим софт-фон X-lite.
Softphone->Account Settings
После запуска программы выбираем вкладку «Еще» и переходим в настройки
В расширенных настройках указываем имя пользователя для авторизации. 
После этого переключаемся на вкладку «набрать»
Позеленевшая центральная кнопка говорит о том что регистрация на CUCM прошла успешно. 
Можно звонить.
Feature Configuration Guide for Cisco Unified Communications Manager, Release 10.5(2)
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
- Getting Started
- Silent Monitoring
- Ad Hoc Conferencing
Book Title
Feature Configuration Guide for Cisco Unified Communications Manager, Release 10.5(2)
Music On Hold
View with Adobe Reader on a variety of devices
Results
Chapter: Music On Hold
Music On Hold
Music On Hold Overview
Use the integrated Music On Hold (MOH) feature to place on-net and off-net users on hold with music from a streaming source. This source makes music available to any on-net or off-net device that you place on hold. On-net devices include station devices and applications that an interactive voice response (IVR) or call distributor places on hold, consult hold, or park hold. Off-net users include those users who are connected through Media Gateway Control Protocol (MGCP) or Skinny Call Control Protocol (SCCP) gateways, Cisco IOS H.323 gateways, and Cisco IOS Media Gateway Control Protocol gateways. The system also makes the Music On Hold feature available for Cisco IP POTS phones that connect to the Cisco IP network through Foreign Exchange Station (FXS) ports on Cisco IOS H.323 or MGCP and for Cisco MGCP or SCCP gateways.
Start Cisco Unified Communications Manager to create a media resource manager. Music On Hold server registers to the media resource manager with its music on hold resources. Music On Hold server is a software application that provides music on hold audio sources and connects a music on hold audio source to multiple streams.
When an end device or feature places a call on hold, Cisco Unified Communications Manager connects the held device to a music resource. When the held device is retrieved, it disconnects from the music on hold resource and resumes normal activity.
Caller-Specific Music On Hold
For SIP calls that a phone receives over the SIP trunk, Cisco Unified Communications Manager can use a different MOH audio source.
An external application, such as the Cisco Unified Customer Voice Portal (CVP) contact center solution, determines the most appropriate MOH audio source based on the caller ID, dialed number, or IVR interaction when a call is received from the public switched telephone network (PSTN).
Increased Capacity of IP Voice Media Streaming Application and Expanded MOH Audio Source
Cisco IP Voice Media Streaming application is installed automatically when you install Cisco Unified Communications Manager. Activate this application to enable the Music On Hold (MOH) feature.
With this release, the capacity of Cisco Unified Communications Manager to support unique and concurrent MOH audio sources, while the Music On Hold service is running on the MOH server, is increased from 51 to 501. The MOH audio sources are numbered from 1 to 501 with the fixed MOH audio source remaining at the number 51.
The fixed MOH device cannot use an audio source that connects through a USB MOH device, because Cisco Unified Communications Manager does not support USB when running on VMware. Use of the fixed MOH USB device is not supported on VMware. However, provision the external sound device for use with deployments that utilize Cisco Unified Survivable Remote Site Telephony (SRST) multicast MOH.
You can configure each MOH audio source to use a custom announcement as an initial greeting and/or an announcement that is played periodically to callers who are hearing the music. Cisco Unified Communications Manager provides 500 custom announcements that you can use on one or multiple MOH audio sources. These announcements are not distributed between the Cisco Unified Communications Manager servers within a cluster. You have to upload these custom announcement files to each server that provides the MOH and announcement services. You must also upload each custom music file for MOH audio sources to each server.
Performance Impact of Media Devices with Services
The Cisco IP Voice Media Streaming application runs as a service for four media devices—annunciator (ANN), software conference bridge, Music On Hold (MOH), and software media termination point. Activate this service on a Cisco Unified Communications Manager server as coresident with call processing. When you activate this service, ensure that you configure these media devices for limited capacity to avoid any impact on the call processing. The default settings for the media devices are defined based on this coresident operation. You can adjust these settings by reducing the use of one or more media devices to increase other settings.
For example, if you are not using software media termination point devices, you can choose the Run Flag setting for the SW MTP to False , select System > Service Parameters > Cisco IP Voice Media Streaming App service > MTP Parameters , and add the MTP Call Count setting to Media Resource > MOH Server > Maximum Half Duplex Streams configuration. Depending on the call traffic, you can modify the default settings. However, monitor the server performance activity for CPU, memory, and IO wait. For higher capacity clusters, such as the ones using 7500 user OVA configuration, it is possible to increase the default media device settings for Call Count by 25%.
For installations where you expect high usage of the media devices, such as Music On Hold, or where high call volumes require higher number of media connections, activate the Cisco IP Voice Media Streaming application service on one or more of the Cisco Unified Communications Manager servers which do not have call processing activated. Activating this service limits the impact of media device usage to other services, such as call processing. Then, you can increase the configuration settings for maximum number of calls for the media devices.
When you activate Cisco IP Voice Media Streaming application as co-resident with Cisco Unified Communications Manager service, it can impact call processing performance. To increase the capacity settings for Music On Hold or annunciator from the default settings, it is suggested to activate Cisco IP Voice Media Streaming application on a server without activating Cisco Unified Communications Manager.
The CPU performance is impacted by MOH when active callers are on hold or when multicast MOH audio streams are configured.
Dedicated MOH server, 1000 held calls, 500 MOH sources with greeting and periodic announcements.
25–45% (7500 user OVA configuration)
Native call queuing with dedicated MOH server and annunciator server, 1000 queued calls, 500 MOH sources with greeting and periodic announcements. An annunciator can play up to 300 simultaneous greeting announcements.
25–45% (7500 user OVA configuration)
Dedicated MOH server, 500 held calls, 500 MOH sources with greeting and periodic announcements.
15–35% (7500 user OVA configuration)
When Cisco IP Voice Media Streaming application is co-resident with Cisco Unified Communications Manager on 2500 OVA (moderate call processing).
MOH: 500 held callers, 100 MOH sources, and 48 to 64 annunciator callers.
When Cisco IP Voice Media Streaming application is a dedicated server on 2500 OVA.
MOH: 750 held callers, 250 MOH sources, and 250 annunciator callers.
When Cisco IP Voice Media Streaming application is co-resident with Cisco Unified Communications Manager on 7500/10K OVA (moderate call processing).
MOH: 500 held callers, 250 MOH sources, and 128 annunciator callers.
When Cisco IP Voice Media Streaming application is a dedicated server on 7500/10K OVA.
Reduce annunciator to 300 for two MOH codecs.
These recommendations are specific to MOH/ANN devices. If you combine these devices with the software media termination point (MTP) and call forward busy (CFB) devices, reduce the limits to provide streams.
Configuration Limitations for Capacity Planning
The Cisco IP Voice Media Streaming application and Self Provisioning IVR services use a media kernel driver to create and control Real-time Transfer Protocol (RTP) streams. This media kernel driver has a capacity of 6000 streams. These streams allow the media devices and IVR to make resource reservations.
These reservations are based on the following capacity calculations:
(Call Count service parameter) * 3
Where 3 indicates total of receiving (RX) and transmitting (TX) calls for endpoint and 1 for .wav file.
Software Conference Bridge
(Call Count service parameter) * 2
Where 2 indicates total streams of RX and TX endpoints.
Software Media Termination Point
(Call Count service parameter) * 2
Where 2 indicates total streams of RX and TX endpoints.
((Maximum Half Duplex Streams) * 3) + (501 * 2 * [number of enabled MOH codecs])
(Maximum Half Duplex Streams) is a configuration setting on the MOH device configuration administration web page.
3 indicates total steams of RX, TX, and greeting announcement .wav file.
501 indicates the maximum number of Music On Hold (MOH) sources.
2 indicates music .wav stream and possible multicast TX stream.
[number of enabled MOH codecs] is based on how many MOH codecs are enabled in the Cisco IP Voice Media Streaming application service parameters.
Self Provisioning IVR Service
Where 500 indicates callers, and 2 indicates total streams from RX and TX streams.
Hence, to enable MOH to support a maximum of 1000 callers, use the following equation: 1000 * 3 + 501 * 2 * 1 = 4002 driver streams with one enabled codec and 1000 * 3 +501 * 2 * 2 = 5004 with two enabled codecs. Reduce the remaining devices and deactivate the Self Provisioning IVR service to limit total reservations to 6000, which allows the MOH device to make these reservations. It may also require that you do not activate the Self Provisioning IVR service on the same server with Cisco IP Voice Media Streaming application.
If configuration settings of the media devices exceed the capacity of the media device driver, the media devices that register with the device driver first will be able to reserve their required stream resources. The media devices that register later are restricted to fewer than requested stream resources. The later registered media devices result in logging some alarm messages and automatically reducing the call count for the restricted media device.
A media kernel driver with a capacity of 6000 streams might not support that many simultaneous media device connections.
Music On Hold Prerequisites
Before you configure multicast, ensure that you configure MOH server and audio sources. If you want to use fixed audio source, configure it before you configure multicast.
Make sure to decide whether you are going to do unicast or multicast Music On Hold
It is crucial to plan the capacity of the deployed and configured hardware and ensure that it can support the anticipated call volume of the network. You need to know the hardware capacity for MOH resources and consider the implications of multicast and unicast MOH in relation to this capacity. Ensure that network call volumes do not exceed these limits. When MOH sessions reach these limits, an additional load can result in poor MOH quality, erratic MOH operation, or loss of MOH functionality.
If you use multicast MOH and the devices that listen to multicast MOH streams are not in the same IP network, you must enable multicast routing in the IP network. Take care when you enable the multicast routing to avoid the potential flooding of parts of the network with wrongly sent multicast packets (specially, across WAN links). Disable multicasts on interfaces on which the multicast MOH packets are not required and use the Max Hops parameter.
For detailed information on planning your Music On Hold deployment, including server capacities, refer to the Music On Hold capacities topics in the Cisco Collaboration System Solution Reference Network Design .
Music On Hold Configuration Task Flow
Before you begin
Procedure
Configure Music On Hold server. See Configure Music On Hold Server.
Stream Music on Hold from Music On Hold data source files that are stored on their disks or external audio source.
Configure MOH audio. See Music On Hold Audio Source Configuration, and perform the following subtasks:
- Upload an MOH audio file. See Upload Audio File for Music On Hold.
- Convert MOH Files. See Convert Music On Hold Files.
- Configure MOH audio source. See Configure Music On Hold Audio Source.
Upload a Music On Hold audio file to make it available for use as a Music on Hold audio source.
Convert the Music On Hold file to the appropriate formats for use by the Music On Hold server.
To place on-net and off-net users on hold (end user hold or network hold) with music streamed from a streaming source.
(Optional) Configure fixed MOH audio source. See Configure Fixed Music On Hold Audio Source.
Configure the fixed MOH audio source in addition to the file stream sources.
Configure Media Resource Group. See Add MOH to Media Resource Group.
Define logical groupings of media servers.
Configure Media Resource Group list. See Configure Media Resource Group List.
Specify a list of prioritized media resource groups.
(Optional) Enable secured MOH through SRTP. See Enable Secured Music On Hold through SRTP.
When you enable the Cisco Unified Communications Manager cluster or system for security, the MOH server registers with the Cisco Unified Communications Manager as an SRTP-capable device.
Configure multicast by performing the following subtasks:
- Plan MOH Server capacity. See Plan Music On Hold Server Capacity.
- Verify Music On Hold service parameters. See Configure MOH Service Parameters.
- Configure multicast Music On Hold audio sources or fixed MOH audio source. See Configure Multicast Music On Hold Audio Sources/Fixed MOH Audio Source.
- Configure multicast Music On Hold server. See Configure Multicast Music On Hold Server.
- Configure a multicast-enabled media resource group. See Configure a Multicast-Enabled Media Resource Group.
- Configure multicast Music On Hold over H.323 intercluster trunks. See Configure Multicast Music On Hold over H.323 Intercluster Trunks.
(Optional) Reset or restart a Music On Hold server. See Reset or Restart a Music On Hold Server.
Reset or restart a music on hold server for changes to take effect, if required.
(Optional) Synchronize Music On Hold server. See Synchronize Music On Hold Server.
Apply configuration to the selected music on hold servers.
Activate Cisco IP Voice Media Streaming
The Cisco IP Voice Media Streaming Application service must be Activated in order to use Music On Hold.
During installation, Unified Communications Manager installs and configures a default Music On Hold audio source. Music On Hold functionality can proceed by using the default audio source.
Procedure
From Cisco Unified CM Administration, choose Tools > Service Activation .
Choose a server from the Server drop-down list.
Under CM Services , make sure the Cisco IP Voice Media Streaming App service is Activated . If the service is deactivated, check the service and click Save .
Configure Music On Hold Server
Before you begin
The Cisco Unified Communications Manager MOH server is automatically added when the Cisco IP Voice Media Streaming Application service is activated.
Procedure
From Cisco Unified CM Administration, choose Media Resources > Music On Hold Server .
Click Find and select the Music On Hold server that you want to update.
Select the Host Server .
Enter a descriptive Music On Hold Server Name along with a Description .
Select the Device Pool you want to use for this server.
Configure server capacity by configuring the following fields:
- Maximum Half Duplex Stream —Set this to the maximum number of devices that can be on unicast music on hold that is streamed from this music on hold server at any given time. You can use the following formula to calculate the maximum:
Note (Server and deployment capacity) – ([Number of multicast MOH sources] * [Number of enabled MOH codecs]) - Maximum Multi-cast Connections —Set this to a value that is greater than or equal to the number of devices that might be placed on multicast MOH at any given time.
(Optional) To enable multi-casting, check the Enable Multi-cast Audio Sources on this MOH Server check box, and configure the multicast IP address ranges.
Configure the additional fields in the Music On Hold Server Configuration window. For help with the fields and their settings, see the online help.
Music On Hold Server Fields for Music On Hold
Displays the registration information of the device.
Displays the IPv4 address.
Displays the IPv6 address.
Device is trusted
If the device is trusted, a green checkmark appears.
Displays the IP address of the existing host server.
Music On Hold Server Name
Enter a unique name for the MOH server. The name can comprise up to 15 characters. You can form the name by using letters, numbers, spaces, dashes, dots (periods), and underscores.
Enter a description for the MOH server. The description can include up to 50 characters. Ensure that this field does not contain ampersand (&), double quotes (“), brackets ([]), less than (<), greater than (>), or the percentage (%).
Choose a device pool for the Music On Hold server from the drop-down arrow and choose a device pool from the list that appears.
Use locations to implement call admission control (CAC) in a centralized call-processing system. CAC enables you to regulate audio quality and video availability by limiting the amount of bandwidth that is available for audio and video calls over links between locations. The location specifies the total bandwidth that is available for calls to and from this location.
From the drop-down list, choose the appropriate location for this MOH server.
The Hub_None location field indicates that the locations feature does not keep track of the bandwidth that this MOH server consumes. The Phantom location field indicates a location that enables successful CAC across intercluster trunks that use H.323 or SIP protocol.
To configure a new location, use the System > Location menu option.
Maximum Half Duplex Streams
Enter a number in this required field for the maximum number of unicast Music On Hold streams that this Music On Hold server supports. This value determines the maximum number of devices that can be on unicast Music On Hold that is streamed from this Music On Hold server at any given time. Valid values range from 0 to 1000.
Maximum Multi-cast Connections
Enter a number in this required field for the maximum number of multicast Music On Hold streams that this Music On Hold server supports. This value determines the maximum number of devices that can be on multicast music on hold that is streamed from this Music On Hold server at any given time. Valid values range from 1 to 999999.
Fixed Audio Source Device
Enter the device name of the fixed audio source device. This device serves as the per-server override that is used if the server has a special sound device installed.
Use Trusted Relay Point
From the drop-down list, enable or disable whether Cisco Unified Communications Manager inserts a trusted relay point (TRP) device with this media endpoint. Choose one of the following values:
Off —Disables the use of a TRP with this device.
On —Enables the use of a TRP with this device.
A trusted relay point (TRP) device designates an Media Transfer Protocol (MTP) or transcoder device that is labeled as Trusted Relay Point.
Cisco Unified Communications Manager places the TRP closest to the associated endpoint device if more than one resource is needed for the endpoint (for example, a transcoder or RSVPAgent).
If both TRP and MTP are required for the endpoint, TRP is used as the required MTP.
If both TRP and RSVPAgent are needed for the endpoint, Cisco Unified Communications Manager first tries to find an RSVPAgent that can also be used as a TRP.
If both TRP and transcoder are needed for the endpoint, Cisco Unified Communications Manager first tries to find a transcoder that is also designated as a TRP.
Use this required field to choose a run flag for the Music On Hold server. To do so, click the drop-down arrow and choose Yes or No. Choosing No disables the music on hold server.
Enable Multicast Audio Sources on this MOH Server
Check or uncheck this check box to enable or disable the multicast of audio sources for this Music On Hold server.
If this MOH server belongs to a multicast media resource group, a message asks you to enable multicast on this MOH server or to update the specified media resource groups either by removing this MOH server or by changing the multicast field of each listed group.
Base Multicast IP Address
If multicast support is needed, enter the base multicast IP address in this field. Valid IP addresses for multicast range from 224.0.1.0 to 239.255.255.255.
IP addresses between 224.0.1.0 and 238.255.255.255 are in the reserved range of IP multicast addresses for public multicast applications. Use of these addresses may interfere with existing multicast applications on the Internet. We strongly recommend using IP addresses that are in the range that is reserved for administratively controlled applications on private networks (239.0.0.0 – 239.255.255.255).
Base Multicast Port Number
If multicast support is needed, enter the base multicast port number in this field. Valid multicast port numbers include even numbers that range from 16384 to 32766.
Increment Multicast on
Click Port Number to increment multicast on port number.
Click IP Address to increment multicast on IP address.
Use multicast by incrementing IP address as the preferred method in firewall situations. This results in a unique IP address for each multicast audio source and helps to avoid network saturation.
This field designates Music On Hold audio stream number that is associated with a particular multicast audio source. Only audio sources that are defined as allowing multicasting appear.
Audio Source Name
This field designates the name of the audio source that is defined to allow multicasting.
For each multicast audio source, enter the maximum number of router hops through which multicast packets should pass. Valid values range from 1 to 127.
Using high values can lead to network saturation. This field also gets identified as Time to Live.
Music On Hold Audio Source Configuration
Upload Audio File for Music On Hold
Procedure
From Cisco Unified CM Administration, choose Media Resources > MOH Audio File Management .
Click Upload File .
Click Choose File and browse to the file you want to upload. Once you’ve selected the file, click Open .
The Upload Result window shows the result of the upload. The uploading procedure uploads the file and performs audio conversions to create codec-specific audio files for MOH. Depending on the size of the original file, processing may take several minutes to complete.
Click Close to close the Upload Result window.
Repeat this procedure if you want to upload additional audio files.
When you import an audio source file, Cisco Unified Communications Manager processes the file and converts the file to the proper formats for use by the Music On Hold server. Followoing are examples of valid input audio source files:
16-bit PCM .wav file
Sample rates of 48 kHz, 44.1 kHz, 32 kHz, 16 kHz, or 8 kHz
MOH audio source files do not automatically propagate to other MOH servers in a cluster. You must upload an audio source file to each MOH server or each server in a cluster separately
Convert Music On Hold Files
When you import an audio source file, Cisco Unified Communications Manager processes the file and converts the file to the proper formats for use by the Music On Hold server.
16-bit PCM .wav file
Sample rates of 48 kHz, 44.1 kHz, 32 kHz, 16 kHz, or 8 kHz
Before you begin
What to do next
Configure Music On Hold Audio Source
Use this procedure to configure Music On Hold audio sources. You can configure audio streams and associate uploaded files to an audio stream. You can configure up to 500 audio streams.
If a new version of an audio source file is available, perform the update procedure to use the new version.
Procedure
From Cisco Unified CM Administration, choose Media Resources > Music On Hold Audio Source .
Do either of the following:
- Click Find and select an existing audio stream.
- Click Add New to configure a new stream.
From the MOH Audio Stream Number , select an audio stream.
Enter a unique name in the MOH Audio Source Name field.
Optional. Check the Allow Multi-casting check box if you want to allow this file to be multi-casted.
Configure the audio source:
- Check the Use MOH WAV file source radio button and from the MOH Audio Source File , select the file you want to assign.
- Check the Rebroadcast External Multicast Source radio button and enter the multicast source IP Address details.
In the Announcement Settings for Held and Hunt Pilot Calls section, assign the announcements that you want to use for this audio source.
Configure the remaining fields in the Music On Hold Audio Source Configuration window. For help with the fields and their settings, see the online help.
Audio Source Fields for Music On Hold
MOH Audio Stream Number
Use this field to choose the stream number for this MOH audio source. Click the drop-down arrow and choose a value from the list. For existing MOH audio sources, the value appears in the MOH Audio Source title.
MOH Audio Source File
Use this field to choose the file for this MOH audio source. Click the drop-down arrow and choose a value from the list.
MOH Audio Source Name
Enter a unique name in this field for the MOH audio source. This name includes up to 50 valid characters, such as letters, numbers, spaces, dashes, dots (periods), and underscores.
Check this check box to specify that the selected MOH audio source allows multicasting.
MOH Audio Source File Status
This pane displays the following information about the source file for the selected MOH audio source:
