Nortel Call Recording Card

Nortel Call Recording CardPlanning, Installation, and Administration Guide

Product Release 6.5 and 7.0 Standard 01.03 November 2009

NN44480-307


Publication number: NN44480-307

Product release: 6.5 and 7.0

Document release: Standard 01.03Date: November 2009

Copyright © 2008-2009 Nortel Networks. All Rights Reserved.

While the information in this document is believed to be accurate and reliable, except as otherwise expressly agreed to in writing NORTEL PROVIDES THIS DOCUMENT "AS IS" WITHOUT WARRANTY OR CONDITION OF ANY KIND, EITHER EXPRESS OR IMPLIED. The information and/or products described in this document are subject to change without notice.

Nortel, Nortel Networks, the Nortel logo, and the Globemark are trademarks of Nortel Networks.

All other trademarks are the property of their respective owners.

Planning, Installation, and Administration Guide iv

Revision historyNovember 2009 Standard 01.03. The Nortel Call Recording Card

Planning, Installation, and Administration Guide is up-issued for Product Release 6.5 and 7.0.

October 2009 Standard 01.02. The Nortel Call Recording Card Planning, Installation, and Administration Guide is up-issued for Product Release 6.5 and 7.0.

April 2008 Standard 01.01. The Nortel Call Recording Card Planning, Installation, and Administration Guide is up-issued for Product Release 6.5.

Planning, Installation, and Administration Guide v

Contents

Getting Started 7About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8How to get help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Installing the Nortel Call Recording Card 11Installation overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Installing the Nortel Call Recording Card . . . . . . . . . . . . . . . . . . . . . . . . . 15

Installing the Nortel Call Recording Card 19Switch Configuration for Nortel Call Recording Card. . . . . . . . . . . . . . . . 20Cabling the Nortel Call Recording Card . . . . . . . . . . . . . . . . . . . . . . . . . . 30Network settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Assigning the Internet Protocol (IP) address . . . . . . . . . . . . . . . . . . . . . . . 38Changing the user name and password for command line access . . . . . . . 42 Recording file format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Engineering Guidelines 45Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Usage guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Test and Debug Capabilities 49Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Self test features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Factory test features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52VxWorks shell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Card state debug utilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Application level debugging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Upgrade Procedures 61Application loadware upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Contents Standard 01.03

vi Nortel Call Recording Card

XA firmware upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67BootROM loadware upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Precautions, Samples, and Error Codes 73Precautions for handling circuit cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Sample boot sequence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Error code definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Glossary 89

Planning, Installation, and Administration Guide 7

C h a p t e r 1

Getting Started

In this chapter About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

How to get help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Getting Started Standard 01.03

8 Nortel Call Recording Card

About this guide

The Nortel Call Recording Card Planning, Installation, and Administration Guide provides step-by-step instructions you must perform to complete the installation and administration of Nortel Call Recording Card.

Intended audience

This guide is intended for:

Nortel installers and distributors who are responsible for installing the Nortel Call Recording Card.

Administrators who are responsible for monitoring and maintaining the Nortel Call Recording Card.

November 2009 Getting Started


How to get help

This section explains how to get help for Nortel products and services.

Finding the latest updates on the Nortel Web site

The content of this documentation was current at the time the product was released. To check for the latest updates to the Nortel Contact Recording and Quality Monitoring documentation, go to http://www.nortel.com/documentation and navigate to the Contact Recording suite.

Getting help from the Nortel Web site

The best way to get technical support for Nortel products is the Nortel Support web site:

http://www.nortel.com/support

This site provides quick access to software, documentation, bulletins, and tools to address issues with Nortel products. From this site, you can:

download software and related tools

download technical documents, release notes, and product bulletins

sign up for automatic notification of new software and documentation

search the Support Web site and Nortel Knowledge Base for answers to technical issues

open and manage technical support cases

Getting Started Standard 01.03


Getting help over the phone from a Nortel Solutions Center

If you do not find the information your require on the Nortel Technical Support Web site, and you have a Nortel support contract, you can also get help over the phone from a Nortel Solutions Center.

In North America, call 1-800-4NORTEL (1-800-466-7835).

Outside North America, go to the Web site below to obtain the phone number for your region:

http://www.nortel.com/callus

Getting help from a specialist by using an Express Routing Code

You can use an Express Routing Code (ERC) to more quickly route your call to the appropriate support specialist. To locate the ERC for your product or service, go to:

http://www.nortel.com/erc

Getting help through a Nortel distributor or reseller

If you purchased a service contract for your Nortel product from a distributor or authorized reseller, you can contact the technical support staff for that distributor or reseller.


C h a p t e r 2

Installing the Nortel Call Recording Card

In this chapter Installation overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Installing the Nortel Call Recording Card . . . . . . . . . . . . . . . . . . . . . . . . 15

Installing the Nortel Call Recording Card Standard 01.03


Installation overview

The following table documents the Nortel Call Recording Card installation information.

Table 1: Nortel Call Recording Card applicability and compatibility

Nortel Call Recording Card

Application and Compatibility

Switch options Small systems:

Option 11 Cabinet / Chassis

Succession 1000

Succession 1000M Cabinet / Chassis

Large systems:

Option 51C/61C/81/81C

Succession 1000M Half Group/Single Group/Multi Group

Card slot location Option 51C,61C, 81 or 81C: any IPE slot except CONT

Any IPE slot in an Option 11 Cabinet / Chassis.

Succession 1000M Half Group / Single Group / Multi Group: any IPE slot except CONT.

Any IPE slot in a Succession 1000 or Succession 1000M Cabinet / Chassis.

Note: On older Option 51C to 81C systems (before IPE shelf vintage NT8D37EC) for slots other than 0,4,8,12, you must install the NT8D81AA backplane to I/O panel cable to connect all required signals to I/O panel.

MDF cabling None (the sets are virtual).

November 2009 Installing the Nortel Call Recording Card


LAN cabling Complete cabling requires:

One NTAG81 PC maintenance cable

50 pin I/O connector -A0852632

NTVQ83 ITG EMC shielding kit

One category 5, 100-base-T Ethernet standard

Software release Meridian 1 Release 25.15 software or later. Succession release 2.0 or later.

Dip switch setting None.

Time and date stamp Automatically sent out by M1 CPU.

Upgrade capability Loadware upgrades performed from maintenance CLI. Upgrade across network using FTP.

Recording storage If using Call Recording, the FTP Server must have adequate file storage space. For example, a one minute call recording consumes up to 480 KB of disk space.

Conference capacity Each Nortel Call Recording Card session uses three conference ports on the switch.

If OBTN is set to either AGENT or ALL, each Nortel Call Recording Card session uses four conference ports on the switch.

If using Agent Greeting and OBTN is set to either AGENT or ALL, each Nortel Call Recording Card port uses five conference ports on the switch.



You must ensure there are enough conference ports on the switch to handle the number of simultaneous observes permitted by the Nortel Call Recording Card keycode. You must also ensure that each agent is assigned adequate conference capacity to permit use by Nortel Call Recording Card, Agent Greeting, OBTN and personal conference activities.

PEP Information To interoperate with Agent Greeting the following PEP must be applied: MPLR17930




Use the following preinstallation checklist to ensure you meet the Nortel Call Recording Card installation requirements.

Preinstallation checklist

To install the Nortel Call Recording Card, you must meet the installation requirements listed in Table 2: “Preinstallation checklist for Nortel Call Recording Card,” on page 15.

Table 2: Preinstallation checklist for Nortel Call Recording Card

Requirements for Nortel Call Recording Card installation Check

Nortel Call Recording Card installation pack, see Table 7: “Nortel Call Recording Card product structure,” on page 30.

r

RS232 maintenance cable for access to the command prompt of the card.

r

Access to switch software with administrator privileges to configure the card at switch level.

r

The switch must have an available slot in which to install the card.

r

IP configuration for the card: card IP address, gateway IP address and subnet mask. See “Assigning the Internet Protocol (IP) address,” on page 38.

r

FTP server configuration

FTP server with accounts set up for Nortel Call Recording Card. These accounts must have write and append access, see “Recording file format,” on page 43. r



Install procedure introduction

Complete the following steps to install the Nortel Call Recording Card. Print these steps and use the provided check boxes to ensure that all installation tasks are completed.

Before installation, perform the following tasks

Read the section on usage guidelines, see “Usage guidelines,” on page 47, before using the card.

r

Ensure the system has adequate conference capacity to support the number of Nortel Call Recording Card sessions installed. See Table 1: “Nortel Call Recording Card applicability and compatibility,” on page 12. If the system does not have adequate conference capacity, install extra XCT cards (large system) or dual fibre and conference cards (small systems) as required.

r



Step 1

Step 2

Step 3

Step 4

Step 5

Determine the cabinet, shelf, and slot location where you want to install the Nortel Call Recording Card. See “Installation overview,” on page 12 for card slot location.

Configure the Nortel Call Recording Card virtual sets on the Meridian 1/Sucession 1000 system. See “Switch Configuration for Nortel Call Recording Card,” on page 20.

Connect cables. See “Cabling the Nortel Call Recording Card ,” on page 30.

Unpack and inspect the circuit card.

ATTENTION!

Handle the circuit card using the guidelines specified in “Precautions for handling circuit cards,” on page 74.

