Cisco Unity Express VoiceMail and Auto Attendant CLI Administrator Guide

Configuring the SIP Proxy Server Location for Cisco Unity Express

The Session Initiation Protocol (SIP) proxy server resides on the router where Cisco Unified CME is installed. Cisco Unified CME can be installed on a different router from where the Cisco Unity Express hardware and software is installed. The SIP proxy server location information must be configured properly to enable all communications between Cisco Unity Express and Cisco Unified CME. The SIP proxy server also enables the message waiting indicators (MWIs) to work with the Cisco Unity Express voice-mail application.

Required Data for This Procedure

The following information is required to configure the SIP proxy server:

• Hostname or IP address of the router where the SIP proxy server resides
• UDP port of the router where the SIP proxy server resides

SUMMARY STEPS

1. config t

2. ccn subsystem sip

3. gateway address ip-address

4. gateway port port-number

5. end

6. show ccn subsystem sip

7. copy running-config startup-config

DETAILED STEPS

Examples

The following example illustrates the show ccn subsystem sip output, which displays the SIP gateway IP address and SIP port number:

Configuring the Call Transfer Mode

Cisco Unity Express permits configuration of attended and semiattended call transfer modes in addition to blind transfers.

SUMMARY STEPS

1. config t

2. ccn subsystem sip

3. transfer-mode { attended | semi-attended | blind refer | blind bye-also ]}

4. end

5. show ccn subsystem sip

DETAILED STEPS

Examples

The following is example output of the show ccn subsystem sip command.

Configuring DTMF Options

The listed options are available for handling incoming and outgoing DTMF signals for SIP calls from Cisco Unified CME and Cisco SRST mode.

Cisco Unity Express provides the following options for transferring DTMF signals for incoming and outgoing SIP calls.

• rtp-nte —Uses the media path to relay incoming and outgoing DTMF signals.

To use the rtp-nte option, verify that the Cisco IOS SIP gateway is configured to use RTP-NTE for SIP calls, as shown in the following example:

• sub-notify —Uses Subscribe and Notify messages to relay incoming DTMF signals to Cisco Unity Express. This option is not available for outgoing DTMF signals from Cisco Unity Express.
• info —Uses the Info message to relay outgoing DTMF signals from Cisco Unity Express to the Cisco IOS SIP gateway. This option is not available for incoming DTMF signals to Cisco Unity Express.
• sip-notify —Uses Unsolicited-Notify messages for incoming and outgoing DTMF signals.

To use the sip-notify option, verify that the Cisco IOS SIP gateway is configured to use Unsolicited NOTIFY for SIP calls, as shown in the following example:

You can configure more than one option for transferring DTMF signals. The order in which you configure the options determines their order of preference.

Table 5-1 shows the various option combinations, the remote end capability, and the signaling option for incoming and outgoing DTMF signals.

SUMMARY STEPS

1. config t

2. ccn subsystem sip

3. dtmf-relay { rtp-nte | sub-notify | info | sip-notify }

To configure more than one signal option, specify them using a single dtmf-relay command.

4. end

5. show ccn subsystem sip

DETAILED STEPS

Examples

The following example displays the output of the show ccn subsystem sip command.

Configuring the MWI Notification Option

Cisco Unity Express expands MWI status update capability to include Cisco Unified Communications Manager and Cisco SRST mode. Three notification options are available:

• Outcall Notification (Not Available in Cisco SRST Mode)
• Sub-Notify Notification
• Unsolicited Notification

From the GUI, select Voice Mail > Message Waiting Indicators > Settings to configure the MWI notification option.

Outcall Notification (Not Available in Cisco SRST Mode)

Only Cisco Unified CME can use the SIP outcall mechanism for generating MWI notifications. Outcall will not work in Cisco SRST mode.

Note If the MWI notification option is outcall, configure the MWI on and off extensions. See Configuring the MWI On and Off Extensions (Not Available in Cisco SRST Mode).

The outcall option is available for backward compatibility. We recommend that you use either sub-notify or unsolicited for the MWI notification option.

To use the outcall option, Cisco Unified CME must configure two ephone-dns that are registered to receive MWI notifications as follows:

Note The number of dots in the above example must be equal to the extension length of the phones connected to Cisco Unified CME.

Sub-Notify Notification

Both Cisco Unified CME and Cisco Unified Communications Manager in SRST mode can use the sub-notify mechanism for generating MWI notifications. With this mechanism, the MWI notifications will reflect the accurate status of messages in a subscriber’s voice mailbox.

After an ephone-dn is configured with the sub-notify option, Cisco Unified CME sends a Subscribe message to Cisco Unity Express to register the phone for MWI notifications. When a new voice message arrives in the voice mailbox for the ephone-dn, Cisco Unity Express updates the MWI status. If Cisco Unity Express does not receive the Subscribe message for the ephone-dn, Cisco Unity Express will not update the MWI status when a new message arrives.

To use the sub-notify option, Cisco Unified CME must configure each ephone-dn that is registered to receive MWI notifications as follows:

For Cisco IOS Releases Prior to 12.3(11)T7

For Cisco IOS Releases 12.3(11)T7 and Later Releases

For Cisco SRST Mode

Note The SIP server IP address used in these commands must be the IP address of Cisco Unity Express. In the examples shown above, this is 10.100.9.6.

Unsolicited Notification

Both Cisco Unified CME and Cisco Unified Communications Manager in SRST mode can use the unsolicited mechanism for generating MWI notifications. With this mechanism, the MWI notifications will reflect the accurate status of messages in a subscriber’s voice mailbox.

The unsolicited option does not require Cisco Unified CME to send a subscription request for each ephone-dn to Cisco Unity Express for MWI notifications. Cisco Unity Express sends Notify messages to Cisco Unified CME whenever the voice mailbox for any ephone-dn receives a new message. In this way, the MWI status reflects the current voice mailbox message status.

To use the unsolicited option, Cisco Unified CME must configure each ephone-dn that is registered to receive MWI notifications as follows:

For Cisco IOS Releases Prior to 12.3(11)T7

For Cisco IOS Release 12.3(11)T7 and Later Releases

Note The SIP server IP address used in these commands must be the IP address of Cisco Unity Express. In the examples shown above, this is 10.100.9.6.

SUMMARY STEPS

1. config t

2. ccn subsystem sip

3. mwi sip { outcall | sub-notify | unsolicited }

4. end

5. show ccn subsystem sip

DETAILED STEPS

Examples

