Cisco Unity

Table Of Contents

Nortel SL-100 Serial SMDI TIMG Integration Guide for Cisco Unity 4.2

Integration Tasks

Task List to Create the Integration

Requirements

Integration Description

Call Information

Integration Functionality

Integrations with Multiple Phone Systems

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

Programming the Nortel SL-100 Phone System

Setting Up the TIMG Units

Downloading and Installing the Required Cisco Unity ES File (Cisco Unity 4.2(1) Only)

Creating an Integration with the Phone System

Testing the Integration

Integrating a Secondary Server for Cisco Unity Failover

Requirements

Integration Description

Setting Up the Secondary Server for Failover

Appendix: Documentation and Technical Assistance

Conventions

Obtaining Documentation, Obtaining Support, and Security Guidelines

Nortel SL-100 Serial SMDI TIMG Integration Guide for Cisco Unity 4.2

---

Revised August 30, 2007

This document provides instructions for integrating the Nortel SL-100 phone system with Cisco Unity 4.2 by using TIMG units (T1 media gateways), T1 digital lines (DS1 or "dry T1" digital lines only), and an RS-232 serial cable.

Integration Tasks

Before doing the following tasks to integrate Cisco Unity with the Nortel SL-100 phone system by using the TIMG units (T1 media gateways), 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 Nortel SL-100 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.

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. Program the Nortel SL-100 phone system and extensions. See the "Programming the Nortel SL-100 Phone System" section.

4. Set up the TIMG units. See the Setting Up the TIMG Units.

5. (Cisco Unity 4.2(1) only) Download and install the required Cisco Unity ES file. See the Downloading and Installing the Required Cisco Unity ES File (Cisco Unity 4.2(1) Only).

6. Create the integration. See the Creating an Integration with the Phone System.

---

Caution Do not edit the phone configuration file (also known as the switch ini file) to customize this integration. If you change the settings in this file, the integration may not function correctly.

---

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

8. If you have a secondary server for Cisco Unity failover, integrate the secondary server. See the "Integrating a Secondary Server for Cisco Unity Failover" section.

Requirements

The Nortel SL-100 integration supports configurations of the following components:

Phone System

•The Nortel SL-100 phone system.

•Software version SE-06 or later.

•T1 digital trunk interface card (NT5D11).

•The firmware must be configured to support T1 line-side signaling.

•T1 CAS connections to the TIMG units by using the FXS/FSO or E&M protocol.

•One or more TIMG units (media gateways). For details, refer to the "Supported Phone System Integrations Through PIMG/TIMG Units" section in the applicable Supported Hardware and Software, and Support Policies for Cisco Unity at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.

•The serial data port on the phone system connected to the serial port on the master TIMG unit with an RS-232 serial cable (which is available from Cisco).

Specifications for the serial cable are in Connecting PBX-IP Media Gateway (PIMG) to the Serial Port of a PBX at http://www.dialogic.com/support/helpweb/mg/tn117.htm.

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

•The voice messaging ports in the phone system connected by T1 digital lines (DS1 or "dry T1" digital lines only) to the ports on the TIMG units.

---

Caution T1 (or "wet T1") connections to the PSTN must be through an MTU, CSU, or other device that provides line isolation. Otherwise, the TIMG units may be damaged.

---

•The TIMG units connected to the same LAN or WAN that Cisco Unity is connected to.

•If the TIMG units connect to a WAN, the requirements for the WAN network connections are:

–For G.729a codec formatting, a minimum of 32.76 Kbps guaranteed bandwidth for each voice messaging port.

–For G.711 codec formatting, a minimum of 91.56 Kbps guaranteed bandwidth for each voice messaging port.

–No network devices that implement network address translation (NAT).

–A maximum 200 ms network latency.

•The phone system ready for the integration, as described in the documentation for the phone system.

Cisco Unity Server

•Cisco Unity 4.2 installed and ready for the integration, as described in the applicable Cisco Unity installation guide at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_installation_guides_list.html.