Ensure a security dongle is installed in the socket on the card. If not currently installed, install a dongle in the socket. See Figure 4: “Media card layout,” on page 31 for the dongle socket location.



Step 6

Step 7

Step 8

Step 9

Fully insert the card in the assigned slot and lock the latches. During boot, the HEX LED displays a visual progress indication of self tests and information about the first failure detected. See “HEX display codes,” on page 52 for more information.

The red LED on the faceplate of the Nortel Call Recording Card remains illuminated until the unit is configured and enabled. If the red LED is illuminated, an error occurred in one of the previous steps.

Configure an Internet Protocol (IP) address for the card. See “Assigning the Internet Protocol (IP) address,” on page 38.

Nortel Call Recording Card installation is complete.


C h a p t e r 3


In this chapter Switch Configuration for Nortel Call Recording Card . . . . . . . . . . . . . . . 20

Cabling the Nortel Call Recording Card . . . . . . . . . . . . . . . . . . . . . . . . . 30

Network settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Assigning the Internet Protocol (IP) address . . . . . . . . . . . . . . . . . . . . . 38

Changing the user name and password for command line access. . . . . 42

Recording file format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43



Switch Configuration for Nortel Call Recording Card

The Nortel Call Recording Card has 32 ports. Of the 32 ports, 16 are configured as Live Monitor ports and 16 are configured as Observe ports.

Each Nortel Call Recording Card session can consist of two ports: a Live Monitor port to allow observers hear the calls as they occur and an observe/record port to perform the recording. These ports must be established in pairs with the even number ports (units 0, 2, 4, 6 and so on) configured as live monitor ports and the odd numbers ports (units 1, 3, 5, 7 and so on) configured as observe/record ports.

An example configuration of two Nortel Call Recording Card sessions has:

Unit 0 as a Live Monitor port with unit 1 as the corresponding Observe/record port.

Unit 2 as a Live Monitor port with unit 3 as the corresponding Observe/record port.

Note: If installing less than 16 Nortel Call Recording Card sessions, configure the required number of Live Monitor and observe/record ports only.

Live Monitor port configuration

Use overlays 11 and 32 to configure Live Monitor ports on the Nortel Call Recording Card.

Invoke Live Monitoring by using the following mechanism:



Nortel Quality Monitoring Application sends a make-call message to the CRC card on Live Monitor channel and then sends channel bridge command to bridge the Live Monitor channel with an observe/record channel. Thus the recipient of the Live Monitor call can hear all calls involving the observed agent.

Overlay 11—Configure the Live Monitor ports (even ports on Nortel Call Recording Card, that is 0,2,4,6 and so on) as Meridian Modular M2616 sets with the following requirements.

Table 3: LD11 Nortel Call Recording Card Live Monitor port configuration

Prompt Response Description

REQ: NEW CHG Add or change.

TYPE: 2616 Ports must be configured as M2616.

TN l s c u Terminal number.

DES d..d Designator.

CUST 0-99

CLS Class of service entries are separated by a space.

UNR Unrestricted access.

FLXA Flexible voice/data ports allowed (required for ports 16–31 only).

VCE Voice port (required for ports 16–31 only).

WTA Warning tone allowed (required for ports 16–31 only).

KEY 0 SCR YYYY Key 0 defined as an SCR key. YYYY is the SCR key DN.

KEY 1—15 UNCONFIGURED.



Create a list of unassigned DNs by using overlay 20 (LD 20, REQ PRT, TYPE LUDN).

Figure 1: “Sample LD11 Live Monitor port switch configuration,” on page 22 shows a sample overlay 11 switch configuration for a Live Monitor port with an SCR of 1560.

Figure 1: Sample LD11 Live Monitor port switch configuration

REQ: prtTYPE: 2616TN 9 0DATE PAGE DESTN 9 0DATE PAGE DES

DES TUI TN 009 0 00 00 TYPE 2616CDEN 8DCUST 0 AOM 0 FDN TGAR 1 LDN NONCOS 0 SGRP 0 RNPG 0 SCI 0 SSU XLST SCPW SFLT NOCAC_CIS 3 CAC_MFC 0 CLS UNR FBD WTA LPR MTD FND ADD HFD MWD LMPN RMMD SMWD AAD IMD XHD IRD NID OLD VCE DRG1 POD DSX VMD CMSD SLKD CCSD SWD LND CNDD CFTD SFD MRD DDV CNID CDCA MSID DAPA BFED RCBD ICDD CDMD LLCN MCTD CLBD AUTU



GPUD DPUD DNDD CFXD ARHD CLTD ASCD CPFA CPTA HSPD ABDD DELD CFHD FICD NAID DNAA BUZZ AGRD MOAD UDI RCC HBTD AHD IPND DDGA NAMA MIND PRSD NRWD NRCD NROD DRDD EXR0 USMD USRD ULAD CCBD RTDD RBDD RBHD PGND FLXD FTTC DNDY DNO3 MCBN CPND_LANG ENGPLEV 02 AST IAPG 0 AACS NOITNA NO DGRP MLWU_LANG 0 DNDR 0 KEY 00 SCR 1560 0 MARP ANIE 0 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 DATE 7 OCT 2003

Observation port configuration

Use overlays 11, 23, and 32 to configure observation ports on the Nortel Call Recording Card. Use the following configuration sequence to configure the observation ports.



1. Configure ACD queue for use with Nortel Call Recording Card in LD23 as described in Table 4: “LD23 Nortel Call Recording Card ACD queue configuration,” on page 24. To permit observation, each observation port must be part of an ACD queue.

2. Configure the observation ports as M2616 in LD11 as described in Table 5: “LD 11 Nortel Call Recording Card observation port configuration,” on page 25.

3. Enable the card in LD32

4. Configure an ACD queue in overlay 23. If an ACD queue is not currently configured, you must configure an ACD queue for the Nortel Call Recording Card.

Table 4: LD23 Nortel Call Recording Card ACD queue configuration

The maximum agent positions parameter (MAXP) is the maximum number of position IDs you can configure for the ACD queue. Each configured Nortel Call Recording Card observation port increments the number of configured positions on this ACD queue. You can configure Nortel Call Recording Cards with a maximum of 16 observation ports.


REQ: NEW CHG Add or change

TYPE: ACD Automatic call distribution

CUST: 0-99 Customer number

ACDN: XXXX ACD queue DN

...

MAXP XXXX Maximum agent positions

OBTN NO, ALL, AGT Observe tone



You can also set an observe tone (OBTN). When observing an agent, a periodic tone (every 15 seconds) may be heard. If you want the agent and the caller to hear the tone, set the OBTN to ALL. If you want the agent to hear the tone only, set the OBTN to AGT for Agent only. To disable the tone, set OBTN to and NO.

Note: This tone is a legal requirement in some regions.

Using overlay 11, configure the observation ports (odd ports on Nortel Call Recording Card, that is 1,3,5,7 and so on) as Meridian Modular M2616 sets as specified in Table 5: “LD 11 Nortel Call Recording Card observation port configuration,” on page 25.

Table 5: LD 11 Nortel Call Recording Card observation port configuration


REQ: NEW CHG Add or change.

TYPE: 2616 Ports must be configured as M2616.

TN l s c u Terminal number.

DES d..d Designator.

CUST 0-99

...

CLS Class of service entries are separated by a space.

SPV ACD supervisor.

FLXA Flexible voice/data ports allowed (required for ports 16–31 only).

VCE Voice port (required for ports 16–31 only).

WTA Warning tone allowed (required for ports 16–31 only).



The observation/recording port uses the ACD Observe Agent (OBV) key to observe agents.

Figure 2: “Observe port switch configuration,” on page 26 shows a sample LD11 switch configuration for an observe/record port.

Figure 2: Observe port switch configuration

REQ: prtTYPE: 2616TN 9 1DATE PAGE DES

DES OBV TN 009 0 00 01 TYPE 2616CDEN 8DCUST 0 AOM 0 FDN TGAR 1 LDN NONCOS 0 SGRP 0 RNPG 0 SCI 0 SSU XLST SCPW

...

KEY 0 ACD XXXX 0 XXXX

Key 0 defined as an ACD key specifying position ID and queue ID.

KEY 1 MSB Make set busy key.

KEY 2 OBV Observe key.

KEY 3—15 UNCONFIGURED



SFLT NOCAC_CIS 3 CAC_MFC 0 CLS UNR FBD WTA LPR MTD FND HTD ADD HFD MWD LMPN RMMD SMWD AAD IMD DOS XHD IRD NID OLD VCE DRG1 POD DSX VMD CMSD SLKD CCSD SWD LND CNDD CFTD SFD MRD DDV CNID CDCA MSID DAPA BFED RCBD ICDD CDMD LLCN MCTD CLBD AUTU GPUD DPUD DNDD CFXD ARHD CNTD CLTD ASCD CPFA CPTA HSPD ABDD DELD CFHD FICD NAID DNAA BUZZ AGRD MOAD UDI RCC HBTD AHD IPND DDGA NAMA MIND PRSD NRWD NRCD NROD DRDD EXR0 USMD USRD ULAD CCBD RTDD RBDD RBHD PGND FLXD FTTC DNDY DNO3 MCBN CPND_LANG ENGHUNT PLEV 02 AST IAPG 0 AACS NOITNA NO DGRP PRI 01 MLWU_LANG 0 DNDR 0 KEY 00 ACD 1810 0 4500 SPV ANIE 0 01 MSB 02 OBV 03 04 05 06 07 08 09 10 11 12 13 14 15



