Guest

Cisco Unity

NEC NEAX 2400 with Serial MCI Integration Guide for Cisco Unity 3.1

 Feedback

Table Of Contents

NEC NEAX 2400 with Serial MCI Integration Guide for Cisco Unity 3.1

Integration Tasks

Integration Steps

Requirements

Integration Description

Integration Features

Planning How the Voice Messaging Ports Will Be Used by Cisco Unity

Preparing for Programming the Phone System

Setting Up the Trunk Card

Programming the NEC NEAX 2400 serial MCI Phone System

Transferring Calls on Phone Systems Without Release Transfer

Configuring Cisco Unity for the Integration

Testing the Integration

Integrating a Secondary Server for Cisco Unity Failover

Requirements

Integration Description

Setting Up the Secondary Server for Failover


Dual Phone System Integration

Dual Phone System Integration Overview

Integration Steps When No Phone Systems Are Installed

Integration Steps When a Circuit-Switched Phone System Is Already Installed

Integration Steps When Cisco CallManager Is Already Installed

Requirements

Changing Cisco Unity Administrator Settings

Changing the Number of Installed Ports


Appendix: Enabling Cisco Unity to Trim Disconnect Tones


Appendix: Remapping Extension Numbers

About the Remapping Feature

Setting Up Cisco Unity to Remap Extension Numbers

Syntax and Examples


Appendix: Assigning Dialogic Ports for a Dual Phone System Integration


Appendix: Documentation and Technical Assistance

Conventions

Obtaining Documentation

Cisco.com

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco Technical Support Website

Opening a TAC Case

TAC Case Priority Definitions

Obtaining Additional Publications and Information


NEC NEAX 2400 with Serial MCI Integration Guide for Cisco Unity 3.1


Revised November 24, 2004

This document provides instructions for integrating the phone system with Cisco Unity.

Integration Tasks

Before doing the following tasks to integrate Cisco Unity with the NEC NEAX 2400 serial MCI phone system, confirm that the Cisco Unity server is ready for the integration by completing the applicable tasks in the Cisco Unity Installation Guide.

The following task list describes the process for creating the integration.

Integration Steps

Follow these steps to set up this integration.

1. Review the system and equipment requirements to confirm that all phone system and Cisco Unity server requirements have been met. See the "Requirements" section.

2. Plan how the voice messaging ports will be used by Cisco Unity. See the "Planning How the Voice Messaging Ports Will Be Used by Cisco Unity" section.

3. If you are using T1 voice messaging ports, set up the digital trunk interface card. See the "Setting Up the Trunk Card" section.

4. Plan how the voice messaging ports will be used by Cisco Unity. See the "Planning How the Voice Messaging Ports Will Be Used by Cisco Unity" section.

5. Program the NEC NEAX 2400 serial MCI phone system and extensions. See the "Programming the NEC NEAX 2400 serial MCI Phone System" section.

6. Configure Cisco Unity for the integration. See the "Configuring Cisco Unity for the Integration" section.

7. Test the integration. See the "Testing the Integration" section.

8. If you have Cisco Unity failover, integrate the secondary server. (Cisco Unity failover is supported only for release 3.1(2) and later.) See the "Integrating a Secondary Server for Cisco Unity Failover" section.

Requirements

The NEC NEAX 2400 serial MCI integration supports configurations of the following components:

Phone System

One of the following NEAX 2400 phone systems with serial MCI:

Table 1 NEAX 2400 Specifications 

Phone System
Software Version

IMX

All software versions

IMG and SIM

(IMG and SIM phone systems may require upgrading to a high-density system to support MCI.)

5200 or later

MMG and UMG

4200 version 5 or later


One IOC serial port for the MCI data link connected to a serial port (COM1 is the default) on the Cisco Unity server with a PH-68 two-port cable and an RS-232C CA-1 cable.

We recommend that the serial cable have the following construction:

A maximum of 50 feet (15.24 m) in length

24 AWG stranded conductors

Low capacitance—for example, no more than 12 pF/ft (39.4 pF/m) between conductors

At least 65 percent braided shield over aluminized polymer sleeve around conductors

UL-recognized overall cable jacket insulation with low dielectric constant

Braided shield fully terminated to and enclosed by a metal connector backshell

Gold-plated connector contacts

MCI feature II installed according to the NEC documentation for the phone system.

One or more of the following station ports (analog) or trunk circuits (T1) set up as voice messaging ports and connected to the voice cards in the Cisco Unity server:

Table 2 Voice Messaging Port Types 

Port Type
Description

Analog

One analog station port for each voice messaging port.

T1

One digital trunk interface card (card number PA-24DTR/DLI) with program version SP3298 3A 001 or later for each group of 24 voice messaging ports.


Use of the Cisco Unity release-to-switch call transfer type requires one of the following versions of the NEAX 2400 phone system software. If the phone system does not support the release-to-switch transfer type, see the "Transferring Calls on Phone Systems Without Release Transfer" section.

Table 3 Specifications for Release-to-Switch Transfer 

Phone System
Software Version

IMX

All versions, with release (blind) transfer to the attendant and to the station

IMG and SIM

5200 or later, with release transfer to the attendant and to the station

MMG and UMG

5200 or later, with release transfer to the attendant and to the station


Open disconnect supervision on all line circuits connected to Cisco Unity.

Alternatively, the Cisco Unity phone configuration file (also called the switch .ini file) must be edited to enable Cisco Unity to trim disconnect tones. For instructions, see the "Appendix: Enabling Cisco Unity to Trim Disconnect Tones" section.

Cisco Unity Server

The applicable voice cards, installed. For details on supported voice cards, refer to Cisco Unity System Requirements, and Supported Hardware and Software, available on Cisco.com at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_pre_installation_guides_list.html.

Cisco Unity installed and ready for the integration as described in the Cisco Unity Installation Guide.

A system key that enables the integration and the appropriate number of voice messaging ports.

An available serial port (COM1 is the default).

Integration Description

The NEAX 2400 serial MCI integration uses a data link, which consists of an RS-232 serial cable connecting the IOC port in the phone system to the Cisco Unity server. The voice messaging lines from the phone system connect to the analog or T1 voice cards in the Cisco Unity server. The following illustrations show the required connections.

Figure 1 Analog and Serial Connections Between the Phone System and Cisco Unity

Figure 2 T1 and Serial Connections Between the Phone System and
Cisco Unity

The phone system sends the following information through the data link:

The extension of the called party

The extension of the calling party (for internal calls) or the phone number of the calling party (if it is an external call and the system uses caller ID)

The reason for the forward (the extension is busy, does not answer, or is set to forward all calls)

Cisco Unity uses this information to answer the call appropriately. For example, a call forwarded to Cisco Unity is answered with the personal greeting of the subscriber. If the phone system routes the call to Cisco Unity without this information, Cisco Unity answers with the opening greeting.

Integration Features

The NEC NEAX 2400 serial MCI integration with Cisco Unity provides the following features.

Call forward to personal greeting

When an incoming call is routed to an unanswered extension, the call is forwarded to the voice mail of the subscriber. The caller then hears the personal greeting of the subscriber and can leave a message.

Call forward to busy greeting

When an incoming call is routed to a busy extension, the call is forwarded to the voice mail of the subscriber. The caller then hears the busy greeting (if the subscriber enabled it) and can leave a message.

Caller ID

Cisco Unity receives caller ID information from the phone system (if available). This information appears in the subject line of the message in the desktop messaging application.

Easy message access

A subscriber can retrieve messages without entering an ID. Cisco Unity identifies a subscriber based on the extension from which the call originated. A password may be required.

