EDITION 2
OCTEL PC/CDR
P/N 101–1480–000
MANUAL
�
Your comments about this document are welcome. They can assist us in improving ourproducts. Please address comments to [email protected] or to the Technical PublicationsManager at
Octel Communications Corporation1001 Murphy Ranch RoadMilpitas, California 95035-7912U.S.A.408-321-2000http://www.octel.com
Copyright� 1996 by Octel Communications Corporation1001 Murphy Ranch RoadMilpitas, California 95035-7912
All rights reserved. No part of this book may be reproduced in any form without writtenpermission from Octel Communications Corporation.
All trademarks identified by the � or � symbol are trademarks or registered trademarks,respectively, of Octel Communications Corporation. All other trademarks belong to theirrespective owners.
Printed in the United States of America.
TEXT PRINTED ON
RECYCLED PAPER
P R E F A C E
iiiEdition 2Octel PC/CDR
The Octel PC/CDR Manual provides instructions about the installation,configuration, and use of Octel PC/CDR Release 2.3. This manual isintended for system managers, Octel and distributor service representatives,and Octel-trained technicians. The term system manager is used in thismanual to describe the person responsible for the Octel PC/CDR application.
This manual is arranged in the same order as the Octel PC/CDR operatingstructure, thus providing easy-to-follow guidelines for operation. Anoverview of the major steps required to use Octel PC/CDR is found insection 1.3.
Throughout most of this manual, the term server is used to refer collectivelyto the Octel Overture 250 and 350 message servers and the Aspen, Branch,Branch XP, Maxum SE, Maxum, and Octel XC1000 voice processors.Exceptions to this rule are noted accordingly.
The terms CDR PC and PC are used interchangeably to refer to thepersonal computer in which the Octel PC/CDR software resides.
CONVENTIONS
The following typographical conventions are used in this manual:
� Bold italic is used for key names, field names, field values, and thetext you must type. For example,
Select option 4 and press Enter.
� Italic is used for the titles of books and for emphasis. For example,
The PC and server baud rates must match, even if you are using adirect connection.
INTERNATIONAL SYMBOLS
The following symbols are used in this manual:
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
When . . .ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
We use this symbol . . .
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
There could be damage to thesoftware or hardware
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
The action could cause personalinjury
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
O C T E L
P C / C D R
CONTENTS
C O N T E N T S
viiEdition 2Octel PC/CDR
1: INTRODUCTION
1.1 OVERVIEW 1-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 OCTEL PC/CDR COMPATIBILITY 1-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3 PROCESS CHECKLIST 1-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4 KEY TERMS AND DEFINITIONS 1-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5 MENU FLOW 1-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6 OCTEL PC/CDR INTERACTION 1-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.7 CDR BUFFER 1-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.8 ALARMS 1-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.9 COLLECTION FILES 1-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2: DATA-COLLECTION PREPARATION
2.1 OVERVIEW 2-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2 UNDERSTANDING THE CDR BUFFER 2-1. . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3 SIZING THE PC AND DETERMINING PROCESSING TIME 2-10. . . . . . .
2.4 CONFIGURING THE SERVER FOR CDR DATA COLLECTION 2-14. . . .
3: INSTALLATION PROCEDURES
3.1 OVERVIEW 3-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2 INSTALLING OCTEL PC/CDR SOFTWARE ON THE PC 3-1. . . . . . . . . . .
3.3 CREATING CDR SYSTEM DATA SUBDIRECTORIES USING MKCDRSYS 3-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4 REMOVING CDR SYSTEM DATA SUBDIRECTORIES 3-9. . . . . . . . . . . . .
3.5 UPGRADING OCTEL PC/CDR SOFTWARE 3-10. . . . . . . . . . . . . . . . . . . . . . .
Chapter Page
C O N T E N T S
viii Edition 2 Octel PC/CDR
4: EQUIPMENT REQUIREMENTS AND CONFIGURATION
4.1 OVERVIEW 4-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2 PC REQUIREMENTS 4-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3 SOFTWARE REQUIREMENTS 4-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4 SERVER-TO-PC CONNECTORS 4-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5 EQUIPMENT CONFIGURATION FOR THE OCTEL OVERTURE 250 AND 350 4-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6 EQUIPMENT CONFIGURATION FOR THE BRANCH, BRANCH XP, ASPEN, MAXUM SE, AND MAXUM 4-12. . . . . . . . . . . . . . . .
4.7 EQUIPMENT CONFIGURATION FOR THE OCTEL XC1000 4-18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5: SOFTWARE ATTRIBUTES
5.1 OVERVIEW 5-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2 ACCESSING THE OCTEL PC/CDR SYSTEM MENU 5-1. . . . . . . . . . . . . . .
5.3 CONFIGURING OCTEL PC/CDR PARAMETERS AND SYSTEM ATTRIBUTES 5-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4 TESTING THE DIRECT CONNECTION BETWEEN THE PC AND THE SERVER USING SMT EMULATION 5-17. . . . . . . . . . . . . . . .
6: CARBON COPY PLUS PROCEDURES
6.1 OVERVIEW 6-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2 CONFIGURING CARBON COPY PLUS PARAMETERS 6-1. . . . . . . . . . . . .
6.3 CHANGING CARBON COPY PLUS PARAMETERS 6-6. . . . . . . . . . . . . . . . .
6.4 USING CARBON COPY PLUS 6-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.5 DISABLING CARBON COPY PLUS 6-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter Page
C O N T E N T S
ixEdition 2Octel PC/CDR
7: PROCESSING METHODS
7.1 OVERVIEW 7-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2 PREPARING TO PROCESS DATA 7-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.3 USING MANUAL PROCESSING 7-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.4 USING AUTOMATIC PROCESSING 7-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.5 USING SCHEDULED AUTOMATIC PROCESSING 7-16. . . . . . . . . . . . . . . .
7.6 USING THE SERVICE-LEVEL DOWNLOAD 7-36. . . . . . . . . . . . . . . . . . . . . .
8: UTILITIES
8.1 OVERVIEW 8-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.2 DISPLAYING THE STATUS OF THE DISK 8-2. . . . . . . . . . . . . . . . . . . . . . . .
8.3 DISPLAYING OCTEL PC/CDR FILES 8-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4 VIEWING AND PRINTING OCTEL PC/CDR FILES 8-4. . . . . . . . . . . . . . . .
8.5 BACKING UP OCTEL PC/CDR FILES 8-10. . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.6 ERASING OCTEL PC/CDR FILES 8-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.7 RESTORING OCTEL PC/CDR FILES 8-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.8 USING SERVICE UTILITIES 8-18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.9 USING THE CHKREV UTILITY 8-36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9: OUTPUT FILE DESCRIPTIONS
9.1 OVERVIEW 9-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.2 CALLER-MENU OUTPUT (CMO) FILES 9-2. . . . . . . . . . . . . . . . . . . . . . . . . . .
9.3 DISK-USAGE OUTPUT (DUO) FILES 9-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.4 FAX OUTPUT (FXO) FILES 9-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.5 FORMS OUTPUT (FDO) FILES 9-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter Page
C O N T E N T S
x Edition 2 Octel PC/CDR
9.6 INDIVIDUAL-PORT-STATISTICS OUTPUT (PSO) FILES 9-10. . . . . . . . . . .
9.7 MESSAGE-DETAIL OUTPUT (MDO) FILES 9-14. . . . . . . . . . . . . . . . . . . . . . .
9.8 NAMENET OUTPUT (NNO) FILES 9-17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.9 PROFILE-CHANGE-DETAILS OUTPUT (PRO) FILES 9-19. . . . . . . . . . . . . .
9.10 SESSION-DETAIL OUTPUT (SDO) FILES 9-21. . . . . . . . . . . . . . . . . . . . . . . . .
9.11 UNSUCCESSFUL-TRANSFER OUTPUT (UTO) FILES 9-24. . . . . . . . . . . . .
10: DTMF OCTELFORMS
10.1 OVERVIEW 10-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.2 CONFIGURING THE SERVER AND OCTEL PC/CDR FOR DTMF OCTELFORMS DATA COLLECTION 10-1. . . . . . . . . . . . . . . . . . . . . . .
10.3 ESTIMATING CDR BUFFER CAPACITY 10-2. . . . . . . . . . . . . . . . . . . . . . . . . .
10.4 ESTIMATING DOWNLOAD TIME AND PC DISK SPACE 10-6. . . . . . . . . .
10.5 PROCESSING DTMF OCTELFORMS DATA 10-6. . . . . . . . . . . . . . . . . . . . . . .
11: SERVICE INFORMATION FOR TRAINEDTECHNICIANS ONLY
11.1 OVERVIEW 11-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.2 IDENTIFYING THE SERVER CHANNEL 11-3. . . . . . . . . . . . . . . . . . . . . . . . . .
11.3 ESTABLISHING THE SERVER CHANNEL 11-4. . . . . . . . . . . . . . . . . . . . . . . .
11.4 CONNECTING THE CABLES, AND COMPLETING MENU 6.3 CONFIGURATION 11-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.5 VERIFYING MENU 6.3 CHANGES 11-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.6 ESTABLISHING OCTEL PC/CDR ATTRIBUTES FOR COMMUNICATION WITH SERVER 11-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.7 CHECKING SERVER-MODEM CONFIGURATION 11-6. . . . . . . . . . . . . . . . .
Chapter Page
C O N T E N T S
xiEdition 2Octel PC/CDR
APPENDIXES
A: OUTPUT FILE STRUCTURES A-1. . . . . . . . . . . . . . . . . . . . . . . . . . .
B: CDR EVENT DESCRIPTIONS B-1. . . . . . . . . . . . . . . . . . . . . . . . . .
C: CDR EVENT BYTE SIZES BY RECORD GROUP C-1. . . . . . .
D: SUBDIRECTORY FILES D-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
E: TRANSMISSION MESSAGES E-1. . . . . . . . . . . . . . . . . . . . . . . . . . .
F: SCHEDULE-LOG-FILE ENTRIES F-1. . . . . . . . . . . . . . . . . . . . . . . .
G: OCTEL PC/CDR TROUBLESHOOTING FORM G-1. . . . . . . . .
ADDENDA Add-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GLOSSARY Glossary-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
INDEX Index-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter Page
O C T E L
P C / C D R
INTRODUCTION
C O N T E N T S
1-iiiEdition 2Octel PC/CDR
CHAPTER 1
1.1 OVERVIEW 1-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 OCTEL PC/CDR COMPATIBILITY 1-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3 PROCESS CHECKLIST 1-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4 KEY TERMS AND DEFINITIONS 1-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5 MENU FLOW 1-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6 OCTEL PC/CDR INTERACTION 1-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.7 CDR BUFFER 1-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.8 ALARMS 1-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.9 COLLECTION FILES 1-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.9.1 BINARY COLLECTION FILE (BCF) 1-12. . . . . . . . . . . . . . . . . . . . . . . .
1.9.2 PROCESSED COLLECTION FILE (PCF) 1-13. . . . . . . . . . . . . . . . . . .
1.9.3 COLLATED DAY FILE (CDF) 1-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.9.4 PENDING-STATE FILE (PSF) 1-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.9.4.1 The COLLATE.PSF File and Dated Pending-State Files 1-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.9.4.2 The COMPRSP.PSF File 1-15. . . . . . . . . . . . . . . . . . . . . . . . .
1.9.5 LOG FILES 1-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.9.5.1 CDR System Log Files (Dated Log Files) 1-15. . . . . . . .
1.9.5.2 Schedule Log File 1-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.9.6 OUTPUT FILES 1-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Section Page
C O N T E N T S
1-iv Edition 2 Octel PC/CDR
TABLESTable 1-1. Octel PC/CDR Server Software Compatibility 1-2. . . . . . . . . . . . .
Table 1-2. Key Term Definitions 1-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FIGURESFigure 1-1. Example of Call, Event, and Session Relationship 1-6. . . . . . . .
Figure 1-2. Menu Flow of the Octel PC/CDR Main Menu, When Accessed by Typing cdr 1-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 1-3. Menu Flow of the Octel PC/CDR System Menu, WhenAccessed by Typing the CDR System Name 1-8. . . . . . . . . . . . . .
Figure 1-4. Octel PC/CDR Processing Sequence 1-11. . . . . . . . . . . . . . . . . . . . .
Page
C H A P T E R 1
Octel PC/CDR Edition 2 1-1
INTRODUCTION
1.1 OVERVIEW
The Octel Call Detail Records� software package (Octel PC/CDR�) is a datacollection and processing system that provides detailed records of activity on theOctel Overture� 250 and 350 message servers and the Branch�, Branch XP�,Aspen�, Maxum SE�, Maxum�, and Octel XC1000� voice processors. OctelPC/CDR is an optional software package available for new servers,a or it can beadded to an existing server.
CDR data is collected in the call detail records (CDR) buffer on the server. Usingthe PCb containing the Octel PC/CDR software, the system manager requeststhat the Octel PC/CDR software download the CDR data to the PC, collate thedata, and then sort it into output files that can be viewed and printed throughthe Octel PC/CDR File Utilities menu. The system manager can then import theoutput files to an application program for further processing.
CDR data from Octel servers differs from the call detail record data provided by aprivate branch exchange (PBX) or central office switch. Data from the CDRbuffer in the server provides details about calls as they take place on the server.Each time a significant action occurs during a call, the server records an eventin the CDR buffer. CDR data is based on the series of events occurring from thetime a server port goes off-hook to receive a call to when the port goes backon-hook when the call is complete. This data includes events for entering amailbox, conducting a password test, beginning an outcall, or transferring toanother mailbox or to a telephone number. Data is also collected for messagewaiting and server events unrelated to the status of the ports.
System managers can use CDR data for the following:
� Billing users for server resources
� Administrative planning
� Providing an audit trail for caller activity and usage patterns
� Recording valuable information necessary for future server planning andengineering
� Troubleshooting
a Unless noted otherwise, the term server in this manual refers collectively to the Octel Overture250 and 350 message servers and the Aspen, Branch, Branch XP, Maxum SE, Maxum, andOctel XC1000 voice processors.
b The terms PC and CDR PC are used interchangeably throughout this document to refer to thePC on which the Octel PC/CDR software is installed.
INTRODUCTION
1-2 Edition 2 Octel PC/CDR
Octel PC/CDR data downloading, processing, and storage requirements varygreatly, based on server traffic and applications. To avoid losing data, the CDRbuffer storage space on the server must be monitored daily until a fill-pattern hasbeen established. Downloads must then be performed regularly so the CDR bufferdoes not become full. (Refer to Chapter 2 for details about the CDR buffer.)
The relationship between Octel PC/CDR and the optional DTMF OctelForms�application package is explained in Chapter 10. Chapter 10 also describesspecial buffer sizing and downloading considerations required for DTMFOctelForms.
1.2 OCTEL PC/CDR COMPATIBILITY
Octel PC/CDR Release 2.3 software supports message server software at OctelAria�1.2. It also supports Aspen software Releases 1.X and newer. However, onlya subset of Octel PC/CDR Release 2.3 events is available from server softwareolder than Aria 1.2. In general, the older the server software release, the fewer theavailable events. Entries in the appendixes are footnoted with the applicableserver software release if the entries are not applicable to all releases.
Table 1-1 shows the compatibility of Octel PC/CDR software with server softwarereleases. An X in the field signifies compatibility.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table 1-1. Octel PC/CDR and Server Software Compatibility.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
OctelPC/CDR
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Compatibility at Server Software Releases
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
OctelPC/CDRSoftwareRelease
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Aspen1.0X–1.3X
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Aspen1.5X
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Aspen2.Xand3.X
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Aspen4.0
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Aspen4.1X
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Aspen5.0*
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Aria 1.0and
Aria 1.1
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Aria 1.2
ÁÁÁÁÁÁÁÁÁÁ1.3 or 1.4
ÁÁÁÁÁÁÁÁX
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ1.5ÁÁÁÁÁÁÁÁX
ÁÁÁÁÁÁÁÁX
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ2.0ÁÁÁÁÁÁÁÁX
ÁÁÁÁÁÁÁÁX
ÁÁÁÁÁÁÁÁX
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
2.1ÁÁÁÁÁÁÁÁÁÁÁÁ
XÁÁÁÁÁÁÁÁÁÁÁÁ
XÁÁÁÁÁÁÁÁÁÁÁÁ
XÁÁÁÁÁÁÁÁÁÁÁÁ
XÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
2.2ÁÁÁÁÁÁÁÁÁÁÁÁ
XÁÁÁÁÁÁÁÁÁÁÁÁ
XÁÁÁÁÁÁÁÁÁÁÁÁ
XÁÁÁÁÁÁÁÁÁÁÁÁ
XÁÁÁÁÁÁÁÁÁÁÁÁ
XÁÁÁÁÁÁÁÁÁÁÁÁ
XÁÁÁÁÁÁÁÁÁÁÁÁ
XÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
2.3ÁÁÁÁÁÁÁÁÁÁÁÁ
XÁÁÁÁÁÁÁÁÁÁÁÁ
XÁÁÁÁÁÁÁÁÁÁÁÁ
XÁÁÁÁÁÁÁÁÁÁÁÁ
XÁÁÁÁÁÁÁÁÁÁÁÁ
XÁÁÁÁÁÁÁÁÁÁÁÁ
XÁÁÁÁÁÁÁÁÁÁÁÁ
XÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
X
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
* Octel XC1000 only.
SECTION 1.1 – 1.2
INTRODUCTION
Octel PC/CDR Edition 2 1-3
1.3 PROCESS CHECKLIST
The following steps are required for the installation and configuration of theOctel PC/CDR software and the processing of CDR data. Complete each step,referring to the sections noted for details.
Step ActionLocation ofInstructions
1. Verify that the Call Detail Recording feature is enabled inthe server by checking system manager menu 13.7.
Section 2.4.1
2. Select the call detail records to be collected by the server. Section 2.4.2
3. Become familiar with the following:
� The CDR buffer
� Octel PC/CDR collection files
� Processing times and PC sizing tables
Chapter 2
Section 1.9
Section 2.3
4. Install the Octel PC/CDR software package on the PC. Section 3.2
5. Create Octel PC/CDR system data subdirectories, usingMKCDRSYS.
Section 3.3
6. Configure Octel PC/CDR parameters and system attrib-utes for each CDR system created with the MKCDRSYSutility.
Section 5.3
7. Connect the server to the PC that contains the Octel PC/CDR software.
Chapters 4and 11
8. Test the direct connection from the PC to the server (alsoincludes SMT emulation instructions).
Section 5.4
9. Configure the Carbon Copy PLUS software. Section 6.2
10. Choose the downloading method and process the CDRdata.
Chapter 7
Manual
a. Perform manual download.b. Collate the binary collection files.c. Generate output files.
Section 7.3
Automatic
a. Select output files to be generated.b. Select blocks to be downloaded.c. Perform automatic download (includes output-file
generation).
Section 7.4
Scheduled automatic
a. Create automatic-processing schedules.b. Start the automatic-scheduler timer (includes
download and output file generation).
Section 7.5
SECTION 1.3
INTRODUCTION
1-4 Edition 2 Octel PC/CDR
StepLocation ofInstructions
Action
11. Print or view the output files, and interpret them. Section 8.4,Chapter 9, andAppendix A
12. Regularly back up Octel PC/CDR files, and then deletethe files from the PC hard drive to conserve space.
Sections 8.5 and8.6
13. If necessary, import output files into an application program to sort data and generate reports.
Pertinentapplicationmanual
14. Run Carbon Copy PLUS software for system maintenancewhen directed by an Octel or distributor service representative.
Section 6.4
15. Disable the Carbon Copy PLUS software when finished. Section 6.5
1.4 KEY TERMS AND DEFINITIONS
Key terms used in this manual are defined in Table 1-2. Refer to the Glossary foradditional definitions.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table 1-2. Key Terms and Definitions.ÁÁÁÁÁÁÁÁÁÁÁÁ
Key TermÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
DefinitionÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AspenÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
(1) One type of server in the Octel product line. (2) Used to identify serversoftware releases that were in use before Aria 1.0.ÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Block
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
A storage section within the CDR buffer that contains events. Blocks ofevents are downloaded to a PC for processing. A block can hold approxi-mately 80 to 140 events.ÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Call
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
A series of events beginning when a server port goes off-hook to receivean incoming call or to initiate an outgoing call. A call ends when the callis completed and the port goes on-hook.ÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CDR buffer
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
The storage space set aside on the server to collect CDR data. Also calledthe buffer.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CDR systemÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Refers to the system name chosen to designate a particular server thatdownloads CDR data to the CDR PC (refer to section 3.3).
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CollatingÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
The process of arranging CDR data in order.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Event
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
An activity on the server that could be of interest to the system managersuch as call activity, network activity, and specific server information.Server information includes date and time set (DTS) and initial programload (IPL) information. Call activity events include entering a mailbox,conducting a password test, going off-hook or on-hook for a specific port,beginning an outcall, and transferring to another mailbox or telephonenumber. Events are described in Appendix B.
SECTION 1.4
INTRODUCTION
Octel PC/CDR Edition 2 1-5
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table 1-2. Key Terms and Definitions (Concluded).
ÁÁÁÁÁÁÁÁÁÁÁÁ
Key Term ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
DefinitionÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
File formatÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
References to file format can mean different things, depending on thecontext in which it is used. Refer to the Glossary for definitions of thedifferent uses of file format in the Octel PC/CDR software.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
File nameÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
The name given to a particular file to be used by DOS. The naming for-mat allows up to eight alphanumeric characters, plus three alphanumer-ic characters for an extension. The first eight characters are separatedfrom the extension with a period; combined, they form the file name.Although file names can be typed as all upper- or lower-case characters(DOS is not case-dependent), file names in this manual are shown in upper- and lower-case characters. Refer to section 1.9 and Chapter 9 forfile-naming conventions used in Octel PC/CDR.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Output filesÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
The categories into which Octel PC/CDR sorts and files the CDR dataafter it has been downloaded to a PC and collated.ÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Server
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Unless noted otherwise, in this manual the term server refers collectivelyto the Octel Overture 250 and 350 message servers and the Branch,Branch XP, Aspen, Maxum SE, Maxum, and Octel XC1000 voice processors.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
SessionÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
The period of time between a caller entering a mailbox and exiting thesame mailbox in telephone-answering or voice-messaging mode. Eachmessage transmitted or received in a network call is also a session. Because a single call can pass through multiple mailboxes, a call canconsist of one or more sessions. For example, multiple mailboxes are entered and exited with Enhanced Call Processing� (ECP) applications(also called single-digit menus) or when a caller uses the restart com-mand within a mailbox. A special session can also include setup, setdate and time (DTS), and initial program load (IPL). Figure 1-1 shows therelationship among events, sessions, and a call.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Systemattributes
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
The parameters that apply to each server from which the PC downloadsCDR data. In the Octel PC/CDR software package, these attributes in-clude necessary communications settings for the connection between thePC and each server. These attributes also define the output files createdwith the manual- and automatic-processing methods and the associatedfile formats.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Systemname
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
The name chosen to designate a particular server. It is used by theMKCDRSYS command (on the PC) to create the directory that stores thedata from that particular server. Type the command cdrhelp at the DOSprompt to list all valid CDR system names.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
VPMODÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
The name used to represent the server in older versions of Octel PC/CDRsoftware and in some Release 2.3 transmission messages.
SECTION 1.4
INTRODUCTION
1-6 Edition 2 Octel PC/CDR
EVENT
EVENT EVENT
SESSION
SESSION SESSION
CALL
Figure 1-1. Example of Call, Event,and Session Relationship.
1.5 MENU FLOW
Figure 1-2 and Figure 1-3 show the Octel PC/CDR menu flow. Figure 1-2 showsthe initial submenus and the automatic scheduler menus displayed after cdr istyped at the DOS prompt to access the Octel PC/CDR software.
Figure 1-3 shows the levels of submenus entered after the CDR system name (as created in section 3.3) is typed at the DOS prompt or selected through themenus shown in Figure 1-3. In most cases, options that do not lead to furtherscreens are not shown. The corresponding figures are referenced at the bottomof each menu box. The Octel PC/CDR System Menu screen is shaded to showthat it is the same screen in both Figure 1-2 and Figure 1-3.
SECTION 1.4 – 1.5
INTRODUCTION
Octel PC/CDR Edition 2 1-7
Octel PC/CDRMain Menu,
Rev. 2.3
CDR System SelectionMenu
Option 1
(Figure 7-12)
Option 2
Octel PC/CDRSystem Menu,
(Figure 5-2)
Rev 2.3
The menu flowcontinues with
Figure 1-3.
Octel PC/CDRAutomatic Schedule
(Figure 7-13)
Menu
Update AutomaticProcessing Schedules
Option 1
(Figure 7-14)
Processing Schedule
Option 2
(Figure 7-17)
Option 3
Update AutomaticScheduler Log File
Option 4
(Figure 7-18)
Octel PC/CDR Octel PC/CDR Enter New Octel PC/CDR
AutomaticOctel PC/CDR
Options 1 and 2
(Figure 7-15)
Option 4
(Figure 7-16)
Schedule Editor Menu
AutomaticOctel PC/CDR
Schedule 1
Schedule Password
Figure 1-2. Menu Flow of the Octel PC/CDR Main Menu,When Accessed by Typing cdr.
SECTION 1.5
INTRODUCTION
1-8 Edition 2 Octel PC/CDR
Oct
el P
C/C
DR
Sys
tem
Men
u,R
ev 2
.3
Sys
tem
Attr
ibut
es
Mod
ify A
utom
atic
Out
put F
ile G
ener
atio
nM
odify
Out
put F
ileF
orm
at T
ypes
Mod
ify P
CC
omm
unic
atio
nsP
aram
eter
s
Oct
el s
erve
rTy
pe S
elec
tion
Sys
tem
Pas
swor
dS
ettin
g
Ses
sion
Det
ail
Out
put F
ile T
ype
Man
ual O
ctel
PC
/CD
RP
roce
ssin
g M
enu
Opt
ion
1O
ptio
n 2
Opt
ion
6O
ptio
n 5
Opt
ion
7
Opt
ion
1O
ptio
n 9
Opt
ion
11
Beg
in C
olla
teP
roce
ssin
gF
ile D
ownl
oad
Set
tings
Out
put F
ileG
ener
atio
n M
enu
Opt
ion
1O
ptio
n 2
Opt
ion
3
Beg
in S
essi
on
Opt
ion
1
(Fig
ure
5-2)
(Fig
ure
5-3)
(Fig
ure
5-5)
(Fig
ure
5-4)
(Fig
ure
5-7)
(Fig
ure
7-5)
(Fig
ure
7-6)
(Fig
ure
7-7)
(Fig
ure
7-8)
(Fig
ure
7–10
)(F
igur
e 5-
6)
Oct
el P
C/C
DR
Oct
el P
C/C
DR
Oct
el P
C/C
DR
Men
u
Det
ail P
roce
ssin
g
Opt
ions
3, 4
, and
5
(ref
er to
par
t b)
**
*S
cree
ns fo
r op
tions
2th
roug
h 8
and
optio
n 10
ar
e si
mila
r.
*S
cree
ns fo
r op
tions
2th
roug
h 8
and
optio
n 10
ar
e si
mila
r.
Oct
el P
C/C
DR
(a) O
pti
on 1
an
d O
pti
on 2
fro
m t
he
Oct
el P
C/C
DR
Sys
tem
Men
u.
Fig
ure
1-3
. M
enu
Flo
w o
f th
e O
ctel
PC
/C
DR
Sys
tem
Men
u,
Wh
en A
cces
sed b
y Typ
ing
the
CD
R S
yste
m N
am
e.
Figure 1-3
SECTION 1.5
INTRODUCTION
Octel PC/CDR Edition 2 1-9
Oct
el P
C/C
DR
Sys
tem
Men
u,
Vie
w
Opt
ion
3
File
Util
ities
Men
u
(Fig
ure
8-2)
Opt
ion
4
Dis
play
Opt
ion
2
Dis
k S
tatu
s
Opt
ion
1
File
Bac
kup
Men
u
Opt
ion
4
File
Era
se M
enu
Opt
ion
5
File
Res
tore
Men
u
Opt
ion
6
Ser
vice
Util
ities
Men
u
Opt
ion
7
Prin
t S
elec
tion
Par
amet
ers
Opt
ion
3
File
Sel
ectio
n
Opt
ion
1
Par
amet
ers
Sel
ect a
Pen
ding
Sta
te F
ile
Opt
ion
4
Sel
ect a
Bin
ary
Col
lect
ion
File
Opt
ion
2
Sea
rch
Col
late
d D
ayF
ile U
tility
Men
u
Opt
ion
1
Sel
ect a
Bin
ary
Col
lect
ion
File
Opt
ion
3
CO
PY
BC
F O
ptio
nsD
UM
PB
CF
Opt
ions
Sel
ect a
Col
late
dD
ay F
ile
Opt
ion
I
Opt
ion
A
Ent
er D
OS
Com
man
d:
Opt
ion
D
CD
F S
earc
h U
tility
Men
uO
utpu
t Sel
ectio
n
Opt
ion
O
CD
F S
earc
h U
tility
Men
uR
ecor
d D
ispl
ay
Opt
ion
R
CD
F S
earc
h U
tility
Men
uE
ntry
of T
ime
Ran
ges
Opt
ion
T
CD
F S
earc
h U
tility
Men
uE
ntry
of P
ort
Opt
ion
P
CD
F S
earc
h U
tility
Men
uE
ntry
of M
ailb
ox
Opt
ion
B
CD
F S
earc
h U
tility
Men
uE
ntry
of E
vent
Typ
e
Opt
ion
E
CD
F S
earc
h U
tility
Men
uE
ntry
of M
essa
ge ID
s
Opt
ion
M
CD
R S
yste
mS
elec
tion
Men
u
Sel
ectio
nN
umbe
r R
ange
s
Ran
ges
Ran
ges
Oct
el P
C/C
DR
Oct
el P
C/C
DR
Oct
el P
C/C
DR
Oct
el P
C/C
DR
Oct
el P
C/C
DR
Oct
el P
C/C
DR
Oct
el P
C/C
DR
Oct
el P
C/C
DR
(Fig
ure
8-5)
(Fig
ure
5-2)
(Fig
ure
8-10
)(F
igur
e 8-
11)
(Fig
ure
8-12
)
(Fig
ure
8-7)
(Fig
ure
8-9)
(Fig
ure
8-14
)(F
igur
e 8-
14)
(Fig
ure
8-19
)
(Fig
ure
8-16
)(F
igur
e 8-
15)
(Fig
ure
8-13
)
F
iles
O
utpu
t FIle
s
Opt
ion
5O
ptio
n 3
Oct
el P
C/C
DR
Mai
n M
enu
Link
s to
VP
MO
D
Dis
play
sO
utpu
t File
Opt
ion
2
Aut
omat
ic
Pro
cess
ing
(b) O
pti
ons
3, 4, an
d 5
fro
m t
he
Oct
el P
C/C
DR
Sys
tem
Men
u.
Fig
ure
1-3
. M
enu
Flo
w o
f th
e O
ctel
PC
/C
DR
Sys
tem
Men
u,
Wh
en A
cces
sed b
y Typ
ing
the
CD
R S
yste
m N
am
e (C
oncl
uded
).
Rev
2.3
(Fig
ure
8-3)
(Fig
ure
8-4)
SECTION 1.5
INTRODUCTION
1-10 Edition 2 Octel PC/CDR
1.6 OCTEL PC/CDR INTERACTION
Two major components are necessary for Octel PC/CDR to collect, retrieve, andmanipulate CDR data:
� The data-collection component in the server (the CDR buffer)
� The Octel PC/CDR data-retrieval and output-file-generation component inthe PC
Figure 1-4 and the following steps show how these components are related. Thecircled numbers in the figure relate to the following steps:
Step Description
1. Event-related activity occurs on the server and is recorded in the CDRbuffer. The CDR buffer is located on the server drives.
2. Using the download process, the system manager periodically downloadsraw CDR event data from the CDR buffer to the hard drive on the CDR PC.
3. The raw event data downloaded to the PC is formed into binary collectionfiles (BCFs).
4. Using the collate process, BCFs are collated to create collated day files(CDFs).
5. Using the generate-output-file option, CDFs are processed into the outputfiles selected by the system manager. (Output files are shown in Figure 1-4in the order in which they are created.)
6. If desired, output files can be imported into application programs for fur-ther processing.
SECTION 1.6
INTRODUCTION
Octel PC/CDR Edition 2 1-11
Binary Collection
Files (BCF)
Session-DetailOutput Files
(SDO)
Message-DetailOutput Files
(MDO)
Individual-Port-Statistics Output
Files (PSO)
Unsuccessful-Transfer Output
Files (UTO)
Octel PC/CDR Files
Application Program Application Program Application Program Application Program
Forms-OutputFile (FDO)
Application Program
Collated Day Files
(CDF)
CDRBUFFER
SERVER
Raw Data
Collate
1
2
3
4
5
6 6 6 6 6
Disk-UsageOutput Files
(DUO)
Caller-MenuOutput Files
(CMO)
Profile-Change-Details OutputFiles (PRO)
Application Program Application Program Application Program Application Program
6 6 6 6
NameNetOutput Files
(NNO)
Application Program
6
Fax OutputFiles (FXO)
Downloadto CDR PC
CDR PC
Figure 1-4. Octel PC/CDR Processing Sequence.
SECTION 1.6
INTRODUCTION
1-12 Edition 2 Octel PC/CDR
1.7 CDR BUFFER
As calls occur on the server, selected CDR events are recorded in the CDR bufferon the server drives. CDR events are selected for collection in system-managerterminal (SMT) menu 16.1.4. Refer to Chapter 2 for information about the CDRbuffer and about selecting events for collection.
1.8 ALARMS
Alarms are generated if blocks of CDR events in the CDR buffer that have not yetbeen downloaded to the CDR PC are about to be overwritten. A non-service-affecting (NSA) alarm is triggered when the CDR buffer has only 20% of availablespace left before unretrieved data will be overwritten. A service-affecting alarm(SA) is triggered when the buffer has only 10% of available space left beforeunretrieved data will be overwritten. These alarms are recorded in SMT menu13.8 and on the alarm panel (if the server is equipped with an alarm panel).Refer to the system manager manual for your server-software release foradditional information about server alarms.
1.9 COLLECTION FILES
As each step of the Octel PC/CDR data process takes place, a different type ofcollection file is created. This section defines the Octel PC/CDR collection filesand describes the information captured by each one. Each collection file name isunique, based on a special naming convention. Each CDR system subdirectory(created with the MKCDRSYS command) has its own set of subdirectories tostore collection files on the CDR PC hard drive. (Refer to section 3.3 for detailsabout CDR system subdirectories.)
1.9.1 BINARY COLLECTION FILE (BCF)
When blocks of CDR events are downloaded to the PC from the CDR buffer, theyare stored as raw data files with the extension of .BCF. These files are stored onthe PC hard drive in the BCF subdirectory for the server (CDR system) fromwhich they were downloaded. Binary collection files (BCFs) are then collated intocollated day files (CDFs). Once the BCFs are collated into CDFs, the BCFs can beautomatically deleted from the hard drive to conserve space. If not configured forautomatic deletion, a processed BCF is collated and then renamed with the fileextension of .PCF (processed collection file), and the PCF is stored in the BCFsubdirectory.
For troubleshooting, system managers and service representatives can viewBCFs using the Service Utilities menu (section 8.8.1), or they can isolate andcopy a section of a BCF for a closer review (section 8.8.2). Because BCFs areuseful for troubleshooting and to conserve disk space, Octel recommends thatyou regularly back up and archive collated BCFs (PCFs) before you delete them(refer to sections 5.3.2, 5.3.3, and 8.6).
SECTION 1.7 – 1.9
INTRODUCTION
Octel PC/CDR Edition 2 1-13
BCFs collated more than once could add duplicate data toyour database, causing data inconsistencies. Only attemptto collate a BCF more than once if advised to do so by yourservice representative.
Caution!
Unless you are advised to do so by your service representative, do not attempt tocollate a BCF more than once. Duplicate data is added to the database if a BCFis collated more than once, causing database inconsistencies.
The BCF name contains the encoded date on which the download occurred.Because of this naming convention, the PC date and time must be accurate.
BCFs are named with the following convention:
Ayymmddi.BCF
where
A represents a file created from one of the first 26 downloads that occurredon the same day. Files created from the 27th through 52nd downloads onthe same day are named Byymmddi.BCF; files created from the 53rd through78th downloads are named Cyymmddi.BCF, and so on.
yymmdd represents the year (yy), month (mm), and day (dd) the downloadoccurred, based on the PC clock date.
i represents a particular file if more than one download is performed on thesame date. The i equals a sequential alphabetic character. For example,A960508A.BCF is the file created for the first download on May 8, 1996.Each download on the same date creates a file name with a different lastletter before the file-name extension (represented by i). For example,A960508B.BCF is the file created from the second download on May 8, 1996.After 26 downloads on the same day, the initial letter (A) in the file namechanges, and the last letter starts over with A. For example, the file createdfrom the 27th download is named B960508A.BCF.
.BCF is the file-name extension given to all binary collection files.
The maximum number of BCFs that can be downloaded per day is 676 (26 filestimes 26 letters).
1.9.2 PROCESSED COLLECTION FILE (PCF)
When a BCF is collated into a CDF, if the BCF was not automatically deleted(refer to section 5.3.2), the BCF is renamed with the extension of .PCF, indicatingthat it is a processed collection file (PCF). To conserve PC disk-storage space andpreserve data for future use, you should regularly back up and then delete PCFs.
Unless you are advised to do so by your service representative, do not attempt tocollate a PCF. Duplicate data is added to the database if a BCF (PCF) is collatedmore than once, causing database inconsistencies.
PCF names are based on the same naming convention as BCFs, except that thefile-name extension is .PCF. PCFs are stored in the BCF subdirectory.
SECTION 1.9
INTRODUCTION
1-14 Edition 2 Octel PC/CDR
1.9.3 COLLATED DAY FILE (CDF)
When BCFs are collated, data is sorted by call, chronologically by completiontime, into collated day files (CDFs). This process creates or appends alreadyexisting CDFs with the call events contained in the BCF. One CDF is created forevery date for which call events exist in the BCF. Therefore, several CDFs can beproduced from a single BCF, depending on how often data is downloaded fromthe server.
CDFs are manually requested unless automatic downloading is used or sched-uled. (Refer to Chapter 7 for information about processing methods.)
CDFs are named with the following convention:
CDyymmdd.CDF
where
CD represents a collated day file.
yymmdd represents year (yy), month (mm), and day (dd) that the callstarted, based on the server clock date.
.CDF is the file-name extension given to collated day files.
CDFs are stored in the CDF subdirectory. Unprocessed CDFs are used by Octeland distributor service representatives for troubleshooting. For this purpose,CDFs can be sorted, viewed, and printed through the Service Utilities menu(section 8.8.1). Appendix B describes the CDR events found in CDFs.
Establish a schedule to back up and then delete CDFs periodically to conservePC disk-storage space.
1.9.4 PENDING-STATE FILE (PSF)
Three types of pending-state files are created by the Octel PC/CDR application:
� The COLLATE.PSF file
� Dated pending-state files
� The COMPRSP.PSF file
1.9.4.1 The COLLATE.PSF File and Dated Pending-State Files. TheCOLLATE.PSF holds all events for calls that are in process when a downloadoccurs and a BCF is created. These events are identified when the BCF iscollated. Dated PSFs are created when the events from COLLATE.PSF are addedto the CDF. Events in the COLLATE.PSF are combined with the events in theBCF from the next download, at the time the BCF is collated, so that the calls inprocess are matched with their completing entries. For example,
1. The COLLATE.PSF file is created when the file A960630A.BCF is collated.Calls in process at the time of the download that created A960630A.BCF areplaced in the COLLATE.PSF file.
2. When A960630B.BCF is collated, the events from COLLATE.PSF are added tothe CDF(s) created from A960630B.BCF to complete calls that were inprocess when the data in A960630A.BCF was downloaded.
SECTION 1.9
INTRODUCTION
Octel PC/CDR Edition 2 1-15
3. The COLLATE.PSF file is copied to a file with the name A960630B.PSF. Thisfile is given the same name as the BCF to which the data was added (in step2), except the file-name extension is .PSF.
4. The COLLATE.PSF file is then overwritten by a new COLLATE.PSF containingevents from calls that were in process when A960630B.BCF was downloaded.
The COLLATE.PSF file is stored in the SYS subdirectory and dated PSFs arestored in the BCF subdirectory. Establish a schedule to back up and then deletethe dated PSFs periodically to conserve PC disk-storage space. Do not delete theCOLLATE.PSF file.
1.9.4.2 The COMPRSP.PSF File. When an individual-port-statistics output(PSO) file is generated, the COMPRSP.PSF file is also created.
The COMPRSP.PSF file stores data about calls that were in process from one dayto the next (over midnight), found in the last CDF processed. This data includescall connect time for each port. A COMPRSP.PSF file is created even if no callsare in process from one day to the next.
The next time a PSO file is generated, call connect times from the currentCOMPRSP.PSF file are added to the PSO file to complete the call information. Anew COMPRSP.PSF file is created after the last CDF is processed, overwriting theexisting COMPRSP.PSF file.
The COMPRSP.PSF file is stored in the BCF subdirectory.
1.9.5 LOG FILES
Two types of log files are created by the Octel PC/CDR application:
� CDR system log files (dated log files)
� Schedule log file (SCHEDCDR.LOG)
1.9.5.1 CDR System Log Files (Dated Log Files). A CDR system log file iscreated for each day that any Octel PC/CDR process, such as collate or down-load, is executed. The results of all downloads, collates, system manager sign-onactivity, and any problems are stored in the CDR system log files. These files arestored in the SYS subdirectory.
CDR system log files are named by the date on which the process occurred.These files are named with the following convention:
Lyymmdd.LOG
where
L represents a CDR system log file.
yymmdd represents the year (yy), month (mm), and day (dd) processingoccurred, based on the PC clock date.
LOG is the file-name extension given to a log file.
If more than one download occurs on the same day, the first CDR system log filecreated for that day is appended to the new log. There is only one CDR systemlog file per day, per CDR system. CDR system log files can be viewed or printedthrough the Octel PC/CDR File Utilities Menu (section 8.4), or they can beexamined to show processing results for a particular day, by using the DOScommands type or print (executed from the CDR system SYS subdirectory) or a text editor.
SECTION 1.9
INTRODUCTION
1-16 Edition 2 Octel PC/CDR
Establish a schedule to back up and then delete CDR system log files periodi-cally to conserve PC disk-storage space.
1.9.5.2 Schedule Log File. An additional log file called SCHEDCDR.LOG,stored in the OCTELCDR\LOG subdirectory, records processing actionsexecuted by the automatic scheduler. Refer to section 7.5.4 for additionalinformation about this file.
1.9.6 OUTPUT FILES
Events in the CDFs are processed (compressed) into output files based on therecords collected in the CDR buffer (selected in SMT menu 16.1.4, described insection 2.4.2) and the output files selected by the system manager (refer tosection 7.3.3).
The following output files can be generated:
� Caller-menu output (CMO) file
� Disk-usage output (DUO) file
� Fax output (FXO) file
� Forms output (FDO) file (optional)
� Individual-port-statistics output (PSO) file
� Message-detail output (MDO) file
� NameNet output (NNO) file
� Profile-change-details output (PRO) file
� Session-detail output (SDO) file
� Unsuccessful-transfer output (UTO) file
Octel PC/CDR output files can be created in a dBASE III format or as ASCII files.The system manager can then use these files for specific purposes. For example,session-detail and individual-port-statistics output files can be created in adBASE III format and imported into a dBASE III billing application program, orthe system manager can use the output files for report generation.
Output files can be viewed or printed using the Octel PC/CDR File UtilitiesMenu (section 8.4). Output files are described in detail in Chapter 9. Appendix Ashows the file structure and description of output file fields and records.
SECTION 1.9
O C T E L
P C / C D R
DATA-COLLECTIONPREPARATION
C O N T E N T S
2-iiiEdition 2Octel PC/CDR
CHAPTER 2
2.1 OVERVIEW 2-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2 UNDERSTANDING THE CDR BUFFER 2-1. . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.1 HOW THE CDR BUFFER IS SIZED 2-2. . . . . . . . . . . . . . . . . . . . . . .
2.2.2 HOW THE CDR BUFFER RECORDS EVENTS 2-3. . . . . . . . . . . . .
2.2.2.1 CDR Block Characteristics 2-3. . . . . . . . . . . . . . . . . . . . . .
2.2.2.2 CDR Block Numbering and Download Sequence 2-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2.3 HOW TO ESTIMATE CDR BUFFER CAPACITY 2-6. . . . . . . . . . . .
2.2.3.1 Estimating the Number of Blocks Filled 2-7. . . . . . . . .
2.2.3.2 Estimating CDR Buffer Capacity, in Days 2-8. . . . . . .
2.2.3.3 Determining Download Frequency 2-9. . . . . . . . . . . . . . .
2.2.3.4 Checking for Potential CDR Data-Loss Warnings 2-10. . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3 SIZING THE PC AND DETERMINING PROCESSING TIME 2-10. . . . . . .
2.3.1 ESTIMATING DOWNLOAD TIME AND PC DISK SPACE 2-10. . .
2.3.1.1 Estimating Download Time 2-11. . . . . . . . . . . . . . . . . . . . .
2.3.1.2 Estimating PC Disk Space Requirements 2-13. . . . . . .
2.3.1.3 Confirming Available Disk Space 2-14. . . . . . . . . . . . . . .
2.3.2 ESTIMATING PROCESSING TIME 2-14. . . . . . . . . . . . . . . . . . . . . . . .
2.4 CONFIGURING THE SERVER FOR CDR DATA COLLECTION 2-14. . . .
2.4.1 CONFIRMING THAT THE SOFTWARE FEATURE IS ENABLED 2-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4.2 SELECTING RECORD GROUPS FOR COLLECTION 2-16. . . . . . .
2.4.2.1 Selecting Record Groups for Servers With Software at Aria 1.1, Aria 1.2, or Aspen Release 4.1 2-20. . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4.2.2 Selecting Record Groups for Servers With Software at Aria 1.0 or Aspen Release 1.0X Through 4.0 2-21. . . . . . . . . . . . . . . . . . . . . .
Section Page
C O N T E N T S
2-iv Edition 2 Octel PC/CDR
2.4.3 MONITORING AVAILABLE CDR BUFFER STORAGE SPACE AND CDR BLOCK INFORMATION 2-22. . . . . . . . . . . . . . . .
2.4.4 USING THE RETRIEVE CALL DETAIL RECORDS OPTION 2-23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4.5 RESETTING THE CALL DETAIL RECORDING LOST DATA COUNTER 2-23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TABLESTable 2-1. Example of CDR Buffer Capacity, in Days, for a
Server With Light Voice-Mail Usage and Few Special Applications 2-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2-2. Description of Columns in Table 2-1 2-7. . . . . . . . . . . . . . . . . . . . .
Table 2-3. Example of Approximate Download Time for a Server With Light Voice-Mail Usage 2-11. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2-4. Description of Columns in Table 2-3 2-11. . . . . . . . . . . . . . . . . . . .
Table 2-5. Time (in Seconds) To Download a Kilobyte, byConnection Type and Baud Rate 2-12. . . . . . . . . . . . . . . . . . . . . . . .
Table 2-6. Record Groups for Data Collection 2-17. . . . . . . . . . . . . . . . . . . . . .
Section Page
C O N T E N T S
2-vEdition 2Octel PC/CDR
FIGURESFigure 2-1. 7020-Block CDR Buffer Diagram, First and
Second Pass 2-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 2-2. 7020-Block CDR Buffer Diagram With 2980 Overwritten Blocks 2-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 2-3. 35,000-Block CDR Buffer Diagram With 10,000 Overwritten Blocks 2-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 2-4. First Screen of Menu 13.7, Display of Software Features Installed, for Servers With Software at Aria 1.2 2-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 2-5. Menu 16.1.4, Call Detail Records Collected, for Servers With Software at Aria 1.1, Aria 1.2, or Aspen Release 4.1 2-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 2-6. Menu 16 – Database Access 2-18. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 2-7. Menu 16.1, Manage Call Detail Recording 2-19. . . . . . . . . . . . . .
Figure 2-8. Example of Menu 16.1.4 With Record Groups 2 and 8 Selected 2-19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 2-9. Menu 16.1.1, Call Detail Recording Status 2-23. . . . . . . . . . . . . .
Figure 2-10. Menu 16.1, Showing That the Data Counter Was Cleared 2-24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Page
C H A P T E R 2
Octel PC/CDR Edition 2 2-1
DATA-COLLECTION PREPARATION
2.1 OVERVIEW
Before CDR data can be stored in the CDR buffer on the server, you mustconfigure the server so that the required data can be collected. The datacollected in the CDR buffer is determined by the server features, the serversoftware release, and the record groups selected in system manager terminal(SMT) menu 16.1.4.
Using the guidelines described in this chapter as a point ofreference, regularly monitor the CDR buffers on all serversfor which CDR data is collected to determine how quicklythe buffers fill. Perform downloads based on this pattern toprevent the buffers from being overwritten and to preventdata from being lost.
Caution!
If data is not downloaded regularly from the CDR buffer to the CDR PC (alsocalled the PC), the buffer could become full, causing important data to beoverwritten. Monitor the CDR buffer regularly to determine how quickly thebuffer fills, and then perform downloads accordingly. Before performing adownload, collating binary collection files (BCFs), and generating output files,confirm that there is enough free disk-storage space on the PC to hold the newdata files. If you are using the optional DTMF OctelForms feature, refer toChapter 10 for information about additional CDR buffer and PC storage needs.
The download and collate processes could take a long time. Estimate theamount of time it will take for these processes, and then perform them at a timewhen the PC is not needed for other Octel PC/CDR tasks, such as during theevening or on a weekend.
This chapter explains the following:
� How the CDR buffer works
� How to manage the data stored in the CDR buffer so it is not overwritten
� How to estimate downloading time and storage needs on the PC
� How to prepare the server, the CDR buffer, and the PC to collect and processCDR data
2.2 UNDERSTANDING THE CDR BUFFER
When there is activity in the server, selected events are recorded in blocks ofdata that are stored in the server’s CDR buffer. These events include informationabout call and messaging activity, network activity, and specific server activities,such as date and time set (DTS) and initial program load (IPL).
DATA-COLLECTION PREPARATION
2-2 Edition 2 Octel PC/CDR
2.2.1 HOW THE CDR BUFFER IS SIZED
An Octel or distributor service representative sets the size of the CDR bufferwhen the server is installed or when CDR data collection is required for OctelPC/CDR or another reporting application.
If the server is . . .And the server-software is . . .
Then the CDR buffersize is typically . . .
Octel Overture 250 orOctel Overture 350
Aria 1.0 or newer Up to 35,000 blocks,in increments of 10
Branch, Branch XP, orAspen
At any release 2020 blocks
Maxum SE or Maxum At any release 7020 blocks
Octel XC1000 Aspen Release 3.0or newer
Up to 35,000 blocks,in increments of 10
Octel XC1000 Older than AspenRelease 3.0
7020 blocks
View SMT menu 16.1.1 (described in section 2.4.3) to determine your server’sbuffer size.
Each CDR block is 2048 bytes; therefore,
When the buffer size(in blocks) is . . .
The approximate serversystem-drive storage spaceused (in MB) is . . .
2020 4
7020 14
35,000 72
If CDR data needs to be collected on an already-installed server, reserving thespace for the CDR buffer does not affect existing data and files on the server, aslong as the server’s drives have enough space available for the CDR buffer. Onall servers, the CDR buffer is duplicated on each system drive.
Because the Octel Overture 250, Octel Overture 350, and Octel XC1000 (withsoftware at Aspen Release 3.0 or newer) have permanent storage space up to35,000 blocks allocated for the CDR buffer on the system drives, system-drivestorage space on these servers is not affected by changes in buffer size. Cur-rently, if the CDR buffer is disabled on a Branch, Branch XP, Aspen, Maxum SE,and Maxum at Aspen software Release 1.1X through 1.5X, this buffer-storagespace cannot be reclaimed. If the buffer size for servers at any other softwarelevel must be reduced, contact your local Octel or distributor support office forassistance.
SECTION 2.2
DATA-COLLECTION PREPARATION
Octel PC/CDR Edition 2 2-3
The following information applies only to the Branch, Branch XP, and Aspenservers:
� Data is stored on the first two drives (drives 0 and 1). The CDR buffer utilizesa portion of this storage space, thereby reducing available message space onthe system drives.
� A server with a voice-digitization rate of 25,000 samples per second and aCDR buffer sized at 2020 blocks requires approximately 50 minutes ofstorage space (25 minutes on each drive). If this server is sized for 7020blocks, 85 minutes of storage space are used on each system drive, leavinglittle space for messages (unless high-capacity drives are in use).
The following information applies to Maxum SEs and Maxums at any softwarerelease and to Octel XC1000 servers at a software release older than AspenRelease 3.0:
� When the CDR buffer is configured at 7020 blocks, approximately 85minutes of storage space is used on each system drive for the CDR buffer.
� Because system drives are not used for messages, the storage requirementsfor the CDR buffer do not affect message-storage space on the system drives.
2.2.2 HOW THE CDR BUFFER RECORDS EVENTS
The CDR buffer is a circular buffer; it overwrites older blocks of CDR eventswhen the buffer is full. The more events that occur on your server, the soonerthe buffer becomes full and begins overwriting the older blocks. This sectiondiscusses the characteristics of the CDR buffer, how downloading CDR dataaffects the CDR buffer, and the sequence in which older blocks of data areoverwritten.
2.2.2.1 CDR Block Characteristics. Note the following characteristics ofCDR blocks:
� Depending on the types of events, each block holds approximately 80 to 140events or 2 kilobytes (2048 bytes) of information.
� If a block is nearly full and the next event to be recorded cannot fit into thatblock, the event is recorded at the beginning of the next block. This processis repeated as call events are recorded in the buffer.
� When a partial block is downloaded, the next block begins to fill and thepartially filled block is not filled.
� When CDR blocks are manually or automatically downloaded from the CDRbuffer to the PC hard drive, the contents of these blocks are not erased fromthe buffer. The data is simply copied and transmitted to the PC hard drive.As a result, if something should happen to the recently downloaded CDRdata on the PC, the CDR blocks can be downloaded from the buffer again, asnecessary, until the blocks are overwritten.
SECTION 2.2
DATA-COLLECTION PREPARATION
2-4 Edition 2 Octel PC/CDR
2.2.2.2 CDR Block Numbering and Download Sequence. CDR blocks are numbered internally from 0 through 65,535; then the numbering sequencerestarts with block number 0. When the server first begins recording CDRevents, the events are recorded in block 0. A 2020-block buffer can wrap aroundapproximately 32 times before it fills all 65,535 blocks and begins renumberingwith block 0. A 7020-block buffer can wrap approximately nine times beforerenumbering with 0. A 35,000-block buffer wraps slightly less than twice.Although the CDR buffer contains 65,535 logical blocks, a maximum of 2020,7020, or up to 35,000 blocks (depending on the configuration of the server’sCDR buffer) are filled before the blocks are overwritten and data is lost.Figure 2-1 is an example of a 7020-block buffer showing sequence numberingfor the first two passes.
BLOCK 0
First passSecond pass
BLOCK 14,039
BLOCK 7020
BLOCK 7019
Figure 2-1. 7020-Block CDR BufferDiagram, First and Second Pass.
When all 2020, 7020, or up to 35,000 blocks become full, the oldest recordedblocks (initially beginning with block 0) are overwritten with current event data.If these oldest blocks were not previously downloaded to a PC, their contents arelost. When block 0 is overwritten, it is renumbered with the next sequentialnumber. For a 2020-block buffer, block 0 is renumbered block 2020 after thefirst pass (the first pass fills blocks 0 through 2019); for a 7020-block buffer,block 0 is renumbered 7020 after the first pass, and so on.
The maximum number of blocks that can be retrieved when downloadingdepends on the number of blocks for which the server is configured. Forexample,
If a buffer is configured for 7020 blocks, and block number 10,000 iscurrently being written (filled), all blocks from 2981 (10,000 minus the 7019blocks in the first pass equals 2981) through 10,000 can be retrieved. Anyblocks of data that are numbered at or below 2980 have been permanentlyoverwritten. Figure 2-2 illustrates this example.
SECTION 2.2
DATA-COLLECTION PREPARATION
Octel PC/CDR Edition 2 2-5
BLOCK 0
BLOCK 7019
Permanently overwritten (lost) blocks (0 through 2980)Blocks available for download (2981 through 10,000)
BLOCK 2980
BLOCK 2981BLOCK 10,000
BLOCK 7020
Figure 2-2. 7020-Block CDR Buffer DiagramWith 2980 Overwritten Blocks.
If a buffer is configured for 35,000 blocks and block number 45,000 iscurrently being written (filled), all blocks from 10,001 (45,000 minus the34,999 blocks in the first pass equals 10,001) through 45,000 can beretrieved. Any blocks of data that are numbered at or below 10,000 havebeen permanently overwritten. Figure 2-3 illustrates this example.
BLOCK 0
BLOCK 34,999
Permanently overwritten (lost) blocks (0 through 10,000)Blocks available for download (10,001 through 45,000)
BLOCK 10,000
BLOCK 10,001BLOCK 45,000
BLOCK 35,000
Figure 2-3. 35,000-Block CDR Buffer DiagramWith 10,000 Overwritten Blocks.
SECTION 2.2
DATA-COLLECTION PREPARATION
2-6 Edition 2 Octel PC/CDR
Refer to section 2.4.3 for information about using SMT menu 16.1.1 to find thesequence numbers of the oldest block, the current block being filled, and thefirst block not retrieved. Refer to Chapter 7 for information about downloadingblocks from the CDR buffer.
2.2.3 HOW TO ESTIMATE CDR BUFFER CAPACITY
Server use and applications such as voice mail and Enhanced Call Processing(ECP) (also called single-digit menus) affect the number of CDR blocks that arefilled each day. The record groups selected for collection (described in section2.4.2) also affect how quickly the CDR buffer becomes full. For example,
Table 2-1 shows the buffer capacity, in days, for a server with light voice-mail usage, few special applications, and a buffer configured for 2020, 7020,or 35,000 blocks. Refer to Table 2-2 for a description of the columns inTable 2-1.
Note that a server with many applications and heavy voice-mail usage fillsthe CDR buffer faster than the example shown in Table 2-1.
Using the guidelines in this chapter as a reference, monitorthe CDR buffer regularly to determine how quickly thebuffer fills. Perform downloads based on this pattern toavoid overwriting the buffer and losing data.
Caution!
If you are using the optional DTMF OctelForms feature, refer to Chapter 10 forinformation about additional CDR buffer and PC storage needs.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table 2-1. Example of CDR Buffer Capacity, in Days, for a Server WithLight Voice-Mail Usage and Few Special Applications.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁAverage Calls per
Day
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁAverage CDR Blocks
Filled per Day
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Buffer Capacity, in DaysÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Average Calls perDay
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Average CDR BlocksFilled per Day
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
2020-BlockBuffer
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
7020-BlockBuffer
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
35,000-BlockBuffer
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
2,500ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
134ÁÁÁÁÁÁÁÁÁÁÁÁ
15ÁÁÁÁÁÁÁÁÁÁÁÁ
52ÁÁÁÁÁÁÁÁÁÁÁÁ
261ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
5,000ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
268ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
7ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
26ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
130ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
7,500ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
402ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
5ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
17ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
87
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
10,000 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
537 ÁÁÁÁÁÁÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁ
13 ÁÁÁÁÁÁÁÁÁÁÁÁ
65ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
15,000ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
805ÁÁÁÁÁÁÁÁÁÁÁÁ
2ÁÁÁÁÁÁÁÁÁÁÁÁ
8ÁÁÁÁÁÁÁÁÁÁÁÁ
43ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
20,000ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
1074ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
1ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
6ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
32
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
25,000 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
1342 ÁÁÁÁÁÁÁÁÁÁÁÁ
1 ÁÁÁÁÁÁÁÁÁÁÁÁ
5 ÁÁÁÁÁÁÁÁÁÁÁÁ
26
SECTION 2.2
DATA-COLLECTION PREPARATION
Octel PC/CDR Edition 2 2-7
Table 2-2. Description of Columns in Table 2-1.
Name of Column Description
Average Calls per Day The estimated number of calls processed by the server eachday. These calls include incoming calls, outcalls, networkcalls, message-waiting-notification calls, and fax calls.
Average CDR BlocksFilled per Day
The average number of CDR blocks filled each day, based onthe daily call volume (in the Average Calls per Day column),with an average of 110 bytes per call.
Buffer Capacity, inDays
The number of days’ worth of buffer storage available betweendownloads for servers with 2020-, 7020-, and 35,000-blockbuffers. These values estimate the maximum number of daysthat CDR event data can be accumulated in the CDR bufferbefore the buffer becomes full and event data is overwritten.
2.2.3.1 Estimating the Number of Blocks Filled. If you have a server withlight voice-mail usage and few special applications, estimate the number of CDRblocks filled by your server per day, as follows:
Step Action Result
1. Multiply the average number of callsprocessed by the server each day by110 (the average number of bytes percall).
The answer is the average number ofbytes of CDR buffer storage spacefilled per day.
For example,
10,000 calls x 110 bytes1,100,000 bytes of storage spacefilled
2. Divide the average number of bytesof storage space filled each day (theanswer from step 1) by 2048 (theaverage number of bytes per block).
The answer is the average number ofCDR blocks filled per day.
For example,
1,100,000 bytes = 537 blocks 2048
SECTION 2.2
DATA-COLLECTION PREPARATION
2-8 Edition 2 Octel PC/CDR
2.2.3.2 Estimating CDR Buffer Capacity, in Days. If you have a serverwith light voice-mail usage and few special applications, estimate the CDR buffercapacity in days for your server, as follows:
Step Action Result
1. Divide the CDR buffer size (2020,7020, or up to 35,000) by the aver-age number of CDR blocks filled perday (from section 2.2.3.1).
The answer is the approximate num-ber of days that data can be collectedin the CDR buffer before the CDRbuffer becomes full. For example,
� For a server with a 2020 blockbuffer,
2020 blocks = 3.7 days537 blocks filled
Rounded down, this means that 3days’ worth of data can be col-lected in the buffer before thebuffer becomes full.
� For a server with a 7020 blockbuffer,
7020 blocks = 13 days 537 blocks filled
This means that 13 days worth ofdata can be collected in the bufferbefore the buffer becomes full.
� For a server with a 35,000 blockbuffer,
35,000 blocks = 65 days 537 blocks filled
This means that 65 days worth ofdata can be collected in the bufferbefore the buffer becomes full.
2. Using the answer from the calcula-tion in step 1 as a guide, monitor theCDR buffer-storage space on theserver until a fill pattern is estab-lished. Perform downloads regularly,based on this pattern, so the CDRbuffer does not become full.
Data from the CDR buffer is down-loaded regularly, so the buffer doesnot become full and data is not over-written.
3. Refer to section 2.2.3.3 to determinethe range of days during which thedownload should be performed.
. . .
SECTION 2.2
DATA-COLLECTION PREPARATION
Octel PC/CDR Edition 2 2-9
Using the guidelines in this chapter as a reference, monitorthe CDR buffer regularly to determine how quickly thebuffer fills. Perform downloads based on this pattern toavoid overwriting the buffer and losing data.
Caution!
2.2.3.3 Determining Download Frequency. Frequent downloads ensurethat blocks are not overwritten before they can be downloaded and that smallerdata files are created. Infrequent downloads create larger data files. Smaller datafiles have a shorter downloading and processing time. Monitor the available CDRbuffer storage space regularly by referring to SMT menu 16.1.1. Download CDRdata to the PC when the CDR buffer is between 30% and 50% full. Waiting untilthe buffer is more than 50% full could result in lost data.
Based on the rule that CDR data should be downloaded when the CDR buffer isbetween 30% and 50% full, determine how frequently data should be down-loaded from the CDR buffer on a server with light voice-mail usage and fewspecial applications, as follows:
Step Action Result
1. Using Table 2-1 or the instructionsin sections 2.2.3.1 and 2.2.3.2,determine the approximate numberof days’ worth of data that can becollected in the CDR buffer beforethe CDR buffer becomes full.
. . .
2. Multiply the number representingthe approximate number of days(from step 1) by 0.3 (30%).
The answer is the suggested numberof days that you can let pass betweendownloads of CDR data. For example,
13 days until buffer becomes fullx 0.3 3.9
Because the answer is not a wholenumber, round it down to establishthe shortest length of time you canwait between downloads, which inthis example is 3 days.
Regardless of this number, you canalways download more frequently thanthe number of days calculated here(and you are encouraged to do so).
SECTION 2.2
DATA-COLLECTION PREPARATION
2-10 Edition 2 Octel PC/CDR
Step ResultAction
3. Multiply the number representingthe approximate buffer capacity indays (from step 1) by 0.5 (50%).
The answer is the maximum numberof days that you should let passbetween downloads of CDR data.
For example,
13 days until buffer becomes fullx 0.5 6.5
Rounded down to the nearest fullday, the answer means you shouldallow a maximum of 6 daysbetween downloads.
4. The answers from steps 2 and 3give you a range of days, duringwhich you should download CDRdata.
If your buffer becomes full in approxi-mately 13 days, download CDR dataevery 3 to 6 days when the buffer isbetween 30% and 50% full.
5. Using the range determined in thiscalculation as a reference, monitoryour CDR buffer to establish a fillpattern.
You can base the frequency of yourdownloads on that fill pattern.
2.2.3.4 Checking for Potential CDR Data-Loss Warnings. When the CDRbuffer approaches capacity, alarms are generated if blocks that have not yetbeen downloaded to the PC are about to be overwritten. Refer to Chapter 1 forinformation about CDR alarms.
2.3 SIZING THE PC AND DETERMINING PROCESSINGTIME
PC disk-storage-space and processing-time requirements vary, based on thetypes of CDR events that are collected, the number of output files generated, andthe configuration of the server and CDR PC being used.
2.3.1 ESTIMATING DOWNLOAD TIME AND PC DISKSPACE
Generally, a server that handles only normal telephone answering and voice mailuses less CDR buffer and CDR PC storage space than a server that also uses anECP application with a large number of mailboxes accessed per call. Table 2-3shows download time estimates based on the estimated number of calls per dayon a server with light voice-mail usage. The columns in Table 2-3 are describedin Table 2-4. Allow more time for the download if the server has moderate orheavy voice-mail use.
SECTION 2.2 – 2.3
DATA-COLLECTION PREPARATION
Octel PC/CDR Edition 2 2-11
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table 2-3. Example of Approximate Download Time fora Server With Light Voice-Mail Usage.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AverageCalls per Day
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Average CDR BlocksFilled per Day
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ApproximateDownloading Time With
Direct Connection at 9600Baud, in Minutes per Day
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
2,500 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
134 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
5ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
5,000 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
268 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
11ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
7,500 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
402 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
16ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
10,000ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
537ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
22ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ15,000
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ805
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ32ÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁ20,000ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ1074
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ43ÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
25,000ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
1342ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
54
Table 2-4. Description of Columns in Table 2-3.
Column Name Description
Average Calls per Day The estimated number of calls processed each day bythe server. These calls include incoming calls, out-calls, network calls, message-waiting-notificationcalls, and fax calls.
Average CDR Blocks Filled perDay
The average number of CDR blocks filled each day,based on the daily call volume (Table 2-1).
Approximate Downloading TimeWith Direct Connection at 9600Baud, in Minutes per Day
The approximate time required to download the datafrom the CDR buffer to the PC, using a direct con-nection at 9600 baud, in minutes per day, based onthe number of calls processed per day.
2.3.1.1 Estimating Download Time. Estimate the length of time required todownload CDR data using the following formula:
60 seconds in a minute
Number of CDR blocks to download x 2 KB x 1.2 seconds*
* Refer to Table 2-5 for the appropriate number of seconds to use in this formula.
SECTION 2.3
DATA-COLLECTION PREPARATION
2-12 Edition 2 Octel PC/CDR
Use this formula, as follows:
Step Action Result
1. Multiply the number of CDR blocksto be downloaded by 2 (the approxi-mate number of kilobytes in a block).
The answer is the total number ofkilobytes to be downloaded. Forexample,
537 blocks x 2 kilobytes (KB) per block1074 KB to be downloaded.
2. Refer to Table 2-5 to determine theapproximate number of secondsrequired to download 1 KB, based onthe type of connection and baud rateused.
. . .
3. Multiply the total number of kilo-bytes to be downloaded (from step 1)by the approximate number ofseconds required to download 1 KB(from step 2).
The answer is the approximate number of seconds required for thedownload. For example, when theconnection is direct and the baudrate is 9600,
1074 KB x 1.2 1288.8 seconds required for thedownload
4. Divide the total number of seconds(from step 3) by 60 (the number ofseconds in a minute).
The answer is the approximate num-ber of minutes required for thedownload. For example,
1288 seconds = 21.5 60
Therefore, the download will takeapproximately 22 minutes.
Table 2-5. Time (in Seconds) To Download aKilobyte, by Connection Type and Baud Rate.
Connection Type BaudRate
Approximate Number ofSeconds Required toDownload a Kilobyte
Direct 9600 1.2
Direct 1200 9.6
Modem 9600 2
Modem 1200 16
SECTION 2.3
DATA-COLLECTION PREPARATION
Octel PC/CDR Edition 2 2-13
2.3.1.2 Estimating PC Disk Space Requirements. Use the followingformula to determine the amount of storage space (in kilobytes) required on thePC hard drive per month for downloaded data, collated data, and output files:
(Average number of CDR blocks filled per day x 2 KB x 30 days) + [(Average number of CDR blocks filled per day x 2 KB x 30 days) x 50%]
Use this formula, as follows:
Step Action Result
1. Multiply the average number ofCDR blocks filled per day by 2(the approximate number of kilo-bytes in a block).
The answer is the total number of kilo-bytes filled per day. For example,
537 blocksx 2 KB per block
1074 KB filled per day
2. Multiply the total kilobytes filledper day by 30 (the average num-ber of days in a month).
The answer is the number of kilobytesfilled per month with downloaded andcollated data. For example,
1074 KB filled per dayx 30 days in a month
32,220 KB filled per month with downloaded and collated data
3. Multiply the total kilobytes filledper month by 0.5 (output filestake up an additional 50% ofstorage space).
The answer is the number of kilobytesfilled per month with output-file data. Forexample,
32,220 KB filled per monthx 0.5 KB output file storage space
16,110 KB filled per month with out-put-file data
4. Add the total kilobytes filled permonth with downloaded andcollated data (step 2) to the totalkilobytes filled per month withoutput-file data (step 3).
The answer is the total amount of PCstorage space needed each month. Forexample,
32,220 KB filled per month+ 16,110 KB for output files
48,330 KB or 48 MB of PC hard-drive-storage space needed eachmonth for downloaded and processeddata
Monitor the amount of storage space available on your PChard drive regularly to ensure that you always have spacefor downloaded files, collated files, and output files.Running out of PC storage space could cause irregularitiesin Octel PC/CDR data.
Caution!
SECTION 2.3
DATA-COLLECTION PREPARATION
2-14 Edition 2 Octel PC/CDR
Establish a schedule to back up files on the PC hard drive periodically and thendelete the older files to conserve PC disk-storage space. Refer to Chapter 1 forinformation about backing up and deleting Octel PC/CDR collection files.
2.3.1.3 Confirming Available Disk Space. Before downloading data fromthe CDR buffer, check the Display Disk Status option on the Octel PC/CDRFile Utilities Menu to confirm that there is enough available disk-storage spaceon the PC hard drive. Refer to Chapter 8 for information about accessing andusing this option. You can also check the available PC disk-storage space byusing the DOS dir command (refer to your DOS manual for instructions).
Compare the required amount of disk space with the actual amount available on the PC. If the PC does not currently have enough space for the projectedrequirements, make more space available.
2.3.2 ESTIMATING PROCESSING TIME
The amount of time it takes to process CDR data varies, based on the number ofblocks downloaded, the number and size of the BCFs and collated day files(CDFs) being processed, and the number of output files selected for generation.It also varies based on the PC’s speed, the disk type, and CPU type. Monitor thesize and number of CDFs and output files processed, and create an approximateprocessing time chart based on the results of your research.
2.4 CONFIGURING THE SERVER FOR CDR DATACOLLECTION
Data is accumulated in the CDR buffer only after the server is configured tocollect Octel PC/CDR data. Configure the server and check for overwrittenblocks, as follows:
Step Action Reference Section
1. Confirm that the Call Detail Recording feature optionhas been enabled to allow the collection of CDR data(menu 13.7).
2.4.1
2. Select the record groups to be collected in the CDRbuffer, using the Call Detail Records Collected screen(menu 16.1.4).
2.4.2
3. Check the Call Detail Recording Status screen (menu 16.1.1) to ensure that the CDR buffer is notoverwritten.
2.4.3
4. If blocks that have not been downloaded have beenoverwritten, reset the Clear Call Detail Recording LostData Counter (menu 16.1.3).
2.4.5
SMT menus can be accessed from the CDR PC using SMT emulation. Refer tosection 5.4 for details about SMT emulation.
SECTION 2.3 – 2.4
DATA-COLLECTION PREPARATION
Octel PC/CDR Edition 2 2-15
2.4.1 CONFIRMING THAT THE SOFTWARE FEATURE ISENABLED
The Call Detail Recording feature option must be enabled before CDR data canbe collected by the server. Data collection for some features, such as AudioMessaging Interchange Specification (AMIS) networking and DTMF OctelForms,also requires that an additional feature option be enabled. (Refer to the appropri-ate manual for details.) Verify that the Call Detail Recording feature option isenabled, as follows:
Step Action Result
1. From the Main Menu on the system-managerterminal (SMT), select option 13 – SystemMaintenance, and press Return.
The System Maintenancemenu appears.
2. Select option 7, and press Return. A screen similar to the oneshown in Figure 2-4 appears.
3. Verify that the Call Detail Recording featureoption has been enabled. If the 16 – Call Detail Recording feature is not preceded by aY, call your local Octel or distributor service representative for assistance in enabling thefeature.
. . .
4. If data is needed for other applications, con-firm that the appropriate feature options areenabled. For example, the 49 – AMIS AnalogNetworking feature must be preceded by a Yfor AMIS data to be collected, and the 43 –DTMF Forms Mailbox feature must be pre-ceded by a Y for DTMF OctelForms data to becollected.
. . .
5. Press Return until the Main Menu reappears. The Main Menu reappears.
SECTION 2.4
DATA-COLLECTION PREPARATION
2-16 Edition 2 Octel PC/CDR
23 MAY 96 08:49:30AM WESTREG SN:12345VPMOD Serial # ........ 12345Network Serial #....... 12345Y 8 – Bulletin MailboxY 10 – InterMail
14 – InfoTexY 16 – Call Detail RecordingY 22 – Forms MailboxY 32 – General Line TypesY 34 – RS232 Integrations
36 – ROLM Limited38 – 72 Port Option42 – Hotel/Motel
Y 44 – Networking46 – Ability to Reset Passwords
Y 48 – Information Center MailboxesY 51 – Octel Index IY 55 – Conference MailboxY 57 – Announcement Mailbox
59 – ACP MTA61 – Short Message Service
WESTREGSoftware Rel. ...... Aria 01.20System Type............250Y 9 – CSAY 12 – PowerCall Agent AccessY 15 – Follow–Me–ForwardY 17 – Database RetrievalY 23 – Monitor Mailbox
33 – Set EmulationY 35 – In–band Integrations
37 – Siemens Limited40 – Information Processing
Y 43 – DTMF Forms MailboxY 45 – Enhanced Call Processing
47 – OutcallingY 49 – AMIS Analog NetworkingY 52 – Octel Index IIY 56 – Fax ProcessingY 58 – ACP Integrations
60 – Skip Password62 – Centralized Network Management –Continued–
Figure 2-4. First Screen of Menu 13.7, Display ofSoftware Features Installed, for Servers
With Software at Aria 1.2.
2.4.2 SELECTING RECORD GROUPS FOR COLLECTION
SMT menu 16.1.4 displays the groups of CDR records that can be selected forcollection. Select at least one of these record groups to allow the server to begincollecting CDR records. Figure 2-5 is an example of menu 16.1.4 for serversusing Octel Aria 1.1 or Aria 1.2 messaging software or Aspen Release 4.1software. Menu 16.1.4 for other software releases does not include record groups9 and 10. Refer to Table 2-6 to determine which record groups to select for theoutput files or events that you need. For example, to collect data for thecaller-menu output (CMO) file, select record groups 2 and 8 for collection.
Menu 16 - Database AccessCall Detail Records Collected
westreg
RecordGroup Types of Records Collected Option
Record Group: Option:
1 All Records As Indicated Below2 Session Related Records . . Yes3 Message Send/Delete/Print Records . Yes4 Network Related Records . . Yes5 Invalid Password Disconnect Records . Yes6 Message Waiting Notification Records . Yes7 DTMF Forms Mailbox Records . . Yes8 Reporting Related Records . . Yes9 Message Count Records . . No10 Message Review Records . . NoMessage Review Record Mailboxes:1: 2: 3: 4: 5:6: 7: 8: 9: 10:
Figure 2-5. Menu 16.1.4, Call Detail Records Collected,for Servers With Software at Aria 1.1, Aria 1.2,
or Aspen Release 4.1.
SECTION 2.4
DATA-COLLECTION PREPARATION
Octel PC/CDR Edition 2 2-17
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table 2-6. Record Groups for Data Collection.
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Record Groups Required
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Desired OutputFiles or Events
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
1 -All
Records
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
2 -SessionRelatedRecords
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
3 -Message
Send/Delete/Print Records
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
4 -NetworkRelatedRecords
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
5 - Invalid
PasswordDisconnect
Records
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
6 -MessageWaiting
Notification
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
7 -DTMFForms
MailboxRecords
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
8 -ReportingRelatedRecords
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
9 -MessageCount
Recordsa
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
10 -MessageReview
Recordsa
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Output Files
ÁÁÁÁÁÁÁÁÁÁÁÁ
Session DetailÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
XÁÁÁÁÁÁÁÁ
XÁÁÁÁÁÁÁÁ
XÁÁÁÁÁÁÁÁ
XÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
UnsuccessfulTransfer
ÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
XÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁMessage Detail ÁÁÁÁÁÁÁX ÁÁÁÁX ÁÁÁÁÁÁÁÁX ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
Individual PortStatistics
ÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
XÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
XÁÁÁÁÁÁÁÁÁÁÁÁ
XbÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁDTMF OctelFormsÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁ
X ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
X ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁFax ÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁ
X ÁÁÁÁÁÁÁÁ
X ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁ
Profile ChangeDetails ÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁ
X ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁ
X ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁCaller Menu ÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁ
X ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁ
X ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁDisk Usage ÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁ
X ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁNameNet ÁÁÁ
ÁÁÁXcÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁEvents
ÁÁÁÁÁÁÁÁÁÁÁÁ
Message Counta ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
X ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁMessage ReviewaÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
X
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
a Available when the server software is at Aria 1.1, Aria 1.2, or Aspen Release 4.1.
b Available for servers with in-band integration only.
c Select any one or more of the record groups to collect NameNet events.
Caution!The speed at which the CDR buffer fills increases with thenumber and type of record groups selected for collection.As records groups are selected for collection, monitor theCDR buffer frequently until a fill pattern is established andthen download data accordingly, so the buffer does notbecome full and data is not lost.
When selecting record groups for collection, keep the following in mind:
� If data for all of the output files and the two events is required, select recordgroup 1 (All Records) to collect all CDR records. Selecting record group 1 isthe same as selecting record groups 2 through 10 for servers at Aria 1.1, Aria1.2, or Aspen Release 4.1, or selecting record groups 2 through 8 for oldersoftware releases.
� Select the Message Send/Delete/Print Records group (record group 3) only ifyou want detailed data about all messages. Selecting this group will causethe buffer to fill more quickly.
SECTION 2.4
DATA-COLLECTION PREPARATION
2-18 Edition 2 Octel PC/CDR
� Select record group 3 if you want data displayed in the Msent (TotalMessages Sent) and Mdel (Total Messages Deleted) fields of the session-detailoutput file.
� Select the Network Related Records group (record group 4) to collectOctelNet� data. When you select record group 3 and feature option 49 isenabled, AMIS networking data also is collected. (Refer to section 2.4.1 forinformation about confirming enabled feature options.)
� Use the Message Waiting Notification group (record group 6) to providedetails about every message-waiting set and message-waiting clear attemptfor servers with in-band integration. This data fills the CDR buffer quickly,especially on busy servers. Select this record group only if this information isneeded.
� Select the the DTMF Forms Mailbox Records group (record group 7) to collectDTMF OctelForms data. Feature option 43 must first be enabled to allowDTMF Forms data to be collected.
� Use the Message Review Records group (record group 10) to generate a newevent each time a message is reviewed by a user. Because of the largenumber of events generated by this record group, the CDR buffer becomesfull faster than usual and can overflow, causing data to be lost. To limit theamount of data collected, actively monitor only those mailboxes that arerequired, and only enable this record group when this data is needed.
Refer to Appendix C for a list of the approximate byte sizes of events included inthe record groups shown in Figure 2-5. Appendix C also shows which events arecollected in each record group.
Refer to section 2.4.2.1 or 2.4.2.2, as appropriate, to select record groups forcollection. Perform the following procedures to access menu 16.1.4:
ÁÁÁÁÁÁÁÁ
Step ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Action ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ResultÁÁÁÁÁÁÁÁÁÁÁÁ
1.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
From the SMT Main Menu, selectoption 16, and press Return.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Menu 16 – Database Access appears, asshown in Figure 2-6.ÁÁÁÁ
ÁÁÁÁÁÁÁÁ
2.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Select option 1, and press Return.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Menu 16.1, Manage Call Detail Record-ing, appears, as shown in Figure 2-7.ÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
3.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Select option 4, and press Return.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Menu 16.1.4, Call Detail Records Col-lected, appears, similar to the screenshown in Figure 2-8.
Menu 16 – Database Access
1 – Manage Call Detail Recording2 – Retrieve Database Information
Enter Option:
westreg
Figure 2-6. Menu 16 – Database Access.
SECTION 2.4
DATA-COLLECTION PREPARATION
Octel PC/CDR Edition 2 2-19
Menu 16 – Database AccessManage Call Detail Recording
1 – Display Call Detail Recording Status2 – Retrieve Call Detail Records3 – Clear Call Detail Recording Lost Data Counter4 – Display/Change Call Detail Records Collected
Enter Option:
westreg
Figure 2-7. Menu 16.1, Manage Call Detail Recording.
Menu 16 - Database AccessCall Detail Records Collected
westreg
RecordGroup Types of Records Collected Option
Record Group: Option:
1 All Records As Indicated Below2 Session Related Records . . Yes3 Message Send/Delete/Print Records . No4 Network Related Records . . No5 Invalid Password Disconnect Records . No6 Message Waiting Notification Records . No7 DTMF Forms Mailbox Records . . No8 Reporting Related Records . . Yes9 Message Count Records . . No10 Message Review Records . . NoMessage Review Record Mailboxes:1: 2: 3: 4: 5:6: 7: 8: 9: 10:
Figure 2-8. Example of Menu 16.1.4 WithRecord Groups 2 and 8 Selected.
SECTION 2.4
DATA-COLLECTION PREPARATION
2-20 Edition 2 Octel PC/CDR
2.4.2.1 Selecting Record Groups for Servers With Software at Aria 1.1,Aria 1.2, or Aspen Release 4.1. If your server software is at Aria 1.1, Aria 1.2,or Aspen Release 4.1, select record groups for collection, as follows:
ÁÁÁÁÁÁÁÁÁÁÁÁ
StepÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ActionÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Result
ÁÁÁÁÁÁÁÁÁÁÁÁ
1. ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Refer to Table 2-6 to determinewhich record groups to collect.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
. . .
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
2. ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
In menu 16.1.4 (Figure 2-8), enterthe number of the first record group(1–10) needed in the RecordGroup: field, based on the desiredoutput files or events. Select recordgroup 1 only if all output files andevents are desired. Press Return.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
The cursor moves to the Option: field.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
3. ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
In the Option: field, enter Y to collect the selected record group,and press Return.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Depending on the entry in the RecordGroup: field, and if the entry in theOption: field is Y, one of the followingoccurs when you press Return:
� If you selected record group 1, allentries in the Option column changeto Yes, and the cursor moves to theMessage Review Record Mailboxes:1: field.
� If you selected a record group between 2 and 9, the entry in theOption column that corresponds tothe selected record group changes toYes, and the cursor returns to the Record Group: field.
� If you selected record group 10, thecursor moves to the Message Re-view Record Mailboxes: 1: field.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
4.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
If you selected a record group be-tween 2 and 9 in step 3, go to step5.
If you selected record group 1 or 10in step 3, complete the Message Review Record Mailboxes: fields,as follows:
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
. . .
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
� To collect message review recordsfor up to 10 mailboxes, enter themailbox numbers for which mes-sage review events are to be col-lected in fields 1: through 10:.Press Return after each entry.
Press the up-arrow key to returnto the previous mailbox field.Press Shift–Del to remove anentry from a field.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
You collect message review records forup to 10 mailboxes.
SECTION 2.4
DATA-COLLECTION PREPARATION
Octel PC/CDR Edition 2 2-21
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ResultÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ActionÁÁÁÁÁÁÁÁÁÁÁÁ
Step
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
� To collect message review recordsfor all mailboxes, enter a zero inthe 1: field to represent eachdigit in a mailbox number onyour server. (For example, enter0000 if your mailboxes are 4digits long.)
Press Return until the cursor isin the Record Group: field.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
You collect message review records forall mailboxes.
The entry in the corresponding Optioncolumn changes to Yes. Make note ofthe warning that appears at the bottomof the screen, and go to step 5.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
� To enter more record groups,press Return until the cursor isin the Record Group: field, andthen repeat steps 2 and 3.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
You can enter more record groups.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
� To save entries if no more mail-boxes or record groups are to beentered, press Return until thecursor is in the Record Group:field, and then go to step 6.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
You can save entries.
ÁÁÁÁÁÁÁÁÁÁÁÁ
5.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Repeat steps 2, 3, and 4 until all thedesired record groups are selected.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
. . .
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
6.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Press Send (or Page Down on somekeyboards) to save the changes.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Changes to menu 16.1.4 are saved, andyou are prompted to press any key tocontinue.
ÁÁÁÁÁÁÁÁÁÁÁÁ
7.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Press Return until you return tothe Main Menu.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
The Main Menu reappears.
2.4.2.2 Selecting Record Groups for Servers With Software at Aria 1.0 orAspen Release 1.0X Through 4.0. If your server software is at Aria 1.0 or atAspen Release 1.0X through 4.0, select record groups for collection, as follows:
ÁÁÁÁÁÁÁÁÁÁÁÁ
StepÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ActionÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Result
ÁÁÁÁÁÁÁÁÁÁÁÁ
1. ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Refer to Table 2-6 to determinewhich record groups to collect.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
. . .
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
2. ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
From menu 16.1.4 (Figure 2-8),enter the number of the first re-cord group (1–8) needed in theRecord Group: field, based onthe desired output files. Selectrecord group 1 only if all outputfiles are desired. Press Return.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
The cursor moves to the Option: field.
SECTION 2.4
DATA-COLLECTION PREPARATION
2-22 Edition 2 Octel PC/CDR
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ResultÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ActionÁÁÁÁÁÁÁÁÁÁÁÁ
Step
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
3. ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
In the Option: field, enter Y tocollect the selected record group.Press Return.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Depending on the entry in the RecordGroup: field, and if the entry in theOption: field is Y, one of the followingoccurs when you press Return:
� If you selected record group 1, all en-tries in the Option column change toYes, and the cursor returns to the Record Group: field.
� If you selected a record group between2 and 8, the entry in the Option col-umn that corresponds to the selectedrecord group changes to Yes, and thecursor returns to the Record Group:field. ÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
4.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Repeat steps 2 and 3 until all the desired record groups are selected.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
. . .
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
5.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Press Send (or Page Down onsome keyboards) to save thechanges.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Changes to menu 16.1.4 are saved, andyou are prompted to press any key to continue.
ÁÁÁÁÁÁÁÁÁÁÁÁ
6.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Press Return until you return tothe Main Menu.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
The Main Menu reappears.
2.4.3 MONITORING AVAILABLE CDR BUFFER STORAGESPACE AND CDR BLOCK INFORMATION
Use menu 16.1.1, Call Detail Recording Status (similar to the screen shown inFigure 2-9), to monitor important information about the CDR buffer. Thisinformation includes the amount of available storage space on the CDR buffer,the total number of blocks reserved for CDR on the server (either 2020, 7020, orup to 35,000), the block sequence numbers, and the number of overwrittenblocks. The information displayed is updated automatically by the server andcannot be changed by the system manager.
If you are using another reporting product, such as the Octel DecisionProReporting Package�, to download data from the CDR buffer, the information onthis screen might not be accurate. Menu 16.1.1 fields accurately reflect the CDRbuffer status for the last download performed. For example, if the last downloadwas performed by Octel PC/CDR, menu 16.1.1 information is accurate as itapplies to the Octel PC/CDR application. If the next download is performed byDecisionPro, menu 16.1.1 is then accurate as it applies to the DecisionProapplication.
SECTION 2.4
DATA-COLLECTION PREPARATION
Octel PC/CDR Edition 2 2-23
CDR Disk Space Free: 91 Percent
Total Number of Blocks for CDR: 7020
Sequence Number of Oldest Block: 0
Sequence Number of Block Currently Being Filled: 1584
Sequence Number of First Block Not Retrieved: 955
Number of Blocks Overwritten: 0
Press any key to continue:
Menu 16 – Database AccessCall Detail Recording Status
westreg
Figure 2-9. Menu 16.1.1, Call Detail Recording Status.
Check the CDR Disk Space Free: field often, to monitor the available CDRbuffer storage space. Download as necessary to avoid having blocks that havenot been downloaded overwritten if the CDR buffer becomes full.
If the entry in the Number of Blocks Overwritten: field is greater than 0, blocksthat have not yet been downloaded have been overwritten. Follow the steps insection 2.4.5 to reset this counter to 0.
2.4.4 USING THE RETRIEVE CALL DETAIL RECORDSOPTION
The Retrieve Call Detail Records option (menu 16.1.2) is used only by fieldservice engineers, through SMT emulation, to perform a special service-relateddownload. A similar menu is described in Chapter 7.
2.4.5 RESETTING THE CALL DETAIL RECORDING LOSTDATA COUNTER
If blocks that have not been downloaded have been overwritten, CDR data hasbeen lost. Review the sizing and downloading information at the beginning ofthis chapter, and update your download schedule so that blocks are notoverwritten again.
SECTION 2.4
DATA-COLLECTION PREPARATION
2-24 Edition 2 Octel PC/CDR
Before another download can be performed, you must reset the overwritten datacounter, using the Clear Call Detail Recording Lost Data Counter option onmenu 16.1.3. Refer to the Number of Blocks Overwritten: field in menu 16.1.1(as shown in Figure 2-9); the entry must be 0 before new data blocks can bedownloaded. Reset the counter, as follows:
ÁÁÁÁÁÁÁÁ
Step ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Action ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ResultÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
1.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
From the SMT Main Menu,select option 16, and press Return.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Menu 16 – Database Access appears, asshown in Figure 2-6.
ÁÁÁÁÁÁÁÁÁÁÁÁ
2. ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Select option 1, and press Return.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Menu 16.1, Manage Call Detail Recording,appears, as shown in Figure 2-7.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
3. ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
To reset the counter, selectoption 3, and press Return.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
The entry in the Number of Blocks Over-written: field on menu 16.1.1 is reset to 0,and the following prompt appears on menu16.1, as shown in Figure 2-10:
Lost data counter cleared. Press anykey to continue:
Menu 16 – Database AccessManage Call Detail Recording
1 - Display Call Detail Recording Status2 - Retrieve Call Detail Records3 - Clear Call Detail Recording Lost Data Counter4 - Display/Change Call Detail Records Collected
Enter Option: 3
Lost data counter cleared. Press any key to continue:
westreg
Figure 2-10. Menu 16.1, Showing Thatthe Data Counter Was Cleared.
SECTION 2.4
O C T E L
P C / C D R
INSTALLATIONPROCEDURES
C O N T E N T S
3-iiiEdition 2Octel PC/CDR
CHAPTER 3
3.1 OVERVIEW 3-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2 INSTALLING OCTEL PC/CDR SOFTWARE ON THE PC 3-1. . . . . . . . . . .
3.3 CREATING CDR SYSTEM DATA SUBDIRECTORIES USING MKCDRSYS 3-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4 REMOVING CDR SYSTEM DATA SUBDIRECTORIES 3-9. . . . . . . . . . . . .
3.5 UPGRADING OCTEL PC/CDR SOFTWARE 3-10. . . . . . . . . . . . . . . . . . . . . . .
3.5.1 UPGRADE CONSIDERATIONS 3-10. . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.1.1 Effect of Output File Changes on Billing Programs 3-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.1.2 CDR Buffer Download Frequency and PC Storage Needs 3-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.1.3 Requirement for New Output Files 3-11. . . . . . . . . . . . . .
3.5.2 UPGRADE PROCEDURE 3-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TABLESTable 3-1. Octel PC/CDR Subdirectories 3-1. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3-2. Octel PC/CDR Installation Program Menu Fields 3-3. . . . . . . . .
Table 3-3. CDR System Subdirectories 3-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Section Page
C O N T E N T S
3-iv Edition 2 Octel PC/CDR
FIGURESFigure 3-1. Octel PC/CDR Installation Program Menu 3-2. . . . . . . . . . . . . . .
Figure 3-2. Sample Listing of a CONFIG.SYS File and anAUTOEXEC.BAT File Showing Added or Modified Lines 3-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3-3. Load Octel PC/CDR System Screen When the Boot Files Are Updated 3-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3-4. Screen Printout Showing Files Created by the INSTCDR Command 3-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3-5. Example of Octel PC/CDR Disk-Directory Structure 3-7. . . . .
Figure 3-6. First Octel PC/CDR System Data Directory Creation Screen 3-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3-7. Second Octel PC/CDR System Data Directory Creation Screen 3-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3-8. Example of a System Creation Screen 3-9. . . . . . . . . . . . . . . . . . .
Figure 3-9. Octel PC/CDR Upgrade Program Menu 3-12. . . . . . . . . . . . . . . . .
Figure 3-10. Upgrade Octel PC/CDR System Screen 3-14. . . . . . . . . . . . . . . . .
Page
C H A P T E R 3
Octel PC/CDR Edition 2 3-1
INSTALLATION PROCEDURES
3.1 OVERVIEW
This chapter provides information about installing the Octel PC/CDR softwarepackage on the CDR PC, creating CDR systems, removing unnecessary CDRsystems, and upgrading to a new release of Octel PC/CDR software. Refer tosection 1.3, steps 1 through 9 of the Process Checklist, for an overview of thesteps required to install and configure the Octel PC/CDR software package.
3.2 INSTALLING OCTEL PC/CDR SOFTWARE ON THE PC
The Octel PC/CDR software package is provided on a single floppy disk in acompressed format. When the software is fully installed, it uses approximately2.7 megabytes (MB) of disk-storage space. Additional storage space is requiredfor data downloaded from the server and for processed files. (Refer to section 2.3for details.) The Octel PC/CDR software package includes the Octel PC/CDR,Mirror, and Carbon Copy PLUS software programs.
Following the instructions in this section, use the INSTCDR.EXE program on theOctel PC/CDR software disk to copy the Octel PC/CDR software onto the PChard drive and to create the subdirectories described in Table 3-1. The MIR, CC,and LOG subdirectories are part of the OCTELCDR subdirectory. The files in theOCTELCDR, MIR, CC, and LOG subdirectories are listed in Appendix D.
Table 3-1. Octel PC/CDR Subdirectories.
Subdirectory Description
OCTELCDR Contains the software for processing Octel PC/CDR files.
MIR Contains the data-communications software used by theCDR PC to communicate with the server.
CC Contains Carbon Copy PLUS software, which is used for re-mote PC maintenance.
LOG Contains the SCHEDCDR.LOG file. This file containsinformation about automatic-schedule transactions. (Referto section 7.5.4 and Appendix F for more information aboutthis file.)
The INSTCDR.EXE program also modifies (appends) the AUTOEXEC.BAT andCONFIG.SYS files in the root directory, if you choose that option when installingthe Octel PC/CDR software. If modified, the original files are renamed with theextension .OLD and are not used with Octel PC/CDR.
INSTALLATION PROCEDURES
3-2 Edition 2 Octel PC/CDR
Configure the Octel PC/CDR software installation menu, as follows:
Step Action Result
1. Confirm that steps 1, 2, and 3 of theProcess Checklist in section 1.3 havebeen completed.
. . .
2. Turn on the CDR PC. The DOS prompt appears.
3. Insert the Octel PC/CDR software diskinto a compatible disk drive on theCDR PC.
. . .
4. At the DOS prompt, type the letter ofthe drive containing the Octel PC/CDRdisk, followed by a colon, and pressEnter. For example,
If the disk is inserted into driveone, type a: at the DOS prompt,and press Enter.
The prompt changes to the desig-nated drive. For example, A:\>.
5. At the designated-drive DOS prompt,type instcdr, and press Enter.
The Octel PC/CDR Installation Program menu appears, with defaultvalues, as shown in Figure 3-1. Thedefault values are generally used in a new installation, but they shouldalways be verified.
6. Use the information in Figure 3-1 andTable 3-2 to determine the correct value for each field. As necessary,move the cursor to the appropriatefield and type in the new value.
. . .
F1 – Help F10 – Proceed ESC – Cancel/Quit
Source Drive Name : A:Boot Drive Name : C:Destination Drive Name : C:Update autoexec.bat & config.sys? : YInstall Octel PC/CDR Software? : Y
Octel PC/CDR Installation Program(C) Copyright 1988–1996 Octel Communications Corporation
Figure 3-1. Octel PC/CDR Installation Program Menu.
SECTION 3.2
INSTALLATION PROCEDURES
Octel PC/CDR Edition 2 3-3
Table 3-2. Octel PC/CDR Installation Program Menu Fields.
Field Description
Source DriveName:
Shows the drive being used to read the Octel PC/CDR softwareinstallation disk and display this menu. This field cannot bechanged.
Boot Drive Name: Shows from which drive the PC boots. This is the PC hard driveon which the CONFIG.SYS and AUTOEXEC.BAT files are located.To change the default of C:, type the boot drive letter, followed bya colon. For example, type d:.
Destination DriveName:
Specifies the drive onto which the Octel PC/CDR software is beinginstalled. This destination must be a hard drive or part of a harddrive with at least 2.2 MB currently available. (Additional storagespace is required for downloaded and processed files. Refer tosection 2.3 for details.) To change the default of C:, type the des-tination drive letter, followed by a colon. For example, type d:.
Updateautoexec.bat &config.sys?:
Questions whether the PC boot files (AUTOEXEC.BAT and CONFIG.SYS) should be altered. Leave this field with the defaultof Y if this is the first installation of the Octel PC/CDR software;otherwise, change to N.
When Y is in the field, the AUTOEXEC.BAT file is updated so that the PC has a path to the Octel PC/CDR software. The CONFIG.SYS file is modified to create the correct environment forthe Octel PC/CDR software to operate as specified. Figure 3-2 isan example of an updated AUTOEXEC.BAT and CONFIG.SYS list-ing. The brackets to the left indicate the lines added or modifiedduring the installation of the Octel PC/CDR software.
Install Octel PC/CDR Software?:
Questions whether the Octel PC/CDR software should be in-stalled. Leave the default of Y to install the Octel PC/CDRsoftware.
type autoexec.bat
echo offprompt $p$gpath c:\;c:\dosclsdoskey
set path=%path%;C:\octelcdr set cdrsysnm=Octel
type config.sys
BUFFERS=20 FILES=160
device=C:\octelcdr\ansi.sys SHELL=C:\COMMAND.COM /p /e:1000
NEW ORMODIFIED
NEW ORMODIFIED
Figure 3-2. Sample Listing of a CONFIG.SYS File and anAUTOEXEC.BAT File Showing Added or Modified Lines.
SECTION 3.2
INSTALLATION PROCEDURES
3-4 Edition 2 Octel PC/CDR
Complete the installation, as follows:
Step Action Result
1. When all field changes are complete,press F10 to proceed.
A screen similar to Figure 3-3appears, with the following prompt:Proceed with Installation? [y/n].
2. Press Y. The software load begins, taking approximately 5 minutes.
As each file is created, the file nameappears on the screen; as the screenfills, data scrolls off the top of thescreen. Figure 3-4 shows a listing ofall the files created by the INSTCDRcommand.
After the software is loaded, the DOSprompt reappears.
3. Remove the disk from the sourcedrive and store it in a safe place.
. . .
4. If Y was selected to update theAUTOEXEC.BAT and CONFIG.SYSfiles, restart the PC by pressing the Ctrl, Alt, and Del keys simultaneously.
The PC reboots and the updatedAUTOEXEC.BAT and CONFIG.SYSfiles are loaded into the PC memoryduring the PC boot process.
This program is about to perform the following:
Update “autoexec.bat” and “config.sys” on Drive “C:” Install Octel PC/CDR Software on Drive “C:”
The Source Drive is “A:”
Proceed with Installation? [y/n]
Figure 3-3. Load Octel PC/CDR System ScreenWhen the Boot Files Are Updated.
SECTION 3.2
INSTALLATION PROCEDURES
Octel PC/CDR Edition 2 3-5
********** Updating CONFIG.SYS **********
File “C:\CONFIG.SYS” updated
********** Updating AUTOEXEC.BAT **********
File “C:\AUTOEXEC.BAT” updated
********** Loading Octel PC/CDR software **********
C:\OCTELCDR\CC\CC30.CFGC:\OCTELCDR\CC\MM30.CFGC:\OCTELCDR\CC\CCINSTAL.EXEC:\OCTELCDR\CC\CCLOG.EXEC:\OCTELCDR\CC\CCREMOVE.EXEC:\OCTELCDR\CC\CCSECURE.EXEC:\OCTELCDR\CC\MODEM.DSCC:\OCTELCDR\CC\CC.EXEC:\OCTELCDR\MIR\WY50SPEC.MEFC:\OCTELCDR\MIR\VT100.MEFC:\OCTELCDR\MIRROR.EXEC:\OCTELCDR\MIRROR.HLPC:\OCTELCDR\MIR\CDRDOWNL.XTSC:\OCTELCDR\MIR\CDRDOWNL.XTKC:\OCTELCDR\MIR\LINKSMT.XTSC:\OCTELCDR\MIR\LOGOFF.XTSC:\OCTELCDR\MIR\LANGUAGE.XTKc:\OCTELCDR\MIR\ANSI.MEFC:\OCTELCDR\LOG\SCHEDCDR.LOGC:\OCTELCDR\CDRCLEAN.BATC:\OCTELCDR\MKCDRSYS.BATC:\OCTELCDR\RMCDRSYS.BATC:\OCTELCDR\CDFS.EXEC:\OCTELCDR\CDRERASE.EXEC:\OCTELCDR\CDRHELP.EXEC:\OCTELCDR\CDRSYSNM.EXEC:\OCTELCDR\CDR.EXEC:\OCTELCDR\CDRMENU.EXEC:\OCTELCDR\CHKREV.EXEC:\OCTELCDR\COLLATE.EXEC:\OCTELCDR\COMPRSB.EXEC:\OCTELCDR\COMPRSF.EXEC:\OCTELCDR\COMPRSM.EXEC:\OCTELCDR\COMPRSP.EXEC:\OCTELCDR\COMPRSU.EXEC:\OCTELCDR\COPYBCF.EXEC:\OCTELCDR\DUMPBCF.EXEC:\OCTELCDR\DUMPSF.EXEC:\OCTELCDR\DV_MAIN.EXEC:\OCTELCDR\LOGO.EXEC:\OCTELCDR\LOGO.DATC:\OCTELCDR\SCHEDCDR.EXEC:\OCTELCDR\SCHEDEDT.EXEC:\OCTELCDR\ANSI.SYSC:\OCTELCDR\COLGRPC:\OCTELCDR\COMPRSX.EXEC:\OCTELCDR\COMPRSR.EXEC:\OCTELCDR\COMPRSD.EXEC:\OCTELCDR\COMPRSC.EXEC:\OCTELCDR\COMPRSN.EXEC:\OCTELCDR\INSTCDR.EXEC:\OCTELCDR\UPGRCDR.EXESYSNAME.DAT 1 file(s) copiedCDRP.SN 1 file(s) copiedContents of distribution disk loaded
You must reboot your computer by pressing CTRL+ALT+DEL keyssimultaneously, so that the changes made to “autoexec.bat” and “config.sys” will take effect.
After you have rebooted, type MKCDRSYS for instructions on howto create Octel PC/CDR System Data Files
A:\>
Figure 3-4. Screen Printout Showing Files Createdby the INSTCDR Command.
SECTION 3.2
INSTALLATION PROCEDURES
3-6 Edition 2 Octel PC/CDR
3.3 CREATING CDR SYSTEM DATA SUBDIRECTORIESUSING MKCDRSYS
For each server that downloads CDR data, use the MKCDRSYS command tocreate a CDR system and its related subdirectories on the PC hard drive. Choosean appropriate name for each CDR system—one that is easily remembered andunique.
The MKCDRSYS command creates 13 subdirectories on the PC hard drive foreach CDR system, as described in Table 3-3. The subdirectories in this table arelisted in the order in which they are created.
Table 3-3. CDR System Subdirectories.
Subdirectory Contents
SYS CDR system log files (dated log files), theCOLLATE pending-state file, and system-attribute files
BCF Binary collection files (raw data), collatedbinary collection files, the COMPRSPpending-state file, and dated pending-state files
CDF Collated day files
SDO Session-detail output files
PSO Individual-port-statistics output files
UTO Unsuccessful-transfer output files
MDO Message-detail output files
FDO Forms output files
FXO Fax output files
PRO Profile-change-details output files
DUO Disk-usage output files
CMO Caller-menu output files
NNO NameNet output files
Each set of CDR system subdirectories contains Octel PC/CDR data for aparticular server. Thirteen subdirectories—one system, two data, and tenoutput-file subdirectories—are created for each CDR system. Figure 3-5 is anexample of this file structure, showing the DOS, CDR system (as named usingthe MKCDRSYS command), and OCTELCDR subdirectories all residing on thesame PC hard drive. These subdirectories could each be on a separate harddrive, with the appropriate paths being established during the Octel PC/CDRsoftware installation and when the CDR systems are established.
SECTION 3.3
INSTALLATION PROCEDURES
Octel PC/CDR Edition 2 3-7
DOS OCTELCDR
BCF BinaryCollection Files
CDF CollatedDay Files
SYSSystem Files
Myymmdd.DBF/ASCPyymmdd.DBF/ASCByymmdd.DBF/ASC Xyymmdd.DBF/ASC
Octel PC/CDRProcessingPrograms
COLLATE.PSF CDyymmdd.CDFAyymmddi.BCF
All DOSFiles (80+)
autoexec.batconfig.sys
PC HARD DISKROOT DIRECTORY
FORMS.DBF/ASC
CC
MIR
System Attribute Files
LOG
Ayymmddi.PCFAyymmddi.PSF
SDOSession-DetailOutput Files
UTOUnsuccessful-
Transfer OutputFiles
MDOMessage-Detail
Output Files
PSOIndividual-Port-Statistics Output
Files
FDOForms Output Files
(optional)
FXOFax Output Files
Fyymmdd.DBF/ASC
PROProfile-Change-
Details Output Files
Ryymmdd.DBF/ASC
DUODisk-Usage Output Files
Dyymmdd.DBF/ASC
CMOCaller-MenuOutput Files
Cyymmdd.DBF/ASC
NNONameNet
Output Files
Nyymmdd.DBF/ASC
name][cdr system
COMPRSP.PSF
Lyymmdd.LOG
PByymmdd.DBF
Figure 3-5. Example of Octel PC/CDR Disk-Directory Structure.
If an incorrect CDR system is created or an existing CDR system is no longerneeded, use the RMCDRSYS (remove Octel PC/CDR system) command to deleteit, as described in section 3.4.
Following the instructions in this section, create a CDR system name, subdirec-tories, and a batch file to provide access to these subdirectories, using theMKCDRSYS command with the following syntax:
mkcdrsys [systemname] [datadrive:] [progdrive:]
where
mkcdrsys is the command to create a CDR system on the PC hard drive.
systemname is the unique name chosen to identify a particular Octel server.
datadrive: is the PC hard drive on which the data subdirectories for the newCDR system are to be created.
progdrive: is the PC hard drive onto which the Octel PC/CDR software wasinstalled.
SECTION 3.3
INSTALLATION PROCEDURES
3-8 Edition 2 Octel PC/CDR
For example,
If the new CDR system subdirectories for the server located in the WesternRegion will be located on drive C: (the same drive as the Octel PC/CDRsoftware), type the following:
mkcdrsys westreg c: c:
Execute the MKCDRSYS command to create CDR systems, as follows:
Step Action Result
1. At the DOS prompt, type theMKCDRSYS command, using the correct syntax, and press Enter.
The first Octel PC/CDR System DataDirectory Creation screen appears, asshown in Figure 3-6.
2. To print a copy of this process as itoccurs, follow the prompts on thescreen to activate the printer, andthen press any key to continue.
If the printer is activated, a copy ofthe session is printed.
The second Octel PC/CDR SystemData Directory Creation screen appears, similar to Figure 3-7.
3. To create the CDR system withoutprinting the process, press any key to continue.
The second Octel PC/CDR SystemData Directory Creation screen appears, similar to Figure 3-7.
4. Press any key to continue or pressCtrl–C to abort the MKCDRSYSutility.
If the process is to continue, a screensimilar to Figure 3-8 appears.
5. Make note of the instructions on thescreen about accessing files.
. . .
6. If printer output was activated in step2, press Ctrl–PrtSc to disable it.
If activated, the printer output isdeactivated.
7. Press any key to continue. The DOS prompt reappears.
Octel PC/CDR System Data Directory Creation
You must have DOS Version 3.2 or above before running this command. Your Current Version is:
MS-DOS Version 6.20
If you would like a printed copy of this session then
1) Make sure your printer is ready and “on line”
2) Press CTRL–PrtSc (Control PrintScreen)
3) Then strike a key to continue
If you enable printer output, and then press CTRL–C, you must press CTRL–PrtSc again to disable printer output.
Press any key to continue . . .
Figure 3-6. First Octel PC/CDR System DataDirectory Creation Screen.
SECTION 3.3
INSTALLATION PROCEDURES
Octel PC/CDR Edition 2 3-9
Octel PC/CDR System Data Directory Creation
About to create Octel PC/CDR System Data Directories and a Start Up Batch File:
Startup Batch File: “c:\OCTELCDR\westreg.BAT” Data Directories: “c:\westreg”
Press CTRL–C to AbortPress any key to continue . . .
Figure 3-7. Second Octel PC/CDR System DataDirectory Creation Screen.
Creating Octel PC/CDR System Start Up Batch File “c:\OCTELCDR\westreg.BAT”...
Creating Octel PC/CDR System Directories for System: westreg on Drive c: ...
System Directories and Start Up Batch File Created.
Type “westreg” to process Octel PC/CDR files for this system.
Type “CDRHELP” to see a list of all start-up batch files created.
If you enabled printer output at the beginning of this session, you should press CTRL–PrtSc now to disable it (then strike a key).
Press any key to continue . . .
Figure 3-8. Example of a System Creation Screen.
3.4 REMOVING CDR SYSTEM DATA SUBDIRECTORIES
The RMCDRSYS command removes a CDR system that was created using theMKCDRSYS command. This command deletes the access batch file for the CDRsystem and all files from the subdirectories for the designated CDR system. Itthen removes all of the subdirectories for the CDR system. Before removing aCDR system, back it up to a floppy disk (refer to Chapter 8 for instructions).
Use the RMCDRSYS command with the following syntax:
rmcdrsys [systemname] [datadrive:] [progdrive:]
where
rmcdrsys is the command to remove a CDR system from the PC hard drive.
systemname is the name of the CDR system to be removed.
datadrive: is the drive on which the designated CDR system subdirectoriesreside.
progdrive: is the PC hard drive onto which the Octel PC/CDR software wasinstalled.
For example,
To remove the westreg CDR system and its related subdirectories located ondrive C: (the same drive as the Octel PC/CDR software), type the following:
rmcdrsys westreg c: c:
SECTION 3.3 – 3.4
INSTALLATION PROCEDURES
3-10 Edition 2 Octel PC/CDR
Execute the RMCDRSYS command to remove a CDR system, as follows:
Step Action Result
1. Back up the CDR system subdirecto-ries to a floppy disk or tape forfuture reference, before they areremoved. Refer to Chapter 8 forinstructions.
. . .
2. At the DOS prompt, type theRMCDRSYS command using the correct syntax, and press Enter.
The following prompt appears:
About to delete CDR system directory “c:\[cdr system name]”and remove startup file “c:\OC-TELCDR\[cdr system name].BAT”
Press CTRL–C to abortPress any key to continue . . .
3. Press any key to delete the namedCDR system and all of its relatedfiles and subdirectories.
The DOS prompt reappears when thedeletion is complete.
4. After the CDR system has been deleted, remove its name from all automatic schedules in which it islisted (refer to section 7.5.1).
. . .
3.5 UPGRADING OCTEL PC/CDR SOFTWARE
If you are using an earlier release of Octel PC/CDR software, you might beinstructed to upgrade to the new release instead of performing a full installation.When upgrading the Octel PC/CDR software, the previously downloaded data forall CDR systems created using the MKCDRSYS remains unchanged; the newsoftware is copied over the old software. The Octel PC/CDR system attributesare not affected by the upgrade.
Before upgrading your Octel PC/CDR software, refer to section 3.5.1 for thingsyou should consider.
3.5.1 UPGRADE CONSIDERATIONS
Consider the following when performing an upgrade:
� Changes to output files can affect billing programs.
� CDR buffer download frequency and PC storage needs might change.
� The MKCDRSYS command needs to be executed for all CDR systems ifoutput files were added with the new software release.
SECTION 3.4 – 3.5
INSTALLATION PROCEDURES
Octel PC/CDR Edition 2 3-11
3.5.1.1 Effect of Output File Changes on Billing Programs. If you useOctel PC/CDR data to bill for server usage, changes to output files can affect theway CDR data interacts with the host billing program.
Caution!Changes made to output files with a new release of OctelPC/CDR software can affect the way CDR data interactswith host billing programs. Based on the information inthis manual, make the necessary changes to your billingapplication software before using the new CDR data.
Refer to Appendix A for field lengths and names that might have changed sincethe last release of Octel PC/CDR software, and make the necessary changes toyour billing-application software before using the new CDR data.
3.5.1.2 CDR Buffer Download Frequency and PC Storage Needs. Newreleases of Octel PC/CDR software sometimes contain new and modified events.
Caution!New and modified events in new releases of Octel PC/CDRsoftware can cause the CDR buffer to become full morequickly than with previous releases. Monitor the CDRbuffer daily to determine how quickly the buffer becomesfull, then perform downloads based on this new pattern toavoid losing data.
Changes to events can cause the CDR buffer to become full more quickly andthe downloaded data to take more space on the PC. After upgrading to a newrelease of Octel PC/CDR software, ensure that data is not lost by monitoring theCDR buffer frequently to become familiar with the new fill pattern, and allowingfor additional storage space requirements on the PC hard drive.
3.5.1.3 Requirement for New Output Files. If the Octel PC/CDR softwareupgrade has new output files, make sure to rerun the MKCDRSYS command(described in section 3.3) for all existing CDR systems to create CDR systemsubdirectories for the new output files. Files in the existing subdirectories arenot affected.
SECTION 3.5
INSTALLATION PROCEDURES
3-12 Edition 2 Octel PC/CDR
3.5.2 UPGRADE PROCEDURE
The procedure to upgrade the Octel PC/CDR software is similar to the initialsoftware installation. Upgrade the software, as follows:
Step Action Result
1. Turn on the CDR PC. The DOS prompt appears.
2. Insert the Octel PC/CDR software diskinto a compatible disk drive on theCDR PC.
. . .
3. At the DOS prompt, type the letter ofthe drive containing the Octel PC/CDRdisk, followed by a colon, and pressEnter. For example,
If the disk is inserted into drive one,type a: at the DOS prompt, andpress Enter.
The prompt changes to the desig-nated drive. For example, A:\>.
4. At the designated-drive DOS prompt,type upgrcdr, and press Enter.
The Octel PC/CDR Upgrade Programmenu appears, with default values,as shown in Figure 3-9. The defaultvalues are generally used for anupgrade, but they should always beverified.
5. Use the information in Figure 3-9 andTable 3-4 to determine the correct val-ue for each field. As necessary, movethe cursor to the appropriate field andtype in the new value.
. . .
Octel PC/CDR Upgrade Program(C) Copyright 1988–1996 Octel Communications Corporation
Source Drive Name : A:Boot Drive Name : C:Destination Drive Name : C:Update autoexec.bat & config.sys? : NUpgrade Octel PC/CDR Software? : Y
F1 – Help F10 – Proceed ESC – Cancel/Quit
Figure 3-9. Octel PC/CDR Upgrade Program Menu.
SECTION 3.5
INSTALLATION PROCEDURES
Octel PC/CDR Edition 2 3-13
Table 3-4. Octel PC/CDR Upgrade Program Menu Fields.
Field Description
Source DriveName:
Shows the drive being used to read the Octel PC/CDR softwareupgrade disk and display this menu. This field cannot bechanged.
Boot Drive Name: Shows from which drive the PC boots. This is the PC hard driveon which the CONFIG.SYS and AUTOEXEC.BAT files arelocated. To change the default of C:, type the boot drive letter,followed by a colon. For example, type d:.
Destination DriveName:
Specifies the drive onto which the Octel PC/CDR software isbeing upgraded. This destination must be a hard drive or a partof a hard drive with at least 2.2 MB currently available. (Addi-tional storage space is required for downloaded and processedfiles. Refer to section 2.3 for details.) To change the default of C:,type the destination drive letter, followed by a colon. For example, type d:.
Updateautoexec.bat &config.sys?:
Questions whether the PC boot files (AUTOEXEC.BAT and CONFIG.SYS) should be altered. Leave this field with the defaultof Y.
Upgrade Octel PC/CDR Software?:
Questions whether the Octel PC/CDR software should beupgraded. Leave the default of Y to upgrade the Octel PC/CDRsoftware.
SECTION 3.5
INSTALLATION PROCEDURES
3-14 Edition 2 Octel PC/CDR
Complete the installation, as follows:
Step Action Result
1. To proceed when all field changesare complete, press F10.
A screen similar to Figure 3-10appears, with the following prompt:Proceed with Upgrade? [y/n]
2. Press Y. The software upgrade begins.
As each file is upgraded, the filename appears on the screen; as thescreen fills, data scrolls off the top ofthe screen.
After the software is upgraded, theDOS prompt reappears.
3. Remove the disk from the sourcedrive and store it in a safe place.
. . .
4. Restart the PC by pressing the Ctrl,Alt, and Del keys simultaneously toupdate the AUTOEXEC.BAT andCONFIG.SYS files.
The PC reboots and new files areloaded into the PC memory duringthe PC boot process.
5. If new output files were added withthis Octel PC/CDR software release,rerun the MKCDRSYS command forall CDR systems. Files in the existingCDR system subdirectories are notaffected.
New CDR system subdirectories arecreated for the new output files.
This program is about to perform the following:
Upgrade Octel PC/CDR Software on Drive “C:”
The Source Drive is “A:”
Proceed with Upgrade? [y/n]
Figure 3-10. Upgrade Octel PC/CDR System Screen.
SECTION 3.5
O C T E L
P C / C D R
EQUIPMENT REQUIREMENTSAND CONFIGURATION
C O N T E N T S
4-iiiEdition 2Octel PC/CDR
CHAPTER 4
4.1 OVERVIEW 4-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2 PC REQUIREMENTS 4-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3 SOFTWARE REQUIREMENTS 4-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4 SERVER-TO-PC CONNECTORS 4-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5 EQUIPMENT CONFIGURATION FOR THE OCTEL OVERTURE 250 AND 350 4-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.1 IDENTIFY THE SERVER CHANNEL 4-7. . . . . . . . . . . . . . . . . . . . . . .
4.5.2 ESTABLISH THE SERVER CHANNEL 4-7. . . . . . . . . . . . . . . . . . . . .
4.5.3 CONNECT THE CABLES AND COMPLETE THE MENU 6.3 CONFIGURATION 4-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.4 VERIFY MENU 6.3 CHANGES 4-11. . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.5.5 ESTABLISH OCTEL PC/CDR ATTRIBUTES FOR COMMUNICATION WITH SERVER 4-11. . . . . . . . . . . . . . . . . . . . . . . .
4.5.6 CHECK SERVER-MODEM CONFIGURATION 4-11. . . . . . . . . . . . .
4.6 EQUIPMENT CONFIGURATION FOR THE BRANCH, BRANCH XP, ASPEN, MAXUM SE, AND MAXUM 4-12. . . . . . . . . . . . . . . .
4.6.1 USE SEPARATE PORTS FOR SMT AND PC (ASPEN SOFTWARE RELEASES 1.5X AND NEWER) 4-13. . . . . . . . . . . . . .
4.6.1.1 Identify the Voice-Processor Channel 4-14. . . . . . . . . . .
4.6.1.2 Establish the Voice-Processor Channel 4-14. . . . . . . . .
4.6.1.3 Connect the Cables and Complete the Menu 6.3 Configuration 4-17. . . . . . . . . . . . . . . . . . . . . . . .
4.6.1.4 Verify Menu 6.3 Changes 4-17. . . . . . . . . . . . . . . . . . . . . . .
4.6.1.5 Establish Octel PC/CDR Attributes for Communication With the Voice Processor 4-17. . . . . .
4.6.1.6 Check Voice-Processor Modem Configuration 4-17. . .
4.6.2 USE A SHARED PORT FOR SMT AND PC (ASPEN SOFTWARE RELEASES 1 THROUGH 1.3X) 4-17. . . . . . . . . . . . . . .
Section Page
C O N T E N T S
4-iv Edition 2 Octel PC/CDR
4.7 EQUIPMENT CONFIGURATION FOR THE OCTEL XC1000 4-18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7.1 USE SEPARATE PORTS FOR SMT AND PC (ASPEN SOFTWARE RELEASES 1.5X AND NEWER). 4-19. . . . . . . . . . . . . .
4.7.1.1 Identify the Channel on the Octel XC1000 4-20. . . . .
4.7.1.2 Establish the Channel on the Octel XC1000 4-20. . . .
4.7.1.3 Connect the Cables and Complete the Menu 6.3 Configuration 4-23. . . . . . . . . . . . . . . . . . . . . . . .
4.7.1.4 Verify Menu 6.3 Changes 4-23. . . . . . . . . . . . . . . . . . . . . . .
4.7.1.5 Establish Octel PC/CDR Attributes for Communication With the Octel XC1000 4-23. . . . . . . .
4.7.1.6 Check Octel XC1000 Modem Configuration 4-23. . . . .
4.7.2 USE A SHARED PORT FOR SMT AND PC (ASPEN SOFTWARE RELEASES 1 THROUGH 1.3X). 4-23. . . . . . . . . . . . . .
TABLESTable 4-1. Parts for the Server-to-PC Connection 4-4. . . . . . . . . . . . . . . . . . .
Table 4-2. Overview of Equipment Configuration Procedures for Octel Overture 250 and 350 4-7. . . . . . . . . . . . . . . . . . . . . . . . .
Table 4-3. Overview of Equipment Configuration Procedures for Voice Processors at Aspen Software Releases 1.5X and Newer 4-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 4-4. Overview of Equipment Configuration Procedures for Octel XC1000 4-20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Section Page
C O N T E N T S
4-vEdition 2Octel PC/CDR
FIGURESFigure 4-1. Example of Direct and Modem Connections Between
the CCF Card on the Octel Overture 250 Message Server and the CDR PC 4-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 4-2. Example of Direct and Modem Connections Between the Octel Overture 350 Message Server and the CDR PC 4-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 4-3. SMT Main Menu for the Octel Overture 250 4-9. . . . . . . . . . . . .
Figure 4-4. Menu 6 – Dialing and Serial Channel Parameters for the Octel Overture 250 4-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 4-5. Example of Menu 6.3 for the Octel Overture 250 4-10. . . . . . .
Figure 4-6. Example of Menu 6.3 for the Octel Overture 350 4-10. . . . . . .
Figure 4-7. Example of Direct and Modem Connections for Aspen Software Releases 1.5X and Newer 4-12. . . . . . . . . . . . . . .
Figure 4-8. Example of Direct and Modem Connections for Aspen Software Releases 1 through 1.3X 4-13. . . . . . . . . . . . . . .
Figure 4-9. SMT Main Menu for Voice Processors With Aspen Release 4.1 4-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 4-10. Menu 6 – Dialing and Serial Channel Parameters for Voice Processors With Aspen Release 4.1 4-16. . . . . . . . . . . .
Figure 4-11. Example of Menu 6.3 for Voice Processors With Aspen Software Release 4.1 4-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 4-12. Example of Direct and Modem Connections Between the Octel XC1000 and the CDR PC for Aspen Software Releases 1.5X and Newer 4-18. . . . . . . . . . . . . . . . . . . . . .
Figure 4-13. Example of Direct and Modem Connections Between the Octel XC1000 and the CDR PC for Aspen Software Releases 1 through 1.3X 4-19. . . . . . . . . . . . . . . . . . . . . .
Figure 4-14. SMT Main Menu for the Octel XC1000 4-22. . . . . . . . . . . . . . . . .
Figure 4-15. Menu 6 – Dialing and Serial Channel Parameters for the Octel XC1000 4-22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 4-16. Example of Menu 6.3 for the Octel XC1000 4-22. . . . . . . . . . . . .
Page
C H A P T E R 4
Octel PC/CDR Edition 2 4-1
EQUIPMENT REQUIREMENTS AND CONFIGURATION
4.1 OVERVIEW
The Octel PC/CDR software package requires a dedicated PC that is connected tothe server with a modem or a direct connection. If the distance between theserver and the PC is more than 50 feet, communication between the server andthe PC requires a modem. Otherwise, use a direct connection with a data cable.
For the Octel PC/CDR software package to work correctly, the PC must meet theminimum requirements listed in sections 4.2 and 4.3 and must be correctlyconnected to the server. The server must then be configured so that the connec-tion to the PC is recognized and downloads of CDR data can be performed.Section 4.4 describes server-to-PC connectors. The following sections describehow to configure the different Octel servers:
Server Section
Overture 250 and 350 Message Servers 4.5
Branch, Branch XP, Aspen, Maxum SE,and Maxum
4.6
Octel XC1000 4.7
Instructions about connecting the server to the PC, to be performed by Octel-trained technicians, are found in Chapter 11.
4.2 PC REQUIREMENTS
Consider the following requirements when purchasing a PC for use with OctelPC/CDR:
� For optimum performance, Octel recommends at least a 486 PC, IBM orIBM-compatible, with a 500-megabyte internal drive. For higher volumeservers, Octel recommends a Pentium PC with a 1-gigabyte internal drive.Refer to Chapter 2 for PC sizing information.
Although the Octel PC/CDR software package runs on IBM-compatible PCs,the differences between computers and operating systems could preventsuccessful operation on some IBM-compatible PCs.
EQUIPMENT REQUIREMENTS AND CONFIGURATION
4-2 Edition 2 Octel PC/CDR
� The PC must be dedicated to the Octel PC/CDR program.
� The PC must have the following features:
� Two RS-232 serial ports, as follows:
� One for the CDR PC-to-server connection (using a direct connection,internal modem, or external modem)
� One for the CDR PC-to-service PC connection (using a separateservice modem on the CDR PC to communicate with the service PC,as explained in Chapter 6)
� A high-capacity 31/2-inch disk drive.
� A real-time clock with internal-battery backup.
� One or two modems, as follows:
� If the distance between the PC and the server is more than 50 feet, amodem is required for PC-to-server communication. The baud rate ofthis modem must match the baud rate of the server. Most Hayes andHayes-compatible modems can be used.
� Another modem is required for service communications. The baudrate of this modem must match the baud rate of the server. (Refer toChapter 6 for information about using the service modem.)
Customers are responsible for modem communication and compatibility.Octel Communications does not endorse specific brands nor does it provideservice for peripheral equipment, unless this equipment was purchasedthrough Octel. Installation of modem equipment is the responsibility of thecustomer.
� IBM DOS or MS-DOS, version 3.2, 3.3, 4.01, 5.0, or 6.2; for largedata-storage requirements, the specific version of DOS must be capableof addressing large partition sizes, above 35 megabytes.
DOS releases 5.0 and lower include a backup file that is required by theOctel PC/CDR backup utilities (as described in Chapters 7 and 8). Whenusing DOS 6.2 or higher, Octel PC/CDR backup utilities might not work.Consider the following configurations:
� If the PC with the Octel PC/CDR software is upgraded to DOS 6.2,the backup file from the earlier installation of DOS 5.0 or lowerremains on the hard drive. The Octel PC/CDR backup utilities shouldwork as described in Chapters 7 and 8.
� If a new PC has DOS 6.2 and that PC is used for Octel PC/CDR, theOctel PC/CDR backup utilities will not work. The backup file isrequired for these utilities, and it is not included with DOS 6.2. If youare using the new-installation version of DOS 6.2, you must use analternative method to back up the Octel PC/CDR files.
� A parallel port (optional) might be required if a printer is used.
SECTION 4.2
EQUIPMENT REQUIREMENTS AND CONFIGURATION
Octel PC/CDR Edition 2 4-3
� Cables and connectors are required, depending on the needs of yourPC-to-server connection. Refer to section 4.4 for details.
� The following hardware is optional:
� 80- or 132-column printer
� Asynchronous, serial data switch (RS-232)
� Streamer-tape-backup unit
4.3 SOFTWARE REQUIREMENTS
The following software is required for Octel PC/CDR:
� The Octel PC/CDR software package, which contains the following components:
� Octel PC/CDR (CDR processing and data communication software)
� Carbon Copy PLUS (remote-maintenance communication software)
� MIRROR II (data communication software)
All three of these programs are installed when the Octel PC/CDR installcommand is executed (as described in Chapter 3).
� Server software at the correct release, depending on the type of server, asfollows:
Server Type Software Requirement
Octel Overture 250 and 350 messageservers
Octel Aria 1.0 or newer messagingsoftware
Branch, Branch XP, Aspen, Maxum SE,Maxum, and Octel XC1000
Aspen software Release 1.0 or newer
� Optional database or application software that works with dBASE III orASCII-based files, provided by the customer. This software is necessary if thecustomer wants to sort data or generate reports.
SECTION 4.2 – 4.3
EQUIPMENT REQUIREMENTS AND CONFIGURATION
4-4 Edition 2 Octel PC/CDR
4.4 SERVER-TO-PC CONNECTORS
The server is connected to the PC either with a direct connection or by modem. If the PC and the server are more than 50 feet apart, a modem connection isrequired. The parts required for the direct or modem connection vary, dependingon the customer’s needs and equipment. Table 4-1 shows parts that could beneeded for the server-to-PC connection. Some of the parts are included in theOctel PC/CDR software package.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table 4-1. Parts for the Server-to-PC Connection.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Type of ConnectionÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Suggested Parts
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Direct ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ� 9-pin to 25-pin female-to-female adapter
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ� 25-pin female-to-female gender changerÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ� 25-pin to 25-pin or 9-pin to 25-pin
male-to-male data cableÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ� Null modem
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Modem (configuration varies)
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
� Modem (if over 50 feet between theserver and the CDR PC)
� Modem for service communications
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ� Modem cables and connectors
4.5 EQUIPMENT CONFIGURATION FOR THE OCTELOVERTURE 250 AND 350
For the Octel Overture 250 or 350 message server to be able to communicatewith the CDR PC, the server must be connected to the CDR PC and correctlyconfigured.
Figure 4-1 and Figure 4-2 show the physical-connection requirements for theOctel Overture 250 and 350 message servers, respectively. The physicalconnection is explained in this section and in Chapter 11. Refer to Chapter 11for detailed installation tasks to be performed by Octel-trained technicians only.
Warning!To avoid dangerous electrical shock, do not performservice-related procedures unless you are qualified to doso. Only Octel-trained technicians are allowed to open theserver cabinet and perform service-related tasks.
SECTION 4.4 – 4.5
EQUIPMENT REQUIREMENTS AND CONFIGURATION
Octel PC/CDR Edition 2 4-5
000226
OCTEL OVERTURE 250
NULL MODEM
CDR PC
MODEM
CCF CARD
LAN
SY
NC
CO
NS
OLE
AS
YN
C 1
AS
YN
C 2
MO
DE
M
TEMP
CALL
PWR
RST
SA
YELIN
DS3DS4DS5
ERRNSA
OOS
REDOUT
0DS1DS2DS
CONNECTION
MODEM
CCF CARD
SYSTEM MANAGERTERMINAL
SERVICEMODEM
DIRECT CONNECTION
PRINTER
AS
YN
C 3
DATA CABLE
SERVERMODEMCDR PC
Figure 4-1. Example of Direct and Modem ConnectionsBetween the CCF Card on the Octel Overture 250
Message Server and the CDR PC.
SECTION 4.5
EQUIPMENT REQUIREMENTS AND CONFIGURATION
4-6 Edition 2 Octel PC/CDR
CDR PC
MODEMCONNECTION
SYSTEM MANAGERTERMINAL
SERVICEMODEM
DIRECT CONNECTION
PRINTER
DATA CABLE
OCTEL OVERTURE 350
DISTRIBUTION PANEL
MODEMSERVER
MODEMCDR PC
NULL MODEM
J43
J44J46
Figure 4-2. Example of Direct and Modem Connections Between theOctel Overture 350 Message Server and the CDR PC.
Refer to Table 4-2 for the steps required to establish a direct or modem connec-tion between the server and the PC. The system manager or Octel-trainedtechnician performs steps 2, 4, and 5. Steps 1, 3, and 6 are performed only byOctel-trained technicians. These steps are described in detail in Chapter 11. Workwith the Octel-trained technician to perform these steps in sequence.
Instructions and screens in this section apply to servers with Aria 1.2 messagingsoftware. Instructions and screens for other releases are similar.
SECTION 4.5
EQUIPMENT REQUIREMENTS AND CONFIGURATION
Octel PC/CDR Edition 2 4-7
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table 4-2. Overview of Equipment Configuration Procedures for Octel Overture 250 and 350.
ÁÁÁÁÁÁÁÁ
StepÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
TaskÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Performed ByÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
DescribedÁÁÁÁÁÁÁÁÁÁÁÁ
1.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Identify the server channel.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Octel-trained technicianÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Section 11.2ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
2.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Establish the channel on theserver.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
System manager or Octel-trained technician
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Section 4.5.2
ÁÁÁÁÁÁÁÁÁÁÁÁ
3. ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Connect the cables and completethe menu 6.3 configuration.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Octel-trained technician ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Section 11.4
ÁÁÁÁÁÁÁÁÁÁÁÁ
4. ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Verify menu 6.3 changes. ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
System manager or Octel-trained technician
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Section 4.5.4
ÁÁÁÁÁÁÁÁÁÁÁÁ
5. ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Establish Octel PC/CDR attrib-utes for communication with theserver.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
System manager or Octel-trained technician
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Section 4.5.5
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
6.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Check the configuration of theserver modem.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Octel-trained technician
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Section 11.7
4.5.1 IDENTIFY THE SERVER CHANNEL
This step is performed by the Octel-trained technician. Refer to section 11.2 fordetails.
4.5.2 ESTABLISH THE SERVER CHANNEL
Establish the server channel identified by the Octel-trained technician in section11.2, as follows:
ÁÁÁÁÁÁÁÁÁÁÁÁ
StepÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ActionÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Result
ÁÁÁÁÁÁÁÁÁÁÁÁ
1. ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
From the SMT Main Menu, shown inFigure 4-3, select option 6, and pressReturn.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Menu 6 – Dialing and Serial Chan-nel Parameters appears, similar tothe screen shown in Figure 4-4.ÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
2.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Select option 3, and press Return.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Menu 6.3, Define CPU Serial Chan-nel, appears with a summary tableand the Channel Number To BeDefined: field displayed.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
3.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
In the Channel Number To Be Defined: field, enter the number of the channel that was identified in section 11.2.
� For the 250 server, enter one of thefollowing, then press Return:1 – Async12 – Async23 – Async3
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
The Channel Type: field appears. Ifthe selected channel was previouslydefined, the remaining fields appear,similar to the screen shown inFigure 4-5 (for the Octel Overture250) or Figure 4-6 (for the OctelOverture 350).
SECTION 4.5
EQUIPMENT REQUIREMENTS AND CONFIGURATION
4-8 Edition 2 Octel PC/CDR
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ResultÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ActionÁÁÁÁÁÁÁÁÁÁÁÁ
Step
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
� For the 350 server, enter one of thefollowing, then press Return:1 – J442 – J433 – J46
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
4. ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
In the Channel Type: field, enter 1 forthe system terminal. Press Return.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
If not already displayed, the remain-ing menu 6.3 fields appear(Figure 4-5 for the Octel Overture250 or Figure 4-6 for the OctelOverture 350). The cursor moves tothe CPU Baud Rate: field.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
5. ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
In the CPU Baud Rate: field, enter thenumber that corresponds to the baudrate used by the Octel PC/CDR soft-ware:
1 - 1200 Baud2 - 9600 Baud3 - 19200 Baud
Press Return.
The baud rate that you enter here mustmatch the baud rate established for theOctel PC/CDR software. (Refer to Chap-ter 5 for information about setting thebaud rate for the PC.)
Octel recommends that downloads beperformed at 9600 baud. If the entry inthis field is 3 (19200 baud), a CDRdownload could fail.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
The cursor moves to the Type ofTerminal on This Channel: field.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
6.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
In the Type of Terminal on ThisChannel: field, enter the type of termi-nal used for communication betweenthe PC and the server. This entry mustagree with the Terminal Emulation Typeentered in the Modify PC Communica-tions Parameters screen of the OctelPC/CDR software (section 5.3.7).
If the Octel PC/CDR terminal-emulationtype is
� WY50SPEC, choose 1 for the Wyse50 or HP 700/43.
� ANSI, choose 2 for the AT&T4425/5425.
� VT100, choose 3 for the DECVT102/220.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
The description corresponding to the selected entry appears in the Type of Terminal on ThisChannel: field.
SECTION 4.5
EQUIPMENT REQUIREMENTS AND CONFIGURATION
Octel PC/CDR Edition 2 4-9
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ResultÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ActionÁÁÁÁÁÁÁÁÁÁÁÁ
Step
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
7. ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Press the SEND key to save thechanges.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
The Channel Number To BeDefined: field reappears. Changesmade to menu 6.3 are not recognizedby the server until the server is shutdown and rebooted by the Octel-trained technician, as described insection 11.4.ÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
8.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Press Return twice to return to theMain Menu.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
The Main Menu reappears(Figure 4-3).
Main Menu
System Management
11 – System Distribution Lists12 – Disk Management13 – System Maintenance14 – System Reports15 – Network Management16 – Database Access17 – External Application Mgnt18 – X.25 Interface Management19 – Not Applicable20 – Service Operations21 – System Backup and Restore
Enter Menu Selection Number:
Copyrights (C) 1984 – 1995, Octel Communications Corporation
General System Parameters
1 – System Parameters 2 – Attendant Schedules, Port Monitoring 3 – Set Date/Time 4 – Port Assignments 5 – Outcalling Parameters 6 – Dialing Parameters
Mailboxes
7 – Change Class of Service Profile 8 – Add Mailbox 9 – Change Mailbox10 – Delete Mailbox
westreg
Figure 4-3. SMT Main Menu for the Octel Overture 250.
Enter Option:
Menu 6 - Dialing and Serial Channel Parameters
1 – Transfer, Outcall, Fax, and Pager Dialing Sequences
2 – In-band Integration Dialing Sequences
3 – Define CPU Serial Channel
4 - MTA (Multiple Terminal Access) Parameters
5 - Integration Link Management
westreg
Figure 4-4. Menu 6 – Dialing and Serial ChannelParameters for the Octel Overture 250.
SECTION 4.5
EQUIPMENT REQUIREMENTS AND CONFIGURATION
4-10 Edition 2 Octel PC/CDR
Menu 6 - Dialing and Serial Channel Parameters- Define CPU Serial Channel -
Channel Active Type Console Stored Type Console1 – Async12 – Async23 – Async3 SMT SMT4 – Console Service Y Service Y
Channel Number To Be Defined: 1
Channel Type: 1 - System Terminal
CPU Baud Rate:Type of Terminal on This Channel:
Press the ’Send’ key to save changes.
westreg
Figure 4-5. Example of Menu 6.3 for theOctel Overture 250.
Menu 6 - Dialing and Serial Channel Parameters- Define CPU Serial Channel -
Channel Active Type Console Stored Type Console 1–J44 SMT SMT 2–J43 3-J46 4–J50 Service Y Service Y
Channel Number To Be Defined: 1Channel Type: 1 - System TerminalCPU Baud Rate: 2 – Type of Terminal on This Channel:
Press the ’Send’ key to save changes.
westreg
Figure 4-6. Example of Menu 6.3 for theOctel Overture 350.
SECTION 4.5
EQUIPMENT REQUIREMENTS AND CONFIGURATION
Octel PC/CDR Edition 2 4-11
4.5.3 CONNECT THE CABLES AND COMPLETE THEMENU 6.3 CONFIGURATION
This step is performed by the Octel-trained technician. Refer to section 11.4 fordetails.
4.5.4 VERIFY MENU 6.3 CHANGES
You or the Octel-trained technician must verify that the server is operational andthat the changes made to menu 6.3 were accepted by the server, as follows:
ÁÁÁÁÁÁÁÁÁ
StepÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ActionÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Result
ÁÁÁÁÁÁÁÁÁÁÁÁ
1.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
From the SMT Main Menu(Figure 4-3), select option 6, andpress Return.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Menu 6 – Dialing and Serial ChannelParameters appears (Figure 4-4).
ÁÁÁÁÁÁÁÁÁ
2.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Select option 3, and press Return. ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Menu 6.3, Define CPU Serial Channel,appears with the Channel Number ToBe Defined: field displayed.ÁÁÁ
ÁÁÁÁÁÁÁÁÁ
3.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Confirm that the entries for the config-ured channel in both the Active Typeand Stored Type columns read SMT.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
. . .
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
If the Active Type column is blank forthe configured channel, but theStored Type column displays SMT,the reboot process was not successful.The Octel-trained technician must re-peat steps 1 and 4 from section 11.4to shut down and reboot the server.Then repeat the steps in this proce-dure to verify the configuration.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁ
4.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Press Return twice to return to theMain Menu.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
The Main Menu reappears(Figure 4-3).
4.5.5 ESTABLISH OCTEL PC/CDR ATTRIBUTES FORCOMMUNICATION WITH SERVER
You or the Octel-trained technician must establish the Octel PC/CDR attributesfor linking the PC with the server. Follow the instructions given in Chapter 5.
4.5.6 CHECK SERVER-MODEM CONFIGURATION
This step is performed by the Octel-trained technician. Refer to section 11.7 fordetails.
SECTION 4.5
EQUIPMENT REQUIREMENTS AND CONFIGURATION
4-12 Edition 2 Octel PC/CDR
4.6 EQUIPMENT CONFIGURATION FOR THE BRANCH,BRANCH XP, ASPEN, MAXUM SE, AND MAXUM
For a Branch, Branch XP, Aspen, Maxum SE, or Maxum to be able to communi-cate with the CDR PC, the Branch, Branch XP, Aspen, Maxum SE, or Maxummust be connected to the CDR PC and correctly configured.
Figure 4-7 and Figure 4-8 show the physical-connection requirements for thevoice processor*-to-PC connection. Depending on the Aspen software release inuse, the PC can either be connected to a separate port on the voice processor(Figure 4-7), or it can share a port with the SMT on the voice processor(Figure 4-8). These two connections are described in sections 4.6.1, 4.6.2, andChapter 11. Refer to Chapter 11 for detailed installation instructions to beperformed by Octel-trained technicians only. Refer to section 4.4 for informationabout the required cables and connectors.
Warning!To avoid dangerous electrical shock, do not performservice-related procedures unless you are qualified to doso. Only Octel-trained technicians are allowed to open thevoice processor cabinet and perform service-related tasks.
SCANNERBOARD
CDR PCMODEM
SERVICEMODEM
PRINTER
SYSTEM MANAGERTERMINAL
CDR PC
DATA CABLE
9- OR 25-PINADAPTER
NULL MODEM
VOICE PROCESSOR
MODEMCONNECTION
DIRECT CONNECTION
MODEMVOICE-PROCESSOR
Figure 4-7. Example of Direct and Modem Connections for Aspen Software Releases 1.5X and Newer.
* In this chapter, the term voice processor refers collectively to the Branch, Branch XP, Aspen, Maxum SE,and Maxum servers.
SECTION 4.6
EQUIPMENT REQUIREMENTS AND CONFIGURATION
Octel PC/CDR Edition 2 4-13
A
B
MODEM MODEM
SERVICEMODEM
PRINTER
SYSTEM MANAGERTERMINAL
CDR PC
SMT DATA CABLE
DATA SWITCH(OPTIONAL)
9- OR 25-PINADAPTER
NULL MODEMMODEM
VOICE PROCESSOR
SCANNERBOARD
CONNECTION
DIRECT CONNECTION
CDR PCVOICE-PROCESSOR
Figure 4-8. Example of Direct and Modem Connections forAspen Software Releases 1 through 1.3X.
4.6.1 USE SEPARATE PORTS FOR SMT AND PC (ASPENSOFTWARE RELEASES 1.5X AND NEWER)
With Aspen software Releases 1.5X and newer, the SMT and the CDR PC can beconnected to separate ports on the voice processor and can be operated at thesame time.
Warning!To avoid dangerous electrical shock, do not performservice-related procedures unless you are qualified to doso. Only Octel-trained technicians are allowed to open thevoice processor cabinet and perform service-related tasks.
Refer to Table 4-3 for the steps required to establish a direct or modem connec-tion between the voice processor and the PC. The system manager or Octel-trained technician performs steps 2, 4, and 5. Steps 1, 3, and 6 are performedonly by Octel-trained technicians. These steps are described in detail in Chapter11. Work with the Octel-trained technician to perform these steps in sequence.
Instructions and screens in this section apply to Aspen software Release 4.1.Instructions and screens for other releases are similar.
SECTION 4.6
EQUIPMENT REQUIREMENTS AND CONFIGURATION
4-14 Edition 2 Octel PC/CDR
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table 4-3. Overview of Equipment Configuration Procedures for VoiceProcessors at Aspen Software Releases 1.5X and Newer.
ÁÁÁÁÁÁÁÁ
StepÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
TaskÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Performed ByÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
DescribedÁÁÁÁÁÁÁÁÁÁÁÁ
1.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Identify the voice-processorchannel.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Octel-trained technicianÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Section 11.2
ÁÁÁÁÁÁÁÁÁÁÁÁ
2.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Establish the channel on the voice processor.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
System manager or Octel-trained technician
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Section 4.6.1.2
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
3.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Connect the cables and com-plete the menu 6.3 configura-tion.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Octel-trained technicianÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Section 11.4
ÁÁÁÁÁÁÁÁÁÁÁÁ
4.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Verify menu 6.3 changes.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
System manager or Octel-trained technician
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Section 4.6.1.4
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
5.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Establish Octel PC/CDR attributes for communication with the voice processor.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
System manager or Octel-trained technician
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Section 4.6.1.5
ÁÁÁÁÁÁÁÁÁÁÁÁ
6.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Check the configuration of thevoice-processor modem.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Octel-trained technicianÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Section 11.7
4.6.1.1 Identify the Voice-Processor Channel. This step is performed bythe Octel-trained technician. Refer to section 11.2 for details.
4.6.1.2 Establish the Voice-Processor Channel. Establish the voice-processor channel identified by the Octel-trained technician in section 11.2, asfollows:
ÁÁÁÁÁÁÁÁÁÁÁÁ
StepÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ActionÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Result
ÁÁÁÁÁÁÁÁÁÁÁÁ
1. ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
From the SMT Main Menu, similar tothe screen shown in Figure 4-9, selectoption 6, and press Return.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Menu 6 – Dialing and Serial Chan-nel Parameters appears, similar tothe screen shown in Figure 4-10.ÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
2.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Select option 3, and press Return.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Menu 6.3, Define CPU Serial Chan-nel, appears with only the ChannelNumber To Be Defined: field displayed.ÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
3.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
In the Channel Number To Be Defined: field, enter the number of the channel that was identified in section 11.2, and press Return.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
The Channel Type: field appears. Ifthe selected channel was previouslydefined, the remaining fields appear,similar to the screen shown inFigure 4-11.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
4.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
In the Channel Type: field, enter 1 forthe system terminal, and press Return.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
If not already displayed, the remaining menu 6.3 fields appear(Figure 4-11). The cursor moves tothe CPU Baud Rate: field.
SECTION 4.6
EQUIPMENT REQUIREMENTS AND CONFIGURATION
Octel PC/CDR Edition 2 4-15
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ResultÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ActionÁÁÁÁÁÁÁÁÁÁÁÁ
Step
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
5. ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
In the CPU Baud Rate: field, enter thenumber that corresponds to the baudrate used by the Octel PC/CDR soft-ware:
1 - 1200 Baud2 - 9600 Baud3 - 19200 Baud
Press Return.
The baud rate that you enter here mustmatch the baud rate established for theOctel PC/CDR software. (Refer to sec-tion 5.3.7 for information about settingthe baud rate for the PC.)
Octel recommends that downloads beperformed at 9600 baud. If the entry inthis field is 3 (19200 baud), a CDRdownload could fail.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
The cursor moves to the Type ofTerminal on This Channel: field.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
6.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
In the Type of Terminal on ThisChannel: field, enter the type of termi-nal used for communication betweenthe PC and the voice processor. Thisentry must agree with the TerminalEmulation Type entered in the ModifyPC Communications Parameters screenof the Octel PC/CDR software (section5.3.7).
If the Octel PC/CDR terminal-emulationtype is
� WY50SPEC, choose 1 for the Wyse50 or HP 700/43.
� ANSI, choose 2 for the AT&T4425/5425.
� VT100, choose 3 for the DECVT102/220.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
The description corresponding to the selected entry appears in the Type of Terminal on ThisChannel: field.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
7.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Press the SEND key to save thechanges.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
The Channel Number To BeDefined: field reappears. Changesmade to menu 6.3 are not recognizedby the voice processor until the voiceprocessor is shut down and rebootedby the Octel-trained technician, asdescribed in section 11.4.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
8.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Press Return twice to return to theMain Menu.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
The Main Menu reappears(Figure 4-3).
SECTION 4.6
EQUIPMENT REQUIREMENTS AND CONFIGURATION
4-16 Edition 2 Octel PC/CDR
Main Menu
System Management
11 – System Distribution Lists12 – Disk Management13 – System Maintenance14 – System Reports15 – Network Management16 – Database Access17 – External Application Mgnt18 – X.25 Interface Management19 – Cluster Configuration20 – Service Operations
Enter Menu Selection Number:
Copyrights (C) 1984 – 1994, Octel Communications Corporation
General System Parameters
1 – System Parameters 2 – Attendant Schedules, Port Monitoring 3 – Set Date/Time 4 – Port Assignments 5 – Outcalling Parameters 6 – Dialing Parameters
Mailboxes
7 – Change Class of Service Profile 8 – Add Mailbox 9 – Change Mailbox10 – Delete Mailbox
Figure 4-9. SMT Main Menu for Voice ProcessorsWith Aspen Release 4.1.
Enter Option:
Menu 6 - Dialing and Serial Channel Parameters
1 – Transfer, Outcall, Fax, and Pager Dialing Sequences2 – In-band Integration Dialing Sequences3 – Define CPU Serial Channel
Figure 4-10. Menu 6 – Dialing and Serial ChannelParameters for Voice Processors
With Aspen Release 4.1.
Menu 6 - Dialing and Serial Channel Parameters- Define CPU Serial Channel -
Channel Active Type Console Stored Type Console1234 – Console Service Y Service Y
Channel Number To Be Defined: 1
Channel Type: 1 - System Terminal
CPU Baud Rate:Type of Terminal on This Channel:
Press the ’Send’ key to save changes.
Figure 4-11. Example of Menu 6.3 for VoiceProcessors With Aspen Software Release 4.1.
SECTION 4.6
EQUIPMENT REQUIREMENTS AND CONFIGURATION
Octel PC/CDR Edition 2 4-17
4.6.1.3 Connect the Cables and Complete the Menu 6.3 Configuration. Thisstep is performed by the Octel-trained technician. Refer to section 11.4 for details.
4.6.1.4 Verify Menu 6.3 Changes. You or the Octel-trained technician mustverify that the voice processor is operational and that the changes made to menu6.3 were accepted by the voice processor, as follows:
ÁÁÁÁÁÁÁÁÁ
StepÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ActionÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Result
ÁÁÁÁÁÁÁÁÁ
1.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
From the SMT Main Menu(Figure 4-9), select option 6, and press Return.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Menu 6 – Dialing and Serial ChannelParameters appears (Figure 4-10).
ÁÁÁÁÁÁÁÁÁÁÁÁ
2.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Select option 3, and press Return.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Menu 6.3, Define CPU Serial Channel,appears with only the Channel Num-ber To Be Defined: field displayed.
ÁÁÁÁÁÁÁÁÁÁÁÁ
3.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Confirm that the entries for the config-ured channel in both the Active Typeand Stored Type columns read SMT.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
. . .
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
If the Active Type column is blank forthe configured channel, but theStored Type column displays SMT,the reboot process was not successful.The Octel-trained technician must re-peat steps 1 and 4 from section 11.4to shut down and reboot the voice pro-cessor. Then repeat the steps in thisprocedure to verify the configuration.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁ
4.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Press Return twice to return to theMain Menu.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
The Main Menu reappears(Figure 4-9).
4.6.1.5 Establish Octel PC/CDR Attributes for Communication With theVoice Processor. You or the Octel-trained technician must establish the OctelPC/CDR attributes for linking the PC with the voice processor by following theinstructions in Chapter 5.
4.6.1.6 Check Voice-Processor Modem Configuration. This step isperformed by the Octel-trained technician. Refer to section 11.7 for details.
4.6.2 USE A SHARED PORT FOR SMT AND PC (ASPENSOFTWARE RELEASES 1 THROUGH 1.3X)
On all voice-processors with software at Aspen Releases 1 to 1.3X, the CDR PCshares the same scanner-board port as the SMT.
When PC access to the voice processor is required, disconnect the cable between theSMT and the voice processor from the SMT and reconnect the cable to the CDR PC.The Octel PC/CDR software package includes an SMT emulator that enables mostsystem-management functions to be performed from the CDR PC, therefore allowingone connection most of the time. (SMT emulation is described in section 5.4.)
A manual or scanning (pollable) data switch can be used to make it easier for theSMT and CDR PC to share the same port. This configuration is illustrated inFigure 4-8. The setting on a manual data switch must then be changed physicallyto provide either SMT or PC access.
SECTION 4.6
EQUIPMENT REQUIREMENTS AND CONFIGURATION
4-18 Edition 2 Octel PC/CDR
4.7 EQUIPMENT CONFIGURATION FOR THE OCTEL XC1000
Before an Octel XC1000 can communicate with the CDR PC, the Octel XC1000must be connected to the CDR PC and be correctly configured.
Figure 4-12 and Figure 4-13 show the physical-connection requirements for the Octel XC1000-to-PC connection. Depending on the Octel XC1000 softwarerelease in use, the PC can either be connected to a separate port on the OctelXC1000 (Figure 4-12), or it can share a port on the Octel XC1000 with the SMT(Figure 4-13). These two connections are described in section 4.7.1, section4.7.2, and Chapter 11. Refer to Chapter 11 for detailed installation instructionsto be performed by Octel-trained technicians only. Refer to section 4.4 forinformation about the required cables and connectors.
Warning!To avoid dangerous electrical shock, do not performservice-related procedures unless you are qualified to doso. Only Octel-trained technicians are allowed to open theOctel XC1000 cabinet and perform service-related tasks.
CDR PC
MODEMCONNECTION
SYSTEM MANAGERTERMINAL
SERVICEMODEM
DIRECT CONNECTION
PRINTER
DATA CABLE
OCTEL XC1000
DISTRIBUTION PANEL
MODEMSERVER
MODEMCDR PC
NULL MODEM
J43
J44J46
Figure 4-12. Example of Direct and Modem ConnectionsBetween the Octel XC1000 and the CDR PC for
Aspen Software Releases 1.5X and Newer.
SECTION 4.7
EQUIPMENT REQUIREMENTS AND CONFIGURATION
Octel PC/CDR Edition 2 4-19
CDR PCMODEMCONNECTION
SYSTEM MANAGERTERMINAL
SERVICEMODEM
DIRECT CONNECTION
PRINTER
DATA CABLE
OCTEL XC1000
DISTRIBUTION PANEL
MODEMSERVER
MODEMCDR PC
NULL MODEM
A
B
DATA SWITCH(OPTIONAL)
DATA CABLE
Figure 4-13. Example of Direct and Modem ConnectionsBetween the Octel XC1000 and the CDR PC for
Aspen Software Releases 1 through 1.3X.
4.7.1 USE SEPARATE PORTS FOR SMT AND PC (ASPENSOFTWARE RELEASES 1.5X AND NEWER).
With Aspen software Release 1.5X and newer, the SMT and the CDR PC can beconnected to separate ports on the Octel XC1000 and can be operated at thesame time.
Warning!To avoid dangerous electrical shock, do not performservice-related procedures unless you are qualified to doso. Only Octel-trained technicians are allowed to open theOctel XC1000 cabinet and perform service-related tasks.
Refer to Table 4-4 for the steps required to establish a direct or modem connec-tion between the Octel XC1000 and the PC. The system manager or Octel-trainedtechnician performs steps 2, 4, and 5. Steps 1, 3, and 6 are performed only byOctel-trained technicians. These steps are described in detail in Chapter 11. Workwith the Octel-trained technician to perform these steps in sequence.
Instructions and screens in this section apply to an Octel XC1000 with AspenRelease 5.0 software. Instructions and screens for other releases are similar.
SECTION 4.7
EQUIPMENT REQUIREMENTS AND CONFIGURATION
4-20 Edition 2 Octel PC/CDR
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table 4-4. Overview of Equipment ConfigurationProcedures for Octel XC1000.
ÁÁÁÁÁÁÁÁ
StepÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
TaskÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Performed ByÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
DescribedÁÁÁÁÁÁÁÁÁÁÁÁ
1.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Identify the channel on the OctelXC1000.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Octel-trained technicianÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Section 11.2
ÁÁÁÁÁÁÁÁÁÁÁÁ
2.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Establish the channel on the Octel XC1000.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
System manager or Octel-trained technician
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Section 4.7.1.2
ÁÁÁÁÁÁÁÁÁÁÁÁ
3.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Connect the cables and completethe menu 6.3 configuration.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Octel-trained technicianÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Section 11.4
ÁÁÁÁÁÁÁÁÁÁÁÁ
4.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Verify menu 6.3 changes.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
System manager or Octel-trained technician
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Section 4.7.1.4
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
5.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Establish Octel PC/CDR attributes for communication with the Octel XC1000.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
System manager or Octel-trained technician
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Section 4.7.1.5
ÁÁÁÁÁÁÁÁÁÁÁÁ
6.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Check configuration of the OctelXC1000 modem.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Octel-trained technicianÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Section 11.7
4.7.1.1 Identify the Channel on the Octel XC1000. This step is performedby the Octel-trained technician. Refer to section 11.2 for details.
4.7.1.2 Establish the Channel on the Octel XC1000. Establish the OctelXC1000 channel identified by the Octel-trained technician in section 11.2, asfollows:
ÁÁÁÁÁÁÁÁÁÁÁÁ
StepÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ActionÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Result
ÁÁÁÁÁÁÁÁÁÁÁÁ
1. ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
From the SMT Main Menu, similar tothe screen shown in Figure 4-14, selectoption 6, and press Return.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Menu 6 – Dialing and Serial Chan-nel Parameters appears, similar tothe screen shown in Figure 4-15.ÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
2.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Select option 3, and press Return.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Menu 6.3, Define CPU Serial Chan-nel, appears with only the ChannelNumber To Be Defined: field displayed.ÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
3.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
In the Channel Number To Be Defined: field, enter the number of the channel that was identified in section 11.2, and press Return. Choosefrom the following list:
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
The Channel Type: field appears. Ifthe selected channel was previouslydefined, the remaining fields appear,similar to the screen shown inFigure 4-16.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
1 – J442 – J433 – J46
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
4.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
In the Channel Type: field, enter 1 forthe system terminal. Press Return.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
If not already displayed, the remaining menu 6.3 fields appear(Figure 4-16). The cursor moves tothe CPU Baud Rate: field.
SECTION 4.7
EQUIPMENT REQUIREMENTS AND CONFIGURATION
Octel PC/CDR Edition 2 4-21
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ResultÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ActionÁÁÁÁÁÁÁÁÁÁÁÁ
Step
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
5. ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
In the CPU Baud Rate: field, enter thenumber that corresponds to the baudrate used by the Octel PC/CDR soft-ware:
1 - 1200 Baud2 - 9600 Baud3 - 19200 Baud
Press Return.
The baud rate that you enter here mustmatch the baud rate established for theOctel PC/CDR software. (Refer to sec-tion 5.3.7 for information about settingthe baud rate for the PC.)
Octel recommends that downloads beperformed at 9600 baud. If the entry inthis field is 3 (19200 baud), a CDRdownload could fail.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
The cursor moves to the Type ofTerminal on This Channel: field.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
6.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
In the Type of Terminal on ThisChannel: field, enter the type of termi-nal used for communication betweenthe PC and the Octel XC1000. Thisentry must agree with the TerminalEmulation Type entered in the ModifyPC Communications Parameters screenof the Octel PC/CDR software (section5.3.7).
If the Octel PC/CDR terminal-emulationtype is
� WY50SPEC, choose 1 for the Wyse50 or HP 700/43.
� ANSI, choose 2 for the AT&T4425/5425.
� VT100, choose 3 for the DECVT102/220.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
The description corresponding tothe selected entry appears in theType of Terminal on This Channel: field.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
7.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Press the SEND key to save thechanges.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
The Channel Number To BeDefined: field reappears. Changesmade to menu 6.3 are not recognizedby the Octel XC1000 until it is shutdown and rebooted by the Octel-trained technician, as described insection 11.4.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
8.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Press Return twice to return to theMain Menu.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
The Main Menu reappears(Figure 4-14).
SECTION 4.7
EQUIPMENT REQUIREMENTS AND CONFIGURATION
4-22 Edition 2 Octel PC/CDR
Main Menu
System Management
11 – System Distribution Lists12 – Disk Management13 – System Maintenance14 – System Reports15 – Network Management16 – Database Access17 – External Application Mgnt18 – X.25 Interface Management19 – Not Applicable20 – Service Operations
Enter Menu Selection Number:
Copyrights (C) 1984 – 1996, Octel Communications Corporation
General System Parameters
1 – System Parameters 2 – Attendant Schedules, Port Monitoring 3 – Set Date/Time 4 – Port Assignments 5 – Outcalling Parameters 6 – Dialing Parameters
Mailboxes
7 – Change Class of Service Profile 8 – Add Mailbox 9 – Change Mailbox10 – Delete Mailbox
Figure 4-14. SMT Main Menu for the Octel XC1000.
Enter Option:
Menu 6 - Dialing and Serial Channel Parameters
1 – Transfer, Outcall, Fax, and Pager Dialing Sequences2 – In-band Integration Dialing Sequences3 – Define CPU Serial Channel4 - MTA (Multiple Terminal Access) Parameters5 - Integration Link Management
Figure 4-15. Menu 6 – Dialing and Serial ChannelParameters for the Octel XC1000.
Menu 6 - Dialing and Serial Channel Parameters- Define CPU Serial Channel -
Channel Active Type Console Stored Type Console 1–J44 SMT SMT 2–J43 3-J46 4–J50 Service Y Service Y
Channel Number To Be Defined: 1Channel Type: 1 - System TerminalCPU Baud Rate: 2 – Type of Terminal on This Channel:
Press the ’Send’ key to save changes.
Figure 4-16. Example of Menu 6.3 for the Octel XC1000.
SECTION 4.7
EQUIPMENT REQUIREMENTS AND CONFIGURATION
Octel PC/CDR Edition 2 4-23
4.7.1.3 Connect the Cables and Complete the Menu 6.3 Configuration. Thisstep is performed by the Octel-trained technician. Refer to section 11.4 for details.
4.7.1.4 Verify Menu 6.3 Changes. You or the Octel-trained technician mustverify that the Octel XC1000 is operational and that the changes made to menu6.3 were accepted by the Octel XC1000, as follows:
ÁÁÁÁÁÁÁÁÁ
StepÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ActionÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Result
ÁÁÁÁÁÁÁÁÁ
1.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
From the SMT Main Menu, selectoption 6, and press Return.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Menu 6 – Dialing and Serial ChannelParameters appears (Figure 4-15).ÁÁÁ
ÁÁÁÁÁÁÁÁÁ
2.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Select option 3, and press Return.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Menu 6.3, Define CPU Serial Channel,appears with only the Channel Num-ber To Be Defined: field displayed.ÁÁÁ
ÁÁÁÁÁÁÁÁÁ
3.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Confirm that the entries for the config-ured channel in both the Active Typeand Stored Type columns read SMT.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
. . .
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
If the Active Type column is blank forthe configured channel, but theStored Type column displays SMT,the reboot process was not successful.The Octel-trained technician must re-peat steps 1 and 4 from section 11.4to shut down and reboot the OctelXC1000. Then repeat the steps in thisprocedure to verify the configuration.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁ
4.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Press Return twice to return to theMain Menu.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
The Main Menu reappears(Figure 4-14).
4.7.1.5 Establish Octel PC/CDR Attributes for Communication With theOctel XC1000. You or the Octel-trained technician must establish the OctelPC/CDR attributes for linking the PC with the Octel XC1000 by following theinstructions in Chapter 5.
4.7.1.6 Check Octel XC1000 Modem Configuration. This step is performedby the Octel-trained technician. Refer to section 11.7 for details.
4.7.2 USE A SHARED PORT FOR SMT AND PC (ASPENSOFTWARE RELEASES 1 THROUGH 1.3X).
On Octel XC1000s with Aspen software at Releases 1 to 1.3X, the CDR PC sharesthe same distribution-board port as the SMT. An Octel XC1000 at any software levelwith MTA capability can dedicate a port on the MTA to the CDR application PC.
When PC access to the Octel XC1000 is required, disconnect the cable between theSMT and the Octel XC1000 from the SMT and reconnect the cable to the CDR PC.The Octel PC/CDR software package includes an SMT emulator that enables mostsystem-management functions to be performed from the CDR PC, therefore allowingone connection most of the time. (SMT emulation is described in section 5.4.)
A manual or scanning (pollable) data switch can be used to make it easier for theSMT and CDR PC to share the same port. This configuration is illustrated inFigure 4-13. The setting on a manual data switch must be changed physically toprovide either SMT or PC access.
SECTION 4.7
O C T E L
P C / C D R
SOFTWARE ATTRIBUTES
C O N T E N T S
5-iiiEdition 2Octel PC/CDR
CHAPTER 5
5.1 OVERVIEW 5-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2 ACCESSING THE OCTEL PC/CDR SYSTEM MENU 5-1. . . . . . . . . . . . . . .
5.2.1 THE CDR COMMAND 5-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2.2 THE SYSTEM NAME COMMAND 5-3. . . . . . . . . . . . . . . . . . . . . . . . . .
5.3 CONFIGURING OCTEL PC/CDR PARAMETERS AND SYSTEM ATTRIBUTES 5-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3.1 OPTION 1, LOG OCTEL PC/CDR PROCESSING OUTPUT TO PRINTER? 5-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3.2 OPTION 2, BINARY COLLECTION FILES ERASED AFTER COLLATION? 5-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3.3 OPTION 3, ERASE BINARY AND COLLATED DAY FILES BEYOND .. DAYS: 5-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3.4 OPTION 4, ERASE ALL OUTPUT & LOG FILES BEYOND .. DAYS: 5-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3.5 OPTION 5, MODIFY AUTOMATIC OUTPUT FILE GENERATION 5-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3.6 OPTION 6, MODIFY OUTPUT FILE FORMAT TYPES 5-8. . . . . . .
5.3.7 OPTION 7, MODIFY COMMUNICATIONS PARAMETERS 5-9. . .
5.3.8 OPTION 8, NEXT BLOCK TO DOWNLOAD BY AUTOMATIC OCTEL PC/CDR PROCESSING 5-14. . . . . . . . . . . . . .
5.3.9 OPTION 9, MODIFY OUTPUT FILE FORMAT LEVEL: 5-15. . . . .
5.4 TESTING THE DIRECT CONNECTION BETWEEN THE PC AND THE SERVER USING SMT EMULATION 5-17. . . . . . . . . . . . . . . .
Section Page
C O N T E N T S
5-iv Edition 2 Octel PC/CDR
TABLESTable 5-1. Suboption Descriptions for the Modify PC
Communications Parameter Information Menu 5-11. . . . . . . . . .
Table 5-2. Output Files With File-Format Level Changes 5-16. . . . . . . . . . .
Table 5-3. Special Emulation Function Keys 5-18. . . . . . . . . . . . . . . . . . . . . . .
FIGURESFigure 5-1. Octel PC/CDR Main Menu 5-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 5-2. Octel PC/CDR System Menu 5-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 5-3. Octel PC/CDR System Attributes Menu 5-4. . . . . . . . . . . . . . . . . .
Figure 5-4. Modify Automatic Output File Generation Menu 5-8. . . . . . . . .
Figure 5-5. Modify Output File Format Types Menu 5-9. . . . . . . . . . . . . . . . .
Figure 5-6. Example of an Output File Type Menu 5-9. . . . . . . . . . . . . . . . . . .
Figure 5-7. Modify PC Communications Parameters Menu With Default Entries 5-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 5-8. Octel PC/CDR System Attributes Menu Showing the Prompt for the Next Block To Download Option 5-15. . . . . . . . .
Figure 5-9. Octel PC/CDR System Attributes Menu for Modify Output File Format Level Option 5-16. . . . . . . . . . . . . . . . . . . . . . .
Page
C H A P T E R 5
Octel PC/CDR Edition 2 5-1
SOFTWARE ATTRIBUTES
5.1 OVERVIEW
The Octel PC/CDR software package consists of several components that arerequired to download, process, and back up (archive) Octel PC/CDR data andoutput files. Before these components can function, the Octel PC/CDR systemattributes must be configured correctly.
While in the Octel PC/CDR application, toggle the entries in fields requiring a yor n (yes or no) response by selecting the option number for that field.
5.2 ACCESSING THE OCTEL PC/CDR SYSTEM MENU
After the Octel PC/CDR software and system directories are installed on theCDR PC, access the Octel PC/CDR Main Menu by typing one of the followingcommands at the DOS prompt:
� cdr
� The individual CDR system name (for example, westreg)
These commands are explained in sections 5.2.1 and 5.2.2.
5.2.1 THE CDR COMMAND
Use the CDR command to load the Octel PC/CDR application into memory andto access the Octel PC/CDR System Menu, as follows:
Step Action Result
1. Type cdr at the DOS prompt, andpress Enter.
The Octel logo and the Call DetailRecords Package banner screensappear in sequence.
2. While the banner is scrolling, pressEnter to access the Main Menu, orwait until the banner stops scrolling.
The Octel PC/CDR Main Menuappears, as shown in Figure 5-1.
3. Select option 1, and press Enter. A list of all defined CDR systemsappears.
4. Select the desired CDR system bytyping its corresponding number inthe Enter Option: field, and pressEnter.
If the system-manager password hasbeen established, the password isrequested.
If the system-manager password has not been established, a promptrequests that you press enter to continue.
SOFTWARE ATTRIBUTES
5-2 Edition 2 Octel PC/CDR
Step ResultAction
5. If the system-manager password hasbeen established, type the password,and press Enter.
If the system-manager password hasnot been established, press Enter.
The Octel PC/CDR System Menuappears, similar to the screen shownin Figure 5-2.
A warning message, similar to thefollowing, might appear above theEnter Option: field:
Warning – Disk C: 15% Free,14,898 KBytes Available
6. If the warning message appears, thePC hard drive has less than 15% ofits storage space available. Beforeproceeding, refer to section 2.3 todetermine the amount of storagespace needed, and then create freespace as required.
. . .
Octel PC/CDR Main Menu, REV 2.30
0 Exit to DOS
1 Select an Individual System for CDR Processing2 Automatic Scheduler Functions
Enter Option:
Figure 5-1. Octel PC/CDR Main Menu.
Octel PC/CDR System Menu, REV 2.30 westreg
0 Exit
1 Update Octel PC System Attributes2 Manual Octel PC/CDR Processing3 Automatic Octel PC/CDR Processing4 File Utilities5 Link with Octel Server for Performing System Manager Functions
Enter Option:
Figure 5-2. Octel PC/CDR System Menu.
SECTION 5.2
SOFTWARE ATTRIBUTES
Octel PC/CDR Edition 2 5-3
5.2.2 THE SYSTEM NAME COMMAND
Type the CDR system name for access to the CDR system menus each time thatyou must process data and update attributes for that particular CDR system. If you are not sure of a CDR system name, type cdrhelp and press Enter todisplay a list of all defined CDR systems.
Use the individual CDR system name to access the Octel PC/CDR System Menu,as follows:
Step Action Result
1. At the DOS prompt, type the name ofthe CDR system to be configured, asnamed using the MKCDRSYS com-mand, and press Enter.
If the system-manager password hasbeen established, the password isrequested.
If the system-manager password hasnot been established, a promptrequests you press enter to continue.
2. If the system-manager password hasbeen established, type the password,and press Enter.
If the system-manager password hasnot been established, press Enter.
The Octel PC/CDR System Menuappears, similar to the screen shownin Figure 5-2.
A warning message, similar to thefollowing, might appear above theEnter Option: field:
Warning – Disk C: 15% Free,14,898 KBytes Available
3. If the warning message appears, thePC hard drive has less than 15% ofits storage space available. Beforeproceeding, refer to section 2.3 todetermine the amount of storagespace needed, and then create freespace as required.
. . .
5.3 CONFIGURING OCTEL PC/CDR PARAMETERS ANDSYSTEM ATTRIBUTES
Configure the system attributes and parameters for each CDR system createdwith the MKCDRSYS command. This process involves making choices that relatespecifically to each CDR system, the CDR data, and its communicationsrequirements.
Caution!Verify that all of the attributes are correct for the specificCDR system’s requirements. Incorrectly set attributescan cause the software to function incorrectly or valuabledata to be lost.
SECTION 5.2 – 5.3
SOFTWARE ATTRIBUTES
5-4 Edition 2 Octel PC/CDR
Configure CDR system parameters for each CDR system created in section 3.3,as follows:
Step Action Result
1. Access the Octel PC/CDR SystemMenu by following the instructionsin section 5.2.
The Octel PC/CDR System Menuappears (Figure 5-2).
2. From the Octel PC/CDR SystemMenu, select option 1, and pressEnter.
The Octel PC/CDR System Attributesmenu appears, similar to Figure 5-3.
3. Select the option number corre-sponding with the description of theattribute to be changed. Press Enter.
With some options, the entry in thefield toggles to other choices eachtime the option number is typed.Other options, when selected, dis-play another screen or require that anumber be typed.
4. Refer to sections 5.3.1 through 5.3.9and configure the system attributes,as necessary.
. . .
5. When all changes have been made,type 0 and press Enter to save thechanges. (Any time you are promptedto press 0 to save changes, pressingEnter alone also saves the changes.)
A message appears briefly at the bot-tom of the screen, indicating that thesystem attributes have been saved,then the Octel PC/CDR SystemMenu reappears (Figure 5-2).
Octel PC/CDR System Attributes Menu westreg
0 Save Attributes & Return to PC/CDR System MenuCurrent Setting
1 Log Octel PC/CDR Processing Output to Printer? (y/n) NO2 Binary Collection Files Erased After Collation? (y/n) YES3 Erase Binary and Collated Day Files Beyond .. Days: Permanent4 Erase All Output & Log Files Beyond .. Days: Permanent5 Modify Automatic Output File Generation6 Modify Output File Format Types7 Modify Communications Parameters8 Next Block to Download by Automatic Octel PC/CDR Processing9 Modify Output File Format Level: 1
Enter Option (ESC to Abort Changes):
Figure 5-3. Octel PC/CDR System Attributes Menu.
SECTION 5.3
SOFTWARE ATTRIBUTES
Octel PC/CDR Edition 2 5-5
5.3.1 OPTION 1, LOG OCTEL PC/CDR PROCESSINGOUTPUT TO PRINTER?
While the Octel PC/CDR processing programs are being executed, the resultsappear on the screen. If you toggle to YES for option 1 (Figure 5-3) and theprinter connected to the CDR PC is on line, these results are also printed. Selectoption 1 and press Enter to toggle the entry in the Current Setting columnfrom NO to YES.
All processing actions are also sent to log files in the SYS subdirectory. (Refer tosection 1.9.5.)
5.3.2 OPTION 2, BINARY COLLECTION FILES ERASEDAFTER COLLATION?
Binary collection files (BCFs) can be deleted automatically after they are collatedto conserve Octel PC/CDR disk-storage space. Because collated BCFs (calledprocessed collection files, or PCFs) could be needed in the future for databasere-creation or troubleshooting, Octel recommends that you toggle to NO foroption 2 (Figure 5-3). If you toggle to NO, the BCF is renamed with a fileextension of .PCF when it is processed.
Delete PCFs when the disk is getting full or when the data is no longer needed.Establish a schedule to copy PCFs to a disk or tape periodically, and thenmanually delete PCFs regularly, or refer to section 5.3.3 to have PCFs automati-cally deleted after a specified number of days. (Refer to section 8.5 for informa-tion about backing up files and to section 8.6 for information about manuallyerasing files.)
Referring to Figure 5-3, select option 2 and press Enter to toggle the defaultsetting of YES to NO in the Current Setting column, so that BCFs are notautomatically erased after collation.
5.3.3 OPTION 3, ERASE BINARY AND COLLATED DAYFILES BEYOND .. DAYS:
The contents of the BCF and CDF (collated day file) subdirectories can be deletedautomatically after a specific number of days to conserve Octel PC/CDRdisk-storage space. Because files in these subdirectories could be needed in thefuture for database re-creation or troubleshooting, Octel recommends that youaccept the default of Permanent in the Current Setting column for this optionto save the contents of the BCF and CDF subdirectories indefinitely.
Establish a schedule to copy the contents of the BCF and CDF subdirectories toa disk or tape periodically, and then manually delete the files to conserve PCdisk-storage space. (Refer to Chapter 8 for information about backing up andmanually erasing files.)
If you choose to have the contents of the BCF and CDF automatically erasedafter a certain number of days, all files in both the BCF and CDF subdirectoriesfor the selected CDR system are erased when the Octel PC/CDR software for theselected system is accessed on the designated day.
SECTION 5.3
SOFTWARE ATTRIBUTES
5-6 Edition 2 Octel PC/CDR
Caution!Important data could be lost if a BCF is erased beforeit is collated. If BCFs are scheduled to be automaticallyerased after a specified number of days, make sure tocollate all BCFs before erasing them.
Configure option 3, as follows:
Step Action Result
1. From the Octel PC/CDR SystemAttributes menu (Figure 5-3), selectoption 3, and press Enter.
The following prompt appears:
Erase BCF/CDF files after howmany days (0 = Permanent)?:
2. Accept the default of 0 to keep BCFsand CDFs indefinitely, or type thenumber of days, from 1 through999, that the BCFs and CDFs are to be saved before deletion. PressEnter.
The corresponding entry in the Current Setting column changes tothe number of days entered, or toPermanent if 0 was retained.
5.3.4 OPTION 4, ERASE ALL OUTPUT & LOG FILESBEYOND .. DAYS:
Log files (stored in the SYS subdirectory) and the content of the output filesubdirectories can be automatically deleted after a specific number of days toconserve Octel PC/CDR disk-storage space. Because erased log files cannot berecovered and erased output files can be re-created only if the CDFs or PCFs arestill available, Octel recommends that you accept the default of Permanent inthe Current Setting column for this option to save the output and log filesindefinitely.
Establish a schedule to copy older log files from the SYS subdirectory andoutput files from their respective subdirectories to a disk or tape periodically,and then manually delete them to conserve PC disk-storage space. (Refer tosection 8.5 for information about backing up files and to section 8.6 for informa-tion about manually erasing files.)
If you choose to have the contents of the log files and output files automaticallyerased after a certain number of days, all files in the output file subdirectoriesand all log files in the SYS subdirectories for the selected CDR system are erasedwhen the Octel PC/CDR software for the selected system is accessed on thedesignated day.
SECTION 5.3
SOFTWARE ATTRIBUTES
Octel PC/CDR Edition 2 5-7
Configure option 4, as follows:
Step Action Result
1. From the Octel PC/CDR SystemAttributes menu (Figure 5-3), selectoption 4, and press Enter.
The following prompt appears:
Erase Log/Output files after howmany days (0 = Permanent)?:
2. Accept the default of 0 to keep thelog and output files indefinitely, ortype the number of days, from 1through 999, that the files are to besaved. Press Enter.
The corresponding entry in the Current Setting column changes tothe number of days entered, or toPermanent if 0 was retained.
5.3.5 OPTION 5, MODIFY AUTOMATIC OUTPUT FILEGENERATION
To select the output files to be automatically created when the automatic orscheduled automatic processing method is executed (as described in sections7.4 and 7.5), configure option 5, as follows:
Step Action Result
1. From the Octel PC/CDR SystemAttributes menu (Figure 5-3), selectoption 5, and press Enter.
The Modify Automatic Output FileGeneration menu appears, similar toFigure 5-4.
2. Type the option number of an outputfile to be generated, type 10 to addnew records to the current formsoutput file, or type 99 to generate alloutput files. Press Enter.
The default of NO in the CurrentSetting column is toggled to YES. If 99 was typed, all current settingschange to YES.
3. Repeat step 2 for each output file tobe generated.
The default of NO in the CurrentSetting column is toggled to YES foreach output file selected.
4. Select option 0 and press Enter toreturn to the Octel PC/CDR SystemAttributes Menu.
The Octel PC/CDR System AttributesMenu reappears (Figure 5-3).
SECTION 5.3
SOFTWARE ATTRIBUTES
5-8 Edition 2 Octel PC/CDR
westregModify Automatic Output File Generation
0 Return to System Attributes MenuCurrent Setting
1 Generate Session Detail Output File NO2 Generate Unsuccessful Transfer Output File NO3 Generate Message Detail Output File NO4 Generate Individual Port Statistics Output File NO5 Generate Fax Output File NO6 Generate Profile Change Output File NO7 Generate Disk Usage Output File NO8 Generate Caller Menu Output File NO9 Generate NameNet Output File NO
10 Append Records to Forms Output File NO
99 Generate All Output Files NO
Enter Option:
Figure 5-4. Modify Automatic Output File Generation Menu.
5.3.6 OPTION 6, MODIFY OUTPUT FILE FORMAT TYPES
To change the default output file format of dBASE III to be compatible to ASCII,configure option 6, as follows:
Step Action Result
1. From the Octel PC/CDR SystemAttributes menu (Figure 5-3), selectoption 6, and press Enter.
The Modify Output File FormatTypes menu appears, similar toFigure 5-5, showing the default fileformat of dBASE III compatible foreach output file in the File FormatCurrent Setting column.
2. Type the number of the output file tobe changed, or type 99 to change alloutput file types at the same time.Press Enter.
An output file type menu appears,similar to Figure 5-6 appears, show-ing the formats available for theselected output files.
3. Type the number of the desired out-put format, and press Enter.
The Modify Output File FormatTypes menu reappears, and the cor-responding entry in the File FormatCurrent Setting column changes tothe selected format.
4. Repeat steps 2 and 3 until the out-put format for all output files isselected.
The corresponding entries in the FileFormat Current Setting columnchange to the selected format.
5. Select option 0 and press Enter toreturn to the Octel PC/CDR SystemAttributes Menu.
The Octel PC/CDR System AttributesMenu reappears (Figure 5-3).
SECTION 5.3
SOFTWARE ATTRIBUTES
Octel PC/CDR Edition 2 5-9
westregModify Output File Format Types
0 Return to System Attributes MenuFile Format Current Setting
1 Set Session Detail Output File Type dBASE III compatible2 Set Unsuccessful Transfer File Type dBASE III compatible3 Set Message Detail Output File Type dBASE III compatible4 Set Port Statistics Output File Type dBASE III compatible5 Set Fax Output File Type dBASE III compatible6 Set Profile Change Output File Type dBASE III compatible7 Set Disk Usage Output File Type dBASE III compatible8 Set Caller Menu Output File Type dBASE III compatible9 Set NameNet Output File Type dBASE III compatible
10 Set Forms Output File Type dBASE III compatible
99 Set All Output File Types
Enter Option:
Figure 5-5. Modify Output File Format Types Menu.
Session Detail Output File Type westreg
0 Return to System Attributes Menu
1 ASCII fixed field 2 ASCII fixed field, space separated3 ASCII fixed field, ’,’ separated4 ASCII fixed field, ’/’ separated5 ASCII variable field, ’,’ separated6 ASCII variable field, ’/’ separated7 dBASE III compatible
Current option: 7, dBASE III compatible
Enter Option:
Figure 5-6. Example of an Output File Type Menu.
5.3.7 OPTION 7, MODIFY COMMUNICATIONSPARAMETERS
Option 7, Modify Communications Parameters, establishes the attributes forlinking the CDR PC with the server.
The following suboptions, shown in the Modify PC Communications Parametersmenu in Figure 5-7, must be specified correctly to link the CDR PC successfullywith the server.
Suboption Suboption Name
1 Communication Port
2 Communication Speed (Baud)
8 Terminal Emulation Type
9 Octel Server System Type
11 Octel Server System Password
SECTION 5.3
SOFTWARE ATTRIBUTES
5-10 Edition 2 Octel PC/CDR
Modify PC Communications Parameters westreg
0 Return to System Attributes MenuCurrent Setting
1 Communication Port 22 Communication Speed (Baud) 96003 Connection Type Direct4 Modem Initialization String5 Dial Prefix String ATV0X1DT6 Octel Server Telephone Number7 Dial Suffix String |8 Terminal Emulation Type WY50SPEC9 Octel Server System Type Overture 250
10 Octel Server Software Version Number 1.2011 Octel Server System Password
Enter Option:
Figure 5-7. Modify PC Communications ParametersMenu With Default Entries.
Modify suboptions 4 through 7 only if a modem is used to connect the PC withthe server. These suboptions are required to support the modem connection.
Caution!Verify that all of the attributes are correct for the specificCDR system’s requirements. Incorrectly set attributescan cause the software to function incorrectly or datainconsistencies to occur.
Configure option 7, as follows:
Step Action Result
1. From the Octel PC/CDR SystemAttributes menu (Figure 5-3), selectoption 7, and press Enter.
The Modify PC CommunicationsParameters menu appears(Figure 5-7).
2. Review each suboption setting toverify that the parameters are setcorrectly for the requirements of thespecified CDR system.
. . .
3. Select the number of a suboption tobe changed, and press Enter.
When most suboptions have beenselected, a prompt appears at thebottom of the screen requesting thenew parameter information. Whensuboptions 9 and 11 are selected, asecond screen appears.
4. Refer to Table 5-1 for the possiblevalues and a description of eachsuboption. Type in the new informa-tion, as requested, and press Enter.
The corresponding entry in the Current Setting column is updated.
SECTION 5.3
SOFTWARE ATTRIBUTES
Octel PC/CDR Edition 2 5-11
Step ResultAction
5. Repeat steps 3 and 4 until all subop-tions have been updated, as neces-sary.
The corresponding entries in theCurrent Setting column areupdated.
6. Select option 0 and press Enter toreturn to the Octel PC/CDR SystemAttributes Menu.
The Octel PC/CDR System AttributesMenu reappears (Figure 5-3).
Table 5-1. Suboption Descriptions for the Modify PCCommunications Parameter Information Menu.
SuboptionNumber
Suboption NamePossibleValues
Comments
1 CommunicationPort
1–4 Enter the serial communicationsport number for the PC port thatconnects the CDR PC with theserver.
2 CommunicationSpeed (Baud)
1200, 9600, or19200
Enter the communications speedused to transmit data from theserver to the PC. The PC andserver baud rates must match,even if you are using a direct connection.
Octel does not recommend usingthe 19200-baud setting. If youselect 19200 baud, a CDR down-load performed during peakbusiness hours could causeserver performance degradation.
3 Connection Type D – DirectM – Modem
Enter D if a direct connection isbeing used, or enter M for amodem connection.
SECTION 5.3
SOFTWARE ATTRIBUTES
5-12 Edition 2 Octel PC/CDR
Table 5-1. PC Communications Parameter Information (Continued).
SuboptionNumber
Suboption NamePossibleValues
Comments
4 Modem Initializa-tion String
String up to 20characters long
If a modem connection is used,enter the character string thatinitializes the modem before theserver telephone number isdialed. Consult your modemmanual for the correct codes.The following characters havespecial meanings in this field.These characters also apply tothe dial prefix and suffix param-eters:
| Insert a carriage return.
~ Delay 1 second.
^ The caret and the characterfollowing the caret are inter-preted as a single controlcharacter.
5 Dial Prefix String String up to 20characters long
If a modem connection is used,enter the dial-prefix string thatprecedes the server telephonenumber dialed. Consult yourmodem manual for the correctcodes.
6 Octel Server Telephone Number
7 or 10 digits If a modem connection is used,enter the telephone number thatallows access to the server whenit is dialed by the modem in thePC through the system managerport. Enter the telephone num-ber in the following format: XXX-XXX-XXXX, where X representsa digit in the telephone number(the area code is optional). Thisfield is ignored if a direct con-nection is used.
7 Dial Suffix String String up to 20characters long
If a modem connection is used,enter the dial-suffix string thatis transmitted after the servertelephone number is dialed.Consult your modem manual forthe correct codes.
SECTION 5.3
SOFTWARE ATTRIBUTES
Octel PC/CDR Edition 2 5-13
Table 5-1. PC Communications Parameter Information (Continued).
SuboptionNumber
Suboption NamePossibleValues
Comments
8 Terminal Emulation Type
WY50SPEC, ANSI,or VT100
Enter the type of terminalemulation used for communica-tion between the PC and theserver. Leave the default ofWY50SPEC, or type VT100 orANSI if appropriate. (ANSI termi-nal emulation is for AT&T 4425and 5425 terminals.) Do notchange this parameter to anyother terminal type withoutexplicit instructions from Octel or distributor service personnel.
9 Octel Server System Type
1 – Branch XP2 – Branch3 – Aspen4 – Maxum5 – Sierra6 – Maxum SE7 – XC 10008 – Overture 2509 – Overture 350
Select the server type for thisCDR system. The server typemust be correct for correct opera-tion. If an incorrect server type isentered, it could cause an errorduring the collate process ordata inconsistencies in the output files.
10 Octel Server Software VersionNumber
. . . Enter the server software versionnumber, as shown in systemmanager menu 13.4, in the formof XX.XX. (For example, enter1.2 for Aria 1.2.) This field is forreference only.
SECTION 5.3
SOFTWARE ATTRIBUTES
5-14 Edition 2 Octel PC/CDR
Table 5-1. PC Communications Parameter Information (Concluded).
SuboptionNumber
Suboption NamePossibleValues
Comments
11 Octel Server System Password
. . . Enter the same password as theone that is required to accessthe system-manager terminal(SMT) menus on the server. Aseries of Xs appears as the pass-word is typed, one for each digit.Press Enter. When prompted,type the password again for verification.
The server password is requiredif the automatic-schedulingmethod of processing is used. Itis also required to allow the CDRPC to link with the server andfor testing the communicationlink between the CDR PC andthe server, as described in sec-tion 5.4. Once an entry is madein this field, this password isrequired for access to the OctelPC/CDR application menus forthe current CDR system.
When the SMT password ischanged, also change the entryin this field, or access to theserver through Octel PC/CDRwill be denied.
5.3.8 OPTION 8, NEXT BLOCK TO DOWNLOAD BYAUTOMATIC OCTEL PC/CDR PROCESSING
Change the entry in option 8, Next Block to Download by Automatic OctelPC/CDR Processing, only if the next block to be downloaded differs from thedefault entry. The default entry is the number for the first block that has notbeen downloaded. Normally, CDR blocks are downloaded only once. However, if a BCF is deleted from the PC before it is collated, download the BCF again byrequesting a previously downloaded series of blocks. Change the entry for thenext block to download to a valid number. (The download will fail if an overwrit-ten block number is entered.)
Caution!Download only CDR blocks that were not previouslydownloaded and collated. Because CDFs are appendedeach time a BCF is collated, duplicate data is added to thedatabase if a BCF containing previously collated blocks iscollated more than once.
SECTION 5.3
SOFTWARE ATTRIBUTES
Octel PC/CDR Edition 2 5-15
When a BCF is collated, the CDFs are appended to include calls from the latestdownload. Collate only BCFs containing CDR buffer blocks that have notpreviously been collated to prevent adding duplicate data to your database. Refer to Chapter 2 for additional information about the CDR buffer.
Configure option 8, as follows:
Step Action Result
1. From the Octel PC/CDR SystemAttributes menu (Figure 5-3), selectoption 8, and press Enter.
A prompt appears at the bottom ofthe screen, as shown in Figure 5-8.
2. In the Block Number?: field, typethe number of the first block to bedownloaded, or leave the promptblank to use the default block number. Press Enter.
The new block number appears in the corresponding field of the Current Setting column.
Octel PC/CDR System Attributes Menu westreg
0 Save Attributes and Return to Main MenuCurrent Setting
1 Log Octel PC/CDR Processing Output to Printer? (y/n) NO2 Binary Collection Files Erased After Collation? (y/n) NO3 Erase Binary and Collated Day Files Beyond .. Days: Permanent4 Erase All Output & Log Files Beyond .. Days: Permanent5 Modify Automatic Output File Generation6 Modify Output File Format Types7 Modify Communications Parameters8 Next Block to Download by Automatic Octel PC/CDR Processing9 Modify Output File Format Level: 1
Enter Option (ESC to Abort Changes): 8
Enter the First Block Number to Download (0 to 65535) or EnterNothing to Receive Octel Server’s Next Default Block NumberBlock Number?:
Figure 5-8. Octel PC/CDR System Attributes MenuShowing the Prompt for the Next Block
To Download Option.
5.3.9 OPTION 9, MODIFY OUTPUT FILE FORMAT LEVEL:
During the collate process, file-format levels establish the format and content of an output file, depending on the server software release. The lower thefile-format level selected, the less the information contained in the output filesand the less storage space required on the hard drive for the storage of outputfiles. The default file-format level is 1.
If you use Octel PC/CDR data to bill for server usage,select the file-format level that corresponds to the structure of the data used in your billing application.Selecting the wrong file-format level could cause datainconsistencies.
Caution!
SECTION 5.3
SOFTWARE ATTRIBUTES
5-16 Edition 2 Octel PC/CDR
Six file formats are available with Octel PC/CDR Release 2.3. Refer to Table 5-2to identify the output files that are affected by the different file-format levels. AnX in the field signifies that changes were made to the corresponding output filebased on the file-format level. Output files not shown contain the same informa-tion, regardless of which file-format level is selected. Refer to Appendix A toidentify the output-file fields affected by the different file-format levels.
Table 5-2. Output Files WithFile-Format Level Changes.
FormatLevel
Session-DetailOutput (SDO)
File
Message-DetailOutput (MDO)
File
Individual-Port-Statistics Out-put (PSO) File
1 X X
2 X X
3 X X X
4 X
5 X
6 X
Configure option 9, as follows:
Step Action Result
1. From the Octel PC/CDR SystemAttributes menu (Figure 5-3), selectoption 9, and press Enter.
A prompt requesting the file-formatlevel appears at the bottom of thescreen, as shown in Figure 5-9.
2. At the prompt, type the number ofthe desired file-format level, andpress Enter.
The new file-format level appears in the corresponding field of the Current Setting column.
Octel PC/CDR System Attributes Menu westreg
0 Save Attributes and Return to Main MenuCurrent Setting
1 Log Octel PC/CDR Processing Output to Printer? (y/n) NO2 Binary Collection Files Erased After Collation? (y/n) NO3 Erase Binary and Collated Day Files Beyond .. Days: Permanent4 Erase All Output & Log Files Beyond .. Days: Permanent5 Modify Automatic Output File Generation6 Modify Output File Format Types7 Modify Communications Parameters8 Next Block to Download by Automatic Octel PC/CDR Processing9 Modify Output File Format Level: 1
Enter Option (ESC to Abort Changes): 9
Set CDR output file format level(1-6):
Figure 5-9. Octel PC/CDR System Attributes Menufor Modify Output File Format Level Option.
SECTION 5.3
SOFTWARE ATTRIBUTES
Octel PC/CDR Edition 2 5-17
5.4 TESTING THE DIRECT CONNECTION BETWEEN THEPC AND THE SERVER USING SMT EMULATION
Test the direct connection between the CDR PC and the server, or use the CDRPC as a system-manager terminal, as follows:
Step Action Result
1. Follow the instructions in section 5.2to access the Octel PC/CDR SystemMenu.
The Octel PC/CDR System Menuappears (Figure 5-2).
2. Select option 5, Link with OctelServer for Performing SystemManager Functions, and pressEnter.
Menus and prompts appear andscroll off the screen as the CDR PC and the server are linked using MIRROR II communication software.
3. If the password was not required toaccess the Octel PC/CDR SystemMenu, it is now requested. Type theappropriate password for the serverbeing accessed at the Please EnterSystem Manager Password:prompt, and press Enter.
If the server is operating and the linkis established correctly, the SMTMain Menu appears, as the CDR PCemulates the functions of the systemmanager terminal. The status line atthe bottom of the screen applies tothe MIRROR II software.
If the link is not established cor-rectly, refer to section 5.3.7 andverify the communications parame-ters, especially the communicationport and baud rate. Also, refer toChapter 4 and ensure that thecables and connectors are installedcorrectly.
After the PC-to-server connection is tested, system management functions canbe performed using the CDR PC.
Caution!When SMT menus are accessed from the CDR PC, mostSMT functions can be performed. Because critical menuentries could be altered through the PC, secure the CDRPC in the same manner as the original SMT.
The following system manager functions cannot be performed from the CDR PC:
� Rebooting the server
� Accessing menu 16 from more than one terminal (SMT or CDR PC) at a time
� Setting the date and time functions
� Shutting down the server
SECTION 5.4
SOFTWARE ATTRIBUTES
5-18 Edition 2 Octel PC/CDR
Do not perform a server shutdown from the CDR PC. Thebaud rate could change and status log entries could belost.
Caution!
Because the MIRROR II software program emulates the SMT, the function keys,the Break key, and the Esc key can be used for system manager functions.Refer to Table 5-3 for keyboard equivalents that are effective when the SMT isaccessed through a PC using the MIRROR II software program.
Table 5-3. Special Emulation Function Keys.
SMT TerminalKeys
WY50SPEC EmulationKeys on CDR PC
Alphabetical Same
Numerical Same
Function Same (except F3, F4, F6)*
Break or Ctrl–C Esc or Ctrl–C
Print Send Page Down
Shift–Print Send Print Screen
* F3 = Opens the MIRROR II command line F4 = Displays MIRROR II status screenF6 = Disconnects and returns to the Octel PC/CDR application
If the CDR PC screen times out and darkens while emulating the SMT, press theEnter key and reenter the password, as prompted.
Return to the Octel PC/CDR System Menu or DOS prompt, as follows:
Step Action Result
1. Press the F6 key to disconnect thelink between the CDR PC and theserver.
Menus and prompts scroll off thescreen as it returns to the Octel PC/CDR System Menu.
2. If you need to return to the DOSprompt, type 0, and press Enter.
The DOS prompt appears.
SECTION 5.4
O C T E L
P C / C D R
CARBON COPY PLUSPROCEDURES
C O N T E N T S
6-iiiEdition 2Octel PC/CDR
CHAPTER 6
6.1 OVERVIEW 6-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2 CONFIGURING CARBON COPY PLUS PARAMETERS 6-1. . . . . . . . . . . . .
6.2.1 OPTION A: COMM PORT ADDRESS 6-3. . . . . . . . . . . . . . . . . . . . . . .
6.2.2 OPTION B: BAUD RATE 6-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.3 OPTION C: MODEM TYPE 6-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.4 OPTION 4: PASSWORD TABLE 6-5. . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.3 CHANGING CARBON COPY PLUS PARAMETERS 6-6. . . . . . . . . . . . . . . . .
6.4 USING CARBON COPY PLUS 6-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.4.1 LOAD CARBON COPY PLUS INTO MEMORY 6-6. . . . . . . . . . . . . .
6.4.2 RESPONSIBILITIES OF THE SYSTEM MANAGER 6-7. . . . . . . . . .
6.4.3 RESPONSIBILITIES OF THE SERVICE REPRESENTATIVE 6-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.4.4 RESPONSIBILITIES OF BOTH THE SYSTEM MANAGER AND THE SERVICE REPRESENTATIVE 6-9. . . . . . . . . . . . . . . . . . .
6.5 DISABLING CARBON COPY PLUS 6-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Section Page
C O N T E N T S
6-iv Edition 2 Octel PC/CDR
TABLETable 6-1. Guidelines for Changing Carbon Copy
PLUS Parameters 6-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FIGURESFigure 6-1. Remote Connection Configuration With
Internal Modems 6-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6-2. Carbon Copy PLUS System Parameters Menu 6-3. . . . . . . . . . . .
Figure 6-3. Available Modem Types Screen 6-4. . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6-4. PASSWORD TABLE Screen 6-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6-5. Example of Carbon Copy PLUS Customer Dialogue Screen 6-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6-6. Example of Carbon Copy PLUS Service Dialogue Screen 6-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Page
C H A P T E R 6
Octel PC/CDR Edition 2 6-1
CARBON COPY PLUS PROCEDURES
6.1 OVERVIEW
The Octel PC/CDR software package includes version 5.1 of Carbon Copy PLUSsoftware, which provides additional service capabilities for the Octel or distribu-tor service representatives. Carbon Copy PLUS is a memory-resident programthat allows a remotely located PC (called the service PC) to be connected to theCDR PC through a modem. Carbon Copy PLUS is used only when a remoteconnection from an Octel or distributor support office is necessary for diagnosticreasons or for system maintenance. Using Carbon Copy PLUS, the servicerepresentative can remotely perform CDR operations and provide troubleshootingservices.
Carbon Copy PLUS requires the following on the CDR PC:
� At least 540K of free memory
� Two communication ports (one for the service modem and the other for thelink to the server)
� A separate service modem (internal or external)
6.2 CONFIGURING CARBON COPY PLUS PARAMETERS
The Carbon Copy PLUS software program is loaded into the CDR PC when theOctel PC/CDR software is installed. Carbon Copy PLUS must be configuredcorrectly for proper operation.
Carbon Copy PLUS requires an internal or external modem on the CDR PC.When using an external modem, the CDR PC must be equipped with at least twoserial communication ports (COM1 and COM2). One of the communication portsis used to communicate with the server; a different communication port is usedfor connection to the service representative’s modem, as shown in Figure 6-1. Aninternal modem appears to the CDR PC as a serial port, with the same namingconvention (COM1 or COM2). Carbon Copy PLUS (for connection to the servicePC) and MIRROR II (for connection to the server) must each be configured withtheir own communication ports. (MIRROR II software is configured when theOctel PC/CDR software attributes are configured, as described in Chapter 5.)
CARBON COPY PLUS PROCEDURES
6-2 Edition 2 Octel PC/CDR
SERVER
BACK OFCDR PC
SERVICE PC
SERVICEMODEMS
COM PORTS
CDR PC CONNECTION1 = DIRECT OR2 = MODEM
1
2
CDR PCMODEM
Figure 6-1. Remote Connection ConfigurationWith Internal Modems.
Note the following before configuring the Carbon Copy PLUS parameters:
� All instructions in this chapter assume that the Octel PC/CDR software isinstalled on drive C. If your Octel PC/CDR software is installed on a differentdrive, substitute that drive letter wherever drive C is mentioned.
� The default parameters for Carbon Copy PLUS are selected at the Octelfactory.
� You can change the parameters by typing the letter or number of theparameter to be changed. Depending on the parameter letter or number that is typed, different results occur, as described in Table 6-1.
Table 6-1. Guidelines for Changing Carbon Copy PLUS Parameters.
When you type thisparameter letter ornumber . . . This occurs . . .
A, B, E,F, or H
Each time you type one of these parameter letters, the parame-ter toggles to a different setting. Continue to type the parameterletter until the desired parameter setting is displayed.
C The Available Modem Types screen appears. Refer to section6.2.3 for configuration instructions.
D Nothing changes. The default entry of USA Keyboard cannotbe changed.
G The Directory: field appears at the bottom of the screen. If youdo not want to use the default directory, enter a working direc-tory path, starting with a backslash (\).
1, 2, 3, or 4 A new menu is displayed. Modify option 1, 2, or 3 only wheninstructed to do so by your service representative. Refer to section 6.2.4 for configuration instructions for option 4.
SECTION 6.2
CARBON COPY PLUS PROCEDURES
Octel PC/CDR Edition 2 6-3
Configure the Carbon Copy PLUS parameters, as follows:
Step Action Result
1. Type cd\octelcdr\cc at the DOS prompton drive C and press Enter to access theOCTELCDR\CC subdirectory.
The prompt changes toC:\OCTELCDR\CC>.
2. Type ccinstal and press Enter to accessthe Carbon Copy PLUS System Parame-ters screen.
The Carbon Copy PLUS SystemParameters menu appears, similarto Figure 6-2.
3. Review each parameter setting to verifythat the parameters are correct, payingparticular attention to options A, B, C,and 4 (described in sections 6.2.1through 6.2.4).
. . .
4. Refer to Table 6-1, and make changes tothe parameters, as necessary.
The parameter settings displayedon the screen are updated as thechanges are made.
5. Press X to save the changes and exit toDOS.
The changes are saved, and theDOS prompt reappears.
Carbon Copy PLUS System Parameters (5.1)
GENERAL PARAMETERS EXIT OPTIONS
A –– Comm Port Address COM1 Q –– Quit, changes not savedB –– Baud Rate 1200 X –– eXit, changes savedC –– Modem Type UK “AT” CompatibleD –– Keyboard handling USA KeyboardE –– Display Type DefaultF –– Menu Colors Yellow on BlackG –– Working Directory Default DirectoryH –– Menu Level Options Advanced
MENU LIST
1 –– CC Optional Configuration Parameters2 –– CCHELP Optional Configuration Parameters3 –– Call Table4 –– Password Table
Type letter for selection:
Figure 6-2. Carbon Copy PLUS System Parameters Menu.
Refer to Table 6-1 for instructions about how to change the key parametersdescribed in the following sections.
6.2.1 OPTION A: COMM PORT ADDRESS
Press A repeatedly until the comm port address of the service modem in theCDR PC is displayed. If the setting Other is required, contact your local Octel or distributor service representative for assistance in configuring this option.
SECTION 6.2
CARBON COPY PLUS PROCEDURES
6-4 Edition 2 Octel PC/CDR
6.2.2 OPTION B: BAUD RATE
Press B repeatedly until the maximum speed of the CDR PC service modem isdisplayed.
6.2.3 OPTION C: MODEM TYPE
The service modem used by the CDR PC must be compatible with the modemused by your Octel or distributor service representative. Press C to select thetype of service modem used in the CDR PC, as follows:
Step Action Result
1. From the Carbon Copy PLUS SystemParameters menu (Figure 6-2), typeC to change the modem type to thatof the CDR PC service modem.
The Available Modem Types screenappears, as shown in Figure 6-3.
2. Use the arrow keys to move the high-lighted cursor to select the modemtype, and press Enter. If the desiredmodem is not available, select theUK “AT” Compatible modem listedtoward the top of the first column.
If the modem type was changed, thefollowing prompt appears:
Do you wish BAUD RATE to beset to Modem’s default rate (Noor Yes)
If no change was made, the CarbonCopy PLUS System Parameters menureappears (Figure 6-2).
3. If the modem type was changed, typeN at the Do you wish BAUD RATEto be set to Modem’s default rate(No or Yes) prompt so that CarbonCopy PLUS uses the baud rateentered in the Baud Rate field.
The Carbon Copy PLUS SystemParameters menu reappears(Figure 6-2).
Available Modem Types
No Modem Codex 2233 Pace
UK “AT” Compatible Concord 296 Popcom & Prentice
MNP Compatible Datarace II Practical Peripherl
Standard “AT” 1200 Dowty Min/Duo/Trio Racal Vadic 2400PA
Standard “AT” 2400 Dowty Quottro Racal Vadic 9600
Microcom QX/12K Evercom II – 1200 Rolm Dataswitch
Microcom QX/V.32c Everex–Cygcom 24E Smarteam
Microcom AX–AT Mode Fastcomm Telebit Compatible
Microcom AX–SX Mode Gandalf Pax Multplx Telebit Trail.–INT
Microcom SX Series IBM 1200 5841 Telebit Trailblazer
Hayes IBM PC Internal Touchbase Worldport
Hayes V–Series Ideacom UDS Fastalk
AST Kyocera US Robotics
AST 2X Series Leading Edg&Omnitel US Robotics 2400E
AT&T 4000 Leased Line / “AT” US Robotics HST
AT&T KS–23095, L1 Micom Dataswitch US Robotics HST–MNP
Bizcomp Migent Ven–Tel
CTS 2424/Sysdyn Miracle WS3000/4000 Zoom Telephonics
Capetronics Multi–Tech 224E
Case Novation
Use Cursor keys to select entry, CR to exit
Figure 6-3. Available Modem Types Screen.
SECTION 6.2
CARBON COPY PLUS PROCEDURES
Octel PC/CDR Edition 2 6-5
6.2.4 OPTION 4: PASSWORD TABLE
The Octel or distributor service representative must enter a password to accessCarbon Copy PLUS in the CDR PC from a remote location. The default passwordwas entered at the Octel factory. The password used by the service representa-tive must match the password configured on this screen for the CDR PC.
Modify the entries in the password table only if requested to do so by an Octel ordistributor service representative. When instructed to change the password,perform the following steps:
Step Action Result
1. From the Carbon Copy PLUS SystemParameters menu (Figure 6-2), type 4.
The PASSWORD TABLE screen ap-pears, similar to the screen shownin Figure 6-4.
2. Modify the password table as advised byyour service representative. Refer to thefunction-key descriptions displayed onthe screen for assistance.
. . .
3. Press the Enter key or right-arrow keyto move the cursor to the next field, ifadditional fields must be modified.
The cursor moves to the next field.
4. Press F10 to save the changes and re-turn to the Carbon Copy PLUS SystemParameters menu.
The Carbon Copy PLUS SystemParameters menu reappears(Figure 6-2).
5. If your password was changed, whenasked to run Carbon Copy PLUS, notifyyour service representative of the newpassword.
. . .
Use Arrow Keys, Pg Up, Pg Dn, Home & End to Position Field Pointer
To Edit a Field enter a character, Ins, Del or F1
FUNCTION KEYS
F1 –– Edit Current Field F2 –– Insert Line
F3 –– Delete Current Line Entry F4 –– Sort Entries by Passwords
F6 –– Special Phone Characters F9 –– Help
F10 – Exit to Main Menu
Password Callback Phone Number Password options
CC CCDOS :STD Keybd
PASSWORD TABLE
Figure 6-4. PASSWORD TABLE Screen.
SECTION 6.2
CARBON COPY PLUS PROCEDURES
6-6 Edition 2 Octel PC/CDR
If a service representative is using Carbon Copy PLUS, Version 5.0, and CarbonCopy PLUS, Version 4.0, is installed on the CDR PC, the passwords will not match.For these two versions of Carbon Copy PLUS to communicate with each other, thepasswords must contain an initial alphabet character, such as an a or a b.
6.3 CHANGING CARBON COPY PLUS PARAMETERS
Follow the instructions in section 6.2 to modify the Carbon Copy PLUS configura-tion parameters, as necessary.
6.4 USING CARBON COPY PLUS
Carbon Copy PLUS is used only when a remote connection between a modem atan Octel or distributor support office and the CDR PC is necessary for systemmaintenance or troubleshooting. All calls to the CDR PC are initiated by an Octelor distributor service representative.
Caution!To prevent unauthorized access, run Carbon Copy PLUSonly when instructed to do so by your Octel or distribu-tor service representative. Do not leave Carbon CopyPLUS running unattended.
Besides risking unauthorized access, running Carbon Copy PLUS requires mainmemory (RAM) that could be used for the Octel PC/CDR program.
6.4.1 LOAD CARBON COPY PLUS INTO MEMORY
When advised to do so by your service representative, load the Carbon CopyPLUS program into memory, as follows:
Step Action Result
1. Make sure that your modem is correctlyconnected to a telephone line. If themodem is connected externally to thePC, make sure it is plugged in and thepower is on.
. . .
2. Type cd\octelcdr\cc at the DOS prompton drive C and press Enter to access theOCTELCDR\CC subdirectory.
The prompt changes toC:\OCTELCDR\CC.
3. Type cc at the prompt, and press Enter. The Carbon Copy PLUS introduc-tion screen is displayed, as the program is loaded into memory.
After a moment, the Carbon Copyis now installed. Press <ALT><RIGHT-SHIFT> for Menus.prompt appears. The DOS promptalso reappears on the screen.
SECTION 6.2 – 6.4
CARBON COPY PLUS PROCEDURES
Octel PC/CDR Edition 2 6-7
Step ResultAction
4. While at the DOS prompt or within theOctel PC/CDR application, if you needaccess to the Carbon Copy PLUS dia-logue screen, press the Alt key and theright Shift key simultaneously.
The Carbon Copy PLUS customerdialogue screen appears, similar tothe screen shown in Figure 6-5.
5. As necessary, toggle back to DOS or theOctel PC/CDR application by pressingthe F10 key or the Esc key.
The DOS prompt or Octel PC/CDRapplication reappears, dependingon where you were before youaccessed Carbon Copy PLUS.
Your Dialogue
Remote Operator’s Dialogue
Carbon Copy (CC V5.1)Meridian Technology, Inc.
Licensed to:Octel Communications Corporation
NO Data Link EstablishedAuto-Answer Mode is EnabledPrinter Assigned to: CC
Time 8:03:30
[F1] Call Support
[F2] Switch Voice to Data Mode
[F3] Capture Screen Image
[F4] Review Captured Screen Image
[F6] Printer / Log Control
[F8] Data Link Maintenance
[F10] Return to Application
Figure 6-5. Example of Carbon Copy PLUSCustomer Dialogue Screen.
6.4.2 RESPONSIBILITIES OF THE SYSTEM MANAGER
Allow remote access to the CDR PC when requested to do so by an Octel ordistributor support representative, as follows:
Step Action Result
1. If Carbon Copy PLUS has not been con-figured, follow the steps in section 6.2.
. . .
2. When instructed to do so by your servicerepresentative, refer to section 6.4.1 andload Carbon Copy PLUS into memory.
Carbon Copy PLUS is ready toreceive a call from the service representative.
3. Press the Alt key and the right Shift keysimultaneously.
The Carbon Copy PLUS dialoguescreen appears (Figure 6-5).
4. Refer to section 6.4.4. for the systemmanager’s responsibilities when the service representative calls.
. . .
SECTION 6.4
CARBON COPY PLUS PROCEDURES
6-8 Edition 2 Octel PC/CDR
6.4.3 RESPONSIBILITIES OF THE SERVICEREPRESENTATIVE
The service representative must have a special master version of the CarbonCopy PLUS software program to be able to access the CDR PC for remotemaintenance.
If it is necessary to update the parameters or add a telephone number to the calltable of the master Carbon Copy PLUS software on the service PC, the servicerepresentative types ccinstal at the DOS prompt from the subdirectory containingthe master version of the Carbon Copy PLUS software. The service representativecan then make changes, as necessary, following the instructions in section 6.2.
From a PC using the master version of Carbon Copy PLUS, perform the followingsteps for remote access to the CDR PC:
Step Action Result
1. Notify the system manager toexpect your call and to load Car-bon Copy PLUS into memory onthe CDR PC.
. . .
2. On the service PC, access the sub-directory that contains the master Carbon Copy PLUS software.
The service PC prompt is similar toC:\CCHELP>.
3. Type cchelp, and press Enter. The Carbon Copy PLUS introductionscreen is displayed. After a moment, aservice dialogue screen appears, simi-lar to Figure 6-6.
4. Press the F1 key to call the CDRPC.
The CALL Table, showing a list of loca-tion descriptions, and the CALL CCUSER box appear in the lower part ofthe screen.
5. Select the location of the CDR PCby following the instructions onthe screen, or type the appropriateaccess telephone number in theNumber: field in the CALL CCUSER box. Press Enter.
The telephone number appears in theNumber: field, and Carbon Copy PLUScalls the customer’s PC.
6. Refer to section 6.4.4 for the ser-vice representative’s responsibili-ties after the connection is made.
. . .
SECTION 6.4
CARBON COPY PLUS PROCEDURES
Octel PC/CDR Edition 2 6-9
Your Dialogue
Remote Operator’s Dialogue
Carbon Copy (CCHELP V5.1)Meridian Technology, Inc.
Licensed to:Octel Communications
NO Data Link EstablishedAuto–Answer Mode is EnabledPrinter Assigned to: CCSpl File: –– NONE ––
Time 08:30:50
[F1] Call CC User[F2] Switch Voice to Data Mode[F7] Terminal Emulation[F10] Return to Application
Figure 6-6. Example of Carbon Copy PLUSService Dialogue Screen.
6.4.4 RESPONSIBILITIES OF BOTH THE SYSTEMMANAGER AND THE SERVICE REPRESENTATIVE
The steps in sections 6.4.1 through 6.4.3 are used to establish the connectionbetween the CDR PC and the service PC. Instructions and responses can bepassed back and forth between the service representative and the systemmanager, by typing instructions and responses on the screen.
To access the Octel PC/CDR application or DOS prompt on the CDR PC, thesystem manager or service representative presses the F10 key. Using CarbonCopy PLUS on the service PC, the service representative views the applicationthat resides on the CDR PC, and the system manager proceeds as directed. Allprompts are shown on both monitors, regardless of who types the entries.
To return to the dialogue screen, the system manager or service representativepresses the Alt key and the right Shift key simultaneously.
SECTION 6.4
CARBON COPY PLUS PROCEDURES
6-10 Edition 2 Octel PC/CDR
6.5 DISABLING CARBON COPY PLUS
Disabling Carbon Copy PLUS removes the RAM resident program from the PCsystem memory and secures the PC from outside access.
Disable Carbon Copy PLUS, as follows:
Step Action Result
1. Type cd\octelcdr\cc at the DOSprompt to access the \OCTELCDR\CCsubdirectory, and press Enter.
The prompt changes toC:\OCTELCDR\CC>.
2. Type ccremove at the DOS prompt, andpress Enter.
The Carbon Copy (V5.1) DeinstallUtility screen is displayed.
3. At the Remove Carbon Copy (Y or N)?prompt, press Y to remove Carbon CopyPLUS from memory.
Carbon Copy PLUS is removedfrom memory, and the DOSprompt reappears.
SECTION 6.5
O C T E L
P C / C D R
PROCESSING METHODS
C O N T E N T S
7-iiiEdition 2Octel PC/CDR
CHAPTER 7
7.1 OVERVIEW 7-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2 PREPARING TO PROCESS DATA 7-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.1 COMPLETING PRELIMINARY TASKS 7-2. . . . . . . . . . . . . . . . . . . . . .
7.2.2 UNDERSTANDING DATA TRANSFER 7-3. . . . . . . . . . . . . . . . . . . . . .
7.2.3 LEARNING ABOUT PARTIALLY FILLED BLOCKS 7-4. . . . . . . . . .
7.2.4 LOCATING LOG FILE ENTRIES 7-4. . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.5 UNDERSTANDING TRANSMISSION AND ERROR MESSAGES 7-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.5.1 Transmission Messages 7-5. . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.5.2 Overwritten Blocks 7-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.5.3 Prior PSF Data Not Found 7-5. . . . . . . . . . . . . . . . . . . . . .
7.2.5.4 Block Numbers in BCF Are out of Sequence 7-5. . . . .
7.2.5.5 Filled Hard Drive 7-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2.5.6 No Previous Day File Available 7-6. . . . . . . . . . . . . . . . . .
7.2.5.7 Backup Utility Errors 7-6. . . . . . . . . . . . . . . . . . . . . . . . . . .
7.3 USING MANUAL PROCESSING 7-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.3.1 DOWNLOADING CDR DATA 7-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.3.2 COLLATING BCFS INTO CDFS 7-9. . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.3.3 GENERATING OUTPUT FILES 7-11. . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.4 USING AUTOMATIC PROCESSING 7-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.4.1 PREPARING FOR AUTOMATIC PROCESSING 7-14. . . . . . . . . . . . .
7.4.2 STARTING AUTOMATIC PROCESSING 7-15. . . . . . . . . . . . . . . . . . .
7.5 USING SCHEDULED AUTOMATIC PROCESSING 7-16. . . . . . . . . . . . . . . .
7.5.1 UPDATING AUTOMATIC PROCESSING SCHEDULES 7-18. . . . .
7.5.1.1 Option 1, Add a New Schedule 7-18. . . . . . . . . . . . . . . . .
7.5.1.2 Option 2, Edit an Existing Schedule 7-22. . . . . . . . . . . .
Section Page
C O N T E N T S
7-iv Edition 2 Octel PC/CDR
7.5.1.3 Option 3, Remove an Existing Schedule 7-22. . . . . . . .
7.5.1.4 Option 4, List Existing Schedules 7-23. . . . . . . . . . . . . .
7.5.1.5 Option 5, Print Existing Schedules 7-24. . . . . . . . . . . . .
7.5.1.6 Option 6, Backup Schedule Parameter File 7-24. . . . .
7.5.1.7 Option 7, Restore Schedule Parameter File 7-26. . . . .
7.5.2 STARTING THE AUTOMATIC SCHEDULER MODE 7-27. . . . . . .
7.5.2.1 Using the Octel PC/CDR Automatic Schedule Menu 7-28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.5.2.2 Using DOS 7-28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.5.3 UPDATING THE SCHEDULE PASSWORD 7-29. . . . . . . . . . . . . . . .
7.5.4 UPDATING AUTOMATIC-SCHEDULER LOG FILES 7-30. . . . . . . .
7.5.4.1 Option 1, List Schedule Log File 7-31. . . . . . . . . . . . . . . .
7.5.4.2 Option 2, Print Schedule Log File 7-32. . . . . . . . . . . . . .
7.5.4.3 Option 3, Backup Schedule Log File 7-32. . . . . . . . . . . .
7.5.4.4 Option 4, Restore Schedule Log File 7-34. . . . . . . . . . . .
7.5.4.5 Option 5, Erase Schedule Log File 7-36. . . . . . . . . . . . . .
7.6 USING THE SERVICE-LEVEL DOWNLOAD 7-36. . . . . . . . . . . . . . . . . . . . . .
7.6.1 USING THE OCTEL PC/CDR SYSTEM MENU 7-37. . . . . . . . . . . .
7.6.2 USING DOS 7-40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Section Page
C O N T E N T S
7-vEdition 2Octel PC/CDR
TABLESTable 7-1. Processing Steps 7-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 7-2. Descriptions of Begin File Transfer Screen Columns 7-4. . . . .
Table 7-3. Collate Processing Screen Column Descriptions 7-10. . . . . . . . .
Table 7-4. Descriptions of Output File Processing Screen Fields 7-13. . . .
Table 7-5. Descriptions of Octel PC/CDR Automatic Schedule Menu Options 7-18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FIGURESFigure 7-1. Example of Octel PC/CDR System Attributes Menu 7-2. . . . . .
Figure 7-2. Begin File Transfer Screen 7-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 7-3. Error Message That Block Numbers in BCF Are Out of Sequence 7-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 7-4. Octel PC/CDR System Menu 7-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 7-5. Manual Octel PC/CDR Processing Menu 7-7. . . . . . . . . . . . . . . . .
Figure 7-6. Octel PC/CDR File Download Settings Menu 7-8. . . . . . . . . . . . .
Figure 7-7. Collate Processing Screen 7-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 7-8. Octel PC/CDR Output File Generation Menu 7-12. . . . . . . . . . .
Figure 7-9. Example of Initial Session-Detail Output File Processing Screen 7-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 7-10. Example of Session-Detail Output File Processing Screen After Files Are Generated 7-13. . . . . . . . . . . . . . . . . . . . . . . .
Figure 7-11. Modify Automatic Output File Generation Menu 7-15. . . . . . . .
Figure 7-12. Octel PC/CDR Main Menu 7-17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Page
C O N T E N T S
7-vi Edition 2 Octel PC/CDR
Figure 7-13. Octel PC/CDR Automatic Schedule Menu 7-17. . . . . . . . . . . . . . .
Figure 7-14. Octel PC/CDR Update Automatic Processing Schedules Menu 7-18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 7-15. Example of Automatic Octel PC/CDR Schedule Editor Menu 7-21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 7-16. Example of Automatic Octel PC/CDR Schedule List, Showing Schedule 1 7-23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 7-17. Example of the Octel PC/CDR Processing Schedule Screen, With Timer Running 7-27. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 7-18. Octel PC/CDR Update Automatic Scheduler Log File Menu 7-30. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 7-19. Example of a Schedule Log File 7-31. . . . . . . . . . . . . . . . . . . . . . . . .
Figure 7-20. SMT Menu 16.1.2, Retrieve Call Detail Records 7-39. . . . . . . . .
Figure 7-21. SMT Menu 16.1.2, Database Access, Retrieve Call Detail Records, Showing Command Line 7-39. . . . . . . . . . . . . . . .
Figure 7-22. Octel PC/CDR Block Retrieval Transfer Screen 7-39. . . . . . . . .
Page
C H A P T E R 7
Octel PC/CDR Edition 2 7-1
PROCESSING METHODS
7.1 OVERVIEW
Before CDR data can be processed into output files, it must be downloaded fromthe CDR buffer on the server to the CDR PC. Octel PC/CDR offers the followingfour methods for downloading and processing CDR data:
� Manual
� Automatic
� Scheduled automatic
� Service-level download
The processing steps shown in Table 7-1 are performed with each of these firstthree methods.
Table 7-1. Processing Steps.
Step Description
1. The PC is linked with the server and CDR data is down-loaded into binary collection files (BCFs) on the PC.
2. The BCFs are collated into collated day files (CDFs).
3. Selected output files are generated.
The service-level download is used primarily by Octel and distributor servicerepresentatives for downloading specific data blocks. These files are thenprocessed using the manual method.
Determine which sections of this chapter apply to your choice of processingmethod, as follows:
If you are using . . .
Refer to section 7.2 for preliminaryinformation and steps and to the followingsection for processing details . . .
Manual processing Section 7.3
Automatic processing Section 7.4
Scheduled automatic processing
Section 7.5
Service-level download Section 7.6
Access the Octel PC/CDR Main Menu by typing cdr or the CDR system name atthe DOS prompt. Refer to section 5.2 for additional instructions.
PROCESSING METHODS
7-2 Edition 2 Octel PC/CDR
7.2 PREPARING TO PROCESS DATA
Before proceeding with CDR data processing, complete the tasks in sections7.2.1 through 7.2.5 and become familiar with the data transfer screens, log files,and error messages. Transmission messages and messages recorded in theschedule log file are described in Appendixes E and F.
7.2.1 COMPLETING PRELIMINARY TASKS
Before you download and process CDR data, complete the following tasks:
Step Task Reference
1. Confirm that the connection between thePC and the server has been establishedand that the data cable between the PCand the server is connected to the correctchannel on the server.
Refer to Chapters 4 and 11 forinformation about connecting theserver to the PC and configuringmenu 6.3 on the system managerterminal (SMT).
2. Confirm that the options in the Octel PC/CDR System Attributes menu, shownin Figure 7-1, are set appropriately.
Refer to Chapter 5 for informationabout establishing Octel PC/CDRsystem attributes.
3. Check that the CDR buffer is not full andthat unretrieved blocks have not beenoverwritten. Do this by viewing menu16.1.1 on the SMT. Always perform thisstep before starting a download.
Refer to section 2.4.3 for details.
4. Check the Display Disk Status screen(option 1 on the Octel PC/CDR File Utili-ties Menu) to determine whether there isenough disk-storage space available onthe PC hard drive for the data to bedownloaded. Always perform this stepbefore starting a download.
Refer to Chapter 8 for informationabout the Display Disk Statusscreen, and refer to Chapter 2 forPC hard-drive-sizing information.
Octel PC/CDR System Attributes Menu westreg
0 Save Attributes & Return to PC/CDR System Menu
Current Setting1 Log Octel PC/CDR Processing Output to Printer? (y/n) NO2 Binary Collection Files Erased After Collation? (y/n) NO3 Erase Binary and Collated Day Files Beyond .. Days: Permanent4 Erase All Output & Log Files Beyond .. Days: Permanent5 Modify Automatic Output File Generation6 Modify Output File Format Types7 Modify Communications Parameters8 Next Block to Download by Automatic Octel PC/CDR Processing9 Modify Output File Format Level: 6
Enter Option (ESC to Abort Changes):
Figure 7-1. Example of Octel PC/CDRSystem Attributes Menu.
SECTION 7.2
PROCESSING METHODS
Octel PC/CDR Edition 2 7-3
7.2.2 UNDERSTANDING DATA TRANSFER
Octel PC/CDR uses MIRROR II software to provide the communication linkbetween the PC and the server. The MIRROR II software transfers data using theXMODEM file-transfer protocol and the data-transfer-verification method withthe cyclical-redundancy-check (CRC) calculation.
While CDR data downloads, the PC screen displays the number of blocks beingdownloaded on a screen similar to Figure 7-2. These transmission blocks differin size from the CDR blocks stored in the CDR buffer in the server. Each blockcounted on this screen contains 128 bytes of data rather than the 2048 bytesstored within each CDR block in the buffer.
Begin file transfer . .
Receiving C:\westreg\bcf\A960726A.BCF – using CRC
Block # % Complete Consec.errors Total errors
2400 –– none 1
PROTOCOL TRANSFER UNDERWAY––Press F3 to cancel
Figure 7-2. Begin File Transfer Screen.
Using the XMODEM file-transfer protocol, the first block downloaded is alwayscounted as block 0. For example,
If 150 CDR blocks are downloaded, beginning with CDR block 1000, the filetransfer screen initially shows a 0 in the Block # column. Each 2048-byte CDRblock is actually downloaded in 128-byte increments (2048 divided by 16).When the download is complete, the entry in the Block # column shows thatapproximately 2400 blocks (16 times 150) were downloaded.
Data transmission is verified using the CRC calculation method. Refer toTable 7-2 for descriptions of the data transmission fields on the Begin filetransfer . . screen (Figure 7-2).
SECTION 7.2
PROCESSING METHODS
7-4 Edition 2 Octel PC/CDR
Table 7-2. Descriptions of Begin File Transfer Screen Columns.
Column Heading Description
Block # This column contains the number of the current 128-byte packetbeing downloaded.
% Complete This column always shows – –.
Consec. errors The counter in the Consec. errors column increments to show thenumber of retries, while attempting to download the current block.After the initial attempt is made, the number in this column increments by 1 for each retry. After the packet is successfully downloaded, the entry in this column is reset to none. If a packetdownloads on the first attempt, nothing registers in this column.
Octel PC/CDR tries up to 10 times to download each 128-byte packet. If a packet is not successfully downloaded after 10 attempts,the communications session ends, and the link to the server is disconnected.
Total errors The counter in the Total errors column is incremented by the finalcount in the Consec. errors column for each 128-byte-packet download-retry attempt. For example,
If all packets are successfully sent on the first try until packet1726, and it takes three attempts to download packet 1726, theentry in the Total errors column changes from none to 3. If itthen takes seven attempts to download packet 1727, the entry is incremented to 10 (3 errors plus 7 errors).
The final number in this field is the cumulative total of the number of times that all 128-byte packets failed attempts to download beforethe total download was successful. This number is the total of all thehighest entries in the Consec. errors column for all packets.
7.2.3 LEARNING ABOUT PARTIALLY FILLED BLOCKS
When a download is performed, if you request all blocks that have not yet beendownloaded, the block currently being filled by the server is also downloaded.The server begins filling a new block when the download is started. It does notreturn to fill the partially filled block.
7.2.4 LOCATING LOG FILE ENTRIES
CDR system log files contain the status of the CDR buffer before a downloadbegins (as displayed in SMT menu 16.1.1) and copies of the screens displayedduring collation and output-file generation. These log files are stored in the SYSsubdirectory for the CDR system for which the process occurred. Refer to section 1.9.5 for details about CDR system log files.
An additional log file, called SCHEDCDR.LOG, is created when the scheduledautomatic method of processing is used. This file records the actions of thescheduler. Refer to section 7.5.4 for information about this log file and toAppendix F for a description of the most common entries.
SECTION 7.2
PROCESSING METHODS
Octel PC/CDR Edition 2 7-5
7.2.5 UNDERSTANDING TRANSMISSION AND ERRORMESSAGES
Several informational and error messages might be seen during the download,collation, and output-file generation processes. After processing data, view theCDR system log file (as described in Chapter 1) to check for error messages andincomplete processes.
When an error message appears during automatic processing or scheduledautomatic processing, the software waits a short time for a response; if it is notreceived, it skips the process in error and proceeds to the next process.
Informational messages and error messages can occur for the reasons explainedin sections 7.2.5.1 through 7.2.5.7. If you need to contact your Octel or distribu-tor service representative for assistance with a transmission or error message,first copy and complete the Octel PC/CDR Troubleshooting Form found inAppendix G.
7.2.5.1 Transmission Messages. During the download process, the servermight display transmission messages on the PC screen. These messages arelisted and explained in Appendix E.
7.2.5.2 Overwritten Blocks. If blocks of data in the CDR buffer areoverwritten before they are downloaded, a download cannot be performed andthe message Starting block number is not valid. appears briefly on thescreen. This message is also recorded in the CDR system log file. Refer to SMTmenu 16.1.1 to confirm that blocks were overwritten, then clear the lost datacounter, and start the download process again. Refer to sections 2.4.3 and 2.4.5for information about menu 16.1.1 and clearing the lost data counter.
7.2.5.3 Prior PSF Data Not Found. The first time data is collated for a newCDR system, the following message appears:
No prior PSF data foundDo you wish to start COLLATE from scratch? (y/n):
Press Y and Enter to start the collation for the first time.
During scheduled automatic processing, the message No prior PSF data foundis displayed, and the collation continues.
7.2.5.4 Block Numbers in BCF Are out of Sequence. The message Error:Block Numbers in BCF are out of Sequence and the prompt Do you wish toskip overlapping blocks? (y/n): appear on the screen during the collationprocess when previously collated blocks are found in the BCF. This message andprompt are shown in Figure 7-3. Press Y and Enter to skip the overlappingblocks and collate only the blocks containing new data. The collate continueswith the first new block.
If this error occurs while using scheduled automatic processing, overlappingblocks are automatically skipped and the process continues.
SECTION 7.2
PROCESSING METHODS
7-6 Edition 2 Octel PC/CDR
******************************************************************************* Error: Block Numbers in BCF are out of Sequence **** Current Block: 50, Last Block Processed: 100 *******************************************************************************Do you wish to skip overlapping blocks? (y/n):
Figure 7-3. Error Message That Block Numbersin BCF Are Out of Sequence.
7.2.5.5 Filled Hard Drive. Always confirm the amount of storage spaceavailable on the PC hard drive before starting any Octel PC/CDR processes. Ifthe PC is about to run out of storage space while collating data, the followingprompt appears:
Less than 100 kbytes remaining on disk.
Shutting down as a precaution.
Last block processed: [block number]
When the PC hard-drive storage space is low, create more storage space usingone of the following methods, and then restart the collation:
� Back up and then delete unnecessary files from the hard drive.
� Install a larger or additional hard drive.
7.2.5.6 No Previous Day File Available. If the prompt Warning: For DateAbove, No Previous Day File Available appears while generating individual-port-statistics output (PSO) files, there might be a missing CDF or there was noCDR data generated on the day preceding the last date entered before thewarning. This prompt could also appear if there are corrupted blocks of data inthe CDF for the missing date. If the skipped date was a normal working day or ifyou suspect a corrupted block, contact your local Octel or distributor supportoffice for assistance. Refer to Chapter 9 for additional information about PSOfiles.
7.2.5.7 Backup Utility Errors. If you are using DOS 6.2 or newer, the OctelPC/CDR backup utilities might not work. Refer to sections 7.5.1.6 and 7.5.4.3for additional information.
7.3 USING MANUAL PROCESSING
When you use the manual processing method, each of the three processing steps(shown in Table 7-1) is performed individually. Use this method to becomefamiliar with the processing steps and when setting up a new server for down-loading. With this method, each step is selected and performed sequentially.Once the manual processing method is working correctly, establish and use theautomatic method. The automatic method performs processing in the samesequence as the manual method, but does not require user input for each step.
SECTION 7.2 – 7.3
PROCESSING METHODS
Octel PC/CDR Edition 2 7-7
7.3.1 DOWNLOADING CDR DATA
Prepare to download CDR data manually, as follows:
Step Action Result
1. Confirm that the tasks in section7.2.1 have been completed.
. . .
2. At the DOS prompt, type a valid CDRsystem name, and press Enter.
If the system manager password hasbeen established, the password isrequested.
If the system manager password hasnot been established, a promptrequests that you press Enter tocontinue.
3. If the system manager password hasbeen established, type the password,and press Enter.
If the system manager password hasnot been established, press Enter.
The Octel PC/CDR System Menuappears, similar to the screen shownin Figure 7-4.
4. Select option 2, and press Enter. The Manual Octel PC/CDR Proces-sing Menu appears, similar to thescreen shown in Figure 7-5. The op-tions listed on this menu are also thesteps required to process CDR data.
5. Select option 1, and press Enter. A screen similar to Figure 7-6appears.
Octel PC/CDR System Menu, REV 2.30 westreg
0 Exit
1 Update Octel PC System Attributes2 Manual Octel PC/CDR Processing3 Automatic Octel PC/CDR Processing4 File Utilities5 Link with Octel Server for Performing System Manager Functions
Enter Option:
Figure 7-4. Octel PC/CDR System Menu.
Manual Octel PC/CDR Processing Menu westreg
0 Return to System Menu
1 Link with Octel Server and Download Octel PC/CDR Data2 Collate Octel PC/CDR Binary Collection Files from Octel Server3 Generate Octel PC/CDR Output Files
Enter Option:
Figure 7-5. Manual Octel PC/CDR Processing Menu.
SECTION 7.3
PROCESSING METHODS
7-8 Edition 2 Octel PC/CDR
Octel PC/CDR File Download Settings westreg
0 Proceed to Download (ESC to Return)
Current Setting1 Binary Collection File Name A960725A.BCF2 First Block Number to Download3 Number of Blocks to Download
Enter Option:
Figure 7-6. Octel PC/CDR File Download Settings Menu.
Use the default entries for options 1, 2, and 3 on the Octel PC/CDR FileDownload Settings menu (Figure 7-6). If specific blocks are needed, perform thedownload as instructed, and then isolate the necessary blocks using theCOPYBCF command described in section 8.8.2.
Start the download, as follows:
Step Action Result
1. From the Octel PC/CDR File Down-load Settings menu (Figure 7-6),select option 0, and press Enter.
The password is requested if it wasnot established earlier in the OctelPC/CDR System Attributes Menu(Figure 7-1).
2. If the password is requested, typethe system manager password, andpress Enter.
The download begins, as explainedin step 3.
3. If the password is not requested, thedownload begins immediately.
As the download process progresses,various Octel PC/CDR and SMT me-nus appear on the screen. The col-umns on the Begin file transfer . .screen are described in section 7.2.2.No action is necessary until thedownload is completed.
When the blocks of data have beensuccessfully downloaded to the PChard drive, the message RetrievalComplete appears briefly at the bot-tom of the screen. A summary screenshowing the retrieved blocks andBCF file name appears, with the following prompt:
Press ENTER/RETURN to continue.
4. Press Enter. The Manual Octel PC/CDR Proces-sing Menu reappears (Figure 7-5).
When a download is performed, the block currently being filled by the server isalso downloaded. The server begins filling a new block when the download isstarted. It does not complete filling the partially filled block that was down-loaded. Refer to Chapter 2 for additional information about blocks.
SECTION 7.3
PROCESSING METHODS
Octel PC/CDR Edition 2 7-9
7.3.2 COLLATING BCFS INTO CDFS
The CDR data downloaded from the server into binary collection files (BCFs)must be collated into collated day files (CDFs) before CDR output files can begenerated. The collation process sorts the BCF into separate groups of eventsassociated with each call. This process creates a CDF or appends alreadyexisting CDFs to the call events contained in the BCF source files. One CDF is created for every date for which call events existed in the BCF.
Collate BCFs into CDFs, as follows:
Step Action Result
1. From the Manual Octel PC/CDR Processing Menu (Figure 7-5), selectoption 2, and press Enter.
Octel PC/CDR searches the CDRsystem subdirectory for BCFs thathave not been collated and displaystheir file names. It also locates theCOLLATE.PSF file in the SYS sub-directory to include that file with theBCF to create the new CDF. (Pend-ing-state files [PSFs] are described inChapter 1.) A screen similar to thefirst four lines of Figure 7-7 and thefollowing prompt appear:
Proceed with the Collation ofthese Files? (y/n):
2. Press Y and Enter to begin collating. During collation, fields similar to theremaining fields shown in Figure 7-7are displayed. The data in thesefields continues to develop until all BCFs are collated. The BCF filename, creation date, and other sum-mary information appear on thescreen as each BCF is collated. Referto Table 7-3 for a description of thecolumns on this screen.
If an error message appears on thescreen during collation, refer to section 7.2.5 for instructions abouthow to proceed.
The collation is complete when thefollowing prompt appears:
Waiting to return to menu. PressENTER/RETURN to continue.
3. Press Enter. The Manual Octel PC/CDR Proces-sing Menu reappears (Figure 7-5).
After the BCFs are collated, the final collation summary, similar to the screenshown in Figure 7-7, is added to the CDR system log file.
SECTION 7.3
PROCESSING METHODS
7-10 Edition 2 Octel PC/CDR
Begin Collate ProcessingFound 2 Octel PC/CDR Binary Collection File(s):
A960725A A960726AProceed with the Collation of these Files? (y/n): Y
>>07–27–96 09:21:14 Collating CDR Files>>System: westreg
CDR Input File Creation System CDR Total Events CallsFile Name Date & Time Blocks Events Rejected Passed
A960725A.BCF 07–25–96 1246 955–1054 1166 0 498A960726A.BCF 07–26–96 09:57:00 1054–1454 44380 0 86581246
Waiting to return to menu.Press ENTER/RETURN to continue.
10:29:16
ID #
Figure 7-7. Collate Processing Screen.
Table 7-3. Collate Processing Screen Column Descriptions.
Column Description
CDR Input FileName
The BCF name as it is prepared for collation.
File Creation Date & Time
The date and time that the BCF was created.
System ID # The serial number of the server from which the BCF was taken.These serial numbers are important if data from multiple servers isprocessed by the same PC.
CDR Blocks A range showing the beginning and ending numbers of the CDRblocks contained in the BCF.
Total Events The number of accumulated events within the BCF.
Events Rejected Because individual events sometimes cannot be associated withcalls and the server has not recorded a beginning for a call, theseevents cannot be processed. This information might indicate sever-al rejected events at the time Octel PC/CDR is installed; however,after the first time BCFs are collated, no events should be rejected.If rejected events are logged, save the BCF (or PCF) and contactyour local Octel or distributor service representative for assistance.Rejected events are also documented in the log file.
Calls Passed The total number of calls successfully collated and placed in CDFs.
SECTION 7.3
PROCESSING METHODS
Octel PC/CDR Edition 2 7-11
7.3.3 GENERATING OUTPUT FILES
Output files contain CDR events organized by subject. CDR events are collectedin the CDR buffer, based on the record types selected in SMT menu 16.1.4(described in Chapter 2). Output files can be generated only for record types that were selected in menu 16.1.4.
Generate only the output files that contain required information, so that PCdisk-storage space is not filled unnecessarily. Not all output files are needed for every application. Refer to Chapter 9 for output-file descriptions.
When selected for generation, an output file with data is created for each day in which the associated events are found in the source CDF. When there are noassociated events for a given date in the CDF, an output file with no data iscreated.
� If the output file was created in dBASE III format, it contains only thecolumn names.
� If the output file was created in ASCII format, it is an empty file.
Generate output files, as follows:
Step Action Result
1. From the Manual Octel PC/CDR Processing Menu (Figure 7-5), selectoption 3, and press Enter.
The Octel PC/CDR Output File Generation Menu appears, similar to Figure 7-8.
2. Type the option number of the outputfile to be generated, and press Enter.
The first four lines of the output-fileprocessing screen appear, similar tothe one shown in Figure 7-9. AllCDFs that have not been processedfor the selected output file are listed,beginning on the third line.
3. To process these files, press Y andEnter.
The remaining fields appear on thescreen, similar to the screen shown inFigure 7-10. Entries in the fieldsdevelop as the selected output file isgenerated. The fields and columns onthis screen vary, depending on theoutput file selected. Refer to Chapter9 for information about the interpre-tation of columns on the processingscreens, which are specific to the dif-ferent output files. Refer to Table 7-4for a definition of the fields found onall output file processing screens.
When the selected output files areprocessed, the following promptappears:
Waiting to return to menu. PressENTER/RETURN to continue.
SECTION 7.3
PROCESSING METHODS
7-12 Edition 2 Octel PC/CDR
Step ResultAction
4. Press Enter to return to the OctelPC/CDR Output File GenerationMenu.
The Octel PC/CDR Output FileGeneration Menu reappears(Figure 7-8).
5. Repeat steps 2, 3, and 4 until all of the required output files are generated.
. . .
6. To return to the Manual Octel PC/CDR Processing Menu, type 0, andpress Enter.
The Manual Octel PC/CDR Proces-sing Menu reappears (Figure 7-5).
Octel PC/CDR Output File Generation Menu westreg
0 Return to Manual Octel PC/CDR Processing Menu
1 Generate Session Detail Output Files2 Generate Unsuccessful Transfer Output Files3 Generate Message Detail Output Files4 Generate Individual Port Statistics Output Files5 Generate Fax Output Files6 Generate Profile Change Output Files7 Generate Disk Usage Output Files8 Generate Caller Menu Output Files9 Generate NameNet Output Files
10 Generate Forms Output File Records
Enter Option:
Figure 7-8. Octel PC/CDR Output FileGeneration Menu.
Begin Session Detail ProcessingFound 2 New or Updating Collated Day File(s):
CD960627 CD960628Do you wish to proceed making Session Detail files? (y/n):
Figure 7-9. Example of Initial Session-DetailOutput File Processing Screen.
SECTION 7.3
PROCESSING METHODS
Octel PC/CDR Edition 2 7-13
Begin Session Detail ProcessingFound 2 New or Updated Collated Day File(s):
CD960727 CD960728Do you wish to proceed making Session Detail files? (y/n): Y
>>07–29–96 11:16:52 Creating Session Detail Output Files>>System: westreg, File Format: 1, Level: 6
CDF Input System CallsTotal Calls & SessionsCallsFile Date ID # IgnoredCalls PassedFailed
07–27–96 0310 3537 0
Waiting to return to menu.Press ENTER/RETURN to continue.
Other
1256
MessagesSent & Deleted
2281 2672 1497 1405
UnsucXfers
007–28–96 0310 4175 0 1598 2577 3080 2060 1712 1
Figure 7-10. Example of Session-Detail Output FileProcessing Screen After Files Are Generated.
Table 7-4. Descriptions of Output File Processing Screen Fields.
Field Name Description
Found [number] New orUpdated Collated DayFile(s):
Displays the names of the CDFs that were added orupdated since the last collation and the number of CDFsfound in the CDF subdirectory for the CDR system.
Do you wish to proceedmaking [output file name]files? (y/n):
Initially, only the output file processing screen is displayedto this point. Pressing Y continues the generation of theselected output file, as described earlier in this section.
System: The name of the CDR system for which the CDFs containdata.
File Format: The number of the file-format type selected when configur-ing the Modify Output File Format Types option on theOctel PC/CDR System Attributes Menu (as described inChapter 5). For example, file-format 7 is dBASE III compatible.
Level: The number of the file-format level selected when configur-ing the Modify Output File Format Level: field on theOctel PC/CDR System Attributes Menu (as described inChapter 5).
7.4 USING AUTOMATIC PROCESSING
The automatic CDR processing method downloads, collates, and generatesoutput files in one step. This method uses the Octel PC/CDR system attributesthat must be set before automatic processing can be executed (Chapter 5). Usethis processing method after you have become familiar with the three processingsteps listed in Table 7-1 while using the manual processing method.
SECTION 7.3 – 7.4
PROCESSING METHODS
7-14 Edition 2 Octel PC/CDR
7.4.1 PREPARING FOR AUTOMATIC PROCESSING
Select output files for automatic generation, establish the password, and selectthe starting block number for the download, as follows:
Step Action Result
1. At the DOS prompt, type a valid CDRsystem name, and press Enter.
If the system manager password hasbeen established, the password isrequested.
If the system manager password hasnot been established, a promptrequests that you press Enter tocontinue.
2. If the system manager password hasbeen established, type the password,and press Enter.
If the system manager password hasnot been established, press Enter.
The Octel PC/CDR System Menuappears, (Figure 7-4).
3. Select option 1, and press Enter. The Octel PC/CDR System AttributesMenu appears (Figure 7-1).
4. To select the output files that are tobe automatically generated after thedownload is performed, select option5, and press Enter.
The Modify Automatic Output FileGeneration menu appears, as shownin Figure 7-11.
5. Select the output files to be gener-ated by typing the option numbercorresponding to the desired outputfile and then pressing Enter. Chooseoption 99 to select all output files forgeneration.
The system toggles YES and NOchoices in the Current Setting col-umn for each selected output file.
6. After you have selected the desiredfiles, select option 0, and pressEnter.
The Octel PC/CDR System AttributesMenu reappears (Figure 7-1).
7. If you have not already establishedthe system manager password, referto section 5.3.7 and enter the pass-word. This password must be estab-lished before using the automaticprocessing method.
. . .
8. To save the changes and return tothe PC/CDR System Menu, selectoption 0, and press Enter.
The changes are saved and the PC/CDR System Menu reappears(Figure 7-4).
SECTION 7.4
PROCESSING METHODS
Octel PC/CDR Edition 2 7-15
westregModify Automatic Output File Generation
0 Return to System Attributes MenuCurrent Setting
1 Generate Session Detail Output File NO2 Generate Unsuccessful Transfer Output File NO3 Generate Message Detail Output File NO4 Generate Individual Port Statistics Output File NO5 Generate Fax Output File NO6 Generate Profile Change Output File NO7 Generate Disk Usage Output File NO8 Generate Caller Menu Output File NO9 Generate NameNet Output File NO
10 Append Records to Forms Output File NO
99 Generate All Output Files NO
Enter Option:
Figure 7-11. Modify Automatic Output FileGeneration Menu.
7.4.2 STARTING AUTOMATIC PROCESSING
Start automatic processing in one of the following ways:
� Select option 3, Automatic Octel PC/CDR Processing from the OctelPC/CDR System Menu (Figure 7-4), and press Enter. Octel PC/CDR dataprocessing begins.
This method returns the screen to the Octel PC/CDR System Menu afterprocessing is complete.
� At the DOS prompt, type systemname -axxxx, where systemname repre-sents the name assigned to the CDR system (section 3.3), -a representsautomatic processing, and xxxx represents the system manager password ofany length. Press Enter. Octel PC/CDR data processing begins. For example,
Type westreg -a7267622242 to begin automatic processing for the CDRsystem called westreg, with the system manager password of7267622242.
This method returns the screen to the DOS prompt after processing iscomplete.
Regardless of which way you choose to execute automatic processing, the threeprocessing steps shown in Table 7-1 are performed.
SECTION 7.4
PROCESSING METHODS
7-16 Edition 2 Octel PC/CDR
7.5 USING SCHEDULED AUTOMATIC PROCESSING
Octel PC/CDR can process data from one server or from multiple serversautomatically, at scheduled intervals. Use the scheduled automatic processingmethod to process CDR data in the evenings or on weekends, when the CDR PCis not needed for performing other Octel PC/CDR functions.
Important information about scheduled automatic processing is as follows:
� To use this method, the CDR PC must be dedicated to running the schedulerthat automatically executes the downloading and processing of Octel PC/CDRdata.
� The Octel PC/CDR Processing Schedule screen must be displayed on the PCscreen for the scheduler to work (refer to section 7.5.2).
� Two passwords are used with scheduled automatic processing:
� The system manager password, which must first be established in theOctel PC/CDR system attributes (refer to section 5.3.7).
� The schedule password, which must be established if you want toexecute the schedule from the DOS prompt (refer to section 7.5.3).
� The scheduled automatic processing method performs all of the stepsrequired to process CDR data (Table 7-1).
� The scheduler can execute a program or batch file that resides on the CDRPC. (You can use batch files for processing additional output files, such asbills or statistical analyses.)
� You can create as many as 10 different schedules.
� Each schedule can specify up to 10 different servers (CDR systems),programs, or batch files.
� The minimum time that you can set between downloads is 3 minutes.
� You can change the default starting date, starting time, and interval.
� Schedules are not executed on the date shown in the Date/Time of NextExecution: field if option 2, Start Automatic Scheduler Mode on the Octel PC/CDR Automatic Schedule Menu (Figure 7-13) is not selected whenthat date arrives. If the scheduled date has passed, select option 2, StartAutomatic Scheduler Mode, and these schedules are automaticallyexecuted, regardless of how old the date of execution is. If you do not want aschedule to be executed after its date of execution, remove the schedule orchange the entry in the Date/Time of Next Execution: field to a later date.Refer to section 7.5.1 for information about removing and editing schedules.
The automatic scheduler uses the current Octel PC/CDR system attributes toconnect and process data files for each CDR system. Update system attributes, if necessary, before proceeding.
SECTION 7.5
PROCESSING METHODS
Octel PC/CDR Edition 2 7-17
Access the Octel PC/CDR Automatic Schedule Menu, as follows:
Step Action Result
1. To access the Octel PC/CDR MainMenu from the DOS prompt, type cdr,and press Enter.
To go directly to the Octel PC/CDRAutomatic Schedule Menu from theDOS prompt, type schedcdr, pressEnter, and then go to step 3.
The Octel logo and Call DetailRecords Package banner screensappear briefly and then the Octel PC/CDR Main Menu appears, asshown in Figure 7-12.
2. Select option 2, and press Enter. If the schedule password has notbeen established, the prompt indi-cates that no password has been es-tablished. (Refer to section 7.5.3, andestablish the schedule password.)
If the schedule password was estab-lished, you are prompted to enter thatpassword.
3. If the schedule password is requested,enter that password, and press Enter.Otherwise, just press Enter.
The Octel PC/CDR AutomaticSchedule Menu appears, as shown inFigure 7-13.
Octel PC/CDR Main Menu, REV 2.30
0 Exit to DOS
1 Select an Individual System for CDR Processing2 Automatic Scheduler Functions
Enter Option:
Figure 7-12. Octel PC/CDR Main Menu.
Octel PC/CDR Automatic Schedule Menu
0 Exit Menu
1 Update Automatic Processing Schedules2 Start Automatic Scheduler Mode3 Update Schedule Password4 Update Automatic Scheduler Log Files
Enter Option:
Figure 7-13. Octel PC/CDR Automatic Schedule Menu.
Refer to Table 7-5 for descriptions of the Octel PC/CDR Automatic ScheduleMenu options.
SECTION 7.5
PROCESSING METHODS
7-18 Edition 2 Octel PC/CDR
Table 7-5. Descriptions of Octel PC/CDRAutomatic Schedule Menu Options.
Option Option Name PurposeReferenceSection
1 Update AutomaticProcessing Schedules
Use this option to create schedules;modify, remove, list, and print existingschedules; and back up and restore schedules.
7.5.1
2 Start AutomaticScheduler Mode
Use this option to turn on the automatic-schedule timer. If no schedules have been created, the automatic-processing-scheduler function cannot be started.
7.5.2
3 Update SchedulePassword
Use this option to establish a passwordthat is required for access to the Octel PC/CDR Automatic Schedule Menu.
7.5.3
4 Update AutomaticScheduler Log Files
Use this option to update the associatedlog file and access utilities for log-filemaintenance.
7.5.4
7.5.1 UPDATING AUTOMATIC PROCESSING SCHEDULES
Use the options on the Update Automatic Processing Schedules menu, shown inFigure 7-14, to add, modify, or view automatic-processing schedules. This menualso provides several file-maintenance utilities.
Select option 1, Update Automatic Processing Schedules from the OctelPC/CDR Automatic Schedule Menu (Figure 7-13) to access the Update AutomaticProcessing Schedules menu (Figure 7-14). The options on the Update AutomaticProcessing Schedules menu are described in sections 7.5.1.1 through 7.5.1.7.
Octel PC/CDR Update Automatic Processing Schedules
0 Exit Menu
1 Add a New Schedule2 Edit an Existing Schedule3 Remove an Existing Schedule4 List Existing Schedules5 Print Existing Schedules6 Backup Schedule Parameter File7 Restore Schedule Parameter File
Enter Option:
Figure 7-14. Octel PC/CDR Update AutomaticProcessing Schedules Menu.
7.5.1.1 Option 1, Add a New Schedule. You must add and configure newschedules using this option before the automatic scheduler can be used. Beforeadding a schedule, make note of the exact names of the CDR systems to beincluded in the schedule. If necessary, display a list of valid CDR systems bytyping cdrhelp at the DOS prompt.
SECTION 7.5
PROCESSING METHODS
Octel PC/CDR Edition 2 7-19
Perform the following steps to add a schedule to the automatic scheduler:
Step Action Result
1. From the Octel PC/CDR Update Auto-matic Processing Schedules menu(Figure 7-14), select option 1, andpress Enter.
The following prompt appears:
Schedule # to add (1–10, or ESC):
2. Enter a unique number from 1through 10 for the schedule to becreated, and press Enter.
When a new schedule number is en-tered, the Automatic Octel PC/CDRSchedule Editor Menu, similar toFigure 7-15, appears.
If an existing schedule number is entered, a prompt indicates that the schedule number is already inuse and asks you to press ENTER/RETURN to continue. Press Enterand return to step 1.
3. Select option 1, and press Enter toenter a schedule name.
The following prompt appears:
Enter the name for this schedule:
4. Type a descriptive name for thisschedule, up to 15 characters long,and press Enter.
Although the name is optional, youshould assign an easily rememberedname to each schedule. This nameneed not be the same as the CDR sys-tem name. If you enter a name in thisfield, it also appears in the schedulelog file, as described in section 7.5.4.
The schedule name appears in theSchedule Name: field.
5. Select option 2 and press Enter to up-date the entry in the Date/Time ofNext Execution: field. The defaultentry for this field is 24 hours fromthe time this screen is accessed forupdating. For example,
If the screen is accessed July 9,1996, at 1:00 p.m., the default entryis 07–10–96 13:00.
The following prompt appears:
Enter the Date of the NextExecution (mm–dd–yy):
6. Type the date on which you want theschedule to be executed, and pressEnter.
If you do not want this schedule to beexecuted on a regular basis, tempo-rarily set the date to a future date, and then revise this entry when theschedule is to be activated again.
The following prompt appears:
Enter the Time of the Next Execution (hh:mm):
SECTION 7.5
PROCESSING METHODS
7-20 Edition 2 Octel PC/CDR
Step ResultAction
7. Type the time at which you want theschedule to be executed. Use the24-hour time format (for example, type10:00 for 10:00 a.m. and type 22:00for 10:00 p.m.). Press Enter.
The updated date and time are dis-played in the Date/Time of Next Execution: field.
The Date/Time of Next Execution:field is automatically updated, basedon the interval entered in step 8, afterthe current schedule is executed.
8. To change the default entry of 1 daybetween executions to another inter-val, select option 3, and press Enter.
The following prompt appears:
Enter the Time Interval BetweenExecutions (ddd:hh:mm):
where ddd represents the numberofdays between scheduled automaticdownloads and data processings andthe hh and mm represent hours andminutes, respectively.
9. Type the number representing the in-terval between executions, in the for-mat shown, and press Enter.
If the interval between scheduled automatic downloads and processingsis less than 1 day, enter the number of hours or minutes that should passbefore the schedule is to be executedagain. The minimum time that can beset between downloads is 3 minutes.For example,
If the schedule is to be executed every day at a specified time, type1:00:00. If the schedule is to beexecuted once each week (every 7days), type 7:00:00. If the scheduleis to be executed every 6 hours,type 0:06:00.
The revised interval is displayed inthe Interval Between Executions:field.
10. Select option 4 and press Enter to en-ter the name of the first CDR system,program, or batch file to be includedin this schedule.
The following prompt appears:
Enter the name of system 1:
11. Type the name of the first valid CDRsystem, program, or batch file to beexecuted, and press Enter.
The CDR system name, program, orbatch file appears in the System/Program Name 1: field.
SECTION 7.5
PROCESSING METHODS
Octel PC/CDR Edition 2 7-21
Step ResultAction
12. Repeat steps 10 and 11 for options 5through 13, until all CDR systems,programs, and batch files to be in-cluded in this schedule have beenlisted. For example,
Enter a CDR system name in theSystem/Program Name 1: field, andenter a batch file that executes anapplication that processes the datain the System/Program Name 2:field.
The entry is made in the correspond-ing field. Entries in options 4 through13 are processed sequentially whenthe schedule is executed.
13. Type 0 and press Enter to save thechanges and return to the Octel PC/CDR Update Automatic ProcessingSchedules screen.
The Octel PC/CDR Update AutomaticProcessing Schedules menureappears (Figure 7-14).
Automatic Octel PC/CDR Schedule Editor Menu
0 Exit Editing & Return to Main Menu
Current Setting for Schedule no. 11 Schedule Name:2 Date/Time of Next Execution: 07–20–96 12:453 Interval Between Executions: 001:00:00
4 System/Program Name 1:5 System/Program Name 2:6 System/Program Name 3:7 System/Program Name 4:8 System/Program Name 5:9 System/Program Name 6:
10 System/Program Name 7:11 System/Program Name 8:12 System/Program Name 9:13 System/Program Name 10:
Enter Option (ESC to Abort Changes):
Figure 7-15. Example of Automatic Octel PC/CDRSchedule Editor Menu.
Refer to section 7.5.2 for instructions about how to start the automaticscheduler.
Normally, all schedules are executed without any problems. However, you caninclude the same CDR system in more than one schedule. This provides abackup, which ensures that the required data is captured despite telephone-lineproblems or a server that might be temporarily out of service when the firstschedule is executed. Octel PC/CDR simply downloads and processes additionaldata during any additionally scheduled runs. For example,
If the CDR buffer is downloaded once a week, one schedule could run atmidnight and another schedule at 2:00 a.m. When the first schedule isexecuted, it might not be able to connect to a specific server (CDR system),because of telephone-line problems. However, when the 2:00 a.m. schedule
SECTION 7.5
PROCESSING METHODS
7-22 Edition 2 Octel PC/CDR
is executed, the connection is possible, and the download occurs. If the firstschedule was not executed, CDR data generated between midnight and 2:00a.m. is included in the second set of files created at 2:00 a.m. If the firstschedule was executed, the second schedule only downloads data generatedafter the download for the first schedule was completed.
7.5.1.2 Option 2, Edit an Existing Schedule. Use this option to change aparameter in an existing schedule, as follows:
Step Action Result
1. From the Octel PC/CDR Update Automatic Processing Schedulesmenu (Figure 7-14), select option 2,and press Enter.
The following prompt appears:
Schedule # to edit (1–10, or ESC):
2. Type the number of the schedule tobe edited, and press Enter.
When a valid number is entered, theAutomatic Octel PC/CDR ScheduleEditor Menu appears (similar toFigure 7-15), with the current schedule settings displayed.
3. Select the option number corre-sponding to the setting to bechanged, make the change, andpress Enter.
All changes made are reflected in theappropriate fields.
4. Type 0 and press Enter to save thechanges and return to the Octel PC/CDR Update Automatic ProcessingSchedules menu.
The Octel PC/CDR Update Automat-ic Processing Schedules menu reap-pears (Figure 7-14).
7.5.1.3 Option 3, Remove an Existing Schedule. Use this option to removea schedule that is no longer needed, as follows:
Step Action Result
1. From the Octel PC/CDR Update Au-tomatic Processing Schedules menu(Figure 7-14), select option 3, andpress Enter.
The following prompt appears:
Schedule # to delete (1–10, orESC):
2. Type the number of the schedule toremove, and press Enter.
A prompt appears, confirming thenumber and name (if used) of theschedule to be removed.
3. Press Y to remove the schedule, orpress N to cancel the deletion.
If you press Y, the schedule isremoved. If you pressed Y or N, theOctel PC/CDR Update AutomaticProcessing Schedules menu reap-pears (Figure 7-14).
SECTION 7.5
PROCESSING METHODS
Octel PC/CDR Edition 2 7-23
7.5.1.4 Option 4, List Existing Schedules. Use this option to review allexisting schedules, as follows:
Step Action Result
1. From the Octel PC/CDR Update Au-tomatic Processing Schedules menu(Figure 7-14), select option 4, andpress Enter.
The screen displays the first sched-ule, similar to the screen shown inFigure 7-16.
2. Press Enter to display additionalschedules.
Additional schedules appear sequentially.
3. When the last schedule is reviewed,press Enter to return to the OctelPC/CDR Update Automatic Process-ing Schedules menu.
The Octel PC/CDR UpdateAutomatic Processing Schedulesmenu reappears (Figure 7-14).
Automatic Octel PC/CDR Schedule 1 – Region1
Date/Time of Next Execution: 06–21–96 23:00Interval Between Executions: 001:00:00
System Name 1: westregSystem Name 2: eastregSystem Name 3:System Name 4:System Name 5:System Name 6:System Name 7:System Name 8:System Name 9:System Name 10:
Press ENTER/RETURN to continue, or ESC to abort.
Figure 7-16. Example of Automatic Octel PC/CDRSchedule List, Showing Schedule 1.
SECTION 7.5
PROCESSING METHODS
7-24 Edition 2 Octel PC/CDR
7.5.1.5 Option 5, Print Existing Schedules. Use option 5 to print allexisting schedules, as follows:
Step Action Result
1. From the Octel PC/CDR Update Au-tomatic Processing Schedules menu(Figure 7-14), select option 5, andpress Enter.
The following prompt appears:
Please make sure your printer isONLINE. Press ENTER/RETURN tocontinue, or ESC to abort.
2. Verify that the printer is on line. . . .
3. Press Enter to begin printing allschedules.
After the schedules are printed, theOctel PC/CDR Update AutomaticProcessing Schedules menu reap-pears (Figure 7-14).
If the printer is not correctly con-nected or not on line, the screen dis-plays the following prompt:
Write fault error writing devicePRNAbort, Retry, Ignore, Fail?
4. If the printer is not correctly con-nected or it is not on line, do the following:
� Press A to abort the process.
� Check the printer connections,and make sure the printer is online.
� Repeat steps 1, 2, and 3.
When the printing process is abortedand you had accessed the AutomaticScheduler Functions menu by typingcdr, the screen returns to the OctelPC/CDR Main Menu (Figure 7-12).
When the printing process is abortedand you had accessed the AutomaticScheduler Functions menu by typingschedcdr, the screen returns to theDOS prompt.
7.5.1.6 Option 6, Backup Schedule Parameter File. Use this option to back up the schedule parameter file (SCHEDCDR.PAR). Make a backup copy in theunlikely event that a PC hard-drive problem occurs or schedules are inadvertentlyerased from the hard drive. Keep the backup copy of the schedule parameter filein a secure location, so that you will not have to re-create the schedules.
If the CDR PC is using IBM DOS or MS-DOS version 6.2 or newer, the OctelPC/CDR backup utilities might not work. If the message Incorrect DOS versionor Error on backup. is displayed while using the Backup Schedule ParameterFile procedure, the DOS file required for this process is either not found on yourPC or not recognized. If one of these messages appears, exit to DOS and manuallycopy the SCHEDCDR.PAR file from the C:\OCTELCDR subdirectory to a floppydisk, following the instructions in your DOS manual.
SECTION 7.5
PROCESSING METHODS
Octel PC/CDR Edition 2 7-25
If the PC is using IBM DOS or MS-DOS version 3.2 through 5.0 (or version 6.2under some circumstances), back up the schedule-parameter file to a floppy diskusing the Backup Schedule Parameter File option, as follows:
Step Action Result
1. Have a blank, formatted floppy diskavailable, onto which you will copythe schedule parameter file(SCHEDCDR.PAR). If this file is toolarge to fit on one floppy disk, haveadditional, formatted floppy disks athand.
. . .
2. From the Octel PC/CDR Update Au-tomatic Processing Schedules menu(Figure 7-14), select option 6, andpress Enter.
The following prompt appears:The automatic Octel PC/CDRschedules file will be backed up.Do you wish to proceed withschedule file backup? (y/n):
3. Press Y and Enter to proceed. The following prompt appears:Destination Drive for Backup (A: to C:)?:
4. Insert the blank, formatted disk intothe disk drive, type the appropriateletter for this drive, followed by acolon (for example, type a:), andpress Enter.
A prompt similar to the followingappears:
Insert backup diskette 01 indrive A:WARNING! Files in the targetdrive A:\ root directory will beerasedPress any key to continue . . .
If the message Incorrect DOS versionor Error on backup. appears, refer toyour DOS manual and manually backup the SCHEDCDR.PAR file. Refer tothe introduction to this section formore information.
5. Press any key to continue. The backup process begins. If the diskbecomes full, you are prompted for ad-ditional disks.
Each backup disk is automaticallylabeled by the operation. This labelshows up as the volume name.
6. If several disks are used, make sureto label the disks in the order inwhich they are created (for example,disks 01, 02, 03, and so on), so thenumbers match the volume names.
After the schedules are copied to thedisk(s), the Octel PC/CDR Update Au-tomatic Processing Schedules menureappears (Figure 7-14).
7. Remove the last backup disk, labelit, and store all the floppy disks in asecure location.
. . .
SECTION 7.5
PROCESSING METHODS
7-26 Edition 2 Octel PC/CDR
7.5.1.7 Option 7, Restore Schedule Parameter File. If the scheduleparameter file (SCHEDCDR.PAR) was corrupted or erased in error and hadpreviously been backed up using option 6, Backup Schedule Parameter File,you can restore the file using option 7, Restore Schedule Parameter File. Ifthe schedule parameter file was backed up using a DOS command, refer to yourDOS manual for instructions about restoring (or copying) the SCHEDCDR.PARfile to the C:\OCTELCDR subdirectory.
Restore the schedule parameter file to the PC hard drive, as follows:
Step Action Result
1. From the Octel PC/CDR Update Auto-matic Processing Schedules menu(Figure 7-14), select option 7, andpress Enter.
The following prompt appears:
The automatic Octel PC/CDRschedules file will be restoredfrom the backup disk and theschedules in the restored filewill REPLACE any currentlyactive schedules.
Do you wish to proceed withschedule file restoration? (y/n):
2. Press Y and Enter to proceed. The Source Drive for Restore (A: toC:)?: prompt appears.
3. Type the letter of the drive containingthe backup disk, and press Enter.
A prompt similar to the followingappears:
Insert backup diskette 01 indrive A:Press any key to continue . . .
4. Insert disk 01 into the appropriatedrive. If several disks were used toback up the schedules, make sure toinsert them, when they are requested,in the order in which they werecreated (disk 01, 02, 03, and so on).
. . .
5. Press any key to restore the files to thehard drive.
As the files are restored, a messagebriefly appears on the screen, indi-cating the date and time that thefiles were backed up.
After the schedules are restored tothe hard drive, the screen returns tothe Octel PC/CDR Update AutomaticProcessing Schedules menu.
6. Remove the last backup disk and keepall the disks in a secure location.
. . .
SECTION 7.5SECTION 7.5
PROCESSING METHODS
Octel PC/CDR Edition 2 7-27
7.5.2 STARTING THE AUTOMATIC SCHEDULER MODE
The date and time entered in the Date/Time of Next Execution: field in theAutomatic Octel PC/CDR Schedule Editor Menu (Figure 7-15) determine thedate and time that automatic processing begins. The Octel PC/CDR ProcessingSchedule, as shown in Figure 7-17, must be displayed on the screen of the CDRPC for the previously defined schedules to be activated and for the automaticprocessor to work. If you wish, turn on the output-to-printer option (described insection 5.3.1) to print the processing steps for each scheduled CDR system asthey occur, for review at a later date.
If the CDR PC is to be left unattended while awaitingautomatic processing, secure it in a locked room or disablethe keyboard. Because the Octel PC/CDR ProcessingSchedule must remain on the screen for the schedules tobe executed at their respective times, server and OctelPC/CDR security could be compromised by attempts touse the CDR PC.
Caution!
Octel PC/CDR Processing Schedule 2 Automatic Octel PC/CDR Schedules waiting to be processed.Next Schedule is: 1 – Region1
Date/Time of Execution: 07–22–96 10:00Interval Between Executions: 001:00:00
Systems to be run are:
System Name 1: westregSystem Name 2: eastregSystem Name 3:System Name 4:System Name 5:System Name 6:System Name 7:System Name 8:System Name 9:System Name 10:
Waiting to process this schedule. Press ESC to cancel.
Time remaining before processing of this schedule: 000:18:59:27
Figure 7-17. Example of the Octel PC/CDR ProcessingSchedule Screen, With Timer Running.
Use one of the following methods to start the automatic-scheduler timer, so thatall existing schedules are executed at their respective starting times.
SECTION 7.5
PROCESSING METHODS
7-28 Edition 2 Octel PC/CDR
7.5.2.1 Using the Octel PC/CDR Automatic Schedule Menu. Execute aschedule using the Octel PC/CDR Automatic Schedule Menu, as follows:
Step Action Result
1. From the Octel PC/CDR AutomaticSchedule Menu (Figure 7-13), selectoption 2, and press Enter.
The Octel PC/CDR ProcessingSchedule screen, similar to thescreen shown in Figure 7-17, is dis-played and must remain displayedfor the schedules to be activated andfor the automatic processor to work.
2. Automatic processing takes place asscheduled, when the timer reaches000:00:00:00.
During processing, the screenschange. When the processing is com-pleted, the Octel PC/CDR ProcessingSchedule reappears (Figure 7-17).
3. Press Esc to return to the Octel PC/CDR Automatic Schedule Menu, ifyou do not want the schedule to runagain at the designated interval.
The Octel PC/CDR Automatic Sched-ule Menu reappears (Figure 7-13).
7.5.2.2 Using DOS. Execute a schedule from the DOS prompt, as follows:
Step Action Result
1. If not already established, establishthe scheduler password using option3, Update Schedule Password(explained in section 7.5.3).
. . .
2. Execute a schedule at the DOSprompt by typing schedcdr –axxxx,substituting the automatic-processing-scheduler password forxxxx. Press Enter.
The Octel PC/CDR ProcessingSchedule screen (similar toFigure 7-17) is displayed and mustremain displayed for the schedulesto be activated and for the automaticprocessor to work.
3. Automatic processing takes place asscheduled, when the timer reaches000:00:00:00.
During processing, the screenschange. When the processing is com-pleted, the Octel PC/CDR ProcessingSchedule reappears (Figure 7-17).
4. Press Esc if you do not want theschedule to run again at the desig-nated interval.
The DOS prompt reappears.
If this program is to run automatically when power is turned on to the PC, addthe schedcdr –axxxx command as the last line of the PC’s AUTOEXEC.BAT file.Placing this command on the last line of the AUTOEXEC.BAT file ensures thatthe automatic-processing timer will start after a power failure.
SECTION 7.5
PROCESSING METHODS
Octel PC/CDR Edition 2 7-29
7.5.3 UPDATING THE SCHEDULE PASSWORD
If you establish a schedule password using the Update Schedule Passwordoption, that password is required to access the Octel PC/CDR AutomaticSchedule Menu (Figure 7-13) and to execute all schedule functions. Theschedule password is only required if the scheduler is to be executed using aDOS command (section 7.5.2.2). However, you should establish a schedulepassword to ensure that unauthorized users cannot tamper with scheduleprocessing. This password does not have to be the same as the password usedby the server. Establish the schedule password, as follows:
Step Action Result
1. From the Octel PC/CDR AutomaticSchedule Menu (Figure 7-13), selectoption 3, and press Enter.
The following prompt appears:
Enter New Schedule Password:
2. Type a password up to 15 alpha-numeric characters long, and pressEnter. Choose a password that iseasy to remember, but not easy toguess.
The following prompt appears:
Enter New Password Again forVerification:
3. Type the password again, and pressEnter.
The Octel PC/CDR Automatic Sched-ule menu reappears (Figure 7-13).
4. Make note of the new password andsave it in a secure location.
. . .
If you forget the schedule password, it cannot be recovered.To gain access to the scheduling menus, you must deleteall of the schedules and the existing schedule password. Inthis case, all automatic processing schedules would have tobe re-created.
Caution!
If you cannot remember the schedule password, the only way to access theautomatic-scheduling menus again is by first deleting the existing password andall of the schedules. Delete the existing password and all schedules, as follows:
Step Action Result
1. At the DOS prompt, type the follow-ing: schedcdr –r
The following prompt appears:
WARNING: Deleting all schedules& password. Are you sure? (y/n):
2. To delete all schedules and the pass-word, press Y and Enter.
The following prompt appears:
Schedule Password not set Press ENTER/RETURN to continue.
SECTION 7.5
PROCESSING METHODS
7-30 Edition 2 Octel PC/CDR
Step ResultAction
3. Press Enter. The Octel PC/CDR Automatic Sched-ule Menu appears (Figure 7-13).
4. Re-create the schedules (section7.5.1), and establish a new password(section 7.5.3).
. . .
7.5.4 UPDATING AUTOMATIC-SCHEDULER LOG FILES
A log file called SCHEDCDR.LOG is maintained in the OCTELCDR\LOGsubdirectory. This file contains information about automatic-schedule transac-tions. Refer to Appendix F for the most common entries in the automaticschedule log file.
Use the Octel PC/CDR Update Automatic Scheduler Log File menu, shown inFigure 7-18, to review the contents of the SCHEDCDR.LOG file and to performother functions associated with the SCHEDCDR.LOG file
Sections 7.5.4.1 through 7.5.4.5 discuss the schedule log file options.
Octel PC/CDR Update Automatic Scheduler Log File
0 Exit Schedule Editor Menu
1 List Schedule Log File2 Print Schedule Log File3 Backup Schedule Log File4 Restore Schedule Log File5 Erase Schedule Log File
Enter Option:
Figure 7-18. Octel PC/CDR Update AutomaticScheduler Log File Menu.
SECTION 7.5
PROCESSING METHODS
Octel PC/CDR Edition 2 7-31
7.5.4.1 Option 1, List Schedule Log File. Use option 1 to list (view) thecontents of the schedule log file, as follows:
Step Action Result
1. From the Octel PC/CDR AutomaticSchedule Menu (Figure 7-13),select option 4, and press Enter.
The Octel PC/CDR Update AutomaticScheduler Log File menu appears(Figure 7-18).
2. Select option 1, and press Enter. The schedule log file is displayed, onescreen at a time, and the following promptappears:
Press ENTER/RETURN to continue, orESC to abort.
Figure 7-19 is an example of a schedulelog file.
3. Continue to press Enter until allscreens of the schedule log filehave been displayed.
Each time Enter is pressed, a new screenis displayed. After the last screen of theschedule log file appears, the Octel PC/CDR Update Automatic Scheduler Log Filemenu reappears (Figure 7-18).
>> 07-26-96 10:16 SCHEDEDT: Startup.
>> 07-26-96 10:19 SCHEDEDT: Shutdown.
07-26-96 11:00: Begin Processing Schedule # 1 – sch1, System/Program # 1 – westreg
>> 07-26-96 11:05 SCHEDCDR: Shutdown
Press ENTER/RETURN to continue, or ESC to abort.
Figure 7-19. Example of a Schedule Log File.
Type the following command at the DOS prompt on the drive containing theOctel PC/CDR software to view the schedule log file:
type \octelcdr\log\schedcdr.log
To stop the information from scrolling down the screen, press Ctrl–S. Tocontinue scrolling, press Ctrl–Q.
SECTION 7.5
PROCESSING METHODS
7-32 Edition 2 Octel PC/CDR
7.5.4.2 Option 2, Print Schedule Log File. Print the schedule log file usingoption 2, as follows:
Step Action Result
1. From the Octel PC/CDR AutomaticSchedule Menu (Figure 7-13), selectoption 4, and press Enter.
The Octel PC/CDR Update Automat-ic Scheduler Log File menu appears(Figure 7-18).
2. Select option 2, and press Enter. The following prompt appears:
Please make sure your printer isONLINE. Press ENTER/RETURN to continue, or ESC to abort.
3. Verify that the printer is on line. . . .
4. Press Enter to begin printing. The schedule log file is printed.
7.5.4.3 Option 3, Backup Schedule Log File. Use option 3 to back up yourschedule log file in case a PC hard-drive problem occurs or the schedule log fileis inadvertently erased from your hard drive. When the backup is performedusing option 3, Backup Schedule Log File, the contents of theC:\OCTELCDR\LOG subdirectory are erased, and a new schedule log file iscreated. (The C:\OCTELCDR\LOG subdirectory contains the SCHEDCDR.LOGfile and a dated schedule log file, if a previously backed up schedule log file wasrestored.)
If the CDR PC is using IBM DOS or MS-DOS version 6.2 or newer, the OctelPC/CDR backup utilities might not work. If the message Incorrect DOS versionor Error on backup. is displayed while using the Backup Schedule Log Fileprocedure, the DOS file required for this process is either not found on your PCor it is not recognized. If one of these error messages occurs, back up andre-create the schedule log file, as follows:
1. Exit to DOS and manually copy the SCHEDCDR.LOG file from theC:\OCTELCDR\LOG subdirectory to a floppy disk, following the instructionsin your DOS manual.
2. Delete the backed-up SCHEDCDR.LOG file to conserve PC disk storagespace.
3. When required, access the Automatic Scheduler Functions menu, and a newSCHEDCDR.LOG file is created automatically.
SECTION 7.5
PROCESSING METHODS
Octel PC/CDR Edition 2 7-33
If the CDR PC is using IBM DOS or MS-DOS version 3.2 through 5.0 or version6.2 (under some circumstances), back up the schedule log file to a floppy diskusing the Backup Schedule Log File option, as follows:
Step Action Result
1. Have a blank, formatted floppy diskavailable onto which the schedulelog file will be copied. If the sched-ule log file is too large to fit on onefloppy disk, have additional for-matted floppy disks at hand.
. . .
2. From the Octel PC/CDR AutomaticSchedule Menu (Figure 7-13), selectoption 4, and press Enter.
The Octel PC/CDR Update AutomaticScheduler Log File menu appears(Figure 7-18).
3. Select option 3, and press Enter. A prompt, similar to the following, appears:
The automatic Octel PC/CDR logfile C:\OCTELCDR\LOG\S960726.LOG will be backedup. A new log file will then bestarted.
Do you wish to proceed with logfile backup? (y/n):
Although the prompt says it is backingup a dated log file(C:\OCTELCDR\LOG\S960726.LOG),the schedcdr.log file is the actual filethat is backed up.
4. Press Y and Enter to proceed.
The following prompt appears:
Destination Drive for Backup (A: to C:)?:
5. Insert a blank, formatted floppydisk into the disk drive.
. . .
6. Type the letter of the drive contain-ing the floppy disk, and pressEnter.
A prompt similar to the followingappears:
Insert backup diskette 01 indrive A:
WARNING! Files in the targetdrive A:\ root directory will beerased Press any key to continue . . .
If the message Incorrect DOS versionor Error on backup. appears, refer toyour DOS manual and manually backup the schedcdr.log file. (Refer to theintroduction to this section for moreinformation.)
SECTION 7.5
PROCESSING METHODS
7-34 Edition 2 Octel PC/CDR
Step ResultAction
7. Press any key to continue. The backup process begins. If the disk becomes full, additional disks are requested.
Each backup disk is automaticallynumbered during the backup opera-tion. This number shows as the vol-ume name on the disk.
The SCHEDCDR.LOG file is copied tothe disk and given a new name. Thename given this file varies, dependingon the release of DOS you are using.The original SCHEDCDR.LOG file iserased, and a new log file with thesame name is created.
After the schedule is copied to thedisk(s), the Octel PC/CDR Update Automatic Scheduler Log File menureappears (Figure 7-18).
8. Remove the last backup disk, labelit, and store all the disks in a se-cure location.
. . .
7.5.4.4 Option 4, Restore Schedule Log File. If you need to review aschedule log file (SCHEDCDR.LOG) that had previously been backed up usingoption 3, Backup Schedule Log File (Figure 7-18), you must first restore thefile to the hard drive. Use option 4, Restore Schedule Log File from the OctelPC/CDR Update Automatic Scheduler Log File menu to restore the file to theC:\OCTELCDR\LOG subdirectory. The restored file is named using the conven-tion Smmddyy.LOG, where S represents the schedule log file and mmddyyrepresents the month, day, and year the file was originally backed up. Use theDOS type command to view the restored schedule log file.
If the schedule-parameter file was backed up using a DOS command, refer toyour DOS manual for instructions about restoring (or copying) theSCHEDCDR.LOG file to the OCTELCDR\LOG subdirectory.
SECTION 7.5
PROCESSING METHODS
Octel PC/CDR Edition 2 7-35
Restore a schedule log file to the PC hard drive, as follows:
Step Action Result
1. From the Octel PC/CDR AutomaticSchedule Menu (Figure 7-13), selectoption 4, and press Enter.
The Octel PC/CDR Update Automat-ic Scheduler Log File menu appears(Figure 7-18).
2. Select option 4, and press Enter. A prompt similar to the followingappears:
Any archived log files on thebackup disk will be restored to your fixed drive in directoryC:\OCTELCDR\LOG\ using thenaming conventionSmmddyy.LOG. The current logwill NOT be replaced.
Do you wish to proceed withlog file restoration? (y/n):
3. Press Y and Enter to proceed. The following prompt appears:
Source Drive for Restore (A: toC:)?:
4. Insert backup disk 01 into the appropriate drive.
. . .
5. Type the letter of the drive contain-ing the backup disk, and press Enter.
A prompt similar to the following appears:
Insert backup diskette 01 indrive A:Press any key to continue . . .
6. Press any key to restore the file tothe PC hard drive.
A message is displayed briefly on thescreen, showing the date and timethat the files were backed up.
After the schedule log file is restoredto the hard drive, the Octel PC/CDRUpdate Automatic Scheduler Log Filemenu reappears (Figure 7-18).
7. Remove the backup disk and returnit to a secure location.
. . .
SECTION 7.5
PROCESSING METHODS
7-36 Edition 2 Octel PC/CDR
7.5.4.5 Option 5, Erase Schedule Log File. Refer to section 7.5.4.3 to backup the schedule log file before deleting it, as erased files cannot be recovered. Ifyou use option 5, Erase Schedule Log File, a new schedule log file is createdas soon as the old schedule log file is erased.
If the schedule log file is backed up using option 3, Backup Schedule Log File,the schedule log file is automatically erased after it is backed up. If the schedulelog file is backed up using a DOS command, erase the original schedule log fileimmediately after backing up the current log file to conserve PC hard drivestorage space, as follows:
Step Action Result
1. From the Octel PC/CDR AutomaticSchedule Menu (Figure 7-13), selectoption 4, and press Enter.
The Octel PC/CDR Update Automat-ic Scheduler Log File menu appears(Figure 7-18).
2. Select option 5, and press Enter. The following prompt appears:
The automatic Octel PC/CDRlog file will be erased and anew log file will then bestarted. The current log con-tents will NOT be saved.
Do you wish to proceed withlog file erasure? (y/n):
3. Press Y and Enter to erase the logfile.
The log file is deleted, a new sched-ule log file is created, and the OctelPC/CDR Update Automatic Schedul-er Log File menu reappears(Figure 7-18).
7.6 USING THE SERVICE-LEVEL DOWNLOAD
The service-level download is used primarily by Octel or distributor servicerepresentatives for troubleshooting. It creates the same binary collection files(BCFs) as all other forms of processing; however, specific data blocks areselected for downloading.
After performing a service-level download, use the manual processing methoddescribed in sections 7.3.2 and 7.3.3 to process the BCFs.
You can execute the service-level download from the Octel PC/CDR SystemMenu or by typing a special command at the DOS prompt.
SECTION 7.5 – 7.6
PROCESSING METHODS
Octel PC/CDR Edition 2 7-37
7.6.1 USING THE OCTEL PC/CDR SYSTEM MENU
Execute the service-level download through the Octel PC/CDR System Menu, asfollows:
Step Action Result
1. At the DOS prompt, type a valid CDRsystem name, and press Enter.
If the system manager password hasbeen established, the password isrequested.
If the system manager password hasnot been established, a promptrequests that you press Enter tocontinue.
2. If the system manager password hasbeen established, type the password,and press Enter.
If the system manager password hasnot been established, press Enter.
The Octel PC/CDR System Menuappears (similar to the screen shownin Figure 7-4).
3. From the Octel PC/CDR System Menu(Figure 7-4), select option 5 and pressEnter to link with the server for per-forming system manager functions.
. . .
4. Type the system manager password, ifprompted. If you entered the systemmanager password in step 2, it is notrequested here.
Several menus scroll across thescreen, and the SMT Main Menu appears.
5. From the SMT Main Menu, selectoption 16, and press Enter.
Menu 16 – Database Access appears.
6. Select option 1, and press Enter. Menu 16.1, Manage Call DetailRecording, appears.
7. Select option 2, and press Enter. Menu 16.1.2, Retrieve Call DetailRecords, appears, similar to thescreen shown in Figure 7-20.
8. In the Sequence Number of FirstBlock to Retrieve: field, type the firstblock number to retrieve, and pressEnter.
The cursor moves to the Number ofBlocks to Retrieve: field.
The entry must either be the numberof a previously downloaded block orthe first block in a sequence that hasnot already been downloaded. If theentry is not one of these, the downloadwill fail. For example,
If blocks 1726 through 1918 havenot been downloaded, a downloadcannot begin at block 1900. It muststart at block 1726, or it must startwith a previously downloaded block.
SECTION 7.6
PROCESSING METHODS
7-38 Edition 2 Octel PC/CDR
Step ResultAction
9. Type the number of blocks to retrieve,and press Enter.
The following prompt appears:
Begin file transfer... Initiatetransfer on PC now...Press Ctrl–X/Return to cancel...Press any key when transfer iscomplete...
10. Press F3. The cursor moves to the commandline, and the Command? promptappears, as shown in Figure 7-21.
11. At the Command? prompt, type rx [filename].bcf, substituting aunique name of up to eight alphanu-meric characters for [filename]. Although BCF file names normally fol-low the convention Ayymmddi.BCF(defined in Chapter 1), any unique filename can be used during the service-level download.
The BCF created with this downloadwill be given the file name that youdefine here, and it will be stored inthe BCF subdirectory.
12. Press Enter to begin the download. A screen similar to Figure 7-22 ap-pears. This screen displays the flowof data being downloaded from theserver to the PC, by incrementingcounters shown on the screen. Thefields on this screen are described insection 7.2.2.
13. When the entry in the Block # fieldstops incrementing, press Enter.
The following prompt appears:
Retrieval complete. Press any key to continue.
14. Press Esc until the screen is blank. . . .
15. Press F3. The cursor moves to the commandline and the Command? promptreappears.
16. Type by, and press Enter. The Command? prompt remains onthe screen.
17. Type qu, and press Enter. The screen returns to the Octel PC/CDR System Menu (Figure 7-4).
SECTION 7.6
PROCESSING METHODS
Octel PC/CDR Edition 2 7-39
Sequence Number of First Block to Retrieve: 955
Number of Blocks to Retrieve:
Menu 16 – Database AccessRetrieve Call Detail Records
Figure 7-20. SMT Menu 16.1.2, Retrieve CallDetail Records.
Sequence Number of First Block to Retrieve: 955
Number of Blocks to Retrieve: 100
Menu 16 – Database AccessRetrieve Call Detail Records
Command?
Begin file transfer . . . Initiate transfer on PC now . . .Press Ctrl–X/Return to cancel . . . Press any key when transfer is complete . . .
Figure 7-21. SMT Menu 16.1.2, Database Access, RetrieveCall Detail Records, Showing Command Line.
Begin file transfer . . . Initiate transfer on PC now . . .Press Ctrl–X/Return to cancel . . . Press any key when transfer is complete . . .
Receiving C:\WESTREG\BCF\filename.bcf – using CRC
Block # % Complete Consec.errors Total errors
160 –– none none
PROTOCOL TRANSFER UNDERWAY––Press F3 to cancel
Figure 7-22. Octel PC/CDR Block Retrieval Transfer Screen.
SECTION 7.6
PROCESSING METHODS
7-40 Edition 2 Octel PC/CDR
7.6.2 USING DOS
Establish the link with the SMT Main Menu by typing the following command atthe DOS prompt on the CDR PC:
systemname –Lxxxx
where
systemname is the name chosen for the CDR system. (If necessary, firsttype the command cdrhelp at the DOS prompt to list all valid system names,and then make note of the system name to be used.)
–L is the parameter required to execute the communication link between thePC and the server.
xxxx is the system manager password (of any length). If no password or anincorrect password is typed here, the normal prompt for a system managerpassword appears and will require an entry before the download can begin.
Repeat steps 4 through 17 from section 7.6.1 to complete the service-leveldownload.
SECTION 7.6
O C T E L
P C / C D R
UTILITIES
C O N T E N T S
8-iiiEdition 2Octel PC/CDR
CHAPTER 8
8.1 OVERVIEW 8-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.2 DISPLAYING THE STATUS OF THE DISK 8-2. . . . . . . . . . . . . . . . . . . . . . . .
8.3 DISPLAYING OCTEL PC/CDR FILES 8-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4 VIEWING AND PRINTING OCTEL PC/CDR FILES 8-4. . . . . . . . . . . . . . . .
8.4.1 SELECTING AN OUTPUT FILE 8-5. . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.4.2 VIEWING AN OUTPUT FILE OR LOG FILE 8-8. . . . . . . . . . . . . . . .
8.4.3 PRINTING AN OUTPUT FILE OR LOG FILE 8-9. . . . . . . . . . . . . . .
8.5 BACKING UP OCTEL PC/CDR FILES 8-10. . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.5.1 USING DOS VERSION 6.2 OR NEWER 8-10. . . . . . . . . . . . . . . . . . .
8.5.2 USING DOS VERSIONS 3.2 THROUGH 5.0 8-11. . . . . . . . . . . . . .
8.6 ERASING OCTEL PC/CDR FILES 8-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.7 RESTORING OCTEL PC/CDR FILES 8-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.8 USING SERVICE UTILITIES 8-18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.8.1 SEARCHING A COLLATED DAY FILE 8-18. . . . . . . . . . . . . . . . . . . .
8.8.1.1 Using the Octel PC/CDR Service Utilities Menu 8-18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.8.1.2 Using DOS 8-25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.8.2 COPYING A BINARY COLLECTION FILE 8-25. . . . . . . . . . . . . . . . .
8.8.2.1 Using the Octel PC/CDR Service Utilities Menu 8-26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.8.2.2 Using DOS 8-28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.8.3 DISPLAYING A BINARY COLLECTION FILE 8-29. . . . . . . . . . . . . .
8.8.3.1 Using the Octel PC/CDR Service Utilities Menu 8-30. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.8.3.2 Using DOS 8-32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Section Page
C O N T E N T S
8-iv Edition 2 Octel PC/CDR
8.8.4 DISPLAYING A PROCESSED COLLECTION FILE 8-34. . . . . . . . .
8.8.5 DISPLAYING A PENDING-STATE FILE 8-34. . . . . . . . . . . . . . . . . . . .
8.8.5.1 Using the Octel PC/CDR Service Utilities Menu 8-34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.8.5.2 Using DOS 8-35. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.9 USING THE CHKREV UTILITY 8-36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TABLESTable 8-1. Fields in Settings Section of Search Collated Day
File Utility Menu 8-20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 8-2. Descriptions of Fields on the Search Criteria Screen 8-22. . . .
Table 8-3. Search Summary Screen Column Descriptions 8-24. . . . . . . . . .
Table 8-4. Column Descriptions for the DUMPBCF Summary Screen 8-32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Section Page
C O N T E N T S
8-vEdition 2Octel PC/CDR
FIGURES
Figure 8-1. Octel PC/CDR System Menu 8-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 8-2. Octel PC/CDR File Utilities Menu 8-2. . . . . . . . . . . . . . . . . . . . . . . .
Figure 8-3. Example of Octel PC/CDR Disk Status Screen 8-3. . . . . . . . . . .
Figure 8-4. Example of the First Screen of the Display Octel PC/CDR Files Option, Containing BCF Information 8-4. . . . . .
Figure 8-5. Main Menu of the View Octel PC/CDR Output Files Option 8-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 8-6. File Selection Parameters Screen 8-7. . . . . . . . . . . . . . . . . . . . . . . . .
Figure 8-7. File Selection Parameters Screen With File Type Options Displayed 8-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 8-8. Main Menu With Output File Summary Shown in the Status Window 8-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 8-9. Print Selection Parameters Screen 8-10. . . . . . . . . . . . . . . . . . . . . .
Figure 8-10. Octel PC/CDR File Backup Menu 8-14. . . . . . . . . . . . . . . . . . . . . . .
Figure 8-11. Octel PC/CDR File Erase Menu 8-16. . . . . . . . . . . . . . . . . . . . . . . . .
Figure 8-12. Octel PC/CDR Service Utilities Menu 8-18. . . . . . . . . . . . . . . . . . .
Figure 8-13. Search Collated Day File Utility Menu 8-19. . . . . . . . . . . . . . . . . .
Figure 8-14. Example of the Select a Binary Collection File Menu 8-27. . . .
Figure 8-15. Example of the COPYBCF Options Menu 8-28. . . . . . . . . . . . . . .
Figure 8-16. DUMPBCF Options Menu 8-31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 8-17. Example of Report Created Using DUMPBCF 8-31. . . . . . . . . . . .
Figure 8-18. Example of DUMPBCF Summary Screen 8-32. . . . . . . . . . . . . . . .
Figure 8-19. Example of Select a Pending State File Menu 8-35. . . . . . . . . . .
Page
C H A P T E R 8
Octel PC/CDR Edition 2 8-1
UTILITIES
8.1 OVERVIEW
Use the options on the Octel PC/CDR File Utilities Menu to perform thefollowing tasks:
� Display the status of the CDR PC hard drive
� Display a listing of all files in the CDR system subdirectories
� View Octel PC/CDR output files and CDR system log files
� Print Octel PC/CDR output files and CDR system log files
� Back up Octel PC/CDR files from the CDR system subdirectories
� Erase Octel PC/CDR files from the CDR system subdirectories
� Restore Octel PC/CDR files that were backed up using the backup utility
� Search, copy, and display collated day files (CDFs)
� Copy and display binary collection files (BCFs)
� Display pending-state files (PSFs)
Use the CHKREV utility to review the revision levels of the files in theOCTELCDR subdirectories. This utility is accessed from the DOS prompt.
Display the Octel PC/CDR File Utilities Menu, as follows:
Step Action Result
1. At the DOS prompt, type the name ofthe CDR system to be configured (asnamed using the MKCDRSYS com-mand; refer to section 3.4), andpress Enter.
If the system-manager password hasbeen established, the password isrequested.
If the system-manager password hasnot been established, a promptrequests that you press Enter tocontinue.
2. If the system-manager password hasbeen established, type the password,and press Enter.
If the system-manager password hasnot been established, press Enter.
The Octel PC/CDR System Menuappears, similar to the screen shownin Figure 8-1.
3. Select option 4, and press Enter. The Octel PC/CDR File UtilitiesMenu appears, as shown inFigure 8-2.
4. Refer to sections 8.2 through 8.8 fordescriptions of the options on theOctel PC/CDR File Utilities Menu.
. . .
UTILITIES
8-2 Edition 2 Octel PC/CDR
Octel PC/CDR System Menu, REV 2.30 westreg
0 Exit
1 Update Octel PC System Attributes2 Manual Octel PC/CDR Processing3 Automatic Octel PC/CDR Processing4 File Utilities5 Link with VPMOD for Performing System Manager Functions
Enter Option:
Figure 8-1. Octel PC/CDR System Menu.
Octel PC/CDR File Utilities Menu westreg
0 Exit File Utilities Menu
1 Display Disk Status2 Display Octel PC/CDR Files3 View/Print Octel PC/CDR Files4 Backup Octel PC/CDR Files5 Erase Octel PC/CDR Files6 Restore Octel PC/CDR Files7 Service Utilities
Enter Option:
Figure 8-2. Octel PC/CDR File Utilities Menu.
All screens, subdirectories, and data referenced in these utilities apply to theCDR system that you select when you access the Octel PC/CDR System Menu(Figure 8-1).
8.2 DISPLAYING THE STATUS OF THE DISK
Use option 1, Display Disk Status to display the following:
� The total number and size (in kilobytes) of files in the subdirectories for theselected CDR system
� The amount of hard-disk space (in kilobytes) in use for the subdirectories ofthe selected CDR system
� The total amount of hard-disk space (in kilobytes) in use on the CDR PC
� The available hard-disk storage space (in kilobytes and percentage free)remaining on the CDR PC
To display the status of the PC hard drive, select option 1 from the OctelPC/CDR File Utilities Menu (Figure 8-2), and press Enter. The Octel PC/CDRDisk Status screen, similar to Figure 8-3, appears.
SECTION 8.1 – 8.2
UTILITIES
Octel PC/CDR Edition 2 8-3
Octel PC/CDR Disk Status westreg
System westreg Directories
In Use: 45 Files, 3,391 KBytes
Total PC Disk C:
In Use: 71,792 KBytes. Available: 439,672 KBytes (86% free).
Press ENTER/RETURN to continue.
Figure 8-3. Example of Octel PC/CDRDisk Status Screen.
8.3 DISPLAYING OCTEL PC/CDR FILES
Use option 2, Display Octel PC/CDR Files to display the Octel PC/CDR fileslocated in each subdirectory of the selected CDR system. Refer to section 3.3 fora list of subdirectories created for each CDR system.
Step Action Result
1. From the Octel PC/CDR File UtilitiesMenu (Figure 8-2), select option 2,and press Enter.
A screen, similar to the screenshown in Figure 8-4, is displayed.This screen contains the followingdetails about the contents of the BCFsubdirectory:
� The total number of files
� The total number of kilobytesused for the storage of files
� The names of the files
2. Press Enter to display informationabout the contents of the next subdi-rectory.
Each time Enter is pressed, detailsabout a different subdirectory aredisplayed. The subdirectories aredisplayed in the following order:
1. BCF 8. FDO
2. CDF 9. FXO
3. SDO 10. PRO
4. UTO 11. DUO
5. MDO 12. CMO
6. PSO 13. NNO
7. SYS
SECTION 8.2 – 8.3
UTILITIES
8-4 Edition 2 Octel PC/CDR
Step ResultAction
3. Continue to press Enter until allsubdirectories have been displayed.
After the details about the final(NNO) subdirectory are displayed, asummary showing the total numberof files and kilobytes in all of theCDR system subdirectories is dis-played.
4. Press Enter. The Octel PC/CDR File UtilitiesMenu reappears (Figure 8-2).
BCF Directory Files, 5 Files, 767 KBytes
A960809A.PCF A960810A.PCF A960812A.BCF A960809A.PSF
Press ENTER/RETURN to continue, or ESC to abort.
Figure 8-4. Example of the First Screen of theDisplay Octel PC/CDR Files Option,
Containing BCF Information.
Some files listed in the output file subdirectories might not contain data and aretherefore not valid files. Refer to Chapter 9 for additional information.
8.4 VIEWING AND PRINTING OCTEL PC/CDR FILES
Use option 3, View/Print Octel PC/CDR Files to select and view or print outputfiles and CDR system log files.
Before viewing or printing Octel PC/CDR files using this option, make note of thefollowing:
� The exact file name of the output file or CDR system log file must be used toview or print the file. Refer to section 8.3 for one way to display a list ofoutput file names.
� Only those output files created in ASCII format and CDR system log files canbe printed using the View/Print Octel PC/CDR Files option.
� Files created in ASCII format are printed using the column names shown inthe Octel PC/CDR Field Name column in Appendix A.
� Regardless of whether the output files were created in dBASE III or ASCIIformat, all files are viewed using the column names shown in the OctelPC/CDR Field Name column in Appendix A.
� When printing an output file or a CDR system log file, be aware that thenumber of columns printed is limited by the capability of the printer. Someprinters truncate the number of columns displayed and others wrap the textto the next line.
� Using the menus in this option, you can access the CDR system log file, eventhough it is not an output file.
SECTION 8.3 – 8.4
UTILITIES
Octel PC/CDR Edition 2 8-5
Prepare to view or print output files and CDR system log files, and then accessthe Main Menu of the View Octel PC/CDR Output Files option, as follows:
Step Action Result
1. Make note of the exact file name ofthe output file to be printed orviewed.
. . .
2. From the Octel PC/CDR File UtilitiesMenu (Figure 8-2), select option 3,and press Enter.
The Main Menu of the View OctelPC/CDR Output Files optionappears, as shown in Figure 8-5.
View Octel PC/CDR Output Files 0 Exit Menu
1 Select Output File
2 View Output File
3 Print Output File
Enter Option:
Main Menu
Status Window
No file open.
Figure 8-5. Main Menu of the View OctelPC/CDR Output Files Option.
8.4.1 SELECTING AN OUTPUT FILE
You must select an output file before you can view or print it. Select an outputfile for viewing or printing, as follows:
Step Action Result
1. From the Main Menu (Figure 8-5),select option 1, and press Enter.
The File Selection Parameters screenappears, as shown in Figure 8-6,with the cursor on the File Type:field.
2. Press F2 to display the list of outputfiles.
A numbered list of output files,including the log file, is displayed, asshown in Figure 8-7.
3. Use the arrow keys to highlight thenumber corresponding to the re-quired output file or the log file, andpress Enter.
The selected number is copied intothe File Type: field, and the cursormoves to the File Format: field.
SECTION 8.4
UTILITIES
8-6 Edition 2 Octel PC/CDR
Step ResultAction
4. Press F2 to display the list of file for-mats.
A numbered list of file formats is dis-played, as follows:
1 – ASCII Data File2 – dBASE Data File3 – Log Data File
5. Use the arrow keys to select the fileformat in which the file to be se-lected was created, and press Enter.Select 3 if you want to display a logfile.
The selected number is copied intothe File Format: field, and the cur-sor moves to the File Date: field.
6. Type a valid output-file date in theformat shown on the screen. Forexample,
If the SDO file is namedB960726.DBF, type 072696 (theslashes are entered automatically).
The file date is defined.
7. Press F10 to select the requested filefor viewing or printing.
The screen returns to the MainMenu. The Status Window at thebottom of the Main Menu displayssummary information about the se-lected file, as shown in Figure 8-8.This information includes the num-ber of records in the file and the file-format level (displayed in the Level:field) selected when the systemattributes were configured.
If the requested output file is notfound, a tone sounds and the follow-ing message appears in the StatusWindow:
Unable to open that file.Press any key to continue:
8. If the output file is not found, con-firm that the requested file name isvalid (section 8.3 explains how todisplay file names) and that the for-mat in which the requested file wascreated was selected in step 5.
Adjust the entries in the FileFormat: and File Date: fields asnecessary, and return to step 7.
. . .
SECTION 8.4
UTILITIES
Octel PC/CDR Edition 2 8-7
Status Window
File Type : 1File Format : 2File Date : 07/26/96
Esc – Exit F1 – Help F2 – Display Choices F10 – Proceed
No file open.
View Octel PC/CDR Output FilesFile Selection Parameters
Figure 8-6. File Selection Parameters Screen.
View Octel PC/CDR Output FilesFile Selection Parameters
File Type : 1File Format : 2File Date : 02/22/92
Status Window
Esc – Exit F1 – Help F2 – Dis
No file open.
Cursor keys scroll, <ENTER> selects and <ESC> exits choice menu
1 – Billing (SDO)2 – Forms (FDO)3 – Message Detail (MDO)4 – Port Statistics (PSO)5 – Unsuccessful Transfer (UTO)6 – Log File Output7 – Fax (FXO)8 – Profile Change Details (PRO)9 – Disk Usage (DUO)10– Caller Menu (CMO)11– NameNet (NNO)
Figure 8-7. File Selection Parameters ScreenWith File Type Options Displayed.
SECTION 8.4
UTILITIES
8-8 Edition 2 Octel PC/CDR
View Octel PC/CDR Output Files 0 Exit Menu
1 Select Output File
2 View Output File
3 Print Output File
Enter Option:
Main Menu
Status Window
FileDate: 08–09–96. FileType: 1 – Billing (SDO)
FileFormat: 2 – dBASE Data File. 3609 Records in File. Level: 6
Figure 8-8. Main Menu With Output FileSummary Shown in the Status Window.
8.4.2 VIEWING AN OUTPUT FILE OR LOG FILE
View a selected output file, as follows:
Step Action Result
1. Follow the steps in section 8.4.1 toselect an output file.
The Main Menu appears (Figure 8-8),with information about the selectedfile shown in the Status Window.
2. Select option 2, and press Enter. The first screen of the selected output file or log file is displayed on the screen. Refer to Chapter 9and Appendix A for output-file-interpretation information and toChapter 1 for information about logfiles.
3. Press F1. Instructions appear about movingthe cursor around the screen to view columns and rows that are not visible.
4. Press F10 or Esc to return to theMain Menu.
The Main Menu reappears(Figure 8-8).
SECTION 8.4
UTILITIES
Octel PC/CDR Edition 2 8-9
8.4.3 PRINTING AN OUTPUT FILE OR LOG FILE
You can use this option to print only CDR system log files and output filescreated in ASCII format. Print a selected output file or log file, as follows:
Step Action Result
1. Follow the steps in section 8.4.1 toselect an output file.
A screen (similar to Figure 8-8)appears, with information about theselected file showing in the statuswindow.
2. Select option 3, and press Enter. The Print Selection Parametersscreen appears, as shown inFigure 8-9, with the cursor on theFirst Line to Print: field.
3. To modify any of the fields, move thecursor to the field to be changed,type the required number, and pressEnter.
The cursor moves to the next field.
Because the number of columnsprinted is limited by the capability of the printer, enter, in the Last Col-umn to Print: field, only the numberof columns that your printer canprint on a page.
To print all data, print this outputfile several times, entering a differentrange of columns each time in theFirst Column to Print: and LastColumn to Print: fields.
4. When the information displayed inall fields is correct, press F10.
The screen returns to the MainMenu, and the following prompt appears in the status window:
Please make certain that yourprinter is online. Press any key to continue:
5. Verify that the printer is on line, andpress any key to begin printing.
The selected file is printed. Refer toChapter 9 and Appendix A for out-put-file-interpretation informationand Chapter 1 for information aboutCDR system log files.
If the printer is not on line, the fol-lowing prompt appears in the statuswindow:
Printing selected records. PressEsc to abort.Write fault error writing deviceLPT1Abort, Retry, Ignore, Fail?
SECTION 8.4
UTILITIES
8-10 Edition 2 Octel PC/CDR
Step ResultAction
6. If the printer is not on line, type a tostop the print request and return tothe Octel PC/CDR File Utilities Menu(Figure 8-2). Bring the printer online, and return to section 8.4.1 toselect the output file for printingagain.
The selected file is printed.
7. Press Esc to return to the Octel PC/CDR File Utilities Menu.
The Octel PC/CDR File UtilitiesMenu reappears (Figure 8-2).
Status Window
View Octel PC/CDR Output FilesPrint Selection Parameters
First Line to Print : 1Last Line to Print :3609First Column to Print : 1Last Column to Print : 175
Esc – Exit F10 – Proceed
FileDate: 08–09–96. FileType: 1 – Billing (SDO)
FileFormat: 2 – dBASE Data File. 3609 Records in File. Level: 6.
Figure 8-9. Print Selection Parameters Screen.
8.5 BACKING UP OCTEL PC/CDR FILES
You must perform routine file maintenance for efficient CDR processing and toensure that the PC hard drive does not become full. Back up the files in the CDRsubdirectories before erasing them from the hard drive to ensure that they areavailable for troubleshooting and as a precautionary measure in the unlikelyevent that a PC hard-drive problem occurs.
Depending on the version of DOS on your PC, you can either back up your filesusing the Octel PC/CDR backup option or you can back up your files manually,by using the utilities provided with DOS.
8.5.1 USING DOS VERSION 6.2 OR NEWER
If the CDR PC is using IBM DOS or MS-DOS version 6.2 or newer, the OctelPC/CDR backup utilities might not work. Follow the instructions in section8.5.2 to back up Octel PC/CDR files. If the message Incorrect DOS version or Error on backup. is displayed while using the backup utility, the DOS filerequired for this process was either not recognized or not found on your PC. In that case, exit to DOS and manually copy or back up the desired files to adisk or tape, following the instructions in your DOS manual.
SECTION 8.4 – 8.5
UTILITIES
Octel PC/CDR Edition 2 8-11
8.5.2 USING DOS VERSIONS 3.2 THROUGH 5.0
If the CDR PC is using IBM DOS or MS-DOS version 3.2 through 5.0 (or version6.2 under some circumstances), use option 4, Backup Octel PC/CDR Files toback up the files in the following subdirectories:
� BCF
� CDF
� All output file subdirectories except FDO
� SYS (system)
� FDO
You can back up all or none of the files within these directories. Groups of filesin the CDF, output file, and SYS directories can be selected for backup by date.
Back up Octel PC/CDR files to a floppy disk using the Backup Octel PC/CDRFiles option, as follows:
Step Action Result
1. Have several blank, formatted floppydisks available onto which to back upthe files.
. . .
2. From the Octel PC/CDR File UtilitiesMenu (Figure 8-2), select option 4,and press Enter.
The Octel PC/CDR File BackupMenu appears, as shown inFigure 8-10.
3. Back up files in a particular subdirec-tory by typing the number correspond-ing to the required subdirectory(Figure 8-10) and press Enter.
A prompt similar to the following appears:
BCF Directory Files to Backup(All/None)
Depending on the subdirectoryselected for backup, the options toback up files are All/None or All/None/Date.
4. Refer to the following list and type theoption that represents the files to bebacked up. Press Enter.
a - All (back up all files in the directory)
n - None (do not back up any files)
d - Date (back up files by date)
When you type a or n and pressEnter, the corresponding field in theCurrent Setting column changes toAll or None.
When you type d (back up files bydate), the following prompt appears:
All files up to but not includingthe date you enter will beselectedEnter the date (mm–dd–yy):
5. If you typed d, type the date in the for-mat mm–dd–yy, and press Enter. Filesdated before but not including thespecified date are backed up.
The date is entered in the corre-sponding field of the Current Setting column.
SECTION 8.5
UTILITIES
8-12 Edition 2 Octel PC/CDR
Step ResultAction
6. Repeat steps 3, 4, and 5 until all filesto be backed up have been selected.
. . .
7. Place a blank, formatted floppy disk inthe disk drive on the PC. (The tapebackup feature is not supported atthis time.)
. . .
8. From the Octel PC/CDR File BackupMenu, select option 6, and press Enter.
The following prompt appears:
Backup Destination Drive:
9. Enter the letter of the drive containingthe floppy disk to which the files are tobe backed up, and press Enter.
The drive designation is entered inthe corresponding field of the Cur-rent Setting column.
10. To begin the backup procedure, selectoption 7, and press Enter.
The following prompt, containing im-portant information about the back-up process, appears on the screen:
Backup of files will beperformed using the DOSbackup utility. You may beprompted repeatedly to “Insertbackup disk in drive” and“Strike any key when ready.”This is normal. You may simplyleave the current diskette in thedrive and press any key eachtime you are so prompted. It isonly necessary to changediskettes when the number (01,02, 03, etc.) of the requestedbackup diskette changes.During the backup procedure,you must press ESC twice toabort the backup sequence. Thebackup procedure will then beaborted at the first opportunity.
About to begin backup. PressESC to abort or any other key tocontinue.
Instead of the prompts Insertbackup disk in drive and Strikeany key when ready. (as referencedabove), you might see a prompt thatsays the following: Insert lastbackup diskette in drive A: Pressany key to continue . . . Respondto this prompt in the same way byleaving the current disk in the driveand pressing any key.
SECTION 8.5
UTILITIES
Octel PC/CDR Edition 2 8-13
Step ResultAction
11. Read and become familiar with theinstructions displayed on the screenbefore proceeding.
. . .
12. Press any key to continue. A prompt similar to the followingappears:
Insert backup diskette 01 indrive A:
WARNING! Files in the targetdrive A:\ root directory will beerased
Press any key to continue . . .
If the prompt Incorrect DOS versionor Error on backup. appears, referto section 8.5.1.
13. Confirm that a blank, formatted diskis in the disk drive, and press any keyto continue.
The backup process begins, and thefile names appear on the screen asthey are being backed up.
If the following prompt appears, thecurrent disk is full. Go to step 15.
Insert backup diskette 02 indrive A:
WARNING! Files in the target drive A:\ root directory will beerased
Press any key to continue . . .
14. If the following prompt appears,
Insert last backup diskette indrive A:Press any key to continue . . .
Do not replace the disk, just press anykey to continue, according to the in-structions given in the prompt in step10. Continue to press any key as thisprompt is repeated.
When the backup is complete, theOctel PC/CDR File Backup Menureappears (Figure 8-10).
15. If the disk is full (refer to step 13),additional disks are requested. Insertanother blank, formatted disk into thedisk drive, and press any key to con-tinue.
Make sure to insert a blank floppy diskwhen an additional disk is requested,or the current disk will be overwritten.
. . .
SECTION 8.5
UTILITIES
8-14 Edition 2 Octel PC/CDR
Step ResultAction
16. Label each disk in the order in whichit was filled (for example, 01, 02, andso on), so the labels match the volumenames.
. . .
17. Remove the last backup disk and storeall of the backup disks in a secure lo-cation.
. . .
18. Select option 0 and press Enter to re-turn to the Octel PC/CDR File UtilitiesMenu.
The Octel PC/CDR File UtilitiesMenu reappears (Figure 8-2).
Octel PC/CDR File Backup Menu westreg
0 Exit & Return to File Utility Menu Current Setting
1 Backup BCF Directory Files? (All/None) None2 Backup CDF Directory Files? (All/None/Date) None3 Backup Output Directory Files? (All/None/Date) None4 Backup System Directory Files? (All/None/Date) None5 Backup FDO Directory Files? (All/None) None
6 Destination Drive for Backup (A:/B:/Tape) A:
7 Begin Backup
Enter Option (Esc to Abort Changes):
Figure 8-10. Octel PC/CDR File Backup Menu.
8.6 ERASING OCTEL PC/CDR FILES
The PC hard drive holds large amounts of data, but it can be filled quickly,unless you frequently back up and then delete or erase unnecessary or olderfiles. Because erased files usually cannot be recovered, erase Octel PC/CDR filesonly after they have been backed up (section 8.5). Additional methods of erasingOctel PC/CDR files are explained in Chapter 5.
Use option 5, Erase Octel PC/CDR Files to erase files from the followingsubdirectories:
� BCF
� CDF
� All output file subdirectories except FDO
� SYS (system)
� FDO
You can erase all or none of the files within these directories. Groups of files inthe CDF, output file, and SYS directories can be selected for erasure by date.
SECTION 8.5 – 8.6
UTILITIES
Octel PC/CDR Edition 2 8-15
Erase Octel PC/CDR files, as follows:
Step Action Result
1. From the Octel PC/CDR File UtilitiesMenu (Figure 8-2), select option 5,and press Enter.
The Octel PC/CDR File Erase Menuappears, as shown in Figure 8-11. If a subdirectory was previouslybacked up by date (refer to section8.5.2), that date is the default valuefor the corresponding field in thismenu.
2. Erase files in a particular subdirec-tory by typing the number corre-sponding to the required subdirec-tory (Figure 8-11), and press Enter.
A prompt similar to the followingappears:
PCF/PSF Files To Erase (All/None):
Depending on the directory filesselected for erasure, the options for backing up files are All/None or All/None/Date.
3. Refer to the following list and typethe option that represents the files tobe erased. Press Enter.
a - All (erase all files in the directory)
n - None (do not erase any files)
d - Date (erase files by date)
When you type a or n and pressEnter, the corresponding field in theCurrent Setting column changes toAll or None.
When you type d (erase files by date),the following prompt appears:
All files up to but not includingthe date you enter will beselectedEnter the date (mm–dd–yy):
4. If you typed d, type the date in theformat mm–dd–yy, and press Enter.Files dated before but not includingthe specified date will be erased.
The date is entered in the corre-sponding field of the Current Setting column.
5. Repeat steps 2 through 4 until allfiles to be erased have been selected.
. . .
SECTION 8.6
UTILITIES
8-16 Edition 2 Octel PC/CDR
Step ResultAction
6. Confirm that only the files you wanterased have been selected. Select op-tion 6 to erase the selected files, andpress Enter.
If the files selected for erasure werenot previously backed up using theBackup Octel PC/CDR Files option,the following prompt appears:
Are you sure you wish to erasethis file (y/n):
This prompt is repeated for each fileuntil the erasure of all files that werenot previously backed up is con-firmed.
If all files were previously backed upusing the Backup Octel PC/CDRFiles option, the file names appearbriefly on the screen as they areerased. When the erase process iscomplete, the Octel PC/CDR EraseMenu reappears (Figure 8-11).
7. If the Are you sure you wish toerase this file (y/n): promptappears, type y to proceed and erasethe file, or type n to leave the file onthe hard drive. Press Enter.
The file names appear briefly on thescreen as they are erased. When theerase process is complete, the OctelPC/CDR Erase Menu reappears(Figure 8-11).
8. Select option 0 and press Enter toreturn to the Octel PC/CDR File Uti-lities Menu.
The Octel PC/CDR File UtilitiesMenu reappears (Figure 8-2).
Octel PC/CDR File Erase Menu westreg
0 Exit & Return to File Utility Menu Current Setting
1 Erase BCF Directory Files? (All/None) All2 Erase CDF Directory Files? (All/None/Date) All3 Erase Output Directory Files? (All/None/Date) All4 Erase System Directory (Log) Files? (All/None/Date) All5 Erase FDO Directory Files? (All/None) All
6 Begin Erase
Enter Option (Esc to Abort Changes):
Figure 8-11. Octel PC/CDR File Erase Menu.
8.7 RESTORING OCTEL PC/CDR FILES
You can use option 6, Restore Octel PC/CDR Files to restore Octel PC/CDRfiles that were backed up using option 4 on the Octel PC/CDR File UtilitiesMenu (section 8.5) to their original subdirectories from the backup disk.
SECTION 8.6 – 8.7
UTILITIES
Octel PC/CDR Edition 2 8-17
Restore backed up Octel PC/CDR files, as follows:
Step Action Result
1. From the Octel PC/CDR File UtilitiesMenu (Figure 8-2), select option 6,and press Enter.
A prompt similar to the followingappears:
Please insert the first disketteof the backup set in drive A:
Press ENTER/RETURN to contin-ue, or ESC to abort.
2. Insert the backup disk into the des-ignated disk drive, and press Enter.
A prompt similar to the followingappears:
Insert backup diskette 01 indrive A:Press any key to continue . . .
3. Confirm that the floppy disk labeled01 is in the disk drive, and press anykey to continue.
Depending on the version of DOS onthe CDR PC, one of the followingoccurs when you press any key:
� With DOS version 3.3 and newer,the file-restore option displays thebacked-up files found on the diskas they are restored to the harddrive. If the backup requires morethan one disk, the additionaldisks are requested as needed.
When all files are restored, the fol-lowing prompt appears:
Restore complete. PressENTER/RETURN to continue.
� With DOS version 3.2, a num-bered list of the backed-up files isdisplayed on the PC screen.
4. If you are using DOS version 3.2,you must select each file and restoreit individually, as follows:
a. Select the files to restore bytyping the corresponding numberof each required file and pressingEnter.
b. When all files are restored, followthe prompts to return to the OctelPC/CDR File Utilities Menu.
The files are restored to the harddrive as they are selected. The OctelPC/CDR File Utilities Menu reap-pears on the screen (Figure 8-2).
5. If you are using DOS version 3.3 ornewer, press Enter to continue.
The Octel PC/CDR File UtilitiesMenu reappears (Figure 8-2).
SECTION 8.7
UTILITIES
8-18 Edition 2 Octel PC/CDR
8.8 USING SERVICE UTILITIES
Use option 7, Service Utilities primarily for file manipulation. This optionallows you to search, copy, and display the collated day files. It also allows youto copy and display binary collection files and to display pending-state files.
From the Octel PC/CDR File Utilities Menu (Figure 8-2), select option 7 andpress Enter to access the Octel PC/CDR Service Utilities Menu, shown inFigure 8-12. The options on this menu are described in sections 8.8.1 through8.8.5.
Octel PC/CDR Service Utilities Menu
0 Exit Service Utilities Menu
1 Search Collated Day File2 Copy Binary Collection File3 Display Binary Collection File4 Display Pending State File
Enter Option:
Figure 8-12. Octel PC/CDR Service Utilities Menu.
8.8.1 SEARCHING A COLLATED DAY FILE
Use the Search Collated Day File option to look for specific data in the collatedday files (CDFs). With this option, you can direct the contents of a CDF to aprinter, the screen, or to another file. If you do not request specific searchcriteria, all events are displayed. When the search is performed, a list of thesearch criteria used and a summary of the requested data are included at theend of the file. If the file is printed, this information is displayed on the screenand printed at the end of the file. You can also execute DOS commands usingthis option.
Select option 1 to access the Search Collated Day File Utility Menu from theOctel PC/CDR Service Utilities Menu (Figure 8-12 and described in section8.8.1.1), or type a special command at the DOS prompt (described in section8.8.1.2).
8.8.1.1 Using the Octel PC/CDR Service Utilities Menu. Access theSearch Collated Day File Utility Menu from the Octel PC/CDR Service UtilitiesMenu, as follows:
Step Action Result
1. From the Octel PC/CDR File UtilitiesMenu (Figure 8-2), select option 7,and press Enter.
The Octel PC/CDR Service UtilitiesMenu appears (Figure 8-12).
2. From the Octel PC/CDR Service Utilities Menu (Figure 8-12), selectoption 1, and press Enter.
The Search Collated Day File UtilityMenu appears, as shown inFigure 8-13.
SECTION 8.8
UTILITIES
Octel PC/CDR Edition 2 8-19
Search Collated Day File Utility Menu
Q QuitS Start SearchD Issue DOS command
––––––––––––––––––––––––––––––––––––Settings–––––––––––––––––––––––––––––––––––A Octel server System name : WESTREGI Input CDF File :O Output selection : SCREENR Record display : TEXT FORMAT
–––––––––––––––––––––––––––––––Search Criteria––––––––––––––––––––––––––––––––T Times :P Ports :B Mailboxes :E Event Records :M Msg ID Address:
Enter Choice:
Figure 8-13. Search Collated Day File Utility Menu.
Update the entries in the Settings section of the Search Collated Day File UtilityMenu, as follows:
Step Action Result
1. From the Search Collated Day FileUtility Menu (Figure 8-13), selectoption I, and press Enter.
The Select a Collated Day File screenappears, showing a numbered list ofall files found in the CDF subdirec-tory.
2. Type the number corresponding tothe CDF to be searched, and pressEnter.
The Search Collated Day File UtilityMenu automatically reappears, withthe selected CDF name displayed inthe Input CDF File: field.
3. Review the default values in theother three fields in the Settingssection of the screen. Refer toTable 8-1 for descriptions of thesefields.
. . .
4. If a default value needs to bechanged, type the letter correspond-ing to that field in the Enter Choice:field, and press Enter.
Based on the field being changed, amenu appears, and you areprompted to make a selection.
5. Refer to Table 8-1, enter the numberthat corresponds to your selection,and press Enter.
The entry in the corresponding fieldis updated.
6. Repeat steps 3, 4, and 5 until allfields in the Settings section havebeen changed, as necessary.
The entries in the fields are updatedas they are changed.
SECTION 8.8
UTILITIES
8-20 Edition 2 Octel PC/CDR
Table 8-1. Fields in Settings Section ofSearch Collated Day File Utility Menu.
OptionLetter
FieldName
Description
A Octel serverSystem name:
Entering an A displays a numbered list of the CDR sys-tems configured on your PC. This field normally defaultsto the current CDR system name. Select the number corresponding to the name of the CDR system from which the CDF you want to search was created.
I Input CDF File: Entering an I displays a numbered list of up to 50 CDFsstored in the CDF subdirectory for the selected CDR sys-tem. Select the number corresponding to the CDF youwant to search.
O Outputselection:
Entering an O displays options for the output of thesearch results. Choose one of the following:
� F to save the search results in a file
� S to display the results on the PC screen
� P to send the results to a printer
If you select F for outputting to a file, the programprompts you for an output file name. Enter a uniquename, following DOS naming conventions (refer to yourDOS manual for instructions). You can specify a path tothe subdirectory in which the file will be stored as part ofthe file name. If a path is not specified, the output file isplaced in the BCF subdirectory.
R Record display: Entering an R displays options for how the results of thesearch are displayed. Choose one of the following:
� T to display the results as text
� H to display the results in hexadecimal
� B to display the results in both text and hexadecimal
� N to display the search summary screen only
Determine what information you need to obtain from this search, and entersearch criteria to limit the search. Configure the fields in the Search Criteriasection to select only the necessary information. If no search criteria is defined,all data will be displayed according to the entries in the Output selection: andRecord display: fields.
When you request a specific port, mailbox, or event or you request a range ofports, mailboxes, or events, all of the data is displayed for any calls that matchthe search criteria.
SECTION 8.8
UTILITIES
Octel PC/CDR Edition 2 8-21
Configure the fields in the Search Criteria section, as follows:
Step Action Result
1. Refer to the Search Criteria sectionof the Search Collated Day File Util-ity Menu (Figure 8-13). Type theoption letter of the search criterionyou wish to configure, and pressEnter. Refer to Table 8-2 for adescription of the fields in theSearch Criteria section and anyspecial formatting information. Theexamples given in Table 8-2 repre-sent the different types of search cri-teria that can be used. All optionscan be configured in the same wayas the examples given.
Based on the option letter typed, aspecial screen appears. This screendisplays the format of the data to beentered and prompts you for a range.
2. Enter up to three numbers or rangesof numbers using the format shownon the screen and in the examples inTable 8-2, then press Enter.
To clear the entry in a search criteriafield, type the letter of the entry to becleared, and press Enter twice.
The entry in the corresponding fieldin the Search Criteria section isupdated.
3. Repeat steps 1 and 2 until all fieldsin the Search Criteria section havebeen configured, as necessary.
. . .
SECTION 8.8
UTILITIES
8-22 Edition 2 Octel PC/CDR
Table 8-2. Descriptions of Fields on the Search Criteria Screen.
Configure thisfield . . . To search for . . .
Comments
Times: The time a callwas started
Uses 24-hour time. For example,
Enter 1530 to search for calls that started at3:30 p.m.
Ports: The port on whicha call was received
To search for a call received on port 1A, enter1A. To search for calls received on ports 1Athrough 1H and 2A through 2H, enter1A–1H,2A–2H.
Mailboxes: A mailbox numberin any mailbox-related field
All mailbox numbers must have the same number of digits. For example,
To search for calls related to mailbox 7260through 7300, enter 7260–7300.
Event Records: Any event Events are displayed in a numbered list. Enterthe number corresponding to the event needed.For example,
Enter 14,17,18 to search for calls containingthe XFR, MS, and MD events.
Msg IDAddress:
A message ID inany message-ID-related field
Obtain message IDs to use in this field by view-ing a CDF (section 8.8.1) or BCF (section 8.8.3).For example,
View a CDF to identify that the entry in theMsgID2: field of a message to be tracked is327891874. Enter 327891874 to search forall messages related to message ID327891874.
SECTION 8.8
UTILITIES
Octel PC/CDR Edition 2 8-23
Perform the search, using the requested search criteria, as follows:
Step Action Result
1. If printed output is required, ensurethat the printer is on line.
. . .
2. To begin the search, select S fromthe Search Collated Day File UtilityMenu (Figure 8-13), and pressEnter.
The results of the search are pres-ented in the manner requested in theOutput selection: field, as follows:
� If the entry in the Output selec-tion: field is FILE, a file is createdto contain the results of thesearch. This file is given the nameentered in the Output selection:field and is saved to the designatedsubdirectory or to the default CDRsystem subdirectory (BCF).
� If the entry in the Output selec-tion: field is SCREEN, the resultsof the search scroll down thescreen. Press Ctrl–S to pause thescrolling, press Ctrl–Q to resumescrolling, and press Ctrl–C tocancel the search.
� If the entry in the Output selec-tion: field is PRINTER, the resultsof the search are printed.
When the search is completed, asummary of the search criteria usedand the search results appears on thePC screen. The following prompt alsoappears:
Press ENTER/RETURN:
3. Refer to Appendix B for descriptionsof the events and fields displayedusing this utility.
. . .
4. Refer to Table 8-3 for descriptions ofthe columns on the search sum-mary screen.
. . .
5. Press Enter. The Search Collated Day File UtilityMenu reappears (Figure 8-13).
6. Select Q and press Enter to exit. The Octel PC/CDR Service UtilitiesMenu reappears (Figure 8-12).
SECTION 8.8
UTILITIES
8-24 Edition 2 Octel PC/CDR
Table 8-3. Search Summary Screen Column Descriptions.
Column Name Description
CDF Input FileDate
The date of the CDF that was searched
System ID # The ID number of the server from which the data in theCDF was downloaded
Matching Calls The number of calls that matched the search criteria
Total Events The number of events within the calls that matched thesearch criteria
Average EventsPer Call
The average number of events within the calls thatmatched the search criteria
MinimumEvents Per Call
The total number of events within the call that had theleast number of events of all the calls that matched thesearch criteria
MaximumEvents Per Call
The total number of events within the call that had thelargest number of events of all the calls that matchedthe search criteria
If necessary, access the Search Collated Day File Utility Menu (Figure 8-13) anduse option D, Issue DOS command to execute a DOS command without leavingthe Octel PC/CDR application. For example,
To view the contents of a log file using the DOS type command, select optionD, and press Enter. At the Enter DOS command: prompt, type the following:
type c:\westreg\sys\L960725.log
The contents of the log file dated July 25, 1996, for the CDR system namedwestreg are displayed.
When using option D, all DOS commands are executed from the BCF sub-directory for the current CDR system, unless a path is included with thecommand. Refer to your DOS manual for additional information about usingDOS commands.
SECTION 8.8
UTILITIES
Octel PC/CDR Edition 2 8-25
Execute a DOS command from the Search Collated Day File Utility Menu, asfollows:
Step Action Result
1. From Search Collated Day File UtilityMenu (Figure 8-13), select option D,and press Enter.
The following prompt appears:
Enter DOS command:
2. Type a DOS command, and pressEnter.
The DOS command is executed, andits function is performed.
When the DOS function is complete,the Enter DOS command: promptreappears.
3. Press the Esc key to return to theSearch Collated Day File UtilityMenu.
The Search Collated Day File UtilityMenu reappears (Figure 8-13).
8.8.1.2 Using DOS. Access the Search Collated Day File Utility Menu fromthe DOS prompt, as follows:
Step Action Result
1. At the DOS prompt, type cdfs, andpress Enter.
The Search Collated Day File UtilityMenu appears (Figure 8-13).
2. Refer to section 8.8.1.1 for instruc-tions about configuring the fields inthe Settings and Search Criteriasections and performing the search.Configure the fields as necessary,and perform the search.
. . .
3. Select Q and press Enter to exit theSearch Collated Day File UtilityMenu option.
The DOS prompt reappears.
8.8.2 COPYING A BINARY COLLECTION FILE
Use the Copy Binary Collection File option (COPYBCF) to isolate specific blocksin a binary collection file (BCF) and to copy the blocks to a smaller, moremanageable file. If you give the new file the extension of .BCF, you can view it using the DUMPBCF command described in section 8.8.3.2.
To copy a BCF that has already been collated (known as a processed collectionfile or PCF), rename the PCF from Ayymmddi.PCF to [unique file name].BCF,using the DOS rename command, and save it to a different subdirectory, so thatOctel PC/CDR does not attempt to collate it again. Refer to Chapter 1 for BCFand PCF file-naming conventions.
SECTION 8.8
UTILITIES
8-26 Edition 2 Octel PC/CDR
Execute the COPYBCF command from the Copy Binary Collection File option onthe Octel PC/CDR Service Utilities Menu (Figure 8-12) or execute the COPYBCFcommand from the DOS prompt. To copy blocks from a PCF or BCF stored in asubdirectory other than the CDR system BCF subdirectory, refer to section8.8.2.2.
8.8.2.1 Using the Octel PC/CDR Service Utilities Menu. Access the CopyBinary Collection File option from the Octel PC/CDR Service Utilities Menu toexecute the COPYBCF command, as follows:
Step Action Result
1. From the Octel PC/CDR Service Uti-lities Menu (Figure 8-12), select op-tion 2, and press Enter.
If there are uncollated BCFs in theBCF subdirectory for the currentCDR system, the Select a Binary Col-lection File menu appears, similar toFigure 8-14.
If all BCFs have been collated, thefollowing message appears:
No data files to selectPress ENTER/RETURN tocontinue.
2. If BCFs are not found in the CDRsystem subdirectory, refer to Chapter7 and perform a download to createa BCF or rename a PCF (asinstructed in the introduction to sec-tion 8.8.2). Refer to section 8.8.2.2 tocopy files from a BCF located in adifferent subdirectory.
. . .
3. When the Select a Binary CollectionFile menu appears, select the num-ber that corresponds to the requiredBCF, and press Enter.
The COPYBCF Options menuappears, as shown in Figure 8-15.
4. Select option 1, and press Enter. The following prompt appears:
Enter Target File Name:
5. Use the default file name ofCOPYBCF.OUT, or type a unique filename following DOS naming conven-tions. Press Enter.
If you have previously used thedefault file name and try to use itagain, you are prompted that it is anexisting file, and you are returned tothe Octel PC/CDR Service UtilitiesMenu.
The file name appears in the TargetFile field.
6. Select option 2, and press Enter. The following prompt appears:
Enter First Block:
SECTION 8.8
UTILITIES
Octel PC/CDR Edition 2 8-27
Step ResultAction
7. Type the beginning block number,and press Enter. This number mustbe a valid block number from thetarget BCF. If no entry is made, thefirst block copied is the first block inthe target BCF.
Refer to the CDR system log file oruse the Display Binary CollectionFile utility (section 8.8.3) to locatevalid block numbers.
The beginning block number appearsin the First Block to Copy field.
8. Select option 3, and press Enter. The following prompt appears:
Enter Last Block:
9. Type the ending block number, andpress Enter. If no entry is made, allblocks are copied, beginning with theblock number designated in step 7.
The last block number appears inthe Last Block to Copy field.
10. After the target file and the numberof blocks have been specified, type 0and press Enter to execute theCOPYBCF command and create thenew file containing the selectedblocks.
The requested blocks are copied, anda confirming message shows therange of blocks copied. The followingprompt appears:
Press ENTER/RETURN to continue.
11. Press Enter to return to the OctelPC/CDR Service Utilities Menu.
The Octel PC/CDR Service UtilitiesMenu reappears (Figure 8-12).
Select a Binary Collection File
0 Return to Service Utility Menu
1 A960726B 2 A960727A
Enter Option:
Figure 8-14. Example of the Select aBinary Collection File Menu.
SECTION 8.8
UTILITIES
8-28 Edition 2 Octel PC/CDR
COPYBCF Options BCF File: c:\westreg\bcf\A960726A.BCF
0 Run COPYBCF (ESC to Cancel)
1 Target File COPYBCF.OUT2 First Block to Copy3 Last Block to Copy
Enter Option:
Figure 8-15. Example of the COPYBCF Options Menu.
8.8.2.2 Using DOS. Execute the COPYBCF command from the DOS promptusing the following syntax:
copybcf [source.bcf] [target.bcf] [–Fn ] [–Lm]
where
copybcf is the command to execute this utility.
source.bcf is the file name of the BCF to be copied. Enter a valid BCF name,in the format Ayymmddi.BCF. If the DOS prompt is not at the CDR system’sBCF subdirectory, include the path to that subdirectory with the file name.For example, type c:\westreg\bcf\a960802A.bcf as the source file name.
target.bcf is the name of the destination file. Enter a unique file name,following the DOS naming convention, to which blocks from the source.bcfare copied after the copybcf command is executed.
If you want to use the DUMPBCF command to view the file, as described insection 8.8.3.2, use the extension .BCF on the file name, and designate apath to a subdirectory other than the CDR system’s BCF subdirectory aspart of the file name. For example,
Type c:\westreg\temp\copy1.bcf as the target file name to create a filecalled COPY1.BCF, and store it in the C:\WESTREG\TEMP subdirectory.
–Fn is an optional parameter that defines the beginning block number of thesection of interest.
–Lm defines the ending block number of the section of interest.
For example,
The file A960802A.BCF contains blocks numbered from 0 to 100. To copyblocks that are numbered from 1225 to 5450 within this file to a file namedSORT.BCF, type the following command at the C:\WESTREG\BCF> DOSprompt:
copybcf a960802a.bcf sort.bcf –F1225 –L5450
Blocks numbered from 1225 to 5450, from the file A960802A.BCF, arestored in the file named SORT.BCF. These blocks can be processed orviewed.
SECTION 8.8
UTILITIES
Octel PC/CDR Edition 2 8-29
Execute the COPYBCF command from the DOS prompt, as follows:
Step Action Result
1. At the DOS prompt on the drive inwhich the CDR system is located,type cd\, and press Enter.
The prompt shows the root directory(for example, C:\>).
2. Type cd, a space, and the CDR system name, and press Enter.
The prompt now includes the CDRsystem name, for example,C:\WESTREG>.
3. Type cd bcf to move to the BCF subdirectory, and press Enter.
The prompt now shows the CDR system name with the BCF subdirec-tory designation, for example,C:\WESTREG\BCF>.
4. Type the COPYBCF command, usingthe syntax explained above, andpress Enter.
The requested blocks are copied, anda confirming message shows on thescreen. If specific blocks were notdesignated, all blocks within the requested BCF are copied.
5. Press Enter to return to the DOSprompt.
The DOS prompt reappears.
8.8.3 DISPLAYING A BINARY COLLECTION FILE
Use the Display Binary Collection File utility (DUMPBCF) to examine thecontents of a binary collection file (BCF). You can view all BCFs within a CDRsystem’s BCF subdirectory, including BCFs copied as instructed in section 8.8.2and given the extension .BCF. BCFs stored in other subdirectories (refer tosection 8.8.2) and PCFs can be viewed using the DUMPBCF command executedfrom the DOS prompt (refer to section 8.8.3.2).
Execute the DUMPBCF command from the Display Binary Collection File optionon the Octel PC/CDR Service Utilities Menu (Figure 8-12), or execute theDUMPBCF command from the DOS prompt.
SECTION 8.8
UTILITIES
8-30 Edition 2 Octel PC/CDR
8.8.3.1 Using the Octel PC/CDR Service Utilities Menu. Access the
Display Binary Collection File option from the Octel PC/CDR Service Utilities
Menu to execute the DUMPBCF command, as follows:
Step Action Result
1. From the Octel PC/CDR Service Uti-lities Menu (Figure 8-12), select op-tion 3, and press Enter.
If there are uncollated BCFs in theBCF subdirectory for the currentCDR system, the Select a Binary Collection File menu appears(Figure 8-14).
If all BCFs have been collated, thefollowing message appears:
No data files to selectPress ENTER/RETURN tocontinue.
2. If BCFs are not found in the CDRsystem BCF subdirectory, refer toChapter 7 and perform a downloadto create a BCF or rename a PCF (asinstructed in the introduction to sec-tion 8.8.2). Refer to section 8.8.3.2 todisplay files from a BCF located in adifferent subdirectory.
. . .
3. When the Select a Binary CollectionFile menu appears, select the num-ber that corresponds to the requiredBCF, and press Enter.
The DUMPBCF Options menuappears, as shown in Figure 8-16.
4. The default entry in the FullReport? field is No. To obtain afull report, select 1, and press Enter.
The field is changed to Yes.
5. The default entry in the Block Date& Time Summary Report field isNo. To obtain a summary reportshowing each block in the BCF, itssize, and the date and time it wascreated, select option 2, and pressEnter.
To display the BCF for a summaryreport, select Yes for either option 1or option 2.
The field is changed to Yes. If a fullreport was selected in step 4, theentry in the Full Report? fieldchanges to No when the entry in op-tion 2 is changed to Yes.
6. Type 0 and press Enter to executethe DUMPBCF command.
If a full report was requested, pressCtrl–S to pause the scrolling, pressCtrl–Q to resume scrolling, andpress Ctrl–C to cancel the search.
Depending on the option chosen, therequested BCF scrolls down thescreen, or a summary of the BCF isdisplayed. Figure 8-17 is an exampleof a DUMPBCF report.
SECTION 8.8
UTILITIES
Octel PC/CDR Edition 2 8-31
Step ResultAction
7. Refer to Appendix B for descriptionsof the events and fields displayedusing this command.
. . .
8. Refer to Table 8-4 for a description ofthe columns on the DUMPBCF sum-mary screen, similar to the screenshown in Figure 8-18.
When the display is complete, asummary of the BCF contents is dis-played, and the following promptappears:
Press ENTER/RETURN to continue.
9. Press Enter to return to the OctelPC/CDR Service Utilities Menu.
The Octel PC/CDR Service UtilitiesMenu reappears (Figure 8-12).
DUMPBCF Options BCF File: westreg
0 Run DUMPBCF (ESC to Cancel)
1 Full Report? No2 Block Date & Time Summary Report No
Enter Option:
Figure 8-16. DUMPBCF Options Menu.
>> 07-25-96 15:36:31 Listing BCF file: c:\westreg\bcf\A960716A.BCF
Block: 36158, Bytes: 02029
07-16-96 06:24:59 P:05H IC (011) TransID: 1500517
07-16-96 06:24:59 P:05H TNE (024) CallType: 0 Caller: Callee:
07-16-96 06:25:13 P:05H PWT (017) Box: 7492 Result: 0 PWType: 0
07-16-96 06:25:13 P:05H SMS (018) Mode: 2 Box: 7492AppID: 0
07-16-96 06:25:17 P:02B MW (025) Box: 7492 Ext: 7492 Dir: 0 Stat: 0
Figure 8-17. Example of Report Created Using DUMPBCF.
SECTION 8.8
UTILITIES
8-32 Edition 2 Octel PC/CDR
DUMPBCF Options BCF File: westreg
0 Run DUMPBCF (ESC to cancel)
1 Full Report? No 2 Block Date & Time Summary Report Yes
Enter Option: 0
>> 07–20–96 09:03:58 Listing BCF file: d:\westreg\bcf\A960718A.BCF
Date Block Time Size Block Time Size Block Time Size–––––––– ––––– –––––––– –––– ––––– –––––––– –––– ––––– –––––––– ––––07–17–96 36169 02:31:22 2047 36170 11:36:35 2020 36171 15:32:35 203307–17–96 36172 19:41:22 2039 36173 23:03:40 1102
CDR Input File Creation File Size System CDR Total File Name Date & Time Bytes ID # Blocks Events–––––––––––– –––––––– –––––––– ––––––––– –––––––––– ––––––––––– –––––––A961118A.BCF 07–20–96 10:53:00 9344 1006 36169–36173
Press ENTER/RETURN to continue.
Figure 8-18. Example of DUMPBCF Summary Screen.
Table 8-4. Column Descriptions for theDUMPBCF Summary Screen.
Column Name Description
CDR Input FileName
The name of the BCF that was displayed
File Creation
Date
Creation Time
The date the BCF was created
The time the BCF was created
File Size Bytes The size of the BCF, in bytes
System ID # The ID number of the server from which the data inthe BCF was downloaded
CDR Blocks The starting and ending block numbers of theblocks contained in the BCF
Total Events The total number of events contained in the BCF
8.8.3.2 Using DOS. Execute the DUMPBCF command from the DOS prompt,using the following syntax:
dumpbcf [sysname] [filename.ext] [–F|–D] [–L] >[newfile] >[prn]
where
dumpbcf is the command to access this utility.
sysname is the CDR system name, created with the MKCDRSYS utility.
SECTION 8.8
UTILITIES
Octel PC/CDR Edition 2 8-33
filename.ext is the file name and file extension of the BCF or PCF to bedisplayed. If the file is stored in a subdirectory other than BCF, include thepath to that subdirectory as part of the file name. For example,
Type dumpbcf westreg c:\special\tempfile.bcf –F to display a filenamed tempfile.bcf located in the subdirectory called special.
–F is an optional parameter that lists all Octel PC/CDR event records in thefile.
–D is an optional parameter that shows date, time, and block-size informa-tion only.
–L is an optional parameter that specifies a pause before returning to theDOS prompt.
>newfile is an optional parameter that creates a file with the designatedname instead of displaying it on the screen. If the extension .BCF is used onthis file name, include the path to a subdirectory other than the CDR systemBCF subdirectory as part of the filename.
>prn is an optional parameter that sends the file to the printer instead ofdisplaying it on the screen.
For example,
To create a file called MONDAY, which contains all events in the westreg system BCF dated 9/18/96, type the following command at the C:\WESTREG\BCF> prompt:
dumpbcf westreg a960918a.bcf –F >monday
To send all of the events in the BCF dated 9/18/96 directly to the printer,type the following command at the C:\WESTREG\BCF> prompt:
dumpbcf westreg a960918a.bcf –F >prn
Execute the DUMPBCF command from the DOS prompt, as follows:
Step Action Result
1. At the DOS prompt on the drive inwhich the CDR system is located,type cd\, and press Enter.
The prompt shows the root directory(for example, C:\>).
2. Type cd, a space, and the CDR system name, and press Enter.
The prompt now includes the CDRsystem name (for example,C:\WESTREG>).
3. Type cd bcf to move to the BCF subdirectory, and press Enter.
The prompt now shows the CDR system name with the BCF subdirec-tory designation, for example,C:\WESTREG\BCF>.
4. Type the DUMPBCF command, usingthe correct syntax, and press Enter.
Depending on the option chosen, therequested BCF scrolls down thescreen, or a summary of the BCF isdisplayed.
SECTION 8.8
UTILITIES
8-34 Edition 2 Octel PC/CDR
Step ResultAction
5. If the full report was requested,press Ctrl–S to pause the scrolling,press Ctrl–Q to resume scrolling,and press Ctrl–C to cancel thesearch.
When the display is complete, asummary of the BCF contents is dis-played, and the following promptappears:
Press ENTER/RETURN to continue.
6. Refer to Appendix B for descriptionsof the events and fields displayedusing this command.
. . .
7. Refer to Table 8-4 for a description ofthe columns on the DUMPBCF sum-mary screen.
. . .
8. Press Enter to return to the DOSprompt.
The DOS prompt reappears.
8.8.4 DISPLAYING A PROCESSED COLLECTION FILE
Use the DUMPBCF utility to view processed collection files (PCFs). PCFs areproduced if No was selected for the Binary Collection Files Erased AfterCollation? field in the Octel PC/CDR System Attributes menu (refer to section5.3.2). If BCFs are not erased after collation, they are renamed with the exten-sion .PCF.
To view a PCF, follow the instructions in section 8.8.3 to execute the DUMPBCFcommand from the DOS prompt, except type pcf instead of bcf as the file nameextension.
8.8.5 DISPLAYING A PENDING-STATE FILE
Use the Display Pending State File option (DUMPSF) to view the contents of apending-state file (PSF). Pending-state files are defined in section 1.9.4.
Execute the DUMPSF command from the Display Pending State File option onthe Octel PC/CDR Service Utilities Menu (Figure 8-12), or execute the DUMPSFcommand from the DOS prompt.
8.8.5.1 Using the Octel PC/CDR Service Utilities Menu. Access theDisplay Pending State File option from the Octel PC/CDR Service Utilities Menuto execute the DUMPSF command, as follows:
Step Action Result
1. From the Octel PC/CDR Service Utilities Menu (Figure 8-12), selectoption 4, and press Enter.
The Select a Pending State File menuappears, similar to the screen shownin Figure 8-19.
2. Select the number that correspondsto the desired PSF, and press Enter.
The requested PSF scrolls down thescreen.
SECTION 8.8
UTILITIES
Octel PC/CDR Edition 2 8-35
Step ResultAction
3. Press Ctrl–S to pause the scrolling,press Ctrl–Q to resume scrolling,and press Ctrl–C to cancel thesearch.
When the display is complete, thefollowing prompt appears:
Press ENTER/RETURN to continue.
4. Press Enter to return to the OctelPC/CDR Service Utilities Menu.
The Octel PC/CDR Service UtilitiesMenu reappears (Figure 8-12).
Select a Pending State File
0 Return to Service Utility Menu
1 COLLATE 3 A960918B
2 COMPRSP 4 A960919A
Enter Option:
Figure 8-19. Example of Select aPending State File Menu.
8.8.5.2 Using DOS. Execute the DUMPSF command from the DOS prompt,using the following syntax:
dumpsf [sysname] [filename.ext] >[newfile] >[prn]
where
dumpsf is the command to access this utility.
sysname is the CDR system name created with the MKCDRSYS utility.
filename.ext is the file name and file extension of the PSF to be listed. If the DOS prompt is not at the CDR system subdirectory that contains thePSF, include the path to that subdirectory along with the file name. Forexample,
To view the COLLATE.PSF file for the westreg system, type the followingat the DOS prompt:
dumpsf westreg c:\westreg\sys\collate.psf
>newfile is an optional parameter that creates a file with the designatedname, instead of displaying it on the screen.
>prn is an optional parameter that sends the file to the printer instead of thescreen.
For example,
To create a file called TEMP, which contains all events in the westregCOMPRSP.PSF file, type the following command at the C:\WESTREG\BCF>prompt:
dumpsf westreg comprsp.psf>temp
SECTION 8.8
UTILITIES
8-36 Edition 2 Octel PC/CDR
To send the contents of the COMPRSP.PSF file directly to the printer, typethe following command at the C:\WESTREG\BCF> prompt:
dump westreg comprsp.psf>prn
Execute the DUMPSF command from the DOS prompt, as follows:
Step Action Result
1. At the DOS prompt on the drive inwhich the CDR system is located,type cd\, and press Enter.
The prompt shows the root directory(for example, C:\>).
2. Type cd, a space, and the CDR system name, and press Enter.
The prompt now includes the CDRsystem name, for example,C:\WESTREG>.
3. Choose one of the following:
� If you want to display theCOMPRSP.PSF file or a dated PSF,type cd bcf to move to the BCFsubdirectory, and press Enter.
� If you want to display theCOLLATE.PSF file, type cd sys,and press Enter.
The prompt now shows the CDR system name with the selected sub-directory designation, for example,C:\WESTREG\BCF> or C:\WESTREG\SYS>.
4. Type the DUMPSF command, usingthe correct syntax, and press Enter.
The requested PSF scrolls down thescreen.
5. If the full report was requested,
� Press Ctrl–S to pause the scrol-ling
� Press Ctrl–Q to resume scrolling
� Press Ctrl–C to cancel the search
The following prompt appears:
Press ENTER/RETURN to continue.
6. Press Enter to return to the DOSprompt.
The DOS prompt reappears.
8.9 USING THE CHKREV UTILITY
Use the CHKREV utility to display the release number of the installed OctelPC/CDR software package and to show the revision date for all of the files withthe extension .EXE located in the OCTELCDR subdirectory.
Service representatives use this utility for troubleshooting. You can also use thisutility to display the size, revision date, and status of all files in the MIR and CCsubdirectories and the size, revision date, and status of all files except the fileswith the extension .EXE in the OCTELCDR subdirectory. On the screen display,a status of OK means that the file was found. No entry in the last column meansthat the file is missing.
To use the CHKREV utility, type chkrev at the DOS prompt from any subdirectory.
SECTION 8.8 – 8.9
O C T E L
P C / C D R
OUTPUT FILE DESCRIPTIONS
C O N T E N T S
9-iiiEdition 2Octel PC/CDR
CHAPTER 9
9.1 OVERVIEW 9-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.2 CALLER-MENU OUTPUT (CMO) FILES 9-2. . . . . . . . . . . . . . . . . . . . . . . . . . .
9.2.1 CMO FILE DESCRIPTION 9-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.2.2 CMO FILE-PROCESSING SUMMARY SCREEN 9-3. . . . . . . . . . . . .
9.3 DISK-USAGE OUTPUT (DUO) FILES 9-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.3.1 DUO FILE DESCRIPTION 9-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.3.2 DUO FILE-PROCESSING SUMMARY SCREEN 9-5. . . . . . . . . . . . .
9.4 FAX OUTPUT (FXO) FILES 9-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.4.1 FXO FILE DESCRIPTION 9-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.4.2 FXO FILE-PROCESSING SUMMARY SCREEN 9-7. . . . . . . . . . . . .
9.5 FORMS OUTPUT (FDO) FILES 9-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.5.1 FDO FILE DESCRIPTION 9-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.5.2 FDO FILE-PROCESSING SUMMARY SCREEN 9-9. . . . . . . . . . . . .
9.6 INDIVIDUAL-PORT-STATISTICS OUTPUT (PSO) FILES 9-10. . . . . . . . . . .
9.6.1 PSO FILE DESCRIPTION 9-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.6.2 PSO FILE-PROCESSING SUMMARY SCREEN 9-13. . . . . . . . . . . .
9.7 MESSAGE-DETAIL OUTPUT (MDO) FILES 9-14. . . . . . . . . . . . . . . . . . . . . . .
9.7.1 MDO FILE DESCRIPTION 9-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.7.2 MDO FILE-PROCESSING SUMMARY SCREEN 9-16. . . . . . . . . . . .
9.8 NAMENET OUTPUT (NNO) FILES 9-17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.8.1 NNO FILE DESCRIPTION 9-17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.8.2 NNO FILE-PROCESSING SUMMARY SCREEN 9-18. . . . . . . . . . . .
Section Page
C O N T E N T S
9-iv Edition 2 Octel PC/CDR
9.9 PROFILE-CHANGE-DETAILS OUTPUT (PRO) FILES 9-19. . . . . . . . . . . . . .
9.9.1 PRO FILE DESCRIPTION 9-19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.9.2 PRO FILE-PROCESSING SUMMARY SCREEN 9-20. . . . . . . . . . . .
9.10 SESSION-DETAIL OUTPUT (SDO) FILES 9-21. . . . . . . . . . . . . . . . . . . . . . . . .
9.10.1 SDO FILE DESCRIPTION 9-21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.10.2 SDO FILE-PROCESSING SUMMARY SCREEN 9-22. . . . . . . . . . . .
9.11 UNSUCCESSFUL-TRANSFER OUTPUT (UTO) FILES 9-24. . . . . . . . . . . . .
9.11.1 UTO FILE DESCRIPTION 9-24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.11.2 UTO FILE-PROCESSING SUMMARY SCREEN 9-25. . . . . . . . . . . .
Section Page
C O N T E N T S
9-vEdition 2Octel PC/CDR
TABLESTable 9-1. CMO File-Processing Summary Screen
Column Descriptions 9-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 9-2. DUO File-Processing Summary Screen Column Descriptions 9-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 9-3. FXO File-Processing Summary Screen Column Descriptions 9-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 9-4. FDO File-Processing Summary Screen Column Descriptions 9-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 9-5. PSO File-Format Level References 9-11. . . . . . . . . . . . . . . . . . . . . . .
Table 9-6. PSO File-Processing Summary Screen Column Descriptions 9-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 9-7. MDO File-Format-Level References 9-15. . . . . . . . . . . . . . . . . . . . . .
Table 9-8. MDO File-Processing Summary Screen Column Descriptions 9-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 9-9. NNO File-Processing Summary Screen Column Descriptions 9-18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 9-10. PRO File-Processing Summary Screen Column Descriptions 9-20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 9-11. SDO File-Format-Level References 9-21. . . . . . . . . . . . . . . . . . . . . .
Table 9-12. SDO File-Processing Summary Screen Column Descriptions 9-23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 9-13. UTO File-Processing Summary Screen Column Descriptions 9-25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Page
C O N T E N T S
9-vi Edition 2 Octel PC/CDR
FIGURESFigure 9-1. Example of a CMO File 9-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 9-2. CMO File-Processing Summary Screen, After Files Are Generated 9-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 9-3. Example of a DUO File 9-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 9-4. DUO File-Processing Summary Screen, After Files Are Generated 9-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 9-5. Example of an FXO File, Showing the First 11 Fields 9-7. . . .
Figure 9-6. FXO File-Processing Summary Screen, After Files Are Generated 9-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 9-7. Example of an FDO File 9-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 9-8. FDO File-Processing Summary Screen, After Files Are Generated 9-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 9-9. Example of a PSO File, Showing the First 17 Fields 9-12. . . .
Figure 9-10. PSO File-Processing Summary Screen, After Files Are Generated 9-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 9-11. Example of an MDO File, Showing the First 10 Fields 9-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 9-12. MDO File-Processing Summary Screen, After Files Are Generated 9-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 9-13. Example of an NNO File, Showing the First 11 Fields 9-17. . .
Figure 9-14. NNO File-Processing Summary Screen, After Files Are Generated 9-18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 9-15. Example of a PRO File 9-19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 9-16. PRO File-Processing Summary Screen, After Files Are Generated 9-20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 9-17. Example of an SDO File, Showing the First Eight Fields 9-22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 9-18. SDO File-Processing Summary Screen, After Files Are Generated 9-22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 9-19. Example of a UTO File 9-24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 9-20. UTO File-Processing Summary Screen, After Files Are Generated 9-25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Page
C H A P T E R 9
Octel PC/CDR Edition 2 9-1
OUTPUT FILE DESCRIPTIONS
9.1 OVERVIEW
CDR events in collated day files (CDFs) are processed (compressed) into outputfiles based on the output files selected for generation by the system manager andthe records collected in the CDR buffer on the server.
You can generate the following output files:
� Caller-menu output (CMO) file
� Disk-usage output (DUO) file
� Fax output (FXO) file
� Forms output (FDO) file
� Individual-port-statistics output (PSO) file
� Message-detail output (MDO) file
� NameNet output (NNO) file
� Profile-change-details output (PRO) file
� Session-detail output (SDO) file
� Unsuccessful-transfer output (UTO) file
Generate only the output files containing information that you need, so that PCdisk-storage space is not filled unnecessarily. Not all output files are needed forevery application.
You can create output files in a dBASE III format or as ASCII files, and then usethese files for specific purposes. For example, create session-detail and individual-port-statistics output files in a dBASE III format and then import them into adatabase for use with a billing application program or use the output files forreport generation.
View and print output files using the View/Print Octel PC/CDR Files option fromthe Octel PC/CDR File Utilities Menu. When an output file is viewed or printedusing this option, it displays the same field names, regardless of whether theoutput file was created in a dBASE III or ASCII format.
Establish a schedule to back up and delete output files periodically to conservePC disk storage space. File management is the responsibility of the systemmanager.
The screens that are displayed when output files are generated often provideuseful information. These screens are also recorded in the CDR system log filefor future reference. Descriptions of the columns displayed on the output-file-processing summary screens that are specific to each output file are found inthis chapter. Refer to Chapter 7 for general information about the fields on thesescreens.
OUTPUT FILE DESCRIPTIONS
9-2 Edition 2 Octel PC/CDR
For additional information about output files, refer to the following:
To find out how to . . . Refer to . . .
Back up an output file Chapter 8
Erase an output file automatically Chapter 5
Erase an output file manually Chapter 8
Generate an output file automatically Chapter 5
Generate an output file manually Chapter 7
Print an output file Chapter 8
Select records for collection Chapter 2
Select the format of the output file (ASCII or dBASE III) Chapter 5
View an output file Chapter 8
For a description of . . . Refer to . . .
Output-file field names and field lengths Appendix A
Output-file structure Appendix A
Output-file-processing summary screen fields Chapter 7
Output-file-processing summary screen columns Chapter 9
Each output file (general description) Chapter 9
9.2 CALLER-MENU OUTPUT (CMO) FILES
The caller-menu output (CMO) file contains information about caller activity inEnhanced Call Processing (ECP) menus (also called single-digit menus or callersmenus). Use the CMO file to track application use, to identify modificationsneeded by the application (based on frequency of menu choice), and to measurecaller acceptance of the ECP process.
9.2.1 CMO FILE DESCRIPTION
The Octel PC/CDR software names the CMO files with the following convention:
Cyymmdd.xxx
where
C represents a caller-menu output file.
yymmdd represents the year (yy), month (mm), and day (dd) the file wascreated, based on the internal server clock.
xxx represents the format of the file. DBF indicates the dBASE III format;ASC indicates various ASCII formats.
SECTION 9.1 – 9.2
OUTPUT FILE DESCRIPTIONS
Octel PC/CDR Edition 2 9-3
Figure 9-1 is an example of a printed CMO file. The capability of the printerlimits the number of columns printed. Some printers truncate the number ofcolumns displayed, and others wrap the data to the next line.
SyID Prt Date Time TransID AppID SourceBox DestNum DT AP
1234 01C 960726 153718 267842 0 9999 99 111234 01D 960726 153747 298734 0 9978 9929 0 31234 01C 960726 153747 329764 0 9929 9937 0 11234 01D 960726 153748 439873 0 9937 1931 0 2
Figure 9-1. Example of a CMO File.
Refer to Appendix A for the file structure and description of all CMO file fields.
Each time CMO files are generated, a new CMO file is created or, if a file alreadyexists for a given date, the new data is appended to the existing file. CMO filesare stored in the CMO subdirectory.
One CMO file with data is created for each day in which caller-menu events arefound in the source CDF. When there are no caller-menu events for a given datein the CDF, a CMO file with no data is created.
� If the CMO file is created in the dBASE III format, it contains only the fieldnames.
� If the CMO file is created in the ASCII format, it is an empty file.
If you use a database or applications program to process this data, the programmust use the correct field names and field lengths. Refer to Appendix A forfield-name and field-length requirements.
9.2.2 CMO FILE-PROCESSING SUMMARY SCREEN
After CMO files are successfully generated, an output-file-processing summaryscreen, similar to Figure 9-2, appears.
Begin Caller Menu ProcessingFound 2 New or Updated Collated Day File(s):
CD960726 CD960727Do you wish to proceed making Caller Menu files? (y/n): Y
>> 07–28–96 10:34:39 > Creating Caller Menu Output Files>> System: westreg, File Format: 1, Level: 6
CDF Input System Total RecordsFile Date ID # Calls Created
07–26–96 1249 3462 7507–27–96 1249 3655 285
Waiting to return to menu.Press ENTER/RETURN to continue.
Figure 9-2. CMO File-Processing Summary Screen,After Files Are Generated.
SECTION 9.2
OUTPUT FILE DESCRIPTIONS
9-4 Edition 2 Octel PC/CDR
Table 9-1 describes the columns on the CMO file-processing screen (Figure 9-2).Output-file-processing summary screens are also recorded in the log file as theoutput file is generated. Refer to section 8.4 for information about viewing andprinting log files. Refer to section 7.3.3 for information about the fields commonto all output-file-processing summary screens.
Table 9-1. CMO File-Processing Summary Screen Column Descriptions.
Column Description
CDF Input FileDate
The date of the CDF. Several CDFs can be produced from a singleBCF, depending on how often data is downloaded from the server.
System ID # The serial number of the server from which the CDF was taken.These serial numbers are important if data from multiple servers isprocessed by the same CDR PC.
Total Calls The total number of calls contained in the CDF.
Records Created The total number of records created in the CMO file.
9.3 DISK-USAGE OUTPUT (DUO) FILES
The disk-usage output (DUO) file monitors disk-storage usage. Use the DUO filefor resource planning by tracking message- and phrase-disk usage and freespace availability at 15-minute intervals.
9.3.1 DUO FILE DESCRIPTION
The Octel PC/CDR software names the DUO files with the following convention:
Dyymmdd.xxx
where
D represents a disk-usage output file.
yymmdd represents the year (yy), month (mm), and day (dd) the file wascreated, based on the internal server clock.
xxx represents the format of the file. DBF indicates the dBASE III format;ASC indicates various ASCII formats.
Figure 9-3 is an example of a printed DUO file. The number of columns printedis limited by the capability of the printer. Some printers truncate the number ofcolumns displayed, and others wrap the data to the next line.
SECTION 9.2 – 9.3
OUTPUT FILE DESCRIPTIONS
Octel PC/CDR Edition 2 9-5
SyID Date Time UMsgH UMsgA UMsgL UPhrH UPhrA UPhrL FMsgH FMsgA FMsgL FPhrH FPhrA FPhrL
0555 960625 154632 25573 25565 25552 190 190 190 14966 14952 14944 1856 1856 18560555 960625 160132 25552 25547 25546 190 190 190 14971 14971 14966 1856 1856 18560555 960625 161632 25548 25542 25534 190 190 190 14984 14975 14970 1856 1856 18560555 960625 163132 25548 25547 25541 190 190 190 14977 14971 14969 1856 1856 18560555 960625 164633 25550 25548 25548 190 190 190 14969 14969 14968 1856 1856 1856
Figure 9-3. Example of a DUO File.
Refer to Appendix A for the file structure and description of all DUO file fields.
Each time DUO files are generated, a new DUO file is created or, if a file alreadyexists for a given date, the new data is appended to the existing file. DUO filesare stored in the DUO subdirectory.
One DUO file with data is created for each day in which disk-usage events arefound in the source CDF. When there are no disk-usage events for a given datein the CDF, a DUO file with no data is created.
� If the DUO file is created in the dBASE III format, it contains only the fieldnames.
� If the DUO file is created in the ASCII format, it is an empty file.
If you use a database or applications program to process this data, the programmust use the correct field names and field lengths. Refer to Appendix A forfield-name and field-length requirements.
9.3.2 DUO FILE-PROCESSING SUMMARY SCREEN
After DUO files are successfully generated, an output-file-processing summaryscreen, similar to Figure 9-4, appears.
Begin Disk Usage ProcessingFound 2 New or Updated Collated Day File(s):
CD960527 CD960528Do you wish to proceed making Disk Usage files? (y/n): Y
>> 05–30–96 10:40:45 > Creating Disk Usage Output Files>> System: westreg, File Format: 1, Level: 6
CDF Input System Total RecordsFile Date ID # Calls Created
05–27–96 1289 3462 3005–28–96 1289 1122 12
Waiting to return to menu.Press ENTER/RETURN to continue.
Figure 9-4. DUO File-Processing Summary Screen,After Files Are Generated.
SECTION 9.3
OUTPUT FILE DESCRIPTIONS
9-6 Edition 2 Octel PC/CDR
Table 9-2 describes the columns on the DUO file-processing screen (Figure 9-4).Output-file-processing summary screens are also recorded in the log file as theoutput file is generated. Refer to section 8.4 for information about viewing andprinting log files. Refer to section 7.3.3 for information about the fields commonto all output-file-processing summary screens.
Table 9-2. DUO File-Processing Summary Screen Column Descriptions.
Column Description
CDF Input FileDate
The date of the CDF. Several CDFs can be produced from a singleBCF, depending on how often data is downloaded from the server.
System ID # The serial number of the server from which the CDF was taken.These serial numbers are important if data from multiple servers isprocessed by the same CDR PC.
Total Calls The total number of calls contained in the CDF.
Records Created The total number of records created in the DUO file.
9.4 FAX OUTPUT (FXO) FILES
Customers with Octel’s optional fax-related products can use the fax output(FXO) file to generate data detailing fax product use. Although you can findgeneral fax-messaging-activity details in the MDO and SDO files, the FXO filecontains events specific to fax-transmission activity.
9.4.1 FXO FILE DESCRIPTION
The Octel PC/CDR software names the FXO files with the following convention:
Fyymmdd.xxx
where
F represents a fax output file.
yymmdd represents the year (yy), month (mm), and day (dd) the file wascreated, based on the internal server clock.
xxx represents the format of the file. DBF indicates the dBASE III format;ASC indicates various ASCII formats.
Figure 9-5 is an example of a printed FXO file showing the first 11 fields. Thenumber of columns printed is limited by the capability of the printer. Someprinters truncate the number of columns displayed, and others wrap the data to the next line.
SECTION 9.3 – 9.4
OUTPUT FILE DESCRIPTIONS
Octel PC/CDR Edition 2 9-7
SyID Prt Date Time TransID AppID Mailbox AC FxP FxSec FaxDestination
1237 02E 960726 090559 266689 0 7624 2 2 401237 03H 960726 090836 267186 0 0 0 01237 04D 960726 091444 267287 0 7624 2 2 501237 04G 960726 121332 0 0 1284 20 2 30 94375911237 06D 960726 121449 267292 0 7469 2 2 30
Figure 9-5. Example of an FXO File,Showing the First 11 Fields.
Refer to Appendix A for the file structure and description of all FXO file fields.
Each time FXO files are generated, a new FXO file is created or, if a file alreadyexists for a given date, the new data is appended to the existing file. FXO filesare stored in the FXO subdirectory.
One FXO file with data is created for each day in which fax events events arefound in the source CDF. When there are no fax events for a given date in theCDF, a FXO file with no data is created.
� If the FXO file is created in the dBASE III format, it contains only the fieldnames.
� If the FXO file is created in the ASCII format, it is an empty file.
If you use a database or applications program to process this data, the programmust use the correct field names and field lengths. Refer to Appendix A forfield-name and field-length requirements.
9.4.2 FXO FILE-PROCESSING SUMMARY SCREEN
After FXO files are successfully generated, an output-file-processing summaryscreen, similar to Figure 9-6, appears.
Begin FAX ProcessingFound 2 New or Updated Collated Day File(s):
CD960609 CD960610Do you wish to proceed making FAX files? (y/n): Y
>> 06–15–96 10:34:39 > Creating Fax Output Files>> System: westreg, File Format: 1, Level: 6
CDF Input System Total RecordsFile Date ID # Calls Created
06-09–96 1210 8498 8206–10–96 1210 8658 17
Waiting to return to menu.Press ENTER/RETURN to continue.
Figure 9-6. FXO File-Processing Summary Screen,After Files Are Generated.
SECTION 9.4
OUTPUT FILE DESCRIPTIONS
9-8 Edition 2 Octel PC/CDR
Table 9-3 describes the columns on the FXO file-processing screen (Figure 9-6).Output-file-processing summary screens are also recorded in the log file as theoutput file is generated. Refer to section 8.4 for information about viewing andprinting log files. Refer to section 7.3.3 for information about the fields commonto all output-file-processing summary screens.
Table 9-3. FXO File-Processing Summary Screen Column Descriptions.
Column Description
CDF Input FileDate
The date of the CDF. Several CDFs can be produced from a singleBCF, depending on how often data is downloaded from the server.
System ID # The serial number of the server from which the CDF was taken.These serial numbers are important if data from multiple servers isprocessed by the same CDR PC.
Total Calls The total number of calls contained in the CDF.
Records Created The total number of records created in the FXO file.
9.5 FORMS OUTPUT (FDO) FILES
Servers with the optional DTMF OctelForms application package collect formsdata in their CDR buffers. The forms output (FDO) file contains DTMF data thatis related to calls to DTMF OctelForms mailboxes. This file includes records ofquestion numbers and callers’ responses. Chapter 10 explains the relationshipbetween the Octel PC/CDR software package and DTMF OctelForms.
9.5.1 FDO FILE DESCRIPTION
The FDO file is not named by date, as are the BCFs and CDFs. The FDO file isnamed FORMS.DBF for a dBASE III format file or FORMS.ASC for an ASCIIformat file. If a file named FORMS.xxx (with xxx representing .DBF or .ASC)already exists when the FDO file is generated, the FORMS.xxx file is appended;otherwise, it is created. The FDO file is stored in the FDO subdirectory. The FDOsubdirectory can have only one FORMS.xxx file at a time.
SECTION 9.4 – 9.5
OUTPUT FILE DESCRIPTIONS
Octel PC/CDR Edition 2 9-9
Because the FDO file increases considerably in size as it is continuallyappended, periodically archive the existing FORMS.xxx and start a newFORMS.xxx file. Conserve PC disk storage space and provide backup forms data in the event of a PC disk problem, as follows:
Step Action
1. To archive the existing FORMS.xxx file, copy it or back it up onto a floppydisk, using the Backup Octel PC/CDR Files option (refer to section 8.5) orDOS (refer to your DOS manual).
2. Rename or erase the FORMS.xxx file from the FDO subdirectory. Use DOS orthe Erase Octel PC/CDR Files option (refer to section 8.6) to erase the file, oruse DOS (refer to your DOS manual) to rename the file.
3. Generate a new FDO file to create a new FORMS.xxx file.
Figure 9-7 is an example of a printed FDO file. The number of columns printedis limited by the capability of the printer. Some printers truncate the number ofcolumns displayed, and others wrap the data to the next line.
Prt Date Time Seq Mailbox Ques Answer
01A 960609 125400 1 3500 0 636501A 960609 125401 1 3500 10 9453901A 960609 125404 1 3500 20 51001A 960609 130542 1 3500 0 671701A 960609 130542 1 3500 10 9512701A 960609 130542 1 3500 20 408
Figure 9-7. Example of an FDO File.
Refer to Appendix A for the file structure and description of all FDO file fields.
If you use a database or applications program to process this data, the programmust use the correct field names and field lengths. Refer to Appendix A forfield-name and field-length requirements.
9.5.2 FDO FILE-PROCESSING SUMMARY SCREEN
After the FDO file is successfully appended, an output-file-processing summaryscreen, similar to Figure 9-8, appears.
SECTION 9.5
OUTPUT FILE DESCRIPTIONS
9-10 Edition 2 Octel PC/CDR
Begin Forms File ProcessingFound 1 New or Updated Collated Day File(s):
CD960712Do you wish to proceed appending to Forms File? (y/n): Y
>>07–13–96 10:56:29 Writing to Forms Master Database>>System: westreg, File Format: 1, Level: 6
CDF Input System TotalFile Date ID # Calls
07–12–96 8720 3539
Waiting to return to menu.Press ENTER/RETURN to continue.
FormsCalls
498
Figure 9-8. FDO File-Processing Summary Screen,After Files Are Generated.
Table 9-4 describes the columns on the FDO file-processing screen (Figure 9-8).Output-file-processing summary screens are also recorded in the log file as theoutput file is generated. Refer to section 8.4 for information about viewing andprinting log files. Refer to section 7.3.3 for information about the fields commonto all output-file-processing summary screens.
Table 9-4. FDO File-Processing Summary Screen Column Descriptions.
Column Description
CDF Input FileDate
The date of the CDF. Several CDFs can be produced from a singleBCF, depending on how often data is downloaded from the server.
System ID # The serial number of the server from which the CDF was taken.These serial numbers are important if data from multiple servers isprocessed by the same CDR PC.
Total Calls The total number of calls contained in the CDF.
Forms Calls The number of DTMF OctelForms calls processed in the CDF.
9.6 INDIVIDUAL-PORT-STATISTICS OUTPUT (PSO) FILES
Individual-Port-Statistics Output (PSO) files contain the total time each port is inuse during every 15-minute period throughout the day and the number of callsstarted within each 15-minute period.
9.6.1 PSO FILE DESCRIPTION
If you use a database or applications program to process this data, the programmust use the correct field names and field lengths. Refer to Appendix A forfield-name and field-length requirements.
SECTION 9.5 – 9.6
OUTPUT FILE DESCRIPTIONS
Octel PC/CDR Edition 2 9-11
The Octel PC/CDR software names the PSO files with the following convention:
Pyymmdd.xxx or PByymmdd.xxx
where
P represents a PSO file. PSO files contain statistics about specific ports,based on the server type, as follows:
� Branch, Branch XP, Aspen, Maxum, or Maxum SE. Ports 1A through18D.
� Octel Overture 250. When the PSO file is created in the dBASE IIIformat, it contains data for ports 1A through 14H. A second PSO file,beginning with PB, contains data for ports 15A through 28H. AlthoughOctel PC/CDR creates the PB file for the Octel Overture 250, the portnumbers are invalid and the file contains no data.
When the PSO file is created in the ASCII format, only one file is created.This output file contains data for all ports (1A through 28H). Because theOctel Overture 250 supports only ports 1A through 9H, disregard thefields for ports greater than 9H that might be displayed in a output file.
� Octel Overture 350 or Octel XC1000. When the PSO file is created inthe dBASE III format, it contains data for ports 1A through 6L. A secondPSO file, beginning with PB, contains data for ports 7A through 12L.
When the PSO file is created in the ASCII format, only one file is created.This output file contains data for all ports (1A through 12L).
PB represents a PSO file when the PSO file is created in the dBASE III formatfor the Octel Overture 250, Octel Overture 350, or Octel XC1000. This filecontains statistics about specific ports based on the server type, as follows:
� Octel Overture 250. Although Octel PC/CDR creates this file for ports15A through 28H on the Octel Overture 250, these port numbers areinvalid and the file contains no data.
� Octel Overture 350 or Octel XC1000. Ports 7A through 12L.
yymmdd represents year (yy), month (mm), and day (dd) that the eventsoccurred, based on the internal server clock.
xxx represents the format of the file. DBF indicates the dBASE III format;ASC indicates various ASCII formats.
Several file-format levels are available for PSO files. Refer to Table 9-5 todetermine where to find additional file-format-level information.
Table 9-5. PSO File-Format Level References.
To find . . . Refer to . . .
Which fields are affected by the different file-format levels Appendix A
Which software releases are affected by the different file-format levels Table 5-2
How to select the file-format level Section 5.3.9
SECTION 9.6
OUTPUT FILE DESCRIPTIONS
9-12 Edition 2 Octel PC/CDR
If you access the Octel PC/CDR System Menu by typing CDR and attempt toview a PSO file containing data downloaded from an Octel Overture 250, OctelOverture 350, or Octel XC1000, unreadable data might appear on the screen. Ifunreadable data is displayed, exit to the DOS prompt and access the OctelPC/CDR software again by typing the name of the CDR system. This conditionoccurs because of a shortage of PC memory. If unreadable data is still displayedafter accessing the software by typing the system name, refer to your DOSmanual for information about increasing conventional memory.
Figure 9-9 is an example of a printed PSO file showing the first 17 fields. Thenumber of columns printed is limited by the capability of the printer. Someprinters truncate the number of columns displayed, and others wrap the data to the next line.
T SyId Date HH MM 01A 01B 01C 01D 01E 01F 01G 01H 02A 02B 02C 02DN 2420 960726 00 00 1 1 1 1 0 0 0 0 0 0 0 0T 2420 960726 00 00 2 0 0 1 0 0 0 0 0 0 0 0N 2420 960726 00 15 0 0 0 0 0 0 0 0 0 0 0 0T 2420 960726 00 15 0 0 0 0 0 0 0 0 0 0 0 0N 2420 960726 00 30 2 0 0 0 0 0 0 0 0 0 0 0T 2420 960726 00 30 4 0 0 0 0 0 0 0 0 0 0 0
Figure 9-9. Example of a PSO File, Showing the First 17 Fields.
Refer to Appendix A for the file structure and description of all PSO file fields.
Each time PSO files are generated, a new PSO file is created or, if a file alreadyexists for a given date, the new data is appended to the existing file. PSO files arestored in the PSO subdirectory.
One PSO file with data is created for each day in which calls are found in thesource CDF. When there are no port-statistics events for a given date in theCDF, a PSO file with no data is created.
� If the PSO file is created in the dBASE III format, it contains only the fieldnames.
� If the PSO file is created in the ASCII format, it is an empty file.
SECTION 9.6
OUTPUT FILE DESCRIPTIONS
Octel PC/CDR Edition 2 9-13
9.6.2 PSO FILE-PROCESSING SUMMARY SCREEN
After PSO files are successfully generated, an output-file-processing summaryscreen, similar to Figure 9-10, appears.
Begin Port Statistics ProcessingFound 2 New or Updated Collated Day File(s): CD960727 CD960729 CD960730Do you wish to proceed making Port Statistics? (y/n): Y
>>07–31–96 02:52:14 Creating Individual Port Statistic Output Files>>File Format: 1, Level: 6
CDF Input System TotalFile Date ID # Calls
07–27–96 7267 2658
Waiting to return to menu.Press ENTER/RETURN to continue.
Sys. Events
25
CallsPassed
263307–29–96 7267 104 2 102
Ignored
Warning: For Date Above, No Previous Day File Available.07–30–96 7267 2224 17 2207
Figure 9-10. PSO File-Processing SummaryScreen, After Files Are Generated.
If the message Warning: For Date Above, No Previous Day File Available.appears while generating PSO files, it means that there might be a missing CDF,that there was no CDR data generated on the day preceding the last date enteredbefore the warning, or that there are corrupted blocks of data in the CDF. Forexample,
On July 29, a PSO file is generated. The message Warning: For Date Above,No Previous Day File Available. appears, because there is no CDF dated07-28-96. Because July 28 was a Sunday, it is possible no CDR data wasgenerated that day. If the skipped date was a normal working day, contactyour local Octel or distributor support office for assistance.
Table 9-6 describes the columns on the PSO file-processing screen (Figure 9-10).Output-file-processing summary screens are also recorded in the log file as theoutput file is generated. Refer to section 8.4 for information about viewing andprinting log files. Refer to section 7.3.3 for information about the fields commonto all output-file-processing summary screens.
SECTION 9.6
OUTPUT FILE DESCRIPTIONS
9-14 Edition 2 Octel PC/CDR
Table 9-6. PSO File-Processing Summary Screen Column Descriptions.
Column Description
CDF Input FileDate
The date of the CDF. Several CDFs can be produced from a singleBCF, depending on how often data is downloaded from the server.
System ID # The serial number of the server from which the CDF was taken. Theseserial numbers are important if data from multiple servers is pro-cessed by the same CDR PC.
Total Calls The total number of calls contained in the CDF.
Sys. EventsIgnored
Number of event records that are not included in the Calls Passedcolumn. This number includes system-manager-event records thathave been recorded, but are not included when calculating other portstatistics.
Calls Passed The number of calls processed from the CDF and placed in the PSOfile.
9.7 MESSAGE-DETAIL OUTPUT (MDO) FILES
Message detail output (MDO) files contain records of every message that hasbeen sent from or deleted from a mailbox. It also includes network message-transmission or message-receipt records.
The following rules apply to networked messages:
� AMIS and Administered AMIS messages are logged in an MDO file when theAMIS or Administered AMIS messages are transmitted from the server orwhen they are returned to the sender.
� OctelNet messages are logged in an MDO file when OctelNet messages arerecorded, transmitted, or returned to the sender.
� AMIS, Administered AMIS, and OctelNet messages received by the server arenot logged in an MDO file.
9.7.1 MDO FILE DESCRIPTION
The Octel PC/CDR software names the MDO files with the following convention:
Myymmdd.xxx
where
M represents a message-detail output file.
yymmdd represents the year (yy), month (mm), and day (dd) that the eventsoccurred, based on the internal server clock.
xxx represents the format of the file. DBF indicates the dBASE III format;ASC indicates various ASCII formats.
Several file-format levels are available for MDO files. Refer to Table 9-7 todetermine where to find additional file-format-level information.
SECTION 9.6 – 9.7
OUTPUT FILE DESCRIPTIONS
Octel PC/CDR Edition 2 9-15
Table 9-7. MDO File-Format-Level References.
To find . . . Refer to . . .
Which fields are affected by the different file-format levels Appendix A
Which software releases are affected by the different file-format levels Table 5-2
How to select the file-format level Section 5.3.9
Figure 9-11 is an example of a printed MDO file showing the first 10 fields. Thenumber of columns printed is limited by the capability of the printer. Someprinters truncate the number of columns displayed, and others wrap the data tothe next line.
SyId Prt Date Time Mailbox Len AT SR Atr OtherNode
0627 05D 960716 001233 7435 65 50 50 0 60627 12A 960716 002859 7435 91 50 50 0 60627 02A 960716 051934 7697 12 10 40 00627 05C 960716 053820 7492 10 0 1 00627 09D 960716 053817 7452 150 0 1 00627 09D 960716 054108 7452 154 11 31 0 1
Figure 9-11. Example of an MDO File,Showing the First 10 Fields.
Refer to Appendix A for the file structure and description of all MDO file fields.
Each time MDO files are generated, a new MDO file is created or, if a file alreadyexists for a given date, the new data is appended to the existing file. MDO filesare stored in the MDO subdirectory.
One MDO file with data is created for each day in which message-detail eventsare found in the source CDF. When there are no message-detail events for agiven date in the CDF, a MDO file with no data is created.
� If the MDO file is created in the dBASE III format, it contains only the fieldnames.
� If the MDO file is created in the ASCII format, it is an empty file.
If you use a database or applications program to process this data, the programmust use the correct field names and field lengths. Refer to Appendix A forfield-name and field-length requirements.
SECTION 9.7
OUTPUT FILE DESCRIPTIONS
9-16 Edition 2 Octel PC/CDR
9.7.2 MDO FILE-PROCESSING SUMMARY SCREEN
After MDO files are successfully generated, an output-file-processing summaryscreen, similar to Figure 9-12, appears.
Begin Message Detail ProcessingFound 1 New or Updated Collated Day File(s):
CD960725 CD960726Do you wish to proceed making Message Detail files? (y/n): Y
>>07–27–96 12:14:36 Creating Message Detail Output Files>>System: westreg, File Format: 1. Level: 6
CDF Input System Total RecordsFile Date ID # Calls Created
07-25-96 0222 498 1935
Waiting to return to menu.Press ENTER/RETURN to continue.
MessagesSent & Deleted
911 1024
MessagesReturned
007-26-96 0222 8658 44548 23487 21059 2
Figure 9-12. MDO File-Processing Summary Screen,After Files Are Generated.
Table 9-8 describes the columns on the MDO file-processing screen (Figure 9-12).Output-file-processing summary screens are also recorded in the log file as theoutput file is generated. Refer to section 8.4 for information about viewing andprinting log files. Refer to section 7.3.3 for information about the fields commonto all output-file-processing summary screens.
Table 9-8. MDO File-Processing Summary Screen Column Descriptions.
Column Description
CDF Input FileDate
The date of the CDF. Several CDFs can be produced from a singleBCF, depending on how often data is downloaded from the server.
System ID # The serial number of the server from which the CDF was taken.These serial numbers are important if data from multiple serversis processed by the same CDR PC.
Total Calls The total number of calls contained in the CDF.
Records Created The total number of records created in the MDO, including mes-sages sent, messages deleted, and messages returned to sender.
Messages Sent The number of messages sent or transmitted from this node. These events are described in Appendix B.
Messages Deleted The number of message-delete events (MD) found in the CDF. This event is described in Appendix B.
Messages Returned The number of networked messages that were returned to the originating mailbox. Messages might be returned because the destination server or mailbox was full.
SECTION 9.7
OUTPUT FILE DESCRIPTIONS
Octel PC/CDR Edition 2 9-17
9.8 NAMENET OUTPUT (NNO) FILES
NameNet output (NNO) files provide information about directory and alarmactivity for the optional NameNet feature.
9.8.1 NNO FILE DESCRIPTION
The Octel PC/CDR software names the NNO files with the following convention:
Nyymmdd.xxx
where
N represents a NameNet output file.
yymmdd represents the year (yy), month (mm), and day (dd) the file wascreated, based on the internal server clock.
xxx represents the format of the file. DBF indicates the dBASE III format;ASC indicates various ASCII formats.
Figure 9-13 is an example of a printed NNO file showing the first 11 fields. Thenumber of columns printed is limited by the capability of the printer. Someprinters truncate the number of columns displayed, and others wrap the data tothe next line.
SyID Prt Date Time TransID AppID Act Node SerialNo Mailbox Alias
1239 03A 960726 035650 1490972 0 71 1 555 74961239 04B 960726 041533 1490973 0 71 40 927 74351239 05D 960726 043201 1490974 0 71 11 8974 75651239 02F 960726 045755 1490978 0 71 2 373 75011239 01B 960726 052800 1490981 0 71 20 5476 7453
Figure 9-13. Example of an NNO File,Showing the First 11 Fields.
Refer to Appendix A for the file structure and description of all NNO file fields.
Each time NNO files are generated, a new NNO file is created or, if a file alreadyexists for a given date, the new data is appended to the existing file. NNO filesare stored in the NNO subdirectory.
One NNO file with data is created for each day in which NameNet events arefound in the source CDF. When there are no NameNet events for a given date inthe CDF, an NNO file with no data is created.
� If the NNO file is created in the dBASE III format, it contains only the fieldnames.
� If the NNO file is created in the ASCII format, it is an empty file.
If you use a database or applications program to process this data, the programmust use the correct field names and field lengths. Refer to Appendix A forfield-name and field-length requirements.
SECTION 9.8
OUTPUT FILE DESCRIPTIONS
9-18 Edition 2 Octel PC/CDR
9.8.2 NNO FILE-PROCESSING SUMMARY SCREEN
After NNO files are successfully generated, an output-file-processing summaryscreen, similar to Figure 9-14, appears.
Begin NameNet Processing Found 2 New or Updated Collated Day File(s):
CD960620 CD960621 Do you wish to proceed making NameNet files? (y/n): Y
>> 06–22–96 08:13:53 > Creating NameNet Output Files >> System: westreg, File Format: 1, Level: 6
CDF Input System Total Records File Date ID # Calls Created
06–20–96 0918 8498 82 06–21–96 0918 8658 17
Waiting to return to menu. Press ENTER/RETURN to continue.
Figure 9-14. NNO File-Processing Summary Screen,After Files Are Generated.
Table 9-9 describes the columns on the NNO file-processing screen (Figure 9-14).Output-file-processing summary screens are also recorded in the log file as theoutput file is generated. Refer to section 8.4 for information about viewing andprinting log files. Refer to section 7.3.3 for information about the fields commonto all output-file-processing summary screens.
Table 9-9. NNO File-Processing Summary Screen Column Descriptions.
Column Description
CDF Input FileDate
The date of the CDF. Several CDFs can be produced from a singleBCF, depending on how often data is downloaded from the server.
System ID # The serial number of the server from which the CDF was taken.These serial numbers are important if data from multiple servers isprocessed by the same CDR PC.
Total Calls The total number of calls contained in the CDF.
Records Created The total number of records created in the NNO.
SECTION 9.8
OUTPUT FILE DESCRIPTIONS
Octel PC/CDR Edition 2 9-19
9.9 PROFILE-CHANGE-DETAILS OUTPUT (PRO) FILES
Profile-change-details output (PRO) files include information about systemprofiles that were added, deleted, and modified. It also includes informationabout when mailboxes were initialized.
9.9.1 PRO FILE DESCRIPTION
The Octel PC/CDR software names the PRO files with the following convention:
Ryymmdd.xxx
where
R represents a profile-change-details output file.
yymmdd represents the year (yy), month (mm), and day (dd) the file wascreated, based on the internal server clock.
xxx represents the format of the file. DBF indicates the dBASE III format;ASC indicates various ASCII formats.
Figure 9-15 is an example of a printed PRO file. The number of columns printedis limited by the capability of the printer. Some printers truncate the number ofcolumns displayed, and others wrap the data to the next line.
SyID Prt Date Time Profile PT AC AT WH ListNum PW PL
0627 01A 960626 154932 6660 21 10 99 4 12 99 00627 01C 960626 154839 6905 0 2 6 4 99 00627 08G 960626 155211 3355 21 10 99 4 11 99 0
Figure 9-15. Example of a PRO File.
Refer to Appendix A for the file structure and description of all PRO file fields.
Each time PRO files are generated, a new PRO file is created or, if a file alreadyexists for a given date, the new data is appended to the existing file. PRO filesare stored in the PRO subdirectory.
One PRO file with data is created for each day in which profile-change events arefound in the source CDF. When there are no profile-change events for a givendate in the CDF, a PRO file with no data is created.
� If the PRO file is created in the dBASE III format, it contains only the fieldnames.
� If the PRO file is created in the ASCII format, it is an empty file.
If you use a database or applications program to process this data, the programmust use the correct field names and field lengths. Refer to Appendix A forfield-name and field-length requirements.
SECTION 9.9
OUTPUT FILE DESCRIPTIONS
9-20 Edition 2 Octel PC/CDR
9.9.2 PRO FILE-PROCESSING SUMMARY SCREEN
After PRO files are successfully generated, an output-file-processing summaryscreen, similar to Figure 9-16, appears.
Begin Profile Change ProcessingFound 2 New or Updated Collated Day File(s):
CD960725 CD960726Do you wish to proceed making Profile Change files? (y/n): Y
>> 07–27–96 02:22:42 > Creating Profile Change Output Files>> System: westreg, File Format: 1, Level: 6
CDF Input System Total Records UserRec Profile ListFile Date ID # Calls Created Changed Changed Changed
07–25–96 0302 498 4 2 1 107–26–96 0302 8658 26 9 0 17
Waiting to return to menu.Press ENTER/RETURN to continue.
Figure 9-16. PRO File-Processing SummaryScreen, After Files Are Generated.
Table 9-10 describes the columns on the PRO file-processing screen (Figure 9-16).Output-file-processing summary screens are also recorded in the log file as theoutput file is generated. Refer to section 8.4 for information about viewing andprinting log files. Refer to section 7.3.3 for information about the fields common to all output-file-processing summary screens.
Table 9-10. PRO File-Processing Summary Screen Column Descriptions.
Column Description
CDF Input FileDate
The date of the CDF. Several CDFs can be produced from a singleBCF, depending on how often data is downloaded from the server.
System ID # The serial number of the server from which the CDF was taken.These serial numbers are important if data from multiple servers isprocessed by the same CDR PC.
Total Calls The total number of calls contained in the CDF.
Records Created The total number of records created in the PRO.
UserRec Changed The number of user records that were added, deleted, or modified.
Profile Changed The number of profiles (node, community, and so on) that were added, deleted, or modified.
List Changed The number of distribution lists (system, personal, or informationservice) that were added, deleted, or modified.
SECTION 9.9
OUTPUT FILE DESCRIPTIONS
Octel PC/CDR Edition 2 9-21
9.10 SESSION-DETAIL OUTPUT (SDO) FILES
Session-detail output (SDO) files contain records of each time a mailbox isaccessed, either in voice-messaging or telephone-answering mode. These recordsalso indicate when callers are logged into the server but are not in a mailbox andprovide information related to outcall events. An outcall session begins when theserver generates an outcall to a subscriber’s telephone. The SDO file includesthe amount of time spent in the outcall session.
SDO files also include details of pager and network outcalls. Pager outcalls are identified separately from other subscriber outcalls and contain the pager-sequence numbers used. Separate network-outcall records are provided forevery outgoing or incoming message, the associated copies, and messages sentto or received from mailboxes on other nodes across the network.
9.10.1 SDO FILE DESCRIPTION
The Octel PC/CDR software names the SDO files with the following convention:
Byymmdd.xxx
where
B represents a session-detail output file.
yymmdd represents year (yy), month (mm), and day (dd) the file was created,based on the internal server clock.
xxx represents the format of the file. DBF indicates the dBASE III format;ASC indicates various ASCII formats.
Several file-format levels are available for SDO files. Refer to Table 9-11 todetermine where to find additional file-format-level information.
Table 9-11. SDO File-Format-Level References.
To find . . . Refer to . . .
Which fields are affected by the different file-format levels Appendix A
Which software releases are affected by the different file-format levels Table 5-2
How to select the file-format level Section 5.3.9
Figure 9-17 is an example of a printed SDO file, showing the first eight fields. The number of columns printed is limited by the capability of the printer. Someprinters truncate the number of columns displayed, and others wrap the data tothe next line.
SECTION 9.10
OUTPUT FILE DESCRIPTIONS
9-22 Edition 2 Octel PC/CDR
SyId Prt Date Time Dur Mailbox Caller Callee0727 03A 960718 001109 17 7435 121445085350727 06H 960718 002709 88 7435 121445085350727 05E 960718 014837 13 7612 31450727 02B 960718 021837 7 7453 31300727 02B 960718 022617 62 7549 31300727 02A 960718 043640 14 7617
Figure 9-17. Example of an SDO File,Showing the First Eight Fields.
Refer to Appendix A for the file structure and description of all SDO file fields.
Each time SDO files are generated, a new SDO file is created or, if a file alreadyexists for a given date, the new data is appended to the existing file. SDO filesare stored in the SDO subdirectory.
One SDO file with data is created for each day in which session-related eventsare found in the source CDF. When there are no session-related events for agiven date in the CDF, a SDO file with no data is created.
� If the SDO file is created in the dBASE III format, it contains only the fieldnames.
� If the SDO file is created in the ASCII format, it is an empty file.
If you use a database or applications program to process this data, the programmust use the correct field names and field lengths. Refer to Appendix A forfield-name and field-length requirements.
9.10.2 SDO FILE-PROCESSING SUMMARY SCREEN
After SDO files are successfully generated, an output-file-processing summaryscreen, similar to Figure 9-18, appears.
Begin Session Detail ProcessingFound 2 New or Updated Collated Day File(s):
CD960727 CD960728Do you wish to proceed making Session Detail files? (y/n): Y
>>07–29–96 11:16:52 Creating Session Detail Output Files>>System: westreg, File Format: 1, Level: 6
CDF Input System CallsTotal Calls & SessionsCallsFile Date ID # IgnoredCalls PassedFailed
07–27–96 0310 3537 0
Waiting to return to menu.Press ENTER/RETURN to continue.
Other
1256
MessagesSent & Deleted
2281 2672 1497 1405
UnsucXfers
007–28–96 0310 4175 0 1598 2577 3080 2060 1712 1
Figure 9-18. SDO File-Processing Summary Screen,After Files Are Generated.
SECTION 9.10
OUTPUT FILE DESCRIPTIONS
Octel PC/CDR Edition 2 9-23
Table 9-12 describes the columns on the SDO file-processing screen(Figure 9-18). Output-file-processing summary screens are also recorded in thelog file as the output file is generated. Refer to section 8.4 for information aboutviewing and printing log files. Refer to section 7.3.3 for information about thefields common to all output-file-processing summary screens.
Table 9-12. SDO File-Processing Summary Screen Column Descriptions.
Column Description
CDF Input FileDate
The date of the CDF. Several CDFs can be produced from a singleBCF, depending on how often data is downloaded from the server.
System ID # The serial number of the server from which the CDF was taken.These serial numbers are important if data from multiple servers isprocessed by the same CDR PC.
Total Calls The total number of calls contained in the CDF.
Calls Failed Entries in this column should always show zero.
Other CallsIgnored
Usually shows the number of single-event calls, such as message-waiting calls, that do not contain any length of time. Calls in the SDOcommonly are used for billing; single-event calls are system-relatedand are not normally used for billing. For in-band integrations, theserver goes off-hook, sends the message-waiting indicator to the PBX,then goes on-hook. The numbers in this column can be high,because they can occur up to three times per message-waiting signal.RS-232 integrations use another method to send message-waitingsignals; that method is not reported here.
Calls Passed The number of calls processed from the CDF and placed in the output file.
Sessions Passed The number of sessions processed from the CDF and placed in theoutput file.
Messages Sent The total number of message-send events (MS) and AMIS message-send events (AMIS_SEND). These events are described in Appendix B.
Messages Deleted
Shows the total number of message-delete (MD) events. This event isdescribed in Appendix B.
Unsuc Xfers The number of attempts made to transfer from a mailbox to anothertelephone number. Unsuccessful transfers occur occasionally whencallers use an ECP mailbox or automated attendant.
SECTION 9.10
OUTPUT FILE DESCRIPTIONS
9-24 Edition 2 Octel PC/CDR
9.11 UNSUCCESSFUL-TRANSFER OUTPUT (UTO) FILES
Unsuccessful-transfer output (UTO) files contain records of each attempted andmonitored transfer, from an automated attendant or ECP mailbox, that is notcompleted for one of the following reasons:
� Busy extension
� Not answered (ring no answer)
� Fast busy
� Extension not in service
� Transfer answered by server
9.11.1 UTO FILE DESCRIPTION
The Octel PC/CDR software names the UTO files with the following convention:
Xyymmdd.xxx
where
X represents an unsuccessful-transfer output file.
yymmdd represents the year (yy), month (mm), and day (dd) that the eventsoccurred, based on the internal server clock.
xxx represents the format of the file, with DBF indicating the dBASE IIIformat and ASC indicating various ASCII formats.
Figure 9-19 is an example of a printed UTO file. The number of columns printedis limited by the capability of the printer. Some printers truncate the number ofcolumns displayed, and others wrap the data to the next line.
SyId Prt Date Time Mailbox RC TnTried
5081 01A 960718 201640 6717 4 6365
5081 01D 960718 220015 6948 2 6391
5081 02C 960719 010533 6996 5 2523
5081 01A 960719 011456 6365 3 2557
5081 02A 960719 031323 6259 4 6365
Figure 9-19. Example of a UTO File.
Refer to Appendix A for the file structure and description of all UTO file fields.
Each time UTO files are generated, a new UTO file is created or, if a file alreadyexists for a given date, the new data is appended to the existing file. UTO filesare stored in the UTO subdirectory.
SECTION 9.11
OUTPUT FILE DESCRIPTIONS
Octel PC/CDR Edition 2 9-25
One UTO file with data is created for each day in which unsuccessful transfersevents are found in the source CDF. When there are no unsuccessful-transferevents for a given date in the CDF, a UTO file with no data is created.
� If the UTO file is created in the dBASE III format, it contains only the fieldnames.
� If the UTO file is created in the ASCII format, it is an empty file.
If you use a database or applications program to process this data, the programmust use the correct field names and field lengths. Refer to Appendix A forfield-name and field-length requirements.
9.11.2 UTO FILE-PROCESSING SUMMARY SCREENAfter UTO files are successfully generated, an output-file-processing summaryscreen, similar to Figure 9-20, appears.
CDF Input System Total Unsuccessful
File Date ID # Calls Transfers
06–27–96 0905 498 32
Waiting to return to menu.Press ENTER/RETURN to continue.
06–28–96 0905 8658 177
Begin Unsuccessful Transfer ProcessingFound 2 New or Updated Collated Day File(s):
CD960627 CD960628Do you wish to proceed making Unsuccessful Transfer Output? (y/n): Y
>>06–29–96 10:34:39 Creating Unsuccessful Transfer Output Files>>System: westreg, File Format: 1, Level: 6
Figure 9-20. UTO File-Processing Summary Screen,After Files Are Generated.
Table 9-13 describes the columns on the UTO file-processing screen(Figure 9-20). Output-file-processing summary screens are also recorded in thelog file as the output file is generated. Refer to section 8.4 for information aboutviewing and printing log files. Refer to section 7.3.3 for information about thefields common to all output-file-processing summary screens.
Table 9-13. UTO File-Processing Summary Screen Column Descriptions.
Column Description
CDF Input FileDate
The date of the CDF. Several CDFs can be produced from a singleBCF, depending on how often data is downloaded from the server.
System ID # The serial number of the server from which the CDF was taken.These serial numbers are important if data from multiple servers isprocessed by the same CDR PC.
Total Calls The total number of calls contained in the CDF.
UnsuccessfulTransfers
The number of calls that failed when transferred from a mailbox toanother telephone number. Unsuccessful transfers occur occasion-ally when callers use an ECP mailbox or automated attendant.
SECTION 9.11
O C T E L
P C / C D R
DTMF OCTELFORMS
C O N T E N T S
Edition 2Octel PC/CDR 10-iii
CHAPTER 10
10.1 OVERVIEW 10-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.2 CONFIGURING THE SERVER AND OCTEL PC/CDR FOR DTMF OCTELFORMS DATA COLLECTION 10-1. . . . . . . . . . . . . . . . . . . . . . .
10.3 ESTIMATING CDR BUFFER CAPACITY 10-2. . . . . . . . . . . . . . . . . . . . . . . . . .
10.3.1 ESTIMATING NUMBER OF BLOCKS FILLED 10-2. . . . . . . . . . . . .
10.3.1.1 Blocks Filled With DTMF OctelForms Data 10-2. . . . .
10.3.1.2 Total Blocks Filled 10-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.3.2 ESTIMATING CDR BUFFER CAPACITY, IN DAYS 10-4. . . . . . . . .
10.3.3 DETERMINING DOWNLOAD FREQUENCY 10-5. . . . . . . . . . . . . . .
10.4 ESTIMATING DOWNLOAD TIME AND PC DISK SPACE 10-6. . . . . . . . . .
10.5 PROCESSING DTMF OCTELFORMS DATA 10-6. . . . . . . . . . . . . . . . . . . . . . .
Section Page
C H A P T E R 10
Octel PC/CDR Edition 2 10-1
DTMF OCTELFORMS
10.1 OVERVIEW
DTMF OctelForms� is an optional data-collection application package currentlyavailable for servers with Aria 1.2 voice-messaging software and older softwarereleases. DTMF OctelForms allows questions to be recorded on the server andcallers to respond to the questions by pressing the touch-tone keys on atelephone. The responses are collected in the same CDR buffer as Octel PC/CDRdata and are downloaded, collated, and generated into the forms output (FDO)file using the Octel PC/CDR software package.
This chapter provides specific parameters for the setup and processing stagesrequired to use the DTMF OctelForms and Octel PC/CDR programs together.Additional information can be found elsewhere, as follows:
To . . . Refer to . . .
Set up and process DTMF OctelFormsdata
The Process Checklist in section 1.3
Find additional information about usingand setting up the DTMF OctelFormsapplication
The DTMF AspenForms System Manager’s Manual
Find a detailed description of the FDO file Chapter 9 and Appendix A
10.2 CONFIGURING THE SERVER AND OCTEL PC/CDRFOR DTMF OCTELFORMS DATA COLLECTION
In addition to the software and SMT menu configurations described in this manualfor Octel PC/CDR, certain menus on the server and the Octel PC/CDR systemattributes must be specially configured. The following special configuration allows
DTMF OctelForms data to be collected and the FDO file to be produced:
� Confirm that feature options 16 – Call Detail Recording and 43 – DTMFForms Mailbox are enabled in menu 13.7 on the system manager terminal(SMT). Refer to section 2.4.1 for details.
� From SMT menu 16.1.4, select record group 7, DTMF Forms MailboxRecords for collection. Refer to section 2.4.2 for details.
� If automatic processing is used (as described in Chapter 7), select option 10,Append Records to Forms Output File to generate the FDO file automati-cally. Refer to section 5.3.5 for instructions.
DTMF OCTELFORMS
10-2 Edition 2 Octel PC/CDR
� Choose the format of the forms output file (dBASEIII or ASCII). Refer tosection 5.3.6 for instructions.
� If a CDR system for the server using the DTMF OctelForms application waspreviously established for Octel PC/CDR, use that same CDR system toproduce the FDO file from the collated day files (CDF). Using the same CDRsystem eliminates downloading the same data from a server’s CDR buffertwice, once for use with Octel PC/CDR and once for generating the FDO filefor DTMF OctelForms.
10.3 ESTIMATING CDR BUFFER CAPACITY
Using the guidelines described in this chapter as a point ofreference, regularly monitor the CDR buffers on all serversfor which Octel PC/CDR data is collected to determine howquickly the buffers fill. Perform downloads based on thispattern to prevent the buffers from being overwritten andto prevent data from being lost.
Caution!
The amount of time between downloads of data from the CDR buffer is deter-mined by how quickly the server’s CDR buffer fills. Download data as often asnecessary to keep the CDR buffer from being overwritten. (Refer to Chapter 2 forinformation about the CDR buffer.)
Use the formulas in this section to develop guidelines for how frequently youshould be downloading data, and then monitor the CDR buffer regularly toestablish its unique fill pattern. Perform downloads accordingly.
The examples used in the following section are based on a customer with aserver that has light voice-mail usage and few special applications. Thiscustomer has a DTMF OctelForms application mailbox that is being used for apublic survey. There are 20 questions in the mailbox, and it is projected that600 people will call the application each day.
10.3.1 ESTIMATING NUMBER OF BLOCKS FILLED
When using Octel PC/CDR data to generate the FDO file and other output files,you must consider the additional data being collected for DTMF OctelForms toestimate how quickly the CDR buffer fills.
10.3.1.1 Blocks Filled With DTMF OctelForms Data. Estimate the numberof CDR blocks filled per day with DTMF OctelForms data by using the followingformula:
(Daily calls x 41) + (Daily calls x questions x 17)
2048Number of CDRblocks filled per day
=
SECTION 10.2 – 10.3
DTMF OCTELFORMS
Octel PC/CDR Edition 2 10-3
Use this formula, as follows:
Step Action Result
1. Obtain the total number of questionsasked in the server’s DTMF Octel-Forms mailboxes.
. . .
2. Obtain the estimated number of dailycalls to mailboxes configured for theDTMF OctelForms application.
. . .
3. Multiply the estimated number ofdaily calls (from step 2) by 41 (theaverage number of bytes in a DTMFOctelForms call).
The answer is the estimated numberof bytes for all calls, per day. Forexample,
600 calls x 41 bytes 24,600 bytes for all calls
4. Multiply the estimated number ofdaily calls (from step 2) by the totalnumber of questions (from step 1).
The answer is the estimated numberof responses to DTMF OctelFormsquestions received per day. Forexample,
600 calls x 20 questions 12,000 responses per day
5. Multiply the estimated number ofresponses received per day (from step4) by 17 (the average number of bytesin a response).
The answer is the number of bytesfor all responses received per day.For example,
12,000 responses x 17 bytes 204,000 bytes for all responses
6. Add the total number of bytes for allcalls (from step 3) to the total num-ber of bytes for all responses (fromstep 5).
The answer is the total number ofbytes for all calls and responses. Forexample,
24,600 bytes for all calls + 204,000 bytes for all responses 228,600 total bytes
7. Divide the total number of bytes(from step 6) by 2048 (the number ofbytes in a CDR block).
The answer is the approximate num-ber of CDR blocks filled each daywith DTMF OctelForms data. Forexample,
228,600 total bytes = 111.6 blocks 2048
112 (rounded up from 111.6)blocks of CDR buffer space arerequired on the server each dayfor DTMF OctelForms data.
SECTION 10.3
DTMF OCTELFORMS
10-4 Edition 2 Octel PC/CDR
10.3.1.2 Total Blocks Filled. Estimate the combined number of CDR blocksfilled each day with both DTMF OctelForms and Octel PC/CDR data, as follows:
Step Action Result
1. Determine the average number ofblocks filled each day with Octel PC/CDR data. Refer to section 2.2.3.1for instructions.
. . .
2. Add the number of blocks filled eachday with Octel PC/CDR data (fromstep 1) to the total number of blocksfilled each day with DTMF Octel-Forms data (from section 10.3.1.1).
The answer is the total number ofblocks filled each day for both applica-tions. For example,
If 537 blocks are filled each daywith Octel PC/CDR data,
537 blocks of Octel PC/CDR data+112 blocks of DTMF OctelForms data 649 blocks filled each day
10.3.2 ESTIMATING CDR BUFFER CAPACITY, IN DAYS
Once you know how many CDR blocks are filled each day with the combinedDTMF OctelForms and Octel PC/CDR data, estimate the number of days thatyou can collect data in the CDR buffer before performing a download. Estimatethe CDR buffer capacity for DTMF OctelForms and Octel PC/CDR data, in days,as follows:
Step Action Result
1. Determine the CDR buffer size byreferring to the entry in the TotalNumber of Blocks for CDR: field ofSMT menu 16.1.1. (Refer to section2.4.3 for instructions about usingmenu 16.1.1.)
This number indicates the maximumnumber of CDR-buffer blocks avail-able for the combined DTMF Octel-Forms and Octel PC/CDR data.
2. Divide the CDR buffer size (2020,7020, or up to 35,000 blocks,depending on the server type) by theestimated number of CDR blocksfilled per day (from section 10.3.1.2).
The answer is the approximate num-ber of days that data can be collectedin the CDR buffer before the CDRbuffer becomes full. For example,
� For a server with a 2020-blockbuffer,
2020 blocks = 3.1 days649 blocks filled
Rounded down, this means that 3days of data can be collected inthe buffer before the bufferbecomes full.
SECTION 10.3
DTMF OCTELFORMS
Octel PC/CDR Edition 2 10-5
Step ResultAction
� For a server with a 7020-blockbuffer,
7020 blocks = 10.8 days 649 blocks filled
This means that approximately 10days of data can be collected inthe buffer before the bufferbecomes full.
� For a server with a 35,000-blockbuffer,
35,000 blocks = 53.9 days 649 blocks filled
This means that approximately 54days of data can be collected inthe buffer before the bufferbecomes full.
3. Using the answer from the calcula-tion in step 2 as a guideline, monitorthe CDR buffer storage space on theserver until a fill pattern is estab-lished. Perform downloads regularly,based on this pattern, so the CDRbuffer does not become full. Refer tosection 10.3.3 to determine the rangeof days during which the downloadshould be performed.
Data from the CDR buffer is down-loaded regularly, so the buffer doesnot become full and data is not over-written.
Keep in mind that servers with a low-to-medium call volume, heavy voice-mailusage, and the Octel DTMF OctelForms application will fill the CDR buffer fasterthan the estimated number of days determined in using the preceding calculations.
10.3.3 DETERMINING DOWNLOAD FREQUENCY
Refer to section 2.2.3.3 to determine how frequently you should download CDRdata. Use the answer from step 3 in section 10.3.2 for the approximate numberof days’ worth of data that can be collected in the CDR buffer, requested in step1 of section 2.2.3.3.
Using the guidelines described in both this chapter andChapter 2 for reference, monitor the CDR buffer regularlyto determine how quickly the buffer becomes full. Performdownloads based on this pattern to avoid overwriting thebuffer and losing data.
Caution!
SECTION 10.3
DTMF OCTELFORMS
10-6 Edition 2 Octel PC/CDR
10.4 ESTIMATING DOWNLOAD TIME AND PC DISK SPACE
Monitor the amount of storage space available on your PChard drive regularly to ensure that you always have spacefor downloaded files, collated files, and output files.Running out of PC storage space could cause OctelPC/CDR irregularities.
Caution!
Once you know how often you need to download data from the CDR buffer, make sure that there is sufficient storage space on the PC hard drive to hold thedownloaded data. The PC must have the storage capacity to hold all the filescreated when data is downloaded and processed. Keeping in mind the capacityof your PC hard drive, establish a schedule for processing DTMF OctelForms andOctel PC/CDR data based on your need for the downloaded data.
Refer to section 2.3 for instructions about estimating download time, diskstorage space, and processing time.
10.5 PROCESSING DTMF OCTELFORMS DATA
Data downloading and processing for both DTMF OctelForms and Octel PC/CDRare done in the same way. Data for DTMF OctelForms and Octel PC/CDR iscollected in the same CDR buffer on the server. The Octel PC/CDR softwaredownloads the data from the CDR buffer and then sorts it using the collationand output-file-generation processes. Downloaded data is stored in binarycollection files (BCFs). Collated BCFs produce collated day files (CDFs). One CDFcontains both DTMF OctelForms and Octel PC/CDR data. To create the formsoutput (FDO) file (used for the DTMF OctelForms data), select it for generationthe same way you would select any other output file.
Refer to Chapter 1 for descriptions of BCFs and CDFs. Refer to Chapter 9 andAppendix A for output-file descriptions. Refer to Chapter 7 for descriptions of thefour methods for processing CDR data.
SECTION 10.4 – 10.5
O C T E L
P C / C D R
SERVICE INFORMATION FORTRAINED TECHNICIANS ONLY
C O N T E N T S
11-iiiEdition 2Octel PC/CDR
CHAPTER 11
11.1 OVERVIEW 11-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.2 IDENTIFYING THE SERVER CHANNEL 11-3. . . . . . . . . . . . . . . . . . . . . . . . . .
11.3 ESTABLISHING THE SERVER CHANNEL 11-4. . . . . . . . . . . . . . . . . . . . . . . .
11.4 CONNECTING THE CABLES, AND COMPLETING MENU 6.3 CONFIGURATION 11-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.5 VERIFYING MENU 6.3 CHANGES 11-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.6 ESTABLISHING OCTEL PC/CDR ATTRIBUTES FOR COMMUNICATION WITH SERVER 11-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.7 CHECKING SERVER-MODEM CONFIGURATION 11-6. . . . . . . . . . . . . . . . .
TABLETable 11-1. Overview of Equipment-Configuration Procedures 11-2. . . . . . .
Section Page
C H A P T E R 11
Octel PC/CDR Edition 2 11-1
SERVICE INFORMATION FORTRAINED TECHNICIANS ONLY
11.1 OVERVIEW
This chapter provides instructions for the Octel-trained technician to connectthe server to the CDR PC. The information in this section is provided only forOctel-trained technicians. Do not attempt these procedures unless you are anOctel-trained technician. Refer to the appropriate service manual for additionalconfiguration and connection information.
Refer to Chapter 4 for additional steps that are performed by either the Octel-trained technician or system manager.
To establish the connection between the server and the CDR PC, refer toTable 11-1 and perform the procedures in sequence. Use these procedures foreither a direct or modem connection. Refer to Chapter 4 for additional information.
Warning!Only Octel-trained technicians are allowed to perform thefollowing procedures. To avoid dangerous electrical shock,do not perform these procedures unless you are qualifiedto do so.
SERVICE INFORMATION FOR TRAINED TECHNICIANS ONLY
11-2 Edition 2 Octel PC/CDR
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table 11-1. Overview of Equipment-Configuration Procedures.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Step
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Task
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Performed By
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Section WithOctel Overture
Procedures
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Section WithBranch, Branch
XP, Aspen,Maxum SE, and MaxumProcedures
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Section WithOctel XC1000
Procedures
ÁÁÁÁÁÁÁÁÁÁÁÁ
1. ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Identify the serverchannel.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Octel-trainedtechnician
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
11.2 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
11.2 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
11.2
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
2.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Establish thechannel on theserver.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
System manageror Octel-trainedtechnician
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
4.5.2ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
4.6.1.2ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
4.7.1.2
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
3.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Connect thecables, and com-plete the menu6.3 configuration.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Octel-trainedtechnician
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
11.4
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
11.4
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
11.4
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
4.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Verify menu 6.3changes.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
System manageror Octel-trainedtechnician
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
4.5.4
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
4.6.1.4
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
4.7.1.4
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
5.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Establish OctelPC/CDR attri-butes for commu-nication with theserver.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
System manageror Octel-trainedtechnician
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
4.5.5ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
4.6.1.5ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
4.7.1.5
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
6.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Check the config-uration of theserver modem.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Octel-trainedtechnician
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
11.7
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
11.7
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
11.7
SECTION 11.1
SERVICE INFORMATION FOR TRAINED TECHNICIANS ONLY
Octel PC/CDR Edition 2 11-3
11.2 IDENTIFYING THE SERVER CHANNEL
Identify the server channel to use for the direct or modem connection to the PC,as follows:
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
If you have . . .ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Then . . .ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CommentsÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
An Octel Overture250 message server
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
1. Locate the CCF card on theserver (Figure 4-1).
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
. . .
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
2. Make note of the empty Asyncchannel (1–3) to which the datacable will be connected.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
The data cable is connected toAsync1, Async2, or Async3,regardless of whether this is adirect or modem connection.
Do not connect the cable untilinstructed to do so.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
An Octel Overture350 message server
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
1. Locate the distribution panel onthe server (Figure 4-2).
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
. . .
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
2. Make note of the empty channel(1–3) to which the data cablewill be connected.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
The data cable is connected tochannel 1 (J44), channel 2(J43), or channel 3 (J46), re-gardless of whether this is adirect or modem connection.
Do not connect the cable untilinstructed to do so.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
A Branch, BranchXP, Aspen, MaxumSE, or Maxum
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
1. Locate the scanner board onthe Branch, Branch XP, Aspen,Maxum SE, or Maxum (Figure 4-7).
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
. . .
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
2. Make note of the empty channel(1 or 2) to which the data cablewill be connected.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Channel 1 is the secondphysical port and channel 2 is the first physical port. Thedata cable is connected tochannel 1 or 2, regardless ofwhether this is a direct ormodem connection.
Do not connect the cable untilinstructed to do so.ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
An Octel XC1000
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
1. Locate the distribution panel onthe Octel XC1000 (Figure 4-12).
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
. . .
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
2. Make note of the empty channel(1–3) to which the data cablewill be connected.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
The data cable is connected tochannel 1 (J44), channel 2(J43), or channel 3 (J46), re-gardless of whether this is adirect or modem connection.
Do not connect the cable untilinstructed to do so.
SECTION 11.2
SERVICE INFORMATION FOR TRAINED TECHNICIANS ONLY
11-4 Edition 2 Octel PC/CDR
11.3 ESTABLISHING THE SERVER CHANNEL
Refer to Table 11-1 for instructions.
11.4 CONNECTING THE CABLES, AND COMPLETING THEMENU 6.3 CONFIGURATION
Connect the data cable or modem cables to the server and to the CDR PC, asfollows. Refer to the equipment configuration figures in Chapter 4, as necessary.When power to the server is restored, the changes made to menu 6.3 (describedin Chapter 4) are recognized.
SECTION 11.3 – 11.4
SERVICE INFORMATION FOR TRAINED TECHNICIANS ONLY
Octel PC/CDR Edition 2 11-5
ÁÁÁÁÁÁÁÁÁÁÁÁ
StepÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ActionÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Result
ÁÁÁÁÁÁÁÁÁÁÁÁ
1. ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Following the instructions in the appropriate servicemanual, shut down and then turn off the power to theserver.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
. . .
ÁÁÁÁÁÁÁÁÁÁÁÁ
2.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
With the cursor at the DOS prompt, turn off the PC.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
. . .ÁÁÁÁÁÁÁÁÁÁÁÁ
3.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
If you have a . . .ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Then . . .ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
. . .
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Direct connection ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
a. Connect a data cable toone end of the nullmodem (use an adapter,if necessary).
b. Connect the other end ofthe null modem to anavailable COM port onthe PC.
c. Connect the other end ofthe cable to the channelon the server that wasconfigured in menu 6.3.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Modem connection withan external PC modem
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
a. Connect one end of adata cable to an availableCOM port on the PC.
b. Connect the other end ofthe data cable to the PCmodem.
c. Connect a second cablebetween the server chan-nel that was configuredin menu 6.3 and theserver modem.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Modem connection withan internal PC modem
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Connect one end of a datacable to the server channelthat was configured inmenu 6.3, and connect theother end to the servermodem.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
4. ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Following the instructions in the appropriate servicemanual, restore power to the server.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
The technician respondsto prompts, as the serveris booted. Changes madeto menu 6.3 are recog-nized by the server.
SECTION 11.4
SERVICE INFORMATION FOR TRAINED TECHNICIANS ONLY
11-6 Edition 2 Octel PC/CDR
11.5 VERIFYING MENU 6.3 CHANGES
Refer to Table 11-1 for instructions.
11.6 ESTABLISHING OCTEL PC/CDR ATTRIBUTES FORCOMMUNICATION WITH SERVER
Refer to Table 11-1 for instructions.
11.7 CHECKING SERVER-MODEM CONFIGURATION
On all servers, if a modem connection is used, the modem in the server must beset to echo off. If this modem is set to echo on, data sent from the server isreturned to the server. (Echo on is a default setting for most modems.) The dataechoed back to the server can overflow the CDR buffer, slow down the server,and cause the server to restart. Consult your modem manual or service repre-sentative for the correct codes to use for setting the modem to echo off.
SECTION 11.5 – 11.7
C O N T E N T S
A-iEdition 2Octel PC/CDR
APPENDIXES
A: OUTPUT FILE STRUCTURES A-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B: CDR EVENT DESCRIPTIONS B-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
C: CDR EVENT BYTE SIZES BY RECORD GROUP C-1. . . . . . . . . . . . . . . . . . . . . .
D: SUBDIRECTORY FILES D-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
E: TRANSMISSION MESSAGES E-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F: SCHEDULE-LOG-FILE ENTRIES F-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
G: OCTEL PC/CDR TROUBLESHOOTING FORM G-1. . . . . . . . . . . . . . . . . . . . . . . .
Page
A AP P E N D I X
Octel PC/CDR Edition 2 A-1
OUTPUT FILE STRUCTURES
Use the tables in this appendix to interpret Octel PC/CDR output files. Refer toChapter 9 for detailed output file descriptions.
Names that appear on the screen and in files viewed or printed through the FileUtilities menu are listed in the Octel PC/CDR Field Name column of the OutputFile Structure tables, regardless of whether they were created in an ASCII ordBASE III format. Names shown in the dBASE III Field Name column appearwhen an output file with the extension of .DBF is imported into the dBASE IIIsoftware program. Output files created in an ASCII format contain data only anddo not include field names.
A.1 CALLER-MENU OUTPUT FILE STRUCTURE
The caller-menu output (CMO) file* monitors caller activity while the caller is in Enhanced Call Processing (ECP) mailbox menus (also known as single-digitmenus or callers menus). Use the CMO file to track application use, identifymodifications needed by the application (based upon frequency of choice), andmeasure caller acceptance of the ECP process. The convention Cyymmdd.ASC orCyymmdd.DBF is used to name CMO files. Table A-1 defines the file structurefor the CMO files. Table A-2 lists code values and descriptions, grouped by thefields that log the codes.
* Available with server software at Aspen Release 2.0 or newer.
OUTPUT FILE STRUCTURESAPPENDIX A
A-2 Edition 2 Octel PC/CDR
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table A-1. Caller-Menu Output File Structure.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Octel PC/CDR Field
Name
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
dBASE IIIField Name
ÁÁÁÁÁÁÁÁÁÁÁÁ
DataType
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
FieldLength
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Description
ÁÁÁÁÁÁÁÁÁÁ
SyID ÁÁÁÁÁÁÁÁÁÁÁÁ
SYSID ÁÁÁÁÁÁ
CharÁÁÁÁÁÁÁÁ
4ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Server serial number (last 4 digits)ÁÁÁÁÁÁÁÁÁÁ
PrtÁÁÁÁÁÁÁÁÁÁÁÁ
PORTIDÁÁÁÁÁÁ
CharÁÁÁÁÁÁÁÁ
3ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Port ID used for activityÁÁÁÁÁÁÁÁÁÁDate
ÁÁÁÁÁÁÁÁÁÁÁÁDATE
ÁÁÁÁÁÁCharÁÁÁÁÁÁÁÁ6
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁDate activity took place (yymmdd format)ÁÁÁÁÁ
ÁÁÁÁÁTimeÁÁÁÁÁÁÁÁÁÁÁÁTIME
ÁÁÁÁÁÁCharÁÁÁÁÁÁÁÁ6
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁTime activity took place (hhmmss format)ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
TransIDÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
TRANS_IDÁÁÁÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁÁÁÁÁ
10ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Transaction ID of call (assigned internally)
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AppID ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
APP_ID ÁÁÁÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁÁÁÁÁ
5ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ID number of application established inSMT menu 17.2ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
SourceBoxÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
SRC_BOXÁÁÁÁÁÁÁÁÁ
CharÁÁÁÁÁÁÁÁÁÁÁÁ
10ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Source mailbox number used for this call
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
DestNumÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
DEST ÁÁÁÁÁÁÁÁÁ
CharÁÁÁÁÁÁÁÁÁÁÁÁ
10ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Mailbox or extension number to which thecaller was routed from the source mailboxÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
DTÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
DEST_TYPEÁÁÁÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁÁÁÁÁ
2ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Identifies destination as mailbox or extensionaÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
APÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ACT_TYPEÁÁÁÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁÁÁÁÁ
2ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Identifies what happened while the callerwas in the source mailboxa
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁa Refer to Table A-2.
OUTPUT FILE STRUCTURES APPENDIX A
Octel PC/CDR Edition 2 A-3
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table A-2. Caller-Menu Output File:Code Values and Descriptions.
ÁÁÁÁÁÁÁÁÁÁÁÁ
CodeValue
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Description
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ACT_TYPE (AP)
ÁÁÁÁÁÁÁÁ
0 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Caller pressed 0ÁÁÁÁÁÁÁÁ
1 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Caller pressed 1ÁÁÁÁÁÁÁÁ
2 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Caller pressed 2ÁÁÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Caller pressed 3ÁÁÁÁÁÁÁÁ
4ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Caller pressed 4ÁÁÁÁÁÁÁÁ
5ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Caller pressed 5ÁÁÁÁÁÁÁÁ6
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁCaller pressed 6ÁÁÁÁ
ÁÁÁÁ7ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁCaller pressed 7ÁÁÁÁ
ÁÁÁÁ8ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁCaller pressed 8ÁÁÁÁ
ÁÁÁÁ9ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁCaller pressed 9ÁÁÁÁ
ÁÁÁÁ10ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁCaller pressed the star keyÁÁÁÁ
ÁÁÁÁÁÁÁÁ
11ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Caller pressed the pound keyÁÁÁÁÁÁÁÁÁÁÁÁ
12ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Caller timed outÁÁÁÁÁÁÁÁÁÁÁÁ
13ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Caller hung up
ÁÁÁÁÁÁÁÁ
14 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Caller entered a name for dial-by-name
ÁÁÁÁÁÁÁÁ
15 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Caller entered a mailbox or extension number
ÁÁÁÁÁÁÁÁ
99 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Unable to identify the ACT_TYPE code
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
DEST_TYPE (DT)ÁÁÁÁÁÁÁÁÁÁÁÁ
0ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
MailboxÁÁÁÁÁÁÁÁÁÁÁÁ
1ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Extension
ÁÁÁÁÁÁÁÁ
99 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Unable to identify the DEST_TYPE code
OUTPUT FILE STRUCTURESAPPENDIX A
A-4 Edition 2 Octel PC/CDR
A.2 DISK-USAGE OUTPUT FILE STRUCTURE
The disk-usage output (DUO) file* monitors server-disk-storage use and can beused for resource planning. Use the DUO file to track message- and phrase-diskusage and free space during 15-minute intervals. The convention Dyymmdd.ASCor Dyymmdd.DBF is used to name DUO files. Table A-3 defines the file structurefor the DUO files.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table A-3. Disk-Usage Output File Structure.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Octel PC/CDR
Field Name
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
dBASE IIIField Name
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
DataType
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
FieldLength
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Description
ÁÁÁÁÁÁÁÁÁÁ
SyID ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
SYSID ÁÁÁÁÁÁÁÁ
CharÁÁÁÁÁÁ
4ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Server serial number (last 4 digits)
ÁÁÁÁÁÁÁÁÁÁ
Date ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
DATE ÁÁÁÁÁÁÁÁ
CharÁÁÁÁÁÁ
6ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Date activity took place (yymmdd format)ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
TimeÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
TIMEÁÁÁÁÁÁÁÁÁÁÁÁ
CharÁÁÁÁÁÁÁÁÁ
6ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Time disk-check event was logged (hhmmssformat)
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
UMsgHÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
USEDMSGHIÁÁÁÁÁÁÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁÁ
5ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Highest amount of message–disk space, inminutes, used during 15-minute interval
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
UMsgAÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
USEDMSGAVGÁÁÁÁÁÁÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁÁ
5ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Average amount of message–disk space, inminutes, used during 15-minute interval
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
UMsgLÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
USEDMSGLOWÁÁÁÁÁÁÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁÁ
5ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Lowest amount of message–disk space, inminutes, used during 15-minute interval
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
UPhrHÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
USEDPHRHIÁÁÁÁÁÁÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁÁ
5ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Highest amount of phrase–disk space, inminutes, used during 15-minute interval
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
UPhrAÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
USEDPHRAVGÁÁÁÁÁÁÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁÁ
5ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Average amount of phrase–disk space, inminutes, used during 15-minute interval
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
UPhrLÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
USEDPHRLOWÁÁÁÁÁÁÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁÁ
5ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Lowest amount of phrase–disk space, inminutes, used during 15-minute interval
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
FMsgHÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
FREEMSGHIÁÁÁÁÁÁÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁÁ
5ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Highest amount of available message space,in minutes, during 15-minute interval
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
FMsgAÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
FREEMSGAVGÁÁÁÁÁÁÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁÁ
5ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Average amount of available message space,in minutes, during 15-minute intervalÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
FMsgLÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
FREEMSGLOWÁÁÁÁÁÁÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁÁ
5ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Lowest amount of available message space,in minutes, during 15-minute intervalÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
FPhrHÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
FREEPHRHIÁÁÁÁÁÁÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁÁ
5ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Highest amount of available phrase space,in minutes, during 15-minute intervalÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
FPhrAÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
FREEPHRAVGÁÁÁÁÁÁÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁÁ
5ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Average amount of available phrase space,in minutes, during 15-minute intervalÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
FPhrLÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
FREEPHRLOWÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁÁÁÁÁ
5ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Lowest amount of available phrase space, inminutes, during 15-minute interval
* Available with server software at Aspen Release 2.0 or newer.
OUTPUT FILE STRUCTURES APPENDIX A
Octel PC/CDR Edition 2 A-5
A.3 FAX OUTPUT FILE STRUCTURE
The fax output (FXO) file* contains events specific to fax-transmission activity.(General fax-messaging activity details are found in the MDO and SDO files.) Theconvention Fyymmdd.ASC or Fyymmdd.DBF is used to name FXO files.Table A-4 defines the file structure. Table A-5 lists code values and descriptions,grouped by the fields that log the codes.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table A-4. Fax Output File Structure.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Octel PC/CDRField Name
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
dBASE IIIField Name
ÁÁÁÁÁÁÁÁÁ
DataType
ÁÁÁÁÁÁÁÁÁÁÁÁ
FieldLength
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
DescriptionÁÁÁÁÁÁÁÁÁÁÁÁSyID
ÁÁÁÁÁÁÁÁÁÁÁÁSYSID
ÁÁÁÁÁÁCharÁÁÁÁÁÁÁÁ4
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁServer serial number (last 4 digits)ÁÁÁÁÁÁ
ÁÁÁÁÁÁPrtÁÁÁÁÁÁÁÁÁÁÁÁPORTID
ÁÁÁÁÁÁCharÁÁÁÁÁÁÁÁ3
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁPort ID used for fax activityÁÁÁÁÁÁ
ÁÁÁÁÁÁDateÁÁÁÁÁÁÁÁÁÁÁÁDATE
ÁÁÁÁÁÁCharÁÁÁÁÁÁÁÁ6
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁDate activity took place (yymmdd format)ÁÁÁÁÁÁ
ÁÁÁÁÁÁTimeÁÁÁÁÁÁÁÁÁÁÁÁTIME
ÁÁÁÁÁÁCharÁÁÁÁÁÁÁÁ6
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁTime activity took place (hhmmss format)ÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
TransIDÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
TRANS_IDÁÁÁÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁÁÁÁÁ
10ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Transaction ID of call (assigned internally)
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AppID ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
APP_ID ÁÁÁÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁÁÁÁÁ
5 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ID number of the application establishedin SMT menu 17.2
ÁÁÁÁÁÁÁÁÁÁÁÁ
Mailbox ÁÁÁÁÁÁÁÁÁÁÁÁ
MAILBOX ÁÁÁÁÁÁ
CharÁÁÁÁÁÁÁÁ
10 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Mailbox number involved in activity
ÁÁÁÁÁÁÁÁÁÁÁÁ
AC ÁÁÁÁÁÁÁÁÁÁÁÁ
ACTIVITY ÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁ
2 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Code description of specific fax activitya
ÁÁÁÁÁÁÁÁÁÁÁÁ
FxP ÁÁÁÁÁÁÁÁÁÁÁÁ
FAX_PAGE ÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Length of fax image, in pages
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
FxSec ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
FAX_SEC ÁÁÁÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁÁÁÁÁ
5 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Length of fax image measured in storageseconds (contains –1 if the length of thefax image is more than 32,000 seconds)
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
FaxDestina-tion
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
FAX_DEST ÁÁÁÁÁÁÁÁÁÁÁÁ
CharÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
24 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Fax telephone number used; field isblank if request for a fax copy made froma fax machine
ÁÁÁÁÁÁÁÁÁÁÁÁ
FaxID ÁÁÁÁÁÁÁÁÁÁÁÁ
FAX_ID ÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁ
5 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Fax ID involved in activity
ÁÁÁÁÁÁÁÁÁÁÁÁ
OFax ÁÁÁÁÁÁÁÁÁÁÁÁ
OFAX_ID ÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁ
5 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Original fax ID for returned fax imageÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
StartÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
STARTÁÁÁÁÁÁÁÁÁ
CharÁÁÁÁÁÁÁÁÁÁÁÁ
6ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Start time for fax activity, if fax receive orprint eventÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
StopÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
STOPÁÁÁÁÁÁÁÁÁ
CharÁÁÁÁÁÁÁÁÁÁÁÁ
6ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Stop time for fax activity, if fax receive orprint event
ÁÁÁÁÁÁÁÁÁÁÁÁ
TC ÁÁÁÁÁÁÁÁÁÁÁÁ
TERM_CODEÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Termination code for fax activitya
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
OtherNodeb ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
OTH_NODEbÁÁÁÁÁÁÁÁÁ
CharÁÁÁÁÁÁÁÁÁÁÁÁ
24 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Destination node for fax network messagetransmitted or fax message sent; sourcenode for fax network message receivedÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
OtherBoxbÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
OTH_BOXbÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
16ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Destination mailbox for fax network mes-sage transmitted or fax message sent;source mailbox for fax network messagereceived
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
a Refer to Table A-5.b Appears only when server software is at Aspen Release 4.0 or newer.
* Available with server software at Aspen Release 2.0 or newer.
OUTPUT FILE STRUCTURESAPPENDIX A
A-6 Edition 2 Octel PC/CDR
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table A-5. Fax Output File:Code Values and Descriptions.
ÁÁÁÁÁÁÁÁÁÁÁÁ
CodeValue
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Description
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ACTIVITY (AC)
ÁÁÁÁÁÁÁÁ
0 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Fax message sent
ÁÁÁÁÁÁÁÁ
1 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Fax message deleted
ÁÁÁÁ2 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁFax message receivedÁÁÁÁÁÁÁÁ
3ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Fax returned to senderÁÁÁÁÁÁÁÁÁÁÁÁ
20 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Printed by user
ÁÁÁÁ21 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁPrinted by auto-printÁÁÁÁÁÁÁÁ
22ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Printed by print-allÁÁÁÁÁÁÁÁ
23 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Printed by fax Information Center Mailbox� (ICMB)ÁÁÁÁÁÁÁÁ
39a ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Networked fax returned to senderÁÁÁÁÁÁÁÁ
40a ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Networked fax message transmitted
ÁÁÁÁÁÁÁÁ
45a ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Networked fax-message copy transmittedÁÁÁÁÁÁÁÁ
50a ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Networked fax message receivedÁÁÁÁÁÁÁÁ
55a ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Networked fax-message copy received
ÁÁÁÁÁÁÁÁ
60b ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Hub returned information to senderÁÁÁÁÁÁÁÁ99
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁUnable to identify the ACTIVITY codeÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
TERM_CODE (TC)
ÁÁÁÁÁÁÁÁ
0 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Entire fax document received, sent, or deletedÁÁÁÁÁÁÁÁ
1 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Too many errorsÁÁÁÁÁÁÁÁ
2 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
No communication
ÁÁÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Loss of carrierÁÁÁÁÁÁÁÁÁÁÁÁ
4ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Timeout
ÁÁÁÁÁÁÁÁ
5 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Page limit exceeded
ÁÁÁÁÁÁÁÁ
6 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Disk fullÁÁÁÁÁÁÁÁ20
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁContinuously busyÁÁÁÁ
ÁÁÁÁ21ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Ring-no-answerÁÁÁÁÁÁÁÁ
22 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Continuously bad lineÁÁÁÁÁÁÁÁ23
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁNon-fax-capable device detectedÁÁÁÁ
ÁÁÁÁ24 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Total retries exceededÁÁÁÁÁÁÁÁ
30a ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Message received by mailbox with extended-absence greetingÁÁÁÁÁÁÁÁ
31a ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Wrong mailbox type
ÁÁÁÁÁÁÁÁ
32a ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Destination mailbox is full
ÁÁÁÁÁÁÁÁ
33a ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Destination-mailbox future-delivery limit exceededÁÁÁÁÁÁÁÁ
34a ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Bad message or network transmission
ÁÁÁÁÁÁÁÁ
35a ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Receiving side determined bad message; message returned to senderÁÁÁÁÁÁÁÁ36a
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁReceiving system fullÁÁÁÁ
ÁÁÁÁ37aÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
NameNet ASCII name mismatchÁÁÁÁÁÁÁÁ
38a ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Message blocked by receiving mailboxÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
a Appears only when server software is at Aspen Release 4.0 or newer.b Appears only when server software is at Aspen Release 4.1, Aria 1.1, or newer.
OUTPUT FILE STRUCTURES APPENDIX A
Octel PC/CDR Edition 2 A-7
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table A-5. Fax Output File:Code Values and Descriptions (Concluded).
ÁÁÁÁÁÁÁÁÁÁÁÁ
CodeValue
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Description
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
TERM_CODE (TC) (Concluded)
ÁÁÁÁÁÁÁÁ
39a ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Destination mailbox does not exist
ÁÁÁÁÁÁÁÁ
40a ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Fax protocol timeout, nothing transmittedÁÁÁÁÁÁÁÁ41a
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁFax protocol timeout, partial fax transmittedÁÁÁÁ
ÁÁÁÁ42aÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Bad fax imageÁÁÁÁÁÁÁÁ
43a ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Bad message driveÁÁÁÁÁÁÁÁ
44aÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Node deletedÁÁÁÁÁÁÁÁ
45a ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Node disabled with the request to return messageÁÁÁÁÁÁÁÁ
46a ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Receiving mailbox not capable of receiving faxesÁÁÁÁÁÁÁÁ
47a ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Receiving port not capable of receiving faxes
ÁÁÁÁÁÁÁÁ
48a ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Receiving node not capable of receiving faxes
ÁÁÁÁÁÁÁÁ
49a ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Transmission port not capable of sending faxes
ÁÁÁÁÁÁÁÁ
50a ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Transmission error
ÁÁÁÁÁÁÁÁ
51b ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Failed to deliver message because of hub synchronization problem
ÁÁÁÁÁÁÁÁ
99 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Unable to identify the TERM_CODE code
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
a Appears only when server software is at Aspen Release 4.0 or newer.b Appears only when server software is at Aspen Release 4.1, Aria 1.1, or newer.
OUTPUT FILE STRUCTURESAPPENDIX A
A-8 Edition 2 Octel PC/CDR
A.4 FORMS OUTPUT FILE STRUCTURE
The forms output (FDO) file contains data related to calls into DTMF OctelFormsmailboxes. The convention Forms.ASC or Forms.DBF is used to name formsoutput files. Table A-6 defines the file structure. Refer to the DTMF OctelFormsManual for detailed information about using forms output file data.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table A-6. Forms Output File Structure.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Octel PC/CDRField Name
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
dBASE IIIField Name
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
DataType
ÁÁÁÁÁÁÁÁÁÁÁÁ
FieldLength
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Description
ÁÁÁÁÁÁÁÁÁÁÁÁ
Prt ÁÁÁÁÁÁÁÁÁÁÁÁ
PORT ÁÁÁÁÁÁÁÁ
Char ÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Port used for session (disregard entries for port 255a)ÁÁÁÁÁÁ
ÁÁÁÁÁÁDateÁÁÁÁÁÁÁÁÁÁÁÁDATE
ÁÁÁÁÁÁÁÁChar
ÁÁÁÁÁÁ6ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁSession start date (yymmdd format)ÁÁÁÁÁÁ
ÁÁÁÁÁÁTimeÁÁÁÁÁÁÁÁÁÁÁÁTIME
ÁÁÁÁÁÁÁÁChar
ÁÁÁÁÁÁ6ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁSession start time (hhmmss format)ÁÁÁÁÁÁ
ÁÁÁÁÁÁSeq
ÁÁÁÁÁÁÁÁÁÁÁÁ
SEQUENCEÁÁÁÁÁÁÁÁ
NumÁÁÁÁÁÁ
3ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Mailbox-sequence trackingÁÁÁÁÁÁÁÁÁÁÁÁ
MailboxÁÁÁÁÁÁÁÁÁÁÁÁ
MAILBOXÁÁÁÁÁÁÁÁ
CharÁÁÁÁÁÁ
10ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Type 12 mailboxÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Ques ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
QUESTION ÁÁÁÁÁÁÁÁÁÁÁÁ
Num ÁÁÁÁÁÁÁÁÁ
4 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
OctelForms question number, frommailbox setup through the server
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Answer ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ANSWER ÁÁÁÁÁÁÁÁÁÁÁÁ
Char ÁÁÁÁÁÁÁÁÁ
16 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Caller’s touch-tone responses to OctelForms questions
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
a Port 255 represents special information used by service personnel. Refer to Table A-7.
Table A-7 contains additional information about Prt 255 entries that is of use toservice personnel. The entry in the FDO Ques field that corresponds to a Prt255 entry determines the reason for that entry. The entry in the Related Eventcolumn refers to the CDR event that caused the entry in the FDO Ques field.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table A-7. Port 255 Entries.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Entry inFDO Ques
Field
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Explanation
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
RelatedEvent
ÁÁÁÁÁÁÁÁÁÁ
9900 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Reason not known ÁÁÁÁÁÁÁÁÁÁ
IPLÁÁÁÁÁÁÁÁÁÁ
9901 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Power failure ÁÁÁÁÁÁÁÁÁÁ
IPLÁÁÁÁÁÁÁÁÁÁ
9902 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Server crashed ÁÁÁÁÁÁÁÁÁÁ
IPLÁÁÁÁÁÁÁÁÁÁ
9903 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Parity error occurred ÁÁÁÁÁÁÁÁÁÁ
IPLÁÁÁÁÁÁÁÁÁÁ
9904 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Server shut down by system manager ÁÁÁÁÁÁÁÁÁÁ
IPL
ÁÁÁÁÁÁÁÁÁÁ
9910 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Initialized clock in new installation ÁÁÁÁÁÁÁÁÁÁ
DTS
ÁÁÁÁÁÁÁÁÁÁ
9911 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Clock not valid at boot up ÁÁÁÁÁÁÁÁÁÁ
DTS
ÁÁÁÁÁÁÁÁÁÁ
9912 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Clock changed by system manager ÁÁÁÁÁÁÁÁÁÁ
DTS
ÁÁÁÁÁÁÁÁÁÁ
9913 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Clock changed by cluster card ÁÁÁÁÁÁÁÁÁÁ
DTS
ÁÁÁÁÁÁÁÁÁÁ
9920 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Confirmed DTMF forms mailbox records not selected forcollection in SMT menu 16.1.4
ÁÁÁÁÁÁÁÁÁÁ
CDRCFG
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
9921ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Confirmed DTMF forms mailbox records selected for collectionin SMT menu 16.1.4
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CDRCFG
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
9922 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Software inconsistency, contact your local Octel or distributorservice representative for assistance
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CDRCFG
OUTPUT FILE STRUCTURES APPENDIX A
Octel PC/CDR Edition 2 A-9
A.5 INDIVIDUAL-PORT-STATISTICS OUTPUT FILESTRUCTUREThe individual-port-statistics output (PSO) file contains two records for every15-minute period. These records are identified by the entry in the TYPE (T) field.The first record, labeled N, contains the number of calls that began on each portfor the 15-minute period. The second record, labeled T, contains the number ofseconds that the port was in use during the specified 15-minute period. Theconvention Pyymmdd.ASC or Pyymmdd.DBF is used to name PSO files. TableA-8 defines the PSO file structure for the Branch, Branch XP, Aspen, Maxum,and Maxum SE voice processors. Table A-9 defines the PSO file structure for theOctel Overture 250 message server. Table A-10 defines the PSO file structure forthe Octel Overture 350 message server and the Octel XC1000.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table A-8. Individual-Port-Statistics Output File Structurefor Branch, Branch XP, Aspen, and Maxum.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Octel PC/CDR
Field Name
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
dBASE IIIField Name
ÁÁÁÁÁÁÁÁÁÁÁÁ
DataType
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
FieldLength
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Description
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
T ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
TYPE ÁÁÁÁÁÁÁÁÁ
CharÁÁÁÁÁÁÁÁÁÁÁÁ
1 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Value equals N (number of calls) or valueequals T (number of seconds/time)
ÁÁÁÁÁÁÁÁÁÁ
SyID ÁÁÁÁÁÁÁÁÁÁÁÁ
SYSID ÁÁÁÁÁÁ
CharÁÁÁÁÁÁÁÁ
4 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Server serial number (last 4 digits)
ÁÁÁÁÁÁÁÁÁÁ
Date ÁÁÁÁÁÁÁÁÁÁÁÁ
DATE ÁÁÁÁÁÁ
CharÁÁÁÁÁÁÁÁ
6 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Date (yymmdd format)
ÁÁÁÁÁHH ÁÁÁÁÁÁHOUR ÁÁÁCharÁÁÁÁ2 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁHour of day (00–23)ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
MMÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
MINÁÁÁÁÁÁÁÁÁÁÁÁ
CharÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
2ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
15-minute-period ending time (00, 15, 30, 45)
ÁÁÁÁÁÁÁÁÁÁ01A
ÁÁÁÁÁÁÁÁÁÁÁÁP01A
ÁÁÁÁÁÁNumÁÁÁÁÁÁÁÁ3
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁNumber of calls or seconds (Port 1A)ÁÁÁÁÁ
ÁÁÁÁÁ01B
ÁÁÁÁÁÁÁÁÁÁÁÁ
P01BÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁ
3ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of calls or seconds (Port 1B)ÁÁÁÁÁÁÁÁÁÁ
01C ÁÁÁÁÁÁÁÁÁÁÁÁ
P01C ÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of calls or seconds (Port 1C)ÁÁÁÁÁÁÁÁÁÁ
01D ÁÁÁÁÁÁÁÁÁÁÁÁ
P01D ÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of calls or seconds (Port 1D)ÁÁÁÁÁÁÁÁÁÁ
02A ÁÁÁÁÁÁÁÁÁÁÁÁ
P02A ÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of calls or seconds (Port 2A)
ÁÁÁÁÁÁÁÁÁÁ
02B ÁÁÁÁÁÁÁÁÁÁÁÁ
P02B ÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of calls or seconds (Port 2B)ÁÁÁÁÁÁÁÁÁÁ
02C ÁÁÁÁÁÁÁÁÁÁÁÁ
P02C ÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of calls or seconds (Port 2C)ÁÁÁÁÁÁÁÁÁÁ
02D ÁÁÁÁÁÁÁÁÁÁÁÁ
P02D ÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of calls or seconds (Port 2D)ÁÁÁÁÁÁÁÁÁÁ
03A ÁÁÁÁÁÁÁÁÁÁÁÁ
P03A ÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of calls or seconds (Port 3A)
ÁÁÁÁÁÁÁÁÁÁ
03B ÁÁÁÁÁÁÁÁÁÁÁÁ
P03B ÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of calls or seconds (Port 3B)
ÁÁÁÁÁÁÁÁÁÁ
. ÁÁÁÁÁÁÁÁÁÁÁÁ
. ÁÁÁÁÁÁ
. ÁÁÁÁÁÁÁÁ
. ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
.ÁÁÁÁÁÁÁÁÁÁ
. ÁÁÁÁÁÁÁÁÁÁÁÁ
. ÁÁÁÁÁÁ
. ÁÁÁÁÁÁÁÁ
. ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
.
ÁÁÁÁÁÁÁÁÁÁ
. ÁÁÁÁÁÁÁÁÁÁÁÁ
. ÁÁÁÁÁÁ
. ÁÁÁÁÁÁÁÁ
. ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
.
ÁÁÁÁÁÁÁÁÁÁ
18A ÁÁÁÁÁÁÁÁÁÁÁÁ
P18A ÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of calls or seconds (Port 18A)
ÁÁÁÁÁÁÁÁÁÁ
18B ÁÁÁÁÁÁÁÁÁÁÁÁ
P18B ÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of calls or seconds (Port 18B)
ÁÁÁÁÁÁÁÁÁÁ
18C ÁÁÁÁÁÁÁÁÁÁÁÁ
P18C ÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of calls or seconds (Port 18C)
ÁÁÁÁÁÁÁÁÁÁ
18D ÁÁÁÁÁÁÁÁÁÁÁÁ
P18D ÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of calls or seconds (Port 18D)ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
BsyaÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
BusyaÁÁÁÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁÁÁÁÁ
3ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of times or seconds all server portsbusyÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
a Appears only when file-format level 3 or higher is selected and server software is at Aspen Release 2.0 ornewer.
OUTPUT FILE STRUCTURESAPPENDIX A
A-10 Edition 2 Octel PC/CDR
Because the Octel Overture 250 supports only ports 1A through 9H, disregardfields for ports greater than 9H that might be displayed.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table A-9. Individual-Port-Statistics Output File Structurefor Octel Overture 250.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Octel PC/CDR Field
Name
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
dBASE IIIField Name
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
DataType
ÁÁÁÁÁÁÁÁÁÁÁÁ
FieldLength
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Description
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
T ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
TYPE ÁÁÁÁÁÁÁÁÁÁÁÁ
Char ÁÁÁÁÁÁÁÁÁ
1 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Value equals N (number of calls) or valueequals T (number of seconds/time)
ÁÁÁÁÁSyID ÁÁÁÁÁÁSYSID ÁÁÁÁChar ÁÁÁ4 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁServer serial number (last 4 digits)ÁÁÁÁÁÁÁÁÁÁDate
ÁÁÁÁÁÁÁÁÁÁÁÁDATE
ÁÁÁÁÁÁÁÁChar
ÁÁÁÁÁÁ6ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁDate (yymmdd format)ÁÁÁÁÁ
ÁÁÁÁÁHH
ÁÁÁÁÁÁÁÁÁÁÁÁ
HOURÁÁÁÁÁÁÁÁ
CharÁÁÁÁÁÁ
2ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Hour of day (00–23)ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
MM ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
MIN ÁÁÁÁÁÁÁÁÁÁÁÁ
Char ÁÁÁÁÁÁÁÁÁ
2 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
15-minute-period ending time (00, 15,30, 45)
ÁÁÁÁÁÁÁÁÁÁ
01AÁÁÁÁÁÁÁÁÁÁÁÁ
P01AÁÁÁÁÁÁÁÁ
NumÁÁÁÁÁÁ
3ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of calls or seconds (Port 1A)ÁÁÁÁÁÁÁÁÁÁ
01B ÁÁÁÁÁÁÁÁÁÁÁÁ
P01B ÁÁÁÁÁÁÁÁ
Num ÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of calls or seconds (Port 1B)ÁÁÁÁÁÁÁÁÁÁ
01C ÁÁÁÁÁÁÁÁÁÁÁÁ
P01C ÁÁÁÁÁÁÁÁ
Num ÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of calls or seconds (Port 1C)ÁÁÁÁÁÁÁÁÁÁ
01D ÁÁÁÁÁÁÁÁÁÁÁÁ
P01D ÁÁÁÁÁÁÁÁ
Num ÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of calls or seconds (Port 1D)
ÁÁÁÁÁÁÁÁÁÁ
01E ÁÁÁÁÁÁÁÁÁÁÁÁ
P01E ÁÁÁÁÁÁÁÁ
Num ÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of calls or seconds (Port 1E)
ÁÁÁÁÁÁÁÁÁÁ
01F ÁÁÁÁÁÁÁÁÁÁÁÁ
P01F ÁÁÁÁÁÁÁÁ
Num ÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of calls or seconds (Port 1F)ÁÁÁÁÁÁÁÁÁÁ
01G ÁÁÁÁÁÁÁÁÁÁÁÁ
P01G ÁÁÁÁÁÁÁÁ
Num ÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of calls or seconds (Port 1G)
ÁÁÁÁÁÁÁÁÁÁ
01H ÁÁÁÁÁÁÁÁÁÁÁÁ
P01H ÁÁÁÁÁÁÁÁ
Num ÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of calls or seconds (Port 1H)
ÁÁÁÁÁ. ÁÁÁÁÁÁ. ÁÁÁÁ. ÁÁÁ. ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ.ÁÁÁÁÁÁÁÁÁÁ.
ÁÁÁÁÁÁÁÁÁÁÁÁ.
ÁÁÁÁÁÁÁÁ.
ÁÁÁÁÁÁ.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ.ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
.ÁÁÁÁÁÁÁÁÁÁÁÁ
.ÁÁÁÁÁÁÁÁÁ
.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
.
ÁÁÁÁÁÁÁÁÁÁ
09A ÁÁÁÁÁÁÁÁÁÁÁÁ
P09A ÁÁÁÁÁÁÁÁ
Num ÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of calls or seconds (Port 09A)ÁÁÁÁÁÁÁÁÁÁ09B
ÁÁÁÁÁÁÁÁÁÁÁÁP09B
ÁÁÁÁÁÁÁÁNum
ÁÁÁÁÁÁ3ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁNumber of calls or seconds (Port 09B)ÁÁÁÁÁ
ÁÁÁÁÁ09C
ÁÁÁÁÁÁÁÁÁÁÁÁ
P09CÁÁÁÁÁÁÁÁ
NumÁÁÁÁÁÁ
3ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of calls or seconds (Port 09C)ÁÁÁÁÁÁÁÁÁÁ
09D ÁÁÁÁÁÁÁÁÁÁÁÁ
P09D ÁÁÁÁÁÁÁÁ
Num ÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of calls or seconds (Port 09D)ÁÁÁÁÁÁÁÁÁÁ
09E ÁÁÁÁÁÁÁÁÁÁÁÁ
P09E ÁÁÁÁÁÁÁÁ
Num ÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of calls or seconds (Port 09E)ÁÁÁÁÁÁÁÁÁÁ09F
ÁÁÁÁÁÁÁÁÁÁÁÁP09F
ÁÁÁÁÁÁÁÁNum
ÁÁÁÁÁÁ3ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁNumber of calls or seconds (Port 09F)ÁÁÁÁÁ
ÁÁÁÁÁ09G
ÁÁÁÁÁÁÁÁÁÁÁÁ
P09GÁÁÁÁÁÁÁÁ
NumÁÁÁÁÁÁ
3ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of calls or seconds (Port 09G)ÁÁÁÁÁÁÁÁÁÁ
09H ÁÁÁÁÁÁÁÁÁÁÁÁ
P09H ÁÁÁÁÁÁÁÁ
Num ÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of calls or seconds (Port 09H)ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Bsya ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Busya ÁÁÁÁÁÁÁÁÁÁÁÁ
Num ÁÁÁÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of times or seconds all serverports busy
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
a Appears only when file-format level 3 or higher is selected.
OUTPUT FILE STRUCTURES APPENDIX A
Octel PC/CDR Edition 2 A-11
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table A-10. Individual-Port-Statistics Output File Structurefor Octel XC1000 and Octel Overture 350.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Octel PC/CDR Field
Name
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
dBASE IIIField Name
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
DataType
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
FieldLength
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Description
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
T ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
TYPE ÁÁÁÁÁÁÁÁÁÁÁÁ
Char ÁÁÁÁÁÁÁÁÁÁÁÁ
1 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Value equals N (number of calls) or valueequals T (number of seconds/time)
ÁÁÁÁÁÁÁÁÁÁÁÁ
SyID ÁÁÁÁÁÁÁÁÁÁ
SYSID ÁÁÁÁÁÁÁÁ
Char ÁÁÁÁÁÁÁÁ
4 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Server serial number (last 4 digits)
ÁÁÁÁÁÁDate ÁÁÁÁÁDATE ÁÁÁÁChar ÁÁÁÁ6 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁDate (yymmdd format)ÁÁÁÁÁÁÁÁÁÁÁÁHH
ÁÁÁÁÁÁÁÁÁÁHOUR
ÁÁÁÁÁÁÁÁChar
ÁÁÁÁÁÁÁÁ2
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁHour of day (00–23)ÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
MMÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
MINÁÁÁÁÁÁÁÁÁÁÁÁ
CharÁÁÁÁÁÁÁÁÁÁÁÁ
2ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
15-minute-period ending time (00, 15,30, 45)
ÁÁÁÁÁÁÁÁÁÁÁÁ01A
ÁÁÁÁÁÁÁÁÁÁP01A
ÁÁÁÁÁÁÁÁNum
ÁÁÁÁÁÁÁÁ3
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁNumber of calls or seconds (Port 1A)ÁÁÁÁÁÁ
ÁÁÁÁÁÁ01B
ÁÁÁÁÁÁÁÁÁÁ
P01BÁÁÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁ
3ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of calls or seconds (Port 1B)ÁÁÁÁÁÁÁÁÁÁÁÁ
01C ÁÁÁÁÁÁÁÁÁÁ
P01C ÁÁÁÁÁÁÁÁ
Num ÁÁÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of calls or seconds (Port 1C)ÁÁÁÁÁÁÁÁÁÁÁÁ
01D ÁÁÁÁÁÁÁÁÁÁ
P01D ÁÁÁÁÁÁÁÁ
Num ÁÁÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of calls or seconds (Port 1D)ÁÁÁÁÁÁÁÁÁÁÁÁ
01E ÁÁÁÁÁÁÁÁÁÁ
P01E ÁÁÁÁÁÁÁÁ
Num ÁÁÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of calls or seconds (Port 1E)
ÁÁÁÁÁÁÁÁÁÁÁÁ
01F ÁÁÁÁÁÁÁÁÁÁ
P01F ÁÁÁÁÁÁÁÁ
Num ÁÁÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of calls or seconds (Port 1F)ÁÁÁÁÁÁÁÁÁÁÁÁ
01G ÁÁÁÁÁÁÁÁÁÁ
P01G ÁÁÁÁÁÁÁÁ
Num ÁÁÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of calls or seconds (Port 1G)ÁÁÁÁÁÁÁÁÁÁÁÁ
01H ÁÁÁÁÁÁÁÁÁÁ
P01H ÁÁÁÁÁÁÁÁ
Num ÁÁÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of calls or seconds (Port 1H)
ÁÁÁÁÁÁÁÁÁÁÁÁ
01I ÁÁÁÁÁÁÁÁÁÁ
P01I ÁÁÁÁÁÁÁÁ
Num ÁÁÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of calls or seconds (Port 1I)
ÁÁÁÁÁÁÁÁÁÁÁÁ
01J ÁÁÁÁÁÁÁÁÁÁ
P01J ÁÁÁÁÁÁÁÁ
Num ÁÁÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of calls or seconds (Port 1J)
ÁÁÁÁÁÁÁÁÁÁÁÁ
01K ÁÁÁÁÁÁÁÁÁÁ
P01K ÁÁÁÁÁÁÁÁ
Num ÁÁÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of calls or seconds (Port 1K)ÁÁÁÁÁÁÁÁÁÁÁÁ
01L ÁÁÁÁÁÁÁÁÁÁ
P01L ÁÁÁÁÁÁÁÁ
Num ÁÁÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of calls or seconds (Port 1L)
ÁÁÁÁÁÁÁÁÁÁÁÁ
. ÁÁÁÁÁÁÁÁÁÁ
. ÁÁÁÁÁÁÁÁ
. ÁÁÁÁÁÁÁÁ
. ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
.ÁÁÁÁÁÁÁÁÁÁÁÁ.
ÁÁÁÁÁÁÁÁÁÁ.
ÁÁÁÁÁÁÁÁ.
ÁÁÁÁÁÁÁÁ.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ.ÁÁÁÁÁÁ
ÁÁÁÁÁÁ.
ÁÁÁÁÁÁÁÁÁÁ
.ÁÁÁÁÁÁÁÁ
.ÁÁÁÁÁÁÁÁ
.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
.ÁÁÁÁÁÁÁÁÁÁÁÁ
12A ÁÁÁÁÁÁÁÁÁÁ
P12A ÁÁÁÁÁÁÁÁ
Num ÁÁÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of calls or seconds (Port 12A)ÁÁÁÁÁÁÁÁÁÁÁÁ
12B ÁÁÁÁÁÁÁÁÁÁ
P12B ÁÁÁÁÁÁÁÁ
Num ÁÁÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of calls or seconds (Port 12B)ÁÁÁÁÁÁÁÁÁÁÁÁ12C
ÁÁÁÁÁÁÁÁÁÁP12C
ÁÁÁÁÁÁÁÁNum
ÁÁÁÁÁÁÁÁ3
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁNumber of calls or seconds (Port 12C)ÁÁÁÁÁÁ
ÁÁÁÁÁÁ12D
ÁÁÁÁÁÁÁÁÁÁ
P12DÁÁÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁ
3ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of calls or seconds (Port 12D)ÁÁÁÁÁÁÁÁÁÁÁÁ12E
ÁÁÁÁÁÁÁÁÁÁP12E
ÁÁÁÁÁÁÁÁNum
ÁÁÁÁÁÁÁÁ3
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁNumber of calls or seconds (Port 12E)ÁÁÁÁÁÁ
ÁÁÁÁÁÁ12FÁÁÁÁÁÁÁÁÁÁP12F
ÁÁÁÁÁÁÁÁNum
ÁÁÁÁÁÁÁÁ3
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁNumber of calls or seconds (Port 12F)ÁÁÁÁÁÁ
ÁÁÁÁÁÁ12G
ÁÁÁÁÁÁÁÁÁÁ
P12GÁÁÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁ
3ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of calls or seconds (Port 12G)ÁÁÁÁÁÁÁÁÁÁÁÁ
12H ÁÁÁÁÁÁÁÁÁÁ
P12H ÁÁÁÁÁÁÁÁ
Num ÁÁÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of calls or seconds (Port 12H)ÁÁÁÁÁÁÁÁÁÁÁÁ
12I ÁÁÁÁÁÁÁÁÁÁ
P12I ÁÁÁÁÁÁÁÁ
Num ÁÁÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of calls or seconds (Port 12I)ÁÁÁÁÁÁÁÁÁÁÁÁ
12J ÁÁÁÁÁÁÁÁÁÁ
P12J ÁÁÁÁÁÁÁÁ
Num ÁÁÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of calls or seconds (Port 12J)
ÁÁÁÁÁÁÁÁÁÁÁÁ
12K ÁÁÁÁÁÁÁÁÁÁ
P12K ÁÁÁÁÁÁÁÁ
Num ÁÁÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of calls or seconds (Port 12K)
ÁÁÁÁÁÁ12L ÁÁÁÁÁP12L ÁÁÁÁNum ÁÁÁÁ3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁNumber of calls or seconds (Port 12L)ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Bsy aÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Busy aÁÁÁÁÁÁÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁÁÁÁÁ
3ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of times or seconds all serverports busy
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
a Appears only when file-format level 3 or higher is selected and server software is at Release 2.0 or newer.
OUTPUT FILE STRUCTURESAPPENDIX A
A-12 Edition 2 Octel PC/CDR
A.6 MESSAGE-DETAIL OUTPUT FILE STRUCTURE
The message-detail output (MDO) file contains records of every message that issent from or deleted from a mailbox.
The following rules apply to networked messages:
� AMIS and Administered AMIS messages are logged in an MDO file when theAMIS or Administered AMIS messages are transmitted from the server orwhen they are returned to the sender.
� OctelNet messages are logged in an MDO file when OctelNet messages arerecorded, transmitted, or returned to the sender.
� AMIS, Administered AMIS, and OctelNet messages received by the server arenot logged in an MDO file.
The convention Myymmdd.ASC or Myymmdd.DBF is used to name message-detail output files. Table A-11 defines the file structure. Table A-12 lists codevalues and descriptions, grouped by the fields that log the codes.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table A-11. Message-Detail Output File Structure.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Octel PC/CDR Field
Name
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
dBASE IIIField Name
ÁÁÁÁÁÁÁÁÁÁÁÁ
DataType
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
FieldLength
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Description
ÁÁÁÁÁÁÁÁÁÁ
SyIDÁÁÁÁÁÁÁÁÁÁÁÁ
SYSIDÁÁÁÁÁÁ
CharÁÁÁÁÁÁÁÁ
4ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Server serial number (last 4 digits)ÁÁÁÁÁÁÁÁÁÁ
PrtÁÁÁÁÁÁÁÁÁÁÁÁ
PORTIDÁÁÁÁÁÁ
CharÁÁÁÁÁÁÁÁ
3ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Port used for sessionÁÁÁÁÁÁÁÁÁÁ
Date ÁÁÁÁÁÁÁÁÁÁÁÁ
DATE ÁÁÁÁÁÁ
CharÁÁÁÁÁÁÁÁ
6ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Date of occurrence (yymmdd format)ÁÁÁÁÁÁÁÁÁÁ
Time ÁÁÁÁÁÁÁÁÁÁÁÁ
TIME ÁÁÁÁÁÁ
CharÁÁÁÁÁÁÁÁ
6ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Time of occurrence (hhmmss format)ÁÁÁÁÁÁÁÁÁÁ
Mailbox ÁÁÁÁÁÁÁÁÁÁÁÁ
MAILBOX ÁÁÁÁÁÁ
CharÁÁÁÁÁÁÁÁ
10ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Mailbox numberÁÁÁÁÁÁÁÁÁÁ
Len ÁÁÁÁÁÁÁÁÁÁÁÁ
LENGTH ÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁ
5ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Total message length (seconds)ÁÁÁÁÁÁÁÁÁÁ
AT ÁÁÁÁÁÁÁÁÁÁÁÁ
ACTION ÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁ
2ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Message send/delete action codea
ÁÁÁÁÁÁÁÁÁÁ
SR ÁÁÁÁÁÁÁÁÁÁÁÁ
S_R ÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁ
2ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Sender/receiver codea
ÁÁÁÁÁÁÁÁÁÁ
Atr ÁÁÁÁÁÁÁÁÁÁÁÁ
ATTRIB ÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁ
3ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Information about message attributesa
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ONodb orOtherNodec
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
OTH_NODEÁÁÁÁÁÁÁÁÁÁÁÁ
CharÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
4b or24c
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Node number; if message sent, destinationnode number; if messaged deleted, sourcenode number; if not a networked message,blank
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
OtherBoxÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
OTH_BOX ÁÁÁÁÁÁÁÁÁÁÁÁ
CharÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
10b
or16c
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Destination mailbox number, if messagesentb
Source mailbox number, if message deletedcÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
FxPdÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
FAX_PAGEdÁÁÁÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁÁÁÁÁ
3ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Page length of fax image sent, received, ordeleted
ÁÁÁÁÁÁÁÁÁÁ
TPd ÁÁÁÁÁÁÁÁÁÁÁÁ
TYPEd ÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁ
2ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Type of message sent, received, or deleteda
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
a Refer to Table A-12.b File-format level 1.c File-format level 2 or higher.d Appears only when file-format level 3 or higher is selected and server software is at Aspen Release 2.0 or
newer.
OUTPUT FILE STRUCTURES APPENDIX A
Octel PC/CDR Edition 2 A-13
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table A-11. Message-Detail Output File Structure (Concluded).ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Octel PC/CDR Field
Name
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
dBASE IIIField Name
ÁÁÁÁÁÁÁÁÁÁÁÁ
DataType
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
FieldLength
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Description
ÁÁÁÁÁÁÁÁÁÁ
TransIDdÁÁÁÁÁÁÁÁÁÁÁÁ
TRANS_IDdÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁ
10ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Transaction ID (assigned internally)ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AppIDd ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
APP_IDd ÁÁÁÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁÁÁÁÁ
5ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ID number of application established inSMT menu 17.2
ÁÁÁÁÁÁÁÁÁÁ
MsgIDe ÁÁÁÁÁÁÁÁÁÁÁÁ
MSG_IDe ÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁ
10ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Message segment ID (assigned internally)
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
d Appears only when file-format level 3 or higher is selected and server software is at Aspen Release 2.0 ornewer.
e Appears only when file-format level 4 or higher is selected and server software is at Aspen Release 4.0 ornewer.
OUTPUT FILE STRUCTURESAPPENDIX A
A-14 Edition 2 Octel PC/CDR
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table A-12. Message-Detail Output File:Code Values and Descriptions.
ÁÁÁÁÁÁÁÁÁÁÁÁ
CodeValue
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Description
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ACTION (AT)
ÁÁÁÁÁÁÁÁ
0 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Message deleted by subscriber; message not previously archived
ÁÁÁÁÁÁÁÁ
1 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Message deleted by subscriber; message previously archivedÁÁÁÁÁÁÁÁ2
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁMessage deleted by server; message not previously archivedÁÁÁÁ
ÁÁÁÁ3ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁMessage previously archivedÁÁÁÁ
ÁÁÁÁÁÁÁÁ
4ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Message deleted by information service (IFS); not archived
ÁÁÁÁÁÁÁÁ
5 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Message deleted by IFS; archivedÁÁÁÁÁÁÁÁ6a
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁMessage deleted by IFS updateÁÁÁÁ
ÁÁÁÁ7aÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Message deleted by external applicationÁÁÁÁÁÁÁÁ
8a ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Message deleted by fax auto-deleteÁÁÁÁÁÁÁÁ
9a ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Message deleted internally because of compounding annotation with imageÁÁÁÁÁÁÁÁ10
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁMessage sent to mailbox on this serverÁÁÁÁ
ÁÁÁÁ11ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Message sent to mailbox on another serverÁÁÁÁÁÁÁÁ
20 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Mailbox not foundÁÁÁÁÁÁÁÁ
21 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Mailbox not voice-messaging mailboxÁÁÁÁÁÁÁÁ
22 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Mailbox fullÁÁÁÁÁÁÁÁ
23ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Mailbox future-delivery message limit fullÁÁÁÁÁÁÁÁ
24 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Receiving server fullÁÁÁÁÁÁÁÁ
25 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Receiving server node deletedÁÁÁÁÁÁÁÁ
26 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Receiving server node disabled with the request to return all messages
ÁÁÁÁÁÁÁÁ
27 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Message determined bad when received at destination server
ÁÁÁÁÁÁÁÁÁÁÁÁ
28 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Receiving server node unable to receive message because node line continuously busy
ÁÁÁÁÁÁÁÁ
29 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Receiving server node line does not answer (ring-no-answer)ÁÁÁÁÁÁÁÁ30
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁReceiving server node line continuously bad lineÁÁÁÁ
ÁÁÁÁ31bÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
NameNet ASCII name mismatchÁÁÁÁÁÁÁÁÁÁÁÁ
32b ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Message blocked by receiving mailbox
ÁÁÁÁ33b ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁReceiving mailbox not capable of receiving faxesÁÁÁÁÁÁÁÁ34b
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁReceiving port not capable of receiving faxesÁÁÁÁ
ÁÁÁÁ35bÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Receiving node not capable of receiving faxesÁÁÁÁÁÁÁÁ
36b ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Transmission port not capable of sending faxesÁÁÁÁÁÁÁÁ
37c ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Hub synchronization problemÁÁÁÁÁÁÁÁ38c
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁMessage delivered to mailbox that has extended-absence greetingÁÁÁÁ
ÁÁÁÁ40aÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Message not previously archived deleted by external applicationÁÁÁÁÁÁÁÁ
41a ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Previously archived message deleted by external applicationÁÁÁÁÁÁÁÁ
42a ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Message not previously archived deleted by the serverÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
a Appears only when file-format level 3 or higher is selected and server software is at Aspen Release 2.0 ornewer.
b Appears only when server software is at Aspen Release 4.0 or newer.c Appears only when server software is at Aspen Release 4.1, Aria 1.1, or newer.
OUTPUT FILE STRUCTURES APPENDIX A
Octel PC/CDR Edition 2 A-15
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table A-12. Message-Detail Output File:Code Values and Descriptions (Continued).
ÁÁÁÁÁÁÁÁÁÁÁÁ
CodeValue
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Description
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ACTION (AT) (Concluded)
ÁÁÁÁÁÁÁÁ
43a ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Previously archived message deleted by the server
ÁÁÁÁÁÁÁÁ
44a ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Message not previously archived deleted by an internal process
ÁÁÁÁÁÁÁÁ
45a ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Previously archived message was deleted by an internal process
ÁÁÁÁÁÁÁÁ
50 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Networked-message transmission, no errors
ÁÁÁÁÁÁÁÁ
51 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Unsuccessful networked-message transmission, mailbox not found
ÁÁÁÁÁÁÁÁ
52 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Unsuccessful networked-message transmission, not a voice-messaging mailbox
ÁÁÁÁÁÁÁÁ
53 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Unsuccessful networked-message transmission, mailbox full
ÁÁÁÁÁÁÁÁ
54 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Unsuccessful networked-message transmission, future-delivery limit exceeded
ÁÁÁÁÁÁÁÁ
55 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Unsuccessful networked-message transmission, receiving server full
ÁÁÁÁÁÁÁÁ
58 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Unsuccessful networked-message transmission, message bad
ÁÁÁÁÁÁÁÁÁÁÁÁ
59b ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Unsuccessful networked-message transmission, NameNet ASCII name mismatch
ÁÁÁÁÁÁÁÁ
60 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Unsuccessful networked-message transmission, transmission (TX) error
ÁÁÁÁÁÁÁÁ
65 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS could not pass failed start sequenceÁÁÁÁÁÁÁÁ66
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁAMIS wrong numberÁÁÁÁ
ÁÁÁÁÁÁÁÁ
67ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Remote system does not support AMIS
ÁÁÁÁÁÁÁÁ
68 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS version not supported by remote system
ÁÁÁÁÁÁÁÁ
69 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS system-access telephone number rejected by remote system
ÁÁÁÁÁÁÁÁ
70 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS bad telephone number in SMTÁÁÁÁÁÁÁÁ71
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁAMIS message too longÁÁÁÁ
ÁÁÁÁÁÁÁÁ
72ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS message does not exist in remote system
ÁÁÁÁÁÁÁÁ
73 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS remote mailbox not accepting this message
ÁÁÁÁÁÁÁÁ
74 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS remote system sent cutoff
ÁÁÁÁÁÁÁÁ
75 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS bad message
ÁÁÁÁÁÁÁÁ
85b ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Unsuccessful networked-message transmission, message blocked by receivingmailbox
ÁÁÁÁÁÁÁÁÁÁÁÁ
86b ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Networked-message transmission, message received by mailbox with extended-absence greeting
ÁÁÁÁÁÁÁÁÁÁÁÁ
87bÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Unsuccessful networked-message transmission, fax protocol timeout, nothingtransmitted
ÁÁÁÁÁÁÁÁÁÁÁÁ
88b ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Unsuccessful networked-message transmission, fax protocol timeout, partialfax transmitted
ÁÁÁÁÁÁÁÁ
89b ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Unsuccessful networked-message transmission, bad fax image
ÁÁÁÁÁÁÁÁ
90b ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Unsuccessful networked-message transmission, bad message drive
ÁÁÁÁÁÁÁÁ
99 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Unable to identify the ACTION code
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
a Appears only when file-format level 3 or higher is selected and server software is at Aspen Release 2.0 ornewer.
b Appears only when server software is at Aspen Release 4.0 or newer.
OUTPUT FILE STRUCTURESAPPENDIX A
A-16 Edition 2 Octel PC/CDR
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table A-12. Message-Detail Output File:Code Values and Descriptions (Continued).
ÁÁÁÁÁÁÁÁÁÁÁÁ
CodeValue
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Description
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ATTRIB (Atr)d
ÁÁÁÁÁÁÁÁ
0 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
No attributes assigned to message
ÁÁÁÁÁÁÁÁ
2e ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Message deposited by information serviceÁÁÁÁÁÁÁÁ4
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁFuture delivery requestedÁÁÁÁ
ÁÁÁÁ8ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Message forwarded from another subscriberÁÁÁÁÁÁÁÁÁÁÁÁ
16 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Confirmation of nondelivery requested
ÁÁÁÁ32 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁConfirmation of delivery requestedÁÁÁÁÁÁÁÁ64
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁMessage marked privateÁÁÁÁ
ÁÁÁÁ128ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Message marked urgentÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
S_R (SR, Sender/Receiver Code)
ÁÁÁÁÁÁÁÁ
0 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Message sent from outside caller to subscriber’s mailboxÁÁÁÁÁÁÁÁ
1 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Message sent from one subscriber’s mailbox to another subscriber’s mailbox
ÁÁÁÁÁÁÁÁ
2 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Message sent from home mailbox to subscriber’s mailbox
ÁÁÁÁ3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁMessage sent from guest 1 mailbox to subscriber’s mailboxÁÁÁÁÁÁÁÁÁÁÁÁ
4ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Message sent from guest 2 mailbox to subscriber’s mailbox
ÁÁÁÁ5 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁMessage sent to home subscriber’s mailbox from subscriber’s mailboxÁÁÁÁÁÁÁÁ6
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁMessage sent to guest 1 mailbox from subscriber’s mailboxÁÁÁÁ
ÁÁÁÁ7ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Message sent to guest 2 mailbox from subscriber’s mailboxÁÁÁÁÁÁÁÁ
8 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Message from information service to subscriberÁÁÁÁÁÁÁÁ
20 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Network message returned to sender’s mailboxÁÁÁÁÁÁÁÁ
21c ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Hub returned information to senderÁÁÁÁÁÁÁÁÁÁÁÁ
31 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Voice-mail message sent from one subscriber’s mailbox to another subscriber’s mailbox
ÁÁÁÁÁÁÁÁ
32 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Voice-mail message sent from home mailbox to subscriber’s mailbox
ÁÁÁÁÁÁÁÁ
33 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Voice-mail message sent from guest 1 mailbox to subscriber’s mailboxÁÁÁÁÁÁÁÁÁÁÁÁ
34ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Voice-mail message sent from guest 2 mailbox to subscriber’s mailbox
ÁÁÁÁÁÁÁÁ
35 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Voice-mail message sent from subscriber’s mailbox to home mailbox
ÁÁÁÁ36 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁVoice-mail message sent from subscriber’s mailbox to guest 1 mailboxÁÁÁÁÁÁÁÁ37
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁVoice-mail message sent from subscriber’s mailbox to guest 2 mailboxÁÁÁÁ
ÁÁÁÁ38ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Voice-mail message sent from information service to subscriberÁÁÁÁÁÁÁÁ
40 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Telephone-answering message sent from outside caller to subscriber’s mailboxÁÁÁÁÁÁÁÁÁÁÁÁ
41ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Telephone-answering message sent from one subscriber’s mailbox to anothersubscriber’s mailbox
ÁÁÁÁÁÁÁÁ
50 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Network transmission, voiceÁÁÁÁÁÁÁÁ
51 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Network transmission, copyÁÁÁÁÁÁÁÁ
52 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Network transmission, special message
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
c Appears only when server software is at Aspen Release 4.1, Aria 1.1, or newer.d Add code values to determine which attributes are set. For example, for a message marked private (64) and
urgent (128), with confirmation of delivery requested (32), the total is 224.e Appears only when server software is at Aspen Release 2.0 or newer.
OUTPUT FILE STRUCTURES APPENDIX A
Octel PC/CDR Edition 2 A-17
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table A-12. Message-Detail Output File:Code Values and Descriptions (Concluded).
ÁÁÁÁÁÁÁÁÁÁÁÁ
CodeValue
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Description
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
S_R (SR, Sender/Receiver Code) (Concluded) ÁÁÁÁÁÁÁÁÁÁÁÁ
60ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS send
ÁÁÁÁ61 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁAMIS voice transmittedÁÁÁÁÁÁÁÁ62
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁAMIS message returned to senderÁÁÁÁ
ÁÁÁÁ99ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Unable to identify the S_R codeÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
TYPE (TP)a
ÁÁÁÁÁÁÁÁ
0 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Real messageÁÁÁÁÁÁÁÁ
1 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Message from external application
ÁÁÁÁÁÁÁÁ
2 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Reply message
ÁÁÁÁ3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁFax annotationÁÁÁÁÁÁÁÁÁÁÁÁ
4ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Fax image
ÁÁÁÁÁÁÁÁ
5 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Returned fax message
ÁÁÁÁÁÁÁÁ
6 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Compound fax messageÁÁÁÁÁÁÁÁ7
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁFax annotation and image (one call)ÁÁÁÁ
ÁÁÁÁ8ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Fax annotation and image (two calls)ÁÁÁÁÁÁÁÁÁÁÁÁ
9 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Converted fax messageÁÁÁÁÁÁÁÁ10
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁForwarded faxÁÁÁÁ
ÁÁÁÁ11ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁForwarded fax returned imageÁÁÁÁ
ÁÁÁÁ20b ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Networked compound fax messageÁÁÁÁÁÁÁÁ
30b ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Networked compound fax copyÁÁÁÁÁÁÁÁ
99 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Unable to identify the TYPE codeÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
a Appears only when file-format level 3 or higher is selected and server software is at Aspen Release 2.0 ornewer.
b Appears only when server software is at Aspen Release 4.0 or newer.
OUTPUT FILE STRUCTURESAPPENDIX A
A-18 Edition 2 Octel PC/CDR
A.7 NAMENET OUTPUT FILE STRUCTURE
The NameNet output (NNO) file* contains events specific to NameNet directory and alarm activity. The convention Nyymmdd.ASC or Nyymmdd.DBF is used toname NNO files. Table A-13 defines the file structure for the NNO files. Table A-14lists code values and descriptions, grouped by the fields that log the codes.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table A-13. NameNet Output File Structure.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Octel PC/CDR
Field Name
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
dBASE IIIField Name
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
DataType
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
FieldLength
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Description
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
SyIDÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
SYSIDÁÁÁÁÁÁÁÁÁÁÁÁ
CharÁÁÁÁÁÁÁÁÁ
4ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Server serial number (last 4 digits)
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Prt ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
PORTID ÁÁÁÁÁÁÁÁÁÁÁÁ
CharÁÁÁÁÁÁÁÁÁ
3ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Port ID of port used for NameNet transmission
ÁÁÁÁÁÁÁÁÁÁÁÁ
Date ÁÁÁÁÁÁÁÁÁÁ
DATE ÁÁÁÁÁÁÁÁ
CharÁÁÁÁÁÁ
6ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Date activity took place (yymmdd format)ÁÁÁÁÁÁÁÁÁÁÁÁ
TimeÁÁÁÁÁÁÁÁÁÁ
TIMEÁÁÁÁÁÁÁÁ
CharÁÁÁÁÁÁ
6ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Time activity took place (hhmmss format)ÁÁÁÁÁÁÁÁÁÁÁÁTransID
ÁÁÁÁÁÁÁÁÁÁTRANS_ID
ÁÁÁÁÁÁÁÁNum
ÁÁÁÁÁÁ10ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁTransaction ID of call (assigned internally)ÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
AppID
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
APP_ID
ÁÁÁÁÁÁÁÁÁÁÁÁ
Num
ÁÁÁÁÁÁÁÁÁ
5
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ID number of application, established inSMT menu 17.2ÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
Act
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ACTIVITY
ÁÁÁÁÁÁÁÁÁÁÁÁ
Num
ÁÁÁÁÁÁÁÁÁ
3
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Type of activitya
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Node ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
NODE ÁÁÁÁÁÁÁÁÁÁÁÁ
Num ÁÁÁÁÁÁÁÁÁ
4ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of the node involved in the NameNet transmission
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
SerialNo ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
SERIAL_NOÁÁÁÁÁÁÁÁÁÁÁÁ
CharÁÁÁÁÁÁÁÁÁ
10ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Serial number of the node involved in theNameNet transmission
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Mailbox ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
MAILBOX ÁÁÁÁÁÁÁÁÁÁÁÁ
CharÁÁÁÁÁÁÁÁÁ
10ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of the mailbox involved in the NameNet transmission
ÁÁÁÁÁÁÁÁÁÁÁÁ
AliasÁÁÁÁÁÁÁÁÁÁ
ALIASÁÁÁÁÁÁÁÁ
CharÁÁÁÁÁÁ
10ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Alias address (if any)ÁÁÁÁÁÁÁÁÁÁÁÁName
ÁÁÁÁÁÁÁÁÁÁNAME
ÁÁÁÁÁÁÁÁChar
ÁÁÁÁÁÁ21ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁSubscriber’s nameÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁ
Sta
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
STATUS
ÁÁÁÁÁÁÁÁÁÁÁÁ
Num
ÁÁÁÁÁÁÁÁÁ
3
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Status of NameNet transmissiona
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
a Refer Table A-14.
* Available with server software at Aspen Release 3.0 or newer.
OUTPUT FILE STRUCTURES APPENDIX A
Octel PC/CDR Edition 2 A-19
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table A-14. NameNet Output File:Code Values and Descriptions.
ÁÁÁÁÁÁÁÁÁÁÁÁ
CodeValue
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Description
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ACTIVITY (Act)
ÁÁÁÁÁÁÁÁÁÁÁÁ
0 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Network-transmission side requested and then received spoken name from OctelNet, or requested mailbox spoken name received from hubaÁÁÁÁ
ÁÁÁÁÁÁÁÁ
1
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Network-receiving side received request for spoken name and then transmittedspoken name to requesterÁÁÁÁ
ÁÁÁÁÁÁÁÁ
2ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Network-transmission side requested and then received ASCII name from OctelNet, or requested mailbox ASCII name received from hubbÁÁÁÁ
ÁÁÁÁÁÁÁÁ
3ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Network-receiving side received request for ASCII name and then transmittedASCII name to requesterÁÁÁÁ
ÁÁÁÁÁÁÁÁ
20ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ASCII name mismatched and deleted permanent entry
ÁÁÁÁÁÁÁÁ
21 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
More than nine of the same name in network directory; name not added
ÁÁÁÁÁÁÁÁÁÁÁÁ
50 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Non-service-affecting alarm activated; network directory has reached directory-full-alarm threshold
ÁÁÁÁÁÁÁÁÁÁÁÁ
51 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Service-affecting alarm activated; network directory has reached critical-usagethreshold and entries will be deleted
ÁÁÁÁÁÁÁÁ
52 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Network directory is fullÁÁÁÁÁÁÁÁ
70c ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Performed name confirmation on transmission sideÁÁÁÁÁÁÁÁ71c
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁPerformed name confirmation on receiving sideÁÁÁÁ
ÁÁÁÁÁÁÁÁ
99ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Unable to identify ACTIVITY code
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
STATUS (Sta)ÁÁÁÁÁÁÁÁ
0ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Successful transmission or receiptÁÁÁÁÁÁÁÁ1
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁMailbox type is not allowed in network directoryÁÁÁÁ
ÁÁÁÁÁÁÁÁ
2ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Mailbox does not exist
ÁÁÁÁÁÁÁÁ
5 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Spoken name is not recorded
ÁÁÁÁÁÁÁÁ
8 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Spoken name is corruptedÁÁÁÁÁÁÁÁ
9ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Name added to network directoryÁÁÁÁÁÁÁÁ11
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁMore than nine of the same name in network directory; name not addedÁÁÁÁ
ÁÁÁÁÁÁÁÁ
12ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Unable to update network directory
ÁÁÁÁÁÁÁÁ
14 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Server is full
ÁÁÁÁÁÁÁÁ
99 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Unable to identify STATUS codeÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
a “or requested mailbox spoken name received from hub” applies only when server software is at AspenRelease 4.1, Aria 1.1, or newer.
b “or requested mailbox ASCII name received from hub” applies only when server software is at Aspen Release4.1, Aria 1.1, or newer.
c Appears only when server software is at Aspen Release 4.0 or newer.
OUTPUT FILE STRUCTURESAPPENDIX A
A-20 Edition 2 Octel PC/CDR
A.8 PROFILE-CHANGE-DETAILS OUTPUT FILESTRUCTURE
The profile-change-details output (PRO) file* contains information about systemprofiles that were added, deleted, initialized, and modified. The conventionRyymmdd.ASC or Ryymmdd.DBF is used to name PRO files. Table A-15 definesthe file structure. Table A-16 lists code values and descriptions, grouped by thefields that log the codes.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table A-15. Profile-Change-Details Output File Structure.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Octel PC/CDRField Name
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
dBASE IIIField Name
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
DataType
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
FieldLength
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Description
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
SyID ÁÁÁÁÁÁÁÁÁÁ
SYSID ÁÁÁÁÁÁÁÁ
CharÁÁÁÁÁÁÁÁ
4 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Server serial number (last 4 digits)
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Prt ÁÁÁÁÁÁÁÁÁÁ
PORTID ÁÁÁÁÁÁÁÁ
CharÁÁÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Port ID used for profile changeÁÁÁÁÁÁÁÁÁÁÁÁÁÁDate
ÁÁÁÁÁÁÁÁÁÁDATE
ÁÁÁÁÁÁÁÁChar
ÁÁÁÁÁÁÁÁ6
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁDate activity took placeÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
TimeÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
TIMEÁÁÁÁÁÁÁÁÁÁÁÁ
CharÁÁÁÁÁÁÁÁÁÁÁÁ
6ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Time activity took place
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Profile ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
PROFILE ÁÁÁÁÁÁÁÁÁÁÁÁ
CharÁÁÁÁÁÁÁÁÁÁÁÁ
10 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of the profile involved in theactivity (such as mailbox, list, or nodenumber)ÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
PT
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
PROF_TYPE
ÁÁÁÁÁÁÁÁÁÁÁÁ
Num
ÁÁÁÁÁÁÁÁÁÁÁÁ
2
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Type of profile involved in the activitya
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AC ÁÁÁÁÁÁÁÁÁÁ
ACTIVITY ÁÁÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁ
2 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Type of activity that took placea
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁAT
ÁÁÁÁÁÁÁÁÁÁACTION
ÁÁÁÁÁÁÁÁNum
ÁÁÁÁÁÁÁÁ2
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁType of action that took placea
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
WHÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
WHOÁÁÁÁÁÁÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁÁÁÁÁ
2ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Identification of person or task makingchangea
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ListNumÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
LIST_NUMÁÁÁÁÁÁÁÁÁÁÁÁ
CharÁÁÁÁÁÁÁÁÁÁÁÁ
10ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
List number, if LIST_CHG event
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
PW ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
PW_TYPE ÁÁÁÁÁÁÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁÁÁÁÁ
2 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Password type changed, if passwordchange eventa
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
PL ÁÁÁÁÁÁÁÁÁÁ
PW_LEN ÁÁÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁ
2 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Length of new passwordÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
a Refer to Table A-16.
* Available with server software at Aspen Release 2.0 or newer.
OUTPUT FILE STRUCTURES APPENDIX A
Octel PC/CDR Edition 2 A-21
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table A-16. Profile-Change-Details Output File:Code Values and Descriptions.
ÁÁÁÁÁÁÁÁÁÁÁÁ
Code ValueÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
DescriptionÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ACTION (AT)
ÁÁÁÁÁÁÁÁÁÁÁÁ
0 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Password changed to new valueÁÁÁÁÁÁÁÁÁÁÁÁ
1 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Password changed to old valueÁÁÁÁÁÁÁÁÁÁÁÁ
2 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Standard greeting changed to personalÁÁÁÁÁÁÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Personal greeting changed to standard
ÁÁÁÁÁÁÁÁÁÁÁÁ
4 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Personal greeting changed to personal
ÁÁÁÁÁÁÁÁÁÁÁÁ
5 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Mailbox initialized
ÁÁÁÁÁÁÁÁÁÁÁÁ
6 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Any other mailbox-profile actionÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
99ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Unable to identify the ACTION codeÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ACTIVITY (AC) ÁÁÁÁÁÁÁÁÁÁÁÁ
0 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AddÁÁÁÁÁÁÁÁÁÁÁÁ
1 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
DeleteÁÁÁÁÁÁÁÁÁÁÁÁ
2 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ModifyÁÁÁÁÁÁÁÁÁÁÁÁ
10 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Message sent to listÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
PROF_TYPE (PT)
ÁÁÁÁÁÁÁÁÁÁÁÁ
0 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Subscriber mailbox
ÁÁÁÁÁÁÁÁÁÁÁÁ
1 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Node profile
ÁÁÁÁÁÁ2 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁCommunity profileÁÁÁÁÁÁÁÁÁÁÁÁ3
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁCluster tableÁÁÁÁÁÁ
ÁÁÁÁÁÁ4ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁCaller’s menuÁÁÁÁÁÁ
ÁÁÁÁÁÁ20
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
System listÁÁÁÁÁÁÁÁÁÁÁÁ
21ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Personal listÁÁÁÁÁÁÁÁÁÁÁÁ
22 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Information listÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
PW_TYPE (PW)
ÁÁÁÁÁÁÁÁÁÁÁÁ
0 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
SubscriberÁÁÁÁÁÁÁÁÁÁÁÁ
1 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Secretary
ÁÁÁÁÁÁÁÁÁÁÁÁ
2 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Home
ÁÁÁÁÁÁÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Guest 1
ÁÁÁÁÁÁÁÁÁÁÁÁ
4 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Guest 2ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
99ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Password not changed, or unable to identify the PW_TYPE code
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
WHO (WH) ÁÁÁÁÁÁÁÁÁÁÁÁ
0ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
System managerÁÁÁÁÁÁÁÁÁÁÁÁ
1 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CSAÁÁÁÁÁÁÁÁÁÁÁÁ
2 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Garbage collectÁÁÁÁÁÁÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Purge taskÁÁÁÁÁÁÁÁÁÁÁÁ
4 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
User
ÁÁÁÁÁÁÁÁÁÁÁÁ
99 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Unable to identify the WHO code
OUTPUT FILE STRUCTURESAPPENDIX A
A-22 Edition 2 Octel PC/CDR
A.9 SESSION-DETAIL OUTPUT FILE STRUCTURE
The session-detail output (SDO) file contains records for each call session. Theconvention Byymmdd.ASC or Byymmdd.DBF is used for naming session-detailoutput files. Table A-17 defines the file structure.
Some fields log codes that can be used to interpret the call session. Table A-18lists code values and descriptions, grouped by the fields that log the codes.
The term tree, as used in this appendix, refers to the software that provides aninterface between a caller and the server. For example, open trees is the entrypoint that a caller reaches on the server. From open trees, callers dial an exten-sion to be transferred or identify themselves as subscribers by pressing the # key.
Cumulative duration for a specific mailbox on a session-detail report is less thanthe overall duration given in a system-manager report (obtained throughsystem-manager menu 14), because each report measures the start and end of asession from a different point. The two types of system-manager reports thatindicate duration are the Individual Subscriber Usage Report and the ShortForm Subscriber Statistics Report. Octel PC/CDR reports do not indicate thetime required to establish the port connection and log into a mailbox, butsystem-manager reports include this information in duration calculations.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table A-17. Session-Detail Output File Structure.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Octel PC/CDR Field
Name
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
dBASE IIIField Name
ÁÁÁÁÁÁÁÁÁÁÁÁ
DataType
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
FieldLength
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Description
ÁÁÁÁÁÁÁÁÁÁ
SyID ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
SYSID ÁÁÁÁÁÁCharÁÁÁÁÁÁÁÁ
4ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Server serial number (last 4 digits)
ÁÁÁÁÁÁÁÁÁÁ
Prt ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
PORTID ÁÁÁÁÁÁCharÁÁÁÁÁÁÁÁ
3ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Port used for session
ÁÁÁÁÁÁÁÁÁÁ
Date ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
DATE ÁÁÁÁÁÁCharÁÁÁÁÁÁÁÁ
6ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Session start date (yymmdd format)
ÁÁÁÁÁÁÁÁÁÁ
Time ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
TIME ÁÁÁÁÁÁCharÁÁÁÁÁÁÁÁ
6ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Session start time (hhmmss format)
ÁÁÁÁÁÁÁÁÁÁ
Dur ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
DURATION ÁÁÁÁÁÁNumÁÁÁÁÁÁÁÁ
5ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Session duration (seconds)ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
MailboxÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
MAILBOXÁÁÁÁÁÁÁÁÁCharÁÁÁÁÁÁÁÁÁÁÁÁ
10ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Mailbox number used in sessionÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CallerÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CALLERÁÁÁÁÁÁÁÁÁÁÁÁ
CharÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
16a or24b
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Caller ID—automatic number identifi-cation or internal (PBX) integration, ifknown
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Callee ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CALLEE ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CharÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
16c,d
or32d,e
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Callee ID—dialed-number identifica-tion; telephone number from which thecall to the server was forwarded
When outcall or network outcall, contains dialed telephone numberÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
a File-format level 1, 2, 3, or 4.b File-format level 5 or higher.c File-format level 1.d When the outcall number is longer than the number of digits allowed in the CALLEE field, the excessive
leading digits are not recorded.e File-format level 2 or higher.
OUTPUT FILE STRUCTURES APPENDIX A
Octel PC/CDR Edition 2 A-23
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table A-17. Session-Detail Output File Structure (Concluded).ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Octel PC/CDR Field
Name
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
dBASE IIIField Name
ÁÁÁÁÁÁÁÁÁÁÁÁ
DataType
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
FieldLength
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Description
ÁÁÁÁÁÁÁÁÁÁ
CTÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CALLTYPEÁÁÁÁÁÁNumÁÁÁÁÁÁÁÁ
2ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Subscriber-call typef
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AS ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ACCESS-TYPE
ÁÁÁÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁÁÁÁÁ
2 or 3bÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Subscriber-access typef
ÁÁÁÁÁÁÁÁÁÁ
TC ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
TERMCODE ÁÁÁÁÁÁNumÁÁÁÁÁÁÁÁ
2ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Session-termination codef
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
DestinationÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
DEST_ORGN ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CharÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
16ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
When session ends by a transfer toanother telephone number or mailbox,contains telephone number or mailbox
When network call, contains remote-node serial number and mailbox, witha + character between the values
Under certain circumstances, such aswhen a NameNet event is generated ora network failure occurs, no value ap-pears after the + characterÁÁÁÁÁ
ÁÁÁÁÁBX
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
UNSUCXFRÁÁÁÁÁÁNumÁÁÁÁÁÁÁÁ
2ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Total number of unsuccessful transfersÁÁÁÁÁÁÁÁÁÁ
MsentÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
MSGSENTÁÁÁÁÁÁNumÁÁÁÁÁÁÁÁ
5ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Total number of messages sentÁÁÁÁÁÁÁÁÁÁ
Mdel ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
MSGDEL ÁÁÁÁÁÁNumÁÁÁÁÁÁÁÁ
5ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Total number of messages deletedÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
DTg ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
DEST_TYPEg ÁÁÁÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁÁÁÁÁ
2ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Identifies destination as mailbox or extensionf
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
TAg ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
TERM_ACTg ÁÁÁÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁÁÁÁÁ
2ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Termination action taken from callermenufÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
TransIDgÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
TRANS_IDgÁÁÁÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁÁÁÁÁ
10ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Transaction ID of call (assigned internally)ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
AppIDgÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
APP_IDgÁÁÁÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁÁÁÁÁ
5ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ID number of application establishedin SMT menu 17.2
ÁÁÁÁÁÁÁÁÁÁ
FaxMSg ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
FAX_MSg ÁÁÁÁÁÁNumÁÁÁÁÁÁÁÁ
5ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of fax messages sentÁÁÁÁÁÁÁÁÁÁ
FaxMDg ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
FAX_MDg ÁÁÁÁÁÁNumÁÁÁÁÁÁÁÁ
5ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of fax messages deletedÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
TUh ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
TUTh ÁÁÁÁÁÁÁÁÁÁÁÁ
NumÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
2ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Identifies which messaging-tutorialprompt was playedf
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
b File-format level 5 or higher.f Refer to Table A-18.g Appears only when file-format level 3 or higher is selected and the server software is at Aspen Release 2.0 or
newer.h Appears only when file-format level 6 or higher is selected and the server software is at Aria 1.2 or newer.
OUTPUT FILE STRUCTURESAPPENDIX A
A-24 Edition 2 Octel PC/CDR
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table A-18. Session-Detail Output File:Code Values and Descriptions.
ÁÁÁÁÁÁÁÁÁÁÁÁ
CodeValue
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Description
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ACCESSTYPE (AS)
ÁÁÁÁÁÁÁÁ
0 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Subscriber password access
ÁÁÁÁÁÁÁÁ
1 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Secretary password access
ÁÁÁÁÁÁÁÁ
2 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Home password access
ÁÁÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Guest 1 password access
ÁÁÁÁÁÁÁÁ
4 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Guest 2 password access
ÁÁÁÁÁÁÁÁ
5 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Unidentified caller (telephone-answering) accessÁÁÁÁÁÁÁÁ
6 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Outcalling without subscriber accessÁÁÁÁÁÁÁÁ
7a ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Visit mailboxÁÁÁÁÁÁÁÁ
8 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Voice-messaging mode—no password input. Occurs on initial entry tutorial
ÁÁÁÁÁÁÁÁ
9 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Open trees
ÁÁÁÁÁÁÁÁ
10 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Network/AMIS access—voice message transmittedÁÁÁÁÁÁÁÁ
11 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Network access—special message transmittedÁÁÁÁÁÁÁÁ
12 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Network access—copy of voice message transmittedÁÁÁÁÁÁÁÁ
13 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Failed network/AMIS transmitÁÁÁÁÁÁÁÁÁÁÁÁ
14b,cÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Network transmission side requested and then received spoken name from OctelNet or requested mailbox spoken name received from hub
ÁÁÁÁÁÁÁÁÁÁÁÁ
15b,dÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Network transmission side requested and then received ASCII name from OctelNet or requested mailbox ASCII name received from hub
ÁÁÁÁÁÁÁÁ
16e ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Hub returned information to sender
ÁÁÁÁÁÁÁÁ
20 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Network/AMIS access—voice message received
ÁÁÁÁÁÁÁÁ
21 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Network access—special message received
ÁÁÁÁÁÁÁÁ
22 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Network access—copy of voice message received
ÁÁÁÁÁÁÁÁ
23 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Failed network/AMIS receiveÁÁÁÁÁÁÁÁÁÁÁÁ
24b ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Network receiving side received request for spoken name and then transmittedspoken name to requester
ÁÁÁÁÁÁÁÁ
25b ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Network receiving side received request for ASCII name and then transmittedASCII name to requesterÁÁÁÁ
ÁÁÁÁ31ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁPager sequence 1ÁÁÁÁ
ÁÁÁÁÁÁÁÁ
32ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Pager sequence 2
ÁÁÁÁÁÁÁÁ
33 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Pager sequence 3
ÁÁÁÁÁÁÁÁ
34a ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Pager sequence 4
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
a Appears only when server software is at Aspen Release 1.5 or newer.b Appears only when server software is at Aspen Release 4.0 or newer.c “or requested mailbox spoken name received from hub” applies only when server software is at Aspen
Release 4.1, Aria 1.1, or newer.d “or requested mailbox ASCII name received from hub” applies only when server software is at Aspen
Release 4.1, Aria 1.1, or newer.e Appears only when server software is at Aspen Release 4.1, Aria 1.1, or newer.
OUTPUT FILE STRUCTURES APPENDIX A
Octel PC/CDR Edition 2 A-25
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table A-18. Session-Detail Output File:Code Values and Descriptions (Continued).
ÁÁÁÁÁÁÁÁÁÁÁÁ
CodeValue
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Description
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ACCESSTYPE (AS) (Concluded)
ÁÁÁÁÁÁÁÁ
35a ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Pager sequence 5
ÁÁÁÁÁÁÁÁ
36a ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Pager sequence 6
ÁÁÁÁÁÁÁÁ
37 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Pager sequence 7
ÁÁÁÁÁÁÁÁ
38 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Pager sequence 8
ÁÁÁÁÁÁÁÁ
39 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Pager sequence 9
ÁÁÁÁÁÁÁÁ
40 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Pager sequence 10ÁÁÁÁÁÁÁÁ
41 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Pager sequence 11ÁÁÁÁÁÁÁÁ
42 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Pager sequence 12ÁÁÁÁÁÁÁÁ
43 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Pager sequence 13ÁÁÁÁÁÁÁÁ
44 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Pager sequence 14
ÁÁÁÁÁÁÁÁ
45ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Pager sequence 15ÁÁÁÁÁÁÁÁ
46ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Pager sequence 16ÁÁÁÁÁÁÁÁ
47 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Pager sequence 17ÁÁÁÁÁÁÁÁ
48 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Pager sequence 18ÁÁÁÁÁÁÁÁ
49 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Pager sequence 19ÁÁÁÁÁÁÁÁ91
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁServer initial program load (IPL)ÁÁÁÁ
ÁÁÁÁ92ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁServer date/time setÁÁÁÁ
ÁÁÁÁ99ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁUnable to identify the ACCESSTYPE codeÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CALLTYPE (CT)
ÁÁÁÁÁÁÁÁ
0 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Call to the server’s direct number from an outside callerÁÁÁÁÁÁÁÁ
1 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Direct call to the server from inside the PBXÁÁÁÁÁÁÁÁ
2 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Direct call to the server from attendantÁÁÁÁÁÁÁÁ
3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Forwarded callf to the server from busy station numberÁÁÁÁÁÁÁÁÁÁÁÁ
4 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Forwarded callf to the server from ring-no-answer, or indicates an incomingcall on DID for in-band integration
ÁÁÁÁÁÁÁÁ
5g ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Outcall from the serverÁÁÁÁÁÁÁÁ
6 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Outgoing network call from the serverÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
a Appears only when server software is at Aspen Release 1.5 or newer.f On some PBX integrations, either call-type code 3 or 4 can indicate that the call was forwarded under the
forward-all-calls status.g Appears only when server software is older than Aspen Release 2.0.
OUTPUT FILE STRUCTURESAPPENDIX A
A-26 Edition 2 Octel PC/CDR
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table A-18. Session-Detail Output File:Code Values and Descriptions (Continued).
ÁÁÁÁÁÁÁÁÁÁÁÁ
CodeValue
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Description
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CALLTYPE (CT) (Concluded)
ÁÁÁÁÁÁÁÁ
7 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Incoming network call from the server
ÁÁÁÁÁÁÁÁ
8g ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Pager outcall
ÁÁÁÁÁÁÁÁ
9g ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS outgoing call
ÁÁÁÁÁÁÁÁ
10 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS incoming call
ÁÁÁÁÁÁÁÁ
11h ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Administered AMIS outgoing call
ÁÁÁÁÁÁÁÁ
12h ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Administered AMIS incoming callÁÁÁÁÁÁÁÁ
25i ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Forward all callsÁÁÁÁÁÁÁÁ
30i ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Outcall on PBXÁÁÁÁÁÁÁÁ
31i ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Local outcallÁÁÁÁÁÁÁÁ
32i ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Local-area-code outcall
ÁÁÁÁÁÁÁÁ
33iÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Long-distance outcallÁÁÁÁÁÁÁÁ
40i ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Pager outcall on PBXÁÁÁÁÁÁÁÁ
41i ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Local pager outcallÁÁÁÁÁÁÁÁ
42i ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Local-long-distance pager outcallÁÁÁÁÁÁÁÁ
43i ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Long-distance pager outcallÁÁÁÁÁÁÁÁ50i
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁLocal AMIS outcallÁÁÁÁ
ÁÁÁÁ51iÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁLong-distance AMIS outcallÁÁÁÁ
ÁÁÁÁ52iÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁInternational AMIS outcallÁÁÁÁ
ÁÁÁÁ53iÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁPrivate-number AMIS outcallÁÁÁÁ
ÁÁÁÁÁÁÁÁ
59iÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Unknown AMIS outcall
ÁÁÁÁÁÁÁÁ
90 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Server-event-call set date and time (DTS), initial program load (IPL)
ÁÁÁÁÁÁÁÁ
99 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Unable to identify the CALLTYPE code
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
DEST_TYPE (DT)j ÁÁÁÁÁÁÁÁ0
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁMailbox numberÁÁÁÁ
ÁÁÁÁ1ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁExtension numberÁÁÁÁ
ÁÁÁÁ99ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
No destination typeÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
g Appears only when server software is older than Aspen Release 2.0.h Appears only when file-format level 6 or higher is selected and server software is at Aria 1.2 or newer.i Appears only when server software is at Aspen Release 2.0 or newer.j Appears only when file-format 3 or higher is selected and the server software is at Aspen Release 2.0 or
newer.
OUTPUT FILE STRUCTURES APPENDIX A
Octel PC/CDR Edition 2 A-27
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table A-18. Session-Detail Output File:Code Values and Descriptions (Continued).
ÁÁÁÁÁÁÁÁÁÁÁÁ
CodeValue
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Description
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
TERM_ACT (TA)j ÁÁÁÁÁÁÁÁ0
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁCaller pressed 0ÁÁÁÁ
ÁÁÁÁ1ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁCaller pressed 1ÁÁÁÁ
ÁÁÁÁ2ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Caller pressed 2ÁÁÁÁÁÁÁÁ
3ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Caller pressed 3ÁÁÁÁÁÁÁÁÁÁÁÁ
4ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Caller pressed 4
ÁÁÁÁÁÁÁÁ
5 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Caller pressed 5
ÁÁÁÁÁÁÁÁ
6 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Caller pressed 6
ÁÁÁÁÁÁÁÁ
7 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Caller pressed 7
ÁÁÁÁÁÁÁÁ
8 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Caller pressed 8
ÁÁÁÁÁÁÁÁ
9 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Caller pressed 9
ÁÁÁÁÁÁÁÁ
10ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Caller pressed the star keyÁÁÁÁÁÁÁÁ
11 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Caller pressed the pound keyÁÁÁÁÁÁÁÁ
12 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Caller timed outÁÁÁÁÁÁÁÁ
13 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Caller hung upÁÁÁÁÁÁÁÁÁÁÁÁ
14 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Caller entered a name for dial-by-name
ÁÁÁÁÁÁÁÁ
15 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Caller entered a mailbox or extension number
ÁÁÁÁÁÁÁÁ
99 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
No termination action
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
TERMCODE (TC) ÁÁÁÁÁÁÁÁ0
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁCaller hung up or was disconnectedÁÁÁÁ
ÁÁÁÁ1ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁCaller routed to a different mailboxÁÁÁÁ
ÁÁÁÁ2ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁCaller transferred to an attendant from a mailbox by pressing the 0 keyÁÁÁÁ
ÁÁÁÁÁÁÁÁ
3ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Caller transferred to an extension from an ECP mailbox or auto attendant orby dialing the number
ÁÁÁÁÁÁÁÁÁÁÁÁ
4 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Incoming call determined to be a network incoming call
ÁÁÁÁÁÁÁÁ
5 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Caller exited mailbox, was still connected to server, and then entered anothermailboxÁÁÁÁ
ÁÁÁÁÁÁÁÁ
6ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Caller exited mailbox, was still connected to server (open system), but disconnected
ÁÁÁÁÁÁÁÁ
7 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Incoming call determined to be an AMIS network incoming callÁÁÁÁÁÁÁÁ
8b ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Caller transferred to message senderÁÁÁÁÁÁÁÁÁÁÁÁ
10 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Outcall or network outcallk unsuccessful because of busy line (includes pageroutcalls
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
b Appears only when server software is at Aspen Release 4.0 or newer.j Appears only when file-format 3 or higher is selected and the server software is at Aspen Release 2.0 or
newer.k “network outcall” applies only when server software is at Release 4.1, Aria 1.1, or newer.
OUTPUT FILE STRUCTURESAPPENDIX A
A-28 Edition 2 Octel PC/CDR
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table A-18. Session-Detail Output File:Code Values and Descriptions (Continued).
ÁÁÁÁÁÁÁÁÁÁÁÁ
CodeValue
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Description
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
TERMCODE (TC) (Continued)
ÁÁÁÁÁÁÁÁÁÁÁÁ
11 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Outcall or network outcallk unsuccessful, ring-no-answer line (includes pager outcalls)ÁÁÁÁ
ÁÁÁÁ12ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁOutcall unsuccessful, fast-busy line (includes pager outcalls)ÁÁÁÁ
ÁÁÁÁÁÁÁÁ
19bÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Successful network-message transmission, message received by mailbox withextended-absence greeting
ÁÁÁÁÁÁÁÁÁÁÁÁ
20ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Successful network-message transmission, including original voice-messagecopy and NameNet name
ÁÁÁÁÁÁÁÁÁÁÁÁ
22 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Unsuccessful network-message transmission, other network-transmission errors occurred
ÁÁÁÁÁÁÁÁÁÁÁÁ
23 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Unsuccessful network-message transmission, mailbox not found on destina-tion server
ÁÁÁÁÁÁÁÁÁÁÁÁ
24 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Unsuccessful network-message transmission, wrong mailbox type on destination serverÁÁÁÁ
ÁÁÁÁÁÁÁÁ
25ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Unsuccessful network-message transmission, mailbox on destination serverfullÁÁÁÁ
ÁÁÁÁÁÁÁÁ
26ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Unsuccessful network-message transmission, mailbox future-delivery on destination server full
ÁÁÁÁÁÁÁÁ
27 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Unsuccessful network-message transmission, destination server fullÁÁÁÁÁÁÁÁÁÁÁÁ
28ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Unsuccessful network-message transmission, possible bad message transmitted
ÁÁÁÁÁÁÁÁ
29 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Unsuccessful network-message transmission, message determined badÁÁÁÁÁÁÁÁ
30 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Network-message-transmission call terminated at request of system managerÁÁÁÁÁÁÁÁ
31 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Network-message-transmission call terminated, low signal measurementÁÁÁÁÁÁÁÁ
32 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Network-message-transmission call terminated, low signal-to-noise ratioÁÁÁÁÁÁÁÁ33
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁNetwork-message-transmission call terminated, other line problemsÁÁÁÁ
ÁÁÁÁ34ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁNetwork-message-transmission call terminated at the request of other serversÁÁÁÁ
ÁÁÁÁÁÁÁÁ
35ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Network-message-transmission call terminated, server error (for example, server is full)
ÁÁÁÁÁÁÁÁ
40 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS message retry and transmit laterÁÁÁÁÁÁÁÁ
41 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS version not supportedÁÁÁÁÁÁÁÁ42
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁAMIS message invalid responseÁÁÁÁ
ÁÁÁÁ43ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁAMIS system telephone number blocked by transmission-acceptance tableÁÁÁÁ
ÁÁÁÁ44ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁNo AMIS system telephone number in SMTÁÁÁÁ
ÁÁÁÁ45ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁAMIS system telephone number in SMT incorrectÁÁÁÁ
ÁÁÁÁÁÁÁÁ
46ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS end-of-session failed because of timeout, frame error, protocol error, orabort
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
b Appears only when server software is at Aspen Release 4.0 or newer.k “network outcall” applies only when server software is at Aspen Release 4.1, Aria 1.1, or newer.
OUTPUT FILE STRUCTURES APPENDIX A
Octel PC/CDR Edition 2 A-29
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table A-18. Session-Detail Output File:Code Values and Descriptions (Continued).
ÁÁÁÁÁÁÁÁÁÁÁÁ
CodeValue
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Description
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
TERMCODE (TC) (Continued)
ÁÁÁÁÁÁÁÁ
47 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS invalid system telephone number (country-code error, not pound-terminated, did not contain three pound signs, or data-length error)ÁÁÁÁ
ÁÁÁÁ48ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁAMIS system internal errorÁÁÁÁ
ÁÁÁÁÁÁÁÁ
49ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS receive-message error (message-record initial error, message-record error, or end-message error)
ÁÁÁÁÁÁÁÁ
50 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS message returned to senderÁÁÁÁÁÁÁÁÁÁÁÁ
51 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS receiving START frame errorÁÁÁÁÁÁÁÁ52
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁAMIS receiving PHNUM (phone number) frame errorÁÁÁÁ
ÁÁÁÁ53ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁAMIS MSGI (message information) frame errorÁÁÁÁ
ÁÁÁÁ54ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁAMIS protocol errorÁÁÁÁ
ÁÁÁÁÁÁÁÁ
60lÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Unsuccessful network-message transmission, message blocked by receivingmailbox
ÁÁÁÁÁÁÁÁÁÁÁÁ
61b ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Unsuccessful network-message transmission, fax protocol timeout, nothingtransmitted
ÁÁÁÁÁÁÁÁÁÁÁÁ
62bÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Unsuccessful network-message transmission, fax protocol timeout, partial faxtransmitted
ÁÁÁÁÁÁÁÁ
63b ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Unsuccessful network-message transmission, bad fax imageÁÁÁÁÁÁÁÁ
64l ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Unsuccessful network-message transmission, bad message driveÁÁÁÁÁÁÁÁÁÁÁÁ
65l ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Unsuccessful network-message transmission, NameNet and ASCII name mismatch
ÁÁÁÁÁÁÁÁ
66e ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Node deleted
ÁÁÁÁÁÁÁÁ
67e ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Node disabled, with request to return all messagesÁÁÁÁÁÁÁÁ
68e ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Continuous bad lineÁÁÁÁÁÁÁÁ
69e ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Receiving mailbox not capable of receiving faxesÁÁÁÁÁÁÁÁ
70l ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Mailbox type not allowed in network directoryÁÁÁÁÁÁÁÁ
71l ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Spoken name not recorded
ÁÁÁÁÁÁÁÁ
72lÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Spoken name corruptedÁÁÁÁÁÁÁÁ
73lÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Unable to update network directoryÁÁÁÁÁÁÁÁ
81 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Caller enters one bad password and server terminates the callÁÁÁÁÁÁÁÁ
82 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Caller enters two bad passwords and server terminates the callÁÁÁÁÁÁÁÁ
83 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Caller enters three bad passwords and server terminates the callÁÁÁÁÁÁÁÁ85e
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁReceiving port not capable of receiving faxesÁÁÁÁ
ÁÁÁÁ86eÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁReceiving node not capable of receiving faxesÁÁÁÁ
ÁÁÁÁÁÁÁÁ
87eÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Transmission port not capable of receiving faxesÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
b Appears only when server software is at Aspen Release 4.0 or newer.e Appears only when server software is at Aspen Release 4.1, Aria 1.1, or newer.l Appears only when server software is at Aspen Release 3.0 or newer.
OUTPUT FILE STRUCTURESAPPENDIX A
A-30 Edition 2 Octel PC/CDR
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table A-18. Session-Detail Output File:Code Values and Descriptions (Continued).
ÁÁÁÁÁÁÁÁÁÁÁÁ
CodeValue
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Description
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
TERMCODE (TC) (Concluded)
ÁÁÁÁÁÁÁÁ
88e ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Hub synchronization problem
ÁÁÁÁÁÁÁÁ
91 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Session terminated by server initial program load (IPL)
ÁÁÁÁÁÁÁÁ
92 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Session terminated by server reset scanner channel
ÁÁÁÁÁÁÁÁ
93 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Session terminated by server trees restart
ÁÁÁÁÁÁÁÁ
94 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
IPL power failure
ÁÁÁÁÁÁÁÁ
95 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
IPL server crashÁÁÁÁÁÁÁÁ
96 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
IPL parity errorÁÁÁÁÁÁÁÁ
97 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Set date and time (DTS), bad clock setting after system bootÁÁÁÁÁÁÁÁ
98 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
IPL system manager shutdown or DTS new installation/clock setÁÁÁÁÁÁÁÁ
99 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Unable to identify the TERMCODE code
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
TUT (TU)h ÁÁÁÁÁÁÁÁ1
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁSend prompt playedÁÁÁÁ
ÁÁÁÁ2ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁReply prompt playedÁÁÁÁ
ÁÁÁÁ99ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁNot applicableÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
e Appears only when server software is at Aspen Release 4.1, Aria 1.1, or newer.h Appears only when file-format 6 or higher is selected and the server software is at Aria 1.2 or newer.
OUTPUT FILE STRUCTURES APPENDIX A
Octel PC/CDR Edition 2 A-31
A.10 UNSUCCESSFUL-TRANSFER OUTPUT FILESTRUCTURE
The unsuccessful-transfer output (UTO) file contains one record for everyoccurrence of an unsuccessful transfer. The convention Xyymmdd.ASC orXyymmdd.DBF is used to name unsuccessful-transfer output files. Table A-19shows the file structure. Table A-20 lists code values and describes why anattempted transfer was unsuccessful.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table A-19. Unsuccessful-Transfer Output File Structure.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Octel PC/CDR Field
Name
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
dBASE IIIField Name
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
DataType
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
FieldLength
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Description
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
SyIDÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
SYSIDÁÁÁÁÁÁÁÁÁÁÁÁ
CharÁÁÁÁÁÁÁÁÁ
4ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Server serial number (last 4 digits)
ÁÁÁÁÁÁPrt ÁÁÁÁÁÁPORTID ÁÁÁÁChar ÁÁÁ3ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁPort used for sessionÁÁÁÁÁÁÁÁÁÁÁÁDate
ÁÁÁÁÁÁÁÁÁÁÁÁXFRDATE
ÁÁÁÁÁÁÁÁChar
ÁÁÁÁÁÁ6ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁDate of occurrence (yymmdd format)ÁÁÁÁÁÁ
ÁÁÁÁÁÁTime
ÁÁÁÁÁÁÁÁÁÁÁÁ
XFRTIMEÁÁÁÁÁÁÁÁ
CharÁÁÁÁÁÁ
6ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Time of occurrence (hhmmss format)ÁÁÁÁÁÁÁÁÁÁÁÁ
Mailbox ÁÁÁÁÁÁÁÁÁÁÁÁ
MAILBOX ÁÁÁÁÁÁÁÁ
Char ÁÁÁÁÁÁ
10ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Number of mailbox attempting transferÁÁÁÁÁÁÁÁÁÁÁÁ
RC ÁÁÁÁÁÁÁÁÁÁÁÁ
REASON ÁÁÁÁÁÁÁÁ
Num ÁÁÁÁÁÁ
2ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Unsuccessful transfer codea
ÁÁÁÁÁÁÁÁÁÁÁÁ
TnTried ÁÁÁÁÁÁÁÁÁÁÁÁ
TN_TRIED ÁÁÁÁÁÁÁÁ
Char ÁÁÁÁÁÁ
16ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Attempted telephone number
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
a Refer to Table A-20.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table A-20. Unsuccessful-Transfer Output File:Code Values and Descriptions.
ÁÁÁÁÁÁÁÁÁÁÁÁ
CodeValue
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Description
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
REASON (RC) ÁÁÁÁÁÁÁÁÁÁÁÁ
2ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
BusyÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ3 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁNot answeredÁÁÁÁ
ÁÁÁÁ4ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁFast-busy or extension not in serviceÁÁÁÁ
ÁÁÁÁ5ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Transfer answered by serverÁÁÁÁÁÁÁÁ
8aÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Operator transfer, telephone number busyÁÁÁÁÁÁÁÁ
9aÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Operator transfer, telephone number not answeredÁÁÁÁÁÁÁÁ
10aÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Operator transfer, telephone number fast-busy
ÁÁÁÁÁÁÁÁ
11aÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Operator transfer, telephone number detected, answered by server
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
a Appears only when server software release is older than Aspen Release 2.0.
A P P E N D I X B
Octel PC/CDR Edition 2 B-1
CDR EVENT DESCRIPTIONS
CDR events, as contained in the collated day file (CDF), are described in thisappendix. The server software release and the record groups selected in SMTmenu 16.1.4 determine which CDR events are captured and recorded in theCDR buffer and then processed into binary collection files (BCFs) and CDFs.
The related port number (when applicable), date, and time the call started arecontained in the CDF as part of the header information for each call. For example,
The header for a series of events occurring on port 03C reads
CALL ON PORT 03C AT 06-27-96 04:41:14
Events within the call are listed chronologically on the following lines, beginningwith the time the event began. The estimated number of bytes contained in theevent (in parenthesis) and the event fields follow the event name. For example,
The first event listed for the call on port 03C reads
04:41:14 IC (011) TransID: 1472676
In the BCF, the date, time, and port number are displayed before the name ofthe event. The estimated number of bytes contained in the event (in parenthesis)and the event fields follow the event name. The port number is in the field calledP:. For example,
The first line of an ON_HOOK event on port 02E reads
06-27-96 04:45:20 P:02E ON_HOOK (011) TransID: 149282
Within this appendix, the term AMIS refers to the intervendor network protocol,and the term OctelNet refers to Octel’s proprietary network protocol. Referencesto port 255 refer to system events unrelated to ports on the server.
The term tree, as used in this appendix, refers to the software that provides aninterface between a caller and the server. For example, open trees is the entrypoint that a caller reaches after calling the server. From open trees, callers thendial an extension to be transferred to or identify themselves as subscribers bypressing the # key.
Table B-1 is an alphabetical list of the event names and their correspondingcodes and descriptions. Table B-2 is a numerical list of event codes and theircorresponding names and descriptions. Table B-3 shows the details of eachevent.
Field names for CDR events displayed using the Online CDR feature (availablewith software at Aspen Release 4.1, Octel Aria 1.1, and newer voice messagingsoftware) are similar to the field names shown in Table B-3.
CDR EVENT DESCRIPTIONSAPPENDIX B
B-2 Edition 2 Octel PC/CDR
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table B-1. Events Alphabetized by Event Name.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Event NameÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
EventCode
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Event Description
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_DIR_FULLÁÁÁÁÁÁÁÁÁÁ
170ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS directory 90% fullÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_EAR_FULL ÁÁÁÁÁÁÁÁÁÁ
171 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS EAR (extended-address-record) array 90% fullÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_RCV_EOS ÁÁÁÁÁÁÁÁÁÁ
164 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
End-of-AMIS session receivedÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_RCV_FCa ÁÁÁÁÁÁÁÁÁÁ
155 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS function code receivedÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_RCV_FRa ÁÁÁÁÁÁÁÁÁÁ
157 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Status of received AMIS frame
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_RCV_IC ÁÁÁÁÁÁÁÁÁÁ
162 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Incoming AMIS callÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_RCV_INVPHÁÁÁÁÁÁÁÁÁÁ
163 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Invalid AMIS system-access telephone number receivedÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_RCV_MSG ÁÁÁÁÁÁÁÁÁÁ
161 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS message-recording status received
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_RCV_MSGIÁÁÁÁÁÁÁÁÁÁ
160 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS message attribute received
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_RCV_PHNUMÁÁÁÁÁÁÁÁÁÁ
159 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Caller’s AMIS system-access telephone number
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_RCV_RESPaÁÁÁÁÁÁÁÁÁÁ
156 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Acknowledgment sent for AMIS-received frameÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_RCV_STARTÁÁÁÁÁÁÁÁÁÁ
158 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS start session received
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_RTS ÁÁÁÁÁÁÁÁÁÁ
166 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS message returned to sender
ÁÁÁÁÁÁÁAM_SEND ÁÁÁÁÁ165 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁAMIS message queuedÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_XMT_EOMÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
146ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
End-of-AMIS message frame transmitted
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_XMT_EOS ÁÁÁÁÁÁÁÁÁÁ
147 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
End-of-AMIS session transmitted
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_XMT_MBOXÁÁÁÁÁÁÁÁÁÁ
144 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS logged bad sender’s mailbox number
ÁÁÁÁÁÁÁAM_XMT_MINFOÁÁÁÁÁ143 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁAMIS-message information transmittedÁÁÁÁÁÁÁÁÁÁÁÁÁÁAM_XMT_OC
ÁÁÁÁÁÁÁÁÁÁ140
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁStart of AMIS outcallÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_XMT_PHNUMÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
142ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS server telephone number transmitted
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_XMT_RESPaÁÁÁÁÁÁÁÁÁÁ
148 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Acknowledgment received from server
ÁÁÁÁÁÁÁAM_XMT_STARTÁÁÁÁÁ141 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁAMIS start session transmittedÁÁÁÁÁÁÁÁÁÁÁÁÁÁAM_XMT_VOICE
ÁÁÁÁÁÁÁÁÁÁ145
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁAMIS transmitted voiceÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁBN_EOS
ÁÁÁÁÁÁÁÁÁÁ
89ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
OctelNet end of sessionÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
BN_IC ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
65 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Incoming call from OctelNet nodeÁÁÁÁÁÁÁÁÁÁÁÁÁÁBN_MULTILINE
ÁÁÁÁÁÁÁÁÁÁ66
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁReserved for future useÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁBN_OCÁÁÁÁÁÁÁÁÁÁ64
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁOutcall to an OctelNet nodeÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁBN_RCV_CP
ÁÁÁÁÁÁÁÁÁÁ
83ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
OctelNet message copy receivedÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
BN_RCV_HDR ÁÁÁÁÁÁÁÁÁÁ
81 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
OctelNet message header receivedÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
BN_RCV_SP ÁÁÁÁÁÁÁÁÁÁ
82 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
OctelNet special message receivedÁÁÁÁÁÁÁÁÁÁÁÁÁÁBN_RCV_START
ÁÁÁÁÁÁÁÁÁÁ80
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁOctelNet receive mode startedÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁBN_RCV_VOICE
ÁÁÁÁÁÁÁÁÁÁ
84ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
OctelNet message receivedÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
BN_RTS ÁÁÁÁÁÁÁÁÁÁ
90 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
OctelNet message returned to senderÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
BN_XMT_CP ÁÁÁÁÁÁÁÁÁÁ
73 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
OctelNet message copy transmittedÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
BN_XMT_HDR ÁÁÁÁÁÁÁÁÁÁ
71 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
OctelNet message header transmitted
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
BN_XMT_SPÁÁÁÁÁÁÁÁÁÁ
72ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
OctelNet special message transmittedÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
BN_XMT_STARTÁÁÁÁÁÁÁÁÁÁ
70 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
OctelNet transmit mode startedÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
BN_XMT_VOICEÁÁÁÁÁÁÁÁÁÁ
74 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
OctelNet message transmittedÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CALLER ÁÁÁÁÁÁÁÁÁÁ
16 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Caller identification
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
a Appears only when certain service-related functions are performed.
CDR EVENT DESCRIPTIONS APPENDIX B
Octel PC/CDR Edition 2 B-3
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table B-1. Events Alphabetized by Event Name (Continued).
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Event NameÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
EventCode
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Event Description
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CALLMNUbÁÁÁÁÁÁÁÁÁÁ
94ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Caller’s menu eventÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CDRCFG ÁÁÁÁÁÁÁÁÁÁ
2 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CDR configurationÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CNN_ENABLE ÁÁÁÁÁÁÁÁÁÁ
172 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Reserved for future applicationsÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CNN_OCL_MB ÁÁÁÁÁÁÁÁÁÁ
175 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Reserved for future applicationsÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CNN_OCL_VM ÁÁÁÁÁÁÁÁÁÁ
174 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Reserved for future applications
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CNN_PRIVACY ÁÁÁÁÁÁÁÁÁÁ
178 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Reserved for future applicationsÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CNN_VC_LINK ÁÁÁÁÁÁÁÁÁÁ
173 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Reserved for future applicationsÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
DISK_USGb ÁÁÁÁÁÁÁÁÁÁ
91 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Disk-usage event
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
DM_PSEUDOb ÁÁÁÁÁÁÁÁÁÁ
198 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Missing start or end of call; for internal use only
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
DTS ÁÁÁÁÁÁÁÁÁÁ
1 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Set date and time
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
FCE ÁÁÁÁÁÁÁÁÁÁ
28 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
OctelForms mailbox end of sessionÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
FPb ÁÁÁÁÁÁÁÁÁÁ
107 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Fax image printed
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
FRb ÁÁÁÁÁÁÁÁÁÁ
106 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Fax image received
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
FRTSb ÁÁÁÁÁÁÁÁÁÁ
108 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Fax returned to sender
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
GEN_ERRc ÁÁÁÁÁÁÁÁÁÁ
118 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
General system error
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
GET_ROUTE ÁÁÁÁÁÁÁÁÁÁ
176 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Reserved for future applications
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
IC ÁÁÁÁÁÁÁÁÁÁ
17 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Incoming call
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
IPL ÁÁÁÁÁÁÁÁÁÁ
0 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Server initial program loadÁÁÁÁÁÁÁÁÁÁÁÁÁÁIVR_EXITb
ÁÁÁÁÁÁÁÁÁÁ151
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁExit IVR application detailsÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
LIST_CHGbÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
93ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Distribution lists added, modified, or deleted, or messagesent to this list
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁMD
ÁÁÁÁÁÁÁÁÁÁ49
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁMessage deletedÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁMSÁÁÁÁÁÁÁÁÁÁ48
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁMessage sentÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁMSG_CNTd
ÁÁÁÁÁÁÁÁÁÁ
116ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Message countÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
MSG_RVWd ÁÁÁÁÁÁÁÁÁÁ
117 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Message reviewÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
MW ÁÁÁÁÁÁÁÁÁÁ
18 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Message waiting set/clearÁÁÁÁÁÁÁÁÁÁÁÁÁÁNNET_ALARMe
ÁÁÁÁÁÁÁÁÁÁ102
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁNameNet-directory alarm activityÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁNNET_DIRe ÁÁÁÁÁ
ÁÁÁÁÁ101ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
NameNet-directory mismatch or nine of same name existÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
NNET_NAMEe ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
100 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
NameNet-transmission or receipt of ASCII or spokenname
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
OC ÁÁÁÁÁÁÁÁÁÁ
19 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Outcall to subscriber, pager, or fax
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
OCL_NAME ÁÁÁÁÁÁÁÁÁÁ
177 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Reserved for future applications
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ON_HOOK ÁÁÁÁÁÁÁÁÁÁ
20 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Port goes on hookÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
PORTS_BUSYb ÁÁÁÁÁÁÁÁÁÁ
95 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
All ports busy
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
PROFILE_CHGbÁÁÁÁÁÁÁÁÁÁ
97 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Mailbox profile changed
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
PWT ÁÁÁÁÁÁÁÁÁÁ
21 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Password testÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
PWT_RJCTÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
129ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Bad-password limitÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
b Appears only when server software is at Aspen Release 2.0 or newer.c Appears only when server software is at Aria 1.2 or newer.d Appears only when server software is at Aspen Release 4.1, Aria 1.1, or newer.e Appears only when server software is at Aspen Release 3.0 or newer.
CDR EVENT DESCRIPTIONSAPPENDIX B
B-4 Edition 2 Octel PC/CDR
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table B-1. Events Alphabetized by Event Name (Concluded).
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Event NameÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
EventCode
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Event Description
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
RSSÁÁÁÁÁÁÁÁÁÁ
22ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Reset scanner board channelÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
SEIZE ÁÁÁÁÁÁÁÁÁÁ
23 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Seize port for outgoing callÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
SESSION ÁÁÁÁÁÁÁÁÁÁ
110 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Reserved for future applicationsÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
SMS ÁÁÁÁÁÁÁÁÁÁ
24 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Session mode set
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
SMSG_ALERT ÁÁÁÁÁÁÁÁÁÁ
113 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Reserved for future applications
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
SMSG_DELVR ÁÁÁÁÁÁÁÁÁÁ
111 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Reserved for future applicationsÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
SMSG_INFO ÁÁÁÁÁÁÁÁÁÁ
114 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Reserved for future applications
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
SMSG_REPORTÁÁÁÁÁÁÁÁÁÁ
112 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Reserved for future applications
ÁÁÁÁÁÁÁSMSG_STFWD ÁÁÁÁÁ115 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁReserved for future applicationsÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
TIGONÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
29ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Used only by Octel Network Services
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
TNE ÁÁÁÁÁÁÁÁÁÁ
25 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Trees, normal entry
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
TREES_FCD ÁÁÁÁÁÁÁÁÁÁ
132 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Forms-mailbox call dataÁÁÁÁÁÁÁÁÁÁÁÁÁÁTREES_FMB
ÁÁÁÁÁÁÁÁÁÁ131
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁForms-mailbox numberÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁTREES_FQA
ÁÁÁÁÁÁÁÁÁÁ
130ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Forms-mailbox question/answerÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
TRS ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
26 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Trees, restart entry
ÁÁÁÁÁÁÁTUTc ÁÁÁÁÁ30 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁMessaging tutorialÁÁÁÁÁÁÁÁÁÁÁÁÁÁUR_CHGb
ÁÁÁÁÁÁÁÁÁÁ92
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁUser record changeÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁXFR
ÁÁÁÁÁÁÁÁÁÁ
27ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
TransferÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
b Appears only when server software is at Aspen Release 2.0 or newer.c Appears only when server software is at Aria 1.2 or newer.
CDR EVENT DESCRIPTIONS APPENDIX B
Octel PC/CDR Edition 2 B-5
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table B-2. Events in Numerical Sequence by Event Code.
ÁÁÁÁÁÁÁÁÁÁÁÁ
EventCode
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Event NameÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Event Description
ÁÁÁÁÁÁÁÁ
0ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
IPLÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Server initial program loadÁÁÁÁÁÁÁÁ
1ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
DTS ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Set date and timeÁÁÁÁÁÁÁÁ
2ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CDRCFG ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CDR configurationÁÁÁÁÁÁÁÁ
16ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CALLER ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Caller identification
ÁÁÁÁÁÁÁÁ
17ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
IC ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Incoming call
ÁÁÁÁÁÁÁÁ
18ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
MW ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Message waiting set/clearÁÁÁÁÁÁÁÁ
19ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
OC ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Outcall to subscriber, pager, or fax
ÁÁÁÁÁÁÁÁ
20ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ON_HOOK ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Port goes on hook
ÁÁÁÁ21ÁÁÁÁÁÁÁÁPWT ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁPassword testÁÁÁÁÁÁÁÁÁÁÁÁ
22ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
RSSÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Reset scanner board channel
ÁÁÁÁÁÁÁÁ
23ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
SEIZE ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Seize port for outgoing call
ÁÁÁÁÁÁÁÁ
24ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
SMS ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Session mode setÁÁÁÁÁÁÁÁ25
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁTNE
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁTrees, normal entryÁÁÁÁ
ÁÁÁÁ26ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
TRSÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Trees, restart entryÁÁÁÁÁÁÁÁÁÁÁÁ
27ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
XFR ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Transfer
ÁÁÁÁ28ÁÁÁÁÁÁÁÁFCE ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁOctelForms mailbox end of sessionÁÁÁÁÁÁÁÁ29
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁTIGON
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁUsed only by Octel Network ServicesÁÁÁÁ
ÁÁÁÁ30aÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
TUTÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Messaging tutorialÁÁÁÁÁÁÁÁ
48ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
MS ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Message sentÁÁÁÁÁÁÁÁ
49ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
MD ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Message deletedÁÁÁÁÁÁÁÁ
64ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
BN_OCÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Outcall to an OctelNet nodeÁÁÁÁÁÁÁÁ
65ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
BN_IC ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Incoming call from OctelNet nodeÁÁÁÁÁÁÁÁ
66ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
BN_MULTILINE ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Reserved for future useÁÁÁÁÁÁÁÁ
70ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
BN_XMT_START ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
OctelNet transmit mode started
ÁÁÁÁÁÁÁÁ
71ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
BN_XMT_HDR ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
OctelNet message header transmitted
ÁÁÁÁÁÁÁÁ
72ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
BN_XMT_SP ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
OctelNet special message transmittedÁÁÁÁÁÁÁÁ
73ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
BN_XMT_CP ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
OctelNet message copy transmittedÁÁÁÁÁÁÁÁ
74ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
BN_XMT_VOICE ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
OctelNet message transmitted
ÁÁÁÁÁÁÁÁ
80ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
BN_RCV_START ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
OctelNet receive mode startedÁÁÁÁÁÁÁÁÁÁÁÁ
81ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
BN_RCV_HDRÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
OctelNet message header received
ÁÁÁÁÁÁÁÁ
82ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
BN_RCV_SP ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
OctelNet special message received
ÁÁÁÁÁÁÁÁ
83ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
BN_RCV_CP ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
OctelNet message copy received
ÁÁÁÁ84ÁÁÁÁÁÁÁÁBN_RCV_VOICE ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁOctelNet message receivedÁÁÁÁÁÁÁÁ89
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁBN_EOS
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁOctelNet end of sessionÁÁÁÁ
ÁÁÁÁÁÁÁÁ
90ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
BN_RTSÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
OctelNet message returned to sender
ÁÁÁÁÁÁÁÁ
91bÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
DISK_USG ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Disk-usage eventÁÁÁÁÁÁÁÁ92b
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁUR_CHG
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁUser record changeÁÁÁÁ
ÁÁÁÁÁÁÁÁ
93bÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
LIST_CHGÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Distribution lists added, modified, or deleted, or messagesent to this list
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
a Appears only when server software is at Aria 1.2 or newer.b Appears only when server software is at Aspen Release 2.0 or newer.
CDR EVENT DESCRIPTIONSAPPENDIX B
B-6 Edition 2 Octel PC/CDR
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table B-2. Events in Numerical Sequence by Event Code (Continued).
ÁÁÁÁÁÁÁÁÁÁÁÁ
EventCode
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Event NameÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Event Description
ÁÁÁÁÁÁÁÁ
94bÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CALLMNUÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Caller’s menu eventÁÁÁÁÁÁÁÁ
95bÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
PORTS_BUSY ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
All ports busyÁÁÁÁÁÁÁÁ
97bÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
PROFILE_CHG ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Mailbox profile changedÁÁÁÁÁÁÁÁÁÁÁÁ
100cÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
NNET_NAME ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
NameNet-transmission or receipt of ASCII or spokenname
ÁÁÁÁÁÁÁÁ
101cÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
NNET_DIR ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
NameNet-directory mismatch or nine of same name exist
ÁÁÁÁÁÁÁÁ
102cÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
NNET_ALARM ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
NameNet-directory alarm activity
ÁÁÁÁÁÁÁÁ
106bÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
FR ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Fax image received
ÁÁÁÁÁÁÁÁ
107bÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
FP ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Fax image printedÁÁÁÁÁÁÁÁ108b
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁFRTS
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁFax returned to senderÁÁÁÁ
ÁÁÁÁÁÁÁÁ
110ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
SESSIONÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Reserved for future applications
ÁÁÁÁÁÁÁÁ
111ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
SMSG_DELVR ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Reserved for future applications
ÁÁÁÁÁÁÁÁ
112ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
SMSG_REPORT ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Reserved for future applicationsÁÁÁÁÁÁÁÁ113
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁSMSG_ALERT
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁReserved for future applicationsÁÁÁÁ
ÁÁÁÁ114ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁSMSG_INFO
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁReserved for future applicationsÁÁÁÁ
ÁÁÁÁÁÁÁÁ
115ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
SMSG_STFWDÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Reserved for future applications
ÁÁÁÁÁÁÁÁ
116dÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
MSG_CNT ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Message countÁÁÁÁÁÁÁÁ117d
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁMSG_RVW
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁMessage reviewÁÁÁÁ
ÁÁÁÁ118aÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
GEN_ERRÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
General system errorÁÁÁÁÁÁÁÁ
129ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
PWT_RJCT ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Bad-password limitÁÁÁÁÁÁÁÁÁÁÁÁ
130ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
TREES_FQA ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Forms-mailbox question/answerÁÁÁÁÁÁÁÁ131
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁTREES_FMB
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁForms-mailbox numberÁÁÁÁ
ÁÁÁÁ132ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
TREES_FCDÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Forms-mailbox call dataÁÁÁÁÁÁÁÁ
140ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_XMT_OC ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Start of AMIS outcallÁÁÁÁÁÁÁÁ
141ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_XMT_STARTÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS start session transmittedÁÁÁÁÁÁÁÁ
142ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_XMT_PHNUMÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS server telephone number transmittedÁÁÁÁÁÁÁÁ
143ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_XMT_MINFOÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS-message information transmittedÁÁÁÁÁÁÁÁ
144ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_XMT_MBOX ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS logged bad sender’s mailbox numberÁÁÁÁÁÁÁÁ
145ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_XMT_VOICE ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS transmitted voiceÁÁÁÁÁÁÁÁ
146ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_XMT_EOM ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
End-of-AMIS message frame transmittedÁÁÁÁÁÁÁÁ
147ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_XMT_EOS ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
End-of-AMIS session transmitted
ÁÁÁÁÁÁÁÁ
148eÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_XMT_RESP ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Acknowledgment received from serverÁÁÁÁÁÁÁÁ
151ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
IVR_EXIT ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Exit IVR application detailsÁÁÁÁÁÁÁÁ
155eÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_RCV_FC ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS function code receivedÁÁÁÁÁÁÁÁ
156eÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_RCV_RESP ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Acknowledgment sent for AMIS-received frame
ÁÁÁÁÁÁÁÁ
157eÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_RCV_FR ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Status of received AMIS frame
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
a Appears only when server software is at Aria 1.2 or newer.b Appears only when server software is at Aspen Release 2.0 or newer.c Appears only when server software is at Aspen Release 3.0 or newer.d Appears only when server software is at Aspen Release 4.1, Aria 1.1, or newer.e Appears only when certain service-related functions are performed.
CDR EVENT DESCRIPTIONS APPENDIX B
Octel PC/CDR Edition 2 B-7
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table B-2. Events in Numerical Sequence by Event Code (Concluded).
ÁÁÁÁÁÁÁÁÁÁÁÁ
EventCode
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Event NameÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Event Description
ÁÁÁÁÁÁÁÁ
158ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_RCV_STARTÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS start session receivedÁÁÁÁÁÁÁÁ
159ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_RCV_PHNUMÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Caller’s AMIS system-access telephone numberÁÁÁÁÁÁÁÁ
160ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_RCV_MSGI ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS message attribute receivedÁÁÁÁÁÁÁÁ
161ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_RCV_MSG ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS message-recording status received
ÁÁÁÁÁÁÁÁ
162ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_RCV_IC ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Incoming AMIS call
ÁÁÁÁÁÁÁÁ
163ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_RCV_INVPH ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Invalid AMIS system-access telephone number receivedÁÁÁÁÁÁÁÁ
164ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_RCV_EOS ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
End-of-AMIS session received
ÁÁÁÁÁÁÁÁ
165ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_SEND ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS message queued
ÁÁÁÁ166ÁÁÁÁÁÁÁÁAM_RTS ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁAMIS message returned to senderÁÁÁÁÁÁÁÁÁÁÁÁ
170ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_DIR_FULLÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS directory 90% full
ÁÁÁÁÁÁÁÁ
171ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_EAR_FULL ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS EAR (extended address record) array 90% full
ÁÁÁÁÁÁÁÁ
172ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CNN_ENABLE ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Reserved for future applicationsÁÁÁÁÁÁÁÁ173
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁCNN_VC_LINK
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁReserved for future applicationsÁÁÁÁ
ÁÁÁÁ174ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CNN_OCL_VMÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Reserved for future applicationsÁÁÁÁÁÁÁÁÁÁÁÁ
175ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CNN_OCL_MB ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Reserved for future applications
ÁÁÁÁ176ÁÁÁÁÁÁÁÁGET_ROUTE ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁReserved for future applicationsÁÁÁÁÁÁÁÁ177
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁOCL_NAME
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁReserved for future applicationsÁÁÁÁ
ÁÁÁÁ178ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CNN_PRIVACYÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Reserved for future applicationsÁÁÁÁÁÁÁÁ
198bÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
DM_PSEUDO ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Missing start or end of call; for internal use onlyÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
b Appears only when server software is at Aspen Release 2.0 or newer.
CDR EVENT DESCRIPTIONSAPPENDIX B
B-8 Edition 2 Octel PC/CDR
Table B-3. Event Details.
Field Description
AM_DIR_FULL (AMIS directory 90% full)
. . . No additional information is logged with this event
AM_EAR_FULL (AMIS EAR [extended-address-record] array 90% full)
. . . No additional information logged with this event
AM_RCV_EOS (End-of-AMIS session received)
P: Server port number used
Success/Fail: Success/failure code:
0 – OK
1 – Frame length error
2 – Data error
Len/Data: Length/data, depends on SF value
AM_RCV_FCa (AMIS function code received)
P: Server port number used
Stat: Status code for receive-function-code event:
1 – Start session
2 – System number
3 – Message information
4 – End message
5 – Protocol extension
6 – End session
255 – Unknown
AM_RCV_FRa (Status of received AMIS frame)
P: Server port number used
Stat: Status code for receive-frame event:
0 – OK
1 – Checksum error
2 – Disconnect
3 – Timeout error
4 – Frame-length error
5 – Data error
6 – Function-code error
7 – Start-digit timeout
8 – Internal error
255 – Unknown
Data: Invalid data or invalid function code, otherwise unused
AM_RCV_IC (Incoming AMIS call)
P: Server port number useda Appears only when certain service-related functions are performed.
CDR EVENT DESCRIPTIONS APPENDIX B
Octel PC/CDR Edition 2 B-9
Table B-3. Event Details (Continued).
Field Description
AM_RCV_INVPH (Invalid AMIS system-access telephone number received)
P: Server port number usedStat: Status code for invalid telephone numbers:
1 – Country-code error2 – Not pound-terminated3 – Did not contain three pound signs4 – Data-length error
255 – UnknownInvalidLen: Length, used only if error in length of telephone number
AM_RCV_MSG (AMIS message-recording status received)
P: Server port number usedStat: Message-received status code:
0 – OK1 – Message-record initial error2 – Message-recorded error3 – End-message error
255 – Unknown
AM_RCV_MSGI (AMIS message attribute received)
P: Server port number usedMsgType: Message-type codes:
0 – New message1 – Reply message2 – Returned message
NDN: Nondelivery-notification types:0 – New message or reply message2 – Message too long3 – Recipient mailbox number does not exist4 – Recipient mailbox does not accept message5 – Destination mailbox full9 – Other reason for returned message
Len: Length of message received, in minutesSendBox: Sender’s mailbox numberRecpBox: Recipient’s mailbox number
Stat: Status code for message attributes:0 – OK1 – Message too long2 – No such mailbox3 – Not accepted4 – Mailbox full5 – Internal error
255 – Unknown
CDR EVENT DESCRIPTIONSAPPENDIX B
B-10 Edition 2 Octel PC/CDR
Table B-3. Event Details (Continued).
Field Description
AM_RCV_PHNUM (Caller’s AMIS system-access telephone number)
P: Server port number usedNumber: Telephone number
Stat: Status code for receive telephone number:0 – OK1 – No reply will be sent2 – Incoming call blocked by transmission table entry3 – SMT telephone number incorrect4 – Protocol error
255 – UnknownNode:b Administered AMIS node number
AM_RCV_RESPa (Acknowledgment sent for AMIS-received frame)
P: Server port number usedStat: Status code for send-response event:
0 – Accept send1 – Retransmission request2 – Frame-specific3 – Frame-specific4 – Frame-specific5 – Frame-specific6 – Timeout7 – Frame error8 – Protocol error9 – Abort
254 – Receiver detected error and sent # # # to disconnect255 – Unknown
AM_RCV_START (AMIS start session received)
P: Server port number usedStat: Status code for start session:
0 – Successful1 – AMIS not installed on this system2 – Disk full3 – Version not supported4 – Protocol error
255 – Unknown
a Appears only when certain service-related functions are performed.b Appears only when server software is at Aria 1.2 or newer.
CDR EVENT DESCRIPTIONS APPENDIX B
Octel PC/CDR Edition 2 B-11
Table B-3. Event Details (Continued).
Field Description
AM_RTS (AMIS message returned to sender)
P: Server port number used
RecpBox: Recipient’s mailbox number
SendBox: Sender’s mailbox number
TOD: Date and time (delivery time in minutes, since 1/1/84)
MsgID1: ID of first message segment
MsgID2: ID of second message segment
Len: Total message-segment length
SegCt: Total number of segments in message
Number: Sender or recipient telephone number
PhType: Type of telephone number
Why: Reason for return:
1 – Ring no answer
2 – Busy
3 – Bad line
4 – Could not pass wakeup setup
5 – Wrong number
6 – Remote server full
7 – Remote server not supporting AMIS
8 – Remote server not supporting this version
9 – Remote system rejected this call
10 – Telephone number wrong in SMT
11 – Remote identify message too long
12 – Remote mailbox not found
13 – Remote mailbox will not accept this message
14 – Remote mailbox full
15 – Remote sent cutoff
16 – Bad message
255 – Unknown
AM_SEND (AMIS message queued)
P: Server port number used
Type: Type of message:
0 – Real message
255 – Unknown
Attr: Attribute of message:
0 – Forwarded message
SR: Send/receive information:
0 – From Octel subscriber to AMIS destination
1 – From AMIS destination to Octel subscriber
RecpBox: Recipient’s mailbox number
CDR EVENT DESCRIPTIONSAPPENDIX B
B-12 Edition 2 Octel PC/CDR
Table B-3. Event Details (Continued).
Field Description
AM_SEND (AMIS message queued) (Concluded)
SendBox: Sender’s mailbox number
TOD: Date and time (in minutes since 1/1/84)
MsgID1: ID of first message segmentMsgID2: ID of second message segment
Len1: First-message-segment length
Len2: Total length of remaining segmentsSegCt: Total number of segments in message
Number: Sender of recipient telephone number
PhType: Type of telephone number
AM_XMT_EOM (End-of-AMIS message frame transmitted)
P: Server port number used
Stat: Status code for end-of-message transmit:
0 – Successful2 – Message too long
3 – Mailbox does not exist4 – Mailbox not accepting AMIS
5 – Mailbox full
6 – Internal error7 – Invalid response
255 – Unknown response
AM_XMT_EOS (End-of-AMIS session transmitted)
P: Server port number usedRoutine: For internal use only
Stat: End-of-session status code:
0 – Successful1 – Timeout
2 – Frame error
3 – Protocol error4 – Abort
255 – Unknown
AM_XMT_MBOX (AMIS logged bad sender’s mailbox number)
P: Server port number usedIUN: Mailbox IUN
AM_XMT_MINFO (AMIS-message information transmitted)
P: Server port number used
SendBox: Sender’s mailbox numberRecpBox: Recipient’s mailbox number
Len: Message length, rounded to minutes
CDR EVENT DESCRIPTIONS APPENDIX B
Octel PC/CDR Edition 2 B-13
Table B-3. Event Details (Continued).
Field Description
AM_XMT_MINFO (AMIS-message information transmitted) (Concluded)
Stat: Status code for message transmit:0 – Successful1 – Retry2 – Message too long3 – No mailbox4 – Not accepting message5 – Mailbox full
255 – Unknown
AM_XMT_OC (Start of AMIS outcall)
P: Server port number usedNumber: AMIS-system-access telephone number dialed
Dial Sequence: AMIS dial sequence with authorization codePhType: Telephone number type:
0 – Local1 – Long distance2 – International3 – Private number
255 – UnknownStat: Outcall status code:
0 – Outcall answered (receiver-off-hook detected)1 – Busy detected2 – Fast-busy detected3 – Ring no answer detected
254 – Unknown, answer assumed255 – Outcall failed, port goes on hook
AM_XMT_PHNUM (AMIS server telephone number transmitted)
P: Server port number usedNumber: AMIS-system-access telephone number used
Stat: AMIS-system-access telephone-transmit status code:0 – Successful1 – Retry later2 – Blocked by transmission-acceptance table3 – No reply4 – Invalid response5 – No number in SMT6 – Number in SMT is incorrect (length)
255 – Unknown response
CDR EVENT DESCRIPTIONSAPPENDIX B
B-14 Edition 2 Octel PC/CDR
Table B-3. Event Details (Continued).
Field Description
AM_XMT_RESPa (Acknowledgment received from server)
P: Server port number used
Stat: Status code for response from remote system:
0 – Time-out getting start digit
1 – Time-out getting response frame
2 – Remote disconnect
3 – Check digit error in received frame
4 – Remote sent accept
5 – Remote sent retransmit
6 – Remote sent time-out
7 – Remote sent frame error
8 – Remote sent protocol error
9 – Remote sent abort
10 – Remote sent valid-response number 2, 3, 4, or 5
11 – Remote sent invalid-response code
12 – Retransmitted three times, remote wants again
AM_XMT_START (AMIS start session transmitted)
P: Server port number used
Stat: AMIS outcall-start status code:
0 – Successful
1 – Retry later
2 – Disk full on receiving system
3 – No networking
4 – AMIS version not supported
5 – Invalid response from receiving system
255 – Unknown response
AM_XMT_VOICE (AMIS transmitted voice)
P: Server port number used
MsgID1: ID of first message segment
MsgID2: ID of second message segment
Len: First-message-segment length
SegCt: Total number of segments in message
StartTime: Transmission start time
EndTime: Transmission end time
Stat: Status code for transmit voice:
0 – Successful
1 – Cutoff key received
2 – Message deleted
255 –Unknown returned code
a Appears only when certain service-related functions are performed.
CDR EVENT DESCRIPTIONS APPENDIX B
Octel PC/CDR Edition 2 B-15
Table B-3. Event Details (Continued).
Field Description
BN_EOS (OctelNet end of session)
P: Server port number used
Node: Node number (1–500)
Serial: Serial number
Stat: End-of-session status code:
0 – Successful session1 – Operator-requested calls discontinued2 – Session terminated on low signal measurement3 – Session terminated on low signal-to-noise ratio4 – Session terminated on other line problems5 – Session terminated at request of other server
254 – Session terminated on system errors255 – Session terminated on unknown errors
BN_IC (Incoming call from OctelNet node)
P: Server port number used
BN_MULTILINE (Reserved for future use)
Node: Node number
Serial: Node serial number
Tasks In Use: Total tasks currently in use
Max Tasks: Maximum number of allowed tasks (per node profile)
Tot Msgs: Total number of messages currently in queue
Tot Msg Len(mins):
Total length of all messages in queue for this node (in minutes)
Msgs/Task: Maximum number of messages in queue before system enables a newtransmission task
Msg Len/Task(mins):
Maximum number of message minutes in queue before systemenables a new transmission task
BN_OC (Outcall to an OctelNet node)
P: Server port number used
Node: Node number of node called (1–500)
Serial: Serial number
Number: Telephone number dialed
Dial Sequence: Dial sequence with authorization code
Stat: Outcall status code:
0 – Outcall answered (receiver off-hook detected)
1 – Busy detected
2 – Fast-busy detected
3 – Ring no answer detected
4 – Unknown, answer assumed
255 – Outcall failed, port goes on hook
b Appears only when server software is at Aria 1.2 or newer.
CDR EVENT DESCRIPTIONSAPPENDIX B
B-16 Edition 2 Octel PC/CDR
Table B-3. Event Details (Continued).
Field Description
BN_OC (Outcall to an OctelNet node) (Concluded)
NodeType:b Type of node0 – OctelNet analog node1 – AMIS analog node
255 – Unknown node
BN_RCV_CP (OctelNet message copy received)
P: Server port number usedDest: Destination (receiver) mailbox numberAttr: Message-attribute flag codes (sum of values):
0 – No special attributes4 – Future delivery requested8 – Message forwarded from another subscriber
16 – Confirmation of nondelivery requested32 – Confirmation of delivery requested64 – Message marked private
128 – Message marked urgentTOD: If future delivery, date and time message was delivered; otherwise,
entry is not applicable to this eventStat: Copy–received status code:
0 – Successful, message copied to destination mailbox1 – Message not copied, requested mailbox does not exist2 – Message not copied, wrong mailbox type3 – Message not copied, destination mailbox full4 – Message not copied, destination-mailbox future-delivery
limit exceeded5 – Message not copied, receiving server full9c – ASCII name mismatch
10c – Unsuccessful transmission; message blocked by receivingmailbox
11d – Successful transmission; message received by mailbox withextended-absence greeting
254 – Message not copied, network transmission error255 – Message not copied, other error
Opt:d Option:0 – Normal1 – Name confirmation
b Appears only when server software is at Aria 1.2 or newer.c Appears only when server software is at Aspen Release 3.0 or newer.d Appears only when server software is at Aspen Release 4.0 or newer.
CDR EVENT DESCRIPTIONS APPENDIX B
Octel PC/CDR Edition 2 B-17
Table B-3. Event Details (Continued).
Field Description
BN_RCV_HDR (OctelNet message header received)
P: Server port number used
Source: Source mailbox number
Dest: Destination (receiver) mailbox number
Attr:e Message-attribute flag codes (sum of values):
0 – No special attributes
4 – Future delivery requested
8 – Message forwarded from another subscriber
16 – Confirmation of nondelivery requested
32 – Confirmation of delivery requested
64 – Message marked private
128 – Message marked urgent
Attr:f Message-return code:
1 – Destination mailbox not found
2 – Wrong mailbox type
3 – Destination mailbox full
4 – Destination mailbox future-delivery limit exceeded
6 – Node deleted
7 – Node disabled with the request to return messages
8 – Message determined bad (during transmission or during garbage collect)
9 – Node continuously busy
10 – Node continuously ring no answer
11 – Node continuously bad line
12 – ASCII name mismatch
13 – Message blocked by receiving mailbox
14 – Receiving mailbox not capable receiving faxes
15 – Receiving port not capable of receiving faxes
16 – Receiving node not capable of receiving faxes
17 – Transmission port not capable of sending faxes
18 – Hub synchronization problem
19 – Recipient has extended-absence greeting with blocked mail-box
255 – Unspecified-return reason
TOD: If future delivery, date and time message was delivered; otherwise,entry is not applicable to this event
e If entry in BN_RCV_HDR Msg Type: field is 1 or 2, refer to this set of attributes; otherwise, use BN_RCV_HDRAttr:f for the message-return code.
f If entry in BN_RCV_HDR Msg Type: field is 4 or 5, refer to this set of attributes; otherwise, use BN_RCV_HDRAttr:e for message-attribute codes. Msg Type: code values 4 and 5 appear only when server software is atAspen Release 4.1, Aria 1.1, or newer.
CDR EVENT DESCRIPTIONSAPPENDIX B
B-18 Edition 2 Octel PC/CDR
Table B-3. Event Details (Continued).
Field Description
BN_RCV_HDR (OctelNet message header received) (Concluded)
Stat: Header-received status code:0 – Successful, ready to receive voice message1 – Requested mailbox does not exist2 – Wrong mailbox type3 – Destination-mailbox full4 – Destination mailbox future-delivery limit exceeded9c – ASCII name mismatch
10c – Unsuccessful transmission; message blocked by receivingmailbox
11d – Successful transmission; message received by mailbox with extended-absence greeting
254 – Network transmission error255 – Unknown error
MsgType:g Type of message:1 – Voice message2 – Compound fax message4 – Voice message returned by hub5 – Fax message returned by hub
Opt:d Option:0 – Normal1 – Name confirmation
BN_RCV_SP (OctelNet special message received)
P: Server port number usedType: Special message-type-indication code:
0 – Confirmation of message delivery (the date/time field indi-cates when the confirmation of delivery request was heard)
1 – Confirmation of nondelivery (the date/time field indicatedwhen the confirmation of delivery request was sent)
Source: Source mailbox numberDest: Destination (receiver) mailbox numberTOD: Date and timeStat: Special message-received status code:
0 – Successful1 – Requested destination mailbox does not exist2 – Wrong mailbox type (not a voice-messaging mailbox)3 – Destination mailbox full4 – Destination-mailbox future-delivery limit exceeded
11d – Successful transmission; message received by mailbox with extended-absence greeting
254 – Network transmission error255 – Unknown error
c Appears only when server software is at Aspen Release 3.0 or newer.d Appears only when server software is at Aspen Release 4.0 or newer.g If entry in BN_RCV_HDR Msg Type: field is 1 or 2, refer to BN_RCV_HDR Attr:e for message-attribute flag
codes. If entry in BN_RCV_HDR Msg Type: field is 4 or 5, refer to BN_RCV_HDR Attr:f for the message-returncode. Msg Type: codes 4 and 5 appear only when server software is at Aspen Release 4.1, Aria 1.1, or newer.
CDR EVENT DESCRIPTIONS APPENDIX B
Octel PC/CDR Edition 2 B-19
Table B-3. Event Details (Continued).
Field Description
BN_RCV_START (OctelNet receive mode started)
P: Server port number usedNode: Node number (1–500)
Serial: Serial number of remote server
BN_RCV_VOICE (OctelNet message received)
P: Server port number usedMsgID: Internal message identifier
Len: Length of first voice segment (seconds; contains –1 if length of segment too long for internal encoding)
Stime: Start date and time sentEtime: Start date and time received
Stat: Header-received status code:0 – Successful; message received and sent to first mailbox1 – Unsuccessful; destination mailbox deleted before message
could be sent to it3 – Unsuccessful; destination mailbox became full before mes-
sage could be sent to it4 – Unsuccessful; destination mailbox future-delivery limit
exceeded5 – Unsuccessful; destination server became full during voice
transmission/recording6 – Unsuccessful; bad message- or network-transmission
problems during voice recording12d – Fax protocol time-out; nothing transmitted13d – Fax protocol time-out; partial transmission
254 – Unsuccessful; bad-message- or network-transmission prob-lems after voice recording
FaxMsgID:d Fax ID of fax image (assigned internally)FaxPage:d Length, in pages, of fax image receivedFaxSec:d Length, in seconds, of fax image receivedFaxPart:d Portion (image or voice) of incomplete fax received
BN_RTS (OctelNet message returned to sender)
P: Server port number usedNode: Target node number of attempted transmission
Serial: Serial number of target node (if known)Source: Source mailbox number
Dest: Destination (receiver) mailbox number
d Appears only when server software is at Aspen Release 4.0 or newer.
CDR EVENT DESCRIPTIONSAPPENDIX B
B-20 Edition 2 Octel PC/CDR
Table B-3. Event Details (Continued).
Field Description
BN_RTS (OctelNet message returned to sender) (Continued)
Attr: Message-attribute flag codes (sum of values):0 – No special attributes4 – Future delivery requested8 – Message forwarded from another subscriber
16 – Confirmation of nondelivery requested32 – Confirmation of delivery requested64 – Message marked private
128 – Message marked urgent
TOD: Date and time when message was delivered
MsgID1: Internal message identifier, first segment
MsgID2: Internal message identifier, second segment
Len1:h Total number of seconds of original message or introductory message (contains –1 if length of segment too long for internal encoding)
Len2:h Total number of seconds of original message (contains –1 if length ofsegment too long for internal encoding or 0 if no segments follow thefirst)
SegCT: Total number of segments in message
Why: Message-return code:1 – Destination mailbox not found2 – Wrong mailbox type3 – Destination mailbox full4 – Destination mailbox future-delivery limit exceeded6 – Node deleted7 – Node disabled with the request to return messages8 – Message determined bad (during transmission or during
garbage collect)9 – Node continuously busy
10 – Node continuously ring no answer11 – Node continuously bad line12c – ASCII name mismatch13c – Message blocked by receiving mailbox14d – Receiving mailbox not capable of receiving faxes15d – Receiving port not capable of receiving faxes16d – Receiving node not capable of receiving faxes17d – Transmission port not capable of sending faxes18i – Hub synchronization problem19i – Recipient has extended-absence greeting with blocked
mailbox255 – Unspecified-return reason
c Appears only when server software is at Aspen Release 3.0 or newer.d Appears only when server software is at Aspen Release 4.0 or newer.h If Len2 is blank, Len1 equals the total number of seconds of the original message. However, if the message
has been copied, the original length moves to Len2, and the length of only the introduction becomes the newLen1.
i Appears only when server software is at Aspen Release 4.1, Aria 1.1, or newer.
CDR EVENT DESCRIPTIONS APPENDIX B
Octel PC/CDR Edition 2 B-21
Table B-3. Event Details (Continued).
Field Description
BN_RTS (OctelNet message returned to sender) (Concluded)
MsgType:d Type of message:
1 – Voice message
2 – Compound fax message
FaxID:d Fax ID of fax image (assigned internally)
FaxPage:d Length, in pages, of fax image
FaxSec:d Length, in seconds, of fax image
FaxPart:d Identifies portion (image or voice) of incomplete fax that was transmitted
NodeType:b Type of node
0 – OctelNet analog node
1 – AMIS analog node
255 – Unknown node
BN_XMT_CP (OctelNet message copy transmitted)
P: Server port number used
Dest: Destination (receiver) mailbox number
Attr: Message-attribute flag codes (sum of values):0 – No special attributes4 – Future delivery requested8 – Message forwarded from another subscriber
16 – Confirmation of nondelivery requested32 – Confirmation of delivery requested64 – Message marked private
128 – Message marked urgent
TOD: Date and time when message will be delivered
Stat: Copy-transmit status code:
0 – Successful, message to destination mailbox1 – Message not transmitted, requested mailbox not found2 – Message not transmitted, wrong mailbox type3 – Message not transmitted, destination mailbox full4 – Message not transmitted, destination mailbox future-
delivery limit reached5 – Message not transmitted, server full9c – ASCII name mismatch
10c – Unsuccessful transmission; message blocked by receivingmailbox
11d – Successful transmission; message received by mailbox with extended-absence greeting
254 – Network transmission error255 – Unknown error
b Appears only when server software is at Aria 1.2 or newer.c Appears only when server software is at Aspen Release 3.0 or newer.d Appears only when server software is at Aspen Release 4.0 or newer.
CDR EVENT DESCRIPTIONSAPPENDIX B
B-22 Edition 2 Octel PC/CDR
Table B-3. Event Details (Continued).
Field Description
BN_XMT_CP (OctelNet message copy transmitted) (Concluded)
Opt:d Option:0 – Normal1 – Name confirmation
BN_XMT_HDR (OctelNet message header transmitted)
P: Server port number usedSource: Source mailbox number
Dest: Destination (receiver) mailbox numberAttr: Message-attribute flag codes (sum of values):
0 – No special attributes4 – Future delivery requested8 – Message forwarded to another mailbox subscriber
16 – Confirmation of nondelivery requested32 – Confirmation of delivery requested64 – Message marked private
128 – Message marked urgentTOD: Date and time message will be deliveredStat: Header-transmit status code:
0 – Successful, ready to receive voice message1 – Requested mailbox does not exist2 – Wrong mailbox type3 – Destination mailbox full4 – Destination mailbox future-delivery limit exceeded9c – ASCII name mismatch
10c – Unsuccessful transmission; message blocked by receivingmailbox
11d – Successful transmission; message received by mailbox with extended-absence greeting
254 – Network transmission error255 – Unknown error
MsgType:c Type of message:1 – Voice message2 – Compound fax message
Opt:c Option:0 – Normal1 – Name confirmation
c Appears only when server software is at Aspen Release 3.0 or newer.d Appears only when server software is at Aspen Release 4.0 or newer.
CDR EVENT DESCRIPTIONS APPENDIX B
Octel PC/CDR Edition 2 B-23
Table B-3. Event Details (Continued).
Field Description
BN_XMT_SP (OctelNet special message transmitted)
P: Server port number usedType: Special message-type-indication code:
0 – Confirmation of message delivery (the date/time field indi-cates when confirmation-of-delivery request was heard)
1 – Confirmation of nondelivery (the date/time field indicateswhen confirmation-of-delivery request was sent)
Source: Source mailbox numberDest: Destination (receiver) mailbox numberTOD: Date and time when message will be deliveredStat: Special-message-transmit status code:
0 – Successful1 – Destination mailbox not found2 – Wrong mailbox type (not a voice-messaging mailbox)3 – Destination mailbox full4 – Sending server full
254 – Network transmission error255 – Unknown error
BN_XMT_START (OctelNet transmit mode started)
P: Server port number usedNode: Node number (1–500)
Serial: Serial number of remote server
BN_XMT_VOICE (OctelNet message transmitted)
P: Server port number usedMsgID1: Internal message identifier, first segmentMsgID2: Internal message identifier, second segment
Len1:h Total number of seconds of original message or introductory message(contains –1 if length of segment too long for internal encoding)
Len2:h Total number of seconds of original message (contains –1 if length ofsegment too long for internal encoding or 0 if no message follows thefirst)
SegCT: Total number of segments in messageStime: Transmit start date and timeEtime: Transmit end date and time
h If Len2 is blank, Len1 equals the total number of seconds of the original message. However, if the messagehas been copied, the original length moves to Len2, and the length of only the introduction becomes the newLen1.
CDR EVENT DESCRIPTIONSAPPENDIX B
B-24 Edition 2 Octel PC/CDR
Table B-3. Event Details (Continued).
Field Description
BN_XMT_VOICE (OctelNet message transmitted) (Concluded)
Stat: Transmit status code:0 – Successful; message transmitted and sent to first mailbox1 – Unsuccessful; destination mailbox deleted before message
could be sent to it3 – Unsuccessful; destination mailbox became full before
message could be sent to it4 – Unsuccessful; destination mailbox future-delivery limit
exceeded6 – Unsuccessful; bad message- or network-transmission
problems during voice transmission8d – Unsuccessful; message determined to be bad
12d – Fax protocol timeout; nothing transmitted13d – Fax protocol timeout; partial fax transmission14d – Unsuccessful transmission; bad fax image15d – Unsuccessful transmission; bad destination drive
254 – Unsuccessful; bad message- or network-transmission problems after voice transmission
FaxID:d Fax ID of the fax image (assigned internally)FaxPage:d Length, in pages, of the fax imageFaxSec:d Length, in seconds, of the fax imageFaxPart:d Identifies portion (image of voice) of incomplete fax that was
transmitted
CALLER (Caller identification)
P: Server port number usedID: Calling-party telephone number
CALLMNUj (Caller’s menu event)
P: Server port number usedSrcBox: Source mailbox number used for this call (only Enhanced Call
Processing [ECP] mailbox types 31–33)Dest: Mailbox or extension number to which the caller was routed from the
source mailboxDestType: Identifies whether value in the Dest: field is an extension or a
mailbox:0 – Mailbox1 – Extension
255 – Destination cannot be identified
d Appears only when server software is at Aspen Release 4.0 or newer.
CDR EVENT DESCRIPTIONS APPENDIX B
Octel PC/CDR Edition 2 B-25
Table B-3. Event Details (Continued).
Field Description
CALLMNUj (Caller’s menu event) (Concluded)
ActType: Identifies what happened while the caller was in the source mailbox:
0 – Caller pressed 0
1 – Caller pressed 1
2 – Caller pressed 2
3 – Caller pressed 3
4 – Caller pressed 4
5 – Caller pressed 5
6 – Caller pressed 6
7 – Caller pressed 7
8 – Caller pressed 8
9 – Caller pressed 9
10 – Caller pressed *
11 – Caller pressed #
12 – Caller timed out
13 – Caller hung up
14 – Caller entered a name for dial-by-name
15 – Caller entered a mailbox or extension number
CDRCFG (CDR configuration)
Bits: Hexadecimal dump showing the event-record code (this informationcan be found in SMT menu 16.1.4)
CNN_ENABLE (Reserved for future applications)
CNN_OCL_MB (Reserved for future applications)
CNN_OCL_VM (Reserved for future applications)
CNN_PRIVACY (Reserved for future applications)
CNN_VC_LINK (Reserved for future applications)
DISK_USGj (Disk-usage event)
UsedMsgHigh: Highest amount of message disk space used, in minutes, during15-minute interval
UsedMsgMed: Medium amount of message disk space used, in minutes, during15-minute interval
UsedMsgLow: Lowest amount of message disk space used, in minutes, during15-minute interval
UsedPhrase-High:
Highest amount of phrase disk space used, in minutes, during15-minute interval
UsedPhrase-Med:
Medium amount of phrase disk space used, in minutes, during15-minute interval
UsedPhrase-Low:
Lowest amount of phrase disk space used, in minutes, during15-minute interval
j Appears only when server software is at Aspen Release 2.0 or newer.
CDR EVENT DESCRIPTIONSAPPENDIX B
B-26 Edition 2 Octel PC/CDR
Table B-3. Event Details (Continued).
Field Description
DISK_USGj (Disk-usage event) (Concluded)
FreeMsgHigh: Highest amount of available message space, in minutes, during15-minute interval
FreeMsgMed: Medium amount of available message space, in minutes, during15-minute interval
FreeMsgLow: Lowest amount of available message space, in minutes, during15-minute interval
FreePhrase-High:
Highest amount of available phrase space, in minutes, during15-minute interval
FreePhrase-Med:
Medium amount of available phrase space, in minutes, during15-minute interval
FreePhrase-Low:
Lowest amount of available phrase space, in minutes, during 15-minute interval
DM_PSEUDOj (Missing start or end of call; for internal use only)
P: Server port number used
SubType: Reason for event start or end:
0 – Start of call
1 – End of call
2 – System (nonport) event
3 – Start-of-session call
4 – End–of-session call
StartReason: Reason for pseudo call start:
0 – No pseudo event at subtype
1 – Lost block
EndReason: Reason for pseudo call end:
0 – No pseudo event at subtype
1 – Lost block
DTS (Set date and time)
P: Server port number used
Old: Server date and time before change
New: Server date and time after change
Reason: Code indicating reason for change of clocks:
0 – Clock setting in a newly installed server
1 – Clock not valid when server booted, system manager forcedto set clock
2 – Clock changed by system manager
3j – Clock changed by cluster card
FCE (OctelForms mailbox end of session)
P: Server port number used
j Appears only when server software is at Aspen Release 2.0 or newer.
CDR EVENT DESCRIPTIONS APPENDIX B
Octel PC/CDR Edition 2 B-27
Table B-3. Event Details (Continued).
Field Description
FPj (Fax image printed)
P: Server port used to print fax imageBox: Mailbox number of fax-image owner
Number: Destination telephone number dialedRcpNum: Recipient telephone number (for cover sheet)
RcpExt: Recipient extension number (for cover sheet)StartTime: Start print/queue date and timeStopTime: Stop print date and time
MsgID: Internal message identifier for first (or only) segment of fax messageFaxPage: Length, in pages, of fax image (1–250)FaxSec: Length of fax image, measured in storage seconds (contains –1 if
length of image is more than 32,000 seconds)BoxType: Sender’s mailbox type
FaxID: Fax ID of the fax imageWhy: Print-reason codes:
0 – Printed by user1 – Printed by auto-print2 – Printed by print-all
Fail: Error numbers in case of print failure:0 – Entire fax document printed1 – Too many errors2 – No communication3 – Loss of carrier4 – Time-out
Image: Type of fax-image message:0 – Fax image only1 – Fax image part of a compound message2 – Fax image recorded as partial
FRj (Fax image received)
P: Server port used for fax-image receiptBox: Mailbox number of fax-image owner
MsgID: Internal message identifierFaxPage: Number of pages in the fax image (1–250)FaxSec: Length of fax image, measured in storage seconds (contains –1 if
length of fax image is more than 32,000 seconds)StartTime: Start receive date and timeStopTime: Stop receive date and time
FaxID: Fax ID of the image
j Appears only when server software is at Aspen Release 2.0 or newer.
CDR EVENT DESCRIPTIONSAPPENDIX B
B-28 Edition 2 Octel PC/CDR
Table B-3. Event Details (Continued).
Field Description
FRj (Fax image received) (Concluded)
FaxPart: Error codes in case partial fax image received:
0 – Entire fax document received
1 – Too many errors
2 – No communication
3 – Loss of carrier
4 – Time-out
5 – Page limit exceeded
6 – Disk full
FRTSj (Fax returned to sender)
P: Server port number used to send return message
Number: Telephone number called that caused FRTS
SrcBox: Source mailbox number of sender
LastTime: Last date and time fax-image printing was attempted
MsgID: Internal message identifier for first (or only) segment of fax message
FaxPage: Length, in pages, of returned fax image
FaxSec: Length, in seconds, measured in storage seconds (contains –1 iflength of fax image is more than 32,000 seconds)
FaxID: Fax ID of returned fax image
OrigID: Original fax ID of returned fax image
Fail: Last-fax-image return reason codes:
1 – Continuously busy2 – Ring no answer3 – Continuously bad line4 – Non-fax-capable device detected5 – Total retries exceeded
GEN_ERRb (General system error)
Subtype: Type of error:
0 – VTIC frame synchronization error
FrameSync-ErrorType:
Type of frame-synchronization error:
0 – Primary
1 – Secondary
2 – All frame synchronization back to normal
GET_ROUTE (Reserved for future applications)
IC (Incoming call)
P: Server port number used
TransID:j Transaction ID of event (assigned internally)
b Appears only when server software is at Aria 1.2 or newer.j Appears only when server software is at Aspen Release 2.0 or newer.
CDR EVENT DESCRIPTIONS APPENDIX B
Octel PC/CDR Edition 2 B-29
Table B-3. Event Details (Continued).
Field Description
IPL (Server initial program load)
P: PC/CDR assigned port number 255Boot: Boot code used on system manager terminal to boot server (ASCII
code or null for autoboot)Reason: Code indicating reason for IPL:
0 – Reason not known1 – Power failed2 – Server crashed (interrupt 3)3 – Memory parity failure4 – Server shut down by system manager
DownTime: Shutdown timeLevel: CDR format level of all following CDR records
Serial: Server serial number
IVR_EXITj (Exit IVR application details)
P: Server port number usedType: Reason IVR application was exited:
1 – Port disconnect2 – Exit to mailbox3 – Exit to subscriber mailbox4 – Supervised transfer5 – Blind transfer6 – Exit to open trees7 – Exception occurred
AppID: ID number of application established in SMT menu 17.2Mbox: Type 40 mailbox number
XcptType: Reason exception mailbox was accessed:1 – Application down2 – Application busy3 – Application interrupted
j Appears only when server software is at Aspen Release 2.0 or newer.
CDR EVENT DESCRIPTIONSAPPENDIX B
B-30 Edition 2 Octel PC/CDR
Table B-3. Event Details (Continued).
Field Description
LIST_CHGj (Distribution lists added, modified, or deleted, or message sent to this list)
P: Server port number used
Time: Date and time when mailbox was created; if entry in field shows01-01-84 00:00:00, mailbox was created before this field becameactive
Number: Distribution-list number
Box: Mailbox number of list owner
Who: Identifies who changed the distribution list:
0 – System manager access/change1 – CSA access/change2 – Subscriber access/change
ListType: Identifies type of list:
0 – System distribution list1 – Personal group list2 – Information list
ActType: Identifies type of activity:
0 – Message sent to this list
1 – List added
2 – List deleted
3 – List modified
MD (Message deleted)
P: Server port number used
Why: Code indicates why message was deleted:
0 – Deleted by user
1 – Deleted by purge task
2j – Deleted by information service (IFS) update
3j – Deleted by external application
4j – Deleted by fax auto-delete
Type: Code indicates type of message:
0 – Real message
1j – External-application message
3j – Fax annotation
4j – Fax image
5j – Returned fax image
6j – Compound fax message
255 – Unknown type (internal error)
Stage: Stage of delivery:
0 – Delivered; includes internal stages (future delivery, network-returned message, delivered, and heard)
1 – Archived message
255 – Unknown (internal error)
j Appears only when server software is at Aspen Release 2.0 or newer.
CDR EVENT DESCRIPTIONS APPENDIX B
Octel PC/CDR Edition 2 B-31
Table B-3. Event Details (Continued).
Field Description
MD (Message deleted) (Concluded)
Snd/Rcv: Code indicates type of sender and receiver of message:0 – Message from outside caller to subscriber1 – Message from subscriber to subscriber2 – Message from home to subscriber3 – Message from guest 1 to subscriber4 – Message from guest 2 to subscriber5 – Message to home from subscriber6 – Message to guest 1 from subscriber7 – Message to guest 2 from subscriber
255 – Unknown sender and receiverBox: Mailbox number from which message was deleted
AppID:j ID number of application, established in SMT menu 17.2 (if applicable)
Time: If message not archived when deleted, field indicates date and time ofdelivery
MsgID1: Internal identifier of message segmentLen1:h Total number of seconds of original message or introductory message
(contains –1 if length of segment is too long for internal encoding)Len2:h Total number of seconds of original message (contains –1 if length of
segment is too long for internal encoding or 0 if no messages followthe first)
FaxID:j ID number of fax imageFaxPage:j Length of fax image, in pages
Node:k Node number (1–500) (if applicable)
h If Len2 is blank, Len1 equals the total number of seconds of the original message. However, if the messagehas been copied, the original length moves to Len2, and the length of only the introduction becomes the newLen1.
j Appears only when server software is at Aspen Release 2.0 or newer.k Appears only when server software release is older than Aspen Release 2.0.
CDR EVENT DESCRIPTIONSAPPENDIX B
B-32 Edition 2 Octel PC/CDR
Table B-3. Event Details (Continued).
Field Description
MS (Message sent)
P: Server port number usedType: Code indicates type of message:
0 – Real message1 – Message from external application2j – Reply message3j – Fax annotation4j – Fax image5j – Returned fax message6j – Compound fax image7j – Fax annotation and image (1 call)8j – Fax annotation and image (2 calls)9j – Converted fax message
10j – Forwarded fax image11j – Forwarded fax returned image12l – Voice message returned from hub13l – Fax message returned from hub
255 – Unknown type (internal error)Attr:m Message-attribute flag codes (sum of values):
0 – No special attributes2 – Message deposited by IFS4 – Future delivery requested8 – Message forwarded from another subscriber
16 – Confirmation of nondelivery requested32 – Confirmation of delivery requested64 – Message marked private
128 – Message marked urgent
j Appears only when server software is at Aspen Release 2.0 or newer.l If entry in Type: field is 12 or 13, refer to MS Attr:n for the message-return code; otherwise, refer to MS
Attr:m for message-attribute flag codes. Type: code values 12 and 13 appear only when server software is atAspen Release 4.1, Aria 1.1, or newer.
mIf entry in Type: field is 0–11, refer to this set of attributes; otherwise, refer to MS Attr:n for themessage-return code.
CDR EVENT DESCRIPTIONS APPENDIX B
Octel PC/CDR Edition 2 B-33
Table B-3. Event Details (Continued).
Field Description
MS (Message sent) (Continued)
Attr:n Message-return code:
1 – Destination mailbox not found2 – Wrong mailbox type3 – Destination mailbox full4 – Destination mailbox future-delivery limit exceeded6 – Node deleted7 – Node disabled with the request to return messages8 – Message determined bad (during transmission or during
garbage collect)9 – Node continuously busy
10 – Node continuously ring no answer11 – Node continuously bad line12 – ASCII name mismatch13 – Message blocked by receiving mailbox14 – Receiving mailbox not capable of receiving faxes15 – Receiving port not capable of receiving faxes16 – Receiving node not capable of receiving faxes17 – Transmission port not capable of sending faxes18 – Hub synchronization problem19 – Recipient has extended-absence greeting with blocked
mailbox255 – Unspecified return reason
Snd/Rcv: Code indicating sender and receiver type of message:
0 – Message from outside caller to subscriber
1 – Message from subscriber to subscriber
2 – Message from home to subscriber
3 – Message from guest 1 to subscriber
4 – Message from guest 2 to subscriber
5 – Message to home from subscriber
6 – Message to guest 1 from subscriber
7 – Message to guest 2 from subscriber
255 – Unspecified sender and receiver
DstBox: Mailbox number (receiver) to which message was sent
SrcBox: Originating mailbox number from which message was sent
DstAppID:j Application ID of destination mailbox
SrcAppID:j Application ID of source mailbox
Time: Date and time when message will be delivered
MsgID1: Internal message identifier (first segment)
j Appears only when server software is at Aspen Release 2.0 or newer.n If entry in Type: field is 12 or 13, refer to this set of attributes; otherwise, refer to MS Attr:m for message-flag
codes. Type: code values 12 and 13 appear only when server software is at Aspen Release 4.1, Aria 1.1, ornewer.
CDR EVENT DESCRIPTIONSAPPENDIX B
B-34 Edition 2 Octel PC/CDR
Table B-3. Event Details (Continued).
Field Description
MS (Message sent) (Concluded)
MsgID2: Internal message identifier (second segment)
Len1:h Total number of seconds of original message or introductory message(contains –1 if length of segment is too long for internal encoding)
Len2:h Total number of seconds of original message (contains –1 if length ofsegment is too long for internal encoding or 0 if no messages followthe first)
SegCT: Total number of segments in message
DstNode: Destination network-node ID (0 for this server or 1–500 for the nodenumber)
SrcNode: Source network-node ID (0 for this server or 1–500 for the node number)
FaxID:j ID number of fax image
FaxPart:j Reason for partial fax message:
0 – Entire fax received1 – Too many errors2 – No communication3 – Loss of carrier4 – Time-out5 – Page limit exceeded6 – Disk full
FaxPage:j Length of fax image in pages
NodeType:b Type of node
0 – OctelNet analog node1 – AMIS analog node
255 – Unknown node
MSG_CNTi (Message count)
P: Server port number used
When: Indicates when event count is added:
0 – Count logged when user entered mailbox1 – Count logged when user exited mailbox
UhVoice: Number of unheard voice messages
HdVoice: Number of voice messages heard
ArVoice: Number of archived voice messages
UhFax: Number of unheard fax messages
HdFax: Number of fax messages heard
ArFax: Number of archived fax messages
MBox: Mailbox number
b Appears only when server software is at Aria 1.2 or newer.h If Len2 is blank, Len1 equals the total number of seconds of the original message. However, if the message
has been copied, the original length moves to Len2, and the length of only the introduction becomes the newLen1.
i Appears only when server software is at Aspen Release 4.1, Aria 1.1, or newer.j Appears only when server software is at Aspen Release 2.0 or newer.
CDR EVENT DESCRIPTIONS APPENDIX B
Octel PC/CDR Edition 2 B-35
Table B-3. Event Details (Continued).
Field Description
MSG_RVWi (Message review)
P: Server port number used
Act: Subscriber action:
0 – Playback-Disc; user disconnected while listening to a message
1 – Playback-Exit; user exited message review while listening toa message by pressing the * key
2 – Playback-Pause; user paused a message3 – Playback-Envelope; user got envelope information while
listening to message4 – Playback-Errors; user’s message-review session was termi-
nated because of incurring too many errors5 – Pause-Disc; user disconnected while message was paused6 – Pause-Exit; user exited message review while message was
paused7 – Pause-Replay; user restarted playback of paused message8 – Pause-Envelope; user got envelope information of paused
message9 – Pause-Error; user incurred too many errors while message
was paused10 – Pause-Timeout; user paused a message for too long and
timed out11 – End of Msg-Disc; user disconnected at end of a message12 – End of Msg-Exit; user exited at end of a message13 – End of Msg-Envelope; user got envelope information at end
of a message14 – End of Msg-Forward; user forwarded a message15 – End of Msg-Errors; user incurred too many errors at end of
a message16 – End of Msg-Timeout; user took too long to act upon
message and timed out17 – End of Msg-Erase; user erased message18 – End of Msg-Reply; user replied to message19 – End of Msg-Save; user saved message20 – End of Msg-Print Fax; user printed fax message21 – Skip to archive; user skipped to archived messages by
pressing # #22 – Skip; user skipped message (at some point other than at
end of message)23 – Invalid Key; user pressed an invalid key24 – Help/Operator; user pressed 0 for help or 00 for operator25 – Call Sender; user used a call-sender feature26 – End of Msg-Skip; user skipped message at end of message27 – Exited with Unheard Msgs; user exited with unheard
messages in mailboxMsgID: Message identifier of reviewed message
MBox: Mailbox number
i Appears only when server software is at Aspen Release 4.1, Aria 1.1, or newer.
CDR EVENT DESCRIPTIONSAPPENDIX B
B-36 Edition 2 Octel PC/CDR
Table B-3. Event Details (Continued).
Field Description
MW (Message waiting set/clear)
P: Server port number usedBox: Mailbox number generated MW signalExt: Telephone number signaledDir: Code for setting and clearing MW indicator:
0 – Set to off1 – Set to on
Stat: Set/Clear action result code:0 – PBX successfully told to turn light on/off1 – Set/clear failed but will be retried2 – Set/clear failed because the extension was not valid and will
be retried3 – Set/clear failed; cannot or will not be retried
NNET_ALARMc (NameNet-directory alarm activity)
Type: Code indicates type of activity:0 – Non-service-affecting alarm activated; network directory has
reached directory-full-alarm threshold1 – Service-affecting alarm activated; network directory reached
critical-usage threshold and entries will be deleted2 – Network directory is full
NNET_DIRc (NameNet-directory mismatch or nine of same name exist)
P: Server port number usedType: Code indicates type of activity:
0 – Permanent entries deleted from network directory if mailboxASCII name did not match mailbox user
1 – Entry cannot be created in network directory because nineof the same DTMF names already exist
Node: Node numberMBox: Mailbox numberAlias: Alias address (if any)
NameLen: Number of characters in mailbox ASCII nameName: Mailbox ASCII name
Status: Code indicates type of activity:0 – No status recorded
11 – More than nine of the same name in network directory;name not added
c Appears only when server software is at Aspen Release 3.0 or newer.
CDR EVENT DESCRIPTIONS APPENDIX B
Octel PC/CDR Edition 2 B-37
Table B-3. Event Details (Continued).
Field Description
NNET_NAMEc (NameNet-transmission or receipt of ASCII or spoken name)
P: Server port number usedType: Code indicates type of activity:
0 – Network transmission side requested and then received spoken name
1 – Network receiving side received request for spoken nameand then transmitted spoken name to requester
2 – Network transmission side requested and then receivedASCII name
3 – Network receiving side request for ASCII name and thentransmitted ASCII name to requester
4i – Requested mailbox ASCII name received by hub5i – Requested mailbox spoken name received by hub
Node: Node numberMBox: Mailbox numberAlias: Alias address (if any)
Status: Code indicates status of NameNet activity:0 – Successful transmission or receipt1 – Mailbox type not allowed in network directory2 – Mailbox does not exist5 – Spoken name not recorded8 – Spoken name corrupted9 – Name added to network directory; not an error
12 – Unable to update network directory
14 – Server full
OC (Outcall to subscriber, pager, or fax)
P: Server port number usedBox: Mailbox number generating outcall
AppID:j ID number of application established in SMT menu 17.2Sched: Outcall schedule used:
0 – Temporary schedule1 – Outcall schedule 1 used2 – Outcall schedule 2 used3j – Outcall requested4 – No schedule used; fax printing
Number: Telephone number called
c Appears only when server software is at Aspen Release 3.0 or newer.i Appears only when server software is at Aspen Release 4.1, Aria 1.1, or newer.j Appears only when server software is at Aspen Release 2.0 or newer.
CDR EVENT DESCRIPTIONSAPPENDIX B
B-38 Edition 2 Octel PC/CDR
Table B-3. Event Details (Continued).
Field Description
OC (Outcall to subscriber, pager, or fax) (Concluded)
Pager: Pager code sequence used:
0 – No pager used
1 – Pager sequence 1 used
2 – Pager sequence 2 used
3 – Pager sequence 3 used
4o – Pager sequence 4 used
5o – Pager sequence 5 used
6o – Pager sequence 6 used
Type:j Type of outcall number:
0 – On PBX
1 – Local
2 – Local area code
3 – Long distance
Stat: Result code of outcall:
0 – Call answered
1 – Telephone number dialed: busy
2 – Telephone number dialed; ring no answer
3 – Telephone number dialed; fast-busy
TransID:j Transmission ID number (assigned internally)
OCL_NAME (Reserved for future applications)
ON_HOOK (Port goes on hook)
P: Server port number used
TransID:j Transmission ID number (assigned internally)
PORTS_BUSYj (All ports busy)
Duration: Busy duration, in seconds
PROFILE_CHGj (Mailbox profile changed)
Number: Profile number
ProfileType: Type of profile changed:
0 – Node
1 – Community
2 – Cluster table
3 – Callers menu
ChgType: Identifies action taken:
0 – Profile created
1 – Profile deleted
2 – Profile modified
j Appears only when server software is at Aspen Release 2.0 or newer.o Appears only when server software is at Aspen Release 1.5 or newer.
CDR EVENT DESCRIPTIONS APPENDIX B
Octel PC/CDR Edition 2 B-39
Table B-3. Event Details (Continued).
Field Description
PWT (Password test)
P: Server port number used
Box: Mailbox number used for sign in
Result: Password result code:
0 – Password valid
1 – Password invalid
2 – Password valid, but already signed into mailbox
PWType: Password type code used (if valid):
0 – User (subscriber) password code used
1 – Secretary password code used
2 – Home password code used
3 – Guest 1 password code used
4 – Guest 2 password code used
PWT_RJCT (Bad-password limit)
P: Server port number used
Box: Mailbox number used for sign in
Threshold: Bad-password-disconnect threshold limit
RSS (Reset scanner board channel)
P: Server port number used
SEIZE (Seize port for outgoing call)
P: Server port number used
TransID:j Transaction ID number (assigned internally)
SESSION (Reserved for future applications)
SMS (Session mode set)
P: Server port number used
Mode: Session-mode code:
0 – Idle, not signed on—open trees
1 – Telephone-answering mode
2 – Voice-messaging mode
3j – Visit mailbox
Box: Mailbox number entered, indicates when new mailbox has been entered; blank if caller enters idle mode (open trees)
AppID:j ID number of application, established in SMT menu 17.2
SMSG_ALERT (Reserved for future applications)
SMSG_DELVR (Reserved for future applications)
SMSG_INFO (Reserved for future applications)
SMSG_REPORT (Reserved for future applications)
j Appears only when server software is at Aspen Release 2.0 or newer.
CDR EVENT DESCRIPTIONSAPPENDIX B
B-40 Edition 2 Octel PC/CDR
Table B-3. Event Details (Continued).
Field Description
SMSG_STFWD (Reserved for future applications)
TIGON (Used only by Octel Network Services)
TNE (Trees, normal entry)
P: Server port number usedCallType: Call-type code indicates when an incoming call enters the server:
0 – Direct call from outside the PBX/Centrex or for noninte-grated servers
1 – Direct call from inside PBX/Centrex2 – Direct call from attendant3 – Forwarded to the server from a busy line4 – Forwarded to the server from a ring-no-answer line; either
code 3 or 4 can be used for forwarding all calls; varies withPBX
5j – Forwarded on all callsCaller: Calling-party telephone numberCallee: Called-party telephone number, if available
TREES_FCD (Forms-mailbox call data)
Start: Date and time of beginning of callCaller: Calling-party telephone number
TREES_FMB (Forms-mailbox number)
P: Server port number usedMailbox: Forms-mailbox number
TREES_FQA (Forms-mailbox question/answer)
P: Server port number usedQuestion: Question reference number (If 9999, indicates caller pressed key to
return to first question in form or to previous form)Answer: Touch-tone response by caller to forms question
TRS (Trees, restart entry)
P: Server port number used
TUTb (Messaging tutorial)
P: Server port number usedType: Identifies which messaging-tutorial prompt was played
1 – Send prompt played2 – Reply prompt played
Mbox: Identifies the mailbox in which the messaging tutorial was played
b Appears only when server software is at Aria 1.2 or newer.j Appears only when server software is at Aspen Release 2.0 or newer.
CDR EVENT DESCRIPTIONS APPENDIX B
Octel PC/CDR Edition 2 B-41
Table B-3. Event Details (Continued).
Field Description
UR_CHGj (User record change)
P: Server port number usedTime: Date and time when user record was created (If entry in field shows
01-01-84 00:00:00, the user record was created before this fieldbecame active)
Box: Mailbox number for which user record was changedMboxType: Type of mailbox
ActType: Identifies action taken:0 – Mailbox created1 – Mailbox deleted2 – Mailbox modified
ModType: Identifies what was modified:0 – Password changed to new value1 – Password changed to old value2 – Standard greeting changed to personal greeting3 – Personal greeting changed to standard greeting4 – Personal greeting changed to personal greeting5 – Mailbox initialized6 – Any other user-record change
Who: Identifies who changed the user record:0 – System manager1 – CSA2 – Garbage collect3 – Purge task4 – User
PWLen: Number of digits in password (Ignore the entry in this field if entry inModType: field not a 0 or a 1)
PWType: Identifies password type used (Ignore the entry in this field if entry inModType: field not a 0 of a 1):
0 – Subscriber1 – Secretary2 – Home3 – Guest 14 – Guest 2
j Appears only when server software is at Aspen Release 2.0 or newer.
CDR EVENT DESCRIPTIONSAPPENDIX B
B-42 Edition 2 Octel PC/CDR
Table B-3. Event Details (Concluded).
Field Description
XFR (Transfer)
P: Server port number usedSrc: Source code indicates how the transfer telephone was determined:
0 – Explicit attendant number given1 – Attendant 1 extension (unassigned or invalid attendant de-
fined in mailbox, department, or community)2 – Valid port group defined3 – Port group 1 (valid port group not defined)4 – Extension given (ECP mailbox)5 – Mailbox attendant extension6 – Group attendant extension7 – Community attendant extension8j – Attendant number defined at mailbox level9j – Attendant number defined at department level
10j – Attendant number defined for community11d – Transferred to message sender
Ext: The extension to which the call was transferredStat: Transfer status code:
0 – Blind transfer, no answer supervision1 – Transfer; answered2 – Transfer; telephone number busy3 – Transfer; telephone number not answered4 – Transfer; telephone number fast-busy5 – Transfer; telephone number detected, answered by the
server6k – Operator blind transfer; no answer supervision7k – Operator transfer; answered8k – Operator transfer; telephone number busy9k – Operator transfer; telephone number not answered
10k – Operator transfer; telephone number fast-busy11k – Operator transfer; telephone number detected, answered by
the serverAppID:j ID number of application established in SMT menu 17.2
d Appears only when server software is at Aspen Release 4.0 or newer.j Appears only when server software is at Aspen Release 2.0 or newer.k Appears only when server software release is older than Aspen Release 2.0.
A CP P E N D I X
Octel PC/CDR Edition 2 C-1
CDR EVENT BYTE SIZES BY RECORDGROUP
Specific events are recorded in the CDR buffer, based on the record groupsselected in SMT menu 16.1.4. Consider the approximate number of bytes ineach event, the frequency at which the event occurs, and the available bufferand PC storage space when selecting record groups to be collected. Table C-1through Table C-11 show the approximate byte size of each event.
If specific events are needed for diagnostic purposes, use these tables todetermine which record groups to select so that the needed events are collected.
The events in Table C-1 are collected if at least one record group is selected.
The term tree, as used in this appendix, refers to the software that provides aninterface between a caller and the server. For example, the term open trees is theentry point that a caller reaches after calling the server. From open trees, callersthen dial an extension to be transferred to or identify themselves as subscribersby pressing the # key.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table C-1. Bytes for Events Collected if AnyRecord Group Is Selected.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Event Name
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Description
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Approx.Number of
BytesÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CDRCFGÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CDR configurationÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
38
ÁÁÁÁÁÁÁÁÁÁÁÁ
DTS ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Set date and time ÁÁÁÁÁÁÁÁÁÁ
15ÁÁÁÁÁÁÁÁÁÁÁÁIPL
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁServer initial program load
ÁÁÁÁÁÁÁÁÁÁ24ÁÁÁÁÁÁ
ÁÁÁÁÁÁNNET_ALARMaÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁDirectory alarm activity
ÁÁÁÁÁÁÁÁÁÁ7ÁÁÁÁÁÁ
ÁÁÁÁÁÁNNET_DIRaÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁDirectory mismatch or nine of same name exist
ÁÁÁÁÁÁÁÁÁÁ49ÁÁÁÁÁÁ
ÁÁÁÁÁÁNNET_NAMEaÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁTransmission or receipt of ASCII or spoken name
ÁÁÁÁÁÁÁÁÁÁ27ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
a Appears only when server software is at Aspen Release 3.0 or newer.
CDR EVENT BYTE SIZES BY RECORD GROUPAPPENDIX C
C-2 Edition 2 Octel PC/CDR
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table C-2. Bytes for Events Collected With SessionRelated Records (Record Group 2).
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Event Name
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Description
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Approx.Number of
Bytes
ÁÁÁÁÁÁÁÁÁÁÁÁ
CALLER ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Caller identification ÁÁÁÁÁÁÁÁÁÁÁÁ
15ÁÁÁÁÁÁÁÁÁÁÁÁ
GEN_ERRbÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
General system error ÁÁÁÁÁÁÁÁÁÁÁÁ
39ÁÁÁÁÁÁÁÁÁÁÁÁ
IC ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Incoming call ÁÁÁÁÁÁÁÁÁÁÁÁ
11ÁÁÁÁÁÁÁÁÁÁÁÁ
IVR_EXITa ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Exit IVR application details ÁÁÁÁÁÁÁÁÁÁÁÁ
19ÁÁÁÁÁÁÁÁÁÁÁÁ
OC ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Outcall to subscriber, pager, or faxÁÁÁÁÁÁÁÁÁÁÁÁ
37ÁÁÁÁÁÁÁÁÁÁÁÁ
ON_HOOKÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Port goes on hook ÁÁÁÁÁÁÁÁÁÁÁÁ
11ÁÁÁÁÁÁÁÁÁÁÁÁ
PWT ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Password test ÁÁÁÁÁÁÁÁÁÁÁÁ
17ÁÁÁÁÁÁÁÁÁÁÁÁ
RSS ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Reset scanner board channel ÁÁÁÁÁÁÁÁÁÁÁÁ
7
ÁÁÁÁÁÁÁÁÁÁÁÁ
SEIZE ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Seize port for outgoing call ÁÁÁÁÁÁÁÁÁÁÁÁ
11
ÁÁÁÁÁÁÁÁÁÁÁÁ
SMS ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Session mode set ÁÁÁÁÁÁÁÁÁÁÁÁ
18
ÁÁÁÁÁÁÁÁÁÁÁÁ
TNE ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Trees, normal entry ÁÁÁÁÁÁÁÁÁÁÁÁ
24
ÁÁÁÁÁÁÁÁÁÁÁÁ
TRS ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Trees, restart entry ÁÁÁÁÁÁÁÁÁÁÁÁ
7
ÁÁÁÁÁÁÁÁÁÁÁÁ
TUTb ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Messaging tutorial ÁÁÁÁÁÁÁÁÁÁÁÁ
16ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
XFRÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
TransferÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
19
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
a Appears only when server software is at Aspen Release 2.0 or newer.b Appears only when server software is at Aria 1.2 or newer.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table C-3. Bytes for Events Collected WithMessage Send/Delete/Print Records
(Record Group 3).ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Event Name
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Description
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Approx.Number of
Bytes
ÁÁÁÁÁÁÁÁÁÁÁÁ
AM_SEND ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS message queued ÁÁÁÁÁÁÁÁÁÁÁÁ
56
ÁÁÁÁÁÁÁÁÁÁÁÁ
FPa ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Fax image printed ÁÁÁÁÁÁÁÁÁÁÁÁ
65
ÁÁÁÁÁÁÁÁÁÁÁÁ
FRa ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Fax image received ÁÁÁÁÁÁÁÁÁÁÁÁ
33
ÁÁÁÁÁÁÁÁÁÁÁÁ
FRTSa ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Fax returned to sender ÁÁÁÁÁÁÁÁÁÁÁÁ
42
ÁÁÁÁÁÁÁÁÁÁÁÁ
MD ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Message deleted ÁÁÁÁÁÁÁÁÁÁÁÁ
35ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
MSÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Message sentÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
56
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
a Appears only when server software is at Aspen Release 2.0 or newer.
CDR EVENT BYTE SIZES BY RECORD GROUP APPENDIX C
Octel PC/CDR Edition 2 C-3
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table C-4. Bytes for Events Collected WithNetwork Related Records (Record Group 4).
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Event Name
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Description
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Approx.Number of
Bytes
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_DIR_FULLÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS directory 90% fullÁÁÁÁÁÁÁÁÁÁÁÁ
6ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_EAR_FULLÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS EAR (extended-address-record) array 90% fullÁÁÁÁÁÁÁÁÁÁÁÁ
6ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_RCV_EOS ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
End-of-AMIS session received ÁÁÁÁÁÁÁÁÁÁÁÁ
9ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_RCV_IC ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Incoming AMIS call ÁÁÁÁÁÁÁÁÁÁÁÁ
7ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_RCV_INVPH ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Invalid AMIS system-access telephone numberreceived
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
9
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁAM_RCV_MSG
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁAMIS message-recording status received
ÁÁÁÁÁÁÁÁÁÁÁÁ8ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁAM_RCV_MSGI
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS message attribute receivedÁÁÁÁÁÁÁÁÁÁÁÁ
27ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_RCV_PHNUMÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Caller’s AMIS system-access telephone numberÁÁÁÁÁÁÁÁÁÁÁÁ
22ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_RCV_STARTÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS start session receivedÁÁÁÁÁÁÁÁÁÁÁÁ
8ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_RTSÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS message returned to senderÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
52
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_XMT_EOM ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
End-of-AMIS message frame transmitted ÁÁÁÁÁÁÁÁÁÁÁÁ
8
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_XMT_EOS ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
End-of-AMIS session transmitted ÁÁÁÁÁÁÁÁÁÁÁÁ
9
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_XMT_MBOX ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS logged bad sender’s mailbox number ÁÁÁÁÁÁÁÁÁÁÁÁ
9
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_XMT_MINFO ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS-message information transmitted ÁÁÁÁÁÁÁÁÁÁÁÁ
25
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_XMT_OC ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Start of AMIS outcall ÁÁÁÁÁÁÁÁÁÁÁÁ
51
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_XMT_PHNUMÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS server telephone number transmitted ÁÁÁÁÁÁÁÁÁÁÁÁ
20ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_XMT_START ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS start session transmitted ÁÁÁÁÁÁÁÁÁÁÁÁ
8ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_XMT_VOICE ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS transmitted voice ÁÁÁÁÁÁÁÁÁÁÁÁ
28ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
BN_EOS ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
OctelNet end of session ÁÁÁÁÁÁÁÁÁÁÁÁ
20ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
BN_IC ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Incoming call from OctelNet node ÁÁÁÁÁÁÁÁÁÁÁÁ
7ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁBN_MULTILINEa
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁMultiline networking task started
ÁÁÁÁÁÁÁÁÁÁÁÁ30ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁBN_OCÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁOutcall to an OctelNet node
ÁÁÁÁÁÁÁÁÁÁÁÁ63ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁBN_RCV_CPÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁOctelNet message copy received
ÁÁÁÁÁÁÁÁÁÁÁÁ21ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁBN_RCV_HDRÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁOctelNet message header received
ÁÁÁÁÁÁÁÁÁÁÁÁ30ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
BN_RCV_SPÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
OctelNet special message receivedÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
28
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
BN_RCV_START ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
OctelNet receive mode started ÁÁÁÁÁÁÁÁÁÁÁÁ
19
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
BN_RCV_VOICE ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
OctelNet message received ÁÁÁÁÁÁÁÁÁÁÁÁ
30
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
BN_RTS ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
OctelNet message returned to sender ÁÁÁÁÁÁÁÁÁÁÁÁ
62
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
BN_XMT_CP ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
OctelNet message copy transmitted ÁÁÁÁÁÁÁÁÁÁÁÁ
21ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
BN_XMT_HDRÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
OctelNet message header transmittedÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
30
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
BN_XMT_SP ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
OctelNet special message transmitted ÁÁÁÁÁÁÁÁÁÁÁÁ
28
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
BN_XMT_START ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
OctelNet transmit mode started ÁÁÁÁÁÁÁÁÁÁÁÁ
19
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
BN_XMT_VOICE ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
OctelNet message transmitted ÁÁÁÁÁÁÁÁÁÁÁÁ
36
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
a Reserved for future use.
CDR EVENT BYTE SIZES BY RECORD GROUPAPPENDIX C
C-4 Edition 2 Octel PC/CDR
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table C-5. Bytes for Events Collected WithInvalid Password Disconnect Records
(Record Group 5).
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Event Name
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Description
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Approx.Number of
Bytes
ÁÁÁÁÁÁÁÁÁÁ
PWT_RJCTÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Bad-password limit ÁÁÁÁÁÁÁÁÁÁ
17
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table C-6. Bytes for Events Collected WithMessage Waiting Notification Records
(Record Group 6).ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Event Name
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Description
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Approx.Number of
BytesÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
MWÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Message waiting set/clearÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
25
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table C-7. Bytes for Events Collected With DTMF Forms Mailbox Records
(Record Group 7).
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Event Name
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Description
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Approx.Number of
Bytes
ÁÁÁÁÁÁÁÁÁÁÁÁ
FCE ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
OctelForms mailbox end of sessionÁÁÁÁÁÁÁÁÁÁÁÁ
7ÁÁÁÁÁÁÁÁÁÁÁÁ
TREES_FCDÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Forms-mailbox call data ÁÁÁÁÁÁÁÁÁÁÁÁ
19ÁÁÁÁÁÁÁÁÁÁÁÁ
TREES_FMBÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Forms-mailbox number ÁÁÁÁÁÁÁÁÁÁÁÁ
15ÁÁÁÁÁÁÁÁÁÁÁÁ
TREES_FQAÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Forms-mailbox question/answer ÁÁÁÁÁÁÁÁÁÁÁÁ
17
CDR EVENT BYTE SIZES BY RECORD GROUP APPENDIX C
Octel PC/CDR Edition 2 C-5
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table C-8. Bytes for Events Collected With ReportingRelated Records (Record Group 8).a
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Event Name
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Description
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Approx.Number of
Bytes
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CALLMNU ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Caller’s menu event ÁÁÁÁÁÁÁÁÁÁ
25ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
DISK_USG ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Disk-usage event ÁÁÁÁÁÁÁÁÁÁ
30ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
LIST_CHG ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Distribution lists added, modified, ordeleted, or message sent to this list
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
30
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
PORTS_BUSYÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
All ports busy ÁÁÁÁÁÁÁÁÁÁ
8
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
PROFILE_CHGÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Mailbox profile changed ÁÁÁÁÁÁÁÁÁÁ
16
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
UR_CHG ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
User record changed ÁÁÁÁÁÁÁÁÁÁ
25
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
a The Reporting Related Records record group is only available when the serversoftware is at Aspen Release 2.0 or newer.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table C-9. Bytes for Events Collected WithMessage Count Records
(Record Group 9).a
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Event Name
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Description
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Approx.Number of
BytesÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
MSG_CNTÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Message countÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
28
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
a The Message Count Records record group is only available when theserver software is at Aspen Release 4.1, Aria 1.1, or newer.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table C-10. Bytes for Events Collected WithMessage Review Records
(Record Group 10).a
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Event Name
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Description
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Approx.Number of
BytesÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
MSG_RVWÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Message reviewÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
20
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
a The Message Review Records record group is only available when theserver software is at Aspen Release 4.1, Aria 1.1, or newer.
CDR EVENT BYTE SIZES BY RECORD GROUPAPPENDIX C
C-6 Edition 2 Octel PC/CDR
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table C-11. Bytes for Miscellaneous Events.
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Event Name
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Description
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Approx.Number of
Bytes
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_RCV_FCa ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AMIS function code received ÁÁÁÁÁÁÁÁÁÁÁÁ
8ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_RCV_FRa ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Status of received AMIS frame ÁÁÁÁÁÁÁÁÁÁÁÁ
9ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_RCV_RESPaÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Acknowledgment sent for AMIS-received frame ÁÁÁÁÁÁÁÁÁÁÁÁ
8ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
AM_XMT_RESPaÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Acknowledgment received from server ÁÁÁÁÁÁÁÁÁÁÁÁ
8ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CNN_ENABLE ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Reserved for future applications ÁÁÁÁÁÁÁÁÁÁÁÁ
23ÁÁÁÁÁÁÁÁÁÁÁÁÁÁCNN_OCL_MB
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁReserved for future applications
ÁÁÁÁÁÁÁÁÁÁÁÁ41ÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁCNN_OCL_VM
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Reserved for future applicationsÁÁÁÁÁÁÁÁÁÁÁÁ
28ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CNN_PRIVACYÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Reserved for future applicationsÁÁÁÁÁÁÁÁÁÁÁÁ
21ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CNN_VC_LINKÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Reserved for future applicationsÁÁÁÁÁÁÁÁÁÁÁÁ
29ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
DM_PSEUDOb ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Missing start or end of call; for internal use onlyÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
42
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
GET_ROUTE ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Reserved for future applications ÁÁÁÁÁÁÁÁÁÁÁÁ
27ÁÁÁÁÁÁÁÁÁÁÁÁÁÁOCL_NAME
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁReserved for future applications
ÁÁÁÁÁÁÁÁÁÁÁÁ17ÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁSESSIONÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁReserved for future applications
ÁÁÁÁÁÁÁÁÁÁÁÁ9ÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁSMSG_ALERTÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁReserved for future applications
ÁÁÁÁÁÁÁÁÁÁÁÁ22ÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
SMSG_DELVRÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Reserved for future applicationsÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
23
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
SMSG_INFO ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Reserved for future applications ÁÁÁÁÁÁÁÁÁÁÁÁ
13
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
SMSG_REPORTÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Reserved for future applications ÁÁÁÁÁÁÁÁÁÁÁÁ
14
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
SMSG_STFWD ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Reserved for future applications ÁÁÁÁÁÁÁÁÁÁÁÁ
7
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
TIGON ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Used only by Octel Network Services ÁÁÁÁÁÁÁÁÁÁÁÁ
17
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
a Appears only when certain service-related functions are performed.b Appears only when server software is at Aspen Release 2.0 or newer.
A DP P E N D I X
Octel PC/CDR Edition 2 D-1
SUBDIRECTORY FILES
During installation, files are copied from the Octel PC/CDR floppy disk to theCDR PC hard drive and organized into subdirectories. Table D-1 lists the files inthe OCTELCDR subdirectory. Table D-2 lists the files in the MIR subdirectory.Table D-3 lists the files in the CC subdirectory. The LOG subdirectory containsone file, SCHEDCDR.LOG, which is appended after each scheduled downloadoccurs. As CDR systems are created, a [cdr system name].BAT file is added tothe OCTELCDR subdirectory for each system created.
Table D-1. OCTELCDR Subdirectory Files.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁFile Names
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
File NamesÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
COLGRPÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
COMPRSM.EXEÁÁÁÁÁÁÁÁÁÁÁÁÁÁCDRCLEAN.BAT
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁCOMPRSN.EXEÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁMKCDRSYS.BAT
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
COMPRSP.EXEÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
RMCDRSYS.BATÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
COMPRSR.EXEÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
LOGO.DAT ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
COMPRSU.EXEÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
SYSNAME.DAT ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
COMPRSX.EXE
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CDFS.EXE ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
COPYBCF.EXE
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CDR.EXE ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
DUMPBCF.EXEÁÁÁÁÁÁÁÁÁÁÁÁÁÁCDRERASE.EXE
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁDUMPSF.EXEÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CDRHELP.EXEÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
DV_MAIN.EXEINSTCDR.EXE
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CDRMENU.EXEÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
LOGO.EXEÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CDRSYSNM.EXEÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
MIRROR.EXEÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CHKREV.EXE ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
SCHEDCDR.EXE
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
COLLATE.EXE ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
SCHEDEDT.EXEUPGRCDR.EXEÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁCOMPRSB.EXEÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁMIRROR.HLPÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁCOMPRSC.EXE
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
SCHEDCDR.PARa
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
COMPRSD.EXE ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CDRP.SNÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
COMPRSF.EXE ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ANSI.SYSÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
a This file is created when the first auto-matic processing schedule is added.
Table D-2. MIR Subdirectory Files.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
File NamesÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
File Names
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ANSI.MEF ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
LANGUAGE.XTKÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
VT100.MEF ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CDRDOWNL.XTS
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
WY50SPEC.MEFÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
LINKSMT.XTSÁÁÁÁÁÁÁÁÁÁÁÁÁÁCDRDOWNL.XTK
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁLOGOFF.XTSÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
SUBDIRECTORY FILESAPPENDIX D
D-2 Edition 2 Octel PC/CDR
Table D-3. CC Subdirectory Files.ÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁFile Names ÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
File NamesÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CC30.CFGÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CCINSTAL.EXEÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
MM30.CFG ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CCLOG.EXEÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
MODEM.DSC ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CCREMOVE.EXEÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CC.EXE ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
CCSECURE.EXE
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
A EP P E N D I X
Octel PC/CDR Edition 2 E-1
TRANSMISSION MESSAGES
Transmission messages are displayed on the CDR PC screen when an erroroccurs during the download of data from a server. The transmission messagesfrom the server that could appear are shown in Table E-1. Transmissionmessages from the CDR PC are shown in Table E-2.
Table E-1. Transmission Messages From the Server.
If you get this message . . . This has occurred . . . And you need to do this . . .
Cancelled by receiver.
The file-transfer process fromthe server to the PC was can-celed by the PC operator.
If not correct, restart the file-transfer process, beginning atthe initial block number.
Error transmissionlimit reached.
The transmission-error countexceeded system limits.(XMODEM determined 10consecutive errors.)
Check connections between thePC and the server. There couldbe a malfunctioning modem,connector, cable, or COM port.This error could also be causedby a bad telephone line.
Starting blocknumber is not valid.
Either an incorrect starting-block number was used inSMT menu 16.1.2 or data hasbeen overwritten.
Use SMT menu 16.1.1 to displaycurrent, valid block numbers. Ifdata has been overwritten, useSMT menu 16.1.3 to clear thelost-data counter, and then retrythe process.
There are older unread blocks thanthe starting blockspecified.
A starting-block number thatdoes not sequentially followthe last block retrieved wasrequested. This is not per-mitted, as this creates orleaves a gap in the CDR re-cord blocks downloaded fromthe server.
Refer to Chapter 7 for instruc-tions about selecting block num-bers, and then enter either thenext block number of data notpreviously retrieved or an earlierblock number. Do not downloadblocks that were previouslycollated. Because collated dayfiles (CDFs) are appended eachtime a BCF is collated, duplicatedata is added to the database ifa BCF containing previouslycollated blocks is collated morethan once. Use SMT menu 16.1.1to determine the number of thefirst block not retrieved.
Unable to establishsynchronizationwith receiver.
The communications port be-tween the PC and the serveris not functioning correctly.
Check data communicationsparameters (refer to section5.3.7). Retry the file-transfer sequence.
TRANSMISSION MESSAGESAPPENDIX E
E-2 Edition 2 Octel PC/CDR
Table E-2. Transmission Messages From the CDR PC.
If you get this message . . . This has occurred . . . And you need to do this . . .
File Transfer Error -Aborted by User.
The F3 key was pressed. Restart the download processif it was canceled in error.
File Transfer Error - Carrier Lost.
The link between the server andthe PC stopped functioning.
Verify that the modem link isfunctioning correctly, andrestart the download.
File Transfer Error - Local File Problem(Disk Full).
The hard drive on the PC is full.Data cannot be downloaded, be-cause there is no storage space.
Back up and delete old files,then restart the download process.
File Transfer Error -Timeout (No Responsefrom VPMOD).
The server is too busy. Restart the download processwhen there is less traffic onthe server.
File Transfer Error -Transfer Not Initiatedby VPMOD.
An attempt was made to down-load an overwritten or emptyblock.
If blocks are overwritten, access SMT menu 16.1.3 toclear the Call Detail RecordingLost Data Counter (refer tosection 2.4.5). Otherwise, con-firm that the first block to bedownloaded is a valid block.
File Transfer Termi-nate Due to VPMODBusy.
The main SMT port or the re-mote service-access port on theserver is already in use.
Restart the download processat a later time when the SMTport is available.
Incorrect Password,Fix In The PC/CDRSystem ParametersMenu.
The password established forthis server is not correct.
Verify and correct, if neces-sary, the password entered inthe Modify PC Communica-tions Parameters Menu screen(section 5.3.7).
Timeout Waiting forPassword Prompt.
The server never returned theprompt Please Enter SystemManager Password.
Restart download process.This error could occurbecause of poor line quality.
VPMOD Busy or Transmission Error.
The remote link to the server isalready in use.
Restart download process at alater time. If this error occursrepeatedly, check connectionsbetween the PC and the serv-er. This error could be causedby a malfunctioning modem,connector, cable, or port.
A FP P E N D I X
Octel PC/CDR Edition 2 F-1
SCHEDULE-LOG-FILE ENTRIES
Entries are logged in the schedule-log file when functions are performed orerrors occur related to either the scheduled automatic processing of CDR data orthe maintenance of the scheduled-automatic-processing files (the schedule-logfile and the schedule parameter file). The following list is not complete, butincludes the log-file entries that occur most often. Refer to Chapter 7 for informa-tion about scheduled automatic CDR processing.
In some instances, the date and time of the entry are noted. The date is repre-sented by mm-dd-yy, which represents month, day, and year, respectively. Thetime is represented by hh:mm, where hh is the hour and mm is minutes, using24-hour time (for example, 13:18 is 1:18 p.m.).
F.1 ENTRIES REQUIRING ACTION
When the following entries appear in the schedule-log file, the system managermust respond, as follows:
When the schedule-log-fileentry reads . . . This has occurred . . . And you need to . . .
>> mm-dd-yy hh:mmSCHEDCDR: PasswordEntry Failure.
The schedule password wasincorrectly entered threetimes.
Confirm that the password iscorrect. Watch for unautho-rized users.
Error restoring log file. The backed-up log file is noton the floppy disk, or thefile is corrupted.
Confirm that the floppy diskcontains the file that wasbacked up using the BackupSchedule Log File option(Chapter 7).
Error restoring sched-ules file C:\OCTELCDR\SCHEDCDR.PAR.
The backed-up scheduleparameter file is not on thefloppy disk, or the file iscorrupted.
Confirm that the floppy diskcontains the file that wasbacked up using the BackupSchedule Parameter Fileoption (Chapter 7).
SCHEDULE-LOG-FILE ENTRIESAPPENDIX F
F-2 Edition 2 Octel PC/CDR
F.2 ENTRIES NOT REQUIRING ACTION
The following entries are for information only and do not require action:
When the schedule-log-file entry reads . . . This has occurred . . .
>> mm-dd-yy hh:mm SCHEDCDR:Shutdown.
The Octel PC/CDR Main Menu option 2, Automatic Scheduler Functions, was exited.
>> mm-dd-yy hh:mm SCHEDCDR:Startup.
Option 2, Automatic Scheduler Functions,was selected from the Octel PC/CDR MainMenu.
>> mm-dd-yy hh:mm SCHEDEDT:Shutdown.
Option 1 or option 4 from the Octel PC/CDRAutomatic Schedule Menu was exited.
>> mm-dd-yy hh:mm SCHEDEDT:Startup.
Option 1 or option 4 from the Octel PC/CDR Automatic Schedule Menu was selected.
mm-dd-yy hh:mm: Begin ProcessingSchedule # 1 - [schedule name], System/ Program # [system/programnumber] - [CDR system name]
Processing of the designated schedule num-ber began at this date and time. No addi-tional entry is made when the process iscompleted or if the process is interruptedand not completed.
mm-dd-yy hh:mm: New log opened after backup. Backed up file C:\OCTELCDR\ LOG\ Syymmdd.LOG to drive A:.
The schedule-log file was erased after it wasbacked up using the Backup Schedule LogFile option, and a new log file was opened.
mm-dd-yy hh:mm: Previous log contents erased. New log opened after erase.
The Erase Schedule Log File utility was usedto erase the schedule-log file.
Backed up file C:\OC-TELCDR\SCHEDCDR.PAR to drive A:.
Schedule parameters were backed up usingthe Backup Schedule Parameter File option.
Restored file C:\OCTELCDR\SCHEDCDR.PAR from drive A:.
Schedule parameters were restored usingthe Restore Schedule Parameters option.
Restored log files from drive A:. The schedule-log file was copied to the \OCTELCDR\LOG subdirectory on the harddrive using the Restore Schedule Log Fileoption.
A GP P E N D I X
Octel PC/CDR Edition 2 G-1
OCTEL PC/CDR TROUBLESHOOTINGFORM
Before calling your Octel service representative or distributor for assistance,please make a copy of this form and take a few minutes to answer all of thequestions. Print the requested screens and files so you have the informationavailable for reference when you call for assistance.
All instructions in this appendix requiring DOS-file access assume that the CDRPC boot drive is drive C and all commands are executed from drive C. If yourboot drive is a different drive, substitute that drive letter wherever drive C isreferenced.
1. From what type of server are you attempting to download?
2. At what software release is this server (from SMT menu 13.7)?
3. What release of Octel PC/CDR software are you using?
4. On what type of personal computer is the Octel PC/CDR software loaded?(386, 486, Pentium, or ?)
5. What is the brand name and model number of the PC?
6. Is the PC also used to run Windows applications?
7. What terminate-and-stay resident (TSR) utilities are loaded?
8. Is a modem being used to connect the Octel PC/CDR application to theserver?
9. If yes, what kind of modem is it?
10. What is the baud rate selected for the Octel PC/CDR download?
11. What is the baud rate of the server?
OCTEL PC/CDR TROUBLESHOOTING FORMAPPENDIX G
G-2 Edition 2 Octel PC/CDR
12. Print the following files from the PC using the screen-print function or theDOS type command. If neither of these methods work, write down theinformation or have the PC available when you call for service.
� Print the AUTOEXEC.BAT file.
� Print the CONFIG.SYS file.
13. Create hard-copy printouts of the following commands executed from theDOS prompt:
� chkdsk (checks the disk for errors)
� set (lists the current operating-system parameters)
� ver (displays the version of DOS being used)
� mem/debug, if DOS version is 4.0 or higher (displays information aboutthe system environment)
Follow the steps given here:
Step Action Result
a. At the DOS prompt, type C:\. The DOS prompt changes to C:\.
b. Type cls, and press Enter. The screen is cleared, leavingonly the DOS prompt visible.
c. Type the command (from the list above),and press Enter.
Information is displayed on thescreen.
d. If more than one screen’s worth of informa-tion is displayed, type the command again,this time followed by >prn.
The information is sent directlyto the printer and printed. It isnot displayed on the screen.
To send one screen of information to theprinter at a time,
1. Press the Shift and Print Screen keyssimultaneously.
The displayed screen is printed.
2. Repeat steps a, b, and c to continue displaying and printing the remaininginformation, one screen at a time.
The remaining screens areprinted, one screen at a time.
14. If this is a data-interpretation or output-file issue, have the BCF or PCFavailable. What is the name of the BCF or PCF?
15. Print the page of the Octel PC/CDR log file that shows the last time the CDRdownload was performed. To access and print the log file, refer to Chapter 8.
16. Print the Octel PC/CDR System Attributes Menu (Figure 5-3) that shows theoutput-file-format level selected.
17. Print the Modify PC Communications Parameters menu (Figure 5-7).
Information compiled by:
Date:
G L O S S A R Y
Octel PC/CDR Edition 2 Glossary-1
GLOSSARY
NUMERALS and SYMBOLS
# key. The lower right-hand key on the American telephone keypad. In AmericanEnglish, called the pound key. In British English, called the hash key.
* key. The lower left-hand key on the American telephone keypad. In AmericanEnglish, called the star key.
A
AA (automated attendant). See Automated attendant.
Alphanumeric. (1) Refers to either the entire set of 128 ASCII characters or thesubset of ASCII characters that includes the 26 alphabetic characters andthe 10 numeric characters. (2) Pertains to a character set that containsboth letters and numerals and usually other characters.
AMIS (audio message interchange specification) analog networking. Anoptional software package that allows subscribers with mailboxes on anOctel server to exchange messages with subscribers on other, non-Octelvoice processors.
Application. (1) A software program or feature that is customized to address acustomer’s specific need for voice or data communications. (2) In thismanual, application also refers to ECP mailboxes (also known as single-digit menus) and other event-producing features of the Octel server.
ASCII (American Standard Code for Information Interchange). A set of 128standard, seven-bit binary codes for upper- and lower-case letters,numbers, punctuation, and special communication-control characters.
Aspen. (1) One type of server in the Octel product line. (2) Server softwarereleases that were in use before Aria 1.0.
ASPEN. The name ASPEN (in capital letters) is used in some transmissionmessages as a synonym for the Octel server.
Asynchronous transmission. A method of data communication that allows datato be sent at irregular intervals by preceding each character with a startbit and following it with a stop bit.
Automated attendant (AA). A feature that answers calls to the server andprompts callers to enter a telephone number or spell a name. After thecaller makes an entry, the automated attendant transfers the call.
GLOSSARY
Glossary-2 Edition 2 Octel PC/CDR
Automatic processing. One of four methods in Octel PC/CDR for downloadingand processing data. This processing method downloads, collates, andgenerates output files in one step, using system attributes that were setbefore the automatic processing started.
Automatic scheduler. See Scheduled automatic processing.
B
Backup. A copy of a program or data made in case the original is lost, damaged,or otherwise inaccessible.
Batch file. A text file with the extension .BAT in the file name. When the name ofthe batch file is typed, DOS executes the commands in the file.
Baud rate. (1) Term used for the speed of signal transmission, in bits per second.(2) Commonly used to mean bits per second, baud is officially defined asthe pulse width in a data-communication stream.
BCF (binary collection file). This file is created when blocks of CDR events aredownloaded from the CDR buffer on the server to the CDR PC. BCFs arestored on the CDR PC hard disk in the BCF subdirectory for the server(CDR system) from which they were downloaded. BCF names contain theencoded date on which the download occurred.
Binary. A variable that can be assigned one of two values, such as on or off or 0or 1.
Binary collection file (BCF). See BCF.
Block. A unit of storage within the CDR buffer that contains events. Blocks ofevents are downloaded to a PC for processing. A block can hold approxi-mately 80 to 140 events.
Buffer. See CDR buffer.
C
Call. A series of events that begins when a server port goes off-hook to receive anincoming call or to initiate an outgoing call. A call ends when the call iscompleted and the port goes on-hook.
Call Detail Records (CDR). See CDR.
Caller. Anyone who attempts to access the Octel server, either by dialing theaccess number directly or by entering a mailbox through telephone-an-swering mode.
Caller-menu output (CMO) file. Created by the Octel PC/CDR software package,these files contain ECP mailbox usage data. CMO files are described indetail in Chapter 9.
A–C
GLOSSARY
Octel PC/CDR Edition 2 Glossary-3
Call event. See Event.
Call volume. The number of calls received by the server within a given timeperiod.
Carbon Copy PLUS. A Meridian Technology software application used forcommunication between PCs. The application is a memory-residentprogram that is part of the Octel PC/CDR software package. Carbon CopyPLUS allows a remotely located personal computer to be connected to theCDR PC through a modem.
CDF (collated day file). See Collated day file.
CDR buffer. The storage space set aside on the server to collect CDR data. Alsocalled the buffer.
CDR (Call Detail Records). Data that is collected in the CDR buffer about eventsthat occur in the Octel server, including events occurring from the time aport goes off-hook to receive a call to the time the port goes on-hook whenthe call is completed. See also Octel PC/CDR.
CDR PC. A personal computer that contains the Octel PC/CDR software package.The manipulation of CDR data downloaded from the server occurs on theCDR PC.
CDR system. Refers to the system name chosen to designate a particular serverthat downloads CDR data to the CDR PC. See also System name.
Central office (CO). A telephone-company switching office that provides telephoneservice to residents and businesses within a designated area.
Centrex. The software and hardware located in a central office to providePBX-type service to customers, eliminating the need for PBX equipment onthe customer site.
Class of service (COS). A class of service, established by the system manager,determines the features available to subscribers on the Octel server.
CMO (caller-menu output) file. See Caller-menu output file.
Code values. Further descriptions of the entries made in some output-file andevent fields.
Collate. In Octel PC/CDR, the process, or the result, of arranging CDR data inorder.
Collated day file (CDF). This file is created by the Octel PC/CDR softwarepackage. The events in a BCF are sorted (collated) by call, chronologicallyby event-completion time into CDFs.
Communication port. The CDR PC serial port used to connect the CDR PC tothe server.
CRC (cyclical redundancy check). See Cyclical redundancy check.
Cyclical redundancy check (CRC). A method of detecting data transmissionerrors.
C
GLOSSARY
Glossary-4 Edition 2 Octel PC/CDR
D
Default. Value assigned by the Octel PC/CDR software package or the Octelserver when another value has not been specified by the subscriber orsystem manager.
Direct connection. A physical communication link that is permanently con-nected, used for data communication. The physical link usually cannot belonger than 50 feet. See also Remote connection.
Disk-usage output (DUO) file. Created by the Octel PC/CDR software package,these files contain information about available space on the server phraseand message drives. DUO files are described in detail in Chapter 9.
DOS (disk operating system). A commonly used PC operating system. DOSfacilitates commands used to manipulate and execute files contained instorage media.
DOS prompt. Greater-than sign (>) that appears at the left of a PC screen. Itusually indicates the selected disk drive and subdirectory. DOS commandscan be executed at the DOS prompt by entering the command name withthe appropriate parameters.
Download. Method for transferring data stored in the server CDR buffer to theCDR PC.
DTMF (dual-tone multifrequency). Tones generated by the touch-tone keys on atelephone. Unique tones are produced by each key. DTMF is a nationallyaccepted abbreviation for dual-tone multifrequency.
DTMF OctelForms. Optional data-collection and -processing software programused with the Octel server. A DTMF OctelForm is a series of questionsrecorded by the system manager in a DTMF forms mailbox and played to a caller in a specific sequence. The caller responds to the questions bypressing the touch-tone keys on the telephone.
DUO (disk-usage output) file. See Disk-usage output file.
E
ECP (Enhanced Call Processing). Software feature that allows the Octel server to route calls to extensions on the PBX or to other Octel server mailboxes.The routing does not require operator assistance. ECP mailboxes havecaller’s menus that allow the server to route callers to the selection theychoose from the caller’s menu. ECP mailboxes are also know as single-digitor caller’s menus.
Enhanced Call Processing. See ECP.
Enter key. A key on a computer keyboard, designated by the word Enter orReturn. Press the Enter key (or the Return key) to execute a statement orcommand.
D–E
GLOSSARY
Octel PC/CDR Edition 2 Glossary-5
Event. An activity on the server that could be of interest to the system manager,such as call activity, network activity, and specific server information.Server information includes date and time set (DTS) and initial programload (IPL) information. Call-activity events include entering a mailbox,conducting a password test, going off-hook or on-hook for a specific port,beginning an outcall, and transferring to another mailbox or telephonenumber. Events are described in Appendix B.
Extension. The PBX or Centrex number dialed to reach a person, not a mailboxon the server.
F
Fax. An abbreviation for facsimile. A document that is transmitted electronicallyand reconstructed by the receiving device.
Fax annotation. A voice message that is related to a fax image and presented inthe mailbox message queue as a single message.
Fax image. A fax by itself (without the annotation and introduction).
Fax message. A fax message can be one of the following: (1) a fax annotation, (2) a fax image, (3) a fax annotation and image, or (4) an introduction andfax image.
Fax output (FXO) file. FXO files, created by the Octel PC/CDR software package,contain information about fax activity. FXO files are described in detail inChapter 9.
FDO (forms output) file. See Forms output (FDO) file.
Field. Part of a record that is the smallest unit normally manipulated by adatabase-management system. A field contains a single piece of informa-tion of predetermined length and format. A field can also be restricted toalphabetical or numerical characters.
File format. The form (ASCII, dBASE, or log data) in which a file is created forreviewing or exporting. (Log files are created automatically by the OctelPC/CDR software package in the log-data format.) This term is presentedin Octel PC/CDR in two forms, File Format and FileFormat:
� The File Format: field, displayed on the output-file-processing screen,shows the number of the file-format type. This number represents theformat in which the output file is to be created (ASCII or dBASE III)and, if in ASCII format, the delimiter to be used. The file-format typesare as follows:
1 – ASCII fixed field2 – ASCII fixed field, separated by spaces3 – ASCII fixed field, separated by commas (,)4 – ASCII fixed field, separated by slashes (/)5 – ASCII variable field, separated by commas (,)6 – ASCII variable field, separated by slashes (/)7 – dBASE III compatible
E–F
GLOSSARY
Glossary-6 Edition 2 Octel PC/CDR
Select the file-format type from the Modify Output File Format Typesmenu. This menu is a submenu of the Octel PC/CDR System AttributesMenu.
� The FileFormat: field in the Status Window summary of the View OctelPC/CDR Output Files screen displays the entry that was made in theFile Format: field on the View Octel PC/CDR Output Files, FileSelection Parameters screen. This number represents the format of theoriginal output file. The file-format options for this field are as follows:
1 – ASCII Data File2 – dBASE Data File3 – Log Data File
File-format level. Determines which output files, fields, codes, and events areavailable for review or export. The file format level corresponds to the Octelserver software release. File format levels 1 through 5 are described insection 5.3.9. Enter the file format level in the Modify Output FileFormat Level: field of the Octel PC/CDR System Attributes Menu. It isdisplayed in the Level: field on the output-file-processing screen and inthe Level: field in the Status Window of the View Octel PC/CDR OutputFiles screen.
File format type. See File format, first definition.
File name. Name given to a particular file used by DOS. The format allows up toeight alphanumeric characters, with up to three alphanumeric charactersfor an extension. The first eight characters are separated from theextension by a period; combined, they form the file name. Although filenames can be typed as all upper- or lower-case characters (DOS is notcase-dependent), file names in this manual are shown in upper- andlower-case characters. Refer to section 1.9 and Chapter 9 for file-namingconventions used in Octel PC/CDR.
File type. The entry in the File Type: field, displayed on the View Octel PC/CDROutput Files, File Selection Parameters screen, determines the output fileto be viewed or printed. The entry in this field is displayed in the File-Type: field, located in the Status Window summary of the View OctelPC/CDR Output Files screen.
Forms output (FDO) file. Created by the Octel PC/CDR software package, thesefiles contain DTMF data from a DTMF forms mailbox, including records ofquestion numbers and callers’ responses. FDO files are described in detailin Chapter 9. See also DTMF OctelForms.
Function keys. Keys labeled F1 through F12, located along the top or at theside of a keyboard.
FXO (fax output) file. See Fax output (FXO) file.
F
GLOSSARY
Octel PC/CDR Edition 2 Glossary-7
G, H
Greeting. Recorded message identifying the location reached by the caller. Thegreeting is the first announcement heard by callers when they reach theOctel server, if there was no answer from the number dialed.
Hub. A device used by OcteLink, the global messaging network from OctelNetwork Services (ONS).
I, J, K
In-band integration. Method of integration in which called-party identificationand message-waiting commands are transmitted over the same channel asthe voice signal. The call information is sent in DTMF tones between theswitch and the server. In-band integrations are supported using eithersingle-line telephone lines or E&M tie trunks.
Individual-port-statistics output (IPO) file. Created by the Octel PC/CDRsoftware package, these files contain daily statistics, collected every 15minutes, for the total time each port was in use during a 15-minute periodand the number of calls placed within the period. IPO files are describedin detail in Chapter 9.
IPO (individual-port-statistics output) file. See Individual-port-statistics output(IPO) file.
L
Level. See File format level.
Link. The connection or the process of connecting two or more servers or otherdevices.
Log file. There are two types of log files. (1) A CDR system log file is created foreach day that a Octel PC/CDR process, such as collate or download, isexecuted. The results of the process are stored in a log file in the SYSsubdirectory on the PC hard disk for each CDR system. Log files arenamed by the date on which the processing occurred and are given theextension of .LOG (for example, L960509.LOG). (2) A transaction log file(also known as the schedule log file) called SCHEDCDR.LOG, located inthe OCTELCDR\LOG subdirectory, collects information about automatic-schedule transmissions. The transaction log file continues to add informa-tion as entries are made, until it is backed up onto a diskette or is erased.
M
Mailbox. An entity created in the Octel server software that provides a userinterface for sending and receiving voice and fax messages. Special mailboxtypes allow different functions to be performed, such as call routing.
Mailbox name. (1) Name of mailbox or subscriber entered in system managermenus 8 and 9.1. (2) Name recorded by a subscriber for mailbox identifi-cation.
G–M
GLOSSARY
Glossary-8 Edition 2 Octel PC/CDR
Mailbox number. The number that uniquely identifies a voice-messaging mailbox.Internal subscribers are assigned a mailbox number that is usually thesame as their telephone numbers.
Manual processing. One of four methods in Octel PC/CDR for downloading andprocessing data. The manual processing method uses three steps toperform downloads. Each step requires user input.
MDO (message-detail output) file. See Message-detail output(MDO) file.
Message-detail output (MDO) file. Created by the Octel PC/CDR softwarepackage, these files contain data records of messages sent or deleted froma mailbox. MDO files are described in detail in Chapter 9.
Message waiting. A feature that enables the server to notify subscribers of newmessages in their mailboxes. Also called message notification.
MIRROR II. A data-communication software product from SoftKlone DistributingCorporation. The application is used by Octel PC/CDR to set up acommunication link between the PC and the server for transferring data.
Modem. An acronym for modulator/demodulator. (1) Device used to interface thesystem manager terminal (SMT) with a telephone line for remote systemmanagement and polling. Also used for connecting a remote SMT to theserver CPU. (2) A method for passing digital information in an analogformat. (3) Device that converts digital signals into analog signals fortransmission through telephone lines.
N
NameNet. An OctelNet feature that allows messages to be addressed to subscrib-ers on remote systems by dialing the remote subscribers’ names.
NameNet output (NNO) file. Created by the Octel PC/CDR software package,these files contain information about NameNet directory and alarm activity.NNO files are described in detail in Chapter 9.
Networking. Optional feature that enables Octel’s servers to transmit messages toeach other at preprogrammed times and frequencies. See also AMIS analognetworking and OctelNet.
NNO (NameNet output) file. See NameNet output (NNO) file.
Node. Each server in an OctelNet network.
Non-service-affecting (NSA) alarm. An alarm that warns the system manager ofa condition that could degrade service if left uncorrected. In Octel PC/CDR, an NSA alarm is logged when the CDR buffer has less than 20% ofspace available before unretrieved data will be overwritten.
NSA (non-service-affecting) alarm. See Non-service-affecting (NSA) alarm.
M–N
GLOSSARY
Octel PC/CDR Edition 2 Glossary-9
O
OctelForms. See DTMF OctelForms.
OctelNet. A networking software product that allows Octel subscribers toexchange messages with subscribers on another Octel server. See alsoAMIS Analog Networking.
Octel PC/CDR. An Octel data collection and processing system that providesdetailed records of activity on a server and that runs on an external PC.
Online CDR. An Octel server utility available only when the server software is atRelease 4.1, and Aria 1.1 or newer. Online CDR is used to review CDRevents directly from the system manager terminal (SMT) without having tofirst download data to a PC. Refer to the Online CDR User Reference Guidefor information about using the Online CDR utility.
Outcalling. A call initiated by the server to a telephone or pager that is outsidethe PBX.
Output files. In Octel PC/CDR, the categories into which Octel PC/CDR sortsand files CDR data after it has been downloaded to a PC and collated.
P, Q
Parameter file. See Schedule parameter file.
Password. (1) The number used to access the server’s system manager terminal.Either the primary or secondary system manager passwords can beused.(2) A number used to access a mailbox as a subscriber. (3) In OctelPC/CDR, a password is required to allow the personal computer to linkwith the server for downloading data. The password used to access OctelPC/CDR menus, if required, is the same as the SMT password. Thispassword is required if the automatic scheduling method of processing isused. (4) In Octel PC/CDR, a schedule password can be established andrequired for accessing the automatic scheduler menus. (5) Carbon CopyPLUS requires a password to access a customer’s PC from a remotelocation.
PBX (private branch exchange). The telephone-switching equipment located in abusiness office designed to process incoming, outgoing, and internaltelephone calls.
PC/CDR. See Octel PC/CDR.
PCF (processed collection file). See Processed collection file.
Pending-state file (PSF). Created by the Octel PC/CDR software package. (1) The COLLATE.PSF file holds all event records for calls that are inprocess when a download occurs. (2) The COMPRSP.PSF file stores dataabout calls in process from one day to the next. It is used with the PSOfile.
0–P
GLOSSARY
Glossary-10 Edition 2 Octel PC/CDR
Port. Any input or output channel on a voice or data-switching system. In aswitch, a port is required for each line, trunk, or peripheral deviceconnected to that switch.
Processed collection file (PCF). Created by the Octel PC/CDR software package,the data in a binary collection file is sorted into collated day files. If thebinary collection file is not automatically set to be deleted, it is renamedwith the extension .PCF. See also Binary collection file (BCF).
Profile-change-details output (PRO) file. Created by the Octel PC/CDR softwarepackage, these files contain information about changes in user records,distribution lists, and other profile types. PRO files are described in detailin Chapter 9.
PRO (profile-change-details output) file. See Profile-change-details output (PRO)file.
PSF (pending state file). See Pending state file (PSF).
R
Remote connection. A data-communication link using modems. Becausemodems are used, the distance between the end devices can be more than50 feet. See also Direct connection.
Root directory. In a PC operating system, contains other directories and perhapsfiles. In DOS, the root directory is usually designated with the drive letterdesignation and a back slash; for example, C:\> designates the DOS rootdirectory for the C drive.
S
SA (service-affecting) alarm. See Service-affecting (SA) alarm.
Scheduled automatic processing. In Octel PC/CDR, data from one or moreservers can be processed automatically at scheduled time intervals. Tendifferent time schedules, each specifying up to 10 Octel servers (CDRsystems), programs, or batch files, can be created, with a minimum time of3 minutes between downloads. The Automatic Scheduler Functions menuis accessed from the Octel PC/CDR Main Menu.
Schedule log file. See Log files.
Schedule parameter file. Contains the schedules created for use with scheduledautomatic processing.
Scroll. (1) To advance or go back, horizontally or vertically, a specified number oflines or columns in a displayed file or menu on a computer screen. (2) Toadvance automatically, by line, as the screen is filled. The entries at thetop of the screen disappear as new entries are made at the bottom of thescreen.
P–S
GLOSSARY
Octel PC/CDR Edition 2 Glossary-11
SDO (session-detail output) file. See Session-detail output (SDO) file.
Segment. This term is used in Appendix B to define the entries in the SegCT:fields. Each time an introduction is added to a message and it is sent toanother mailbox, the segment count increments by 1. A new message sentto a mailbox on the server is 1 segment long. If an introduction is addedto the message and the message is sent to a second mailbox (or severalother mailboxes), the message is then 2 segments long. If the secondmailbox owner adds an introduction and sends the same message to athird mailbox (or several other mailboxes), it is 3 segments long.
Server. Unless noted otherwise, in this manual, the term server or Octel serverrefers collectively to the Octel Overture 250 and 350 message servers andthe Branch, Branch XP, Aspen, Maxum, and Octel XC1000 voice proces-sors.
Service-affecting (SA) alarm. Warns the system manager of an existing conditionthat could cause data and messages to be lost. In Octel PC/CDR, aservice-affecting alarm is logged when the buffer has less than 10% ofavailable space left before unretrieved data will be overwritten.
Service-level download. A method of downloading and processing CDR data. Thismethod is used primarily by service personnel for troubleshooting. Itcreates the same binary collated files (BCFs) as all other forms of process-ing; however, specific data blocks must be selected for downloading.
Session. The period of time between a caller entering a mailbox and exiting thesame mailbox in telephone-answering or voice-messaging mode. Eachmessage transmitted or received in a network call is also a session.Because a single call can pass through multiple mailboxes, a call canconsist of one or more sessions. For example, multiple mailboxes areentered and exited with ECP applications or when a caller uses the restartcommand within a mailbox. A special session can also include setup, setdate and time (DTS), and initial program load (IPL).
Session-detail output (SDO) file. Created by the Octel PC/CDR software package,these files contain event records of each time a mailbox was accessed,either in voice-messaging or telephone-answering mode, and when callersare logged into the server but not into a mailbox. SDO files are describedin detail in Chapter 9.
SMT (system manager terminal). See System manager terminal.
SMT emulation. When a server is connected to the CDR PC using the MIRROR IIsoftware program, the Octel PC/CDR software on the CDR PC allows SMTemulation, and both Octel PC/CDR and SMT tasks can be performedusing the CDR PC. SMT emulation allows the system manager to downloadblocks from the server and to perform most system manager tasks fromthe CDR PC.
Source mailbox. The location from which a caller begins an action.
Subscriber. Person who has been assigned a mailbox number on an Octel server.Subscribers can be located on or off the premises and are not required tohave a telephone number. Subscribers have access to all server featuresallowed by their classes of service.
S
GLOSSARY
Glossary-12 Edition 2 Octel PC/CDR
Syntax. The rules governing the structure of a language and its expressions.
System attributes. The parameters that apply to each server from which theCDR PC downloads CDR data. In the Octel PC/CDR software package,these attributes include necessary communications settings for theconnection between the CDR PC and each server. These attributes alsodefine the output files created with both the manual and automaticprocessing methods and the associated file formats.
System manager. Person responsible for operating and maintaining the serverand the Octel PC/CDR software package.
System manager terminal. Video display terminal that allows the systemmanager to set up and change the Octel server, set operational parame-ters, and monitor server performance.
System name. The name chosen to designate a particular server. It is used bythe MKCDRSYS command (on the PC) to create the directory that storesthe data from that particular server. Type the command cdrhelp at theDOS prompt to list all valid CDR system names. See also CDR system.
T
Telephone-answering mode. Mode of operation in which the server performs atelephone-answering function that (1) answers telephones forwarded to theserver; (2) plays a personal greeting from the subscriber or a systemgreeting generated by the server using a recorded name; and (3) recordsand stores the caller’s message for later review by the receiver.
Traffic. In Octel PC/CDR, the number of calls processed by a server.
Transaction log file. See Log file.
Trees. An Octel term for the software that provides an interface between a callerand the server. The expression open trees refers to the entry point of a callinto the server, where callers have the option of dialing an extensionnumber or identifying themselves as subscribers on the server.
Truncate. To shorten by cutting off. In this manual, it refers to the cutting off ofdata that is too wide for a screen display.
U
Unsuccessful-transfer output (UTO) file. Created by the Octel PC/CDR softwarepackage, these files contain statistics for failed attempts to transfer froman automated attendant or from an ECP mailbox. Reasons for failureinclude a busy extension, ring-no-answer, the extension is not in service,or the transfer was answered by the server. UTO files are described indetail in Chapter 9.
User. Person who uses the server; for example, a subscriber or an outside caller.See also Subscriber.
UTO (unsuccessful-transfer output) file. See Unsuccessful-transfer output (UTO)files.
S–U
GLOSSARY
Octel PC/CDR Edition 2 Glossary-13
V
Voice mail. A technology that provides a communication link among subscriberswho are not in direct telephone contact with one another. Subscribers cansend messages, listen to messages sent by others, reply to messages, andsend copies of messages to other subscribers. Subscribers also hearsystem broadcast messages and bulletin broadcast messages.
Voice-messaging mode. A voice-mail feature used by server subscribers toexchange messages or information with other subscribers without being indirect telephone contact with one another. In a single call, subscribers cansend messages, listen to messages sent by other subscribers or left byoutside callers, reply to messages, and send copies of messages to othersubscribers.
Voice processor. Equipment that allows nonsimultaneous voice and fax communication.
VPMOD. Used in some Octel PC/CDR Release 6.00 transmission messages torepresent the server.
W, X, Y, Z
XMODEM. An error-correcting data-transmission protocol for transmitting filesbetween personal computers.
V–Z
I N D E X
Index-1Edition 2Octel PC/CDR
Symbols
^in modem parameters, 5-12
|in modem parameters, 5-12
~in modem parameters, 5-12
# keydefined, Glossary-1
* keydefined, Glossary-1
A
ACCESSTYPE (AS) codes, SDO files, A-24,A-25
ACT_TYPE (AC) codes, FXO files, A-6
ACT_TYPE (AP) codes, CMO files, A-3
ACTION (AT) codesMDO files, A-14, A-15PRO files, A-21
ACTIVITY (AC) codesPRO files, A-21
ACTIVITY (Act) codesMNO files, A-19
AlarmsCDR data-loss warning, 1-12CDR data-loss warnings, 2-10
Alphanumericterm defined, Glossary-1
AM_DIR_FULL event details, B-8
AM_EAR_FULL event details, B-8
AMIS analog networkingdefined, Glossary-1
AM_RCV_EOS event details, B-8
AM_RCV_FC event details, B-8
AM_RCV_FR event details, B-8
AM_RCV_IC event details, B-8
AM_RCV_INVPH event details, B-9
AM_RCV_MSG event details, B-9
AM_RCV_MSGI event details, B-9
AM_RCV_PHNUM event details, B-10
AM_RCV_RESP event details, B-10
AM_RCV_START event details, B-10
AM_RTS event details, B-11
AM_SEND event details, B-11, B-12
AM_XMT_EOM event details, B-12
AM_XMT_EOS event details, B-12
AM_XMT_MBOX event details, B-12
AM_XMT_MINFO event details, B-12, B-13
AM_XMT_OC event details, B-13
AM_XMT_PHNUM event details, B-13
AM_XMT_RESP event details, B-14
AM_XMT_START event details, B-14
AM_XMT_VOICE event details, B-14
Applicationdefined, Glossary-1
Approximate Download Time example, 2-11
Archiving, binary collection files (BCFs)See Backing up; Restoring
ASCIIdefined, Glossary-1output file format, 9-1, 9-2
AspenCDR buffer
disabling, 2-2drive storage space used, 2-3location of stored data, 2-3size, 2-2storage space requirement (in
minutes), 2-3defined, 1-4, Glossary-1equipment configuration, 4-12 through
4-17port statistics, 9-11
ASPENdefined, Glossary-1
Asynchronous transmissiondefined, Glossary-1
INDEX
Index-2 Edition 2 Octel PC/CDR
ATTRIB (Atr) codes, MDO files, A-16
AUTOEXEC.BAT file, 3-1printing, G-2restarting after update, 3-4, 3-14updating, 3-3, 3-13
during installation, 3-3during upgrade, 3-13
Automated attendantdefined, Glossary-1
Automatic Octel PC/CDR Schedule EditorMenu, 7-21
Automatic Octel PC/CDR Schedule 1 screen,7-23
Automatic processing, 7-16 through 7-36defined, Glossary-2described, 7-15 through 7-17DTMF OctelForms data, 10-6output file generation, 5-7preparation, 7-2 through 7-6, 7-15
creating more storage space, 7-6data transfer, 7-3, 7-4error messages, 7-5 through 7-6log file entries, 7-4partially filled blocks, 7-4preliminary tasks, 7-2transmission messages, 7-5 through
7-6processing overview, 7-1schedules, 7-16starting methods, 7-16steps, 1-3
Automatic processing schedules, 7-16through 7-36
adding, 7-18 through 7-22backing up, 7-24deleting, 7-22described, 7-28editing, 7-22establishing password, 7-29 through 7-30listing, 7-23mode, using DOS, 7-28printing, 7-24removing, 7-22restoring schedule parameter file, 7-26timer, 7-27updating, 7-18 through 7-27
Automatic Schedule Menu, 7-17
Automatic schedulerSee Scheduled automatic processing
Automatic Schedule mode, 7-27 through7-28
starting date and time, 7-27Octel PC/CDR Automatic Schedule
Editor Menu, 7-22illustrated, 7-17using, 7-27 through 7-29
using DOS, 7-28
Available Modem Types screen, 6-4
B
Backing upSee also RestoringBegin File Transfer screen, 7-3binary collection files (BCFs), 1-12CDR system log files, 1-16collated day files (CDFs), 1-14defined, Glossary-2errors in backup utility, 7-6Octel PC/CDR files, 8-10 through 8-14
DOS version 6.2 or newer, 8-10DOS versions 3.2 through 5.0, 8-11
through 8-14output files, 8-10 through 8-14
DOS version 6.2 or newer, 8-10DOS versions 3.2 through 5.0, 8-11
through 8-14pending-state files (PSFs), 1-15schedule log file, 7-32scheduled automatic processing, 7-22
Batch filedefined, Glossary-2
Baud rateAspen, 4-12 through 4-13Branch and Branch XP, 4-12 through
4-13Carbon Copy PLUS, 6-4channels, 4-20, 4-21communications parameter, 5-11defined, Glossary-2Maxum and Maxum SE, 4-12 through
4-13modems, 4-2Octel Overture 250 and 350, 4-8Octel XC 1000, 4-21
BCF subdirectory, 3-6
BCFsSee Binary collection files (BCFs)
A–B
INDEX
Index-3Edition 2Octel PC/CDR
Begin File Transfer screencolumns, 7-4illustrated, 7-3
Billingeffect of upgrading software, 3-10output file-format level, 5-15selecting file-format level, 5-16
Binaryterm defined, Glossary-2
Binary collection files (BCFs)archiving, 1-12avoiding duplicate data in database, 1-13backing up, 1-12collating, 1-13collating manually, 7-9 through 7-10copying, 1-12, 8-25 through 8-29
using DOS, 8-28using service utilities, 8-26 through
8-28creating BCF subdirectory, 3-6defined, Glossary-2deleting, 5-5deleting/erasing, 1-12, 5-5described, 1-12 through 1-13displaying, 8-29 through 8-34
using DOS, 8-32using service utilities, 8-30
maximum daily downloads, 1-13naming convention, 1-13renamed PCF, 1-12, 5-5subdirectory, location, 1-12viewing, 1-12
Block Retrieval Transfer screen, 7-39
BlocksCDR buffer size, 2-2characteristics, 2-3 through 2-6defined, 1-4, Glossary-2downloading
CDR blocks, 7-3more than once, 2-3sequence, 2-4 through 2-7
DTMF OctelForms data-estimationformulas, 10-3 through 10-6
estimating number filled, 2-6 through2-10
procedure, 2-7with DTMF OctelForms data, 10-2
through 10-7
factors affecting fill rate, 2-6fill-rate formulas, 2-4 through 2-10, 10-2
through 10-5fill pattern, 2-1important information, 2-3information stored
in kilobytes, 2-3in number of events, 2-3
logical blocks, 2-4lost data, 2-4manually downloading CDR data, 7-9
through 7-10maximum retrieved with download
described, 2-4 through 2-6example, 2-4illustrated, 2-5
next block to download, 5-14numbering sequence, 2-4 through 2-7overwriting sequence, 2-4 through 2-6partially filled, 2-3, 7-4, 7-8renumbering of overwritten blocks, 2-4size (in bytes), 2-2status after download, 2-3transmission blocks, size, 7-3
BN_EOS event details, B-15
BN_IC event details, B-15
BN_MULTILINE event details, B-15
BN_OC event details, B-15, B-16
BN_RCV_CP event details, B-16
BN_RCV_HDR event details, B-17, B-18
BN_RCV_SP event details, B-18
BN_RCV_START event details, B-19
BN_RCV_VOICE event details, B-19
BN_RTS event details, B-19, B-20, B-21
BN_XMT_CP event details, B-21, B-22
BN_XMT_HDR event details, B-22
BN_XMT_SP event details, B-23
BN_XMT_START event details, B-23
BN_XMT_VOICE event details, B-23, B-24
BranchCDR buffer
disabling, 2-2drive storage space used, 2-3location of stored data, 2-3size, 2-2storage space requirement (in
minutes), 2-3
B
INDEX
Index-4 Edition 2 Octel PC/CDR
equipment configuration, 4-12 through4-17
port statistics, 9-11
Branch XPCDR buffer
disabling, 2-2drive storage space used, 2-3location of stored data, 2-3size, 2-2storage space requirement (in
minutes), 2-3equipment configuration, 4-12 through
4-17port statistics, 9-11
BufferSee CDR buffer
C
Calldefined, 1-4, Glossary-2relationship to sessions and events,
illustrated, 1-6volume, Glossary-3
Call detail recordsSee CDR
Callerdefined, Glossary-2
CALLER event details, B-24
Caller-menu output (CMO) filesSee also Output filesapplications, 9-2 through 9-4code value, A-3creating CMO subdirectory, 3-6defined, Glossary-2described, 9-2 through 9-4, A-2, A-3file structures, A-2File-Processing Summary screen, 9-3, 9-4files without data, 9-3naming convention, 9-2, A-1printed report example, 9-3subdirectory, 9-3
CALLMNU event details, B-24, B-25
Calls in processat time of downloading, 1-14 through
1-15
CALLTYPE (CT) codes, SDO files, A-25, A-26
Carbon Copy PLUS, 6-1 through 6-10baud rate, 6-4changing parameters, 6-2, 6-6comm port address, 6-3configuring, 6-1 through 6-6
assumptions, 6-2options
Option 4: Password Table, 6-5 through6-6
Option A: Comm Port Address, 6-3Option B: Baud Rate, 6-4Option C: Modem Type, 6-4
defined, Glossary-3parameters, 6-2
Customer Dialogue screen, 6-7described, 6-1disabling, 6-10exiting, 6-10installing, 6-1 through 6-6loading into memory, 6-6MIRROR II with, 6-1modem type, 6-4password table, 6-5remote access, 6-5remote access to CDR PC, 6-8remote connection configuration, 6-2remote usage, 6-6removing from memory, 6-10requirements, 6-1
communication port, 6-1modem, 6-1
screensAvailable Modem Types, 6-4Customer Dialogue, 6-7Password Table, 6-5 through 6-6Service Dialogue, 6-9
security, 6-6service representative responsibilities,
6-8, 6-9subdirectory, 3-1system manager responsibilities, 6-7, 6-9System Parameters menus, 6-3
Carbon Copy PLUS System Parameters menuoptions
baud rate, 6-4comm port address, 6-3modem type, 6-4password table, 6-5, 6-6
B–C
INDEX
Index-5Edition 2Octel PC/CDR
Cautionsavoid affecting host billing programs when
upgrading PC/CDR software, 3-11avoid data inconsistencies, 5-10, 5-15avoid duplicate data during collation,
5-14avoid log-entry loss, 5-18avoid overwriting buffer/losing data, 2-6,
2-9, 10-5collate all BCFs before erasing them, 5-6ensure PC/CDR security, 7-27ensure remembering password, 7-29ensure security of the CDR PC, 5-17monitor available storage space, 2-13,
10-6prevent unauthorized access to Carbon
Copy PLUS, 6-6prevent lost data, 2-1, 2-17, 3-11, 5-3,
10-2
cc command, 6-3
CC subdirectory, 3-1, D-2
ccremove command, 6-10
CDF subdirectory, 3-6
CDFsSee Collated day files (CDFs)
cdfs command, 8-25
CDRdefined, Glossary-3described, 1-1
CDR blocksSee Blocks
CDR buffer35,000-block, overwritten blocks,
illustrated, 2-57020-block
first and second pass, illustrated, 2-4overwritten blocks, illustrated, 2-5
alarms, 2-10blocks, 2-1through 2-7, 5-14 through
5-15, 7-3, 7-8 through 7-10, 10-2through 10-4
call detail recording lost data counter,resetting procedure, 2-23
capacityestimating blocks filled, 10-2 through
10-4estimating capacity (in days), 10-4
capacity (in days), example, 2-6confirming available disk space, 2-14defined, 1-4, Glossary-3described, 1-12, 2-1 through 2-10determining data collected, 2-1determining size, 2-2disabling on voice processors, 2-2displaying CDR record groups, 2-16downloading
creating processing time chart, 2-14estimating processing time, 2-14factors affecting processing time, 2-14monitoring factors, 2-14using other reporting products, 2-22
downloading data, 2-14downloading to PC
frequency, 3-11, 10-5 through 10-6software upgrade effect, 3-10
drive storage space used for CDR buffer,2-2 through 2-3
establishing fill pattern, 2-1estimating capacity
blocks filled, 10-2 through 10-4described, 2-6 through 2-10in days, 10-4 through 10-5procedure, 2-8
factors affecting fill rate, 2-6location of stored data, 2-3monitoring
CDR block information, 2-22storage space, 2-9, 2-22
overwriting blocks, 2-4, 2-5percent full, 2-9recording events, 2-3 through 2-6reserving space on drives, 2-2retrieve call detail records option, 2-23selecting CDR record groups for
collection, 2-16Aria 1.0, 2-21Aria 1.1, 2-20Aria 1.2, 2-20Aspen Release 1.0X through 4.0, 2-21Aspen Release 4.1, 2-20procedure, 2-20, 2-21
size, 2-2size (in blocks), 2-2sizing
described, 2-2 through 2-3table, 2-2
status, 7-4storage space allocated, 2-2storage space requirement (in minutes),
2-3
C
INDEX
Index-6 Edition 2 Octel PC/CDR
system drive storage space used, 2-3system-drive storage space used, 2-2total blocks filled, estimating formula,
10-4 through 10-6
CDR Buffer Capacity exampleSee Example of CDR Buffer Capacity
cdr command, 1-6, 5-1, 7-1
CDR datacollate, Glossary-3described, 1-1downloading methods, 7-1processing, 7-1uses for, 1-1
CDR eventsSee also Eventsavailability by software release, 1-2blocks, partially filled, 2-3defined, 1-4information included, 2-1organization, 7-11recording in CDR buffer, 2-3 through 2-6relationship to calls and sessions,
illustrated, 1-6
CDR PCcommunications parameters, 5-9 through
5-14defined, 1-1, Glossary-3distribution-board port, 4-23estimating PC disk space needs, 2-10
through 2-14hardware requirements, 4-1 through 4-3remote access, restrictions, 6-7scanner-board port, 4-17SMT emulation, 5-17 through 5-19software requirements, 4-3system manager functions, unaccessable,
5-17
CDR systemdefined, 1-4, Glossary-3
CDR system log filesdescribed, 1-15 through 1-16
CDR system names, 1-5
CDRCFG event details, B-25
cdrhelp command, 1-5
Central office (CO)defined, Glossary-3
Centrexdefined, Glossary-3
Channelsidentifying, 11-3Octel XC1000, establishing, 4-20
Checklists, 1-13 through 1-4
chkdsk command, G-2
CHKREV utility, 8-36
Circular buffer, 2-3
Class of servicedefined, Glossary-3
Code valuesdefined, Glossary-3
Collated day files (CDFs)defined, Glossary-3
Communication portdefined, Glossary-3
CMO File-Processing Summary screencolumn descriptions, 9-4illustrated, 9-3
CMO filesSee Caller-menu output (CMO) files
CMO subdirectory, 3-6, 9-3
CNN_ENABLE event details, B-25
CNN_OCL_MB event details, B-25
CNN_OCL_VM event details, B-25
CNN_PRIVACY event details, B-25
CNN_VC_LINK event details, B-25
Code values and descriptionsSee also Tablescaller-menu output (CMO) files, A-3defined, Glossary-3fax output (FXO) files, A-6, A-7message-detail output (MDO) files, A-14
through A-17NameNet output (NNO) files, A-19profile-change-details output (PRO) files,
A-21session-detail output (SDO) files, A-24
through A-31unsuccessful-transfer output (UTO) files,
A-31
Collate Processing screen, 7-10
COLLATE.PSF, described, 1-14 through 1-15
C
INDEX
Index-7Edition 2Octel PC/CDR
Collated day files (CDFs)backing up, 1-14creating CDF subdirectory, 3-6creating from binary collection files, 7-9
through 7-10deleting/erasing, 1-14, 5-5described, 1-12 through 1-16naming convention, 1-14searching, 8-18 through 8-25subdirectory, 1-14uses for, 1-14viewing, 1-14
Collationbinary collection files (BCFs), 1-13collating BCFs manually, 7-9 through
7-10defined, 1-4deleting BCFs after, 5-5processed collection files (PCFs), 1-13restarting, 7-6summary, 7-9
Column names% Complete, 7-4Active Type, 4-11, 4-17, 4-23Approximate Downloading Time With
Direct Connection at 9600 Baud, inMinutes per Day, 2-11
Average Calls per Day, 2-7, 2-11Average CDR Blocks Filled per Day, 2-7,
2-11Block #, 7-3, 7-4Buffer Capacity, in Days, 2-7Calls Failed, 9-23Calls Passed, 7-10, 9-14, 9-23CDF Input File Date, 9-4, 9-6, 9-8, 9-10,
9-14, 9-16, 9-18, 9-20, 9-23, 9-25CDR Blocks, 7-10, 8-32CDR Input File, 7-10CDR Input File Name, 8-32Consec. errors, 7-4Current Setting, 5-5 through 5-7, 5-10,
5-11, 5-15, 5-16, 7-14, 8-11, 8-12,8-15
File Creation Date, 8-32File Creation Date & Time, 7-10File Creation Time, 8-32File Format Current Setting, 5-8File Size Bytes, 8-32Forms Calls, 9-10List Changed, 9-20
Messages Deleted, 9-16, 9-23Messages Returned, 9-16Messages Sent, 9-16, 9-23Option, 2-20 through 2-22Other Calls Ignored, 9-23Profile Changed, 9-20Records Created, 9-6, 9-8, 9-16, 9-18,
9-20Rejected Events, 7-10Sessions Passed, 9-23Stored Type, 4-11, 4-17, 4-23Sys. Events Ignored, 9-14System ID #, 7-10, 8-32, 9-4, 9-6, 9-8,
9-10, 9-14, 9-16, 9-18, 9-20, 9-23,9-25
Total Calls, 9-4, 9-6, 9-8, 9-10, 9-14,9-16, 9-18, 9-20, 9-23, 9-25
Total errors, 7-4Total Events, 7-10, 8-32Unsuc Xfers, 9-23Unsuccessful Transfers, 9-25User Rec Changed, 9-20
CommandsSee also UtilitiesCC (Carbon Copy PLUS), 6-1 through
6-10ccremove, 6-10cdfs, 8-25cdr, 1-6, 5-1, 7-1cdrhelp, 1-5chkdsk, G-2copybcf, 8-25 through 8-29debug, G-2dir, 2-14DUMPBCF, 8-31, 8-32dumpbcf, 8-29 through 8-34DUMPSF, 8-34 through 8-36mem, G-2MKCDRSYS, 3-6 through 3-9printing hard-copy for DOS command
results, G-2RMCDRSYS, 3-9 through 3-10schedcdr, 7-28set, G-2systemname, 7-40type, G-2UPGRCDR, 3-12ver, G-2
Communication link, 7-40
Communication Port, 5-11
C
INDEX
Index-8 Edition 2 Octel PC/CDR
Communication Speed, 5-11
Compatibility, Octel PC/CDR and serversoftware, 1-2
COMPRSP.PSF, described, 1-15
CONFIG.SYS file, 3-1printing, G-2restarting after update, 3-4updating, 3-3, 3-13
during installation, 3-3during upgrade, 3-13
Configurationchecklist, 1-3 through 1-4
ConfiguringCarbon Copy PLUS parameters, 6-1
through 6-6connecting cables, 11-4, 11-5equipment for Branch, Branch XP, Aspen,
Maxum SE, and Maxum, 4-12separate ports for SMT and PC (Aspen
software releases 1.5X andnewer), 4-13
shared port for SMT and PC (Aspensoftware releases 1 through1.3X), 4-17
equipment for Octel Overture 250 and350, 4-4
equipment for Octel XC1000, 4-18separate ports for SMT and PC (Aspen
software releases 1.5X andnewer), 4-19
shared port for SMT and PC (Aspensoftware releases 1 through1.3X), 4-23
establishing the server channel, 4-20identifying the server channel, 11-3parameters, 5-3 through 5-4server for data collection, 2-1server-to-PC connectors, 4-4system attributes, 5-3 through 5-17
Connecting cables, 11-4 through 11-5
Connectorsserver-to-PC, 4-4
COPYBCF command, 8-25 through 8-29
COPYBCF Options menu, 8-28
CRC (cyclical-redundancy-check) calculation,7-3
CRC calculation method, 7-3
Creating CDR systems, 3-8
Creating subdirectories using MKCDRSYS,3-6 through 3-9
Customer Dialogue screen, 6-7
Cyclical-redundancy-check (CRC)calculation, 7-3
defined, Glossary-3
D
Dataavoiding duplicate data in database,
processed collection files (PCFs),1-13
avoiding duplicate database, 1-13
Comm Port Address, 6-3binary collection files (BCFs), 1-13processed collection files (PCF), 1-13
Data collectiondetermining data to be collected, 2-1estimating
CDR buffer capacity, in days, 10-4through 10-5
download frequency, 10-5 through10-6
number of blocks filled, 10-2 through10-4
overview, 2-1required record groups, 2-17
all records, 2-17DTMF forms mailbox records, 2-17,
2-18invalid password disconnect records,
2-17message count records, 2-17message review records, 2-17message send/delete/print records,
2-17, 2-18message waiting notification records,
2-17, 2-18network-related records, 2-17, 2-18reporting related records, 2-17selection factors, 2-17session-related records, 2-17
retrieval and manipulation processdescribed, 1-10 through 1-11illustrated, 1-11
C–D
INDEX
Index-9Edition 2Octel PC/CDR
server configuration, 2-14 through 2-24confirming software feature is enabled,
2-15monitoring CDR block information,
2-23monitoring CDR buffer space, 2-23resetting lost data counter, 2-23selecting record groups for collection,
2-16 through 2-22using Retrieve Call Detail Records
option, 2-23
Data processing sequence, described, 1-10through 1-11
Data switch, 4-17
Data transfer, 7-3 through 7-4
Data transmission, verifying, CRCcalculation method, 7-3
Database software, 4-3
Data-loss warning, 2-10
Dated log filesSee CDR system log files
Dated pending-state files (PSFs)described, 1-14 through 1-15naming convention, 1-15
dBASE output file format, 5-8, 9-1
debug command, G-2
Defaultterm defined, Glossary-4
Definitions, key terms, 1-4
DeletingSee Erasing
DEST_TYPE (DT) codesCMO files, A-3SDO files, A-26
Dialing and Serial Channel Parameters(Menu 6.3), 4-16
dir command, 2-14
Direct connectioncommunications parameter, 5-11connecting cables, 11-4 through 11-5Connection Type field, 5-11defined, Glossary-4parts required, 4-4system attribute specification, 5-11testing, 5-17
Disk Status screendescribed, 8-2illustrated, 8-3
DISK_USG event details, B-25, B-26
Disk-usage output (DUO) filesSee also Output filescreating DUO subdirectory, 3-6defined, Glossary-4described, 9-4 through 9-6, A-4file structure, A-4File-Processing Summary screen, 9-5files without data, 9-5naming convention, 9-4, A-4printed report example, 9-5subdirectory, 9-5
Display, CDR system names, 1-5
Display Octel PC/CDR files options screen,8-4
DM_PSEUDO event details, B-26
DOSaccessing PC/CDR Utility Menu, 8-25backing up Octel PC/CDR files
backup file required, 4-2DOS version 3.2 through 5.0, 8-11DOS version 6.2 or newer, 8-10
copying binary collection files (BCFs),8-28
defined, Glossary-4displaying
binary collection files (BCFs), 8-32Octel PC/CDR release number, 8-36pending state files (PSFs), 8-35
printing hardcopy for DOS commandresults, G-2
prompt defined, Glossary-4restoring PC/CDE files, 8-17searching collated day files (CDFs), 8-25service-level download, 7-40starting automatic scheduler mode, 7-28utilities, performing Octel PC/CDR file
maintenance, 8-10
DOS version compatibility, 4-2
Downloadingavoiding lost data, 1-2CDR blocks, 7-3CDR buffer status, 7-4collation summary, 7-9COPYBCF command, 7-8
D
INDEX
Index-10 Edition 2 Octel PC/CDR
creating more storage space, 7-6defined, Glossary-4determining frequency, 2-9, 2-10disk space requirement, 10-6effect of upgrading software, 3-10establishing schedule, 2-1estimating formula, 2-11, 2-12estimating PC disk space, 2-10 through
2-14estimating time, 2-10 through 2-14
baud rate, 2-12connection type, 2-12
files created, COLLATE.PSF, 1-14frequency, 10-5isolating blocks, 7-8manually downloading CDR data, 7-7
through 7-8maximum daily downloads, 1-13processing methods, 1-3 through 1-4service level download, 7-36 through 7-40status of blocks, 2-3steps, 7-8system names, service-level download
command, 7-40time requirement, 2–12, 10-6
Download Settings Menu, 7-8
DTMF OctelFormsCDR buffer
download frequency, 10-5estimating capacity in days, 10-4estimating number of blocks filled,
10-2time required to download, 10-6
configuration, 10-1configuring FDO file, 10-1 through 10-2data collection, 2-17, 10-1 through 10-2defined, Glossary-4described, 10-1estimating CDR buffer capacity, 10-2
through 10-5PC disk space requirements, 10-6processing data, 10-6references, 10-1special configuration, 10-1 through 10-2
DTS event details, B-26
DUMPBCF command, 8-29 through 8-34illustrated, 8-31options menu, 8-32summary screen, 8-32
DUMPSF command, 8-34
DUO File-Processing Summary screencolumn descriptions, 9-6illustrated, 9-5
DUO filesSee Disk-usage output (DUO) files,
DUO subdirectory, 3-6, 9-5
E
ECP (Enhanced Call Processing)defined, Glossary-4
EmulationSee SMT emulation
Erasingbinary collection files (BCFs), 1-12CDR system log files, 1-16collated day files (CDFs), 1-14eligible subdirectories/files, 8-14 through
8-15pending-state files (PSFs), 1-15
Error messages, 7-5 through 7-6, 8-6backup utility errors, 7-6from CDR PC, E-2from server, E-1low storage space warning, 5-2, 7-6schedule-log-file entries, F-1, F-2unavailable day file, 7-6write fault error, 8-9
Events, B-1, C-1 through C-6See also CDR eventsAM_DIR_FULL, B-8AM_EAR_FULL, B-8AM_RCV_EOS, B-8AM_RCV_FC, B-8AM_RCV_FR, B-8AM_RCV_IC, B-8AM_RCV_INVPH, B-9AM_RCV_MSG, B-9AM_RCV_MSGI, B-9AM_RCV_PHNUM, B-10AM_RCV_RESP, B-10AM_RCV_START, B-10AM_RTS, B-11AM_SEND, B-11, B-12AM_XMT_EOM, B-12AM_XMT_EOS, B-12
D–E
INDEX
Index-11Edition 2Octel PC/CDR
AM_XMT_MBOX, B-12AM_XMT_MINFO, B-12, B-13AM_XMT_OC, B-13AM_XMT_PHNUM, B-13AM_XMT_RESP, B-14AM_XMT_START, B-14AM_XMT_VOICE, B-14BN_EOS, B-15BN_IC, B-15BN_MULTILINE, B-15BN_OC, B-15, B-16BN_RCV_CP, B-16BN_RCV_HDR, B-17, B-18BN_RCV_SP, B-18BN_RCV_START, B-19BN_RCV_VOICE, B-19BN_RTS, B-19, B-20, B-21BN_XMT_CP, B-21, B-22BN_XMT_HDR, B-22BN_XMT_SP, B-23BN_XMT_START, B-23BN_XMT_VOICE, B-23, B-24byte size by record group, C-1 through
C-6any group, C-1DTMF forms mailbox records, C-4invalid password-disconnect records,
C-4message count records, C-5message review records, C-5message send/delete/print records,
C-2message-waiting-notification records,
C-4miscellaneous events, C-6network-related records, C-3reporting-related records, C-5session-related records, C-2
CALLER, B-24CALLMNU, B-24, B-25CDRCFG, B-25CNN_ENABLE, B-25CNN_OCL_MB, B-25CNN_OCL_VM, B-25CNN_PRIVACY, B-25CNN_VC_LINK, B-25collecting diagnostic data, C-1dates, C-1defined, Glossary-5DISK_USG, B-25, B-26DM_PSEUDO, B-26
DTS, B-26FCE, B-26FP, B-27FR, B-27, B-28FRTS, B-28GEN_ERR, B-28GET_ROUTE, B-28header information, B-1IC, B-28IPL, B-29IVR_EXIT, B-29LIST_CHG, B-30MD, B-30, B-31MS, B-32, B-33, B-34MSG_CNT, B-34MSG_RVW, B-35MW, B-36NNET_ALARM, B-36NNET_DIR, B-36NNET_NAME, B-37OC, B-37, B-38OCL_NAME, B-38ON_HOOK, B-38port number, B-1PORTS_BUSY, B-38PROFILE_CHG, B-38PWT, B-39PWT_RJCT, B-39rejected events, 7-10RSS, B-39searching collated day files (CDFs), 8-22SEIZE, B-39SESSION, B-39SMS, B-39SMSG_ALERT, B-39SMSG_DELVR, B-39SMSG_INFO, B-39SMSG_REPORT, B-39SMSG_STFWD, B-40tables, C-1 through C-6
alphabetized by event name, B-2, B-3,B-4
details, B-8numerical sequence by code, B-5, B-6,
B-7TIGON, B-40time, B-1TNE, B-40TREES_FCD, B-40TREES_FMB, B-40TREES_FQA, B-40
E
INDEX
Index-12 Edition 2 Octel PC/CDR
TRS, B-40TUT, B-40UR_CHG, B-41XFR, B-42
Example of Approximate Download Time,2-11
Example of CDR Buffer Capacity, 2-6
Extensiondefined, Glossary-5
F
Faxannotation, defined, Glossary-5defined, Glossary-5image, defined, Glossary-5message, defined, Glossary-5
Fax output (FXO) filesSee also Output filescode value, A-6, A-7creating FXO subdirectory, 3-6defined, Glossary-5described, 9-6 through 9-8, A-5 through
A-7file structure, A-5file-processing summary screen, 9-7files without data, 9-7naming convention, 9-6printed report example, 9-7subdirectory, 9-7
FCE event details, B-26
FDO File-Processing Summary screen, 9-10column descriptions, 9-10illustrated, 9-10
FDO filesSee Forms output (FDO) files
FDO subdirectory, 3-6, 9-8
Fielddefined, Glossary-5
Field namesAverage Events Per Call, 8-24Baud Rate, 6-4Binary Collection Files Erased After
Collation?, 8-34Block Date & Time Summary Report, 8-30
Block Number?, 5-15Boot Drive Name, 3-3, 3-13CDF Input File, 8-24Channel Number To Be Defined, 4-7, 4-9,
4-11, 4-14, 4-15, 4-17, 4-20, 4-21,4-23
Channel Type, 4-7, 4-8, 4-14, 4-20CPU Baud Rate, 4-8, 4-14, 4-15Date/Time of Next Execution, 7-16, 7-19,
7-20Destination Drive Name, 3-3, 3-13Directory, 6-2Do you wish to proceed making [output
file name] files?(y/n), 7-13Enter Choice, 8-19Enter Option, 5-1, 5-2, 5-3Event Records, 8-22File Date, 8-6File Format, 7-13, 8-5, 8-6File Type, 8-5First Block to Copy, 8-27First Column to Print, 8-9First Line to Print, 8-9Found [number] New or Updated Collated
Day File(s), 7-13Full Report?, 8-30Input CDF File, 8-19, 8-20Install Octel PC/CDR Software?, 3-3Interval Between Executions, 7-20Last Column to Print, 8-9Level, 7-13, 8-6Mailboxes, 8-22Matching Calls, 8-24Maximum Events Per Call, 8-24Mdel, 2-18Message Review Record Mailboxes, 2-20Minimum Events Per Call, 8-24Modify Output File Format Level, 7-13Msent, 2-18Msg ID Address, 8-22MsgID2, 8-22Number, 6-8Number of Block Overwritten, 2-24Octel Server System Name, 8-20Option, 2-20, 2-22Output selection, 8-20, 8-23Ports, 8-22Record display, 8-20Record Group, 2-20, 2-21, 2-22Schedule Name, 7-19Sequence Number of Blocks to Retrieve,
7-37
E–F
INDEX
Index-13Edition 2Octel PC/CDR
Sequence Number of First Block toRetrieve, 7-37
Source Drive Name, 3-3, 3-13System, 7-13System ID, 8-24System/Program Name 1, 7-20, 7-21System/Program Name 2, 7-21Target File, 8-26Times, 8-22Total Events, 8-24Total Number of Blocks for CDR, 10-4Type of Terminal on This Channel, 4-8,
4-15, 4-21Update autoexec.bat & config.sys?, 3-3,
3-13Upgrade Octel PC/CDR Software?, 3-13
File Backup Menu, 8-14
File Erase Menu, 8-16
File formatdefined, 1-5, Glossary-5type, defined, Glossary-6types, Glossary-5
File-format leveldefined, Glossary-6described, 5-15output files affected, 5-16
File Maintenance, using DOS utilities, 8-10through 8-11
File namesdefined, 1-5, Glossary-6naming conventions
binary collection files (BCFs), 1-12,1-13
caller-menu output (CMO) files, 9-2CDR system log files, 1-15 through
1-16collated day files (CDFs), 1-14disk-usage output (DUO) files, 9-4fax output (FXO) files, 9-6forms output (FDO) files, 9-8individual-port-statistics output (PSO)
files, 9-11message-detail output (MDO) files,
9-14NameNet output (NNO) files, 9-17processed collection files (PCFs), 1-13session-detail output (SDO) files, 9-21unsuccessful-transfer output (UTO)
files, 9-24
File Selection Parameters screen, 8-7
File structures, A-1caller-menu output (CMO) files, A-1disk-usage output (DUO) files, A-4fax output (FXO) files, A-5forms output (FDO) files, A-8individual-port-statistics output (PSO)
files, A-9message-detail output (MDO) files, A-12NameNet output (NNO) files, A-18profile-change-details output (PRO) files,
A-20session-detail output (SDO) files, A-22unsuccessful-transfer output (UTO) files,
A-31
File typedefined, Glossary-6
File Utilities Menu, 8-1 through 8-36Backup Octel PC/CDR Files option, 8-10
through 8-14described, 8-1options
display disk status, 8-2display Octel PC/CDR files, 8-3
through 8-4erase Octel PC/CDR files, 8-14
through 8-16restore Octel PC/CDR files, 8-16view/print Octel PC/CDR files, 8-4
through 8-10
FilesSee also File names; Subdirectories;
UtilitiesAUTOEXEC.BAT, 3-1
updating during installation, 3-3updating during upgrade, 3-13
autoexec.bat, G-2backing up
backup utility errors, 7-6DOS version compatibility, 4-2Octel PC/CDR files, 8-10 through 8-14PC requirements, 4-1
BCF renamed PCF, 1-12binary collection files (BCFs), described,
1-12 through 1-13CC subdirectory files, D-2collated day files (CDFs)
described, 1-14searching, 8-18 through 8-25
CONFIG.SYS, 3-1updating during installation, 3-3updating during upgrade, 3-13
F
INDEX
Index-14 Edition 2 Octel PC/CDR
config.sys, G-2copying binary collection files (BCFs),
8-25 through 8-29created during installation, 3-5deleting
binary collection files (BCFs), 5-5collated day files (CDFs), 5-5 through
5-6log files, 5-6Octel PC/CDR files, 8-14 through 8-16output files, 5-6schedule log file, 7-36
displayingbinary collection files (BCFs), 8-29individual-port-statistics output (PSO)
files, 9-12log files, 8-4 through 8-10Octel PC/CDR files, 8-3, 8-4output files, 8-4 through 8-10pending-state files (PSFs), 8-34processed collection files (PCFs), 8-34revision date, 8-36
illustrated, 1-11log files
CDR system log files, 1-15 through1-16
creating subdirectory, 3-6 through 3-9dated log files, 1-15 through 1-16deleting, 5-6locating entries, 7-4printing, 8-4 through 8-10SCHEDCDR.LOG, 1-16, 3-1, 7-30schedule log file, 1-16schedule-log-file entries, F-1 through
F-2scheduler log file, 7-30viewing, 8-4 through 8-10
LOG subdirectory files, D-1MIR subdirectory files, D-1OCTELCDR subdirectory files, D-1output files
See also individual output file namesautomatic generation, 5-7backing up, 8-10 through 8-14deleting, 5-6described, 1-16, 9-1 through 9-25empty, 7-11format level, 5-15format types, 5-8generating, 9-1 through 9-2interpreting output, A-1manual generation, 7-11
naming conventions, 9-2no data, 7-11printing, 8-4 through 8-10selecting, 8-5 through 8-8software upgrade impact, 3-10viewing, 8-4 through 8-10
pending-state files (PSFs)COLLATE.PSF, described, 1-14
through 1-15COMPRSP.PSF, described, 1-15dated, described, 1-14 through 1-15described, 1-14 through 1-15
processed collection files (PCFs),described, 1-13
restoringOctel PC/CDR files, 8-16 through 8-17schedule log file, 7-34schedule parameter file, 7-26
SCHEDCDR.LOG, 7-4created, 7-4restoring, 7-34
SCHEDCDR.PARbacking up, 7-24restoring, 7-26
schedule log file, displaying, 7-31schedule parameter file, 7-26scheduler log file, 7-30
Format, output filelevel, 5-15types, 5-8
Forms output (FDO) filesSee also Output filescreating FDO subdirectory, 3-6defined, Glossary-6described, 9-8 through 9-10, A-8file structure, A-8File-Processing Summary screen, 9-10naming conventions, 9-8port 255 entries, A-8printed report example, 9-9subdirectory, 9-8
Formulas for estimating CDR buffercapacity, 2-7 through 2-10, 10-3through 10-5
FP event details, B-27
FR event details, B-27, B-28
FRTS event details, B-28
Function keysdefined, Glossary-6Wyse 50 terminal emulation, 5-18
F
INDEX
Index-15Edition 2Octel PC/CDR
FXO File-Processing Summary screen, 9-8
FXO filesSee Fax output (FXO) files
FXO subdirectory, 3-6, 9-7
G
GEN_ERR event details, B-28
GET_ROUTE event details, B-28
Greetingdefined, Glossary-7
H
Hardwareconfiguration, 4-18 through 4-23equipment configuration procedures, 11-2optional, 4-3requirements, 4-1 through 4-3
Hubdefined, Glossary-7
I, J
IC event details, B-28
In-band integrationdefined, Glossary-7
Individual-port-statistics output (PSO) filesSee also Output filesCOMPRSP.PSF, 1-15creating PSO subdirectory, 3-6defined, Glossary-7described, 9-10 through 9-14, A-9file structure, A-9 through A-12file-format level references, 9-11File-Processing Summary screen, 9-13files without data, 9-12format level, 5-16naming conventions, 9-11pending-state file created, 1-15printed report example, 9-12subdirectory, 9-12viewing data, 9-12
Initial Session-Detail Output File Processingscreen, 7-12
Installation, checklist, 1-3 through 1-4
Installation Program Menu, 3-2configuring, 3-2field descriptions
Boot Drive Name, 3-3, 3-13Destination Drive, 3-3Destination Drive Name, 3-13Install Octel PC/CDR Software?, 3-3Source Drive Name, 3-3, 3-13Update autoexec.bat & config.sys?,
3-3, 3-13Upgrade Octel PC/CDR software?, 3-13
INSTCDR.EXE utilityAUTOEXEC.BAT changes, 3-1, 3-3CONFIG.SYS changes, 3-1, 3-3files created, 3-5menu, 3-2subdirectories created, 3-1
IPL event details, B-29
IVR_EXIT event details, B-29
K
KeyboardWyse 50 emulation, 5-18
L
Linkdefined, Glossary-7
LIST_CHG event details, B-30
Log filesCDR system log files
backing up, 1-16deleting/erasing, 1-16described, 1-15 through 1-16naming convention, 1-15 through 1-16printing, 1-15 through 1-16subdirectory, 1-15 through 1-16viewing, 1-15 through 1-16
creating subdirectory, 3-6 through 3-9dated log files
See CDR system log filesdefined, Glossary-7deleting, 5-6described, 1-15 through 1-16
F–L
INDEX
Index-16 Edition 2 Octel PC/CDR
displaying, 8-4 through 8-10locating entries, 7-4printing, 8-4 through 8-10SCHEDCDR.LOG
described, 1-16subdirectory, 1-16
schedule log file, 1-16, 3-1example, 7-31
schedule-log-file entries, F-1 through F-2updating scheduler log files, 7-30 through
7-36backing up, 7-32 through 7-35erasing, 7-35listing, 7-31printing, 7-31, 7-32restoring, 7-34 through 7-35
viewing, 8-4 through 8-10
LOG subdirectory, 3-1, D-1
Lost data counter, 2-23
M
Main MenuOctel PC/CDR, 7-17View Octel PC/CDR Output Files, 8-5
Mailboxdefined, Glossary-7name defined, Glossary-7number defined, Glossary-8
Manual processing, 7-6 through 7-13collating BCFs into CDFs, 7-9 through
7-10defined, Glossary-8described, 7-6downloading Octel PC/CDR data, 7-7
through 7-8DTMF OctelForms data, 10-6output-file generation, 7-11 through 7-13preparation, 7-2 through 7-6
creating more storage space, 7-6data transfer, 7-3, 7-4error messages, 7-5, 7-6log file entries, 7-4, 7-5partially filled blocks, 7-4preliminary tasks, 7-2transmission messages, 7-5, 7-6
processing overview, 7-1steps, 1-3
MaxumCDR buffer
disabling, 2-2size, 2-2system drive storage space used, 2-3
equipment configuration, 4-12 through4-17
port statistics, 9-11
Maxum SECDR buffer
disabling, 2-2size, 2-2system drive storage space used, 2-3
equipment configuration, 4-12 through4-17
port statistics, 9-11
MD event details, B-30, B-31
MDO File-Processing Summary screen, 9-16
MDO filesSee Message-detail output (MDO) files
MDO subdirectory, 3-6, 9-15
mem command, G-2
Menu flowdescribed, 1-6illustrated, 1-7 through 1-9
Menus for Octel PC/CDRAutomatic Processing Schedule, 7-28Automatic Schedule Editor Menu, 7-21Automatic Schedule Menu, 7-17
options, 7-17Begin File Transfer screen, 7-3Call Detail Records Collected (menu
16.1.4)accessing, 2-18example, 2-19
Carbon Copy PLUS, System Parametersmenu, 6-3
COPYBCF Options menu, 8-28Database Access (menu 16)
accessing, 2-18example, 2-18, 2-19
Displaying Binary Collection File option,8-29
DUMPBCF Options menu, 8-31File Backup Menu, 8-14File Download Settings Menu, 7-8File Erase Menu, 8-16File Utilities Menu, 8-1, 8-2Installation Program menu, 3-2
L–M
INDEX
Index-17Edition 2Octel PC/CDR
Main Menu, 5-2, 7-17Main Menu (View Octel PC/CDR Output
Files), 8-5Manage Call Detail Recording (Menu
16.1), 2-18accessing, 2-18
Manual Octel PC/CDR Processing Menu,7-7
Menu 16 – Database Access, Retrieve CallDetail Records, 7-39
Menu 6.3 – Dialing and Serial ChannelParameters, 4-16
Modify Automatic Output File GenerationMenu, 7-15
Modify Automatic Output File Generationmenu, 5-8
Modify Output File Format Types menu,5-9
Modify PC Communications Parametersmenu, 5-10
Octel PC/CDR File Download SettingsMenu, 7-8
Octel PC/CDR Processing Menu, 7-7Output File Generation Menu, 7-12Processing Menu, 7-7Retrieve Call Detail Records, 7-39Scheduler Log File menu, 7-30Search Collated Day File Utility Menu,
8-19Select a Binary Collection File menu, 8-27Select a Pending State File menu, 8-35Service Utilities Menu, 8-18Session Detail Output File Type menu,
5-9SMT Menu, 7-39System Attributes Menu, 5-4, 5-15, 5-16System Attributes menu, 7-2System Data Directory Creation screens,
3-8System Menu, 5-2, 7-7, 7-37, 8-2Update Automatic Processing Schedules
menu, 7-18Update Automatic Scheduler Log File
menu, 7-30Upgrade Program menu, 3-12View Octel PC/CDR Output Files Option
(Main Menu), 8-5
Message serverSee Server
Message waitingdefined, Glossary-8
Message-detail output (MDO) filesSee also Output filescode values, A-14, A-15, A-16, A-17creating MDO subdirectory, 3-6defined, Glossary-8, 9-14 through 9-16descriped, A-12 through A-17file structure, A-12, A-13file-format level, 5-16file-format level references, 9-15File-Processing Summary screen, 9-16
through 9-17files without data, 9-15naming convention, 9-14network messages, 9-14printed report example, 9-15subdirectory, 9-15
Message-receipt records, 9-14
MessagesSee also Error messages; Transmission
messagesdata collection, 2-17transmission messages, 7-5, E-1 through
E-2
MIR subdirectory, 3-1, D-1
MIRROR IICarbon Copy PLUS with, 6-1data transfer, 7-3data-transfer-verification method, 7-3defined, Glossary-8Wyse 50 special-emulation function keys,
5-18XMODEM file transfer protocol, 7-3
MIRROR II subdirectory, 3-1
MKCDRSYS utilitycreating data subdirectory, 3-6 through
3-9subdirectories created, 3-6syntax, 3-7system attribute configuration, 5-3
through 5-16
Modemsbaud rate, 4-2, 5-11, 6-4Carbon Copy PLUS, 6-1 through 6-6
comm port address, 6-3parameters, 6-4remote connection configuration, 6-2requirements, 6-1
checking connections, 11-6com port address, 6-3
M
INDEX
Index-18 Edition 2 Octel PC/CDR
communications parameters, 5-9 through5-14
connecting cables, 11-4connection type, 4-4, 5-11connectors required, 4-4data transfer, 7-3defined, Glossary-8dial prefix string, 5-12dial suffix string, 5-12direct connection, defined, Glossary-4echo on/echo off codes, 11-6equipment installation responsibility, 4-2initialization string, 5-12Octel Overture 250, modem connection to
CDR PC, illustrated, 4-5Octel Overture 350, modem connection to
CDR PC, illustrated, 4-6Octel XC1000
modem connection to CDR PC forAspen software releases 1through 1.3X, illustrated, 4-19
modem connection to CDR PC forAspen software releases 1.5X andnewer, illustrated, 4-18
PC requirements, 4-2PC-to-server communications, 4-2port, 5-11protocol, file transfer, 7-3remote connection, defined, Glossary-10service communications, 6-1service communications type, 6-4types, 6-4
Modify Automatic Output File Generationmenu, 5-8, 7-15
Modify Output File Format Types menu, 5-9,Glossary-6
Modify PC Communications Parametersmenu, 5-10 through 5-12
Communication Port: field, 5-11defaults, 5-10suboptions, 5-11
communication port, 5-11communication speed (baud), 5-11connection type, 5-11dial prefix string, 5-12dial suffix string, 5-12modem initialization string, 5-12Octel server software version number,
5-13Octel server system password, 5-14
Octel server system type, 5-13Octel server telephone number, 5-12terminal emulation type, 5-13
testing communications parameters,5-14, 5-17
MS event details, B-32 through B-34
MSG_CNT event details, B-34
MSG_RVW event details, B-35
MW event details, B-36
N
NameNetdefined, Glossary-8
NameNet output (NNO) filesSee also Output filescode value, A-19creating NNO subdirectory, 3-6defined, Glossary-8described, 9-17 through 9-18description, A-18, A-19file structure, A-18File-Processing Summary screen, 9-18
through 9-19files without data, 9-17naming convention, 9-17printed report example, 9-17printing, limitations, 9-17subdirectory, 9-17
NamesCDR system name
defined, 1-4displaying valid, 1-5
file name, term defined, 1-5
Naming conventionsbinary collection files (BCFs), 1-12, 1-13caller-menu output (CMO) file, 9-2
through 9-3CDR system log files, 1-15 through 1-16collated day files (CDFs), 1-14dated pending-state files (PSFs), 1-15disk-usage output (DUO) files, 9-4fax output (FXO) files, 9-6file names, 1-5forms output (FDO) file, 9-8individual-port-statistics output (PSO)
files, 9-10message-detail output (MDO) files, 9-14
M–N
INDEX
Index-19Edition 2Octel PC/CDR
NameNet output (NNO) files, 9-16processed collection files (PCFs), 1-13profile-change-details output (PRO) files,
9-18, 9-19, 9-20session-detail output (SDO) files, 9-21,
9-22, 9-23unsuccessful-transfer output (UTO) files,
9-25
Network messages, 9-14
Networkingdefined, Glossary-8
NNET_ALARM event details, B-36
NNET_DIR event details, B-36
NNET_NAME event details, B-37
NNO File-Processing Summary screen, 9-18
NNO filesSee NameNet output (NNO) files
NNO subdirectory, 3-6, 9-17
Nodedefined, Glossary-8
Non-service-affecting (NSA) alarmsdefined, Glossary-8generated, 1-12
O
OC event details, B-37, B-38
OCL_NAME event details, B-38
Octel Overture 250See also Serversbaud rate requirements for downloading,
4-8CDR buffer, 2-2Dialing and Serial Channel Parameters
menu, 4-10direct connection to CDR PC, illustrated,
4-5equipment configuration, 4-4illustrated, 4-5invalid port numbers, 9-11modem connection to CDR PC, illustrated,
4-5port statistics, 9-11procedures, 4-7
Octel Overture 350See also Serversbaud rate requirements for downloading,
4-8CDR buffer, 2-2Dialing and Serial Channel Paremeters
menu, 4-10direct connection to CDR PC, illustrated,
4-6equipment configuration, 4-4illustrated, 4-6individual-port-statistics (PSO) file
structure, A-11invalid ports, 9-11modem connection to CDR PC, illustrated,
4-6port statistics, 9-11procedures, 4-7
Octel PC/CDRSee also individual screens by subjectaccess, 5-1 through 5-3Automatic Octel PC/CDR Schedule Editor
menu, 7-21automatic processing, 7-13 through 7-15benefits to system managers, 1-1compatibility with server software, 1-2configuration, remote connection with
internal modems, illustrated, 6-2defined, Glossary-9description of application, 1-1disk-directory structure, 3-7equipment requirements, 4-1installing on the PC
AUTOEXEC.BAT changes, 3-1 through3-5
CONFIG.SYS changes, 3-1 through 3-5configuring the Installation Program
menu, 3-2files created, 3-5Installation Program menu fields, 3-3root directory modifications, 3-1
through 3-5steps, 3-2subdirectories created, 3-1Update Program Menu fields, 3-13
loading software into memory, 5-1through 5-3
logging processing output to printer, 5-5personal computers (PC) requirements,
4-1printing files, considerations, 8-4process checklist, 1-3 through 1-4software attributes, 5-1 through 5-18
N–O
INDEX
Index-20 Edition 2 Octel PC/CDR
subdirectory structure, 3-7upgrading Octel PC/CDR software, 3-10
through 3-14upgrading software, 3-10 through 3-14
CDR buffer download frequency andstorage needs, 3-11
considerations, 3-10effect on billing programs, 3-10new output files required, 3-11upgrade procedure, 3-12 through 3-14
viewing files, considerations, 8-4
Octel PC/CDR Automatic Schedule Menuillustrated, 7-18steps, 7-31
Octel PC/CDR file option, output files,generating, 9-1
Octel PC/CDR files, displaying, 8-4
Octel PC/CDR System Attributes Menu, 7-2
Octel PC/CDR Troubleshooting Form, G-1
Octel PC/CDR Main Menu, 5-2, 7-2, 7-18
Octel XC1000active channels, example, 4-22CDR buffer
size, 2-2storage space allocated, 2-2system drive storage space used, 2-3
configuringshared port for SMT and CDR PC, 4-23verifying changes, 4-23
configuring separate ports, 4-19 through4-23
Dialing and Serial Channel ParametersMenu, example, 4-22
direct connection to CDR PCAspen Releases 1 through 1.3X,
illustrated, 4-19Aspen Releases 1.5X and newer,
illustrated, 4-18equipment configuration, 4-18 through
4-23establishing the channel, 4-20 through
4-22individual-port-statistics (PSO) file
structure, A-11invalid ports, 9-11Main Menu (SMT), 4-22
Menu 6.3, 4-22modem connection to CDR PC
Aspen Releases 1 through 1.3X,illustrated, 4-19
Aspen Releases 1.5X and newer,illustrated, 4-18
port statistics, 9-11ports, shared, 4-23SMT port connection, 4-19verifying Menu 6.3, 4-23
OCTELCDR subdirectory, 3-1, D-1
OcteLink, hub, Glossary-7
OctelNetdefined, Glossary-9
ON_HOOK event details, B-38
Online CDRdefined, Glossary-9
Outcallingdefined, Glossary-9
Output File Generation Menu, 7-12
Output File Processingscreen, field description, 7-13summary screen, 9-5, 9-6
Output files, 9-1 through 9-25, A-1 throughA-32
See also specific file typesASCII format, 9-1automatic generation, 5-7backing up, 8-10 through 8-14caller-menu output (CMO) files, 9-2, 9-3CDR events, 7-11creating subdirectory, 3-6 through 3-9dBASE III format, 9-1defined, Glossary-9deleting, 5-6described, 9-1 through 9-25
disk-usage output (DUO) files, 9-4fax output (FXO) files, described, 9-6individual-port-statistics output (PSO)
files, 9-10message-detail output (MDO) files,
9-14NameNet output (NNO) files, 9-17profile-change details output (PRO)
files, 9-19session-detail output (SDO) files, 9-21unsuccessful-transfer output (UTO)
files, 9-24
O
INDEX
Index-21Edition 2Octel PC/CDR
displaying, 8-4 through 8-10file structures
caller-menu output (CMO) files, A-1,A-2
disk-usage output (DUO) files, A-4fax output (FX) files, A-5forms output (FDO) file, A-8individual-port-statistics output (PSO)
files, A-9message-detail output (MDO) files,
A-12, A-13NameNet output (NNO) files, A-18profile-change-detail output (PRO) files,
A-20session-detail output (SDO) files, A-22,
A-23unsuccessful-transfer output (UTO)
files, A-31file-format levels, 5-15, 5-16file-format types, 5-8forms output (FDO) files, described, 9-8importing, 1-4manual generation, 7-11 through 7-13naming conventions
caller-menu output (CMO) files, 9-2disk-usage output (DUO) files, 9-4fax output (FXO) files, 9-6forms output (FDO) files, 9-8individual-port-statistics output (PSO)
files, 9-11message-detail output (MDO) files,
9-14NameNet output (NNO) files, 9-17profile-change details output (PRO)
files, 9-19session-detail output (SDO) files, 9-21unsuccessful-transfer output (UTO)
files, 9-24overview, 1-16, 9-1 through 9-2printing, 8-4 through 8-10, 9-1references, 9-2selecting, 8-5 through 8-8term defined, 1-5viewing, 8-4 through 8-10, 9-1
P, Q
Pager outcalls, 9-21
Parameter fileSee Schedule parameter file
Parameters, configuring, 5-3
Password Table screen, 6-5
PasswordsCarbon Copy PLUS password table, 6-5defined, Glossary-9forgotten schedule password, 7-29schedule password, updating, 7-29
through 7-30systemmanager, 5-14
PBX (private branch exchange)defined, Glossary-9See CDR PC
PC communications parametersbaud rate, 5-11Carbon Copy PLUS, 6-3connection type, 5-11dial prefix string, 5-12dial suffix string, 5-12modem initialization string, 5-12port, 5-11software version number, 5-13system password, 5-14system type, 5-13telephone number, 5-12terminal emulation type, 5-13testing, 5-17
PC requirements, 4-1 through 4-3
PCFsSee Processed collection files (PCFs)
PCsSee Personal computers (PC)
Pending-state files (PSFs)COLLATE.PSF
backing up, 1-15described, 1-14subdirectory, 1-15
COMPRSP.PSFdescribed, 1-15subdirectory, 1-15
creating PSF subdirectory, 3-6 through3-9
dated, described, 1-14 through 1-15dated files
backing up, 1-15subdirectory, 1-15
defined, Glossary-9deleting/erasing, 1-15described, 1-14 through 1-15displaying, 8-34selecting, 8-34
O–P
INDEX
Index-22 Edition 2 Octel PC/CDR
Personal computers (PC)See also CDR PCbaud rate, 5-11Carbon Copy PLUS requirements, 6-1checking available disk space, 2-14direct connection test, 5-17downloading CDR buffer
frequency, 3-11, 10-5time required, 10-6
installing Octel PC/CDR, 3-1 through 3-5memory shortage, 9-12remote access, 6-1 through 6-10remote connection configuration, 6-2requirements, 4-1 through 4-3
clock, 4-2disk drive, 4-2disk space, 10-6disk space, estimating, 2-13 through
2-14estimating formula, 2-13modems, 4-2optional hardware, 4-3overview, 4-1parallel port, 4-2performance, 4-1ports, 4-2server-to-PC connectors, 4-4
SMT emulation, 5-17 through 5-18software requirements, 4-3Wyse 50 special-emulation function keys,
5-18
Portscommunications port, 5-11defined, Glossary-10PC requirements, 4-2printer requirement, 4-2
PORTS_BUSY event details, B-38
Pound keydefined, Glossary-1
Print Selection Parameters screen, 8-10
Printer requirements, 4-2
PrintingCDR system log files, 1-15 through 1-16hard-copy for DOS commands, G-2hard-copy of screens, G-2log files, 8-4 through 8-10output files, 8-4 through 8-10, 9-1processing results, 5-5schedule log file, 7-32
PRO File-Processing Summary screencolumn descriptions, 9-20illustrated, 9-20printed report example, 9-20
PRO filesSee Profile-change-details output (PRO)
files
PRO subdirectory, 3-6, 9-19
Process checklist, 1-3 through 1-4
Processed collection files (PCFs)binary collection files renamed as, 5-5collating, 1-13defined, Glossary-10described, 1-13displaying, 8-34naming convention, 1-13subdirectory, 1-13
Processingautomatic processing, 7-13 through 7-15
described, 7-13output file generation, 5-7preparation, 7-14 through 7-15processing overview, 7-1scheduled, 7-16 through 7-18starting methods, 7-15
avoiding lost data, 1-2checklist, 1-3 through 1-4data, illustrated, 1-11DTMF OctelForms data, 10-6manual processing, 7-6 through 7-13
collating BCFs into CDFs, 7-9 through7-10
described, 7-6 through 7-13downloading Octel PC/CDR data, 7-7output file generation, 7-11 through
7-13processing overview, 7-1
methodsautomatic processing, 1-3described, 7-1manual processing, 1-3scheduled automatic processing, 1-3steps, 1-3
preparation, 7-2 through 7-6creating more disk-storage space, 7-6creating more storage space, 7-6data transfer, 7-3error messages, 7-5locating log file entries, 7-4partially filled blocks, 7-4
P
INDEX
Index-23Edition 2Octel PC/CDR
tasks, 7-2transmission messages, 7-5
scheduled automatic processing, 7-16through 7-36
described, 7-16processing overview, 7-1schedule log file example, 7-31updating schedules, 7-18
scheduled-automatic processing, outputfile generation, 5-7
schedule-log-file entries, F-1 through F-2sequence
described, 1-10illustrated, 1-11
service-level download, 7-36 through 7-40described, 7-36using DOS, 7-40using the System Menu, 7-37 through
7-39starting automatic scheduler mode, 7-27steps, 7-1updating automatic-scheduler log files,
7-30updating schedule password, 7-29
Processing methods, overview, 7-1
Processing Schedule screen, 7-27
PROF_TYPE (PT) codes, PRO files, A-21
PROFILE_CHG event details, B-38
Profile-change-details output (PRO) filesSee also Output filescode value, A-21creating PRO subdirectory, 3-6defined, Glossary-10described, 9-19 through 9-20description, A-20, A-21file structure, A-20File-Processing Summary screen, 9-20
through 9-21files without data, 9-19naming convention, 9-19printed report example, 9-19printing, limitations, 9-19subdirectory, 9-19
PSFsSee Pending-state files (PSFs)
PSO File-Processing Summary screencolumn descriptions, 9-14illustrated, 9-13printed report example, 9-12
PSO filesSee Individual-port-statistics output (PSO)
files
PSO subdirectory, 3-6, 9-12
PW_TYPE (PW) codes, PRO files, A-21
PWT event details, B-39
PWT_RJCT event details, B-39
R
Raw data files, 1-12
REASON (RC) codesUTO files, A-31
Referenceprocess checklist, 1-3 through 1-4
Rejected events, 7-10
Release numberdisplaying, 8-36
Remote connectiondefined, Glossary-10
Removing CDR system data subdirectories,3-9 through 3-10
Renaming BCFs as PCFs, 5-5
Reportsgenerating, 1-4
RequirementsCarbon Copy PLUS, 6-1CDR processing time, 2-10 through 2-14downloading, avoiding lost data, 1-2PC storage, 2-10 through 2-14personal computers (PC), 4-1 through 4-3
clock, 4-2disk drive, 4-2DOS version, 4-2modems, 4-2optional hardware, 4-3overview, 4-1performance, 4-1ports, 4-2server-to-PC connectors, 4-4software, 4-3
processing, avoiding lost data, 1-2storing data, avoiding lost data, 1-2
P–R
INDEX
Index-24 Edition 2 Octel PC/CDR
RestoringOctel PC/CDR files, 8-16 through 8-17schedule log file, 7-34schedule parameter file, 7-26
Retrieve Call Detail Records menu, 7-39
Revision datedisplaying, 8-36
RMCDRSYS utility, 3-9
Root directorydefined, Glossary-10
RSS event details, B-39
S
S R (SR, Sender/Receiver) codesMDO files, A-16, A-17
SCHEDCDR command, 7-28
SCHEDCDR.LOGdescribed, 1-16file, 7-4, 7-30 through 7-36restoring, 7-34subdirectory, 1-16
SCHEDCDR.PAR file, 7-24, 7-26
Schedule log file, 3-1backing up, 7-32defined, Glossary-7deleting/erasing, 7-36described, 1-16example, 7-31listing, 7-31printing, 7-32restoring, 7-34subdirectory, 1-16
Schedule parameter filedefined, Glossary-10restoring, 7-26
Schedule password, 7-29
Scheduled automatic processing, 7-16through 7-36
adding new schedules, 7-18 through 7-21automatic scheduler log file, 7-33 through
7-39backing up data, 7-22
schedule log file, 7-35 through 7-39schedule parameter file, 7-27 through
7-29
defined, Glossary-10described, 7-16DTMF OctelForms data, 10-6edit existing schedule, 7-22, 7-25erase schedule, 7-22important information, 7-16passwords required, 7-16listing exsisting schedules, 7-23preparation, 7-2 through 7-6
data transfer, 7-3error messages, 7-4locating log file entries, 7-4partially filled blocks, 7-4tasks, 7-2transmission messages, 7-4
printing existing schedules, 7-24restore schedule parameter file, 7-26schedule log file, 3-1schedule parameter file entries, F-1
through F-2schedule-log file entries, F-1 through F-2scheduler log file, 7-30 through 7-36starting automatic scheduler mode, 7-27
setting date and time, 7-27using DOS, 7-28
steps, 1-3, 7-1updating schedule password, 7-29updating schedules, 7-18 through 7-26
Schedule-log file, entries, F-1 through F-2not requiring action, F-1requiring action, F-1
Scheduler log file, 7-30 through 7-36
SchedulesSee also Scheduled automatic processingautomatic processing schedules
adding, 7-18backing up, 7-24backing up parameter file, 7-24deleting, 7-22editing, 7-22listing, 7-23printing, 7-24removing, 7-22restoring schedule parameter file, 7-26timer, 7-27
password, 7-29schedule log file, 3-1
backing up, 7-32 through 7-34deleting/erasing, 7-36entries, F1 through F2example, 7-31
R–S
INDEX
Index-25Edition 2Octel PC/CDR
listing, 7-31printing, 7-32restoring, 7-34
Scrolldefined, Glossary-10
SDO File-Processing Summary screencolumn descriptions, 9-23illustrated, 9-22printed report example, 9-22
SDO filesSee Session-detail output (SDO) files
SDO subdirectory, 3-6, 9-22
Search Collated Day File Utility Menu, 8-18through 8-25
field descriptions, 8-20, 8-21illustrated, 8-19setting entries, 8-19 through 8-21
Search Criteria Screen, field descriptions,8-22
Search Summary Screen, 8-24
SecuritySee also PasswordCarbon Copy PLUS, 6-6running automatic processing
unattended, 7-27
Segmentdefined, Glossary-11
SEIZE event details, B-39
Select a Binary Collection File menu, 8-27
Select a Pending State File menu, 8-35
Serverbaud rate, 5-11CDR buffer, 2-2channel identification, 11-3checking for overwritten blocks, 2-14collecting data, 2-2configuring for CDR data collection, 2-14,
2-14defined, 1-1, Glossary-11direct connection test, 5-17displaying call detail records collected,
example, 2-16displaying installed software features,
example, 2-16
drives, storage space used (in MB), 2-2enabling features, 2-15
audio messaging interchangespecification (AMIS), 2-15
DTMF OctelForms, 2-15selecting record groups for collection,
2-16 through 2-22server-to-PC connectors, 4-4shutting down, 5-17software, compatibility with Octel
PC/CDR software, 1-2software
release, CDR buffer size, 2-2requirements, 4-3version number, 5-13
system type for communications, 5-13telephone number, 5-12term defined, 1-5
Service-affecting (SA) alarmsdefined, Glossary-11
Service information, 11-1channel identification, 11-3checking server-modem configuration,
11-6connecting cables, 11-4 through 11-5equipment configuration procedures, 11-2establishing Octel PC/CDR attributes for
communication with server, 11-6verifying menu 6.3 changes, 11-6
Service-level downloaddefined, Glossary-11described, 7-36executing, 7-36 through 7-40System Menu, 7-37using DOS, 7-40
Service representativeCarbon Copy PLUS responsibilities, 6-8Troubleshooting Form, G-1 through G-2
Service utilitiesSee Utilities
Service Utilities Menu, 8-18copy binary collection file, 8-25display binary collection file, 8-29display pending state file, 8-34search collated day file, 8-18
Service-affecting (SA) alarmsdefined, Glossary-11generated, 1-12
S
INDEX
Index-26 Edition 2 Octel PC/CDR
Sessiondefined, 1-5, Glossary-11relationship to calls and events,
illustrated, 1-6
Session Detail Output File Type menu, 5-9
SESSION event details, B-39
Session-detail output (SDO) filesSee also Output filescode value, A-24 through A-30creating SDO subdirectory, 3-6defined, Glossary-11described, 9-21 through 9-23, A-22
through A-30file structure, A-22, A-23file-format -level references, 9-21File-Processing Summary screen, 9-22files without data, 9-22format level, 5-15, 5-16naming conventions, 9-21, A-22printed report example, 9-22printing, limitations, 9-21record types, 9-21 through 9-23
set command, G-2
Shutdown from PC, 5-18
Sierraconfiguration, 4-18 through 4-23system type for communications, 5-13
SMS event details, B-39
SMSG_ALERT event details, B-39
SMSG_DELVR event details, B-39
SMSG_INFO event details, B-39
SMSG_REPORT event details, B-39
SMSG_STFWD event details, B-40
SMT emulationdefined, Glossary-11function keys, 5-18steps to establish, 5-17testing the direct connection, 5-17
through 5-18
Softwarecompatibility, server and Octel PC/CDR
releases, 1-2requirements, 4-3upgrading Octel PC/CDR software, 3-12
Source mailboxdefined, Glossary-11
Star keydefined, Glossary-1
STATUS (Sta) codes, NNO files, A-19password, 5-14
Status Window, 8-8
Storageavoiding lost data, 1-2creating more space before processing,
7-6displaying disk status, 8-2 through 8-3PC requirements, 10-6warning for low storage space, 5-2, 7-7
Subdirectoriesbinary collection files (BCFs), 3-6caller-menu output (CMO) files, 3-6Carbon Copy PLUS, 3-1CC, 3-1CMO, 9-3collated day files (CDFs), 1-14, 3-6creating
instcdr.exe utility, using, 3-1MKCDRSYS command (data
subdirectories), 3-6 through 3-9program subdirectories, 3-1
deleting data subdirectories, 3-9directory tree structure, 3-7disk-usage output (DUO) files, 3-6displaying Octel PC/CDR files, 8-2DUO, 9-5fax output (FXO) files, 3-6FDO, 9-8forms output (FDO) files, 3-6FXO, 9-7individual-port-statistics output (PSO)
files, 3-6location, BCFs, 1-12LOG, 3-1log files, 3-6message-detail output (MDO) files, 3-6MIR, 3-1MIRROR II, 3-1NameNet output (NNO) files, 3-6OCTELCDR, 3-1pending-state files (PSFs)
COLLATE.PSF, 1-15COMPRSP.PSF, 1-15dated files, 1-15
S
INDEX
Index-27Edition 2Octel PC/CDR
processed collection files (PCFs), 1-13profile-change details output (PRO) files,
3-6PSO, 9-12removing data subdirectories, 3-9SCHEDCDR.LOG, 1-16SDO, 9-22session-detail output (SDO) files, 3-6subdirectory files, D-1 through D-2system attribute files, 3-6unsuccessful-transfer output (UTO) files,
3-6UTO, 9-24
Subscriberdefined, Glossary-11
Subscriber outcalls, 9-21
Syntaxdefined, Glossary-12
SYS subdirectory, 3-6
SystemSee CDR system
System attributes, 5-3 through 5-16automatic output file generation, 5-7communications parameters, 5-9 through
5-14baud rate, 5-11connection type, 5-11dial prefix string, 5-12dial suffix string, 5-12modem initialization string, 5-12port, 5-11terminal-emulation type, 5-13testing, 5-17
configure parameters, 5-4configuring, 5-3, 5-4creating subdirectories, 3-6 through 3-9defined, Glossary-12deleting files
binary collection files (BCFs), 5-5collated day files (CDFs), 5-5 through
5-6log files, 5-6output files, 5-6
establishing, 5-3menu, 5-4, 7-2
next block to download, 5-14option selection
erase all output & binary and log filesbeyond...days, 5-6
erasing binary and collated day filesbeyond...days, 5-5
erasing bindary collection files (BCFs)after collation, 5-5
log processing output to printer, 5-5modify automatic output file
generation, 5-7modify communications parameters,
5-9modify output -file-format level, 5-15modify output -file-format types, 5-8next block to download by automatic
Octel PC/CDR processing, 5-14system parameters, 5-4term defined, 1-5testing the direct connection, 5-17
System Attributes Menuautomatic-processing method, 7-14illustrated, 5-4, 5-15, 7-2next block to download, 5-14, 5-15
System Data Directory Creation screen, 3-8
System drives, storage space used (in MB),2-2
System managerdefined, Glossary-12password, 5-14responsibilities, 6-7
System manager terminal (SMT)defined, Glossary-12terminal emulation type, 5-13Wyse 50 special-emulation function keys,
5-18
System Menuaccessing, 5-1 through 5-3file utilities, 8-2illustrated, 7-7, 8-2service-level download, 7-37using, 7-37 through 7-40
System nameaccessing the System Menu, 5-3defined, 1-5determining, 5-3displaying valid names, 1-5listing established CDR systems, 5-3
S
INDEX
Index-28 Edition 2 Octel PC/CDR
System namesdefined, Glossary-12service-level-download command, 7-40
System Parameters menu (Carbon CopyPLUS), 6-3
SYSTEMNAME command, 7-40
T
Telephone-answering modedefined, Glossary-12
TERM ACT (TA) codes, SDO files, A-27
TERM_CODE (TC) codes, FXO files, A-6, A-7
TERMCODE (TC) codes, SDO files, A-27through A-30
TIGON event details, B-40
Timer, automatic scheduler, 7-27
TNE event details, B-40
Trafficdefined, Glossary-12
Transaction log file, Glossary-7
Transmission blocks, 7-3
Transmission messagesfrom CDR PC, E-2from server, E-1understanding messages, 7-5
Treesdefined, Glossary-12
TREES_FCD event details, B-40
TREES_FMB event details, B-40
TREES_FQA event details, B-40
Troubleshooting, using service-leveldownload, 7-36
Troubleshooting Form, G-1 through G-2
Truncatedefined, Glossary-12
TRS event details, B-40
TUT (TU) codes, SDO files, A-30
TUT event details, B-40
TYPE (TP) codes, MDO files, A-17
type command, G-2
U
Unreadable data, 9-12See Output files
Unsuccessful-transfer output (UTO) filesSee also Output filescode value, A-31creating UTO subdirectories, 3-6defined, Glossary-12described, 9-24 through 9-25, A-31file format, 9-25file structure, A-31File-Processing Summary screen, 9-25files without data, 9-25naming convention, 9-24printed report example, 9-24printing, limitations, 9-24record types, 9-24 through 9-25subdirectory, 9-24
Update Automatic Processing Schedulesmenu, 7-18
Upgrade Program menu, 3-12
UPGRCDR utility, 3-12 through 3-14
UR_CHG event details, B-41
Userdefined, Glossary-12
Utilities, 8-1 through 8-36See also Commandsbacking up Octel PC/CDR files, 8-10
through 8-14using DOS version 3.2 through 5.0,
8-11using DOS version 6.2 or newer, 8-10
CHKREV utility, 8-36copying binary collection files (BCFs),
8-25deleting/erasing Octel PC/CDR files, 8-14
through 8-16disk status display, 8-2 through 8-3displaying
binary collection files (BCFs), 8-29through 8-34
disk status, 8-2Octel PC/CDR files, 8-3 through 8-4Octel PC/CDR release number, 8-36pending-state files (PSFs), 8-34processed collection files (PCFs), 8-34
erasing Octel PC/CDR files, 8-14overview, 8-1
S–U
INDEX
Index-29Edition 2Octel PC/CDR
printing Octel PC/CDR files, 8-4restoring Octel PC/CDR files, 8-16
through 8-17searching collated day files (CDFs), 8-18selecting Octel PC/CDR files, 8-5service utilities, 8-18 through 8-36viewing log files, 8-8viewing Octel PC/CDR files, 8-4viewing output files, 8-8
UTO File-Processing Summary screencolumn descriptions, 9-25illustrated, 9-25printed report example, 9-24
UTO filesSee Unsuccessful-transfer output (UTO)
files
UTO subdirectory, 3-6, 9-24
V
ver command, G-2
View Octel PC/CDR Output Files option(Main Menu), 8-5
View Octel PC/CDR Output Files screenFile Selection Parameters screen, File
format: field, Glossary-6Status Window summary, Glossary-6
Viewingbinary collection files (BCFs), 1-12CDR system log files, 1-15 through 1-16collated day files (CDFs), 1-14
Voice maildefined, Glossary-13
Voice processorsdefined, Glossary-13equipment configurations, 4-12 through
4-17
Voice-digitization rate, 2-3
Voice-messaging modedefined, Glossary-13
VPMODdefined, 1-5, Glossary-13
W
Warning, avoid electrical shock, 4-4, 4-12,4-13, 4-18, 4-19, 11-1
WHO (WH) codes, PRO files, A-21
Wyse 50 terminal emulation, 5-18
X, Y, Z
XC1000See Octel XC1000
XFR event details, B-42
XMODEMdefined, Glossary-13file-transfer protocol, 7-3
U–Z
Top Related