DATE 7 OCT 2003

Enabling Nortel Call Recording Card units

Overlay 32 – When switch configuration is complete, enable the Nortel Call Recording Card units as shown in Table 6: “LD 32 Enable Nortel Call Recording Card unit,” on page 28.

Table 6: LD 32 Enable Nortel Call Recording Card unit

ATTENTION!

Never configure or enable more units on a Nortel Call Recording Card slot than the keycode permits.

Figure 3: “Sample LD32 status output,” on page 28 shows a sample LD 32 status for a card with 16 Nortel Call Recording Card sessions configured.

Figure 3: Sample LD32 status output

00 = UNIT 00 = IDLE (2616)01 = UNIT 01 = IDLE (2616 LOG OUT)02 = UNIT 02 = IDLE (2616)03 = UNIT 03 = IDLE (2616 LOG OUT)04 = UNIT 04 = IDLE (2616)05 = UNIT 05 = IDLE (2616 LOG OUT)06 = UNIT 06 = IDLE (2616)07 = UNIT 07 = IDLE (2616 LOG OUT)08 = UNIT 08 = IDLE (2616)09 = UNIT 09 = IDLE (2616 LOG OUT)10 = UNIT 10 = IDLE (2616)11 = UNIT 11 = IDLE (2616 LOG OUT)12 = UNIT 12 = IDLE (2616)13 = UNIT 13 = IDLE (2616 LOG OUT)14 = UNIT 14 = IDLE (2616)15 = UNIT 15 = IDLE (2616 LOG OUT)

Command Description

ENLC l s c u Enable the pre-configured unit



16 = UNIT 16 = IDLE (2616)17 = UNIT 17 = IDLE (2616 LOG OUT)18 = UNIT 18 = IDLE (2616)19 = UNIT 19 = IDLE (2616 LOG OUT)20 = UNIT 20 = IDLE (2616)21 = UNIT 21 = IDLE (2616 LOG OUT)22 = UNIT 22 = IDLE (2616)23 = UNIT 23 = IDLE (2616 LOG OUT)24 = UNIT 24 = IDLE (2616)25 = UNIT 25 = IDLE (2616 LOG OUT)26 = UNIT 26 = IDLE (2616)27 = UNIT 27 = IDLE (2616 LOG OUT)28 = UNIT 28 = IDLE (2616)29 = UNIT 29 = IDLE (2616 LOG OUT)30 = UNIT 30 = IDLE (2616)31 = UNIT 31 = IDLE (2616 LOG OUT)



Cabling the Nortel Call Recording Card

Use this section to connect the Nortel Call Recording Card cables.

Introduction

The Nortel Call Recording Card installation pack contains the following items.

Table 7: Nortel Call Recording Card product structure

The 32-port media card comes with the dongle and the compact flash with the Nortel Call Recording Card load preinstalled (the C:/exec file on the Compact Flash card). Figure 4: “Media card layout,” on page 31 shows the layout of the Media Card.

Part # NT Code Description

A0888965 NTVQ01BA 32 port media card

A0852632 A0852632 Shielded 50 pin key telephone to 9D sub and twin RJ45 adapter (L-Adapter)

A0870556 NTVQ83AA ITG EMC shielding kit

A0783483 NTCW84JA M1 backplane to 50-pin I/O panel cable (filter block)

N0056092 NT9S80MA Compact flash with Nortel Call Recording Card application load

Security device (dongle)



Figure 4: Media card layout

Interfaces

The Nortel Call Recording Card has one network interface (the C-LAN interface). This is used for:

Socket access to control the card from the Nortel QM system.

Access to FTP to transfer the call recordings from the card.

The Nortel Call Recording Card uses the backplane interface to the switch to download time-and-date messages from the switch.

Dongle

RED Enable LED

PC Card (PCMCIA) slot

Compact Flash C:/drive

Ethernet activity LEDs

HEX Display

Serial Maintenance Port

Reset button



C-LAN interface

The Nortel Call Recording Card supports a single connector solution for access to the C-LAN Ethernet port.

Cables and connectors for the C-LAN interface functions include:

• The A0783483 (NTCW84JA) Meridian 1 Large System I/O panel filter block

• The A0852632 L-shaped connector block, see Figure 5: “Nortel Call Recording Card adapter CLAN (L-adapter),” on page 33. You need standard shielded CAT-5 LAN cables (< 100 meters) to attach the LAN ports to the local network.

ATTENTION!

You must install an EMC shielding kit (ferrite- A0870556) on the C-LAN interface cables to meet regulatory requirements at the installation site. Place the ferrite on the C-LAN Ethernet cable during installation using cable ties to secure the ferrite in the correct position. This applies to both small and large systems.

Nortel Call Recording Card adapter C-LAN (L-adapter)

The adapter (see Figure 5: “Nortel Call Recording Card adapter CLAN (L-adapter),” on page 33) breaks out the signals from the I/O connector on small and large systems to the following:

Customer LAN port (CLAN)

One RS232 port

Notes:

Connect the C-LAN Ethernet cable to the port labelled T-LAN on the L-adapter.

The Nortel Call Recording Card does not use the port labelled E-LAN.



Figure 5: Nortel Call Recording Card adapter CLAN (L-adapter)

Filter block installation for large systems

On large systems, you must install the A0783483 I/O panel-mounting filter block before installing the Nortel Call Recording Card adapter CLAN (L-adapter), see Figure 6: “L-adapter and filter block connection setup on large systems,” on page 34. The filter block permits the CLAN to operate at 100 Mbps on large systems, such as an option 81.



Figure 6: L-adapter and filter block connection setup on large systems

RS232 maintenance port

The RS232 maintenance port provides access to the Nortel Call Recording Card command prompt for monitoring and maintenance purposes, such as upgrades and debugging. This port is available at the 9-pin connector on the Nortel Call Recording Card Adapter CLAN and also at the mini-DIN socket on the faceplate of the Nortel Call Recording Card. The serial port settings are 9600 baud, 8 data bits, 1 stop bit, no parity, and no flow control.

ATTENTION!

Access the maintenance port by one connection only (9-pin connector or mini-DIN socket) at a time.



Connecting the Nortel Call Recording Card to a modem

To provide remote access to the Command Line Interface (CLI) for support and remote maintenance, you can connect a modem to the serial port of the Nortel Call Recording Card. To set up a working interface, perform the following procedure:

1 Using a standard serial cable, establish communication with the Hayes-compatible modem from a PC with the following settings: 9600 baud, 8 data bits, 1 stop bit, no parity, and no flow control.

2 From the command line, type the following:

AT <return>

3 At the OK prompt, enter the required settings from Table 8: “Modem settings,” on page 35.

Table 8: Modem settings

4 Use the 9-pin connector on the card adapter (L-adapter) to connect the modem to the Nortel Call Recording Card.

Setting Action

ASSO=1<return> set to auto-answer on first ring

ATQ1 <return> disable result codes

ATE0<return> disable local echo

AT&W0<return> save settings



Network settings

This section documents the Nortel Call Recording Card network settings.

Network speed/duplex setting

The Nortel Call Recording Card C-LAN interface auto negotiates its speed and duplex settings. To verify these settings, execute the following command from the maintenance command line interface:

->linkGetOperation 0

Result:

0x2a4eedc (tShell): T-LAN in Autonegotiation Mode

0x2a4eedc (tShell): T-LAN operating in 100Mbps, Full-Duplex mode.

Note: The T-LAN shown in the output of the linkGetOperation command is the C-LAN of the card.

Security settings

Nortel Call Recording Card uses a number of TCP/UDP ports to operate correctly. These are documented in the following table.

Table 9: TCP/UDP ports used

L4 Protocol (TCP/UDP)

Port Number Description Comment

TCP 21 ftp You can select another port for FTP.

TCP 23 telnet

TCP 111 sunrpc-portmapper



TCP 6001 Socket connection Port that controls operation of the CRC card from the Nortel QM application over the TCP-IP socket.



Assigning the Internet Protocol (IP) address

Nortel Call Recording Card permits two basic methods of assigning IP addresses to individual cards. These are static assignment using the maintenance and debug serial port and dynamic assignment using the Dynamic Host Configuration Protocol (DHCP).

Nortel recommends assigning a static IP address to the card unless a reserved IP address entry can be made in the DHCP server, which always gives the reserved IP address to the Nortel Call Recording Card.

Static IP address assignment

When you assign an IP address, you must ensure that you have a unique IP address, the correct subnet mask and the correct gateway address. An incorrect IP address or subnet mask can cause the LAN to which the card is connected to stop responding. If an incorrect gateway address is assigned, the card is inaccessible beyond its local LAN.

Using static assignment, the operator assigns an IP address, subnet mask, and default gateway IP address using the serial port interface. After restarting, the Nortel Call Recording Card retrieves the IP information from NVRAM and applies it. To switch to this mode of IP assignment, you must invoke the function lnIsaIPMethodSet with the parameter 2 (that is, lnIsaIPMethodSet 2). The command sequence to assign a static IP address to the card is shown in “Command sequence to assign a static IP address” on page 39.

You must access the card using the maintenance port. To access the shell, you must enter the correct user name and password.