•For Cisco Unity 4.2(1) only, the latest ES installed.

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

Integration Description

The Nortel SL-100 integration sends call information and MWI requests through the data link, which is an RS-232 serial cable that connects the phone system and the master TIMG unit. Voice connections are sent through the T1 digital lines between the phone system and the TIMG units. The TIMG units communicate with the Cisco Unity server through the LAN or WAN by using Session Initiation Protocol (SIP). 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 with forwarded calls:

•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 Nortel SL-100 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)

•Message waiting indication (MWI)

Supervised Transfer for Calls

When supervised transfer is enabled and a caller hangs up while being transferred to another phone, the called phone will ring briefly even though there is no call. If the ringing phone is answered, there will be no call, only dead air will be heard.

Integrations with Multiple Phone Systems

Cisco Unity 4.2 can be integrated with two or more phone systems at one time. For information on the maximum supported combinations and instructions for integrating Cisco Unity with multiple phone systems, refer to the Multiple Phone System Integration Guide for Cisco Unity 4.2 at http://cisco.com/en/US/products/sw/voicesw/ps2237/products_installation_and_configuration_guides_list.html.

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 integrations)	Do not check this check box. Otherwise, the integration may not function correctly.
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 Nortel SL-100 Phone System

Instruct the phone system technician to set up the phone system in the manner directed in the following procedure.

To Program the Nortel SL-100 Phone System for a Serial TIMG Integration with Cisco Unity

---

Step 1 Program the phone lines connecting to the voice messaging ports on the TIMG units as a multiline hunt group.

Make sure that the phone system sends calls only to Cisco Unity voice messaging ports that are set to Answer Calls. Calls sent to a voice port not set to Answer Calls cannot be answered by Cisco Unity and may cause other problems.

Step 2 Enable hookflash transfer capability on each phone line that connects to the voice messaging ports on the TIMG units.

Step 3 Enable caller ID (through the serial data link to the master TIMG unit) on each subscriber extension.

---

Caution The phone system just provide caller ID through the serial data link to the master TIMG unit. Otherwise, some integration features will not function correctly.

---

Step 4 For each subscriber extension, set the call forwarding options to the following:

•Unrestricted source

•Forward when the extension is not answered

•Forward when the extension is busy

---

The following phone system programming is provided as an example. The specific programming for your phone system may vary depending on its configuration.

---

Note The following programming was accomplished through the maintenance administration position (MAP) terminal.

---

Example of Programming for the Nortel SL-100 Phone System

1. On the MAP terminal, enter table mpc and press Enter.

2. Enter add and press Enter.

3. On Table MPC, enter the following settings.

Table 2 Settings for Table MPC 

Field	Setting
MPCNO	Enter the MPC number used for SMDI.
MPCIOC	Enter the number associated with the MPC (SMDI) card.
IOCCCT	Enter the slot position on the IOC shelf multiplied by 4, from 0 to 32.
EQ	Enter the NT product engineering code for the MPC card in the format 1X89zz or FX30zz, where zz are the two letters at the end of the product code.
DLDFILE	In the format MPCAxxyy, enter the name of the 8-character download file for SMDI and MPCA.

4. Enter table mpclink and press Enter.

5. Enter add and press Enter.

6. On Table MPCLINK, enter the following settings.

Table 3 Settings for Table MPCLINK 

Field	Subfield	Setting
LINKKEY	MPCNO	Enter the MPC number used for SMDI (the same number entered in Table MPC).
	LINKNO	Enter the MPC link number for SMDI application with ASYNC protocol.