Identified subscriber messaging

Cisco Unity automatically identifies a subscriber who leaves a message during a forwarded internal call, based on the extension from which the call originated.

Message waiting indication

When a message is waiting for a subscriber, Cisco Unity notifies the phone system to activate the message waiting indicator (MWI) on the subscriber extension.


Planning How the Voice Messaging Ports Will Be Used by Cisco Unity

Before programming the phone system, you need to plan how the voice messaging ports will be used by Cisco Unity. The following considerations will affect the programming for the phone system (for example, setting up the hunt group or call forwarding for the voice messaging ports):

The number of voice messaging ports installed.

The number of voice messaging ports that will answer calls.

The number of voice messaging ports that will only dial out, for example, to send message notification, to set message waiting indicators (MWIs), to make AMIS deliveries, and to make telephone record and playback (TRAP) connections.

The Number of Voice Messaging Ports to Install

The number of voice messaging ports to install depends on numerous factors, including:

The number of calls Cisco Unity will answer when call traffic is at its peak.

The expected length of each message that callers will record and that subscribers will listen to.

The number of subscribers.

The number of ports that will be set to dial out only.

The number of calls made for message notification.

The number of MWIs that will be activated when call traffic is at its peak.

The number of AMIS delivery calls.

The number of Media Master connections needed when call traffic is at its peak. (Media Master connections are used by Cisco Unity web applications and e-mail clients to play back and record over the phone.)

It is best to install only the number of voice messaging ports that are needed so that system resources are not allocated to unused ports.

The Number of Voice Messaging Ports That Will Answer Calls

The calls that the voice messaging ports answer can be incoming calls from unidentified callers or from subscribers. Typically, these voice messaging ports are the busiest. They also have the lowest port numbers for the phone system. As a general guideline, assign approximately 75 percent of the voice messaging ports to answer calls.

You can set voice messaging ports to both answer calls and to dial out (for example, to set MWIs).

The Number of Voice Messaging Ports That Will Only Dial Out, and Not Answer Calls

Ports that will only dial out and will not answer calls can do one or more of the following:

Notify subscribers by phone, pager, or e-mail of messages that have arrived.

Turn MWIs on and off for subscriber extensions.

Make outbound AMIS calls to deliver voice messages from Cisco Unity subscribers to users on another voice messaging system. (This action is available only with the AMIS licensed feature.)

Make a Media Master connection so that subscribers can use the phone as a recording and playback device in Cisco Unity web applications and e-mail clients.

Typically, these voice messaging ports are the least busy ports. They also have the highest port numbers for the phone system. As a general guideline, assign approximately 25 percent of the voice messaging ports to dial out.


Caution In programming the phone system, do not send calls to voice messaging ports in Cisco Unity that cannot answer calls (voice messaging ports that are not set to Answer Calls). For example, if a voice messaging port is set only to Dialout MWI, do not send calls to it.

Preparing for Programming the Phone System

Record your decisions about the voice messaging ports to guide you in programming the phone system.

Setting Up the Trunk Card

If the phone system uses a T1 line to connect to Cisco Unity, confirm that the firmware version of the trunk card is correct, and set the DIP switches before you program the phone system.

To confirm the trunk card firmware version


Step 1 Remove the 24DTR/DLI trunk card from the phone system.

Step 2 Locate the removable, integrated circuit (PROM) with a white label. This PROM contains the program, or firmware, of the trunk card. The relative location of the PROM may vary, but it is the only PROM with a white label on the trunk card.

Step 3 Confirm that the firmware version printed on the label is "SP-3298 3A 001" or later. If the version is incorrect, update the firmware by replacing the PROM or the trunk card.


To set the trunk card switches


Step 1 Set the switches for the 24DTR/DLI trunk card as shown below.

Figure 3 Trunk Card Switch Settings

Step 2 Replace the 24DTR/DLI trunk card into the phone system.


For more information, refer to NEAX 2400 IMX Circuit Card Manual.

Programming the NEC NEAX 2400 serial MCI Phone System

If you use programming options other than those supplied in the following procedure, the performance of the integration may be affected.

If you want to remap extension numbers (for example, when multiple subscribers use a single phone, or when multiple extension numbers on a single phone should go to a single subscriber greeting), see the "Appendix: Remapping Extension Numbers" section.

To Program the NEC NEAX 2400 serial MCI Phone System


Step 1 Specify the Universal Call Distribution (UCD) group for the voice messaging system ports based on the type of voice messaging ports:

Analog

Assign each analog circuit an extension number, then add each of the numbers to the UCD group.

T1

Assign each trunk circuit an extension number, then add each of the numbers to the UCD group.


If the number of voice messaging system ports exceeds the number of supported ports in a UCD group, specify additional UCD groups, and then link them together using the AUOG command. Software versions 7200 or later support up to 100 ports in a UCD group while software versions earlier than 7200 support up to 20 ports in a UCD group.

Make sure that the phone system sends calls only to Cisco Unity voice ports in the UCD group that are set to Answer Calls on the System > Ports page in the Cisco Unity Administrator. Calls sent to a voice port not set to Answer Calls cannot be answered by Cisco Unity and may cause other problems.


Caution Do not use a phantom single line extension for the UCD pilot number. Otherwise, the UCD group will not work properly.

Step 2 Program each phone to forward calls to the UCD pilot number assigned to the voice messaging ports, based on one of the Cisco Unity call transfer types shown in Table 4.

Table 4 Call Transfer Types for UCD Pilot Number 

Transfer Type
Usage

Release transfer
(blind transfer)

Program the phone to forward calls to the UCD pilot number when:

The extension is busy

The call is not answered

Supervised transfer

Program the phone to forward calls to the UCD pilot number only when the call is not answered. Confirm that call forwarding is disabled when the extension is busy.


Step 3 Use the AIOC command to set up the RS-232 serial data port connected to Cisco Unity as follows:

9600 baud

8 data bits

1 stop bit

No parity

Step 4 Use the AUCD command to program the phone system to send UCD call information to MCI. Assign a value of "0" to the "MCI Data Transfer" field for the appropriate tenant and UCD pilot numbers.

Step 5 Use the programming system data table to program the ASYD settings. Each bit is part of a hexadecimal number displayed in the ASYD settings. Convert the hexadecimal number to binary to determine the individual settings.

Table 5 Programming System Data 

System
Index
Bit
Value
Description

1

17

b4

1

Release (blind) transfer to attendant console

 

28

b0-4

0

Guard timer not required

   

b5

1

MWI controlled by MCI

 

29

b1-7

0/1

No/Yes: Assign I/O port for MCI output

Port 1 = b1, port 2 = b2, and so on

 

34

b1-4

0

Set output to no parity and 1 stop bit

 

60

b3

0

UCD queuing required

 

63

b0

1

Release transfer for stations in service

 

69

b0

1

No recall, execute call forwarding on no answer

 

70

b0

1

Called number display, when forwarding to attendant console

 

77

b2

0

MWI refresh required

 

78

b0

1

Calling number display enabled

   

b1

1

Called station status display enabled

 

238

b0-7

0

Lamp flash rate

 

246

b3

0

MCI expansion set to normal

 

400

b2

1

Calling number information sent to MCI

2

6

b0

1

MCI in service when terminating to a UCD group

 

7

b1

0

MCI out of service when terminating to attendant console


Step 6 Use the programming system data local data table to program the ASYDL settings. Each bit is part of a hexadecimal number displayed in the ASYDL settings. Convert the hexadecimal number to binary to determine the individual settings.