Note: The default user name is crcadmin and the default password is crcsecurity. See “Changing the user name and password for command line access” on page 42 for details on changing these defaults.



If, on first boot of the card, you cannot log into the shell using the default user name and password, check that the correct software version is on the card. This is displayed during boot, see “Sample boot sequence” on page 76.

Figure 7: Command sequence to assign a static IP address

VxWorks login: crcadmin

Password: crcsecurity

>

> lnIsa_writeSubnetMask “AAA.BBB.CCC.DDD”

value = 0 = 0x0

> lnIsa_progIP “DDD.CCC.BBB.AAA”

value = 0 = 0x0

lnIsa_writeGW “ZZZ.YYY.XXX.WWW”

value = 0 = 0x0

lnIsaIPMethodSet 2

value = 0 = 0x0

You must reset the Card now by either pressing the reset button on the faceplate or by typing sysReboot at the command line interface. When the card restarts, you can test the operation of the network interface by using the ping command.

ping “mm.nn.oo.pp”,3

mm.nn.oo.pp is another IP address in the network the Nortel Call Recording Card can access. The number 3 shows that three ping packets are sent to the other IP address.

The output is similar to the following example:

> ping "47.85.3.41", 3

PING 47.85.3.41: 56 data bytes



64 bytes from 47.85.3.41: icmp_seq=0. time=0. ms



----47.85.3.41 PING Statistics----

3 packets transmitted, 3 packets received, 0% packet loss

round-trip (ms) min/avg/max = 0/0/0

value = 0 = 0x0

DHCP IP address assignment

DHCP dynamically determines the network configuration of each Nortel Call Recording Card. DHCP reduces the work necessary to administer an IP network by using a server to allocate network addresses. DHCP also permits automatic reuse of addresses by specifying a lease time. Clients must renew the lease periodically.

The client (the Nortel Call Recording Card) first broadcasts a discover message containing its Ethernet address as a client identifier. A DHCP server replies with an offer message, containing configuration parameters. The client can receive offers from multiple DHCP servers. The client must select a server by broadcasting a request message containing the server identifier. The server acknowledges the reply and assigns the configuration to the client. The client can now use the assigned configuration.

The DHCP server assigns a reserved address to the card to guarantee that the card always receives the same IP address. Otherwise, the card must have an assigned DNS name to ensure it is always found using a Web browser. If the local DHCP server provides long lease periods, this may not be necessary.

lnIsaIPMethodSetThe lnIsaIPMethodSet function has three possible options:

Use DHCP for IP address assignment



Use static IP address information stored in NVRAM,

Hybrid (not recommended for Nortel Call Recording Card)

The parameter to lnIsa_writeSubnetMask is the subnet mask in dot notation format. It is critical that the subnet mask matches the local subnetting policy or you can not access some systems on the LAN from the Nortel Call Recording Card or vice versa.

The parameter to lnIsa_progIP is a string containing the dot notation representation of the IP address to be assigned to the card.

The parameter to lnIsa_writeGW is a string containing the dot notation representation of the IP address of the default router for the local LAN.

Note: The gateway address must be an IP address in the local subnet of the IP address previously assigned to the card using lnIsa_progIP. If a gateway address is not configured it is not possible to access the Nortel Call Recording Card from outside the local subnet.

To return to DHCP IP address assignment, execute the following command on the serial maintenance port:

lnIsaIPMethodSet 1



Changing the user name and password for command line access

Nortel strongly recommends that the logon password and user name for command line access are changed from their default values by using the command shellPasswordSet. (Defaults are crcadmin for user name, crcsecurity for password).

Both the user name and password must be between eight and ten characters long:

> shellPasswordSet

Enter current username: username1

Enter current password: password1

Enter new username: username2

Enter new password: password2

Enter new password again to confirm: password2:

value = 0

>

If a non-zero value is returned, the password and user name did not change.

User name and password applicability

The same user name and password are used for maintenance port command line access, telnet access, and FTP access.



Recording file format

Call recording files generate in G.711 format. The Nortel Quality Monitoring application packages the recordings as G.711 mu-law WAV files with an embedded timestamp in the header.




C h a p t e r 4

Engineering Guidelines

In this chapter Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Usage guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Engineering Guidelines Standard 01.03


Introduction

The following section documents measured performance and real-time engineering guidelines for operating the Nortel Call Recording Card.

November 2009 Engineering Guidelines


Usage guidelines

You must disable the Nortel Call Recording Card at the switch, using overlay 32, before performing any PCMCIA drive access.

To disable the card, use the DISC command as shown in Table 10: “Disabling the Nortel Call Recording Card using overlay 32,” on page 47.

Table 10: Disabling the Nortel Call Recording Card using overlay 32

When the PCMCIA drive access is complete, enable the card using the ENLC command shown in Table 11: “Enabling the Nortel Call Recording Card using overlay 32,” on page 47.

Table 11: Enabling the Nortel Call Recording Card using overlay 32

Never leave debug logging enabled on the card, as this severely affects real-time performance.

To interoperate with Agent Greeting, you must apply the MPLR17930 switch patch.

Never enable more units on a Nortel Call Recording Card slot than the keycode allows.

Due to switch software limitations, it is not possible to observe/record the consult part of the calls during conference or transfer.

Command Description

DISC l s c Disable the pre-configured card.

Command Description

ENLC l s c Enable the pre-configured card.

Engineering Guidelines Standard 01.03


Due to switch software limitations, it is not possible to perform a double-observe. This means you cannot perform an observation on a call already being observed by another observer. However, it is possible for the observer to conference a call, once an observation is in progress, thus allowing multiple remote observers of one call.

Due to switch software limitations, it is not possible to observe on IVR ACD queues. However, agents are not typically logged on IVR ACD queues, so this should not be a limitation.


C h a p t e r 5

Test and Debug Capabilities

In this chapter Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Self test features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Factory test features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

VxWorks shell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Card state debug utilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Application level debugging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Test and Debug Capabilities Standard 01.03


Introduction

The Nortel Call Recording Card provides maintenance and diagnostic features at various levels to identify and clear fault conditions. The card features include:

Self test features

Factory test features

VxWorks shell

Card state debug utilities

Application level debugging

November 2009 Test and Debug Capabilities


Self test features

The Nortel Call Recording Card runs various diagnostics to detect hardware faults and ensure correct operation. The test coverage is divided into the following categories:

8051 co-processor power up self tests

BIOS diagnostics

Base code self tests

Progress information of self tests is available through the serial port on the Card.



Factory test features

Factory test features include the HEX display, status LED, and reset switch.

HEX display codes

The Nortel Call Recording Card base card includes a HEX LED display on the faceplate to provide status information during maintenance operations. During startup and diagnostic tests, this display provides a visual progress indication, and information on the first failure detected. The HEX LED display codes are indicated in Table 12: “HEX Display codes during boot,” on page 52.

Table 12: HEX Display codes during boot

Code Code description

T:00 Initialization

T:01 Testing internal RAM

T:02 Testing ALU

T:03 Testing address modes

T:04 Testing watchdog

T:05 Testing 8051 co-processor

T:06 Testing timers

T:07 Testing external RAM

T:08 Testing dongle

T:09 Programming timeswitch FPGA

T:10 Programming ISPDI FPGA



If the internal RAM test, ALU test, address mode test, boot ROM test, timer test, or external RAM test fails, the pack goes into a maintenance loop because no further processing is possible.

If a test fails, F:XX shows on the HEX display for three seconds after the T:13 message, with the number represented by XX indicating the test that failed. For example, if the 8051 co-processor test failed, F:05 shows. If more than one test fails, the message indicates the first failure.

T:11 Testing host dual port RAM

T:12 Testing DS-30 dual port RAM

T:13 Testing SEEPROM

T:14 Booting IXP1200, waiting for response with self test information

T:15 Not used at present





T:20 Waiting for application start-up message from IXP1200

T:21 T:21 CardLAN enabled, waiting for request configuration message

T:22 T:22 CardLAN operational, A07 enabled, display now under host control

VPOK Card booted but slot not enabled at switch

CRC Card fully booted and operational




In addition, if the IXP encounters any failures during its initialization, an H:XX error code displays. The list of error codes is shown in Table 13: “HEX display error codes,” on page 54:

Table 13: HEX display error codes

You can also use the RS232 port to monitor the progress of self tests. Messages indicating the completion of each self test phase, as well as any detected faults are printed to this port. Support is provided for boundary scan and access to the boundary scan interface on the FPGAs.

Status LED

A single red LED on the faceplate indicates the enabled / disabled status of the card, and indicates the power status on self test.

The LED is OFF if:

the channel capacity of the card is not zero

and


H:00 IXP1200 not booting

H:01 SDRAM test failure

H:02 SRAM test failure

H:04 PCMCIA device failure

H:08 Network interface failure

H:10 Meridian interface failure

H:20 DSP interface failure

H:40 NVRAM/EEPROM interface failure

H:80 PCM connector failure



the card is in the normal mode of operation.

The LED is ON if:

the channel capacity of the card is zero.

or

the card is in maintenance mode.

Reset switch

The reset switch on the faceplate permits you to manually reset the card without having to power down. You typically use this switch to clear a fault condition during setup or during non-traffic periods.

ATTENTION!