The following example displays the output of the show ccn subsystem sip command.

Configuring the MWI On and Off Extensions (Not Available in Cisco SRST Mode)

Cisco Unity Express uses the MWI on and off extensions with the affected telephone extension to generate a SIP call to Cisco Unified CME, which changes the status of the telephone’s MWI light.

This configuration is required only if the MWI notification option is configured as outcall. (See the earlier section Configuring the MWI Notification Option.)

Prerequisites

Verify that the MWI on and off extensions are configured on Cisco Unified CME; otherwise, the MWI light will not work.

Required Data for This Procedure

The following information is required to configure the MWI on and off extensions:

• Extension number dedicated to the MWI on extension
• Extension number dedicated to the MWI off extension

SUMMARY STEPS

1. config t

2. ccn application ciscomwiapplication

3. parameter strMWI_ON_DN on-extension

4. parameter strMWI_OFF_DN off-extension

5. end

6. copy running-config startup-config

DETAILED STEPS

Configuring the Inclusion of Envelope Information in SIP MWI Notifications

To determine whether envelope information is included in SIP MWI notifications, use the mwi envelope-info command.

Enabling the inclusion of envelope information in SIP MWI notifications does not effect whether Cisco Unity Express accepts MWI subscriptions that request envelope information. It only determines whether envelope information is not included in SIP MWI notifications and it effects only the content of MWI messages generated by Cisco Unity Express. Disabling the inclusion of envelope information does not terminate existing MWI subscriptions. After it is enabled, subsequent MWI notifications include envelope information for any existing MWI subscription that requested with envelope information

Prerequisites

• Cisco Unity Express 3.2 or a later version
• The mwi envelope-info command is relevant only when the mwi sip sub-notify command is used. For more information about the mwi sip sub-notify command, see the earlier section Configuring the MWI Notification Option.)

SUMMARY STEPS

1. config t

2. ccn subsystem sip

3. mwi envelope-info

4. end

5. copy running-config startup-config

DETAILED STEPS

Configuring Centralized Cisco Unity Express

Available in Cisco Unity Express 3.2 and later versions, the centralization feature enables the Cisco Unity Express NME or Cisco Unity Express SM-SRE-700-K9 to interoperate with up to ten Cisco Unified CME systems.

Note The Cisco Unity Express AIM-CUE/AIM2-CUE, NM-CUE, NM-CUE-EC and ISM-SRE-300-K9 modules support only one Cisco Unified CME system.

Geographically dispersed Cisco Unified CME systems can be connected to Cisco Unity Express across a WAN link. Cisco Unity Express can be co-located with one of these Cisco Unified CME systems, although it is not required.

Figure 5-1 Centralized Cisco Unity Express Deployment Topology

To interconnect more than ten Cisco Unified CME systems, you can use Cisco Unified Messaging Gateway to interconnect multiple Cisco Unity, Cisco Unity Express, and third party messaging systems.

Note Cisco Unity Express does not support importing and/or managing Cisco Unified CME Extension Mobility (EM) users, only ephone users.

To receive the greatest benefit from the centralization feature, you must configure a single central Cisco Unified CME gateway to manage the company’s dial-plan. This central Cisco Unified CME gateway is called the “local” site and is a predefined site on the system. The local site cannot be deleted.

Cisco Unity Express uses one SIP gateway for all outgoing calls and faxes. This SIP gateway must be aware of the company’s dial-plan and be capable of routing calls from Cisco Unity Express to any Cisco Unified CME in the network. This gateway is configured independently of the sites, but by default, it routes to the Cisco Unified CME at the local site.

If you plan to use Outcall or Unsolicited Notify for MWI, the MWI relay must be enabled on the central (local) Cisco Unified CME and the other Cisco Unified CME routers must subscribe to this one. The central one will keep track of which numbers are defined where and pass on the MWI messages accordingly.

If you plan to use Subscribe-Notify for MWI, then the individual gateways must use Cisco Unity Express as their MWI server.

Note Cisco Unity Express does not support automatic MWI synchronization if the WAN link between Cisco Unity Express and Cisco Unified CME is disrupted. You must manually synchronize the MWI if it is out of synch.

The detailed MWI relay design guide, the MWI Relay section of the Cisco Unified Communications Manager Express Solution Reference Network Design Guide, is located at http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/srnd/design/guide/cmesrnd.html .

The commands listed in the following are not available when Cisco Unity Express is working in Cisco Unified Communications Manager mode.

The following instructions describe how t o provision Cisco Unified CME sites:

– Defining a Cisco Unified CME Site (Site Provisioning)

– Deleting a Cisco Unified CME Site

Note The following procedures replace the following EXEC mode command found in Cisco Unity Express 3.1 and earlier versions, whose purpose was to provision the single Cisco Unified CME it supported:
web admin cme hostname [hostname] username [username] password [password].
Although this command has not been deprecated, when you have multiple Cisco Unified CME systems, this command will apply only to the central (local) site.

Defining a Cisco Unified CME Site (Site Provisioning)

Prerequisites

Cisco Unity Express 3.2 or a later version

SUMMARY STEPS

1. config t

2. site name [ site-name | local ]

3. site-hostname hostname

4. description “text ”

5. web username username password password

6. web credentials hidden username-password-hash

7. xml username username password password

8. xml credentials hidden username-password-hash

9. exit

10. username username site site-name

11. end

12. show site [ site-name ]

13. show users site [site-name]

DETAILED STEPS

Deleting a Cisco Unified CME Site

The following configuration mode command deletes a site. You cannot delete the local site.

no site name site-name

The syntax for the site name is the same as the username, containing letters, numbers, hyphens, and/or dots, maximum 32 characters.

Example

The following example illustrates some of the configurations described above.

Configuring FAX Support for Centralized Cisco Unity Express

Prerequisites

Cisco Unity Express 3.0 or a later version

SUMMARY STEPS

1. config t

2. fax gateway inbound address {ip-address | hostname}

3. fax print E164-number site sitename

4. end

5. show fax configuration

DETAILED STEPS

Examples

The following example configures the inbound fax gateway IP address:

The following example sets the site’s fax number to 555-0112:

The following is sample output for the show fax configuration command if only one site is configured:

The following is sample output for the show fax configuration command if more than one site is configured:

Configuring NonSubscriber Distribution Lists for Centralized Cisco Unity Express

To configure NonSubscriber Distribution Lists for Centralized Cisco Unity Express, see Configuring Public Distribution Lists.