Table 6 Programming System Data Local Data 

System
Index
Bit
Value
Description

1

641

b1

0/1

0/1: MCI/IMX station number/phone number

 

832

b0-7

00-FD

Assign the FPC of the node connected to MC

 

833

b0

0

IOC serial interface enabled for MCI

   

b1

0

0/1: ICS/IMX format



For more information, refer to the NEC documentation for the phone system.

Transferring Calls on Phone Systems Without Release Transfer

Because phone systems without release (blind) transfer do not support the Cisco Unity release-to-switch call transfer type, the phone system does not forward calls to Cisco Unity when all of the following three conditions are met:

The phone system does not support release transfers to the attendant console and release transfers to the stations.

The phone system is set to forward unanswered calls.

A call is transferred from an extension to another that does not answer.

When all of these conditions are met, the phone system returns the call to the extension originally called. (Calls that the operator transferred appear on the console as "Recall" when they return.)

Configuring Cisco Unity for the Integration

After ensuring that the Cisco Unity server is ready for the integration by completing the appropriate tasks in the Cisco Unity Installation Guide, do the following procedures to confirm that the integration is enabled and to enter the port settings.

To Confirm That the Integration Is Enabled


Step 1 On the Cisco Unity server, go to the Cisco Unity Administrator by doing one of the following:

In Internet Explorer, go to http://<server name>/web/sa.

Double-click the desktop shortcut to the Cisco Unity Administrator.

Step 2 Go to System > Licensing > Licensed Features.

Step 3 In the Integration field, confirm that the setting is Serial for a single phone system integration or Multiple Integrations for a dual phone system integration.

Step 4 If the setting is not Serial or Multiple Integrations, contact your sales representative for the necessary system key.

Step 5 Go to System > Switch. Confirm that the settings match those in the following table. If the settings are incorrect, integration features may not be enabled.

Table 7 Switch Settings 

Switch Parameter
Required Setting

Manufacturer

NEC

Model

NEAX 2400

Switch PBX Software Version

All w/ analog ports

All w/ T1 ports

Integration

Serial


Step 6 Click the Save icon.


To Enter Port Settings


Step 1 In the Cisco Unity Administrator, go to the System > Ports page.

Step 2 Select a port in the table.

Step 3 Indicate the settings for the port.

For a hunt group, use the first voice-messaging ports for incoming calls and the last ports to dial out. This helps minimize the possibility of a collision, in which an incoming call arrives on a port at the same time that Cisco Unity takes the port off-hook to dial out.

Step 4 Type the extension for the port. If the extension for the port is not entered correctly, the integration will not work.

Step 5 Repeat Step 2 through Step 4 for the remaining ports.

Step 6 Click the Save icon.

Step 7 For the settings to take effect, exit the Cisco Unity software.


Testing the Integration

To test whether Cisco Unity and the phone system are integrated correctly, do the procedures in the order listed.

If any of the steps indicates a failure, refer to the following documentation as applicable:

The installation guide for the phone system

Cisco Unity Troubleshooting Guide

The setup information earlier in this document

To Set Up the Test Configuration


Step 1 Set up two test extensions (Phone 1 and Phone 2) on the same phone system that Cisco Unity is connected to.

Step 2 Set Phone 1 to forward calls to the Cisco Unity pilot number when calls are not answered.

Step 3 In the Cisco Unity Administrator, go to the Subscribers > Subscribers > Profile page.

If Example Subscriber is not displayed, click the Find icon (the magnifying glass) in the title bar, then click Find, and select Example Subscriber in the list that appears.

Step 4 In the Extension field, enter the extension of Phone 1.

Step 5 Click the Save icon.

Step 6 In the navigation bar, click Call Transfer to go to the Subscribers > Subscribers > Call Transfer page for Example Subscriber.

For more information on transfer settings, refer to the "Subscriber Template Call Transfer Settings" section in the online Help for the Cisco Unity Administrator.

Step 7 Under Transfer Incoming Calls, click Yes, Ring Subscriber's Extension, and confirm that the extension number is for Phone 1.

Step 8 Under Transfer Type, click Release to Switch.

Step 9 Click the Save icon.

Step 10 In the navigation bar, click Messages to go to the Subscribers > Subscribers > Messages page for Example Subscriber.

Step 11 Under Message Waiting Indicators (MWIs), check the Use MWI for Message Notification check box.

Step 12 In the Extension field, enter x.

Step 13 Click the Save icon.

Step 14 Open the Status Monitor by doing one of the following:

In Internet Explorer, go to http://<server name>/web/sm.

Double-click the desktop shortcut to the Status Monitor.

On the Windows taskbar next to the clock, right-click the Cisco Unity icon and click Status Monitor.


To Test an External Call with Release Transfer


Step 1 From Phone 2, enter the access code necessary to get an outside line, then enter the number outside callers use to dial directly to Cisco Unity.

Step 2 On the Status Monitor, note the port that handles this call.

Step 3 When you hear the opening greeting, enter the extension for Phone 1. Hearing the opening greeting means that the port is configured correctly.

Step 4 Confirm that Phone 1 rings and that you hear a ringback tone on Phone 2. Hearing a ringback tone means that Cisco Unity released the call and transferred it to Phone 1.

Step 5 Leaving Phone 1 unanswered, confirm that the state of the port handling the call changes to "Idle." This state means that release transfer is successful.

Step 6 Confirm that, after the number of rings that the phone system is set to wait, the call is forwarded to Cisco Unity and that you hear the greeting for Example Subscriber. Hearing the greeting means that the phone system forwarded the unanswered call and the call-forward information to Cisco Unity, which correctly interpreted the information.

Step 7 On the Status Monitor, note the port that handles this call.

Step 8 Leave a message for Example Subscriber and hang up Phone 2.

Step 9 On the Status Monitor, confirm that the state of the port handling the call changes to "Idle." This state means that the port was successfully released when the call ended.

Step 10 Confirm that the MWI on Phone 1 is activated. The activated MWI means that the phone system and Cisco Unity are successfully integrated for turning on MWIs.


To Test an Internal Call with Release Transfer


Step 1 From Phone 1, enter the internal pilot number for Cisco Unity.

Step 2 When asked for your password, enter 12345. Hearing the request for your password means that the phone system sent the necessary call information to Cisco Unity, which correctly interpreted the information.

Step 3 Confirm that you hear the recorded voice name for Example Subscriber. Hearing the voice name means that Cisco Unity correctly identified the subscriber by the extension.

Step 4 When asked whether you want to listen to your messages, press 1.

Step 5 After listening to the message, press 3 to delete the message.

Step 6 Confirm that the MWI on Phone 1 is deactivated. The deactivated MWI means that the phone system and Cisco Unity are successfully integrated for turning off MWIs.

Step 7 Hang up Phone 1.

Step 8 On the Status Monitor, confirm that the state of the port handling the call changes to "Idle." This state means that the port was successfully released when the call ended.


To Set Up Supervised Transfer on Cisco Unity


Step 1 In the Cisco Unity Administrator, go to the Subscribers > Subscribers > Call Transfer page.

If Example Subscriber is not displayed, click the Find icon (the magnifying glass) in the title bar, then click Find, and select Example Subscriber in the list that appears.

For more information on transfer settings, refer to the "Subscriber Template Call Transfer Settings" section in the online Help for the Cisco Unity Administrator.

Step 2 Under Transfer Type, click Supervise Transfer.

Step 3 Set the Rings to Wait For field to 3.

Step 4 Click the Save icon.


To Test Supervised Transfer