Before using the Reset Switch you must ensure that the Nortel Call Recording Card is disabled in LD32 using the DISC command. Otherwise some of the ports may cause an OVD error on the Meridian CPU and become disabled when the card resets. Once the card is reactivated (the HEX display has passed the T:21 state) re-enable the card in LD32 using the ENLC command.

Debug terminal access

Access the Nortel Call Recording Card debug terminal using an RS-232 port. You can access this port is using the NTAG81CA faceplate serial cable. Messages indicating the completion of each self-test phase, as well as any detected faults, log to this serial port.

The pinouts for the Mini-DIN Connector, to which the faceplate maintenance cable connects, are shown in Table 14: “Faceplate connector mini-DIN Connector pin-out,” on page 56.

The terminal connected to the serial port requires these settings: 9600bps, 8 data bits, 1 stop bit, no parity, and no flow control.



Table 14: Faceplate connector mini-DIN Connector pin-out

Debug features

When the Nortel Call Recording Card starts, the 8051 auxiliary processor controls the serial port and uses it to provide debug information, progress of self tests, and so on. After the 8051 auxiliary processor releases the main processor (ixp1200) from reset, the main processor (by default) grants VxWorks shell access through this port. The card also supports remote access to the shell through telnet.

Pin # Signal Directory Description

1 BDTRB- O Port B data terminal ready

2 BSOUTB- O Port B serial data out

3 BSINB- I Port B serial data in

4 SGND C Signal ground

5 BSINA- I Port A serial data in

6 BCTSA- I Port A clear to send

7 BSOUTA- O Port A serial data out

8 BDTRA- O Port A data terminal ready



VxWorks shell

The VxWorks shell performs basic operations, administration, and management (the most important of which is loadware upgrade). Access the VxWorks shell through a serial connection to COM1 or through a telnet connection. The shell is protected from unauthorized access by a user name and password. This password is common across FTP, telnet, and the serial port. If the shell is idle for a period of time you must enter the password and user name again to gain access.

Once you enter the shell user name and password, you have complete access to all the VxWorks commands.

ATTENTION!

Incorrect use of some shell commands can cause the Nortel Call Recording Card to restart and may change operational behavior.

The default user name is crcadmin and the default password is crcsecurity.



Card state debug utilities

Some debug facilities are available from the VxWorks shell, which you can use to print out the state of certain global variables. A list of the available debug commands is provided in Table 15: “VxWorks shell card state debug utilities,” on page 58.

Table 15: VxWorks shell card state debug utilities

Use these commands to debug issues on the card at various levels.

Command Description

getAriesState Prints current state of all 32 M2616 (Aries) sets

printAriesState x Prints globals associated with M2616 (Aries) set x

printVpGlobs Prints all VP globals

printVpChannel x Prints globals associated with VP channel x

swInfoGet Prints the loadware, DSP and 8051XA firmware versions

ifShow Prints the IP and Ethernet addresses

inetStatShow Prints the status of all network links

Ping "10.85.15.60",x Pings IP address 10.85.15.60 x number of times.

Press Ctrl+C to stop to return to VxWorks shell.



Application level debugging

The following section documents application level debugging.

Task logging commands

Table 16: “Task logging commands,” on page 59 lists the commands to turn logging on and off for each of the individual tasks in the Nortel Call Recording Card application.

Table 16: Task logging commands

Task Turn logging:On Off

Parameters

DSPM gLogDspm=1 gLogDspm=0

Aries AriesDebugOn 0,X ariesDebugOff 0,X 0,X -- range of channels

tcmDebugOn 0,X tcmDebugOff 0,X

VP-App vpDebugOn vpDebugOff

Socket socketDebugOn socketDebugoff

Client clientDebugOn clientDebugOn




C h a p t e r 6

Upgrade Procedures

In this chapter Application loadware upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

XA firmware upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

BootROM loadware upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Upgrade Procedures Standard 01.03


Application loadware upgrade

The loadware is located on the compact flash drive as the file C:/exec. To upgrade the card, the contents of this file must be overwritten with the new target load. There are three recommended methods for performing this task:

1. “Loadware upgrade from an external FTP server,” on page 62.

2. “Loadware upgrade using the PCMCIA Card to transfer loadware to the compact flash card,” on page 63.

3. “Loadware upgrade using FTP to transfer the loadware to the compact flash card,” on page 65.

You must access VxWorks shell to upgrade the card. This is available either through a telnet connection or through serial access to COM1. For shell access, the default user name is crcadmin and the default password is crcsecurity. See “VxWorks shell,” on page 57 for more information.

Loadware upgrade from an external FTP server

Use the following procedure to perform a loadware upgrade from an external FTP server.

1 Copy the loadware to an FTP server.

2 Disable the card using overlay 32 on the switch software.

3 Perform the upgrade using the upgrade command from the shell as shown in the following example:

upgrade("<Server IP Address>", "<userID>", "<password>", "<path>","newexec")value = 0 = 0x0Connecting to <Server IP Address>...connected to <Server IP Address> OKFile Length = 0x0059d1fcBank Size = 0x00780000Updating sector: 0..1..2..3..4..5..6..7..8..9..10..11..12..13..14..15..16..1

November 2009 Upgrade Procedures


7..18..19..20..21..22..23..24..25..26..27..28..29..30..31..32..33..34..35..36..37..38..39..40..41..42..43..44..file read complete Program filename = /C:/exec Checksum = 0xdef4797d length = 0x59d1fcVerifying checksum ...Upgrade completed OKReboot the pack to run new loadware

The <userid> and <password> are those of the FTP server and the <path> is the path to the file on the FTP Server.

4 After the upgrade is complete, enable the card from overlay 32 on the switch software

5 Restart the card.

6 After the card is restarted, at the shell, type:

swVersionShow <CR>

This command displays the current software version running on the card. For example:

softwareRev: CRC Rel: 0.01

Loadware upgrade using the PCMCIA Card to transfer loadware to the compact flash card

Use this procedure to upgrade the loadware from the local /C:/ drive Compact flash card.


2 Insert the PCMCIA card into the faceplate PCMCIA card slot.

3 Copy loadware from the PCMCIA card (/A:/ drive) to the compact flash card (/C:/ drive) as shown in the following example:

copy("/A:/newexec","/C:/newexec")

The checksum value varies between software loads. Consult the release notes for the applied upgrade load to identify the correct value.



4 Remove the PCMCIA card from the faceplate slot.

Attention: Do not insert a card in the /A:/ drive when Nortel Call Recording Card is in normal operation.

5 At the shell, upgrade the loadware using the upgradePCMCIA command as shown in the following example:

upgradePCMCIA("/C:/newexec")value = 0 = 0x0Opening file /C:/newexecFile /C:/newexec openedFile Length = 0x0059d1fcBank Size = 0x00780000Updating sector: 0..1..2..3..4..5..6..7..8..9..10..11..12..13..14..15..16..17..18..19..20..21..22..23..24..25..26..27..28..29..30..31..32..33..34..35..36..37..38..39..40..41..42..43..44..file read complete Program filename = /C:/exec Checksum = 0xdef4797d length = 0x59d1fcVerifying checksum ...Upgrade completed OKReboot the pack to run new loadware

"C:/newexec" is the location of the file copied onto the compact flash card.

6 After the upgrade is complete, remove the original loadware file transferred to the card by typing the following from the shell:

rm "/C:/newexec" <CR>

7 Enable the card using overlay 32 on the switch software.

8 Restart the card.

9 After the card restarts, type the following command at the shell:

swVersionShow <CR>

This command displays the current software version running on the card, for example:





Loadware upgrade using FTP to transfer the loadware to the compact flash card

Use this procedure to upgrade the loadware from the local /C:/ drive on the compact flash card.


2 FTP into the IP address of the card. Use the same user name and password as used for the VxWorks shell. See “VxWorks shell,” on page 57 for more information.

3 Change the directory to the /C: drive on the card.

4 Change the file transfer type to binary.

5 Copy the new loadware file to the compact flash drive. The following example shows copying the loadware (newexec) onto the compact flash drive of the card.

ftp "<Card IP address>",Connected to <Card IP address>",.220 VxWorks FTP server (VxWorks 5.4) ready.Name (<Card IP address>",:user1): crcadmin331 Password requiredPassword:230 User logged inftp> bin200 Type set to I, binary modeftp> cd "/C:/"250 Changed directory to "/C:/"ftp> put newexec200 Port set okay150 Opening BINARY mode data connection226 Transfer completelocal: newexec remote: newexec5886476 bytes sent in 15 seconds (389.57 Kbytes/s)ftp> bye221 Bye...see you later

6 At the shell, upgrade the loadware using the upgradePCMCIA command as shown in the following example:

upgradePCMCIA("/C:/newexec")value = 0 = 0x0



Opening file /C:/newexecFile /C:/newexec openedFile Length = 0x0059d1fcBank Size = 0x00780000Updating sector: 0..1..2..3..4..5..6..7..8..9..10..11..12..13..14..15..16..17..18..19..20..21..22..23..24..25..26..27..28..29..30..31..32..33..34..35..36..37..38..39..40..41..42..43..44..file read complete Program filename = /C:/exec Checksum = 0xdef4797d length = 0x59d1fcVerifying checksum ...Upgrade completed OKReboot the pack to run new loadware.

7 After the upgrade is complete, remove the original loadware file that was transferred onto the card by typing the following command from the shell:

rm "/C:/newexec" <CR>

Where "C:/newexec" is the location of the file copied to the compact flash card.

8 Enable the card using overlay 32 on the switch software.

9 Restart the card.

10 After restarting the card, type the following command from the shell:

swVersionShow <CR>

This command displays the current software version running on the card, for example:





XA firmware upgrade

There are three recommended methods for upgrading XA firmware.

1. “XA upgrade from an external FTP server,” on page 67.

2. “XA upgrade using PCMCIA card to transfer firmware to compact flash card,” on page 68.

3. “XA upgrade using FTP to transfer firmware to compact flash card,” on page 69.

Note: XA Upgrades to the card require access to the VxWorks shell on the bootROM load. This is available either through a telnet connection or through serial access to COM1. For bootROM load shell access, the default user name is itgadmin and the default password is itgadmin.

XA upgrade from an external FTP server

Use this procedure to upgrade XA from an external FTP server.

1 Ensure the XA firmware is loaded on an FTP server.

2 Reboot the card.

3 While the card reboots, when prompted, type jkl to access the bootROM.

Note: The LAN cable must be connected into the other port on the L-adapter for the network interface on the bootROM load to work correctly.

4 Perform the upgrade by typing the following command at the shell:

upgradeXa "<server IP address>", "<userid>", "<password>", "<path>", "<filename>" <CR>

The <userid> and <password> are those of the FTP server and the <path> is the path to the file on the FTP server.

5 After the upgrade is complete, reboot the card.



XA upgrade using PCMCIA card to transfer firmware to compact flash card

Use this procedure to perform an XA upgrade using the PCMCIA card to transfer firmware to the compact flash card.

1 Reboot the card.


3 Insert the PCMCIA Card into the faceplate PCMCIA Card slot.

4 Copy the loadware from the PCMCIA card (/A:/ drive) to the compact flash card (/C:/ drive) as shown in the following example:

copy("/A:/filename","/C:/filename")

5 Remove the PCMCIA Card from the faceplate slot.

Attention: Do not insert a card in the /A:/ drive when Nortel Call Recording Card is in normal operation.

6 Upgrade the XA firmware by typing the following command from the shell:

upgradeXa "<server IP address>", "<userid>", "<password>", "<path>", "<filename>" <CR>

Where <Server IP Address> is the IP address of the Nortel Call Recording Card. <userid> and <password> are the same as the shell user name/ password on the Nortel Call Recording Card. <path> is the location on the card where the XA firmware is located.




XA upgrade using FTP to transfer firmware to compact flash card

Use this procedure to upgrade XA using FTP to transfer firmware to the compact flash card.

1 Use the FTP application to copy the XA firmware onto the /C: drive using the same method as outlined previously for transferring the application load.


2 Reboot the card.


4 Upgrade the XA firmware by typing the following from the shell:

upgradeXa "<server IP address>", "<userid>", "<password>", "<path>", "<filename>" <CR>.

Where <Server IP Address> is the IP address of the Nortel Call Recording Card. <userid> and <password> are the same as the shell user name/ password on the Nortel Call Recording Card. <path> is the location on the card where the XA firmware is located.




BootROM loadware upgrade

There are three recommended methods for upgrading bootROM loadware.

1. “BootROM loadware upgrade from an external FTP Server,” on page 70.

2. “BootROM loadware upgrade using PCMCIA Card to transfer loadware to Compact Flash Card,” on page 71.

3. “BootROM loadware upgrade using FTP to transfer loadware to Compact Flash Card,” on page 71.

BootROM loadware upgrades to the card require access to the VxWorks shell on the bootROM load. This is available either through a telnet connection or through serial access to COM1. For bootROM load shell access, the default user name is itgadmin and the default password is itgadmin.

BootROM loadware upgrade from an external FTP Server

1 Ensure the BootROM loadware firmware is loaded on an FTP server.

2 Reboot the card.


Attention: The LAN cable must be connected into the other port on the L-Adapter for the network interface on the bootROM load to work correctly.

4 At the shell, perform the upgrade by typing the following command:

upgradeBoot "<server IP address>", "<userid>", "<password>", "<path>", "<filename>" <CR>

The <userid> and <password> are those of the FTP server and the <path> is the path to the file on the FTP Server.




BootROM loadware upgrade using PCMCIA Card to transfer loadware to Compact Flash Card

Use this procedure to perform a BootROM loadware upgrade using PCMCIA Card to transfer loadware to Compact Flash Card.

1 Reboot the card.


3 Insert the PCMCIA card into the faceplate PCMCIA Card slot.

4 Copy loadware from the PCMCIA card (/A:/ drive) onto the compact flash card (/C:/ drive) as shown in the following example:


5 Remove the PCMCIA card from the faceplate slot.

Note: Do not insert a card in the /A:/ drive when the Nortel Call Recording Card is in normal operation.

6 At the shell, perform the bootROM, by typing the following command:

upgradePCMCIABoot "/C:/bootROM"<CR>.

Where <Server IP Address> is the IP address of the Nortel Call Recording Card. <userid> and <password> are the same as the shell user name/ password on the Nortel Call Recording Card. <path> is the location on the card where the bootROM loadware is located.


BootROM loadware upgrade using FTP to transfer loadware to Compact Flash Card

Use this procedure to perform a BootROM loadware upgrade using FTP to transfer loadware to Compact Flash Card.

1 FTP the bootROM loadware onto the /C: drive using the same method as outlined previously for transferring the application load.

2 Reboot the card.




4 At the shell, perform the bootROM, by typing the following command:

upgradeBoot "<server IP address>", "<userid>", "<password>", "<path>", "<filename>" <CR>.

Where <Server IP Address> is the IP address of the Nortel Call Recording Card. <userid> and <password> are the same as the shell user name/ password on the Nortel Call Recording Card. <path> is the location on the card where the bootROM loadware is located.



A p p e n d i x A

Precautions, Samples, and Error Codes

In this appendixPrecautions for handling circuit cards . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Sample boot sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Error code definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Precautions, Samples, and Error Codes Standard 01.03


Precautions for handling circuit cards

Figure 8: Warning risk of personal injury

To avoid personal injury and equipment damage when handling circuit cards, follow the guidelines listed below:

Wear a properly connected antistatic wrist strap when you work with switching equipment. If a wrist strap is not available, regularly touch one of the bare metal strips in a module to discharge static.

Do not unpack or handle cards near electric motors, transformers, or similar machinery.

Handle cards by the edges only. Do not touch the contacts or components.

Set cards on a protective antistatic bag. If an antistatic bag is not available, hand-hold the card, or set it in a card cage unseated from the connectors.

Store cards in their protective packing. Do not stack cards on top of each other unless they are packaged.

Keep cards installed in the system as much as possible to avoid dirty contacts and unnecessary wear.

Store cards in a cool, dry, dust-free area.

November 2009 Precautions, Samples, and Error Codes


Figure 9: Repair and maintenance

Complete the following tasks during repair and maintenance procedures:

Turn off the circuit breaker or switch for a module power supply before the power supply is removed or inserted.

Software disable cards, if applicable, before they are removed or inserted.

Hardware disable cards, whenever there is an enable/disable switch, before they are removed or inserted.

Return defective or heavily contaminated cards to a repair center. Do not try to repair or clean them.



Sample boot sequence

Figure 10 below shows a sample boot sequence for the Nortel Call Recording Card. The Nortel Call Recording Card software release is printed to the screen during the boot sequence. This is shown in Figure 10: “Sample boot sequence,” on page 76.

Figure 10: Sample boot sequence

MC Firmware Rls 6.58051XA Firmware Version 4.9 6 Dec 2002(C) Nortel Inc. 2001EPLD Version: 4.032K External RAM detected8K DPRAM detectedDongle serial number: 10237502All FPGAs are configuredAll self tests have passedSRAM test okay

SDRAM Addr test okay

SDRAM blank over

Early serial debug initialized

VxWorks System Boot

Copyright 1984-1998 Wind River Systems, Inc.



CPU: IXP1200

Version: 5.4

BSP version: 5.2

Creation date: Feb 24 2003, 11:03:32

Enter jkl to force boot to BootROM vxWorks prompt

auto-booting...

boot device : ata=

unit number : 1

processor number : 0

file name : /C:/exec

flags (f) : 0x0

other (o) : ixpMac

Attaching to ATA disk device... Found device : Cirrus CL-PD672x

PC Card Detected: Socket 1

cisGet : pcCard recognized

Loading /C:/exec...

/C:/ - Volume is OK

2517080 + 1549940 + 11287972

Starting at 0x1000...

Early serial debug initialized



Setting tLogTask priority to 250

Found device : Cirrus CL-PD672x

0x3affe64 (tRootTask): PC Card Detected: Socket 1

logTask: 2 log messages lost.

ipMethodInit, gIPMethod = 2

IP Address from NVRAM: 47.166.107.144

IP Data in NVRAM Valid, Boot Line updated

IP Address:47.166.107.144

Gateway Address:47.166.107.190

Subnet Mask::ffffffc0

Host Name: bootHost

Target Name: vxTarget

User: defuser

MAC Address for Port 0 is : 00:20:d8:d0:48:9e

SysConf: uEng_intConnect to pktHandlingIsr.

0 symbols bound.

Load uCode from buffer Status : Return Success

