Fujitsu 9600 Serial Integration Guide for Cisco Unity 5.0

Revised November 26, 2007

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 Fujitsu 9600 phone system, confirm that the Cisco Unity server is ready for the integration by completing the applicable tasks in the applicable Cisco Unity installation guide.

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

Task List to Create the Integration

Use the following task list to set up a new integration with the Fujitsu 9600 phone system. If you are installing a new Cisco Unity server by using the applicable Cisco Unity installation guide, you may have already completed some of the following tasks.

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.

•A license that enables the applicable number of voice messaging ports.

•An available serial port (COM1 is the default).

Integration Description

The Fujitsu 9600 integration uses a data link, which consists of an RS-232 serial cable connecting the phone system and the Cisco Unity server. The voice messaging lines from the phone system connect to the analog voice cards in the Cisco Unity server. Figure 1 shows the required connections.

Figure 1 Connections Between the Phone System and Cisco Unity

Call Information

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 Functionality

The Fujitsu 9600 integration with Cisco Unity provides the following integration features:

•Call forward to personal greeting

•Call forward to busy greeting

•Caller ID

•Easy message access (a subscriber can retrieve messages without entering an ID because Cisco Unity identifies the subscriber based on the extension from which the call originated; a password may be required)

•Identified subscriber messaging (Cisco Unity identifies the subscriber who leaves a message during a forwarded internal call, based on the extension from which the call originated)

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 following table describes the voice messaging port settings in Cisco Unity that can be set in UTIM, and that are displayed as read-only text on the System > Ports page of the Cisco Unity Administrator.

Table 1 Settings for the Voice Messaging Ports

Field

Considerations

Extension

Enter the extension for the port as assigned on the phone system.

Enabled

Check this check box to enable the port. The port is enabled during normal operation.

Uncheck this check box to disable the port. When the port is disabled, calls to the port get a ringing tone but are not answered. Typically, the port is disabled only by the installer during testing.

Answer Calls

Check this check box to designate the port for answering calls. These calls can be incoming calls from unidentified callers or from subscribers.

Message Notification

Check this check box to designate the port for notifying subscribers of messages. Assign Message Notification to the least busy ports.

Dialout MWI

(not used by serial or SMDI integrations)

Check this check box to designate the port for turning MWIs on and off. Assign Dialout MWI to the least busy ports.

AMIS Delivery

(available with the AMIS licensed feature only)

Check this check box to designate the port for making outbound AMIS calls to deliver voice messages from Cisco Unity subscribers to users on another voice messaging system. Cisco Unity supports the Audio Messaging Interchange Specification (AMIS) protocol, which provides an analog mechanism for transferring voice messages between different voice messaging systems.

This setting affects outbound AMIS calls only. All ports are used for incoming AMIS calls.

Because the transmission of outgoing AMIS messages may tie up voice ports for long periods of time, you may want to adjust the schedule on the Network > AMIS > Schedule page so that outgoing AMIS calls are placed during closed hours or at times when Cisco Unity is not processing many calls.

TRAP Connection

Check this check box so that subscribers can use the phone as a recording and playback device in Cisco Unity web applications and e-mail clients. Assign TRAP Connection to the least busy ports.

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 TRAP connections needed when call traffic is at its peak. (TRAP connections are used by Cisco Unity web applications to play back and record over the phone.)

•The number of calls that will use the automated attendant and call handlers when call traffic is at its peak.

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, the voice messaging ports that answer calls are the busiest.

You can set voice messaging ports to both answer calls and to dial out (for example, to send message notifications). However, when the voice messaging ports perform more than one function and are very active (for example, answering many calls), the other functions may be delayed until the voice messaging port is free (for example, message notifications cannot be sent until there are fewer calls to answer). For best performance, dedicate certain voice messaging ports for only answering incoming calls, and dedicate other ports for only dialing out. Separating these port functions eliminates 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.

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 TRAP connection so that subscribers can use the phone as a recording and playback device in Cisco Unity web applications.

Typically, these voice messaging ports are the least busy ports.

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.

Programming the Fujitsu 9600 Phone System

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

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.

Do the following procedure.

To Program the Fujitsu 9600 Phone System

Step 1 Assign a DCC port for integration with Cisco Unity.

Step 2 On the phone system, in Assign Single Line Phone, set Type to 1 for the Fujitsu 9600 phone lines used as voice messaging ports.

Step 3 In Change Service Parameter, make the following changes:

•Set Type to 2 and ID:01 to 01 for the Fujitsu 9600 phone lines used as voice messaging ports.

Note This setting disables the immediate ring feature.

•Set Type to 2 and ID:64 to 0 for the reorder tone so that Cisco Unity can recognize disconnected calls.

•Set Type to 1 and ID:41 to 500 (500 milliseconds) for the hookflash timer to match the setting in Cisco Unity.

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

Table 2 Call Transfer Types

Transfer Type

Usage

Release transfer(blind transfer)

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

•The extension is busy

•The call is not answered

Supervised transfer

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

Creating a New Integration with the Fujitsu 9600 Phone System

After ensuring that the Fujitsu 9600 phone system and the Cisco Unity server are ready for the integration, do the following procedures to set up the integration and to enter the port settings.

<the station prefix plus the default extension length; accept the default or click another setting; this length is either 10 or 7>

Default Extension Length

<the default length of extensions on the phone system; accept the default or click another setting>

Step 9 On the Select COM Port Settings page, enter the following settings, then click Next.

Table 5 Settings for the Select COM Port Settings Page

Field

Setting

COM Port

<the communications port on the Cisco Unity server that will receive the call information; typically, this setting is 1>

Baud Rate

<the baud rate that the phone system uses>

Data Bits

<the number of data bits that the phone system uses>

Stop Bits

<the number of stop bits that the phone system uses>

Parity

<the parity that the phone system uses>

Step 10 On the Set Number of Voice Messaging Ports page, enter the number of voice messaging ports on Cisco Unity that you want to connect to the phone system, then click Next.

This number cannot be more than the number of ports on the installed voice cards or the number of ports set up on the phone system.

Step 11 If other integrations already exist, the Enter Trunk Access Code page appears. Enter the extra digits that Cisco Unity must use to transfer calls through the gateway to extensions on the other phone systems with which it is integrated. Then click Next.

Step 12 On the Reassign Subscribers page, any subscribers whose phone system integration has been deleted and who are not currently assigned to a phone system integration will appear in the list.

If no subscribers appear in the list, click Next and continue to Step 13.

Otherwise, select the subscribers that you want to assign to this phone system integration and click Next. You can use the following selection controls for selecting subscribers.

Table 6 Selection Controls for the Reassign Subscribers Page

Selection Control

Effect

Check All

Checks the check boxes for all subscribers in the list.

Uncheck All

Unchecks the check boxes for all subscribers in the list.

Toggle Selected

For the subscribers highlighted in the list, toggles between checking and unchecking the check boxes.

If some highlighted subscriber check boxes are checked and others are unchecked, clicking this button will check all the check boxes. Clicking again will uncheck all the check boxes.

Step 13 On the Reassign Call Handlers page, any call handlers whose phone system integration has been deleted and that are not currently assigned to a phone system integration will appear in the list.

If no call handlers appear in the list, click Next and continue to Step 14.

Otherwise, select the call handlers that you want to assign to this phone system integration and click Next. You can use the following selection controls for selecting call handlers.

Table 7 Selection Controls for the Reassign Call Handlers Page

Selection Control

Effect

Check All

Checks the check boxes for all call handlers in the list.

Uncheck All

Unchecks the check boxes for all call handlers in the list.

Toggle Selected

For the call handlers highlighted in the list, toggles between checking and unchecking the check boxes.

If some highlighted call handler check boxes are checked and others are unchecked, clicking this button will check all the check boxes. Clicking again will uncheck all the check boxes.

Step 14 On the Completing page, verify the settings you entered, then click Finish.

For best performance, 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.

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 Message Notification, do not send calls to it.

Table 8 Settings for the Voice Messaging Ports

Field

Considerations

Extension

Enter the extension for the port as assigned on the phone system.

Enabled

Check this check box to enable the port. The port is enabled during normal operation.

Uncheck this check box to disable the port. When the port is disabled, calls to the port get a ringing tone but are not answered. Typically, the port is disabled only by the installer during testing.

Answer Calls

Check this check box to designate the port for answering calls. These calls can be incoming calls from unidentified callers or from subscribers.

Message Notification

Check this check box to designate the port for notifying subscribers of messages. Assign Message Notification to the least busy ports.

Dialout MWI

(not used by serial or SMDI integrations)

Check this check box to designate the port for turning MWIs on and off. Assign Dialout MWI to the least busy ports.

AMIS Delivery

(available with the AMIS licensed feature only)