Configuring Cisco Unified CME SIP Options for RFC Compliance

Cisco Unity Express provides the protocol command to ensure compatibility with all Cisco IOS releases. Cisco IOS Release 12.4(2)T and earlier releases are not RFC 3261 compliant. The lack of compliance causes the Cisco Unity Express software not to interoperate properly with those older Cisco IOS releases when sip-notify or sub-notify are used for DTMF.

Required Data for This Procedure

The release number of the Cisco IOS software running on your call control platform.

SUMMARY STEPS

1. config t

2. ccn subsystem sip

3. protocol { pre-rfc3261 | rfc3261 }

4. end

5. show ccn subsystem sip

DETAILED STEPS

Example

The following example sets the SIP option to RFC 3261 for call platforms using Cisco IOS Release 12.4(2)T or a later release.

Following is example output of the show ccn subsystem sip command.

Prerequisites

To use a separate CTI port for MWI, you must have 3.2 or later releases.

Required Data for This Procedure

The following information is required to configure the JTAPI parameters:

• IP address or hostname for the primary, secondary, and tertiary Cisco Unified Communications Manager servers
• JTAPI user ID and password from Cisco Unified Communications Manager. The password is case sensitive. These values must match the JTAPI user ID and password that were configured on Cisco Unified Communications Manager.
• List of CTI ports
• To use a separate CTI port for MWI, a list of DNs that are assigned on Cisco Unified Communications Manager and are under the control of Cisco Unity Express JTAPI application user.

Note If you are using Cisco Unified Communications Manager 5.0 or a later version, verify that the AXL service is active. To do this, go to the Cisco Unified Communications Manager serviceability website, click on Tools > Service Activation. Look for Cisco AXL Web service.

SUMMARY STEPS

1. config t

2. ccn subsystem jtapi

3. ccm-manager address {primary-server-ip-address | primary-server-hostname} { secondary-server-ip-address | secondary-server-hostname }
{ tertiary-server-ip-address | tertiary-server-hostname }

4. ccm-manager username jtapi-user-id password jtapi-user-password

5. ctiport cti-port-number

6. mwiport dn-number

7. redirect-css cti-port { ccm-default | calling-party | redirecting-party }

8. redirect-css route-point { ccm-default | calling-party | redirecting-party }

9. end

10. show ccn subsystem jtapi

11. copy running-config startup-config

DETAILED STEPS

Examples

Following is example output of the show ccn subsystem jtapi command:

se-10-0-0-0# show ccn subsystem jtapi

Creating a Script File

To create a script file, use the Cisco Unity Express Editor software. See to the Cisco Unity Express Guide to Writing Auto-Attendant Scripts for guidelines and procedures for creating a script file.

The file cannot be larger than 256 KB. Starting with Cisco Unity Express 3.1, script files can also be created using Editor Express. Editor Express can be accessed using the GUI option System > Scripts > New.

Note Cisco Unity Express Editor Express provides only a subset of the functionality that is available the Cisco Unity Express Script Editor. Use Cisco Unity Express Editor Express for simple call-flow customizations only.

After creating the script, use the GUI or Cisco Unity Express ccn copy command to upload the file to the Cisco Unity Express module. See the next section, “Uploading a Script File,” for the upload procedure.

Note If you create your script using Cisco Unity Express Editor Express, you do not need to upload because it is directly saved on the Cisco Unity Express module.

Uploading a Script File

After creating the AEF file, upload the file using the ccn copy url command in Cisco Unity Express EXEC mode:

ccn copy url ftp:// source-ip-addres s/script-filename.aef script script-filename.aef [username username password password]

This command is equivalent to using the GUI option Voice Mail > Scripts and selecting Upload.

An error message appears if you try to upload more than the maximum number of scripts allowed on your Cisco Unity Express module.

Displaying the List of Existing Scripts

To displays details of the script files existing on the module, use the following command in Cisco Unity Express EXEC mode:

show ccn scripts

Downloading a Script File

Scripts can be copied from the auto-attendant and stored on another server or PC.

To download or copy a script file, use the ccn copy script command in Cisco Unity Express EXEC mode:

ccn copy script script-filename url ftp:// destination-ip-addres s / script-filename

Deleting a Script File

To delete an auto-attendant script file from Cisco Unity Express, use the ccn delete command in Cisco Unity Express EXEC mode:

ccn delete script script-filename

Recording a Prompt File

Two methods are available to create prompt files:

• Create a wav file with the following format: G.711 u-law, 8 kHz, 8 bit, Mono. The file cannot be larger than 1 MB (about 2 minutes). After recording the wav file, use the GUI or Cisco Unity Express CLI ccn copy url command to copy or upload the file to the Cisco Unity Express module. See the next section, “Uploading a Prompt File,” for the upload procedure.
• Cisco Unity Express provides an in-built application called Administration via Telephone (AvT), which lets you record customized prompt files directly on the module using a telephone. For details on how to configure and use AvT, see the chapter Configuring the Administration via Telephone Application.

We recommend using the AvT on the TUI to record greetings and prompts because the AvT provides higher sound quality compared to.wav files recorded using other methods.

Uploading a Prompt File

After recording the.wav prompt file, upload the file using the ccn copy url command in Cisco Unity Express EXEC mode:

ccn copy url source-ip-addres s prompt prompt-filename [ language xx_YY ] [ username name password password ]

where prompt-filename is the file to be uploaded, xx_YY is the language of the prompt file, name is the FTP server login ID, and password is the FTP server password.

The optional language parameter lets you specify the language directory in which you want the prompt to be uploaded. An error message appears if the language specified in the command is not installed on the module. If the language parameter is omitted in this CLI command, the prompt is uploaded to the default system language directory.

This command is equivalent to using the GUI option Voice Mail > Prompts and selecting Upload.

An error message appears if you try to upload more than the maximum number of prompts allowed on your Cisco Unity Express module.

Displaying Existing Prompt File lists

To display details of the prompt files existing on the module, use the following command in Cisco Unity Express EXEC mode:

show ccn prompts [language xx_YY ]

The optional language parameter lets you specify the language directory from which the prompts will be listed. If the language parameter is omitted in this CLI command, then prompts from all language directories are listed.

Downloading a Prompt File

Prompts can be copied from the Cisco Unity Express module and stored on another server or PC.

To copy or download a prompt file, use the ccn copy prompt command in Cisco Unity Express EXEC mode:

ccn copy prompt prompt-filename url ftp: // destination-ip-addres s / prompt-filename [ language xx_YY ] [ username name password password ]

where prompt-filename is the file to be downloaded, destination-ip-address is the IP address of the FTP server, xx_YY is the language directory from which the prompt file is to be downloaded, name is the FTP server login ID, and password is the FTP server password.

Renaming a Prompt File

To rename a prompt file already existing on the Cisco Unity Express module, use the ccn rename prompt command in Cisco Unity Express EXEC mode:

ccn rename prompt old-name new-name [ language xx_YY ]

where old-name is the existing filename and new-name is the revised name, and xx_YY is the language directory in which the prompt to be renamed resides. If the language parameter is omitted in this CLI command, the system renames the prompt old-name from the default system language directory.

An error message appears if the prompt old-name does not exist in that language directory.

se-10-0-0-0# ccn rename prompt AAmyprompt.wav AAmyprompt2.wav

Deleting a Prompt File

To delete a prompt file from the Cisco Unity Express module, use the ccn delete command in Cisco Unity Express EXEC mode:

ccn delete prompt prompt-filename [ language xx_YY ]

where prompt-filename is the file to be deleted, and xx_YY is the language directory from which the prompt is to be deleted. If the language parameter is omitted from this CLI command, the system attempts to delete this prompt from the default system language directory.

An error message appears if the prompt prompt-filename does not exist in that language directory.

Rerecording a Prompt File

You can rerecord existing prompt files using the AvT application.

For details on how to rerecord prompts using AvT, see the “Configuring the Administration via Telephone Application” section.

Creating and Modifying Applications

Use the following procedure to create or modify an application.

Required Data for This Procedure

• Application name.
• Script name for the application.
• Maxsessions value. See the “Sharing Ports Among Applications and Triggers” section.
• Name and value for each parameter that the script requires. These may vary, depending on the script that you have created.

Note For more information about creating scripts, see the Cisco Unity Express Guide to Writing Scripts.

SUMMARY STEPS

1. config t

2. ccn application full-name [ aa | ivr ]

3. default [description | enabled | maxsessions | script | parameter name]

4. description “ text ”

5. maxsessions number

6. no [description | enabled | maxsessions | script | parameter name]

7. parameter name “ value ”

8. script name

9. enabled

10. end

11. show ccn application [ aa | ivr ]

12. copy running-config startup-config

DETAILED STEPS

Examples

The following example illustrates the show ccn application output:

Script Parameters for Applications

While creating a script with Cisco Unity Express Script Editor, you can specify some script variables to be “parameters.” The value of these “parameters” can be easily modified using the Cisco Unity Express configuration commands, without the need to edit the script using the Cisco Unity Express Script Editor. This has two benefits:

• You can deploy the same script at multiple locations and still customize the script flow to some extent for that particular location without needing different scripts for different locations. For example, you can create a simple script which welcomes the caller by playing a prompt such as “Welcome to ABC stores,” and then transfers the caller to the operator. You can specify this welcome prompt and the operator extension as script parameters while creating the script. Then you can deploy the same script at multiple locations and change the welcome prompt and operator extension by using the Cisco Unity Express configuration commands.
• You can create multiple applications using the same script, but with different values for the script parameters, thereby allowing you to provide a different experience to the caller depending on the application being invoked.

To view a list of script parameters, create an application using that script, and then use the show ccn application command to display the list of parameters and their default values.

To change the value of these parameters, see Step 7 in Creating and Modifying Applications.

Deleting an Application

If you have an application that you do not want to keep, use this procedure to delete the application and any triggers associated with that application.

After you delete the application and triggers, the script associated with the application still remains installed on the Cisco Unity Express module.

The following system applications ship with Cisco Unity Express, and cannot be deleted:

• autoattendant
• ciscomwiapplication
• msgnotification
• promptmgmt (the AvT application)
• voicemail

Required Data for This Procedure

The following information is required to delete an application:

• Application name
• All trigger numbers or URL names associated with the application

SUMMARY STEPS

1. show ccn application

2. show ccn trigger

3. config t

4. no ccn trigger [sip | jtapi | http] phonenumber number

5. no ccn application name

6. exit

7. show ccn application

8. show ccn trigger

9. copy running-config startup-config

DETAILED STEPS

Examples

The following is sample output from the show ccn application and show ccn trigger commands:

The following configuration deletes the auto-attendant application and its trigger:

Now the output of the show commands looks similar to the following:

Configuring SIP Triggers for the Applications

Cisco Unity Express uses SIP to handle incoming calls in Cisco Unified CME and Cisco SRST mode. If you are deploying Cisco Unity Express in either of these modes, you must configure a SIP trigger for your application so that it can be invoked by incoming calls. This type of trigger is identified by the phone number which is dialed to invoke the desired application.

The telephone number that identifies your SIP trigger must match the dial-peer configured on the Cisco IOS SIP gateway. In order for Cisco Unity Express to be able to handle incoming calls on this phone number properly, you must configure the dial-peer on the Cisco IOS SIP gateway as follows:

Note Make sure that VAD is turned OFF on the dial-peer, it is configured to use g711ulaw codec and the session target is pointing to the Cisco Unity Express module.

Cisco Unity Express supports a maximum of 8 SIP triggers for all applications combined, regardless of the hardware type.

Required Data for This Procedure

The following information is required to configure the SIP triggers for applications:

• Telephone number that invokes the application. The number must be different for different applications. The number value must match one of the patterns configured in the destination-pattern field of the SIP dial peer pointing to Cisco Unity Express.
• Maximum number of callers that can access the trigger simultaneously. See Sharing Ports Among Applications and Triggers for guidelines on assigning this value.

SUMMARY STEPS

1. config t

2. ccn trigger sip phonenumber number

3. application application-name

4. enabled

5. maxsessions number

6. locale xx_YY

7. end

8. show ccn trigger

9. copy running-config startup-config

DETAILED STEPS

	Command or Action	Purpose