Step 1 From Phone 2, enter the access code necessary to get an outside line, then enter the number outside callers use to dial directly to Cisco Unity.

Step 2 On the Status Monitor, note the port that handles this call.

Step 3 When you hear the opening greeting, enter the extension for Phone 1. Hearing the opening greeting means that the port is configured correctly.

Step 4 Confirm that Phone 1 rings and that you do not hear a ringback tone on Phone 2. Instead, you should hear the indication your phone system uses to mean that the call is on hold (for example, music or beeps).

Step 5 Leaving Phone 1 unanswered, confirm that the state of the port handling the call remains "Busy." This state and hearing an indication that you are on hold mean that Cisco Unity is supervising the transfer.

Step 6 Confirm that, after three rings, you hear the greeting for Example Subscriber. Hearing the greeting means that Cisco Unity successfully recalled the supervised-transfer call.

Step 7 During the greeting, hang up Phone 2.

Step 8 On the Status Monitor, confirm that the state of the port handling the call changes to "Idle." This state means that the port was successfully released when the call ended.


To Return Example Subscriber to the Default Settings


Step 1 In the Cisco Unity Administrator, go to the Subscribers > Subscribers > Call Transfer page.

If Example Subscriber is not displayed, click the Find icon (the magnifying glass) in the title bar, then click Find, and select Example Subscriber in the list that appears.

