Cisco Unified SRST 4.0: Configuring Additional Call Features

Table Of Contents

Configuring Additional Call Features

Contents

Information About Configuring Additional Call Features

How to Configure Additional Call Features

Enabling Three-Party G.711 Ad Hoc Conferencing

Configuring MOH for G.711 VoIP and PSTN Calls

Configuring MOH from Flash Files

Defining XML API Schema

Where to Go Next

Configuring Additional Call Features

This chapter describe how to configure three-party G.711 ad hoc conferencing and music on hold (MOH) for Cisco Unified Survivable Remote Site Telephony (SRST).

Note Prior to version 4.0, the name of this product was Cisco SRST.

Note The Cisco IOS Voice Configuration Library includes a standard library preface, glossary, and feature and troubleshooting documents and is located at http://www.cisco.com/en/US/products/ps6441/prod_configuration_guide09186a0080565f8a.html.

Contents

• Information About Configuring Additional Call Features

• How to Configure Additional Call Features

• Where to Go Next

Information About Configuring Additional Call Features

Optional features available for configuration include three-party G.711 ad hoc conferencing and MOH. MOH is available from flash files on the Cisco Unified SRST router and for G.711, on-net VoIP, and PSTN calls.

For information on configuring MOH from a live feed, see the Configuring SRST MOH Live-Feed Support section at http://www.cisco.com/univercd/cc/td/doc/product/access/ip_ph/srs/srsinter/moh.htm.

Also available is an eXtensible Markup Language (XML) application program interface (API). This interface supplies data from Cisco Unified SRST to management software.

How to Configure Additional Call Features

This section contains the following tasks:

• Enabling Three-Party G.711 Ad Hoc Conferencing (Optional)

• Configuring MOH for G.711 VoIP and PSTN Calls (Optional)

• Configuring MOH from Flash Files (Optional)

• Defining XML API Schema (Optional)

Enabling Three-Party G.711 Ad Hoc Conferencing

Enabling three-party G.711 ad hoc conferencing involves configuring the maximum number of simultaneous three-party conferences supported by the Cisco Unified SRST router. For conferencing to be available, an IP phone must have a minimum of two lines connected to one or more buttons. See the "Configuring a Secondary Dial Tone" section on page 57.

SUMMARY STEPS

1. call-manager-fallback

2. max-conferences max-conference-numbers

3. exit

DETAILED STEPS

Command or Action

Purpose

Step 1

call-manager-fallback
Example:

Router(config)# call-manager-fallback

Enters call-manager-fallback configuration mode.

Step 2

max-conferences max-conference-numbers
Example:

Router(config-cm-fallback)# max-conferences 16

Sets the maximum number of simultaneous three-party conferences supported by the router. The maximum number possible is platform dependent:

•Cisco 1751 router—8

•Cisco 1760 router—8

•Cisco 2600 series routers—8

•Cisco 2600-XM series routers—8

•Cisco 2801 router—8

•Cisco 2811, Cisco 2821, and Cisco 2851 routers—16

•Cisco 3640 and Cisco 3640A routers—8

•Cisco 3660 router—16

•Cisco 3725 router—16

•Cisco 3745 router—16

•Cisco 3800 series router—24

Step 3

exit
Example:

Router(config-cm-fallback)# exit

Exits call-manager-fallback configuration mode.

Examples

The following example configures up to eight simultaneous three-way conferences on a router.

call-manager-fallback
max-conferences 8

Configuring MOH for G.711 VoIP and PSTN Calls

MOH configuration works with G.711 VoIP and PSTN calls only. For all other calls, such as internal calls between Cisco Unified IP Phones, a tone is heard. The MOH file can be in .wav or .au file format. However, the file format must contain 8-bit 8-kHz data, such as a-law or u-law data format.

The moh command allows you to specify the .au and .wav format music files that are played to callers who have been put on hold.

Prerequisites

You can obtain .au files from the Technical Support Software Download site at http://www.cisco.com/cgi-bin/tablebuild.pl/ip-iostsp. Copy the music-on-hold.au file to the flash memory on your Cisco Unified SRST router.

SUMMARY STEPS

1. call-manager-fallback

2. moh filename

3. exit

DETAILED STEPS

Command or Action

Purpose

Step 1

call-manager-fallback
Example:

Router(config)# call-manager-fallback

Enters call-manager-fallback configuration mode.

Step 2

moh filename
Example:

Router(config-cm-fallback)# moh jazz.wav

Enables MOH during G.711, on-net VoIP, and PSTN calls.

•filename—Filename of the music file.

Step 3

exit
Example:

Router(config-cm-fallback)# exit

Exits call-manager-fallback configuration mode.

Example

The following example enables the playing of an audio file called classical.au on G.711, on-net VoIP, and PSTN calls:

call-manager-fallback
moh classical.au

Configuring 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 CallManager fallback and normal Cisco Unified CallManager service. Multicasting MOH from individual branch routers saves WAN bandwidth by eliminating the need to stream MOH audio from central offices to remote branches.

Configuration for this feature involves configuring Cisco Unified SRST and Cisco Unified CallManager to work together, which is described in Integrating Cisco CallManager and Cisco SRST to Use Cisco SRST As a Multicast MOH Resource at http://www.cisco.com/univercd/cc/td/doc/product/access/ip_ph/srs/srsinter/moh.htm.

The MOH Multicast from Flash Files feature can act as a backup mechanism to the MOH live feed feature. 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. See the Configuring SRST MOH Live-Feed Support section at http://www.cisco.com/univercd/cc/td/doc/product/access/ip_ph/srs/srsinter/moh.htm.

Defining XML API Schema

The Cisco IOS commands in this section allow you to specify parameters associated with the XML API. For more information, refer to the XML Developer Guide for Cisco CME/SRST.

SUMMARY STEPS

1. call-manager-fallback

2. xmlschema schema-url

3. exit

DETAILED STEPS

Command or Action

Purpose

Step 1

call-manager-fallback
Example:

Router(config)# call-manager-fallback

Enters call-manager-fallback configuration mode.

Step 2

xmlschema schema-url
Example:

Router(config-cm-fallback)# xmlschema http://server2.example.com/
schema/schema1.xsd

Specifies the URL for an XML API schema to be used with this Cisco Unified SRST system.

•schema-url—Local or remote URL as defined in RFC 2396.

Step 3

exit
Example:

Router(config-cm-fallback)# exit

Exits call-manager-fallback configuration mode.

Where to Go Next

If you need to configure security, see the " Setting Up Secure Survivable Remote Site Telephony" chapter, or if you need to configure voicemail, see the " Integrating Voice Mail with Cisco Unified SRST" chapter. If you do not need any of those features, go to the "Monitoring and Maintaining Cisco Unified SRST" chapter.

	Command or Action	Purpose
Step 1	call-manager-fallback Example: Router(config)# call-manager-fallback	Enters call-manager-fallback configuration mode.
Step 2	max-conferences max-conference-numbers Example: Router(config-cm-fallback)# max-conferences 16	Sets the maximum number of simultaneous three-party conferences supported by the router. The maximum number possible is platform dependent: •Cisco 1751 router—8 •Cisco 1760 router—8 •Cisco 2600 series routers—8 •Cisco 2600-XM series routers—8 •Cisco 2801 router—8 •Cisco 2811, Cisco 2821, and Cisco 2851 routers—16 •Cisco 3640 and Cisco 3640A routers—8 •Cisco 3660 router—16 •Cisco 3725 router—16 •Cisco 3745 router—16 •Cisco 3800 series router—24
Step 3	`exit` Example: Router(config-cm-fallback)# exit	Exits call-manager-fallback configuration mode.