LINKALM		Enter Y to activate the MPCLINK alarm for system busy (SYSB) MPC links. Enter N if you do not want to activate the MPCLINK alarm for system busy (SYSB) MPC links. Note If you enter N, the system does not generate MPC908 (MPC link state transition) logs.
PROTOCOL		Enter ASYNC.
LINKNABL		Enter 765.
PARM		Enter APLDEFN.
ADEFN		Enter SMDI.
PARM		Enter BAUDRATE.
RATE		Enter B9600.
PARM		Enter PARITY.
PRTY		Enter EVEN.
PARM		The following are among the optional parameters: L1IDLY, L2IDLY, LNKDOWN. If you enter a parameter, you are then prompted to enter a value for it. L1IDLY and L2IDLY timers can be used in offices with heavy SMDI/VMS traffic to shorten the amount of time the MPC can delay sending an MWI to the switch. (The default is 3 seconds.) The LNKDOWN timer adjusts the length of time the switch takes to recognize LINK failure and sets the LINK to SYSB. (The default is 2 seconds.)
CHARBITS		Enter BIT7.

7. Enter table sllnkdev and press Enter.

8. Enter add and press Enter.

9. On Table SLLNKDEV, enter the following settings.

Table 4 Settings for Table SLLNKDEV 

Field	Setting
DEVNAME	Enter a unique device name.
DEVICE	Enter 1X89.
MPCNO	Enter the value MPC number that was specified in Table MPC.
LINKNO	Enter the value for the MPC link number that was specified in Table MPCLINK.
XLATION	Enter NONE.
PROTOCOL	Enter NONE.
DIRECTION	Enter INOUTLK.
XFER	Enter SMDIDATA.
OPTION	Enter NUMOFDIGS.
NUMDIGS	The number of digits sent by the phone system to the voice messaging system through the SMDI link. Note The entry value chosen should match the dialing plan configured on the phone system.
OPTION	Enter CGNADDRDN.
OPTION	Enter $.

10. Enter table ofrt and press Enter.

You use Table OFRT to set up a treatment for unanswered calls. The following example shows settings for routing unanswered calls back to the voice messaging system.

11. Enter add and press Enter.

12. On Table OFRT, enter the following settings.

Table 5 Settings for Table OFRT 

Field	Setting
RTE	If the record is the first in the route list, enter the route reference number assigned to the route list. Otherwise, leave this field blank.
RTESEL	Enter the route selector.
SNPA	Enter the serving NPA (area code) of the DN.
TYPCALL	Enter the type of call: •DD •NP •OA
ORIGSCRE	Enter LCL (for local) or NLCL (for non-local).
REPLDIGS	Enter up to 11 replace digits.
CANCNORC	Enter Y or N to indicate whether to cancel normal change.
BILLCODE	Enter the billing code. If there is no billing number, enter N.

13. Enter table digcol and press Enter.

You use Table DIGCOL to set up the action that the line module must take with the first digit that is dialed.

14. Enter add and press Enter.

15. On Table DIGCOL, enter the following settings.

Table 6 Settings for Table DIGCOL 