Step 2 Under Transfer Incoming Calls, click No (Send Directly to Subscriber's Greeting).

Step 3 In the navigation bar, click Profile to go to the Subscribers > Subscribers > Profile page.

Step 4 In the Extension field, enter 99990.

Step 5 Click the Save icon.

Step 6 In the navigation bar, click Messages to go to the Subscribers > Subscribers > Messages page for Example Subscriber.

Step 7 Under Message Waiting Indicators (MWIs), uncheck the Use MWI for Message Notification check box.

Step 8 Click the Save icon.


Integrating a Secondary Server for Cisco Unity Failover

The Cisco Unity failover feature enables a secondary server to provide voice messaging services when the primary server becomes inactive. For information on installing a secondary server for failover, refer to the Cisco Unity Installation Guide, available at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.

For information on failover, refer to the Cisco Unity Failover Configuration and Administration Guide, available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/fail/fail401/ex/index.htm.

Requirements

The following components are required to integrate a secondary server:

Phone System

Two serial ports for the MCI data link, one for the primary server and the second for the secondary server.

If only one serial port is available, it is necessary to connect a data splitter unit to the serial cable and connect two serial cables from the data splitter unit, one going to the primary server, the other to the secondary server.

Two RS-232 cables connecting the two serial ports to the primary server and the secondary server.

For T1 voice connectivity, a digital trunk circuit set up as voice messaging ports and connected to voice cards in the secondary server for each digital trunk circuit that is connected to the primary server.

Cisco Unity Server

One secondary server for each primary server installed and ready for the integration, as described in the Cisco Unity Installation Guide and earlier in this integration guide.

For analog voice connectivity, the applicable cable configuration for each analog voice messaging port to simultaneously connect the phone system to the corresponding ports on both the primary and the secondary servers. For example, connect port 1 on the phone system with both port 1 on the primary server and port 1 on the secondary server.

For T1 voice connectivity, the same number of D/240PCI-T1 voice cards on the secondary server as on the primary server, connected to the phone system through T1 cables.

A license that enables failover.

Integration Description

The phone system uses two data links to send call information to the primary and secondary servers. The analog or T1 voice messaging lines from the phone system provide voice connectivity to the primary and secondary servers. Figure 4 shows the required connections for analog voice connectivity. Figure 5 shows the required connections for T1 voice connectivity.

Figure 4 Analog Connections Between the Phone System and Cisco Unity Servers

Figure 5 T1 Connections Between the Phone System and Cisco Unity Servers


Caution For T1 voice connectivity, it is necessary to either shut down the Dialogic services or disconnect the T1 line to the inactive server before the active server can answer calls.

The primary and secondary servers act in the following manner:

When the primary server is operating normally, the secondary server is inactive.

When the primary server becomes inactive, the secondary server becomes active.

When the primary server becomes active again, the secondary server becomes inactive.

Setting Up the Secondary Server for Failover

Do the applicable procedure to integrate the secondary server.

To Set Up the Secondary Server for Failover (Analog Voice Connectivity)


Step 1 Install a secondary server with the same configuration as the primary server. For installation instructions, refer to the Cisco Unity Installation Guide.

Step 2 Make all voice connections from the phone system to the corresponding ports on both the primary server and the secondary server. For example, connect port 1 from the phone system with port 1 on both the primary and the secondary servers.

Step 3 Connect the serial cables to the two serial ports on the phone system. Then connect one serial cable to the serial port on the primary server, and the other serial cable to the serial port on the secondary server.

Step 4 Program the phone system to send call information simultaneously through both serial ports.

Step 5 On the Windows Start menu of the secondary server, click Programs > Cisco Unity > Manage Integrations. The UTIM window appears.

Step 6 On the Integration menu of the UTIM window, click New. The Telephony Integration Setup Wizard appears.

Step 7 Enter the settings to match the integration settings on the primary server.

Step 8 At the prompt to restart the Cisco Unity server, click Yes. The Cisco Unity server restarts.


Note When restarting Cisco Unity, use the UTIM prompt instead of the Cisco Unity icon in the Windows taskbar. The taskbar icon does not restart all of the Cisco Unity services.


Step 9 After Cisco Unity restarts, on the Windows Start menu of the Cisco Unity server, click Programs > Cisco Unity > Manage Integrations. UTIM appears.

Step 10 In the left pane of the UTIM window, click the phone system integration you created.

Step 11 In the right pane of the UTIM window, click the Ports tab.

Step 12 Enter the port settings to match the port settings on the primary server.


Caution In programming the phone system, do not send calls to voice messaging ports in Cisco Unity that cannot answer calls (voice messaging ports that are not set to Answer Calls). For example, if a voice messaging port is set only to Dialout MWI, do not send calls to it.

Step 13 Click Save.

Step 14 Exit UTIM.

Step 15 Click Programs > Cisco Unity > Edit Switch Utility.

Step 16 In the Switch Configuration Editor window, in the Manufacturer field, click <the name of the manufacturer of the phone system>.

Step 17 In the Model field, click <the model of the phone system>.

Step 18 Click Edit.

Step 19 In the Switch Configuration dialog box, click the Incoming Calls tab.

Step 20 In the Call Rings field, enter 3 and click OK.

Step 21 In the Switch Configuration Editor dialog box, click Exit.

Step 22 On the Windows Start menu, click Run.

Step 23 Enter Regedit and click OK.


Caution Changing the wrong registry key or entering an incorrect value can cause the server to malfunction. Before you edit the registry, confirm that you know how to restore it if a problem occurs. (Refer to the "Restoring" topics in Registry Editor Help.) If you have any questions about changing registry key settings, contact Cisco TAC.

Step 24 If you do not have a current backup of the registry, click Registry > Export Registry File, and save the registry settings to a file.

Step 25 Expand the key HKEY_LOCAL_MACHINE\Software\Active Voice\Miu\1.0\Initialization.

Step 26 Double-click New Call Delay on Inactive Backup Server.

Step 27 In the Edit DWORD Value dialog box, in the Value Data field, enter 0, and click OK.

Step 28 Close the Registry Editor.

Step 29 Restart the Cisco Unity server.


No changes to the hunt group programming on the phone system are necessary for analog voice connectivity.

To Set Up the Secondary Server for Failover (T1 Voice Connectivity)


Step 1 Install a secondary server with the same configuration as the primary server. For installation instructions, refer to the Cisco Unity Installation Guide.

Step 2 Connect the T1 cables from the phone system to the secondary server.

Step 3 On the phone system, create one or more UCD groups for the voice messaging ports on the secondary server.

Step 4 Set up the RS-232 serial data port that will be connected to the secondary server.

Step 5 Use the AUOG command to set up the UCD groups for the secondary server as overflow for the primary server UCD group.

Step 6 Connect the serial cables to the two serial ports on the phone system. Then connect one serial cable to the serial port on the primary server and the other serial cable to the serial port on the secondary server.

Step 7 On the Windows Start menu of the secondary server, click Programs > Cisco Unity > Manage Integrations. The UTIM window appears.

Step 8 On the Integration menu of the UTIM window, click New. The Telephony Integration Setup Wizard appears.

Step 9 Enter the settings to match the integration settings on the primary server.

Step 10 At the prompt to restart the Cisco Unity server, click Yes. The Cisco Unity server restarts.


Note When restarting Cisco Unity, use the UTIM prompt instead of the Cisco Unity icon in the Windows taskbar. The taskbar icon does not restart all of the Cisco Unity services.


Step 11 After Cisco Unity restarts, on the Windows Start menu of the Cisco Unity server, click Programs > Cisco Unity > Manage Integrations. UTIM appears.

Step 12 In the left pane of the UTIM window, click the phone system integration you created.

Step 13 In the right pane of the UTIM window, click the Ports tab.

Step 14 Enter the port settings to match the port settings on the primary server except for the extension numbers, which are different for the secondary server.


Caution In programming the phone system, do not send calls to voice messaging ports in Cisco Unity that cannot answer calls (voice messaging ports that are not set to Answer Calls). For example, if a voice messaging port is set only to Dialout MWI, do not send calls to it.

Step 15 Click Save.

Step 16 Exit UTIM.

Step 17 If the Force Failover If Call Arrives on Inactive Secondary check box is not checked in the Failover Monitor, skip the remaining steps.

If the Force Failover If Call Arrives on Inactive Secondary check box is checked in the Failover Monitor, on the Windows Start menu of the server, click Programs > Cisco Unity > Edit Switch Utility.

Step 18 In the Switch Configuration Editor window, in the Manufacturer field, click <the name of the manufacturer of the phone system>.

Step 19 In the Model field, click <the model of the phone system>.

Step 20 Click Edit.

Step 21 In the Switch Configuration dialog box, click the Incoming Calls tab.

Step 22 In the Call Rings field, enter 3 and click OK.

Step 23 In the Switch Configuration Editor dialog box, click Exit.

Step 24 On the Windows Start menu, click Run.

Step 25 Enter Regedit and click OK.


Caution Changing the wrong registry key or entering an incorrect value can cause the server to malfunction. Before you edit the registry, confirm that you know how to restore it if a problem occurs. (Refer to the "Restoring" topics in Registry Editor Help.) If you have any questions about changing registry key settings, contact Cisco TAC.

Step 26 If you do not have a current backup of the registry, click Registry > Export Registry File, and save the registry settings to a file.

Step 27 Expand the key HKEY_LOCAL_MACHINE\Software\Active Voice\Miu\1.0\Initialization.

Step 28 Double-click New Call Delay on Inactive Backup Server.

Step 29 In the Edit DWORD Value dialog box, in the Value Data field, enter 0, and click OK.

Step 30 Close the Registry Editor.

Step 31 Restart the Cisco Unity server.



Caution For T1 voice connectivity, it is necessary to either shut down the Dialogic services or disconnect the T1 line to the inactive server before the active server can answer calls.


Dual Phone System Integration


Cisco Unity can be integrated with one each of the following phone systems at the same time:

A traditional, circuit-switched phone system. Any circuit-switched phone system that Cisco Unity integrates with can be used in a dual phone system integration.

Cisco CallManager.

All extensions for subscribers and call handlers must be unique regardless of which phone system a subscriber (or call handler) uses. To transfer calls from one phone system to the other, Cisco Unity must dial the same access codes that a subscriber dials when calling someone on the other phone system.

Dual Phone System Integration Overview

Before doing the following integration steps, confirm that theCisco Unity server is ready for the integration by completing the applicable tasks in the Cisco Unity Installation Guide.

Integration Steps When No Phone Systems Are Installed

Follow these steps to set up the dual phone system integration when no phone systems are installed.

1. Install the circuit-switched phone system.

2. Integrate the circuit-switched phone system and Cisco Unity. See instructions earlier in this integration guide.

3. Install Cisco CallManager.

4. Integrate Cisco CallManager and Cisco Unity. See the applicable Cisco CallManager integration guide, located at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_configuration_guides_list.html.

5. Change the Cisco Unity Administrator settings. See the "Changing Cisco Unity Administrator Settings" section.

Integration Steps When a Circuit-Switched Phone System Is Already Installed

Follow these steps to set up the dual phone system integration when the circuit-switched phone system is already installed and Cisco CallManager is being newly installed.

1. Install Cisco CallManager.

2. Integrate Cisco CallManager and Cisco Unity. See the applicable Cisco CallManager integration guide, located at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_configuration_guides_list.html.

3. Change the Cisco Unity Administrator settings. See the "Changing Cisco Unity Administrator Settings" section.

Integration Steps When Cisco CallManager Is Already Installed

Follow these steps to set up the dual phone system integration when Cisco CallManager is already installed and a circuit-switched phone system is being newly installed.

1. Remove the existing TSP on Cisco Unity. See the "To Remove the Existing TSP" section.

2. Install the circuit-switched phone system.

3. Integrate the circuit-switched phone system and Cisco Unity. See the instructions earlier in this integration guide.

4. Reinstall the TSP. See the "To Reinstall the TSP" section.

5. Change the Cisco Unity Administrator settings. See the "Changing Cisco Unity Administrator Settings" section.

Requirements

The dual phone system integration supports configurations of the following components:

A Cisco Unity system key with the integration type set to "Multiple integrations" and with the appropriate number of voice messaging ports enabled.

The Cisco Unity server set up and Cisco Unity 3.1(x), as described in the Cisco Unity Installation Guide.

A circuit-switched phone system installed and integrated with Cisco Unity. For details, see the instructions earlier in this integration guide. The circuit-switched phone system (including the voice card software used in the integration) must be installed and integrated with Cisco Unity before Cisco CallManager is integrated.

A supported version of Cisco CallManager and the Cisco Unity-CM service provider (TSP) installed and configured. For information about integrating Cisco Unity with Cisco CallManager and the Cisco Unity-CM service provider, see the applicable Cisco CallManager integration guide, located at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_configuration_guides_list.html.

Changing Cisco Unity Administrator Settings

After Cisco Unity is installed and the phone systems have been separately integrated, you need to adjust settings on pages in the Cisco Unity Administrator so that Cisco Unity can work with both phone systems.

Follow these steps to set up the dual phone system integration.

1. Specify settings for the circuit-switched phone system on the System > Switch > Switch page. For details, see the "To Specify Switch Settings for the Circuit-Switched Phone System" section.


Caution Specify settings for the circuit-switched phone system before specifying settings for Cisco CallManager. You must proceed in this order, or the integration may not work.

2. Specify settings for Cisco CallManager on the IP Switch page. For details, see the "To specify switch settings for Cisco CallManager" section.

3. On the Ports page, assign port ranges to the circuit-switched phone system first, then to CallManager, and adjust settings for the ports assigned to each phone system. For details, see the "To Modify Voice Port Settings" section.

4. Select the phone system that subscribers and call handlers use. For details, see the "To Select Which Phone System Subscribers and Call Handlers Use" section.

5. Select the phone system that Cisco Unity uses when dialing out to send message notifications. For details, see the "To Select Which Phone System Cisco Unity Uses for Message Notification" section.


Caution If you need to add or remove voice cards or uninstall the voice card software after the dual phone system integration is set up, you must also reinstall the TSP (Cisco Unity-CM service provider). Do not reinstall the TSP until after you have set up the voice cards or reinstalled the voice card software. For more information, see the "Changing the Number of Installed Ports" section.

To Specify Switch Settings for the Circuit-Switched Phone System


Step 1 Go to the System > Switch > Switch page. The settings for the circuit-switched phone system selected during the Cisco Unity Setup program appear.

Step 2 In the Access Code field, enter the trunk access code that Cisco Unity must dial to transfer calls to Cisco CallManager from the circuit-switched phone system.

The access code is the same number that subscribers on the circuit-switched phone system dial to reach someone on the Cisco CallManager system.

Step 3 Adjust other settings as applicable. For more information about the other settings on the Switch page, refer to the online Help in the Cisco Unity Administrator.

Step 4 Click the Save icon, then click OK in the Warning dialog box.


To specify switch settings for Cisco CallManager


Step 1 Go to the System > Switch > IP Switch page.

Step 2 In the Set Active Switch Type section, enter values as shown in the following table:

Table 8 Switch Settings 

Switch Parameter
Required Setting

Manufacturer

Cisco

Model

CallManager

Switch PBX software version

3.01 or later

Integration

TAPI


Step 3 Click Set As Active, then click OK in the Warning dialog box.

Step 4 In the Access Code field, enter the trunk access code that Cisco Unity must dial to transfer calls to the circuit-switched phone system from Cisco CallManager.

The access code is the same number that subscribers on Cisco CallManager dial to reach someone on the circuit-switched phone system.

Step 5 Click the Save icon, then click OK in the Warning dialog box.


To Modify Voice Port Settings


Step 1 Go to the System > Ports page.

Step 2 In the Port Assignments section, indicate the range of ports to be assigned to the circuit-switched phone system. The port range for the circuit-switched phone system begins with 1 and extends to no more than the number of ports that are on the installed voice cards. Do not assign more ports to the circuit-switched phone system than the number of ports on the voice cards.


Caution If you assign fewer voice ports to the circuit-switched phone system than are available on the installed voice cards, you must edit the registry for this port range to take effect. Otherwise, all available voice ports on the voice cards are used in the integration regardless of the Port Assignments settings. For information on editing the registry for the port range, see the appendix "Assigning Dialogic Ports for a Dual Phone System Integration."

Step 3 In the Port Assignments section, indicate the range of ports to be assigned to Cisco CallManager. The port range must begin with the next port after the last port for the circuit-switched phone system. The range for Cisco CallManager must end with the port number of the last port displayed on the Ports page, or the number of licensed voice ports on the system key, whichever is lower. In other words, the number of ports available for Cisco CallManager is the difference between the number of licensed voice ports on the system key and the number of ports assigned to the circuit-switched phone system.

Step 4 Enter an extension for each port.

Step 5 Specify other settings as applicable. For each phone system, confirm that an appropriate number of ports are used to answer calls and to dial out for message waiting indicators (MWIs), message notifications, and Media Master recordings by phone.

Step 6 Click the Save icon.


Caution The port range for each phone system must be set as specified in Step 2 and Step 3 above. If there is a port range mismatch, Cisco Unity will be unable to answer incoming calls and to dial out.

To Select Which Phone System Subscribers and Call Handlers Use

For existing subscriber templates, subscriber accounts, and call handlers, Cisco Unity uses the circuit-switched phone system as its default. Therefore, during the initial setup of the dual phone integration, you will modify only those pages that will be using Cisco CallManager. Note that changes made to subscriber templates do not affect existing subscriber accounts.


Step 1 In Cisco Unity Administrator, go to the applicable page:

Subscribers > Subscriber Template > Profile

Subscribers > Subscribers > Profile

Call Management > Call Handlers > Profile

Step 2 In the Switch list, select the applicable phone system.

Step 3 Adjust other settings as applicable. For more information, refer to the online Help in the Cisco Unity Administrator.


Caution If the Switch setting on the Profile page for the subscriber or call handler does not match the phone system actually used by a subscriber or call handler, Cisco Unity will not be able to transfer calls to or from the subscriber or call handler. Additionally, Cisco Unity will be unable to turn the MWIs for the subscriber on or off and will be unable to reach the extension for the subscriber when recording by phone with Media Master.

To Select Which Phone System Cisco Unity Uses for Message Notification

If subscribers use message notification, you can select which phone system Cisco Unity dials out on when notifying subscribers of new messages. Note that changes made to subscriber templates do not affect existing subscribers.


Step 1 In Cisco Unity Administrator, go to the applicable page:

Subscribers > Subscriber Template > Message Notification

Subscribers > Message Notification.

Step 2 For each device, in the Switch list select the phone system that Cisco Unity uses to dial out when notifying subscribers of new messages. Each notification device can be associated with a specific phone system (except for text pagers).

Cisco Unity uses the phone system specified on the subscriber template Profile page as the default.

Step 3 Adjust other settings as applicable. For more information, refer to the online Help in the Cisco Unity Administrator.


Caution The selected phone system must have at least one port set to dial out for message notifications on the System > Ports page. If the selected phone system does not have any ports set for this function, notifications will fail.

Changing the Number of Installed Ports

After the dual phone system integration is set up, if you need to add or remove voice cards or uninstall voice card software, follow these steps:

1. Remove the existing TSP. For details, see the "To Remove the Existing TSP" section. (In versions earlier than 3.1(1), the Cisco Unity-CM TSP was known as the AV-Cisco TSP.)

2. As applicable, remove or add voice cards, or uninstall and reinstall the voice card software. For information about removing Dialogic voice card software, refer to the chapter about voice cards in the Cisco Unity Installation Guide.

3. Reinstall the TSP after you have set up the voice cards or reinstalled the voice card software. For details, see the "To Reinstall the TSP" section.

4. Adjust the port assignments on the System > Ports page. The voice messaging ports must appear in the following order in the list of ports: first are all the ports connected to the circuit-switched phone system, second are the ports connected to CallManager.

If you completely remove the circuit-switched phone system, you must adjust the port assignments for Cisco CallManager on the System > Ports page, after the voice cards and voice card software used in the integration with the circuit-switched phone system have been removed.

To Remove the Existing TSP


Step 1 On the Cisco Unity server, log on to Windows as an administrator.

Step 2 Stop Cisco Unity (right-click the Cisco Unity icon in the system tray, then click Stop Unity).

Step 3 On the Windows Start menu, click Settings > Control Panel > Add/Remove Programs.

Step 4 In the list, click Cisco Unity-CM TSP.


Note In versions earlier than 3.1(1), the Cisco Unity-CM TSP was known as the AV-Cisco TSP.


Step 5 Click Remove.

Step 6 Click Yes.

Step 7 Close Control Panel.


To Reinstall the TSP


Step 1 On the Cisco Unity server, log on to Windows as an administrator.

Step 2 On the Windows Start menu, click Settings > Control Panel.

Step 3 Double-click Phone and Modem Options. The Phone and Modem Options dialog box appears.

Step 4 Click the Advanced tab.

Step 5 Click Add. The Add Driver dialog box appears.

Step 6 Click Cisco Unity-CM Service Provider, then click Add. A dialog box appears confirming the installation of the TSP.

Step 7 Click OK to close the dialog box.

Step 8 Click Close to close the Phone and Modem Options dialog box.

Step 9 Close Control Panel.

Step 10 Restart the Cisco Unity server.



Appendix: Enabling Cisco Unity to Trim Disconnect Tones


Under certain conditions, the phone system may send a disconnect tone that the voice cards do not interpret right away as being a disconnect. In these circumstances, Cisco Unity will record the disconnect tone in messages.

When the disconnect tone sent by the phone system cannot be changed, it is possible to enable Cisco Unity to remove (or trim) the disconnect tone from messages. To do this, you must edit the phone configuration file (also known as the switch .ini file). Do the following procedure on the Cisco Unity server.

To Enable Cisco Unity to Trim Disconnect Tones


Step 1 On the Windows Start menu, click Programs > Cisco Unity > Manage Integrations. UTIM appears.

Step 2 In the left pane of the UTIM window, click the phone system integration, and click the Properties node.

Step 3 In the right pane of the UTIM window, click the Integration tab.

Step 4 Note the name of the phone configuration file that appears in the Configuration File field.

Step 5 Exit UTIM.

Step 6 On the Windows Start menu, click Programs > Accessories > Notepad. The Notepad window appears.

Step 7 On the File menu, click Open.

Step 8 In the Open dialog box, browse to the \CommServer\IntLib directory, and double-click the name of the Switch.ini file you noted in Step 4.

Step 9 In the Configuration section of the file, locate the following line:

TrimDisconnectTonesOnRecordings=0

If the line does not exist in the Configuration section, skip to the next step.

Step 10 If you located the line, change the final digit of the line to 1 so that the line reads:

TrimDisconnectTonesOnRecordings=1

If the line does not exist in the Configuration section, add the line shown above to the end of the Configuration section.

Step 11 Save the file, and exit Notepad.

Step 12 For the settings to take effect, restart the Cisco Unity server.



Appendix: Remapping Extension Numbers


About the Remapping Feature

The extension remapping feature lets you convert to the extensions of your choice the calling numbers and forwarding numbers of calls handled by Cisco Unity. This feature is useful, for example, when the phone system cannot map multiple extension numbers on a subscriber phone to a single Inbox.

Remapping can change one or both of the following extension numbers in a call:

Calling number (the number from which a call originates). For example, Cisco Unity changes the calling number of calls so that the caller ID appears to be a different extension than the one that actually placed the call.

Forwarding number (the number that a call is going to). For example, unanswered calls to all line extensions on a single phone can be forwarded to the Inbox of a single subscriber; or unanswered calls to phones not assigned to subscribers can be forwarded to the Inbox of a supervisor.

Setting Up Cisco Unity to Remap Extension Numbers

This section includes a procedure for enabling the remapping feature. You can create multiple files in either or both of two directories:

In the Calling directory, one or more .exm files remap caller ID numbers.

In the Forwarding directory, one or more .exm files remap numbers that Cisco Unity provides with calls it forwards.

When you create remapping instructions in a .exm file in a directory, Cisco Unity remaps only the type of extension number that the directory is named for. For example, if you want to remap only the extensions that Cisco Unity provides with calls it forwards, you enter the instructions in a .exm file in the Forwarding directory; in this circumstance, the Calling directory needs no .exm file.

In each directory, you can have several .exm files with different file names but with the same .exm extension. This helps you to organize the remapping information. For example, you could create two files in a directory: Ports_1-12.exm and Ports_13-24.exm. Cisco Unity reads all files that have the .exm extension in these directories.

To Remap Extension Numbers


Step 1 On the Cisco Unity server, browse to the CommServer\IntLib\ExtensionMapping directory. In this directory is the file Sample.txt and two more directories: Calling and Forwarding.

Step 2 To remap calling numbers, go to the Calling directory.

Step 3 In a text editor application, create a new .exm file, or open a currently existing .exm file.

For an example, open the file Sample.txt in the CommServer\IntLib\ExtensionMapping directory.

Step 4 Enter [Range] and press Return to create a section for indicating which voice messaging ports will be monitored for remapping calls.

A .exm file can have only one [Range] section.

Step 5 Enter ports= followed by the numbers of the voice messaging ports, separated by commas. Ranges are designated by a hyphen (-) without spaces. To monitor all voice messaging ports, enter ports=* on this line. Then press Return.

For example, you might enter:

ports=1,2,5-34

Step 6 To create a section for the remapping rules, press Return, enter [Number Mappings], and then press Return.

A .exm file can have only one [Number Mappings] section.

Step 7 Enter one remapping rule on the line, and then press Return.

See the remapping rule examples in the following "Syntax and Examples" section. The rule format is:

<original number>, <new number>

The rules cannot include spaces between digits. However, the numbers must be separated by a comma and a single space. Wildcard characters cannot appear at the beginning of a number.

Step 8 For all remaining rules, repeat Step 7.

Step 9 Save and close the .exm file.

Step 10 To remap forwarding numbers, browse to the directory CommServer\IntLib\ExtensionMapping\Forwarding.

Step 11 Repeat Step 3 through Step 9 to remap forwarding numbers.

Step 12 For extension remapping to take effect, restart the Cisco Unity software.


Syntax and Examples

Table 9 shows the wildcard characters you can use in the .exm files.

Table 9 Wildcard Characters 

Wildcard
Result

*

Matches zero or more digits.

?

Matches exactly one digit. Use ? as a placeholder for a single digit.


Table 10 gives examples for the syntax and results of rules in the .exm files.

Table 10 Syntax Examples 

Rule
Original Number
New Number

2189, 1189

3189, 1189

4189, 1189

2189

3189

4189

1189

1189

1189

2???, 1???

2189

2291

1189

1291

3???, 1???

3189

3291

1189

1291

8???, 61???

8000

8765

61000

61765

123*, 44*

12300

12385

4400

4485


Cisco Unity executes rules in the order they appear in the .exm file. For example, the .exm file might contain the following rules:

1234, 1189
3189, 1189
4189, 1189
123?, 8891

The extension 1234 would be remapped to 1189 while extensions 1233 and 1235 would be remapped to 8891, because the rule mapping 1234 appears earlier.

An .exm file might contain the following:

[Range]
ports=1,2,5-34

[Number Mappings]
2189, 1189
3189, 1189
4189, 1189
8???, 9???


Appendix: Assigning Dialogic Ports for a Dual Phone System Integration


In a dual phone system integration, Cisco Unity assigns a voice messaging port to the traditional, circuit-switched phone system for every port available on the installed voice cards before assigning voice messaging ports to Cisco CallManager. The result is that Cisco Unity may not have enough voice messaging ports remaining to assign to Cisco CallManager.

The maximum number of voice messaging ports are assigned to the circuit-switched phone system regardless of the settings on the Ports page in the System Administrator.

For example, a dual phone system integration might have the following configuration:

A circuit-switched phone system has a four-port voice card installed.

Cisco CallManager has six Voice Mail ports set up.

The Cisco Unity server has a system key enabled for a total of eight ports.

The Ports page on System Administrator indicates that Ports 1 and 2 are assigned to the circuit-switched phone system and Ports 3 through 8 are assigned to Cisco CallManager.

Even so, Ports 1 through 4 (the total voice card ports) will be assigned to the circuit-switched phone system, and Ports 5 through 6 will be assigned to Cisco CallManager.

If you want to assign fewer than the total number of voice card ports to the circuit-switched phone system, you must first set the Port assignments on the Ports page of the System Administrator, then do the following procedure.

To Set the Port Assignments in the Registry


Step 1 On the Cisco Unity server, on the Windows Start menu, click Run.

Step 2 In the Open field, enter Regedit and press Enter. The Registry Editor appears.


Caution Changing the wrong registry key or entering an incorrect value can cause the server to malfunction. Before you edit the registry, confirm that you know how to restore it if a problem occurs. (Refer to the "Restoring" topics in Registry Editor Help.) Note that a typical backup of the Cisco Unity server does not back up the registry. Also note that for a Cisco Unity failover system, registry changes on one Cisco Unity server must be made manually on the other Cisco Unity server, because registry changes are not replicated. If you have any questions about changing registry key settings, contact Cisco TAC.

Step 3 If you do not have a current backup of the registry, click Registry > Export Registry File, and save the registry settings to a file.

Step 4 Expand the key HKEY_LOCAL_MACHINE\Software\ActiveVoice\MIU\1.0\Initialization\ServiceProvider <x>, where <x> is a number.

You will find several subkeys with this name.

Step 5 Locate the subkey in which the value Service Provider Name is D41MT.TSP.

Step 6 In this subkey, in the Edit menu click New > DWORD Value. A new value appears in the subkey.

Step 7 Enter the name DeviceID Lower Bound and press Enter.

Step 8 Double-click the DeviceID Lower Bound value. The Edit DWORD Value dialog box appears.

Step 9 In the Value Data field, enter 1 and click OK.

Step 10 in the Edit menu click New > DWORD Value. A new value appears in the subkey.

Step 11 Enter the name DeviceID Upper Bound and press Enter.

Step 12 Double-click the DeviceID Upper Bound value. The Edit DWORD Value dialog box appears.

Step 13 In the Value Data field, enter the number of Dialogic ports you want to assign and click OK.

Step 14 Close the Registry Editor.

Step 15 For the settings to take effect, exit and restart the Cisco Unity software.



Appendix: Documentation and Technical Assistance


Conventions

The NEC NEAX 2400 with Serial MCI Integration Guide for Cisco Unity 3.1 uses the following conventions.

Table 11 NEC NEAX 2400 with Serial MCI Integration Guide for Cisco Unity 3.1 Conventions 

Convention
Description

boldfaced text

Boldfaced text is used for:

Key and button names. (Example: Click OK.)

Information that you enter. (Example: Enter Administrator in the User Name box.)

< >

(angle brackets)

Angle brackets are used around parameters for which you supply a value. (Example: In the Command Prompt window, enter ping <IP address>.)

-

(hyphen)

Hyphens separate keys that must be pressed simultaneously. (Example: Press Ctrl-Alt-Delete.)

>

(right angle
bracket)

A right angle bracket is used to separate selections that you make:

On menus. (Example: On the Windows Start menu, click Settings > Control Panel > Phone and Modem Options.)

In the navigation bar of the Cisco Unity Administrator. (Example: Go to the System > Configuration > Settings page.)

[x]

(square brackets)

Square brackets enclose an optional element (keyword or argument). (Example: [reg-e164])

[x | y]

(vertical line)

Square brackets enclosing keywords or arguments separated by a vertical line indicate an optional choice. (Example: [transport tcp | transport udp])


The NEC NEAX 2400 with Serial MCI Integration Guide for Cisco Unity 3.1 also uses the following conventions:


Note Means reader take note. Notes contain helpful suggestions or references to material not covered in the document.



Caution Means reader be careful. In this situation, you might do something that could result in equipment damage or loss of data.

Section heading: Cisco Unity Documentation

Used in: All book prefaces, all release notes, pretty much everything.
Last updated: 2/12/04, CA. Last edited: 2/12/04, CA.

For descriptions and URLs of Cisco Unity documentation on Cisco.com, refer to About Cisco Unity Documentation. The document is shipped with Cisco Unity and is available at http://www.cisco.com/univercd/cc/td/doc/product/voice/c_unity/about/aboutdoc.htm.

Obtaining Documentation

Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.

Cisco.com

You can access the most current Cisco documentation on the World Wide Web at this URL:

http://www.cisco.com/univercd/home/home.htm

You can access the Cisco website at this URL:

http://www.cisco.com

International Cisco websites can be accessed from this URL:

http://www.cisco.com/public/countries_languages.shtml

Ordering Documentation

You can find instructions for ordering documentation at this URL:

http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm

You can order Cisco documentation in these ways:

Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Ordering tool:

http://www.cisco.com/en/US/partner/ordering/index.shtml

Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, USA) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).