Starting Microengines.

0x3affe64 (tRootTask): Loading MAC_21440...

0x3affe64 (tRootTask): mac21440Load: Init String[0] NULL: ixpMac


0x3affe64 (tRootTask): MAC 21440 String : Processed all arugments

0x3affe64 (tRootTask): mac21440InitMem: Net Pool ID is 49099716

0x3affe64 (tRootTask): Done loading mac21440...



0x3affe64 (tRootTask): mac21440Start: Starting port 0

TLAN Port set to Auto-Negotiate Speed and Duplex Settings

Waiting For Carrier link to Return

MAC Address for Port 1 is : 00:20:d8:d0:48:9f

0x3affe64 (tRootTask): Carrier still down after 10 Seconds


0x3affe64 (tRootTask): mac21440Load: Init String[0] NULL: ixpMac


0x3affe64 (tRootTask): MAC 21440 String : Processed all arugments

0x3affe64 (tRootTask): mac21440InitMem: Net Pool ID is 44973820

0x3affe64 (tRootTask): Done loading mac21440...

0x3affe64 (tRootTask): mac21440Start: Starting port 1

ELAN set to 10BaseT Operation

ELAN set to Half Duplex Operation

Waiting For Carrier link to Return

Attached TCP/IP interface to ixpMac unit 0

Attaching network interface lo0... done.

NFS client support not included.

Adding 7917 symbols for standalone.

]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]

]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]



]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]

]]]]]]]]]]] ]]]] ]]]]]]]]]] ]] ]]]] (R)

] ]]]]]]]]] ]]]]]] ]]]]]]]] ]] ]]]]

]] ]]]]]]] ]]]]]]]] ]]]]]] ] ]] ]]]]

]]] ]]]]] ] ]]] ] ]]]] ]]] ]]]]]]]]] ]]]] ]] ]]]] ]] ]]]]]

]]]] ]]] ]] ] ]]] ]] ]]]]] ]]]]]] ]] ]]]]]]] ]]]] ]] ]]]]

]]]]] ] ]]]] ]]]]] ]]]]]]]] ]]]] ]] ]]]] ]]]]]]] ]]]]

]]]]]] ]]]]] ]]]]]] ] ]]]]] ]]]] ]] ]]]] ]]]]]]]] ]]]]

]]]]]]] ]]]]] ] ]]]]]] ] ]]] ]]]] ]] ]]]] ]]]] ]]]] ]]]]

]]]]]]]] ]]]]] ]]] ]]]]]]] ] ]]]]]]] ]]]] ]]]] ]]]] ]]]]]

]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]

]]]]]]]]]]]]]]]]]]]]]]]]]]]]] Development System

]]]]]]]]]]]]]]]]]]]]]]]]]]]]

]]]]]]]]]]]]]]]]]]]]]]]]]]] VxWorks version 5.4

]]]]]]]]]]]]]]]]]]]]]]]]]] KERNEL: WIND version 2.5

]]]]]]]]]]]]]]]]]]]]]]]]] Copyright Wind River Systems, Inc., 1984-2000

CPU: IXP1200. Processor #0.

Memory Size: 0x3b00000. BSP version 3.2+AG.

****************************************************

-> NORTEL CALL RECORDING CARD

SoftwareRelease: CRC 0.1

****************************************************

0x2a61d94 (tMaint): Task spawned.

Indicates booting with a Nortel Call Recording Card load. If this is not present, the incorrect loadware is on the card.



0x3affe64 (): task deadrecordingDiskInit: created REC: volume (5 MB)

0x2a61d94 (tMaint): Init XA

0x2a61d94 (tMaint): XA : - Create MsgQ (Struct)

0x2a61d94 (tMaint): XA : - Register with M-1 Manager

0x2a61d94 (tMaint): XA : - Spawn xaTask()

0x2516b50 (tXA): Task Spawned OK

********** Initalising initAppGlob

serial number = d8d0489f

/C:/ - Volume is OK

0x2a61d94 (tMaint): XA : - Query 8051XA for Dongle ID

0x2a61d94 (tMaint): dspmInit : Initialising DSPM

0x2516b50 (tXA): Got Dongle Response

0x2516b50 (tXA): Dongle : 10237502

0x2516b50 (tXA): Got Version Response

0x2516b50 (tXA): Version : MC Firmware Rls 6.5

0x2516b50 (tXA): Serial Number not supported

0x250c0e8 (tDSPM): tDSPM suspended

0x2a61d94 (tMaint): xaToHostPollingEnable: XA to Host Polling Enabled.

0x243fa38 (tVpAppl): Task spawned.



0x2501d90 (tGenDTMF): Task spawned.

0x2501d90 (tGenDTMF): Task initializing...

0x2503f3c (tAries): Task spawned.

0x2503f3c (tAries): Task initializing...

0x2503f3c (tAries): Downloading ag-sa timeswitch

0x2503f3c (tAries): Not sending the configuration message

0x24ffbe4 (tMirosInit): mirosInit

0x243d88c (tServer): Task spawned.

0x243d88c (tServer): Task initializing...

0x243d88c (tServer): tServer IP Addr: 47.166.107.144

0x2514294 (tDspmStart): dspmStart : Downloading DSP Loadware (File) to core 0...

0x2514294 (tDspmStart): dmaInit : Initialising DMA...

0x243fa38 (tVpAppl): Task initializing...

0x243fa38 (tVpAppl): Giving the dspmSem to let the dspm run




0x2514294 (tDspmStart): Trying to take the dspmSem

0x2514294 (tDspmStart): Dspm bootup proceeding...

0x3afd010 (tAriesAudit): Task spawned.

0x3afd010 (tAriesAudit): Task initializing...

0x2a61d94 (tMaint): Aries go operational...

0x2503f3c (tAries): Task operational.

0x2a61d94 (tMaint): Aries audit go operational...



0x3afd010 (tAriesAudit): Task operational.

0x2a61d94 (tMaint): Generate DTMF go operational...

0x2501d90 (tGenDTMF): Task operational.

0x2a61d94 (tMaint): VP application go operational...

0x243fa38 (tVpAppl): Trying to take vpAppSem

0x2514294 (): task dead Giving the vpapp semaphore

0x243fa38 (tVpAppl): VP-App Resuming...

0x250c0e8 (tDSPM): tDSPM resuming...

0x243fa38 (tVpAppl): Task operational.

0x2a61d94 (tMaint): Server go operational...

0x243d88c (tServer): Task operational.

0x2a61d94 (tMaint): tMirosInit application go operational...

0x24ffbe4 (tMirosInit): MIROS: VPS App Task is operational with 32 DSP ports and 32 ARIES ports

0x24ffbe4 (tMirosInit): mirosLoadSoftwareVersion: loaded version 0.1

0x24ffbe4 (tMirosInit): TUI language Directory is '/C:TUI/ENGLISH'



Error code definitions

Figure 11: “Nortel Call Recording Card error code definitions,” on page 84 shows the error code definitions the Call Recording Card sends to the QM application when errors occur on the Call Recording Card.

Figure 11: Nortel Call Recording Card error code definitions

#define C_NONE 0 /* no error occurred */#define C_UNKNOWN 1 /* Unknown cause */#define C_PREV_REGISTERED 2 /* Previously registered */#define C_UNSUPPORTED_PROTOCOL3 /* Protocol Version not supported by this

* version of software */#define C_INV_PROTOCOL 4 /* Invalid Protocol Version */#define C_INV_SOFTWARE_REV 5 /* Invalid Sfotware Version */#define C_POLL_FREQ_RANGE 6 /* Polling Frequency Out of Range */#define C_INV_EVENT_NOTIFY 7 /* Invalid Event Notification flag */#define C_ALREADY_RELEASED 8 /* Client Already Released */#define C_NOT_REGISTERED 9 /* Client Not Registered */ #define C_NUM_CHANNEL_RANGE 10 /* No. of channels exceeds card capacity */#define C_INCOMPLETE 11 /* Incomplete Oper. (Not enough channels */#define C_INV_NUM_CHANNELS 12 /* Bad Value for Number of Channels */#define C_INV_PARTIAL_OP 13 /* Bad Value for Partial Operation */#define C_NOT_ACQUIRED 14 /* Channel not acquired before operation */#define C_INV_CHANNEL_ID 15 /* Invalid Channel ID */#define C_INV_MAINT_COMMAND 16 /* Invalid Maintenance Command */#define C_INV_CARD_STATE 17 /* Invalid Card State Value */#define C_SEG_SET_OPEN 18 /* Segment Set Already Open */#define C_MAX_OPEN_SEG 19 /* Max. Open Segment set limit reached */#define C_NO_SUCH_SEG 20 /* Segment does not exist */#define C_INV_SEG_SET 21 /* Invalid Segment Set */#define C_NOT_CONNECTED 22 /* OBSOLETE in Rls1.5 * Not Connected

*/#define C_IN_USE 23 /* Already In Use or active*/#define C_PLAY_IN_PROGRESS 24 /* Play Command Already in Progress */#define C_OPERATION_STOPPED 25 /* Operation stopped by other command */#define C_INV_SEG 26 /* OBSOLETE in Rls1.7

* Bad Segment */