Field	Subfield	Setting
DGKEY	DATNAME	Enter the character assigned to the block of data in Table DIGCOL.
	DIGIT	Enter a numeric value from 0-9, STAR (*), or OCT (#) to specify the digit that is applicable to the record.
DGDATA	DGCOLSEL	Enter COL for the collection of more digits.
COLDATA	TMODE	Enter S for short timing mode.
	NUMDIGS	Number of digits. If the TMODE value is S, specify the number of digits for which short timing is required after the receipt of each digit. The number of digits specified, which does not include the initial digit, must be no greater than three for short timing.

16. Enter table ucdgroup and press Enter.

You use Table UCDGRP to set up the UCD group.

---

Note The UCD group must have a unique primary DN.

---

17. Enter add and press Enter.

18. On Table UCDGRP, enter the following settings.

Table 7 Settings for Table UCDGRP 

Field	Setting
UCDNAME	This is the name of the UCD group. It can be up to 16 characters in length. The first eight characters must be unique.
ACD	Enter N.
CUSTGRP	Name of the customer group to which the UCD group belongs.
UCDRNGTH	Ringing threshold, in one-second intervals, after which an unanswered call to a UCD agent is forwarded to the route specified in the THROUT field. The range is 0-63.
TABNAME	Enter OFRT.
INDEX	Enter the number assigned to the route list in Table OFRT (1-1023).
TABNAME	Enter OFRT for the table to which translations are routed.
INDEX	Enter the number assigned to the route list in Table OFRT (1-1023).
PRIOPRO	Enter Maximum time, in seconds, a call can wait in a UCD group (0-255).
MAXPOS	Enter the maximum number of UCD agent positions that can be active at one time. This number should be the number of ports on the all TIMG units that are connected to the phone system.
DBG	Delayed billing. Enter Y if billing starts when the call is answered by a UCD agent. Enter N if billing starts when the caller receives a recorded announcement.
DEFPRIO	Enter 0.
RLSCNT	Enter 0.
MAXWAIT	Enter the maximum time, in seconds, that a call waits in the incoming call queue before being answered (0-1800).
MAXCQSIZ	Enter the maximum number of calls that can be in the incoming queue waiting for an idle channel (0-511).
OPTION	Enter UCD_SMDI.
SMDI_LINK	Enter the terminal designation defined in Table SLLNKDEV.
SMDI_ DESK_NO	Enter the message desk number (1-63). If you have more than one UCD group, one of them must be set to 63. We recommend that the first UCD group on a data link be set to 63. The second is set to 62, and so on. Note If CRR (Call Request Retrieval) is used, all requests are made to the UCD group with SMDI_DSK_NO = 63.

19. Enter table dnroute and press Enter.

You use Table DNROUTE to set up the UCD group.

---

Note The UCD group must have a unique primary DN.

---

20. Enter add and press Enter.

21. On Table DNROUTE, enter the following settings.

Table 8 Settings for Table DNROUTE 

Field	Subfield	Setting
DNNM	AREACODE	Enter the DN for the UCD group specified as the UCDGRP. Note The UCD DN must be a dialable number from an agent on the phone system so that dialing plans and translation tables do not conflict.
	OFCCODE
	STNCODE
DN_SEL		Enter FEAT.
FEATURE		Enter UCD.
UCDGRP		Enter the value for the UCDNAME field that is defined in Table UCDGROUP.
DNTYPE		Enter PRIM.
TOLLPRIO		Enter 0.

22. Enter table lninv and press Enter.

You use Table LNINV to assign card slots on the line or remote line module.

23. Enter add and press Enter.

24. On Table LNINV, enter the following settings.

Table 9 Settings for Table LNINV 

Field	Setting
LEN	Enter the line equipment number of the card slot.
CARDCODE	Enter 5d11ae.
PADGRP	Enter the name of the appropriate pad group that appears in the PADDATA table.
STATUS	Enter WORKING.
GND	Enter Y.
BNV	Enter NL.
MNO	Enter Y.
CARDTYPE	Enter NIL.

25. Enter servord and press Enter.

You will add agents to the UCD group by entering the following inputs at the prompts.

Table 10 Inputs for Adding Agents to the UCD Group 

Prompt	Input	Description
SO:	NEW
SONUMBER:	Press Enter.	When to invoke this service. Pressing Enter starts the service at the current date and time.
DN:		The Directory Number of the line. Use ten-digit DNs.
LCC_ACC:	IBN	The line class code of service.
GROUP:		The name of the IBN customer group to which the line belongs. For example, covm.
SUBGRP:		The subgroup number. For example, 0.
NCOS:		The network class of service. For example, 1.
SNPA:		The serving NPA (area code) of the DN.
LEN_OR_LT D:		The line equipment number of the line. For example, 4 0 1 0 (separated by spaces).
OPTION:	COD	The cut-off on disconnect.
OPTION:	UCD	Uniform call distribution.
OPTION:	DGT	Digitone.
OPTION:	3WC	Three-way calling.
OPTION:	CXR	Call Transfer.
CXFERTYP:	CTALL	Call Transfer Type. CTALL = transfer all calls.
CXRRCL:	N	Call Transfer Recall.
METHOD:	STD	Method of Call Transfer: Std = Std Call Transfer method.
OPTION:	SMDI	Simplified message desk interface.
LINENO:		The UCD terminal number. This is the line number associated with the SMDI channel. This parameter must be unique for each agent in the associated UCDGRP.
UCDGRP:		The UCDNAME from the UCDGRP table. This is the UCD group to which you are adding the agent.
AUTO_LOG:	Y	Autologon capability required.
OPTION:	$	The data you have entered appears.
	Y	Enter Y.

26. Enter servord and press Enter.

You will add a pilot number (UCD group DN) for the ports on the TIMG units by entering the following inputs at the prompts.

Table 11 Inputs for Adding Agents to the UCD Group 

Prompt	Input	Description
SO:	NEW
SONUMBER:	Press Enter.	When to invoke this service. Pressing Enter starts the service at the current date and time.
DN:		The directory number of the line. This is the DN that you enter in the SDN table.
LCC:	IBN	The line class code of service.
GROUP:		The name of the IBN customer group to which the line belongs.
SUBGRP:		The subgroup number.
NCOS:		The network class of service.
SNPA:		Serving NPA (area code) of the DN.
LEN:		Line equipment number of the line. For example, 4 0 1 0.
OPTION:	cfb	Call Forward Busy. Note This input is optional.
CFBCNTL:	N	Normal assignment for CFB. Note This input is optional.
CFBDN:		The primary UCD DN. Note This input is optional.
OPTION:	CFF	Call Forward Fixed.
CFFDN:		The Primary UCD DN.
OPTION:	CFU	Call Forward Universal.
OVRDACR:	N	Override Automatic Callback.
OPTION:	$	The data you entered appears.
	Y	Enter Y to confirm the data.

27. Connect a phone to the line.

28. Pick up the handset.

29. Dial the call forward activation code followed by the pilot number (UCD DN). For example, dial *80 5551234.

---

Note If you do not know this code, look it up in Table IBNXLA. The code is in the CFWP field.

---

30. Confirm that you hear the confirmation tone, which indicates that the line has been forwarded.

---

Note If the phone system is restarted, you must repeat Step 27. through Step 30. for each line DN that CFUs to the UCD group.

---

31. Enter table ibnxla and press Enter.

You use Table IBNXLA to set up and message waiting indicators (MWIs).

32. Enter add and press Enter.

33. On Table IBNXLA, enter the following settings.

Table 12 Settings for Table IBNXLA 

Field	Subfield	Setting
KEY	XLANAME	Enter the name of the translator, 1-8 characters, for the MWI feature.
	DGLIDX	Enter the access code for the MWI feature.
RESULT	TRSEL	Enter FEAT.
	ACR	Enter N.
	SMDR	Enter N.
	FEATURE	Enter the following features: CRA CRR CRDS CRDA UCDD UCDA CFWP CFWC

Setting Up the TIMG Units

Do the following procedures to set up the analog TIMG units (media gateways) that are connected to the phone system.

These procedures require that the following tasks have already been completed:

•The phone system is connected to the TIMG units by using T1 digital lines and the applicable RS-232 serial cable.

•The TIMG units are ready to be connected to the LAN or WAN.

•The TIMG units are connected to a power source.

Fields that are not mentioned in the following procedures must keep their default values. For the default values of all fields, see the manufacturer documentation for the TIMG units.

To Download the TIMG Firmware Update Files for TIMG Units

---

Step 1 On a Windows workstation that will have access to the TIMG units, open a web browser and go to the Cisco Unity PIMG Software Download page at http://www.cisco.com/cgi-bin/tablebuild.pl/unity-PIMG.

---

Note To access the software download page, you must be logged on to Cisco.com as a registered user.

---

Step 2 On the Cisco Unity PIMG Software Download page, click the most recent version of the firmware for your TIMG units.

Step 3 On the Details page, click Next.

Step 4 On the Document page, click Accept.

Step 5 In the Enter Network Password dialog box, enter your user name and password, then click OK.

Step 6 In the File Download dialog box, click Save.

Step 7 In the Save As dialog box, browse to the Windows workstation that will have access the TIMG units, browse to a directory where you want to save the file, and click Save.

Step 8 In the Download Complete dialog box, click Open. The window for extracting the TIMG firmware update files appears.

Step 9 Click Extract.

Step 10 In the Extract dialog box, browse to the directory where you want the extracted files, and click Extract.

Step 11 Close the window for the extracting application.

---

To Set Up the TIMG Units

---

Step 1 On the Windows workstation, add a temporary route to enable access to the TIMG units.

a. On the Windows Start menu, click Run.

b. Enter cmd, and press Enter. The Command Prompt window appears.

c. At the command prompt, enter route add 10.12.13.74 <IP Address of Workstation>, and press Enter.

For example, if the IP address of the workstation is 198.1.3.25, enter "route add 10.12.13.74<space>198.1.3.25" in the Command Prompt window.

d. Close the Command Prompt window.

Step 2 Connect a TIMG unit to the network.

Step 3 In the web browser, go to http://10.12.13.74.

Step 4 On the System Login page, enter the following case-sensitive settings.

Table 13 System Login Page Settings 

Field	Setting
Username	Enter admin.
Password	Enter IpodAdmin.

Step 5 Click Log On.

Step 6 On the Configure menu, click Upgrade.

Step 7 On the Upgrade page, click Browse.

Step 8 In the Choose File dialog box, browse to the directory on the Windows workstation that has the extracted TIMG firmware update files.

Step 9 Click Ls_<xx>.app (where <xx> is multiple digits), and click Open.

Step 10 On the Upgrade page, click Install.

Step 11 After the file is installed, a message prompting you to restart the TIMG unit appears. Click Cancel.

---

Caution Do not restart the TIMG unit until you are instructed to do so later in this procedure, even if the file installation fails. Restarting the TIMG unit at this step may prevent the TIMG unit from functioning correctly.

---

Step 12 Repeat Step 6 through Step 11 for the file Run_<xx>.dsp.

Step 13 On the Configure menu, click Upgrade.

Step 14 On the Upgrade page, under Import, click Browse.

Step 15 In the Choose File dialog box, browse to the file Ls_<xx>.fsh.

Step 16 Click Ls_<xx>.fsh, and click Open.

Step 17 On the Upgrade page, click Install.

Step 18 After the file is installed, a message prompting you to restart the TIMG unit appears. Click OK.

Step 19 In the web browser, go to http://10.12.13.74.

Step 20 On the System Login page, enter the following case-sensitive settings.

Table 14 System Login Page Settings 

Field	Setting
Username	Enter admin.
Password	Enter IpodAdmin.

Step 21 Click Log On.

Step 22 On the Configure menu, click Password.

Step 23 On the Password page, enter the following settings.

Table 15 Password Page Settings 

Field	Setting
Old Password	Enter IpodAdmin. (This setting is case sensitive.)
New Password	Enter your new password. (This setting is case sensitive.)
Confirm Password	Enter your new password. (This setting is case sensitive.)

Step 24 Click Change.

Step 25 On the Configure menu, click IP.

Step 26 On the IP page, enter the following settings for LAN1.

Table 16 IP Page Settings for LAN1 

Field	Setting
Client IP Address	Enter the new IP address that you want to use for the TIMG unit. (This is the IP address that you will enter in UTIM when you create the integration.)
Client Subnet Mask	Enter the new subnet mask, if the subnet mask is different from the default IP address.
Default Network Gateway Address	Enter the IP address of the default network gateway router that the TIMG units will use.
BOOTP Enabled	If you are using DHCP, click Yes. If you are not using DHCP, click No.

Step 27 Click Apply Changes.

Step 28 On the Configure menu, click System.

Step 29 On the System page, enter the following settings.

Table 17 System Page Settings for the System and Telephony Groups 

Field	Setting
Operating Mode	Click SIP.
PCM Coding	Click uLaw.

Step 30 Determine which serial port on the TIMG unit you will use to connect the data link serial cable from the phone system, then enter the following settings in the applicable group.

Table 18 System Page Settings for Serial Port Groups 

Field	Setting
Serial Port Baud Rate	Click the setting that is configured on the phone system. The default setting is 9600.
Serial Port Parity	Click the setting that is configured on the phone system. The default setting is None.
Serial Port Data Bits	Click the setting that is configured on the phone system. The default setting is 8.
Serial Port Stop Bits	Click the setting that is configured on the phone system. The default setting is 1.

Step 31 Click Apply Changes.

Step 32 On the Configure menu, click Gateway.

Step 33 On the Gateway page, click the Gateway Routing tab.

Step 34 On the Gateway Routing tab, enter the following settings.

Table 19 Gateway Routing Tab Settings 

Field	Setting
Fault Tolerance Enabled	Click Yes.
Load Balancing Enabled	Enter No.
VoIP Endpoint ID: 1	(Cisco Unity without failover) Enter the IP address for the Cisco Unity server. (Cisco Unity with failover configured) Enter the IP address for the primary Cisco Unity server.
VoIP Endpoint ID: 2	(Cisco Unity without failover) Leave this field blank. (Cisco Unity with failover configured) Enter the IP address for the secondary Cisco Unity server.

Step 35 Click Apply Changes.

Step 36 On the Gateway page, click the Gateway Advanced tab.

Step 37 On the Gateway Advanced tab, enter the following settings.

Table 20 Gateway Advanced Tab Settings 

Field	Settings
Advanced Call Routing
Call Connect Mode	Click OnAnswer.
Send DNIS to VoIP Endpoint	Click No.
Destination for Unroutable IP Calls	Leave this field blank.
Destination for Unroutable PBX Calls	Leave this field blank.
Monitor Call Connections	Click No.
Telephony
Minimum Call Party Delay	Enter 0.
Maximum Call Party Delay	Enter 2000.
Dial Digit on Time	Enter 100.
Dial Inter-Digit Time	Enter 100.
Dial Pause Time	Enter 2000.
Turn MWI On FAC	Leave this field blank.
Turn MWI Off FAC	Leave this field blank.
Dial Send Key	Click None.
Outbound Call Connect Timeout	Enter 10000.
Wait for Ringback/Connect on Blind Transfer	Click Yes.
Hunt Group Extension	Enter the pilot number for the Cisco Unity voice messaging ports.
Audio
Audio Compression	Click the preferred codec for audio compression: •G.711—The TIMG unit will use only the G.711 codec. •G.729—The TIMG unit will prefer the G.729a codec but can also use the G.711 codec.
RTP Digit Relay Mode	Click RFC2833.
Signaling Digit Relay Mode	Click On.
Voice Activity Detection	Click On.
Frame Size	Click the applicable setting: •G.711—20 •G.729a—10 Caution Failure to use the correct setting will result in recorded messages containing nothing but silence.
Frames Per Packet	Click the applicable setting: •G.711—1 •G.729a—2 Caution Failure to use the correct setting will result in recorded messages containing nothing but silence.
Quality of Service
Call Control QOS Byte	(TIMG units connect only to a LAN) Enter 0 (equivalent to DSCP AF31). (TIMG units connect to a WAN) Enter 104 (equivalent to DSCP AF31).
RTP QOS Byte	(TIMG units connect only to a LAN) Enter 184 (equivalent to DSCP EF). (TIMG units connect to a WAN) Enter 184 (equivalent to DSCP EF).
Traps and Alarms
SNMP Traps Enabled	Click No.
E-mail Alarms Enabled	Click No.
HTTP Server Enabled	Click Yes.
HTTPs Server Enabled	Click No.

Step 38 Click Apply Changes.