Step 1	config t   se-10-0-0-0(config)# config t	Enters configuration mode.
Step 2	ccn trigger sip phonenumber number   se-10-0-0-0(config)# ccn trigger sip phonenumber 50150 se-10-0-0-0(config)# ccn trigger sip phonenumber 50160	Specifies the telephone number that acts as the trigger to start the application on the Cisco Unity Express module and enters trigger configuration mode. number— The value should match one of the patterns configured in the destination-pattern field of the SIP dial peer pointing to Cisco Unity Express. Note Beginning with Cisco Unity Express 8.0, this number can be a combination of digits and wildcard characters. For more information, see the “Wild Card Trigger Patterns” section
Step 3	application application-name   se-10-0-0-0(config-trigger)# application voicemail se-10-0-0-0(config-trigger)# application autoattendant se-10-0-0-0(config-trigger)# application promptmgmt	Specifies the name of the application to invoke when a call is made to the trigger phone number.
Step 4	enabled   se-10-0-0-0(config-trigger)# enabled	Enables the trigger.
Step 5	maxsessions number   se-10-0-0-0(config-trigger)# maxsessions 3 se-10-0-0-0(config-trigger)# maxsessions 6	Specifies the maximum number of callers that this application can handle simultaneously. See the “Sharing Ports Among Applications and Triggers” section for guidelines on assigning this value.
Step 6	locale xx_YY   se-10-0-0-0(config-trigger)# locale en_US	(Optional) Specifies the trigger language. Any prompts being played out by an application invoked by this trigger will be played out in this language. Use this configuration only if you have more than one language installed on the system. The default for this configuration is to use the system default language as the trigger language.
Step 7	end   se-10-0-0-0(config-trigger)# end	Returns to privileged EXEC mode.
Step 8	show ccn trigger   se-10-0-0-0# show ccn trigger	Displays the details of all configured triggers.
Step 9	copy running-config startup-config   se-10-0-0-0# copy running-config startup-config	Copies the configuration changes to the startup configuration.

Examples

The following sample configuration sets two triggers on the Cisco Unity Express module:

se-10-0-0-0# config t

se-10-0-0-0(config)# ccn trigger sip phonenumber 50150

se-10-0-0-0(config-trigger)# application voicemail

se-10-0-0-0(config-trigger)# maxsessions 4

se-10-0-0-0(config-trigger)# enabled

se-10-0-0-0(config)# ccn trigger sip phonenumber 50160

se-10-0-0-0(config-trigger)# application autoattendant

se-10-0-0-0(config-trigger)# maxsessions 3

se-10-0-0-0(config-trigger)# enabled

The output of show ccn trigger looks similar to the following:

Wild Card Trigger Patterns

Beginning with Cisco Unity Express 8.0, the trigger number can be a combination of digits and wildcard characters. Incoming calls targeted to a number that matches the pattern cause the associated script to be invoked. The script determines which number was dialed by inspecting the called number attribute associated with the call. Cisco Unity Express supports a limit of 32 characters in the trigger pattern. Wildcard patterns are supported for both SIP and JTAPI triggers.

Table 5-2 shows the trigger pattern wildcards and special characters supported in Cisco Unity Express 8.0.

Wildcard patterns are based on Cisco Unified Communications Manager route patterns. The rules for choosing between multiple wildcard patterns matching an incoming call are similar to those used by Cisco Unified Communications Manager. For each pattern that is a candidate match for the dial string, Cisco Unity Express calculates the number of other dial strings of the same length as the input dial string that would match each pattern, and then selects the pattern that has the fewest alternative dial string matches.

Configuring JTAPI Triggers for the Applications (Cisco Unified Communications Manager Only)

Cisco Unity Express uses JTAPI to handle incoming calls in Cisco Unified Communications Manager mode. If you are deploying Cisco Unity Express in Cisco Unified Communications Manager mode, you must configure a JTAPI trigger for your application so that it can be invoked by incoming calls. This type of trigger is identified by the phone number which is dialed to invoke the desired application.

The telephone number that identifies your JTAPI trigger must match the Route Point configured on the Cisco Unified Communications Manager.

Beginning in Cisco Unity Express 8.0, the trigger number can be a combination of digits and wildcard characters. See the “Wild Card Trigger Patterns” section.

Note This Route Point must be associated with the JTAPI user configured on Cisco Unified Communications Manager. This same JTAPI user must also be configured on Cisco Unity Express module. See the “Configuring Triggers” section for details on JTAPI user configuration.

Cisco Unity Express supports a maximum of 8 JTAPI triggers for all applications combined, regardless of the hardware type.

This configuration is required for only for Cisco Unified Communications Manager mode.

Required Data for This Procedure

The following information is required to configure the JTAPI triggers for applications:

• Telephone number that invokes the application. The number must be unique for each application.
• Number of seconds the system must wait for a caller response before it times out and drops the call.
• Language to use for the prompts. Cisco Unity Express supports many languages. Only one can be installed on the system. See the Release Notes for Cisco Unity Express for a list of available languages.
• Maximum number of callers that can access the trigger simultaneously. See the “Sharing Ports Among Applications and Triggers” section for guidelines on assigning this value.

SUMMARY STEPS

1. config t

2. ccn trigger jtapi phonenumber number

3. application application-name

4. enabled

5. maxsessions number

6. locale xx_YY

7. end

8. show ccn trigger

9. copy running-config startup-config

DETAILED STEPS

	Command or Action	Purpose
Step 1	config t   se-10-0-0-0# config t	Enters configuration mode.
Step 2	ccn trigger jtapi phonenumber number   se-10-0-0-0(config)# ccn trigger jtapi phonenumber 6700	Specifies the telephone number that acts as the trigger to start the application on Cisco Unity Express and enters trigger configuration mode. The number value must match a JTAPI route point configured on Cisco Unified Communications Manager. Note Beginning with Cisco Unity Express 8.0, this number can be a combination of digits and wildcard characters. For more information, see the “Wild Card Trigger Patterns” section
Step 3	application application-name   se-10-0-0-0(config-trigger)# application promptmgmt	Specifies the name of the application to invoke when a call is made to the trigger phone number.
Step 4	enabled   se-10-0-0-0(config-trigger)# enabled	Enables the trigger.
Step 5	maxsessions number   se-10-0-0-0(config-trigger)# maxsessions 3	Specifies the maximum number of callers that this trigger can handle simultaneously. See the “Sharing Ports Among Applications and Triggers” section for guidelines on assigning this value.
Step 6	locale xx_YY   se-10-0-0-0(config-trigger)# locale en_US	(Optional) Specifies the trigger language. Any prompts being played out by an application invoked by this trigger will be played out in this language. Use this configuration only if you have more than one language installed on the system. The default for this configuration is to use the system default language as the trigger language.
Step 7	end   se-10-0-0-0(config-trigger)# end	Returns to privileged EXEC mode.
Step 8	show ccn trigger   se-10-0-0-0# show ccn trigger	Displays the details of all configured triggers.
Step 9	copy running-config startup-config   se-10-0-0-0# copy running-config startup-config	Copies the configuration changes to the startup configuration.