Check this check box to designate the port for making outbound AMIS calls to deliver voice messages from Cisco Unity subscribers to users on another voice messaging system. Cisco Unity supports the Audio Messaging Interchange Specification (AMIS) protocol, which provides an analog mechanism for transferring voice messages between different voice messaging systems.

This setting affects outbound AMIS calls only. All ports are used for incoming AMIS calls.

Because the transmission of outgoing AMIS messages may tie up voice ports for long periods of time, you may want to adjust the schedule on the Network > AMIS > Schedule page so that outgoing AMIS calls are placed during closed hours or at times when Cisco Unity is not processing many calls.

TRAP Connection

Check this check box so that subscribers can use the phone as a recording and playback device in Cisco Unity web applications and e-mail clients. Assign TRAP Connection to the least busy ports.

Step 6 Click Save.

Step 7 Exit UTIM.

If the phone system uses extension numbers that begin with zero (for example, 0123 or 09876), do the following procedure.

Note that after the procedure is done all extension numbers must have the same number of digits. In this case, for example, 0123 and 1234 are both allowed, but 0123 and 234 are not allowed. The extension 234 would be interpreted as 0234.

•In the status bar next to the clock, right-click the Cisco Unity tray 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 which port 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 correctly 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 the test 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 which port handles this call.

Step 8 Leave a message for the test 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 Listening to Messages

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

Step 2 When asked for your password, enter the default password. 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 the test subscriber (if you did not record a voice name for the test subscriber, you will hear the extension number for Phone 1). Hearing the voice name means that Cisco Unity correctly identified the subscriber by the extension.

If the name of the test subscriber is not displayed, click the Find icon (the magnifying glass) in the title bar, then click Find, and select the name of the test subscriber in the list that appears.

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

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 which port 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 the test 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.

Requirements

The following components are required to integrate a secondary server:

Phone System

•A serial data port for the data link.

•A data splitter unit to split the single data link into two serial cables.

•Two additional RS-232 serial cables (to be used with the serial cable from the integration of the primary server). With the three serial cables, connect one from the data port in the phone system to the data splitter unit; connect the second from the data splitter unit to the serial port on the primary server; and connect the third from the data splitter unit to the serial port on the secondary server.

Cisco Unity Server

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

•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.

•A license that enables failover.

Integration Description

The phone system uses a data link to send call information to the primary and secondary servers. The data splitter unit splits the single serial cable into two serial cables, enabling the data link to connect to the primary and secondary servers. The analog voice messaging lines from the phone system provide voice connectivity to the primary and secondary servers. Figure 2 shows the required connections.

Figure 2 Connections Between the Phone System and Cisco Unity Servers

The primary and secondary servers act in the following manner:

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

Setting Up the Secondary Server for Failover

Step 1 Install a secondary server with the same configuration as the primary server. For installation instructions, refer to the applicable 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 one serial cable from the serial port on the phone system to the data splitter unit.

Step 4 Connect the remaining two serial cables to the two serial ports on the data splitter unit. 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 Enter the settings to match the integration settings on the primary server.

Note We recommend not reassigning any unassigned subscribers and call handlers to the new integration, if you are asked by the wizard. Failover replication will automatically assign the correct integration.

Step 8 At the prompt to restart the Cisco Unity services, click Yes.

Note When restarting the Cisco Unity services, 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 10 In the left pane of the UTIM window, click the phone system integration that you created in Step 6.

Step 11 In the right pane, click Properties.

Step 12 On the Integration tab, compare the setting of the Integration ID field for the secondary server to the setting of the Integration ID field for the primary server.

Step 13 If the integration IDs of the phone system on the primary and secondary server are the same, continue to Step 19.

If the integration IDs of the phone system on the primary and secondary servers are different, on the secondary server, click Modify Integration ID.

Step 14 When cautioned that subscribers associated with the current Integration ID setting will not be automatically associated with the new Integration ID setting, click OK.

Step 15 In the Modify Integration ID dialog box, in the Enter New Integration ID field, enter the Integration ID setting for the phone system on the primary server and click OK.

Step 16 Click Save.

Step 17 At the prompt to restart the Cisco Unity services, click No.

Step 18 In the left pane, click the phone system integration that you created in Step 6.

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

Step 20 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.

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 32 If you do not have a current backup of the registry, click Registry > Export Registry File, and save the registry settings to a file.

Obtaining Documentation, Obtaining Support, and Security Guidelines

For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.