-
Cisco Unified SRST System Administrator Guide
-
Feature Roadmap
-
Overview
-
Setting Up the Network
-
Setting Up Cisco Unified IP Phones
-
Setting Up Call Handling
-
Configuring Toll Fraud Prevention
-
Configuring Additional Call Features
-
Integrating Cisco Unified Communications Manager and Cisco SRST to Use Cisco SRST as a Multicast MOH Resource
-
Setting Up Secure Survivable Remote Site Telephony
-
Integrating Voice Mail with Cisco Unified SRST
-
Setting Video Parameters
-
Monitoring and Maintaining Cisco Unified SRST
-
Configuring Enhanced 911 Services
-
Appendix A: Preparing Cisco Unified SRST Support
-
Index
-
Table Of Contents
Prerequisites for Using Cisco Unified SRST Gateways as a Multicast MOH Resource
Restrictions for Using Cisco Unified SRST Gateways as a Multicast MOH Resource
Information About Using Cisco Unified SRST Gateways as a Multicast MOH Resource
Cisco Unified SRST Gateways and Cisco Unified Communications Manager
Codecs, Port Numbers, and IP Addresses
How to Use Cisco Unified SRST Gateways as a Multicast MOH Resource
Configuring Cisco Unified Communications Manager for Cisco Unified SRST Multicast MOH
Configuring the MOH Audio Source to Enable Multicasting
Creating an MRG and an MRGL, Enabling MOH Multicast, and Configuring Gateways
Creating a Region for the MOH Server
Verifying Cisco Unified Communications Manager Multicast MOH
Configuring Cisco Unified SRST for Multicast MOH from an Audio File
Enabling Multicast MOH on the Cisco Unified SRST Gateway
Verifying Basic Cisco Unified SRST Multicast MOH Streaming
Verifying Cisco Unified SRST MOH to PSTN
Verifying Cisco Unified SRST Multicast MOH to IP Phones
Configuring Cisco Unified SRST for MOH from a Live Feed
Setting Up the Voice Port on the Cisco Unified SRST Gateway
Setting Up the Directory Numbers on the Cisco Unified SRST Gateway
Verifying Cisco Unified SRST MOH Live Feed
Configurations Examples for Cisco Unified SRST Gateways
MOH Routed to Two IP Addresses: Example
Feature Information for Cisco Unified SRST as a Multicast MOH Resource
Integrating Cisco Unified Communications Manager and Cisco Unified SRST to Use Cisco Unified SRST as a Multicast MOH Resource
Revised: February 4, 2009
This chapter describes how to configure Cisco Unified Communications Manager and Cisco Unified Survivable Remote Site Telephony (Cisco Unified SRST) to allow Cisco Unified Communications Manager to use Cisco Unified SRST gateways as multicast music-on-hold (MOH) resources during fallback and normal Cisco Unified Communications Manager operation. A distributed MOH design with local gateways providing MOH eliminates the need to stream MOH across a WAN and saves bandwidth.
Finding Feature Information in This Module
Your Cisco Unified CME version may not support all of the features documented in this module. For a list of the versions in which each feature is supported, see the "Feature Information for Cisco Unified SRST as a Multicast MOH Resource" section.
Contents
•
Prerequisites for Using Cisco Unified SRST Gateways as a Multicast MOH Resource
•
•
•
•
Prerequisites for Using Cisco Unified SRST Gateways as a Multicast MOH Resource
•
•
–
–
–
•
•
•
•
Restrictions for Using Cisco Unified SRST Gateways as a Multicast MOH Resource
•
•
•
•
•
Information About Using Cisco Unified SRST Gateways as a Multicast MOH Resource
To configure Cisco Unified SRST gateways as an MOH resource, you should understand the following concepts:
•
•
Cisco Unified SRST Gateways and Cisco Unified Communications Manager
Cisco Unified SRST gateways can be configured to multicast Real-Time Transport Protocol (RTP) packets from flash memory during fallback and normal Cisco Unified Communications Manager operation. To make this happen, Cisco Unified Communications Manager must be configured for multicast MOH so that the audio packets do not cross the WAN. Instead, audio packets are broadcast from the flash memory of Cisco Unified SRST gateways to the same multicast MOH IP address and port number configured for Cisco Unified Communications Manager multicast MOH. IP phones at remote sites are able to pick up RTP packets that are multicast from the local branch gateways instead of from the central Cisco Unified Communications Manager.
Multicast MOH for PSTN callers is supported when the Cisco Unified SRST router is used as the Cisco IOS voice gateway for Cisco Unified Communications Manager. In this state the Cisco Unified SRST function of the router remains in standby mode (no phones registered) with call control of the phones and gateway provided by Cisco Unified Communications Manager. This feature does not apply when the Cisco Unified SRST router is in fallback mode (phones are registered to Cisco Unified SRST). Instead, MOH is provided to PSTN callers via a direct internal path rather than through the multicast loopback interface.
Figure 1 shows a sample configuration in which all phones are configured by Cisco Unified Communications Manager to receive multicast MOH through port number 16384 and IP address 239.1.1.1. Cisco Unified Communications Manager is configured so that multicast MOH cannot reach the WAN, and local Cisco Unified SRST gateways are configured to send audio packets from their flash files to port number 16384 and IP address 239.1.1.1. Cisco Unified Communications Manager and the IP phones are spoofed and behave as if Cisco Unified Communications Manager were originating the multicast MOH.
Note
Figure 1 Multicast MOH from Cisco Unified SRST Flash Memory
Codecs, Port Numbers, and IP Addresses
Cisco Unified SRST multicast MOH supports G.711 only. Figure 2 shows an example in which G.711 is the only codec used by a central Cisco Unified Communications Manager and three branches. In some cases, a Cisco Unified Communications Manager system may use additional codecs. For example, for bandwidth savings, Cisco Unified Communications Manager may use G.711 for multicast MOH and G.729 for phone conversations.
As shown in the example in Figure 2, IP address 10.1.1.1 and port 1000 are used during phone conversations when G.729 is in use, and IP address 239.1.1.1 and port 16384 are used when a call is placed on hold and G.711 is in use.
Figure 2 IP Address and Port Usage for G.711 and G.729 Configuration
Figure 1 and Figure 2 show all branches using Cisco Unified SRST multicasting MOH. Figure 3 shows a case in which some gateways are configured with Cisco Unified SRST and other gateways are not. When the central site and Branch 3 phone users are put on hold by other IP phones in the Cisco Unified Communications Manager system, MOH is originated by Cisco Unified Communications Manager. When Branch 1 and Branch 2 phone users are put on hold by other phone users in the Cisco Unified Communications Manager system, MOH is originated by the Cisco Unified SRST gateways.
Figure 3 MOH Sources for Cisco Unified SRST and Other Unified SRST IP Phones Using MOH
To enable MOH audio packet transmission through two paths, the Cisco Unified Communications Manager MOH server must be configured with either one IP address and two different port numbers or one port address and two different IP multicast addresses so that one set of branches can use Cisco Unified SRST multicast MOH and the other can use Cisco Unified Communications Manager multicast MOH.
Multicast MOH Transmission
If Cisco Unified SRST multicast MOH is supported by all branches in a system, such as in Figure 1, Cisco Unified Communications Manager must be configured to keep all multicast MOH audio packets from reaching the WAN. When there is a mix of Cisco Unified SRST branches, as shown in Figure 3, one set of Cisco Unified Communications Manager MOH audio files must reach the WAN and another set must not. Audio packets from the central Cisco Unified Communications Manager must cross the WAN to reach branches running Cisco Unified Communications Manager. For branches running Cisco Unified SRST, the packets must not reach the WAN. For more information about Multicast MOH, see the "Configuring Cisco Unified SRST for Multicast MOH from an Audio File" section.
MOH from a Live Feed
MOH live feed provides live feed MOH streams from an audio device connected to an E&M or FXO port to Cisco IP phones in SRST mode. Music from a live feed is from a fixed source and is continuously fed into the MOH playout buffer instead of being read from a flash file.
Cisco Unified SRST is enhanced with the moh-live command. The moh-live command provides live feed MOH streams from an audio device connected to an E&M or FXO port to Cisco IP phones in SRST mode. Live feed MOH can also be multicast to Cisco IP phones. For more information about Cisco Unified SRST MOH live feed, see the "Configuring Cisco Unified SRST for MOH from a Live Feed" section.
MOH from Flash Files
The MOH Multicast from Flash Files feature facilitates the continuous multicast of MOH audio feed from files in the flash memories of Cisco Unified SRST branch office routers during Cisco Unified Communications fallback and normal Cisco Unified Communications service. Multicasting MOH from individual branch routers saves WAN bandwidth by eliminating the need to stream MOH audio from central offices to remote branches.
The MOH Multicast from Flash Files feature can act as a backup mechanism to the MOH live feed feature. Using the Flash to backup the live-feed is the recommend method rather than using just the live feed feature alone.
Cisco Unified Communications Manager MOH audio files must reach the WAN and another set must not. Audio packets from the central Cisco Unified Communications Manager must cross the WAN to reach branches running Cisco Unified Communications Manager. For branches running Cisco Unified SRST, the packets must not reach the WAN.
Table 1 provides a summary of options for MOH.
Table 1 Music on Hold (MOH)
Flash memory
No external audio input is required.
Configuring Cisco Unified SRST for Multicast MOH from an Audio File
Live feed
The multicast audio stream has minimal delay for local IP phones. The MOH stream for PSTN callers is delayed by a few seconds. If the live feed audio input fails, callers on hold hear silence.
Live feed and flash memory
The live feed stream has a few seconds of delay for both PSTN and local IP phone callers. The flash MOH acts as backup for the live-feed MoH.
We recommend this option if you want live-feed because it provides guaranteed MOH if the live-feed input is not found or fails.
Configuring Cisco Unified SRST for Multicast MOH from an Audio File
and
How to Use Cisco Unified SRST Gateways as a Multicast MOH Resource
To use Cisco Unified SRST gateways as a multicast MOH resource, perform the following tasks:
•
•
•
Configuring Cisco Unified Communications Manager for Cisco Unified SRST Multicast MOH
The following sections describe the Cisco Unified Communications Manager configuration tasks for Cisco Unified SRST multicast MOH:
•
•
•
•
To use Cisco Unified SRST gateways as multicast MOH resources, you must configure Cisco Unified Communications Manager to multicast MOH to the required branch sites. To accomplish this, you must configure IP addresses, port numbers, the MOH source, and the MOH audio server.
Even though the MOH routing is set up to prevent the Cisco Unified Communications Manager-sourced multicast MOH from actually reaching the WAN and the remote phones, the configured Cisco Unified Communications Manager MOH IP port and address information are still used by Cisco Unified Communications Manager to tell the phones which multicast IP address to listen to for MOH (for the MOH sourced by SRST).
Configuring the MOH server involves designating a maximum number of hops for the audio source. A configuration of one hop keeps Cisco Unified Communications Manager multicast MOH packets from reaching the WAN, thus spoofing Cisco Unified Communications Manager and allowing Cisco Unified SRST multicast MOH packets to be sent from Cisco Unified SRST gateways to their component phones. For cases in which Cisco Unified Communications Manager multicast must reach gateways that do not run Cisco Unified SRST, use the Cisco IOS ip multicast boundary command to control where multicast packets go.
After the MOH server is configured, the MOH server must be added to a Media Resource Group (MRG); the MRG is added to a Media Resource Group List (MRGL); and the designated Cisco Unified Communications Manager branch gateways are configured to use the MRGL.
Five Cisco Unified Communications Manager windows are used to configure the MOH server, audio source, MRG, MRGL, and individual gateways. Figure 4 provides an overview of this process.
The last Cisco Unified Communications Manager configuration task involves creating an MOH region that assigns MOH G.711 codec usage for the central site or sites and branch office or offices.
Regions specify the codecs that are used for audio and video calls within a region and between existing regions. For information about regions, see the "Region Configuration" section in the Cisco Unified Communications Manager Administration Guide. From the Cisco Unified Communications Manager documentation directory, click Maintain and Operate Guides and select the required Cisco Unified Communications Manager version to locate the administration guide for your version.
Figure 4 Unified Communications Manager Screens for Configuring Multicast MOH
Configuring the MOH Audio Source to Enable Multicasting
The MOH audio source is a file from which Cisco Unified Communications Manager transmits RTP packets. You can create an audio file or use the default audio file. For Cisco Unified SRST multicast MOH, only one audio source can be used, even if, for example, one out of 500 sites uses Cisco Unified SRST multicast MOH. In addition, all Cisco Unified Communications Manager systems must use the same audio source for user and network MOH because Cisco Unified SRST multicast MOH can stream audio only to a single multicast IP address and port. For Cisco Unified SRST multicast MOH, the Cisco Unified Communications Manager audio source file must be configured for G.711 bandwidth.
Tip
Whether you use a default Cisco Unified Communications Manager MOH audio source or you create one, the MOH audio source must be configured for multicasting in the Music On Hold (MOH) Audio Source Configuration window.
Note that the MOH Audio Source File Status section shows that the MOH audio source file is configured for four codec formats. If you are planning to use several codecs, ensure that the audio source file accommodates them.
For further information about the creation of an MOH audio source, see the Cisco Unified Communications Manager Administration Guide. From the Cisco Unified Communications Manager documentation directory, click Maintain and Operate Guides and select the required Cisco Unified Communications Manager version.
Use this procedure to configure the MOH audio source to enable multicasting and continuous play.
Note
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Step 1
Step 2
Step 3
Step 4
Enabling Multicast on the Cisco Unified Communications Manager MOH Server and Configuring Port Numbers and IP Addresses
Enter a base multicast IP address and port number in the Multicast Audio Source Information section of the Music On Hold (MOH) Server Configuration window. If you are using Cisco Unified Communications Manager multicast MOH and Cisco Unified SRST multicast MOH (see the "Codecs, Port Numbers, and IP Addresses" section and the "Multicast MOH Transmission" section), you must select a port and IP address increment method to configure for two sets of port numbers and IP address.
If the Increment Multicast on radio button is set to IP address, each MOH audio source and codec combination is multicast to different IP addresses but uses the same port number. If it is set to Port Number, each MOH audio source and codec combination is multicast to the same IP address but uses different destination port numbers.
Table 2 shows the difference between incrementing on an IP address and incrementing on a port number, using the base IP address of 239.1.1.1 and the base port number of 16384. The table also matches Cisco Unified Communications Manager audio sources and codecs to IP addresses and port numbers.
Incrementation is triggered by a change in codec usage. When codec usage changes, a new IP address or port number (depending on the incrementation selected) is assigned to the new codec type and is put into use. The original codec keeps its IP address and port number. For example, as seen in Table 2, if your baseline IP address and port number are 239.1.1.1 and 16384 for a G.711 mu-law codec and the codec usage changes to G.729 (triggering an increment on the port number), the IP address and port number in use changes, or increment, to 239.1.1.1 and 16386. If G.711 usage resumes, the IP address and port number returns to 239.1.1.1 and 16384. If G.729 is in use again, the IP address and port goes back to 239.1.1.1 and 16386, and so forth.
It is important to configure a Cisco Unified Communications Manager port number and IP address that use a G.711 audio source for Cisco Unified SRST multicast MOH. If Cisco Unified Communications Manager multicast MOH is also being used on gateways that do not have Cisco Unified SRST and use a different codec, such as G.729, ensure that the additional or incremental port number or IP address uses the same audio source as the Cisco Unified SRST gateways and the required codec.
The Music On Hold (MOH) Server Configuration window is also where the multicast audio source for the MOH server is configured. For Cisco Unified SRST multicast MOH, the Cisco Unified Communications Manager MOH server can use only one audio source. An audio source is selected by inputting the audio source's maximum number of hops.
The Max Hops configuration sets the length of the transmission of the audio source packets. Limiting the number of hops is one way to stop audio packets from reaching the WAN and thus spoofing Cisco Unified Communications Manager so Cisco Unified SRST can multicast MOH. If all of your branches run Cisco Unified SRST, use a low number of hops to prevent audio source packets from crossing the WAN. If your system configuration includes routers that do not run Cisco Unified SRST, enter a high number of hops to allow source packets to cross the WAN. Use the ip multicast bounder and access-list commands to keep resource packets from specific IP addresses from reaching the WAN.
Use this procedure to enable multicast and configure port numbers and IP addresses.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Step 1
a.
b.
c.
d.
Step 2
In the Music On Hold (MOH) Server Configuration window, enter an IP address in the Base Multicast IP Address field and enter a port number in the Base Multicast Port Number field. Ensure that the IP address and port number use the required audio source and codec. See Table 2.
Step 3
In the Music On Hold (MOH) Server Configuration window, in the Increment Multicast on field, choose Port Number if you want port numbers to be incremented and the IP address to remain unchanged. Choose IP Address if you want IP addresses to be incremented and the port number to remain unchanged.
•
•
Note
Step 4
In the Music On Hold (MOH) Server Configuration window, next to the Audio Source Name field, enter 1 in the Max Hops field if all of your branches run Cisco Unified SRST. If your system configuration includes routers that do not run Cisco Unified SRST, enter 16 in the Max Hops field.
Step 5
If all of your branches run Cisco Unified SRST, skip this step. If your system configuration includes routers that do not run Cisco Unified SRST and use a different codec, enter the following Cisco IOS commands starting from global configuration mode on the central site router:
a.
Enters interface configuration mode, where slot is the slot number and port is the port number.
b.
Configures an administratively scoped boundary, where access-list-number is a number from 1 to 99 that identifies an access list that controls the range of group addresses affected by the boundary.
c.
Exits interface configuration mode.
d.
Configures the access list mechanism for filtering frames by IP address. For the ip-address argument, enter the MOH IP address that you want to prevent from going over the WAN. Normally this would be the base IP address entered in Step 2.
The following is an example configuration:
Router(config)# interface serial 0/0Router(config-if)# ip multicast boundary 1Router(config-if)# exitRouter(config)# access-list 1 deny 239.1.1.1
Creating an MRG and an MRGL, Enabling MOH Multicast, and Configuring Gateways
The next task involves configuring individual gateways to use an MOH server that can transport the required MOH audio source to their IP phones on hold. This is accomplished by creating a Media Resource Group (MRG). An MRG references media resources, such as MOH servers. The MRG is then added to a Media Resource Group List (MRGL), and the MRGL is added to the phone and gateway configurations.
MRGs are created in the Media Resource Group Configuration window. MRGLs are created in the Media Resource Group List Configuration window. Phones are configured in the Phone Configuration window. Gateways are configured in the Gateway Configuration window.
Note
Add MRGL to a gateway or IP phone configuration by adding the MRGL to a device pool configuration. For further information about device pools, see the Cisco Unified Communications Manager Administration Guide. From the Cisco Unified Communications Manager documentation directory, click Maintain and Operate Guides and select the required Cisco Unified Communications Manager version.
Use the following procedure to create an MRG and MRGL, to enable MOH multicast, and to configure gateways.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Step 1
a.
b.
c.
d.
e.
This pane lists the media resources that can be chosen for an MRG and can include the following media resource types:
–
–
–
–
–
Music-on-hold servers that are configured for multicast are labeled as (MOH) [Multicast].
f.
g.
Step 2
a.
b.
c.
d.
e.
f.
Step 3
a.
b.
c.
d.
e.
Step 4
a.
b.
c.
d.
e.
Creating a Region for the MOH Server
To ensure that the MOH server uses G.711 for Cisco Unified SRST gateways, you must create a separate region for the MOH server. For more information about codecs, see the "Codecs, Port Numbers, and IP Addresses" section. For information about regions, see the Cisco Unified Communications Manager Administration Guide. From the Cisco Unified Communications Manager documentation directory, click Maintain and Operate Guides and select the required Cisco Unified Communications Manager version.
Configure the Region Configuration window. If the Cisco Unified Communications Manager system uses G.711 only, all of the central sites and their constituent branches for the MOH region must be set to G.711. If a Cisco Unified Communications Manager system has a combination of branches that do and do not run Cisco Unified SRST multicast MOH and the branches that do not run Cisco Unified SRST require a different codec for Cisco Unified Communications Manager multicast MOH, they must be configured accordingly.
A Region Configuration window where the "MOH Server" region is configured to use the G.711 and G.729 codecs might look like this:
•
•
•
Use the following procedure to create a region for the MOH server.
SUMMARY STEPS
1.
2.
DETAILED STEPS
Step 1
a.
b.
c.
d.
e.
f.
Step 2
Verifying Cisco Unified Communications Manager Multicast MOH
The Cisco Unified Communications Manager multicast MOH configuration must run correctly in order for Cisco Unified SRST multicast MOH to work. Verification of Cisco Unified Communications Manager multicast MOH differs for configurations using a WAN with multicast enabled and a WAN with multicast disabled.
You must verify that the Cisco Unified Communications Manager multicast MOH is provided through multicasting and not unicasting. Because unicast MOH is enabled by default, it is easy to mistakenly conclude that multicast MOH is working when it is not.
SUMMARY STEPS
1.
2.
DETAILED STEPS
Step 1
a.
b.
Step 2
a.
b.
c.
d.
Configuring Cisco Unified SRST for Multicast MOH from an Audio File
Note
Use the following procedures to configure Cisco Unified SRST for multicast MOH from an audio file.
•
•
•
•
Prerequisites
•
•
•
Note
•
•
Enabling Multicast MOH on the Cisco Unified SRST Gateway
No multicast MOH routing configuration is required for Cisco Unified SRST gateways because each Cisco Unified SRST gateway is configured to act as a host running an application that streams multicast MOH packets from the network. The multicast moh command declares the Cisco Unified Communications Manager multicast MOH address and port number and allows Cisco Unified SRST gateways to route MOH from flash memory to up to four IP addresses. If no route IP addresses are configured, the flash MOH is sent through the IP address configured in the Cisco Unified SRST
ip source-address command.SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
DETAILED STEPS
Step 1
ccm-manager music-on-hold
Example:Router(config)# ccm-manager music-on-hold
Enables the multicast MOH feature on a voice gateway.
Step 2
interface loopback number
Example:Router(config)# interface loopback 1
Configures an interface type and enters the interface configuration mode.
•
Step 3
ip address ip-address mask
Example:Router(config-if)# ip address 10.1.1.1 255.255.255.255
Sets a primary IP address for an interface.
•
•
Step 4
exit
Example:Router(config-if)# exit
Exits interface configuration mode.
Step 5
interface fastethernet slot/port
Example:Router(config)# interface fastethernet 0/0
(Optional if the route keyword is not used in the multicast moh command. See Step 9 and Step 13.) Configures an interface type and enters interface configuration mode.
Step 6
ip address ip-address mask
Example:Router(config-if)# ip-address 172.21.51.143 255.255.255.192
(Optional if the route keyword is not used in the multicast moh command. See Step 9 and Step 13.) Sets a primary IP address for an interface.
Step 7
exit
Example:Router(config-if)# exit
(Optional if the route keyword is not used in the multicast moh command. See Step 9 and Step 13.) Exits interface configuration mode.
Step 8
call-manager-fallback
Example:Router(config)# call-manager-fallback
Enters call-manager-fallback configuration mode.
Step 9
ip source-address ip-address [port port]
Example:Router(config-cm-fallback)# ip source-address 172.21.51.143 port 2000
(Optional if the route keyword is not used in the multicast moh command. See Step 13.) Enables a router to receive messages from Cisco Unified IP phones through the specified IP addresses and ports.
•
•
Step 10
max-ephones max-phones
Example:Router(config-cm-fallback)# max-ephones 1
Configures the maximum number of Cisco Unified IP phones that can be supported by a router.
•
Step 11
max-dn max-directory-number
Example:Router(config-cm-fallback)# max-dn 1
Sets the maximum possible number of virtual voice ports that can be supported by a router.
•
Step 12
moh filename
Example:Router(config-cm-fallback)# moh music-on-hold.au
Enables use of an MOH file.
•
Step 13
multicasting-enabled
Selects the multicast-enabled MOH audio source in the User Hold MOH Audio Source field on the Phone Configuration page in Cisco Unified Communications Manager Administration GUI.
Step 14
multicast moh multicast-address port port [route ip-address-list]
Example:Router(config-cm-fallback)# multicast moh 239.1.1.1 port 16386 route 239.1.1.2 239.1.1.3 239.1.1.4 239.1.1.5
Enables multicast of MOH from a branch office flash MOH file to IP phones in the branch office.
•
•
Step 15
exit
Example:Router(config-cm-fallback)# exit
Exits call-manager-fallback configuration mode.
Verifying Basic Cisco Unified SRST Multicast MOH Streaming
Use the following procedure to verify that multicast MOH packets are configured with the multicast moh command.
SUMMARY STEPS
1.
2.
3.
DETALED STEPS
Step 1
This command sets debugging for MOH. You can use this command to show that the Cisco Unified SRST gateway is multicasting MOH out of Loopback 0 and Fast Ethernet 0/0:
Router# debug ephone moh!MOH route If FastEthernet0/0 ETHERNET 172.21.51.143 via ARPMOH route If Loopback0 46 172.21.51.98 via 172.21.51.98!Step 2
Use this command to confirm that the interface output rates match one G.711 stream, which the show interfaces fastethernet output displays as 50 packets/sec and 80 kbps or more.
Router# show interfaces fastethernet 0/0!30 second output rate 86000 bits/sec, 50 packets/sec!Step 3
Use this command to verify that the Cisco IOS software was able to read the MOH audio file successfully.
Router# show ephone summary!File music-on-hold.au type AU Media_Payload_G.711Ulaw64k 160 bytes!
Troubleshooting Tips
The show ephone summary output should show a file type as either .au or .wav. If INVALID appears, an error exists.
Router# show ephone summary!File music-on-hold.au type INVALID Media_Payload_G.711Ulaw64k 160 bytes651-!An invalid output might be caused by the order in which the Cisco Unified SRST configuration commands are entered. Use the no call-manager-fallback command and reenter the multicast MOH commands. Rebooting may also clear the error.
Verifying Cisco Unified SRST MOH to PSTN
Use the following procedure to verify Cisco Unified Communications Manager control of MOH (the WAN link is up) and that multicast MOH packets transmit over a public switched telephone network (PSTN).
Note
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Step 1
Use a Cisco Unified SRST gateway IP phone to call a PSTN phone, and put the PSTN caller on hold. The PSTN caller should hear MOH.
Step 2
Use this command to verify that the MOH is multicast if you are using Windows and Cisco Unified Communications Manager version 4.3 or an earlier version. Note that the show ccm-manager music-on-hold command displays information about PSTN connections on hold only. It does not display information about multicast streams going to IP phones on hold. The following is an example of show ccm-manager music-on-hold command output.
Router# show ccm-manager music-on-holdCurrent active multicast sessions : 1Multicast RTP port Packets Call Codec IncomingAddress number in/out id Interface===================================================================239.1.1.1 16384 326/326 42 G.711ulaw Lo0If the PSTN caller hears MOH, and the show ccm-manager music-on-hold command displays no active multicast streams, the MOH is unicast. Confirm this by checking the MOH performance counters as discussed in the "Verifying Cisco Unified Communications Manager Multicast MOH" section.
Step 3
Use this command if H.323 is being used and no multicast address appears in the show ccm-manager music-on-hold command output to verify the H.323 handshaking between Cisco Unified Communications Manager and the Cisco Unified SRST gateway. When a PSTN caller is placed on hold, Cisco Unified Communications Manager sends an H.245 closeLogicalChannel, followed by an openLogicalChannel. Verify that the final openLogicalChannelAck from Cisco Unified Communications Manager to the Cisco Unified SRST gateway contains the expected multicast IP address and port number. In the following example, the IP address is EF010101 (239.1.1.1) and the port number is 16384.
Router# debug h245 asn*Mar 1 04:20:19.227: H245 MSC INCOMING PDU ::=value MultimediaSystemControlMessage ::= response : openLogicalChannelAck :{forwardLogicalChannelNumber 6forwardMultiplexAckParameters h2250LogicalChannelAckParameters :{sessionID 1mediaChannel unicastAddress : iPAddress :{network 'EF010101'HtsapIdentifier 16384}mediaControlChannel unicastAddress : iPAddress :{network 'EF010101'HtsapIdentifier 16385}}}Step 4
Use this command with the debug h245 asn command to further verify the H.323 handshaking between Cisco Unified Communications Manager and the Cisco Unified SRST gateway.
Router# show call active voice | include RemoteMediaRemoteMediaIPAddress=239.1.1.1RemoteMediaPort=16384The IP address and port number displayed must match the IP address and port number displayed by the debug h245 asn command. If the RemoteMediaIPAddress field displays 0.0.0.0, you probably have encountered caveat CSCdz00697. For more information, see the Cisco Bug ToolKit and the "Restrictions for Using Cisco Unified SRST Gateways as a Multicast MOH Resource" section.
Troubleshooting Tips
•
–
–
Note
Router# show ccm-manager music-on-holdCurrent active multicast sessions : 1Multicast RTP port Packets Call Codec IncomingAddress number in/out id Interface===================================================================239.1.1.1 16384 326/326 42 G.711ulaw Lo0*If no MOH streams are shown (that is, there are no rows of data beneath the columns), Cisco Unified Communications Manager was not correctly configured to provide the Cisco Unified SRST gateway with MOH. Configuration errors might include that the required codec has not been enabled on Cisco Unified Communications Manager (check the service parameters) and that no MRGL was assigned to the gateway, or, if one was assigned, it has insufficient resources. Check Cisco Intrusion Detection System (Cisco IDS) Event Viewer for error messages.
•
Use the show ccm-manager music-on-hold command to investigate.
Router# show ccm-manager music-on-holdCurrent active multicast sessions : 1Multicast RTP port Packets Call Codec IncomingAddress number in/out id Interface===================================================================239.1.1.1 16384 326/326 42 G.711ulaw Lo0 *–
–
–
–
–
For more information, see Step 9 in the "Enabling Multicast MOH on the Cisco Unified SRST Gateway" section.
Verifying Cisco Unified SRST Multicast MOH to IP Phones
To verify that Cisco Unified Communications Manager is signaling the IP phone to receive Cisco Unified SRST multicast MOH correctly, perform the following steps.
SUMMARY STEPS
1.
2.
DETAILED STEPS
Step 1
Use an IP phone to call a second IP phone, and put the second caller on hold. The second caller should hear MOH.
Step 2
Use the Performance window to check the MOHMulticastResourceActive and MOHUnicastResourceActive counters under the Cisco MOH Device performance object. See Step 2 in the "Verifying Cisco Unified Communications Manager Multicast MOH" section. For Cisco Unified SRST multicasting MOH to work, the multicast counter must increment.
Troubleshooting Tips
If no MOH is heard and the Cisco Unified SRST MOH signaling is multicasting, connect a sniffer to the PC port on the back of IP phone. If the IP phone and Cisco Unified SRST gateway are connected to the same subnet, multicast RTP packets must be detected at all times, even when the IP phone was not placed on hold. If the IP phone and the Cisco Unified SRST gateway are not connected to the same subnet, multicast RTP packets are detected only when the IP phone is placed on hold and sends an Internet Group Management Protocol (IGMP) Join to the closest router.
Configuring Cisco Unified SRST for MOH from a Live Feed
The following sections describe the configuration tasks for Cisco Unified SRST MOH live feed:
•
•
•
To configure MOH from a live feed, establish a voice port and dial peer for the call and then create a "dummy" phone or directory number. The dummy number allows for making and receiving calls, and the number is not assigned to a physical phone. It is that number that the MOH system autodials to establish the MOH feed.
The moh-live command allocates one of the virtual voice ports from the pool of virtual voice ports created by the max-dn command. The virtual voice port places an outgoing call to the dummy number; that is, the directory number specified in the moh-live command. The audio stream obtained from the MOH call provides the music-on-hold audio stream.
We recommend that the interface for live-feed MOH is an analog E&M port because it requires the minimum number of external components. Connect a line-level audio feed (standard audio jack) directly to pins 3 and 6 of an E&M RJ-45 connector. The E&M WAN interface card (WIC) has a built-in audio transformer that provides appropriate electrical isolation for the external audio source. (An audio connection on an E&M port does not require loop current.) The signal immediate and auto-cut-through commands disable E&M signaling on this voice port. A G.711 audio packet stream is generated by a digital signal processor (DSP) on the E&M port.
In Cisco IOS Release 12.4(15)T and later releases, you can directly connect a live-feed source to an FXO port if the signal loop-start live-feed command is configured on the voice port; otherwise, the port must connect through an external third-party adapter to provide a battery feed. An external adapter must supply normal telephone company (telco) battery voltage with the correct polarity to the tip and ring leads of the FXO port and it must provide transformer-based isolation between the external audio source and the tip and ring leads of the FXO port.
Music from a live feed is continuously fed into the MOH playout buffer instead of being read from a flash file, so there is typically a 2-second delay. An outbound call to an MOH live-feed source is attempted (or reattempted) every 30 seconds until the connection is made by the directory number that was configured for MOH. If the live-feed source is shut down for any reason, the flash memory source automatically activates.
A live-feed MOH connection is established as an automatically connected voice call that is made by the Cisco Unified SRST MOH system itself or by an external source directly calling in to the live-feed MOH port. An MOH call can be from or to the PSTN or can proceed via VoIP with voice activity detection (VAD) disabled. The call is assumed to be an incoming call unless the out-call keyword is used with the moh-live command during configuration.
The Cisco Unified SRST router uses the audio stream from the call as the source for the MOH stream, displacing any audio stream that is available from a flash file. An example of an MOH stream received over an incoming call is an external H.323-based server device that calls the directory number to deliver an audio stream to the Cisco Unified SRST router.
Prerequisites
Cisco Unified SRST for multicast MOH, as described in "Configuring Cisco Unified SRST for Multicast MOH from an Audio File" section, is not required for the MOH live-feed configuration. However, MOH live feed is designed to work in conjunction with multicast MOH.
Restrictions
•
•
•
•
Setting Up the Voice Port on the Cisco Unified SRST Gateway
Use the following procedure to activate MOH from a live feed and to set up and connect the physical voice port.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
DETAILED STEPS
Setting Up the Directory Numbers on the Cisco Unified SRST Gateway
After setting up the voice port, create a dial peer and give the voice port a directory number with the destination-pattern command. The directory number is the number that the system uses to access the MOH.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Step 1
dial-peer voice tag pots
Example:Router(config)# dial-peer voice 7777 pots
Enters dial-peer configuration mode.
Step 2
destination-pattern string
Example:Router(config-dial-peer)# destination-pattern 7777
Specifies the directory number that the system uses to create music on hold. This command specifies either the prefix or the full E.164 telephone number to be used for a dial peer.
Step 3
port port
Example:Router(config-dial-peer)# port 1/1/0
Associates the dial peer with the voice port that was specified in the "Setting Up the Voice Port on the Cisco Unified SRST Gateway" section.
Step 4
exit
Example:Router(config-dial-peer)# exit
Exits dial-peer configuration mode.
Establishing the MOH Feed
Use the following procedure to establish the MOH feed and connect the music source, such as a CD player, to autodial the directory number.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Step 1
call-manager-fallback
Example:Router(config)# call-manager-fallback
Enters call-manager-fallback configuration mode.
Step 2
max-dn max-directory-number
Example:Router(config-cm-fallback)# max-dn 1
Sets the maximum possible number of virtual voice ports that can be supported by a router.
•
Step 3
multicast moh multicast-address port port [route ip-address-list]
Example:Router(config-cm-fallback)# multicast moh
239.1.1.1 port 16386 route 239.1.1.2 239.1.1.3 239.1.1.4 239.1.1.5
Enables multicast of MOH from a branch office flash MOH file to IP phones in the branch office.
Note
•
•
Step 4
moh-live dn-number calling-number out-call outcall-number
Example:Router(config-cm-fallback)# moh-live dn-number 3333 out-call 7777
Specifies that this telephone number is to be used for an outgoing call that is to be the source for an MOH stream.
•
•
The outcall keyword makes a connection to the local router voice port that was specified in the "Setting Up the Voice Port on the Cisco Unified SRST Gateway" section.
Step 5
exit
Example:Router(config-cm-fallback)# exit
Exits call-manager-fallback configuration mode.
Verifying Cisco Unified SRST MOH Live Feed
To verify MOH live feed, use the debug ephone moh command and the other commands described in the "Verifying Basic Cisco Unified SRST Multicast MOH Streaming" section.
Configurations Examples for Cisco Unified SRST Gateways
This section provides the following configuration examples for Cisco Unified SRST gateways:
•
MOH Routed to Two IP Addresses: Example
The following example declares the Cisco Unified Communications Manager multicast MOH IP address 239.1.1.1 and port number 16384 and streams music-on-hold.au audio file packets out the interfaces that are configured with the IP addresses 10.1.1.1 and 172.21.51.143.
ccm-manager music-on-holdinterface Loopback0ip address 10.1.1.1. 255.255.255.255interface FastEthernet0/0ip address 172.21.51.143 255.255.255.192call-manager-fallbackip source-address 172.21.51.143 port 2000max-ephones 1max-dn 1moh music-on-hold.aumulticast moh 239.1.1.1 port 16384 route 172.21.51.143 10.1.1.1
Note
MOH Live Feed: Example
The following example configures MOH from a live feed. Note that the dial peer references the E&M port that was set with the voice-port command and that the dial peer number (7777) matches the outcall number configured with the out-call keyword of the moh-live command.
voice-port 1/0/0 input gain 3 auto-cut-through operation 4-wire signal immediate ! dial-peer voice 7777 pots destination-pattern 7777 port 2/0/0 ! ! call-manager-fallback max-conferences 8 max-dn 1 moh-live dn-number 3333 out-call 7777 ! ...Feature Information for Cisco Unified SRST as a Multicast MOH Resource
Table 3 lists the enhancements to the Cisco Unified SRST as a Mulitcast MOH Resource feature by version.
To determine hardware and software compatibility, see the Cisco Unified Communications Manager Compatibility Information page at the following URL:
http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_device_support_tables_list.htmlSee also the Cisco Unified Communications Manager Documentation Roadmaps at the following URL:
http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_documentation_roadmaps_list.htm.Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note
Where to Go Next
For information about monitoring and maintaining Cisco Unified SRST, see the "Monitoring and Maintaining Cisco Unified SRST" section on page 223.
For additional information, see the "Additional References" section on page 44 in the "Overview of Cisco Unified SRST" section on page 31.