Examples

The following sample configuration sets two triggers on the Cisco Unity Express module:

se-10-0-0-0# config t

se-10-0-0-0(config)# ccn trigger jtapi phonenumber 6500

se-10-0-0-0(config-trigger)# application voicemail

se-10-0-0-0(config-trigger)# maxsessions 4

se-10-0-0-0(config-trigger)# enabled

se-10-0-0-0(config)# ccn trigger jtapi phonenumber 6700

se-10-0-0-0(config-trigger)# application autoattendant

se-10-0-0-0(config-trigger)# maxsessions 8

se-10-0-0-0(config-trigger)# enabled

Output of the show ccn trigger command looks similar to the following:

Configuring HTTP Triggers for the Applications

Cisco Unity Express can accept incoming HTTP requests to invoke an application using an HTTP trigger. For example, you can use it to initiate an IVR application notifying customers that their order has been filled and shipped. This type of trigger is identified by the URL suffix of the incoming HTTP request.

This type of trigger can only be used if an IVR license has been purchased and installed on the system.

For details on how to configure and use HTTP triggers, see the Cisco Unity Express Interactive Voice Response CLI Administrator Guide.

Configuring Multiple Triggers for an Application

Your network may require multiple triggers for one or more Cisco Unity Express applications. For example, the following are some scenarios where multiple triggers for the same application are useful:

• Multiple language support—You have an auto-attendant application which you want to deploy in two different languages. One way to achieve this would be to have two different triggers (call-in numbers) pointing to the same application, but with different values for the locale parameter.
  
  For example, assume that you have call-in numbers 6700 and 6900 (both pointing to the same auto-attendant application), the locale for the trigger 6700 is configured to be xx_XX, and the locale for the trigger 6900 is configured to be yy_YY. If the callers dial 6700, they will hear the auto-attendant greetings in the language xx_XX. If the callers dial 6900, they will hear the auto-attendant greetings in the language yy_YY.
• Different call treatment for internal and external callers—You have an auto-attendant application, and you want to provide slightly different Menu options for internal and external callers. In other words, you want to provide an option to the internal callers to transfer to the inventory department, but you do not want to present this option to the external callers. One way to achieve this would be to have two different triggers (call-in numbers) pointing to the same application, and by making a branching decision in your script by checking the called number using the “Get Call Contact Info” step.

Repeat the procedure described in the “Configuring SIP Triggers for the Applications” section and the “Configuring JTAPI Triggers for the Applications (Cisco Unified Communications Manager Only)” section (depending on your deployment mode) to create multiple triggers for an application.

Sharing Ports Among Applications and Triggers

Accessing an Application

The maximum number of callers that can access an application concurrently is determined by two parameters:

• The maxsessions value configured for the triggers invoking the application.
• The maxsessions value configured for the application itself.

If more calls than the trigger's configured maxsession value are received, callers hear a busy tone.

If more calls than the application's configured maxsession value are received, Cisco Unity Express plays an error prompt to the callers.

The following example shows how the maxsessions values for applications and triggers play a role in how many active calls can be made to an application. In this example:

• Your module has 8 ports.
• You assigned the auto-attendant application a maxsessions value of 5.
• You configured 2 triggers both invoking the same auto-attendant application.
• You configured one trigger with a maxsessions value of 2 and the other trigger with a maxsessions value of 4.

The maximum number of callers that can access the auto-attendant application simultaneously is five, not six. This is because although your system has a total of six sessions available for the two triggers, they both are accessing the same application, which allows only five concurrent sessions. The maxsessions value of the application acts as the gating factor in this case.

If you configure both triggers with a maxsessions value of 2, the maximum number of concurrent calls to the application is four, not five. This is because the system has a total of only four ports assigned to the two triggers. The maxsessions value assigned to the triggers acts as the factor in this example.

Sharing Ports Among Different Applications

Cisco Unity Express supports multiple voice applications, and each of these applications need voice ports in order to execute. Consider the expected call traffic for each application when assigning the maxsessions for them. One application may have a higher call volume and therefore need more sessions than another, and at the same time you may want each application to have at least one session available for incoming calls. You should distribute the ports to your applications keeping in mind the usage of each application.

For example, your module has four ports and you configure the voice-mail application to have four maxsessions, and the auto-attendant application also to have four maxsessions. If four callers access voice-mail simultaneously, no ports is available for auto-attendant callers. Only when zero, one, two, or three callers access voice-mail simultaneously is at least one port available for auto-attendant.

As another example, you configure the voice-mail auto-attendant applications to have three maxsessions. At no time will one application use up all the ports. If voice-mail has three active calls, one caller can access auto-attendant. A second call to either voice-mail or auto-attendant is not successful.

Overview of Holidays

You can configure:

• Year-specific holidays
• Fixed holidays

Year-Specific Holidays

• Cisco Unity Express supports up to three year-specific holiday lists for: the previous year, the current year, and the next year. If a year has no configured entries, the system handles that year as having no year-specific holidays.

For example, if the current year is 2005 and you have not configured entries for 2006 (the next year), the system handles 2006 as having zero (0) holidays. You may configure holidays for 2005 and 2006 (the next year) but not for 2007.

• Each year-specific list can contain a maximum of 26 holidays.
• By default, all three year-specific holiday lists are empty.
• The administrator can delete entries from a previous year list but cannot add or modify that list in any other way.
• The system automatically deletes the previous year list at the beginning of the new calendar year.
• For example, the system will delete the 2004 holiday list on January 1, 2006.
• To copy holidays from one year to the next, use the GUI option Copy all to next year under System > Holiday Settings.

Fixed Holidays

• Fixed holidays are permanent holidays which apply to all years and do not need to be re-configured year after year (unlike year-specific holidays). If a holiday falls on the same date every year, those may be configured as fixed holidays.

For example, if your business is always closed on January 1st for New Year celebrations, then you may configure January 1st as a fixed holiday.

• A maximum of 10 fixed holidays can be configured on the system.
• By default, there are no fixed holidays configured on the system.
• Fixed holidays may overlap with year-specific holidays. If you create a year-specific holiday
• that overlaps with a fixed holiday, a warning is issued. However, no warning is issued if you try to create a fixed holiday that overlaps with a year-specific holiday.

To configure holiday lists, use the graphical user interface (GUI) System > Holiday Settings option or the command-line interface (CLI) commands described in this section.