Documentation Feedback

You can submit e-mail comments about technical documentation to bug-doc@cisco.com.

You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:

Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Obtaining Technical Assistance

For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, the Cisco Technical Assistance Center (TAC) provides 24-hour-a-day, award-winning technical support services, online and over the phone. Cisco.com features the Cisco Technical Support website as an online starting point for technical assistance. If you do not hold a valid Cisco service contract, please contact your reseller.

Cisco Technical Support Website

The Cisco Technical Support website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The Cisco Technical Support website is available 24 hours a day, 365 days a year. The Cisco Technical Support website is located at this URL:

http://www.cisco.com/tac

Accessing all the tools on the Cisco Technical Support website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a login ID or password, register at this URL:

http://tools.cisco.com/RPF/register/register.do

Opening a TAC Case

Using the online TAC Case Open Tool is the fastest way to open P3 and P4 cases. (P3 and P4 cases are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Case Open Tool automatically recommends resources for an immediate solution. If your issue is not resolved using the recommended resources, your case will be assigned to a Cisco TAC engineer. The online TAC Case Open Tool is located at this URL:

http://www.cisco.com/tac/caseopen

For P1 or P2 cases (P1 and P2 cases are those in which your production network is down or severely degraded) or if you do not have Internet access, contact Cisco TAC by telephone. Cisco TAC engineers are assigned immediately to P1 and P2 cases to help keep your business operations running smoothly.

To open a case by telephone, use one of the following numbers:

Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447

For a complete listing of Cisco TAC contacts, go to this URL:

http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

TAC Case Priority Definitions

To ensure that all cases are reported in a standard format, Cisco has established case priority definitions.

Priority 1 (P1)—Your network is "down" or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.

Priority 2 (P2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.

Priority 3 (P3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.

Priority 4 (P4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.

Obtaining Additional Publications and Information

Information about Cisco products, technologies, and network solutions is available from various online and printed sources.

Cisco Marketplace provides a variety of Cisco books, reference guides, and logo merchandise. Go to this URL to visit the company store:

http://www.cisco.com/go/marketplace/

The Cisco Product Catalog describes the networking products offered by Cisco Systems, as well as ordering and customer support services. Access the Cisco Product Catalog at this URL:

http://cisco.com/univercd/cc/td/doc/pcat/

Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press online at this URL:

http://www.ciscopress.com

Packet magazine is the Cisco quarterly publication that provides the latest networking trends, technology breakthroughs, and Cisco products and solutions to help industry professionals get the most from their networking investment. Included are networking deployment and troubleshooting tips, configuration examples, customer case studies, tutorials and training, certification information, and links to numerous in-depth online resources. You can access Packet magazine at this URL:

http://www.cisco.com/packet

iQ Magazine is the Cisco bimonthly publication that delivers the latest information about Internet business strategies for executives. You can access iQ Magazine at this URL:

http://www.cisco.com/go/iqmagazine

Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:

http://www.cisco.com/ipj

Training—Cisco offers world-class networking training. Current offerings in network training are listed at this URL:

http://www.cisco.com/en/US/learning/index.html