#define C_NULL_SEG 27 /* No Segment Specified (null list) */#define C_INV_INTERRUPT_FLAG 28 /* Invalid Interrupt Flag */#define C_INV_CLEAR_BUF_OPT 29 /* Invalid Clear Buffer Option */#define C_INV_REPEAT_FLAG 30 /* Invalid Repeat Flag */#define C_ALREADY_COLLECTING 31 /* Already Collecting Digits on channel */



#define C_MIN_DIGIT 32 /* Minimum Digit Not Reached */#define C_TOUT_FIRST 33 /* First Digit Timeout */#define C_TOUT_INTER 34 /* Inter Digit Timeout */#define C_OVFL_KEY_BUF 35 /* Key Buffer Overflow */#define C_INV_CANCEL_KEY 36 /* Invalid Cancel Key String */#define C_INV_TERM_KEY 37 /* Invalid Termination Key String */#define C_MIN_EXCEEDS_MAX 38 /* Minimum Digit exceeds Maximum Digit */#define C_MAX_EXCEEDS_BUF_SIZE 39 /* Maximum Digit exceeds key buffer size*/#define C_CANCEL_EQ_TERM 40 /* Canceling key equals Termination Key */#define C_INV_LOCATION 41 /* OBSELETE in Rls1.5

* No such location */

#define C_INV_DTMF 42 /* Invalid DTMF String */#define C_INV_SEQUENCE 43 /* Prerequisite Operation not executed */#define C_NO_ANSWER 44 /* Call Not Answered */#define C_INV_DN 45 /* Invalid DN */#define C_NOT_OFF_HOOK 46 /* OBSELETE in Rls1.5

* Channel Not Off Hook */

#define C_NOT_JOINED 47 /* Channels not Joined */#define C_TOUT_POLL 48 /* Polling Timeout */#define C_MAINT_MODE_IN_PROG 49 /* Maintenance mode request in progress */#define C_CALLER_DISCONNECT 50 /* Disconnected by Caller */#define C_INV_MESSAGE 51 /* Invalid Message */#define C_MAX_CLIENT_LIMIT 52 /* Maximum number of clients connected */#define C_IE_NOT_FOUND 53 /* Mandatory IE not found */#define C_INV_DSP_PORT 54 /* DSP Ports value out of range */#define C_INV_ARIES_PORT 55 /* Aries Portsvalue out of range */#define C_INV_CAPACITY 56 /* Capacity value out of range */#define C_INV_FULL_FLAG 57 /* Invalid Full Flag value */#define C_INV_RESULT 58 /* Result value out of range */#define C_INV_CHANNEL_PAIR 59 /* Channels IDs are equal, invalid for a

* joinchannel command */

#define C_INV_SEG_LIST 60 /* Error verifying Segment list IE */#define C_ERR_SEG_LIST_EXTRACT61 /* Error getting segment info from a

* segment list IE */

#define C_INV_SERIAL_NUM 62 /* Serial IE incorrect length */#define C_INV_MANUFACTURING 63 /* Invalid length for Manufacturing IE */#define C_INV_STATISTICS 64 /* Invalid len for Client Statistics IE */#define C_INV_CAUSE 65 /* Invalid Cause IE */#define C_IE_UNKNOWN 66 /* Unknown IE in a message */#define C_CLIENT_RELEASE 67 /* Close socket and release the client */#define C_OVFL_MSG_Q 68 /* Too many requests are placed in the

* Application work Q at a time */

#define C_OVFL_WIP 69 /* All the clients WIP slots are full*/



#define C_MESSAGE_UNSUPPORTED 70 /* message known but not supported */#define C_MSG_LEN_TOO_BIG 71 /* max message length exceeded */#define C_NOT_ACTIVE 72 /* channel is not active */#define C_ALREADY_ACQUIRED 73 /* channel alreay acquired */#define C_ALREADY_ACTIVE 74 /* channel alreay active */#define C_MSG_LEN_TOO_SMALL 75 /* msgLen< allowed or msgLen < hdrIE len */#define C_NO_CALL_TO_ANSWER 76 /* no call to answer on channel */#define C_PRIMARY_DSCNTD 77 /* call on primary DN has disconnected so

* conference, retrieve orig. not allowed */

#define C_INCOMING_CALL 78 /* incoming call on channel */#define C_ADDON_DSCNTD 79 /* add on call disconnected */#define C_KEY_NOT_CONFIGURED 80 /* key is not configured for this operation

* for this set */

#define C_CHANNEL_RELEASE 81 /* call disconnected due to channel release */

#define C_CHANNEL_DISABLE 82 /* channel released due to channel disable */#define C_BUSY_DN 83 /* busy DN dialled */#define C_DSP_ERROR 84 /* the DSP/DSPM is unable to process the

* request */

#define C_INV_RESET_STATS 85 /* invalid reset stats ie */#define C_ARIES_UNAVAILABLE 86 /* VP_Application unable to send action

* to ARIES task */

#define C_INV_CLIENT 87 /* OBSELETE in Rls1.5 * client ID different from client ID * which ordered card to enter * maintenance mode. */

#define C_INV_MAINT_TRANS 88 /* OBSELETE in Rls1.5 * request to change card state is not * allowed in current state. */

#define C_DIGNOT_ALREADY_DISABLED 89 /* digit notification already disabled */#define C_DSP_CARD_REMOVAL 90 /* dsp card removal event */#define C_CHANNEL_JOINED 91 /* The channel is curently joined */#define C_INV_PLAY_MODE 92 /* Play mode value invalid */#define C_DIGNOT_ALREADY_ENABLED 93 /* digit notification already enabled */#define C_INV_MINMAX_DIGIT 94 /* min/max digit value out of range */#define C_IN_REQUESTED_MODE 95 /* Already in requested maintenance mode */#define C_CONF_ESTABLISHED 96 /* Conference call on primary DN key */#define C_DISCONNECT_CALL 97 /* AddOn disconnected due to

* DisconnectCall request. */



#define C_M1_CONF_BUSY 98 /* ConferenceCall failed. M1 out of * conference loops. */

#define C_FTP_IN_PROGRESS 99 /* Cannot exit maintenance mode if FTP * session in progress. */

#define C_LOADWARE_UPGRADE 100 /* cannot exit maintenance mode during * loadware upgrade

*/#define C_DSP_UPGRADE 101 /* cannot exit maintenance mode during

* DSP firmware upgrade */

#define C_DN_NOT_SUPPORTED 102 /* DN string too long (max 31 digits) */#define C_ATA_DISK_REMOVAL 103 /* ATA Disk removal event */#define C_XA_UPGRADE 104 /* cannot exit maintenance mode during

* 8051xa upgrade */

#define C_INV_KEYCODE 105 /* keycode supplied is invalid */#define C_BUFFER_ERROR 106 /* error in accessing record buffer space */#define C_BUFFER_FULL 107 /* record buffer space is full */#define C_LOCALFILE_ERROR 108 /* error in creating local file */#define C_RECORDING 109 /* DSP is already recording channel */#define C_NOT_RECORDING 110 /* DSP is not currently recording */#define C_OBSERVE_FAIL 111 /* invalid agent ID, or agent is

* already being observed, or set never entered observe mode after the

observe key was pressed. */#define C_INV_COMPRESSION_FLAG112 /* compression type specified invalid */#define C_INV_LOCALFILE_FLAG 113 /* localfile flag specified invalid */#define C_INV_IPADDRESS 114 /* invalid IP address */#define C_INV_USERNAME 115 /* Invalid Username length */#define C_INV_PASSWORD 116 /* Invalid Password length */#define C_INV_FILENAME 117 /* Invalid Filename length */#define C_INV_PATHNAME 118 /* Invalid Pathname lenth */#define C_INV_AGENTID 119 /* Invalid Agent ID */#define C_INV_RECORDID 120 /* Invalid Record ID */#define C_INV_INTERCALLGAP 121 /* Invalid Intercall Gap ID */#define C_INV_STORAGEUSED 122 /* Invalid Storage Used ID length */#define C_INV_FTPERROR 123 /* Invalid FTP Error */




A p p e n d i x B

Glossary

CDN Controlled Directory Number

CTI Computer Telephony Integration

DID Direct Inward Dial

DSP Digital Signal Processor

FTP File Transfer Protocol

ITGSA Internet Telephony Gateway Strong Arm

Media Card Hardware Platform for applications such as MIRAN

MIRAN Meridian Integrated Recorded Announcement Trunk

NTP Nortel Technical Publication

OPN Original Party Number

PC Personal Computer

SQL Standard Query Language

WAV File format used to store files under Microsoft Windows™.

Glossary Standard 01.03



Copyright © 2008-2009 Nortel Networks. All Rights Reserved.

While the information in this document is believed to be accurate and reliable, except as otherwise expressly agreed to in writing NORTEL PROVIDES THIS DOCUMENT "AS IS" WITHOUT WARRANTY OR CONDITION OF ANY KIND, EITHER EXPRESS OR IMPLIED. The information and/or products described in this document are subject to change without notice.

Nortel, Nortel Networks, the Nortel logo, and the Globemark are trademarks of Nortel Networks.

All other trademarks are the property of their respective owners.

To provide feedback or report a problem with this document, go to www.nortel.com/documentfeedback.

Publication number: NN44480-307Product release: 6.5 and 7.0

Document release: Standard 01.03

Date: November 2009

http://support.avaya.com/supportfaqs

Documents

Nortel Call Recording Card