Using the Holiday Lists

The Cisco Unity Express Editor provides a step “Is Holiday” that checks the holidays configured on the system to determine whether the specified date is a holiday or not. The step takes as input the date to check against the holiday list. See the Cisco Unity Express Guide to Writing and Editing Scripts for more information on steps.

For example, you can use the “Is Holiday” step in your script to check if the current day is a holiday. If it is a holiday, you can play a customized greeting to the caller, such as “We are closed today. If this is an emergency, please call 1-222-555-0150 for assistance. Otherwise, please call back later.”

Configuring Holiday Lists

Prerequisites

Cisco Unity Express 3.0 or a later version

Configuring Year-Specific Holiday Lists

Use the following command in Cisco Unity Express configuration mode to configure a year-specific holiday list:

calendar holiday date yyyy mm dd [ description holiday-description ]

where yyyy is the 4-digit year, mm is the 2-digit month, dd is the 2-digit day, and holiday-description is an optional description of the holiday. If the description is more than one word, enclose the text in quotes (“ ”).

The valid values for yyyy are the current year or the next year. An error message appears if the year or date is out of range.

se-10-0-0-0# config t

se-10-0-0-0(config)# calendar holiday date 2005 05 30 description “Memorial Day”

se-10-0-0-0(config)# exit

se-10-0-0-0#

Configuring the Fixed Holiday List

Use the following command in Cisco Unity Express configuration mode to configure a fixed holiday:

calendar holiday fixed month day [description holiday- description ]

where month is the 2-digit month, day is the 2-digit day, and holiday-description is an optional description of the holiday. If the description is more than one word, enclose the text in quotes (“ ”).

se-10-0-0-0# config t

se-10-0-0-0(config)# calendar holiday fixed 07 04 description “Independence Day”

se-10-0-0-0(config)# exit

se-10-0-0-0#

Displaying the Holiday List

Several CLI commands are available in Cisco Unity Express EXEC mode for displaying the holiday lists.

Prerequisites

Cisco Unity Express 3.0 or a later version

Displaying All Holiday Lists

The following command displays all the holiday lists configured on the system:

show calendar holiday [ all ]

This command displays the date and description for all holidays for all years. This display includes both year-specific holidays and fixed holidays. The output of this command appears similar to the following:

Displaying Holiday Lists for a Specific Year

The following command displays the holidays configured for a specific year:

show calendar holiday year yyyy

where yyyy is the 4-digit year. This command displays the date and description for all holidays configured for the specified year. This display includes both year-specific holidays and fixed holidays. If no holidays are configured for that year and the fixed holiday list is empty, the message “No holidays found for the specified year” appears. The output of this command appears similar to the following:

Displaying Holiday Lists for a Specific Month

The following command displays the holidays configured for a specific month in a specified year:

show calendar holiday year yyyy month mm

where yyyy is the 4-digit year and mm is the 2-digit month. This command displays the date and description for all holidays configured for the specified month in the specified year.This display includes both year-specific holidays and fixed holidays. If no holidays are configured for that month and there are no holidays in that month, the message “No holidays found for the specified month” appears.

The output of this command appears similar to the following:

Deleting Holidays from the List

Several CLI commands are available in Cisco Unity Express configuration mode for deleting holidays from the list.

Prerequisites

Cisco Unity Express 3.0 or a later version

Deleting a Year-Specific Holiday from the Holiday List

The following command deletes a year-specific holiday:

Caution Use this command with caution because this operation is irreversible. Do not press the “Enter” key after the year; doing so deletes the holiday list for the entire year.

---

no calendar holiday date yyyy mm dd

where yyyy is the 4-digit year, mm is the 2-digit month, and dd is the 2-digit day.

se-10-0-0-0# config t

se-10-0-0-0(config)# no calendar holiday date 2004 11 25

se-10-0-0-0(config)# end

Deleting Year-Specific Holidays from a Specific Month

Caution Use this command with caution because this operation is irreversible and can cause the loss of the temporary holiday configuration for the entire month.

---

The following command deletes the year-specific holidays configured for a specific month in the specified year:

no calendar holiday year yyyy month mm

where yyyy is the 4-digit year and mm is the 2-digit month.

se-10-0-0-0# config t

se-10-0-0-0(config)# no calendar holiday year 2004 month 09

se-10-0-0-0(config)# end

Deleting Year-Specific Holidays for a Specific Year

Caution Use this command with caution because this operation is irreversible and may cause the loss of the holiday configuration for the entire year.

---

The following command deletes all the year-specific holidays configured for the specified year:

no calendar holiday year yyyy

where yyyy is the 4-digit year.

se-10-0-0-0# config t

se-10-0-0-0(config)# no calendar holiday year 2004

se-10-0-0-0(config)# end

Deleting a Fixed Holiday from the Holiday List

The following command deletes a fixed holiday:

no calendar holiday fixed month day

where month is the 2-digit month and day is the 2-digit day.

se-10-0-0-0# config t

se-10-0-0-0(config)# no calendar holiday fixed 07 04

se-10-0-0-0(config)# exit

Overview of Business-Hours Schedules

You can configure up to 4 weekly business-hours schedules. Each day is divided into 48 half-hour time slots. Each of these time slots can be configured to specify whether the business is open or closed during that time. Use the graphical user interface (GUI) System > Business Hours Settings option or the command-line interface (CLI) commands described in this section to configure these slots.

The Cisco Unity Express system ships with one default schedule called “systemschedule.” This schedule indicates the business is open 24 hours per day, 7 days per week. Use the GUI System > Business Hours Settings option or CLI commands to modify or delete this default schedule. This schedule counts toward the maximum limit of 4 business-hours schedules.

Using the Business-Hours Schedule

The Cisco Unity Express Editor provides a step “Business Hours” that checks whether the business is open or closed during a specified time slot. The step takes three parameters as input: a date, time and the name of a schedule configured on the system. See the Cisco Unity Express Guide to Writing and Editing Scripts for more information about steps.

For example, you can use the “Business Hours” step in your script to check whether the business is currently open or not. If it is closed, you can play a customized greeting to the caller, such as “You have reached us during our off-hours. If this is an emergency, please call 1-222-555-0150 for assistance. Otherwise, please call back later.”

Creating a Business-Hours Schedule

Follow this procedure to create a business-hours schedule.

Data Required for This Procedure

The following information is required to configure a business-hours schedule:

• Schedule name

The maximum length of the name is 31 alphanumeric characters, including uppercase letters A to Z, lowercase letters a to z, digits 0 to 9, underscore (_), and dash (-). The first character of the name must be a letter.

If a schedule with this name does not exist, the system will create it. By default, a newly created schedule is open, 24 hours per day, 7 days per week.

If the schedule already exists, any changes will modify the schedule.

• Day of the week
• Starting and ending clock times when the business is open and closed

SUMMARY STEPS

1. config t

2. calendar biz-schedule schedule-name

3. closed day day-of-week from hh:mm to hh:mm

4. open day day-of-week from hh:mm to hh:mm

5. end

DETAILED STEPS

Examples

The following example configures a new business-hours schedule:

se-10-0-0-0# config t

se-10-0-0-0(config)# calendar biz-schedule normal

Adding new schedule

se-10-0-0-0(config-business)# closed day 1 from 00:00 to 24:00

se-10-0-0-0(config-business)# closed day 2 from 00:00 to 08:30

se-10-0-0-0(config-business)# closed day 2 from 17:30 to 24:00

se-10-0-0-0(config-business)# closed day 3 from 00:00 to 08:30

se-10-0-0-0(config-business)# closed day 3 from 17:30 to 24:00

se-10-0-0-0(config-business)# closed day 4 from 00:00 to 08:30

se-10-0-0-0(config-business)# closed day 4 from 17:30 to 24:00

se-10-0-0-0(config-business)# closed day 5 from 00:00 to 08:30

se-10-0-0-0(config-business)# closed day 5 from 20:00 to 24:00

se-10-0-0-0(config-business)# closed day 6 from 00:00 to 08:30

se-10-0-0-0(config-business)# closed day 6 from 18:00 to 24:00

se-10-0-0-0(config-business)# closed day 7 from 00:00 to 09:00

se-10-0-0-0(config-business)# closed day 7 from 13:00 to 24:00

se-10-0-0-0(config-business)# end

Modifying Business-Hours Schedules

In Cisco Unity Express configuration mode, use the following command to access a business-hours schedule for modification:

calendar biz-schedule schedule-name

where schedule-name is the name of the business-hours schedule to modify. If a schedule with the specified business name does not exist, the system creates it.

The following example accesses the existing “normal” business-hours schedule:

se-10-0-0-0# config t

se-10-0-0-0(config)# calendar biz-schedule normal

Modifying existing schedule

se-10-0-0-0(config-business)# open day 1 from 09:00 to 12:00

se-10-0-0-0(config-business)# end

se-10-0-0-0#

Only the hours specified using these commands are affected. The other time slots in the business-hours schedule are not modified.

Changing the Status of Open or Closed Hours

To modify an existing schedule, specify the open and closed hours for each day as needed.

Changing an Open Slot to a Closed Slot

Use either of the following configuration mode commands to change an open slot to a closed slot:

no open day day-of-week from hh : mm to hh : mm

closed day day-of-week from hh : mm to hh : mm

where day-of-week is the numeric day of the week (1 equals Sunday), hh are hours in the 24-hour clock format, and mm are minutes, either 00 or 30.

For example, use the no open day 2 from 09:00 to 10:00 command if your business is open on Monday from 09:00 to 17:00; and use the closed day 3 from 09:00 to10:00 command if your business is closed Tuesday 9:00 a.m. to 10:00 a.m.

Changing a Closed Slot to an Open Slot

Use either of the following commands to change a closed slot to an open slot:

no closed day day-of-week from hh : mm to hh : mm

open day day-of-week from hh : mm to hh : mm

where day-of-week is the numeric day of the week (1 equals Sunday), hh are hours in the 24-hour clock format, and mm are minutes, either 00 or 30.

For example, if Monday is closed from 00:00 to 10:00, then no closed day 2 from 09:00 to 10:00 or open day 2 from 09:00 to 10:00 opens the Monday time slot 9:00 a.m. to 10:00 a.m.

Examples

The following output shows the “normal” business-hours schedule:

The following commands modify the “normal” business hours by closing Monday hours from 8:30 to 9:30 and opening Saturday hours from 1:00 p.m. to 2:00 p.m.:

se-10-0-0-0# config t

se-10-0-0-0(config)# calendar biz-schedule normal

se-10-0-0-0(config-business)# no open day 2 from 08:30 to 09:30

se-10-0-0-0(config-business)# no closed day 7 from 13:00 to 14:00

se-10-0-0-0(config-business)# end

The following output shows the changed schedule:

Displaying Business-Hours Schedules

Several CLI commands are available in Cisco Unity Express EXEC mode for displaying the business-hours schedules.

Displaying a Specific Schedule

The following command displays a specific business-hours schedule:

show calendar biz-schedule schedule-name

where schedule-name is the name of the schedule. This command displays each day of the week and the open hours. The output of this command appears similar to the following.

Displaying All Businesses Schedules

The following command displays all the configured business-hours schedules in the system:

show calendar biz-schedule [ all ]

This command displays the open hours for each day of the week for each schedule. The output of this command appears similar to the following:

Deleting a Business-Hours Schedule

The following configuration mode command deletes a specified business-hours schedule:

no calendar biz-schedule schedule-name

where schedule-name is the name of the business-hours schedule to delete.

If you delete a business-hours schedule which is being used in the “Business Hours” step in an application, the step assumes that the business is open 24 hours a day, 7 days a week.

The following example deletes the “normal” business-hours schedule:

se-10-0-0-0# config t

se-10-0-0-0(config)# no calendar biz-schedule normal

se-10-0-0-0(config)# exit

se-10-0-0-0#

Prerequisites

You must configure the Cisco IOS gateway for T.37 on-ramp and off-ramp fax support. See the “Configuring Your Cisco IOS Gateway for T.37 On-Ramp and Off-Ramp Fax Support” section for more details.

To restrict specified extensions from using this feature, you must configure a restriction table as described in the “Configuring Restriction Tables” section.

Required Data for This Procedure

This procedure requires:

• IP address or hostname of the outbound fax gateway
• IP address or hostname for the inbound fax gateway
• Fax number used to print faxes

SUMMARY STEPS

1. config t

2. fax gateway outbound address { hostname | ip-address }

3. fax gateway inbound address { hostname | ip-address }

4. fax print E.164

5. voice mailbox owner name

6. enable fax

7. end

8. show fax configuration

DETAILED STEPS

Example

The following sample configuration configures the fax parameters on a Cisco Unity Express module: