OCTEL CALL DETAIL RECORDS MANUAL

Edition Three

OCTEL

CALL DETAIL RECORDS

P/N 101–1154–000

MANUAL

PUBLICATION HISTORY

Edition Name: Edition ThreeEdition Date: May 1992Printing Date:

Software Release: 1.5

First Printing: May 1992Second Printing: March 1993

Copyright 1993 by Octel Communications Corporation890 Tasman Drive

Milpitas CA 95035-7439

All rights reserved. No part of this book may be reproducedin any form without written permission from

Octel Communications Corporation.

Printed in the United States of America.

)))�$)4)/.��(2%%�#4%,��

��

�#4%,� �/--5.)#!4)/.3� �/20/2!4)/.� 02/$5#%3� ()'(:0%2&/2-!.#%� 6/)#%� 02/#%33/23��

�(%� �#4%,� �!,,� �%4!),� �%#/2$3� -!.!'%-%.4� 0!#+!'%� ��#4%,� �� )3� !.� /04)/.!,

3/&47!2%� 02/'2!-� 4(!4� 02/#%33%3� $!4!� #/,,%#4%$� "9� 4(%� 6/)#%� 02/#%33/2�� $/7.,/!$3

4(%� $!4!� 4/� !� 3%0!2!4%� �� !.$� 3/243� 4(%� $!4!� "9� 35"*%#4� ).4/� /54054� &),%3�� (%� /54054

&),%3� !2%� 4(%.� 42!.3&%22%$� 4/� !� $!4!"!3%� !00,)#!4)/.� 02/'2!-� )&� !$$)4)/.!,� -!.)05,!4)/.

)3� 2%15)2%$�� #4%,� �� #!.� !,3/� "%� 53%$� &/2� 42/5",%3(//4).'� 4(%� 6/)#%� 02/#%33/2�

�()3� %$)4)/.� /&� 4(%� �� 02/6)$%3� ).3425#4)/.3� !"/54

4(%� ).34!,,!4)/.�� #/.&)'52!4)/.�� !.$� 53%� /&� �#4%,� �� %,%!3%� �� !.$� 3/-%

"!3)#� 42/5",%3(//4).'� 4//,3�� 4� )3� ).4%.$%$� &/2� 3934%-� -!.!'%23� !.$� �#4%,

�/--5.)#!4)/.3� !.$� $)342)"54/2� 3%26)#%� 2%02%3%.4!4)6%3�

�(%� -!.5!,� )3� !22!.'%$� ).� 4(%� 3!-%� /2$%2� !3� 4(%� �#4%,� �� /0%2!4).'

3425#452%�� 4(53� 02/6)$).'� %!39:4/:&/,,/7� '5)$%,).%3� &/2� 3)-0,%� /0%2!4)/.�� .

/6%26)%7� /&� 4(%� -!*/2� 34%03� )3� &/5.$� ).� 3%#4)/.� ��

�(2/5'(/54� 4()3� -!.5!,�� 4(%� 4%2-� 6/)#%� 02/#%33/2� )3� 53%$� 4/� 2%&%2� #/,,%#4)6%,9� 4/�

4(%� �30%.�� 2!.#(�� 2!.#(� �� !85-� �� !.$� �!85-� 6/)#%:02/#%33).'� -/$5,%3�

4(%� �#4%,� �� 6/)#%:).&/2-!4)/.:02/#%33).'� 0,!4&/2-�� !.$� 4(%� �)%22!� -5,4)0,%:

!00,)#!4)/.3� 0,!4&/2-�� (%.� 4(%� 4%2-� 6/)#%:02/#%33).'� -/$5,%� )3� 53%$�� )4� 2%&%23

/.,9� 4/� 4(%� �30%.�� 2!.#(�� 2!.#(� �� !85-� �� !.$� �!85-� 6/)#%:02/#%33).'

-/$5,%3�� ,,� 2%&%2%.#%3� 4/� 4(%� �)%22!� -5,4)0,%:!00,)#!4)/.� 0,!4&/2-� !,3/� !00,9� 4/� 4(%

�#4%,� �� 6/)#%:).&/2-!4)/.:02/#%33).'� 0,!4&/2-�

�(%� 4%2-3� �#4%,� �� !.$� �� !2%� 53%$� ).4%2#(!.'%!",9� 4(2/5'(/54� 4()3� -!.5!,�

�.� -/34� ).34!.#%3�� "/,$&!#%� 4%84� 3%4� ).� )4!,)#3� 2%&%23� %)4(%2� 4/� !� &)%,$� /.� !� 3934%-:

-!.!'%2:4%2-).!,� -%.5� /2� /.� !� �� 3#2%%.�� 4/� +%9342/+%3� 4/� "%� -!$%�� /2� 4/

!� 0!24)#5,!2� +%9� /.� 4(%� +%9"/!2$�

�()3� -!.5!,� ).#,5$%3� !.� %6!,5!4)/.� &/2-� &/2� #/--%.43� !.$� 35''%34)/.3� 4/

)-02/6%� 4()3� -!.5!,� !.$� !.� %22!4!� &/2-� &/2� !.9� #/22%#4)/.3�

��

�30%.� � ��54/-!4)#� ��%%#(� �8#(!.'%� �%47/2+�� 2!.#(�� !.$� �!85-� � 6/)#%� 02/#%33).'� -/$5,%3� !.$�#4%,�%4� � .%47/2+).'� 3/&47!2%� !2%� 2%')34%2%$� 42!$%-!2+3� /&� �#4%,� �/--5.)#!4)/.3� �/20/2!4)/.�

2!.#(� �� !.$� �!85-� �� 6/)#%� 02/#%33).'� -/$5,%3�� #4%,� �� 6/)#%� ).&/2-!4)/.� 02/#%33).'0,!4&/2-�� )%22!�� -5,4)0,%� !00,)#!4)/.3� 0,!4&/2-�� !,,� �%4!),� �%#/2$3�� !.$� �� !,,� �%4!),� �%#/2$3�-!.!'%-%.4� 0!#+!'%3�� !.$� �.(!.#%$�� !,,� �2/#%33).'� !.$� �#4%,�/2-3�� !00,)#!4)/.� 0!#+!'%3� !2%42!$%-!2+3� /&� �#4%,� �/--5.)#!4)/.3� �/20/2!4)/.�

�!2"/.� �/09� �� )3� !� 42!$%-!2+� /&� �%2)$)!.� �%#(./,/'9�� .#�

�� )3� !� 2%')34%2%$� 42!$%-!2+� /&� �� /-054%2� �/20/2!4)/.�

$ �� )3� !� 2%')34%2%$� 42!$%-!2+� /&� �3(4/.:�!4%� �/20/2!4)/.�

�!9%3� � )3� !� 2%')34%2%$� 42!$%-!2+� /&� �!9%3� �)#2/#/-054%2� �2/$5#43�� .#�

� �� !.$� �� !2%� 2%')34%2%$ � 42!$%-!2+3� /&� �.4%2.!4)/.!,� 53).%33� �!#().%3� �/20/2!4)/.�

�� )3� !� 2%')34%2%$� 42!$%-!2+� /&� �/&4�,/.%� �)342)"54).'� �/20/2!4)/.�

��:�� )3� ! � 2%')34%2%$� 42!$%-!2+� /&� �)#2/3/&4� �/20/2!4)/.�

�93%� � )3� !� 2%')34%2%$� 42!$%-!2+� /&� �93%� �%#(./,/'9�

CONTENTS

viiEdition ThreeOctel PC/CDR

CONTENTS

ONE: INTRODUCTION

1.1 OVERVIEW 1-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.2 PROCESS CHECKLIST 1-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3 KEY TERMS AND DEFINITIONS 1-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.4 EQUIPMENT CONFIGURATION AND REQUIREMENTS 1-4. . . . . . . . . . . . . . . . .

1.5 OCTEL PC/CDR INTERACTION 1-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.6 CDR BUFFER 1-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.7 COLLECTION FILES 1-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.8 HIGHLIGHTS 1-17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

TWO: DATA COLLECTION PREPARATION

2.1 OVERVIEW 2-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.2 UNDERSTANDING THE CDR BUFFER 2-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3 WARNING OF POTENTIAL CDR DATA LOSS 2-5. . . . . . . . . . . . . . . . . . . . . . . . . .

2.4 DETERMINING PROCESSING TIME AND SIZING THE PC 2-5. . . . . . . . . . . . . .

2.5 CONFIGURING THE VOICE PROCESSOR FOR CDR DATA COLLECTION 2-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.6 HIGHLIGHTS 2-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

THREE: INSTALLATION PROCEDURES

3.1 OVERVIEW 3-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2 VERIFY OCTEL PC/CDR FEATURE 3-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.3 INSTALL OCTEL PC/CDR SOFTWARE INTO PC 3-1. . . . . . . . . . . . . . . . . . . . . . .

3.4 CREATE CDR SYSTEM DATA SUBDIRECTORIES USING MKCDRSYS 3-5. . .

3.5 REMOVE CDR SYSTEM DATA SUBDIRECTORIES 3-8. . . . . . . . . . . . . . . . . . . . .

3.6 UPGRADE OCTEL PC/CDR SOFTWARE 3-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.7 HIGHLIGHTS 3-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section Page

viii Edition Three Octel PC/CDR

FOUR: SOFTWARE ATTRIBUTES

4.1 OVERVIEW 4-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.2 ACCESS THE OCTEL PC/CDR SYSTEM MENU 4-1. . . . . . . . . . . . . . . . . . . . . . . .

4.3 CONFIGURE OCTEL PC/CDR PARAMETERS AND SYSTEM ATTRIBUTES 4-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.4 TEST THE DIRECT CONNECTION BETWEEN THE PC AND THE VOICE PROCESSOR 4-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.5 HIGHLIGHTS 4-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

FIVE: CARBON COPY PLUS PROCEDURES

5.1 OVERVIEW 5-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.2 CONFIGURING CARBON COPY PLUS 5-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.3 CHANGING CARBON COPY PLUS PARAMETERS 5-3. . . . . . . . . . . . . . . . . . . . .

5.4 USING CARBON COPY PLUS 5-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.5 DISABLING CARBON COPY PLUS 5-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.6 HIGHLIGHTS 5-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SIX: PROCESSING METHODS

6.1 OVERVIEW 6-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.2 USING MANUAL PROCESSING 6-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.3 USING AUTOMATIC PROCESSING 6-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.4 USING SCHEDULED AUTOMATIC PROCESSING 6-15. . . . . . . . . . . . . . . . . . . . .

6.5 USING THE SERVICE-LEVEL DOWNLOAD 6-27. . . . . . . . . . . . . . . . . . . . . . . . . . .

6.6 HIGHLIGHTS 6-30. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SEVEN: UTILITIES

7.1 OVERVIEW 7-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.2 FILE UTILITIES OPTIONS 7-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.3 HIGHLIGHTS 7-18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section Page

ixEdition ThreeOctel PC/CDR

EIGHT: DTMF OCTELFORMS

8.1 OVERVIEW 8-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8.2 CHOOSE APPLICATIONS 8-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8.3 DETERMINE BUFFER SIZE 8-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8.4 ESTIMATE CDR BUFFER AND PC DISK STORAGE SPACE 8-2. . . . . . . . . . . . .

8.5 ESTIMATE DOWNLOAD AND PROCESSING TIME 8-4. . . . . . . . . . . . . . . . . . . . .

8.6 COLLECT CDR DATA 8-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8.7 PROCESS DTMF OCTELFORMS WITH OCTEL PC/CDR 8-5. . . . . . . . . . . . . . . .

8.8 SELECT OUTPUT FILES AND OUTPUT FILE FORMATS 8-5. . . . . . . . . . . . . . . .

8.9 PROCESS OUTPUT FILES 8-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8.10 HIGHLIGHTS 8-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

APPENDIXES A-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

GLOSSARY G-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

INDEX I-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section Page

1

INTRODUCTION

1-iiiEdition ThreeOctel PC/CDR

CHAPTER ONECONTENTS

1.1 OVERVIEW 1-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.2 PROCESS CHECKLIST 1-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3 KEY TERMS AND DEFINITIONS 1-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.4 EQUIPMENT CONFIGURATION AND REQUIREMENTS 1-4. . . . . . . . . . . . . . . . .

1.4.1 Physical-Connection Requirements 1-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4.1.1 Shared Port for SMT and PC 1-5. . . . . . . . . . . . . . . . . . . . . . . . . . 1.4.1.2 Separate Ports for SMT and PC 1-5. . . . . . . . . . . . . . . . . . . . . . . 1.4.1.3 Cables and Connectors 1-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.4.2 PC Requirements 1-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.4.3 Software Requirements 1-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.5 OCTEL PC/CDR INTERACTION 1-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.6 CDR BUFFER 1-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.7 COLLECTION FILES 1-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.7.1 Binary Collection Files (BCFs) 1-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.7.2 Processed Collection Files (PCFs) 1-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.7.3 Collated Day Files (CDFs) 1-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.7.4 Pending State Files (PSFs) 1-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.7.5 Log Files 1-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.7.6 Output Files 1-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.7.6.1 Session-Detail Output Files 1-12. . . . . . . . . . . . . . . . . . . . . . . . . . . 1.7.6.2 Unsuccessful-Transfer Output Files 1-13. . . . . . . . . . . . . . . . . . . . 1.7.6.3 Message-Detail Output Files 1-14. . . . . . . . . . . . . . . . . . . . . . . . . . 1.7.6.4 Individual-Port-Statistics Output Files 1-15. . . . . . . . . . . . . . . . . . 1.7.6.5 Forms-Output File 1-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.8 HIGHLIGHTS 1-17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section Page

1-iv Edition Three Octel PC/CDR

FIGURES

Figure 1-1. Call, Event, and Session Relationship 1-4. . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 1-2. Octel PC/CDR Configuration Diagram for Voice-Processing-Module Software Releases 8.32 to 10.2X and Release 1 to 1.4X 1-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 1-3. Octel PC/CDR Configuration Diagram for Voice-Processing Module Software Release 1.5X 1-6. . . . . . . . . . . . . . .

Figure 1-4. Octel PC/Call Detail Record Processing Sequence 1-8. . . . . . . . . . . . . .

Figure 1-5. Example of a Session-Detail Output File 1-13. . . . . . . . . . . . . . . . . . . . . .

Figure 1-6. Example of an Unsuccessful-Transfer Output File 1-14. . . . . . . . . . . . . .

Figure 1-7. Example of a Message-Detail Output File 1-15. . . . . . . . . . . . . . . . . . . . .

Figure 1-8. Example of an Individual-Port-Statistics Output File 1-16. . . . . . . . . . . . .

Figure 1-9. Example of a Forms-Output File 1-17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Page

1

1-1Edition ThreeOctel PC/CDR

INTRODUCTION

1.1 OVERVIEW

The Octel Call Detail Records management package (Octel PC/CDRa) is a datacollection and processing system that provides detailed call-data records about theOctel Communications family of voice-processing products. The Octel Communica-tions family of voice-processing products includes the Branch , Branch XP ,Aspen , Maxum SE , and Maxum voice-processing modules, the OctelXC1000 voice-information-processing platform, and the Sierra multiple-applica-tions platform. In this manual, all references to the Sierra multiple-applicationplatform also apply to the Octel XC1000 voice-information-processing platform.

Octel PC/CDR is an optional software package available on new voice-processorsb,or it can be added to established voice processors after installation. Octel PC/CDRcollects data that is used for extensive call billing, administrative planning, andtroubleshooting. This data is then transferred to a personal computerc (PC) forsorting and data formatting. To run Octel PC/CDR software Release 1.5, voice-processing-moduled software must be at Release 8.32 to 10.2X or Release 1 to1.5X. Sierra software must be at Sierra Release 2.1 or combined releases 1.2X andabove.

Octel PC/CDR data differs from the call-detail record data provided by a privatebranch exchange or central office switch. Octel PC/CDR output data providesdetailed information about calls as they take place in the voice processor. Each timea significant action occurs during a call, the voice processor records the event inthe call-detail-records (CDR ) buffer in the voice processor. Octel PC/CDR data isbased on the series of events occurring from the time a voice-processor port goesoff-hook to receive a call to when the port goes back on-hook, when the call iscomplete. Data is also collected for message waiting and voice-processor eventsunrelated to the status of the ports. CDR data is downloaded to a PC and sortedinto output files that can be viewed and printed through the Octel PC/CDR FileUtilities menu, or the files can be imported into a database application program forfurther manipulation.

Some system managers require Octel PC/CDR output files in addition to thestandard system manager reports available with all voice processors, because CDRoutput files provide more detailed information for measuring and monitoringindividual mailbox usage. Specifically, Octel PC/CDR offers several detailedoutput-data files showing how calls are processed. These files include data showingaccesses to an individual subscriber’s mailbox and messages transmitted between

a The terms Octel PC/CDR and CDR are used interchangeably throughout this manual.b In this manual, the term voice processor refers collectively to the Aspen, Branch, Branch XP, Maxum SE, and

Maxum voice-processing modules; the Octel XC1000 voice-information-processing platform; and the Sierramultiple-application platform.

c For faster processing, a 386 system is recommended, although not required. A PC with high-capacity drivescan be used.

d The term voice-processing module refers to the Branch, Branch XP, Aspen, Maxum SE, and Maxumvoice-processing modules.

INTRODUCTION

1-2 Edition Three Octel PC/CDR

nodes across a network. System managers can also use CDR records to bill usersfor voice-processor resources, provide an audit trail for caller activity and usagepatterns, and record valuable information necessary for future voice-processorplanning and engineering. Octel PC/CDR can also be used for troubleshooting.

Octel PC/CDR data downloading, processing, and storage requirements varygreatly based on voice-processor traffic and applications. To avoid losingdata, monitor buffer-storage space on the voice processor daily until a patternhas been established.

The relationship between Octel PC/CDR and the optional DTMF OctelFormsapplication package is explained in Chapter Eight. Chapter Eight also describesspecial buffer sizing and downloading considerations.

1.2 PROCESS CHECKLIST

This section provides major steps for the installation, configuration, and processingof Octel PC/CDR data. To complete each step, refer to the sections noted inparentheses for detailed instructions.

1. Connect the voice processor to the PC that will contain the Octel PC/CDRsoftware (section 1.4).

2. Become familiar with the CDR buffer in the voice processor (sections 1.6, 2.2,and 2.5.3) and the Octel PC/CDR collection files (section 1.7).

3. Verify that the Octel PC/CDR feature is enabled in the voice processor bychecking system manager menu 13.7 (section 2.5.1).

4. Select call-detail records to be collected by the voice processor (section 2.5.2).

5. Install the Octel PC/CDR software in the PC (section 3.3).

6. Create Octel PC/CDR system data subdirectories using MKCDRSYS (section3.4).

7. Configure Octel PC/CDR parameters and system attributes for each CDRsystem created with the MKCDRSYS utility (section 4.3).

8. Test the direct connection from the PC to the voice processor (also includesSMT emulation instructions) (section 4.4).

9. Install and configure Carbon Copy PLUS software (section 5.2).

10. Choose the downloading method and process the CDR data (Chapter Six).

Manual (section 6.2)

a. Perform manual download.

b. Collate the binary collection files.

c. Generate output files.

Automatic (section 6.3)

a. Select output files to be generated.

b. Select blocks to be downloaded.

c. Perform automatic download (includes output-file generation).

SECTION 1.1 – 1.2

INTRODUCTION


Scheduled automatic (section 6.4)a. Create automatic processing schedules.

b. Start the automatic scheduler timer (includes download and outputfile generation).

11. Print or view the output files (section 7.2.3) and interpret them using the tablesin Appendix A.

12. Back up Octel PC/CDR files (section 7.2.4).

13. Import output files into a database-application program to sort data andgenerate reports (refer to the manual for the software program used).

14. Erase Octel PC/CDR files that are no longer necessary (section 7.2.5).

15. Run Carbon Copy PLUS software when directed by an Octel or distributorservice representative for system maintenance (section 5.4), and disable thesoftware (section 5.5) when finished.

1.3 KEY TERMS AND DEFINITIONS

The following terms are used in this manual.

Block is a storage section within the CDR buffer. Blocks are filled with eventrecords, and then the events within the blocks are downloaded to a PC forprocessing. A block can hold approximately 80 to 140 event records.

Buffer is the storage space set aside on the voice processor to collect OctelPC/CDR data.

Call is a series of events beginning when the voice-processor port goesoff-hook to receive an incoming call or to initiate an outgoing call. A call endswhen the call is completed and the port goes on-hook.

CDR system refers to the systemname chosen to designate a particularvoice processor that downloads CDR data to the CDR PC (refer to section3.4).

Collation is the process, or the result, of arranging CDR data in order.

Events are the occurrences and records of everything that happens to a callfrom when the port goes off-hook through when it goes back on-hook. Theseevent records include entering a mailbox, conducting a password test, goingoff-hook or on-hook for a specific port, beginning an outcall, or transferring toanother mailbox or telephone number.

File name is the name given to a particular file to be used by DOS. Thenaming format allows as many as eight alphanumeric characters, plus threealphanumeric characters for an extension. The first eight characters areseparated from the extension with a period; combined, they form the filename. File names in this manual are shown in upper- and lower-casecharacters. Upper-case characters indicate characters that are nonvariable andrequired. Lower-case characters are variables assigned to indicate appropriateinfor- mation, as defined for the particular file name. Refer to section 1.7 forthe file-name conventions used in Octel PC/CDR.

Output files are the categories into which Octel PC/CDR sorts and files thevoice-processor CDR data after it has been downloaded to a PC and collated.

SECTION 1.2 – 1.3

INTRODUCTION


Session begins when a caller enters a mailbox and ends when a caller exitsthe same mailbox. Because a single call can pass through multiple mailboxes(for example, in Enhanced Call Processing (ECP) applications or when acaller uses the restart command within a mailbox), a call normally consists ofone or more sessions. Figure 1-1 shows the relationship between a call,event, and session.

EVENT

EVENT EVENT

SESSION

SESSION SESSION

CALL

Figure 1-1. Call, Event, and Session Relationship.

System attributes are the selected parameters that apply to each voiceprocessor from which the PC downloads CDR data. In the Octel PC/CDRpackage, these attributes include necessary communications settings for theconnection between the PC and each voice processor. These attributes alsodefine the output files created with the automatic-processing methods and theassociated file format.

Systemname is the name chosen to designate a particular voice processor. Itis used by the MKCDRSYS command (on the PC) to create the directory thatstores (1) the data from that particular voice processor and (2) directories onthe PC hard-disk drive. Type the command cdrhelp from the DOS prompt tolist all valid CDR systemnames.

VPMOD is used in some of the Octel PC/CDR menus. It represents the voiceprocessor.

1.4 EQUIPMENT CONFIGURATION AND REQUIREMENTS

Octel voice processors are equipped with a local system-manager terminal (SMT)for normal system-management functions. This SMT is also used by field serviceengineers to perform voice-processor diagnostic tests and, therefore, must beavailable on site. Additionally, a separate PC is required to download and processthe CDR data collected by the voice-processor’s CDR buffer. Follow the instructionsin sections 1.4.1 through 1.4.3 to configure the equipment and software required forOctel PC/CDR to work properly.

SECTION 1.3 – 1.4

INTRODUCTION


1.4.1 Physical-Connection Requirements

Depending on the voice-processor software release in use, the CDR PC couldeither share a port on the voice processor with the SMT or it could use a port of itsown. These two connections are described in sections 1.4.1.1 and 1.4.1.2. Section1.4.1.3 discusses the required cables and connectors.

Only trained technicians should open voice-processor cabinets.Cabinets contain high voltage and currents.

Caution!

1.4.1.1 Shared Port for SMT and PC. The CDR PC shares the same scanner-board port asthe SMT on voice-processing modules with software Releases 8.32 to 10.2X andReleases 1 to 1.4X. The CDR PC shares the same distribution-board port as the SMTon Sierras with Sierra software Release 2.10 and combined Release 1.2X. When PCaccess to the voice processor is required, the cable between the SMT and the voiceprocessor must be disconnected from the SMT and then connected to the PC. OctelPC/CDR includes an SMT emulator that enables most system-management functionsto be performed from the CDR PC. This feature is described in section 4.4.

A manual or scanning (pollable) data switch can be used, so that the SMT and PC can share the same port. This configuration is illustrated in Figure 1-2. Once the dataswitch is connected to the voice processor, both the SMT and the PC can beconnected to the input ports on the data switch at the same time. The setting on amanual data switch must then be changed physically to provide either SMT or PCaccess.

Sierras at any software level that have MTA capability can dedicate a port on theMTA to the CDR application PC.

1.4.1.2 Separate Ports for SMT and PC. With voice-processor-software Release 1.5X,both the SMT and the CDR PC can be connected to the voice processor andoperated at the same time. The ports used for the SMT and CDR PC must beconfigured in SMT menu 6. Refer to the System Manager Manual for informationabout configuring ports on scanner and distribution boards.

Voice-Processing Module. Connect the SMT cable to the third physical port(channel 4) on the scanner board, and connect an RJ-11 cable from the first(channel 2) or second (channel 1) physical port to the CDR PC. This configurationis illustrated in Figure 1-3.

Sierra and Octel XC1000. Connect the SMT to connector J50 (channel 4) on thedistribution board and connect the CDR PC to connector J43, J44, or J46 (channels2, 1, or 3 respectively). (Availability of channels 1 through 3 is dependent upon thenumber of integration links used. If three integration links are used, a channel is notavailable for simultaneous SMT and CDR operation.)

1.4.1.3 Cables and Connectors. The Octel PC/CDR package includes the cables andconnectors needed to connect the PC to the voice processor. Both 9-pin and 25-pinserial port connectors are provided. If a data switch or modem connection is used,other cables and connectors, provided by the customer, could be required.

SECTION 1.4

INTRODUCTION


A

B

MODEM MODEM

MAINTENANCEMODEM

PRINTER

SYSTEM MANAGERTERMINAL

PERSONALCOMPUTER/CDR

SMT CABLE (RJ-11)

DATA SWITCH(OPTIONAL)

9- OR 25-PINADAPTOR

9- OR 25-PINPC/AT SERIAL PORT

OUTPUT (MALE)MODEMS (IFOVER 50 FEET)

VOICE-PROCESSING MODULE

SCANNERBOARDa

a This is a distribution board on a Sierra.

Figure 1-2. Octel PC/CDR Configuration Diagram for Voice-Processing-Module Software Releases 8.32 to 10.2X and Release 1 to 1.4X.

SCANNERBOARDa

a This is a distribution board on a Sierra.

MODEM MODEM

MAINTENANCEMODEM

PRINTER

SYSTEM MANAGERTERMINAL

PERSONALCOMPUTER/CDR

SMT CABLE (RJ-11)

9- OR 25-PINADAPTOR

9- OR 25-PINPC/AT SERIAL PORT

OUTPUT (MALE)MODEMS (IFOVER 50 FEET)

VOICE-PROCESSING MODULE

Figure 1-3. Octel PC/CDR Configuration Diagram for Voice-Processing Module Software Release 1.5X.

SECTION 1.4

INTRODUCTION


1.4.2 PC Requirements

The Octel PC/CDR software package runs on an IBM-compatible PC. However,given the differences between computers and operating systems, successfuloperation on all IBM-compatible PCs cannot be ensured in all cases.

The PC must include the following:

An IBM PCa, IBM-compatible PCa, or an IBM PS/2 , Model 50 or higher,equipped with the following:

640K RAM with no other memory-resident programs loaded.

1.2-MB, 51/4-inch or 1.44-MB, 31/2-inch high-capacity, diskette drive.

Internal hard disk (40 MB minimum); capacity requirement varies,depending on the voice processor’s monthly call volume and severalother factors. Typically, 40 to 95 MB is required for every 10,000 callsprocessed and stored. Also allow 1.8 MB of storage space for the OctelPC/CDR software.

RS-232 serial port (the 9- or 25-pin male output connection to the voiceprocessor).

Parallel port (for connection to the optional printer).

Real-time clock (internal-battery backup).

Modem: 9600 or 1200 baud for maintenance communications (anadditional serial port could be required for this modem).

An additional modem, with manual-configuration switches, is required if thedistance between the voice processor and the PC is more than 50 feet.Most Hayes and Hayes-compatible modems can be used for communi-cation between the PC and the voice processor.

Customers are responsible for modem communication and compati-bility. Octel Communications does not endorse specific brands nordoes it provide service for peripheral equipment unless that equip-ment was purchased through Octel Communications. Installation ofmodem equipment is the responsibility of the customer.

IBM DOS or MS-DOS , version 3.2, 3.3, 4.01, or 5.0. For large-data-storagerequirements, the specific version of DOS must be capable of addressinglarge-partition sizes, above 35 megabytes; for example, COMPAQ MS-DOSVersion 3.3.

Optional hardware, as follows:

132-column or 80-column printer

Asynchronous serial (RS-232) data switch

Streamer-tape-backup unit

1.4.3 Software Requirements

The Octel PC/CDR package contains the following software:

Octel PC/CDR (CDR processing and data communication software)

Carbon Copy PLUS (remote maintenance communication software)

MIRROR II (data communication software)

a For faster processing, a 386 system is recommended, although not required. A PC can be used if it has high-capacity drives.

SECTION 1.4

INTRODUCTION


All three software programs are installed when the Octel PC/CDR install commandis executed.

Voice-processing modules require software Release 8.32 to 10.2X or Release 1 to1.5X. Sierra software must be at Sierra Release 2.1 or combined releases 1.2X andabove.

Optional database or application software (dBASE III or ASCII based), provided bythe customer, might be desired for sorting data and report generation.

1.5 OCTEL PC/CDR INTERACTION

The Octel PC/CDR package consists of two major components: the data-collectioncomponent in the voice processor (the CDR buffer) and the data-retrieval andoutput-file-generation component in the PC. Figure 1-4 and the following steps showhow these components are related:

Binary Collection

Files (BCF)

Session- Detail Files

(SDO)

Message-Detail Files

(MDO)

Individual-Port-Statistics Files

(PSO)

Unsuccessful- Transfer

Files (UTO)

Octel PC/CDR Files and Programs

Application Program Application Program Application Program Application Program

Forms-Output File (FDO)

Application Program

Collated Day Files

(CDF)

CDRBUFFER

VOICE PROCESSOR

Raw Data

Downloadedto PC

Collate

1

2

3

4

5

6 6 6 6 6

Figure 1-4. Octel PC/Call Detail Record Processing Sequence.

SECTION 1.4 – 1.5

INTRODUCTION


1. As calls are made through the voice processor and voice mail is used, calland mailbox event data are recorded in the CDR buffer located on the drivesin the voice-processor.

2. Periodically, the system manager downloads CDR event data from the CDRbuffer to a hard disk on a PC.

3. The raw event data downloaded to the PC is formed into binary collection files(BCFs).

4. The Octel PC/CDR software on the PC collates the BCFs to create thecollated day files (CDFs).

5. The CDFs are processed into the output files selected by the systemmanager.

6. If desired, output files are imported into application programs for reportgeneration.

1.6 CDR BUFFER

As calls occur on the voice processor, CDR event records are recorded in the CDRbuffer in the voice-processor drives. The buffer can be sized for either 2020 or 7020blocks. The Aspen, Branch, and Branch XP voice-processing modules are usuallysized at 2020 blocks, and the Maxum SE, Maxum, Octel XC1000, and Sierra aresized at 7020 blocks.

The CDR buffer and event records are duplicated on each system drive. Thebuffer-storage space reduces message space available by approximately 25 minuteson each disk when sized for 2020 blocks on an Aspen, Branch, and Branch XP.Because the Maxum SE, Maxum, and Sierra system drives are not used to storemessages, they have enough free space to be sized for 7020 blocks (equivalent to85 minutes of message storage). If an Aspen, Branch, or Branch XP is sized for7020 blocks, make sure to consider the additional space requirements. The CDRbuffer is described in detail in section 2.2.

1.7 COLLECTION FILES

This section defines Octel PC/CDR collection-file names, describes the informationcaptured by each collection file, and provides samples of the printed output files.Each collection file name is based on a unique naming convention. Each CDRsystem subdirectory created with the MKCDRSYS command has its own set ofsubdirectories for collection files. Refer to section 3.4 for detailed information aboutCDR system subdirectories.

1.7.1 Binary Collection Files (BCFs)

When blocks are downloaded to the PC from the CDR buffer, they are first filed onthe PC hard disk in the BCF subdirectory for the voice processor (CDR system)from which they were downloaded. BCFs are then collated into collated day files(CDFs). Once the BCFs are collated, they can be automatically deleted from thehard disk to conserve space. If not deleted, the processed BCFs are renamed witha file extension of PCF (processed collection files) after they are collated. BCFs canbe viewed through the Service Utilities menu (section 7.2.7.3), or a section of aBCF can be isolated and copied for a closer review (section 7.2.7.2).

SECTION 1.5 – 1.7

INTRODUCTION


Each BCF file 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

whereA represents a file created from one of the first 26 downloads that occurred on the

same day. Files created from the 27th through 52nd downloads on the sameday are named Byymmddi.BCF; files created from the 53rd through 68thdownloads are named Cyymmddi.BCF, and so forth.

yymmdd represents the year (yy), month (mm), and day (dd) the downloadoccurred, based on the PC clock.

i represents a particular file if several files are downloaded on the same date. The iequals a sequential alphabetic character. For example, A920726A.BCF is thefirst file downloaded on July 26, 1992. Every other file downloaded on that datewould cause the last letter before the period (represented by i) to change.A920726B.BCF is the second file downloaded on July 26, 1992. After 26 fileshave been downloaded, the initial letter (A) in the file name changes, forexample, to B920726A.BCF.

The maximum number of BCFs that can be downloaded per day is 676 (26 files x26 letters).

1.7.2 Processed Collection Files (PCFs)

When a BCF is collated into a CDF, the BCF is renamed with the extension of PCFif the BCF was not automatically deleted (refer to section 4.3.2). If data needs to becollated a second time, a PCF can be renamed with the .BCF extension (using theDOS rename command) and the BCF can then be collated again. To conserve diskspace, PCF files should eventually be deleted or off-loaded to a diskette or tape forstorage.

PCF names are based on the same naming convention as BCFs, except that thefile-name extension is PCF.

1.7.3 Collated Day Files (CDFs)

BCFs are collated by sorting events from every call on every port, chronologicallyby completion time, into CDFs. This process creates or appends already existingCDFs with the call events contained in the BCF file. One CDF is created for everydate that call events exist in the BCF. CDFs are manually requested unlessautomatic downloading is used or scheduled (refer to Chapter Six for informationabout data-processing methods).

CDFs are named with the following convention:

CDyymmdd.CDF

whereCD represents a collated day file.

yymmdd represents year (yy), month (mm), and day (dd) that the call started,based on the voice-processor clock.

CDF also represents a collated day file.

SECTION 1.7

INTRODUCTION


The CDFs are stored in the CDF subdirectory on the hard disk. Unprocessed CDFsare used by Octel and distributor service representatives for troubleshooting. Forthis purpose, CDFs are sorted, viewed, and printed through the Service Utilitiesmenu (section 7.2.7.1). Appendix B describes the CDF event records.

1.7.4 Pending State Files (PSFs)

A PSF named COLLATE.PSF is created every time BCF files are collated. PSFshold all event records for calls that are in progress when a download occurs. Whenthe next collation occurs, this file is copied to a file named AyymmddA.PSF. Thecurrent COLLATE.PSF file is then merged with the downloaded data and theprevious calls in progress are matched with their completing entries. At the end ofthis download, a new COLLATE.PSF file is generated containing the call records inprogress at the time the most recent download began.

A PSF is created every time BCF files are collated. It is named by the date onwhich the download occurred. Dated PSFs are stored in the BCF subdirectory andthe COLLATE.PSF file is stored in the SYS subdirectory on the PC hard disk. DatedPSF names are based on the same naming convention as BCFs, except that thefile-name extension is PSF.

1.7.5 Log Files

A log file is created for each day that any Octel PC/CDR process (such as collateor download) is executed. The results of all downloads, system manager sign-onactivity, and any problems are stored as log files. These files are stored in thesystem files (SYS) subdirectory on the PC hard disk for the CDR system.

Log files are named by the date on which processing occurred. Log files are namedwith the following convention:

Lyymmdd.LOG

whereL represents a log file.

yymmdd represents the year (yy), month (mm), and day (dd) processing occurredbased on the PC clock date.

LOG also represents a log file.

If more than one download occurs on the same day, the first log file created for thatday is appended to the new log. There can be only one log file per day, per CDRsystem. Log files can be viewed or printed through the Octel PC/CDR File UtilitiesMenu (section 7.2.3). Log files can also be examined to show processing results fora particular day, by using the DOS commands type or print (executed from the CDRsystem SYS subdirectory).

1.7.6 Output Files

Event records in the CDFs are processed (compressed) into output files based onthe records collected in the CDR buffer (selected in SMT menu 16.1.4, section2.5.2) and the output files selected by the system manager (refer to section 6.2.3).The output-file options are as follows:

SECTION 1.7

INTRODUCTION


Session-detail output (SDO) files

Unsuccessful-transfer output (UTO) files

Message-detail output (MDO) files

Individual-port-statistics output (PSO) files

Forms-output (FDO) file (optional)

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-statistic output files can be created and importedinto a dBASE III billing application program, or the system manager could use theoutput files for report generation.

Output files can be viewed or printed through the Octel PC/CDR File Utilities Menu(section 7.2.3). Appendix A gives the file structure and description of output-filefields and records.

1.7.6.1 Session-Detail Output Files. One SDO file is created for each day that calls arefound in the source CDF. SDO files contain event records of each time a mailbox isaccessed, either in voice-messaging or telephone-answering mode. The eventrecords also indicate when callers are logged into the voice processor but are not ina mailbox.

Outcall events are included in the SDO files. An outcall session begins when thevoice processor generates an outcall to a subscriber’s telephone. The SDO fileincludes the amount of time spent in the session.

SDO files also include details of pager and network outcalls. Pager outcalls areidentified separately from other subscriber outcalls and contain the pager-sequencenumbers used. Separate network-outcall records are provided for every outgoing orincoming message, the associated copies, and messages sent to or received frommailboxes on other nodes across the network.

SDO files include the following:

Voice-processor serial number

Port-identification number

Date and time the mailbox was accessed

Time spent in the mailbox (including the length of the greeting and themessage)

Mailbox number

Telephone number of incoming caller (if available)

Call origination (direct, incoming, forwarded)

Password type used (if any)

Termination conditions (hung up, transferred)

Outgoing telephone number for outcalls and network callsa

Number of unsuccessful-transfer occurrences

Total messages sent and deleted during session

a When the outcall number is longer than the number of digits allowed in the CALLEE field, the excessiveleading digits are not recorded.

________________

SECTION 1.7

INTRODUCTION


SDO files are created in either a dBASE III or an ASCII format. The database orapplications program used to process this data must be set with the proper fieldsand field lengths. Refer to Appendix A for field-name and length requirements.

SDO files are named with the following convention:

Byymmdd.xxx

whereB represents a session-detail-output file.

yymmdd represents year (yy), month (mm), and day (dd) the file was created,based on the voice-processor clock.

xxx represents the format of the file, with DBF indicating the dBASE III format andASC indicating various ASCII formats.

The SDO files are created and stored in the SDO subdirectory.

There are two file-format levels available for SDO files. The only difference betweenlevel one and level two is that some of the fields in level two allow more digits tobe entered than some of the fields in level one. Refer to section 4.3.9 for instruc-tions about how to select the file-format level, and refer to Appendix A to identifythe affected fields.

SDO files can be displayed and printed through the Octel PC/CDR File Utilitiesmenu (refer to section 7.2.3 for more detailed information). Figure 1-5 is anexample of a printed SDO file. Refer to Appendix A for field-name definitions, andrefer to section 6.2.3.1 for additional information about SDO files.

SyId Prt Date Time Dur Mailbox Caller Callee CT AT TC Destination BX Msent Mdel

0627 01C 920415 060143 17 4117 4117 4 5 0 0 0 00627 01D 920415 060131 88 7402 7402 1 0 0 0 0 10627 01C 920415 061036 13 9002 1 5 1 9010 0 0 00627 01C 920415 061049 7 9010 1 5 1 3217 0 0 00627 01C 920415 061056 62 3217 1 5 0 0 1 00627 01B 920415 061202 14 6114 6114 4 5 0 0 0 0

Figure 1-5. Example of a Session-Detail Output File.

1.7.6.2 Unsuccessful-Transfer Output Files. UTO files contain records of each attemptedand monitored 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 voice processor

SECTION 1.7

INTRODUCTION


UTO files include the following data:

Voice-processor serial number (last four digits)

Port identification used

Date and time of occurrence

Mailbox number attempting the transfer

Reason code for unsuccessful transfer

Attempted telephone number

One UTO file is created for each day that calls are found in the source CDF. Eachtime UTO files are generated, a new UTO file is created or an existing file for thatsame date is appended.

UTO files are created in either a dBASE III or an ASCII format. The database orapplications program used to process this data must be set with the proper fieldsand field lengths. Refer to Appendix A for field-name and length requirements.

UTO files are named with the following convention:

Xyymmdd.xxx

whereX represents an unsuccessful-transfer output file.

yymmdd represents year (yy), month (mm), and day (dd) that the events occurred,based on the voice-processor clock.


UTO files are created and stored in the UTO subdirectory.

UTO files can be displayed and printed through the Octel PC/CDR File Utilitiesmenu (refer to section 7.2.3 for more detailed information). Figure 1-6 is anexample of a printed UTO file. Refer to Appendix A for field-name definitions andrefer to section 6.2.3.2 for additional information about UTO files.

SyId Prt Date Time Mailbox RC TnTried

5081 01A 920418 201640 6717 4 63655081 01D 920418 220015 6948 2 63915081 02C 920419 010533 6996 5 25235081 01A 920419 011456 6717 3 25575081 02A 920419 031323 6948 4 6365

Figure 1-6. Example of an Unsuccessful-Transfer Output File.

1.7.6.3 Message-Detail Output Files. MDO files contain data records of every messagethat is sent or deleted in the voice processor. In particular, the data records containthe following:

Voice-processor serial number

Port number

SECTION 1.7

INTRODUCTION


Date and time when a message was sent or deleted

Mailbox number

Message length

Destination or origination mailbox

One MDO file is created for each day that calls are found in the source CDF. Eachtime MDO files are generated, a new MDO file is created or an existing file for thesame date is appended.

MDO files are created in either a dBASE III or an ASCII or format. The database orapplications program used to process this data must be set with the proper fieldsand field lengths. Refer to Appendix A for field-name and length requirements.

MDO files are named using with following convention:

Myymmdd.xxx

whereM represents a message-detail output file.

yymmdd represents the year (yy), month (mm), and day (dd) that the eventsoccurred, based on the voice-processor clock.


MDO files are created and stored in the MDO subdirectory.

There are two file-format levels available for MDO files. The only difference betweenlevel one and level two is that some of the fields in level two allow more digits tobe entered than some of the fields in level one. Refer to section 4.3.9 for instruc-tions about how to select the file-format level and refer to Appendix A to identify theaffected fields.

MDO files can be displayed and printed through the Octel PC/CDR File Utilitiesmenu (refer to section 7.2.3 for more detailed information). Figure 1-7 is anexample of a printed MDO file. Refer to Appendix A for field-name definitions andrefer to section 6.2.3.3 for additional information about MDO files.

SyId Prt Date Time Mailbox Len Ac SR Atr OthNod OthBox

0627 01B 920416 064904 4125 13 10 0 0 67170627 01C 920416 065053 7329 57 0 0 00627 01D 920416 065132 4248 20 10 1 0 54540627 01D 920416 065416 5325 16 10 0 0 53580627 01D 920416 065526 4248 31 10 1 0 22220627 01D 920416 065651 4313 18 0 0 0

Figure 1-7. Example of a Message-Detail Output File.

1.7.6.4 Individual-Port-Statistics Output Files. PSO files contain the total time each portis in use during every 15-minute period throughout the day and the number of callsstarted within each 15-minute period.

SECTION 1.7

INTRODUCTION


One PSO file is created for each day that calls are found in the source CDF. Eachtime PSO files are generated, a new PSO file is created or an existing file for thatsame date is appended.

PSO files are created in either a dBASE III or an ASCII format. The database orapplications program used to process this data must be set with the proper fieldsand field lengths. Refer to Appendix A for field-name and length requirements.

PSO files are named using with the following convention:

Pyymmdd.xxx or PByymmdd.xxx

whereP represents a PSO file with statistics about ports 1 through 72 (ports 1A through

18D for voice-processing modules and ports 1A through 6L for the OctelXC1000 and Sierra).

PB represents a PSO file with statistics about ports 73 through 144 (7A through12L) . This file is only created when the dBASE III format is chosen for the OctelXC1000 and Sierra platforms. (When the PSO file is created in the ASCIIformat for the Octel XC1000 and Sierra, only one file is created, containing all144 ports of data.).

yymmdd represents year (yy), month (mm), and day (dd) that the events occurred,based on the voice-processor clock.


PSO files are created and stored in the PSO subdirectory.

Display and print PSO files through the Octel PC/CDR File Utilities menu (refer tosection 7.2.3 for more detailed information). Figure 1-8 is an example of a printedPSO file. Refer to Appendix A for field-name definitions and refer to section 6.2.3.4for additional information about PSO files.

T SyId Date HH MM 01A 01B 01C 01D 02A 02B 02C 02D 03A 03B 03C 03D . . . 18D

N 2420 920416 00 00 1 0 0 0 0 0 0 0 0 0 0 0 . . . 0T 2420 920416 00 00 62 0 0 0 0 0 0 0 0 0 0 0 . . . 0N 2420 920416 00 00 0 0 0 0 0 0 0 0 0 0 0 0 . . . 0T 2420 920416 00 00 0 0 0 0 0 0 0 0 0 0 0 0 . . . 0N 2420 920416 00 00 2 0 0 1 0 0 0 0 0 0 0 0 . . . 0T 2420 920416 00 00 144 0 0 15 0 0 0 0 0 0 0 0 . . . 0

Figure 1-8. Example of an Individual-Port-Statistics Output File.

1.7.6.5 Forms-Output File. FDO files contains DTMF data that is based on calls intoDTMF Forms mailboxes. (DTMF OctelForms is an optional application package.)This file includes records of question numbers and callers’ responses. ChapterEight explains the relationship between Octel PC/CDR and the optional DTMFOctelForms application package.

SECTION 1.7

INTRODUCTION


The FDO file is not named according to date like the BCFs and CDFs. There isonly one FDO. The existing FDO file is appended each time data is processed. If anew file is to be created each time DTMF OctelForms is processed, the existingFORMS.ASC or FORMS.DBF file should be renamed, copied onto a floppy disk, orerased. The file increases considerably in size if it is left alone and continuallyappended. File management is the responsibility of the system manager.

The output-file-generation process results in the creation of the DTMF OctelFormsdatabase file. The file structure is dependent on the format selection specified in theoutput-file format-type field (refer to section 4.3.6). The file is named FORMS.DBFfor dBASE III format files or FORMS.ASC for ASCII format files. If a file with thisname already exists, the file is appended; otherwise, it is created.

The FDO file can be in either a dBASE III or an ASCII format. The database orapplications program used to process this data must be set with the proper fieldsand field lengths. Refer to Appendix A for field-name and field-length requirements.

After processing, the FDO file is stored in the FDO subdirectory for the particularCDR system on the PC hard disk. Each FDO subdirectory can have only oneFORMS file at a time. When a new FORMS file is generated, it appends to the oldFORMS file. If the old FORMS file was deleted, a new one is created.

Display and print FDO files through the Octel PC/CDR File Utilities menu (refer tosection 7.2.3 for more detailed information). Figure 1-9 is an example of a printedFDO file. Refer to Appendix A for field-name definitions and refer to section 6.2.3.5for additional information about FDO files.

Prt Date Time Seq Mailbox Ques Answer

01A 920409 125400 1 3500 0 636501A 920409 125400 1 3500 10 9453901A 920409 125400 1 3500 20 51001A 920409 130542 1 3500 0 671701A 920409 130542 1 3500 10 9512701A 920409 130542 1 3500 20 408

Figure 1-9. Example of a Forms-Output File.

1.8 HIGHLIGHTS

Octel PC/CDR data is collected for call billing, administrative planning, andtroubleshooting purposes.

Octel PC/CDR data is based on the series of events occurring from the timethe voice processor port goes off-hook to receive a call to when the port goesback on-hook after the call is completed and for message-waiting andvoice-processor events not related to port status.

Event records are recorded into the CDR buffer in the voice-processor drive.

When Octel PC/CDR data is downloaded to the PC, the data is filed in theBCF subdirectory on the hard disk.

Collated BCFs are organized into CDFs.

CDFs can be compressed into the following output files: session detail,unsuccessful transfer, message detail, individual port statistics, and forms.

SECTION 1.7 – 1.8

2

DATA COLLECTIONPREPARATION


CHAPTER TWOCONTENTS

2.1 OVERVIEW 2-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.2 UNDERSTANDING THE CDR BUFFER 2-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.2.1 Size the Buffer 2-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.2.2 Record and Retrieve Call Events 2-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.3 WARNING OF POTENTIAL CDR DATA LOSS 2-5. . . . . . . . . . . . . . . . . . . . . . . . . .

2.4 DETERMINING PROCESSING TIME AND SIZING THE PC 2-5. . . . . . . . . . . . . .

2.5 CONFIGURING THE VOICE PROCESSOR FOR CDR DATA COLLECTION 2-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.5.1 Confirm Software Feature Enabled 2-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.5.2 Select Call Detail Records To Be Collected 2-9. . . . . . . . . . . . . . . . . . . . . .

2.5.3 Monitor Available CDR Buffer Storage Space 2-11. . . . . . . . . . . . . . . . . . . .

2.5.4 Use Retrieve Call Detail Records Option for Download by Service Engineer 2-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.5.5 Clear Call Detail Recording Lost Data Counter 2-12. . . . . . . . . . . . . . . . . .

2.6 HIGHLIGHTS 2-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section Page


TABLES

Table 2-1. Example of CDR Buffer Capacity, In Days, for a Voice Processor With Light Voice-Mail Usage and Few Special Applications 2-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 2-2. Example of Processing Time and PC Disk-Space Requirements for a Voice Processor With Light Voice-Mail Usage 2-6. . . . . . . . . . . . . . .

Table 2-3. Record Groups Required for Octel PC/CDR Output Files 2-10. . . . . . . . .

FIGURES

Figure 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. Menu 13.7, Display of Software Features Installed 2-8. . . . . . . . . . . . .

Figure 2-4. Menu 16, Database Access 2-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2-5. Menu 16.1, Manage Call Detail Recording 2-9. . . . . . . . . . . . . . . . . . . . . .

Figure 2-6. Menu 16.1.4, Call Detail Records Collected 2-9. . . . . . . . . . . . . . . . . . . .

Figure 2-7. Menu 16.1.1, Call Detail Recording Status 2-11. . . . . . . . . . . . . . . . . . . . .

Figure 2-8. Clear Call Detail Recording Lost Data Counter Screen 2-12. . . . . . . . .

Page

2


DATA COLLECTION PREPARATION

2.1 OVERVIEW

The voice processor and Octel PC/CDR software components interact; the voiceprocessor collects and downloads the CDR data that the PC receives and collates.This chapter explains how to prepare the CDR buffer, the voice processor, and thePC to collect and process CDR data.

2.2 UNDERSTANDING THE CDR BUFFER

As calls occur on the voice processor, CDR event records are recorded in the CDRbuffer on the voice-processor drives. Buffer space is reserved (sized) for OctelPC/CDR through the voice processor’s system utilities. This space is reserved whenthe voice processor is installed or when an existing voice processor adds the OctelPC/CDR software. If Octel PC/CDR is added to a voice processor, existing data andfiles on the voice processor are not affected. However, the voice processor’s drivesmust first have enough space available for the CDR buffer.

2.2.1 Size the Buffer

The CDR buffer is sized to either 2020 or 7020 blocks when the voice processor isinstalled or when the Octel PC/CDR software is installed by an Octel or distributorservice representative. The CDR buffer is typically sized at 2020 blocks on anAspen, Branch, and Branch XP and 7020 blocks on a Maxum SE, Maxum, OctelXC1000, and Sierra. Each CDR block is 2048 bytes; therefore, a buffer of 2020blocks uses approximately 4 megabytes (MB) of voice processor system-drivestorage space, and a buffer of 7020 bytes uses approximately 14 MB. Currently,this buffer-storage space cannot be reclaimed if Octel PC/CDR is disabled on voiceprocessors at software Release 10.43 and 1.1X through 1.5X. Contact the localOctel or distributor support office for assistance for voice processors at any othersoftware level if the buffer size needs to be reduced. View system-manager terminal(SMT) menu 16.1.1 to determine the voice processor’s buffer size.

On an Aspen, Branch, and Branch XP, system information is stored on the firsttwo drives (drives 0 and 1). Octel PC/CDR requires a portion of this system-storage space for the CDR buffer, thereby reducing available message space onthe system drives. The Aspen, Branch, and Branch XPs with voice-digitizationrates of 25,000 samples per second and CDR buffers sized at 2020 blocks requireapproximately 50 minutes of storage space (25 minutes on each drive). If anAspen, Branch, or Branch XP is sized for 7020 blocks, 85 minutes of storagespace are used on each system drive, leaving little space for messages, unlesshigh-capacity drives are in use.

When the CDR buffer is configured at 7020 blocks on a Maxum SE, Maxum, OctelXC1000, or Sierra, approximately 85 minutes of storage space is used on eachsystem drive. Because these system drives are not used for messages, the storagerequirements do not affect their message-storage space.



Voice-processor usage and applications (such as ECP mailboxes and voice mail)affect buffer capacity and the number of blocks filled per day. Table 2-1 shows thebuffer capacity, in days, for a voice processor with light voice-mail usage and fewspecial applications. A voice processor with many applications and heavy voice-mailusage fills the buffer faster than in the example shown in Table 2-1. When the OctelPC/CDR software is first installed, monitor the CDR buffer daily to establish apattern as to how quickly the buffer fills, then perform downloads based on thispattern.

Table 2-1. Example of CDR Buffer Capacity, In Days,for a Voice Processor With Light Voice-Mail Usage

and Few Special Applications.

2,500 110 18 655,000 215 9 327,500 320 6 21

10,000 430 4 1615,000 640 3 1020,000 855 2 825,000 1,070 1 6

Average-Calls per

Day

AverageCDR Blocks

Filledper Day

Buffer Capacity,Days

2020-BlockBuffer

7020-BlockBuffer

Instructions about the use of this table and a description of the columns are asfollows:

The Average Calls per Day column indicates the estimated number of callsprocessed each day by the voice processor. These calls include incomingcalls, outcalls, network calls, and message-waiting notification calls.

The Average CDR Blocks Filled per Day column indicates the averagenumber of CDR blocks filled each day, based on the daily call volume(Average Calls per Day column) and an average of 88 bytes per call. Forexample,

AverageBytes

Per Call

AverageCalls

Per Day

Bytes Per Day

Bytes Per BlockBlocks Per Day

88 10,000880,000

2048430

x = =

x = =

The Buffer Capacity, Days columns indicate the number of days worth ofbuffer storage available between downloadings, based on buffer size. Thesevalues estimate the maximum number of days that CDR event data can beaccumulated in the CDR buffer before the buffer is filled and event data isoverwritten. For example,

SECTION 2.2



2020-Block Buffer430 Blocks

Per Day

2020430

= 4.7 days or=

7020-Block Buffer430 Blocks

Per Day

7020430

= 16.3 days=

Voice processors with a low-to-medium call volume and heavy voice-mailusage fill the buffer faster than shown in Table 2-1. For example,

A voice processor with 7000 to 8000 calls per day and heavyvoice-mail usage could fill a 7020 block buffer in just 3 days.

Download the CDR buffer to the PC when it is between 30% and 50% full.Monitor the available buffer-storage space frequently through SMT menu16.1.1. Frequent downloadings ensure that blocks are not overwritten beforethey are downloaded. Also, smaller data files have a shorter downloading andprocessing time.

The following example shows how to determine the number of days betweendownloadings for a voice processor with light voice-mail usage and few specialapplications:

Refer to Table 2-1 and locate the number in the Average CDR BlocksFilled per Day column that corresponds to the calls processed eachday by the voice processor. The corresponding number in the appro-priate Buffer Capacity, Days column (2020 or 7020 blocks) determinesthe number of days of buffer storage available on the voice processor.For example, 7500 calls per day equals 320 CDR blocks filled per day,which equals 21 days of storage space available in a 7020-block bufferbefore blocks are overwritten.

The CDR buffer will be filled in 21 days; therefore, CDR data should bedownloaded at least every 7 to 10 days (when the buffer is between30% and 50% full).

2.2.2 Record and Retrieve Call Events

When the voice processor first begins recording Octel PC/CDR events, the eventsare recorded in block 0. Depending on the event types, a block holds approximately80 to 140 event records or 2 kilobytes of information. If the block is nearly full andthe next event cannot fit into the block, it is recorded at the beginning of the nextblock. This process is repeated as call events are recorded in the buffer. If a partialblock is downloaded, the voice processor skips to the next block. It does not returnto fill the partially filled block.

When CDR blocks are manually or automatically downloaded from the CDR bufferto the PC hard disk, the contents of these blocks are not erased from the buffer.The data is simply copied and transmitted to the PC hard disk. If something shouldhappen to recently downloaded and processed CDR data, the CDR blocks can beretrieved, as necessary, until the blocks are overwritten.

SECTION 2.2



CDR blocks are numbered internally from 0 through 65,535; then the numberingsequence restarts with block number 0. The sequence numbers of the oldest block,the current block being filled, and the first block not retrieved are displayed in SMTmenu 16.1.1. A 2020-block buffer can wrap around approximately 32 times before itfills all 65,535 blocks and begins renumbering with block 0. A 7020-block buffer canwrap approximately nine times before renumbering with 0. Although the CDR buffercontains 65,535 logical blocks, a maximum of 2020 or 7020 blocks (depending onthe configuration of the CDR buffer) are filled before the blocks are overwritten anddata is lost. Figure 2-1 is an example of a 7020-block buffer showing sequencenumbering for the first two passes.

BLOCK 0

First passSecond pass

BLOCK 14,039

BLOCK 7020

BLOCK 7019

Figure 2-1. 7020-Block CDR Buffer Diagram, First and Second Pass.

When all 2020 or 7020 blocks are filled, the oldest recorded blocks (initially block 0)are overwritten with current event data, in a first-in first-out (FIFO) sequence. If theoldest blocks were not previously downloaded to a PC, their contents are lost.When it is overwritten, block 0 is renamed with the next sequential number. For a2020- block buffer, block 0 is renamed block 2020 after the first pass (the first passfills blocks 0 through 2019). For a 7020-block buffer, block 0 is renamed 7020 afterthe first pass.

The maximum number of blocks that can be retrieved when downloading dependson the number of blocks for which the voice processor is configured. For example,

If a buffer is configured for 7020 blocks, and block number 10,000 is currentlybeing written (filled), all blocks from 2981 (10,000 minus the 7019 blocks in thefirst pass = 2981) through 10,000 can be retrieved. Any blocks of data that arenumbered at or below 2980 have been permanently overwritten. Figure 2-2illustrates this example.

Refer to Chapter Six for detailed information about the retrieval (downloading) ofblocks from the CDR buffer.

SECTION 2.2



BLOCK 0

BLOCK 7019

Permanently overwritten 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 Diagram With 2980 Overwritten Blocks.

2.3 WARNING OF POTENTIAL CDR DATA LOSS

Alarms are generated if blocks that have not yet been downloaded to the PC areabout to be overwritten. A non-service-affecting (NSA) alarm is logged when theCDR buffer has less than 20% of available space left before unretrieved data will beoverwritten. A service-affecting alarm (SA) is logged when the buffer has less than10% of available space left before unretrieved data will be overwritten. Thesealarms are recorded in SMT menu 13.8 and on the alarm panel if the voiceprocessor is equipped with an alarm panel. The alarm status can also be viewed inthe voice-processor status log. Refer to the System Manager Manual for additionalinformation about the alarm capability.

2.4 DETERMINING PROCESSING TIME AND SIZING THE PC

PC disk-storage-space and processing-time requirements vary based on the typesof CDR events that are collected and the configuration of the voice processor used.Table 2-2 shows PC processing time and storage estimates for a voice processorwith light voice-mail usage. Generally, a voice processor handling only normaltelephone answering and voice mail consumes less CDR buffer and PC storagespace than a voice processor handling an ECP application with a large number ofmailboxes accessed per call. For ECP applications that consume more buffer space,the PC disk-space requirements estimates shown in Table 2-2 should be increasedby 50% or more.

SECTION 2.2 – 2.4



Table 2-2. Example of Processing Time and PC Disk-Space Requirements for a Voice Processor With Light Voice-Mail Usage.

2,500 18 65 0.2 10–255,000 9 32 0.3 20–457,500 6 21 0.4 30–70

10,000 4 16 0.5 40–9515,000 3 10 0.8 60–14020,000 2 8 1.0 80–19025,000 1 6 1.2 100–235

Callsper Day

Buffer Capacity,Days Downloading

& Processing Time at 9600 Baud,

Hr/Daya

PC Disk-SpaceRequirements

per Month,MB

2020-BlockBuffer

7020-BlockBuffer

a Based on the programs running on a PC/AT (8-MHz CPU) equipped with a hard disk with 35-ms average access time.

Table 2-2 lists PC processing-time and storage estimates based on the estimatednumber of calls received per day by a voice processor with light voice-mail usage.Allow for a longer processing time and more PC disk space for storage if the voiceprocessor has moderate or heavy voice-mail usage. The columns in Table 2-2 aredescribed below:

The Calls per Day column indicates the estimated number of calls processedeach day by the voice processor. These calls include incoming calls, outcalls,network calls, and message-waiting-notification calls.

The Buffer Capacity, Days columns are described in section 2.2.1.

The Downloading & Processing Time at 9600 Baud, Hr/Day columnindicates the time required to download and process the data in the CDRbuffer, based on the number of calls processed per day. Use the followingformula to determine the total time, in hours, that a download and processingwill take:

Total processing time = [days between downloading] x [processing time]

For the days between downloading, insert the number from the BufferCapacity, Days column that corresponds to the estimated number of calls perday to the voice processor and the size of the CDR buffer (2020 or 7020blocks). For the processing time, insert the corresponding number from theDownloading & Processing Time at 9600 Baud, Hr/Day column.

The processing time estimates shown in Table 2-2 are the normal elapsedtimes for downloading at 9600 baud and for processing data to create fourstandard output files. If CDR event data is downloaded from the voiceprocessor at 1200 baud, multiply the total estimated time by 4.5 to determine

SECTION 2.4



the total downloading time required. To estimate only downloading time at9600 baud, allow 2 seconds per block. For example,

120 blocks x 2 seconds per block = 240 seconds

240 seconds 60 seconds per minute

= 4 minutes to download

The PC Disk-Space Requirements per Month, MB column indicates themegabytes of PC disk-storage space required to store a full month ofdownloaded data (CDFs, session detail, message detail, unsuccessful transfer,and individual-port-statistics output files), based on the number of callsprocessed per day. If there is not enough storage space on the PC disk, onlya portion of a full month’s data can be stored at a time. Data must beperiodically downloaded, backed up (if desired), and then erased from the PCdisk to avoid running out of room.

Determine the storage space required on the PC disk by locating the numberin the PC Disk-Space Requirements per Month column in Table 2-2 thatcorresponds to the number of calls processed per day by the voice processor.For example,

7500 calls per day = 30 to 70 MB of PC disk space required for downloaded and processed files

Before downloading data from the CDR buffer, check the Display Disk Statussubmenu of the Octel PC/CDR File Utilities Menu to confirm that there isenough available disk-storage space on the PC hard disk. (Refer to section7.2.1 for more information about this menu.) If the PC is about to run out ofstorage space while downloading data from the CDR buffer, the followingmessage appears on the PC screen:

Less than 100 kbytes remaining on disk.

Shutting down as a precaution.

Last block processed: XXXXX

If this message appears, create more storage space on the PC disk by deletingunnecessary files or installing a larger or additional disk drive before continuingwith the download.

2.5 CONFIGURING THE VOICE PROCESSOR FOR CDR DATACOLLECTION

Data is accumulated in the CDR buffer only after the voice processor is configuredto collect Octel PC/CDR data. Configuring the voice processor requires the followingprocedures:

Enable the call-detail recording-software feature option (menu 13.7) to allowthe collection of CDR data.

Configure the Call Detail Records Collected screen (menu 16.1.4) to show thetypes of CDR records to be collected.

Check the Call Detail Recording Status screen (menu 16.1.1) to ensure thatthe CDR buffer has enough storage space available.

SECTION 2.4 – 2.5



Reset the Clear Call Detail Recording Lost Data Counter (menu 16.1.3) ifblocks that have not been downloaded have been overwritten.

If a port is not dedicated to the CDR PC, access menus 13 and 16 through thesystem-manager terminal before the PC has been connected or, after the PC hasbeen connected, access menus 13 and 16 through the Octel PC/CDR SystemMenu, option 5 (Link with Aspen for Performing System Manager Functions). Referto section 4.4 for details about SMT emulation. If a port is dedicated to the CDRPC, access menus 13 and 16 through the Octel PC/CDR System Menu, option 5(Link with Aspen for Performing System Manager Functions) or directly through theSMT.

2.5.1 Confirm Software Feature Enabled

The call-detail recording-software feature option must be enabled before CDR datacan be collected by the voice processor. Perform the following steps to verify thatthis option is enabled:

1. From the Main Menu of the system-manager terminal, select menu 13 andpress the Enter key. The System Maintenance menu appears.

2. Select option 7 from menu 13 and press the Enter key. A screen similar tothe one shown in Figure 2-3 appears. Verify that the call-detail recordingfeature has been enabled. If the 16 – Call Detail Recording feature is notpreceded by a Y, call the local Octel or distributor support office for assistancein enabling the feature.

Press any key to return to option selection:

26 APR 92 12:37:43PM WESTREGVPMOD Serial # ........ 1234 Software Release ...... A1.51

Y 8 – Bulletin Mailbox Y 9 – CSA10 – InterMail Y 12 – Personal PowerCall14 – InfoTex Y 15 – Network Dial–By–Name

Y 16 – Call Detail Recording Y 17 – Database RetrievalY 22 – Forms Mailbox Y 23 – Monitor MailboxY 32 – General Line Types 33 – Mitel LimitedY 34 – RS232 Integrations Y 35 – In-band Integrations

36 – ROLM Limited 37 – Siemens Limited38 – 72 Port Option Y 40 – Information Processing41 – Low Storage Option 42 – Hotel/Motel

Y 43 – DTMF Forms Mailbox Y 44 – NetworkingY 45 – Enhanced Call Processing Y 46 – Ability to Reset PasswordsY 47 – Outcalling Y 48 – Information Center MailboxesY 49 – AMIS Analog Networking Y 50 – Release 10

51 – Octel Index I Y 52 – Octel Index IIY 55 – Conference Mailbox Y 57 – Announcement Mailbox

58 – ACP Integrations 59 – ACP MTA

Figure 2-3. Menu 13.7, Display of Software Features Installed.

3. Additional feature options must be enabled for data to be collected for otherapplications. The 49 – AMIS Analog Networking feature must be enabled ifAMIS (audio messaging interchange specification) data is to be collected, andthe 43 – DTMF Forms Mailbox feature must be enabled for DTMF Octel-Forms data to be collected.

4. Press the Enter key twice to return to the Main Menu.

SECTION 2.5



2.5.2 Select Call Detail Records To Be Collected

Perform the following steps to instruct the voice processor which CDR data recordsto begin collecting for output reports:

1. From the system-manager-terminal Main Menu, select menu 16.a Menu16 – Database Access appears, as shown in Figure 2-4.

Menu 16 – Database Access

1 – Manage Call Detail Recording2 – Retrieve Database Information

Enter Option:

Figure 2-4. Menu 16, Database Access.

2. Select option 1 from menu 16. Menu 16.1, similar to Figure 2-5, is displayed.

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:

Figure 2-5. Menu 16.1, Manage Call Detail Recording.

3. Select option 4 from menu 16.1. The Call Detail Records Collected submenuappears, as shown in Figure 2-6.

Menu 16 – Database AccessCall Detail Records Collected

RecordGroup Types of Records Collected Option

1 All Records As Indicated Below2 Session Related Records Yes3 Message Send/Delete Records No4 Network Related Records No5 Invalid Password Disconnect Records No6 Message Waiting Notification Records No7 DTMF Forms Mailbox Records Yes

Record Group: Option:

Figure 2-6. Menu 16.1.4, Call Detail Records Collected.

a If using the PC as an SMT, only one user can access menu 16 at a time. Refer to section 4.4 for detailsabout SMT emulation.

SECTION 2.5



Menu 16.1.4 displays the choices of types of CDR records to be collected. Thisinformation must be entered before the voice processor can begin collecting CDRevents. Select one or more of six different record types: Session Related, MessageSend/Delete, Network Related, Invalid Password Disconnect, Message WaitingNotification, and DTMF Forms Mailbox. Refer to Appendix C for a list of theapproximate byte size of each event included in each of the record selectionsavailable in the menu shown in Figure 2-6. Keep this and the available storagespace on the CDR buffer and the PC in mind when selecting record groups to becollected.

Request the Message Send/Delete Records group only if detailed data about allmessages is desired. If this group is not selected in menu 16.1.4, entries in thetotal-messages-sent and total-messages-deleted data fields in the session-detailoutput file will all be zeros.

The Network Related Records group collects OctelNet data. AMIS networking datais also collected if Record Group 4 is selected and feature option 49 is enabled(refer to section 2.5.1).

DTMF OctelForms data is collected if record groups 2 and 7 are selected andfeature option 43 is enabled (refer to section 2.5.1).

Message-waiting-notification records provide details about every message-waitingset and clear attempt for voice processors with in-band integration. This fills thebuffer blocks quickly, especially on large voice processors. Message waiting eventsare not generated by voice processors with RS-232 integrations.

Refer to Table 2-3 to determine which record group(s) to select from the Call DetailRecords Collected submenu so the appropriate records are collected. For example,

If message-detail output files are desired, select record groups 2, 3, and 5.

Table 2-3. Record Groups Required for Octel PC/CDR Output Files.

DesiredOutputFiles

Record Groups Required

1 – AllRecords

2 – SessionRelatedRecords

3 – MessageSend/Delete

Records

4 – NetworkRelatedRecords

5 – InvalidPasswordDisconnect

Records

6 – MessageWaiting

Notification

7 – DTMFForms

MailboxRecords

Session Detail

UnsuccessfulTransfer

Message Detail

Individual PortStatistics

DTMF OctelForms(optional)

X

X

X

X

X

X

X

X

X

X

X

X

X X

X

X X

X

a

a Available for voice processors with in-band integration only.

SECTION 2.5



To select the types of records to be collected, perform the following steps:

1. Refer to Figure 2-6 and Table 2-3. Type the record group number(s) for therequired records, based on the desired output files, in the Record Group:field. Select record group 1 only if all of the output files are desired.

2. In the Option: field, select the record group to be collected by pressing Y foryes or N for no. Press the Enter key.

3. Repeat steps 1 and 2 until all of the desired record groups have beenselected.

4. Press the Print Send key (or the Page Down key on some keyboards) tomake the changes.

5. Press any key to return to the Manage Call Detail Recording menu (submenu16.1).

2.5.3 Monitor Available CDR Buffer Storage Space

The Call Detail Recording Status screen (menu 16.1.1), shown in Figure 2-7, allowsthe system manager to monitor important information about the CDR buffer. Thisinformation includes the amount of free CDR buffer space, the total number ofblocks reserved for CDR (either 2020 or 7020), the block sequence numbers, andthe number of overwritten blocks. The information displayed is updated automatical-ly by the voice processor and cannot be changed by the system manager.

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

Figure 2-7. Menu 16.1.1, Call Detail Recording Status.

Review the CDR Disk Space Free: field often to check for free CDR buffer space.Download as necessary to avoid having blocks that have not been downloadedoverwritten when the CDR buffer is 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.5.5 to reset this counter to 0.

2.5.4 Use Retrieve Call Detail Records Option for Download by ServiceEngineer

The Retrieve Call Detail Records option (menu 16.1.2) is used only by field serviceengineers (through SMT emulation) to perform a special service-related download.

SECTION 2.5



A similar menu is described in Chapter Six. Refer to section 6.2.1 for instructionsabout how to select blocks to be retrieved manually through the Octel PC/CDRsoftware.

2.5.5 Clear Call Detail Recording Lost Data Counter

If blocks that have not been downloaded have been overwritten, use the Clear CallDetail Recording Lost Data Counter submenu (menu 16.1.3) to clear the overwrittenblock counter (menu 16.1.1) before new data blocks can be downloaded. If thiscounter is not cleared, the downloading process cannot be executed.

To clear the counter, select option 3 and press the Enter key. The counter iscleared and the following prompt appears:

Lost data counter cleared. Press any key to continue:

Figure 2-8 shows menu 16.1 after suboption 3 is selected.

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:

Figure 2-8. Clear Call Detail Recording Lost Data Counter Screen.

2.6 HIGHLIGHTS

When the Octel PC/CDR software is first installed, monitor the CDR bufferdaily to establish a pattern as to how quickly the buffer fills, then performdownloads based on this pattern.

Octel PC/CDR data is recorded in the CDR buffer on the voice-processordrives.

The CDR buffer can be sized for 2020 or 7020 blocks.

The CDR buffer size can be increased, but cannot always be reduced.

CDR records to be collected by the voice processor are identified in menu16.1.4.

CDR event data should be downloaded when the CDR buffer becomes 30%to 50% filled with new CDR event records.

SECTION 2.5 – 2.6

3

INSTALLATIONPROCEDURES


CHAPTER THREECONTENTS

3.1 OVERVIEW 3-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2 VERIFY OCTEL PC/CDR FEATURE 3-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.3 INSTALL OCTEL PC/CDR SOFTWARE INTO PC 3-1. . . . . . . . . . . . . . . . . . . . . . .

3.4 CREATE CDR SYSTEM DATA SUBDIRECTORIES USING MKCDRSYS 3-5. . .

3.5 REMOVE CDR SYSTEM DATA SUBDIRECTORIES 3-8. . . . . . . . . . . . . . . . . . . . .

3.6 UPGRADE OCTEL PC/CDR SOFTWARE 3-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.7 HIGHLIGHTS 3-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

FIGURES

Figure 3-1. Octel PC/CDR Installation Program Menu 3-2. . . . . . . . . . . . . . . . . . . . . .

Figure 3-2. Listing of the New CONFIG.SYS File and a SampleAUTOEXEC.BAT File Showing Added Line 3-3. . . . . . . . . . . . . . . . . . . . .

Figure 3-3. Load Octel PC/CDR System Screen 3-4. . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-4. Files Created by the INSTCDR Command 3-4. . . . . . . . . . . . . . . . . . . . . .

Figure 3-5. Example of Octel PC/CDR Disk-Directory Structure 3-6. . . . . . . . . . . . .

Figure 3-6. First Octel PC/CDR System Data Directory Creation Menu 3-7. . . . . . .

Figure 3-7. Second Octel PC/CDR System Data Directory Creation Menu 3-7. . . .

Figure 3-8. Example of a System Creation Screen 3-7. . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-9. Octel PC/CDR Upgrade Program Menu 3-9. . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-10. Upgrade Octel PC/CDR System Screen 3-9. . . . . . . . . . . . . . . . . . . . . . . .

Figure 3-11. Files Created by the UPGRCDR Command 3-10. . . . . . . . . . . . . . . . . . .

Section Page

3


INSTALLATION PROCEDURES

3.1 OVERVIEW

This chapter provides information about loading software into the PC, setting up thevoice processor’s configuration parameters, and establishing the communication linkwith the voice processor. The following steps, described in Chapters Two throughFive, are required to install and configure Octel PC/CDR:

1. Verify that the Octel PC/CDR feature is enabled in voice processors byviewing system manager menu 13, submenu 7 (section 2.5.1).

2. Install the Octel PC/CDR software on the PC using the INSTCDR command(section 3.3).

3. Create CDR system data subdirectories using MKCDRSYS (section 3.4).

4. Configure Octel PC/CDR parameters (section 4.3).

5. Test the direct or modem connection (section 4.4) from the PC to the voiceprocessor.

6. Configure the Carbon Copy Plus software on the PC (section 5.2). (CarbonCopy PLUS is to be used only when directed for system maintenance.)

3.2 VERIFY OCTEL PC/CDR FEATURE

For CDR data to be collected by the voice processor, the call detail recordingsoftware feature (menu 13.7, feature 16) must be enabled. Refer to section 2.5.1 forinstructions about how to verify that this feature is enabled.

3.3 INSTALL OCTEL PC/CDR SOFTWARE INTO PC

Octel PC/CDR software is provided on a single diskette in a compressed format.This diskette contains the installation program for installing the software on adestination drive. When the software is fully installed, it uses approximately 1.8 MBof disk-storage space. (Additional storage space is required for downloaded andprocessed files. Refer to section 2.2.1.)

The INSTCDR.EXE utility program on the Octel PC/CDR master diskette is used tocopy the Octel PC/CDR software onto the PC hard disk and to create the followingsubdirectories:

OCTELCDR contains the software for processing Octel PC/CDR files. Thefiles in this subdirectory are listed in Appendix D, Table D-1.

OCTELCDR\MIR contains the data-communications utility software forconnecting the CDR PC to the voice processor. The files in this subdirectoryare listed in Appendix D, Table D-2.



OCTELCDR\CC contains Carbon Copy software, which is used for remote PCmaintenance. The files in this subdirectory are listed in Appendix D, Table D-3.

OCTELCDR\LOG contains the SCHEDCDR.LOG file that is the log for theautomatic scheduler.

The INSTCDR.EXE utility also modifies (appends) or creates the AUTOEXEC.BATand CONFIG.SYS files in the root directory. If these files previously existed, theoriginal files are renamed with the extension .OLD and are not used with OctelPC/CDR.

Perform the following steps to install the Octel PC/CDR software:

1. Insert the Octel PC/CDR diskette into a compatible disk drive on the PC to beused for the Octel PC/CDR software.

2. Change the drive indicator (normally a part of the DOS prompt) to the drivecontaining the Octel PC/CDR diskette. For example,

If the diskette is inserted into drive one, type a: at the C: prompt. Press theEnter key.

3. At the A: prompt, type instcdr and press the Enter key. The Octel PC/CDRInstallation Program menu appears with default options, as shown in Figure3-1. The default values are generally used in a new installation, but theyshould always be verified.

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–1992 Octel Communications Corporation

Figure 3-1. Octel PC/CDR Installation Program Menu.

4. Use the following definitions to determine the correct entry for each field. Asnecessary, move the cursor to the appropriate field and type in the new entry.

The Source Drive Name: field shows the drive used to read the OctelPC/CDR software diskette. The drive being used to view this menu isdisplayed. This field cannot be changed.

The Boot Drive Name: field shows from which drive the PC boots. Thisshould be the letter designating the PC hard-disk drive.

SECTION 3.3



The Destination Drive Name: field specifies the drive on which theOctel PC/CDR software is going to be stored. This destination must bea hard-disk drive or a part of a hard-disk drive with at least 1.8 MBcurrently available. (Additional storage space is required for downloadedand processed files. Refer to section 2.2.1.)

The Update autoexec.bat & config.sys?: field questions whether thePC boot files should be altered. Leave this field with the default of Y ifthis is the first installation of the Octel PC/CDR software; otherwise,change to N.

The AUTOEXEC.BAT file is updated so that the PC has a path to theOctel PC/CDR software. The CONFIG.SYS file is modified to create thecorrect environment for the Octel PC/CDR software to operate asspecified. These files are created if they do not already exist. Figure 3-2shows an example of an updated AUTOEXEC.BAT and CONFIG.SYSlisting. The arrows to the left indicate the lines added and modifiedduring the installation of the Octel PC/CDR software. The INSTCDRcommand does not change the existing parameters in these files.

type AUTOEXEC.BAT

echo offprompt $p$g$cclspath c:\;c:\utils;c:\dos;d:\dbxl;d:\ws;d:\ws\docs;d:\nortonecho

NEW OR MODIFIED–––> set path=%path%;C:\octelcdr

type CONFIG.SYS

device=C:\octelcdr\ansi.sys buffers=20 files=60 shell=C:\COMMAND.COM /p /e:1000

NEW ORMODIFIED

Figure 3-2. Listing of the New CONFIG.SYS File and a SampleAUTOEXEC.BAT File Showing Added Line.

The Install Octel PC/CDR Software?: field questions whether the PCsoftware should be installed. Leave the default of Y to install the OctelPC/CDR software.

5. Press the F10 key when all item changes are complete. A screen similar toFigure 3-3 appears.

6. When the Proceed with Installation? [y/n] prompt appears, select Y. Thesoftware load begins and takes approximately 5 minutes.

As each file is created, the file name appears on the screen; as the screenfills, data at the top scrolls off the screen. Figure 3-4 shows a listing of all thefiles created by the INSTCDR command.

SECTION 3.3



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

C:\>A:instcdr********** 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\VT100.MEFC:\OCTELCDR\MIR\WY50SPEC.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\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.SYSSYSNAME.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

Figure 3-4. Files Created by the INSTCDR Command.

SECTION 3.3



7. After the software is loaded, remove the diskette from the source drive andstore it in a safe place. Keep this diskette as a backup.

8. If Y was selected in step 4 to update the AUTOEXEC.BAT and CONFIG.SYSfiles, restart the PC by pressing the Ctrl , Alt , and Del keys simultaneously. Thenew files are then loaded into the PC memory during the PC boot process.

3.4 CREATE CDR SYSTEM DATA SUBDIRECTORIES USINGMKCDRSYS

Use the MKCDRSYS utility to create CDR system subdirectories on the PC harddisk for each voice processor that downloads CDR data. Choose an appropriatename for each CDR system—one that is easily remembered and unique for eachvoice processor.

The MKCDRSYS utility creates the following eight subdirectories on the PC harddisk for each CDR system subdirectory:

BCF: Contains binary collection files (raw data)

CDF: Contains collated day files

SYS: Contains log files, pending state files, and system attribute files

SDO: Contains session-detail output files

UTO: Contains unsuccessful-transfer output files

MDO: Contains message-detail output files

PSO: Contains individual port-statistics output files

FDO: Contains forms output files (optional)

Each set of directories contains Octel PC/CDR data for a particular voice processor.One system directory and eight subdirectories are included for each CDR system.Figure 3-5 is an example of this file structure with the DOS, SYSTEMNAME, andOCTELCDR subdirectories all on the same hard disk. These subdirectories could eachbe on a separate hard disk, with the appropriate paths being established at the timethe CDR system name is established.

If an incorrect CDR system is created or is no longer needed, use the RemoveOctel PC/CDR system utility to delete it.

Perform the following steps to create CDR system names and subdirectories:

1. At the DOS prompt, enter the MKCDRSYS command using the following syntax:

mkcdrsys [systemname] [datadrive:] [progdrive:]

where

mkcdrsys is the command utility to create a CDR system on the hard drive.

systemname is the unique name chosen to identify a particular OctelPC/CDR voice processor.

datadrive: is the drive in which the data subdirectories are created.

progdrive: indicates the drive containing the installed Octel PC/CDRsoftware.

SECTION 3.3 – 3.4



DOS SYSTEMNAME OCTELCDR

BCFBinary

Collection Files

CDFCollatedDay Files

UTOUnsuccessfulTransfer Files

SYSSystem

Files

Detail FilesMessage

MDO PSOIndividual PortStatistics Files

SDOSession

Detail-Output

Myymmdd.DBF/ASC Pyymmdd.DBF/ASCByymmdd.DBF/ASC Xyymmdd.DBF/ASC

PC/CDRProcessingPrograms

COLLATE.PSF, Log Files, Pending StateCDyymmdd.CDFAyymmddi.BCF

All DosFiles (80+)

Autoexec.batConfig.sys

PC HARD DISKROOT DIRECTORY

FDOForms Output File

(optional)

FORMS.DBF/ASC

CC

MIR

Files (PSF), System Attribute File

LOG

Files

Ayymmddi.PCFAyymmddi.PSF

Figure 3-5. Example of Octel PC/CDR Disk-Directory Structure.

For example,

If the new CDR system subdirectory for the voice processor located in thewestern region will be located on drive C:, the same drive as the OctelPC/CDR software, type the following:

mkcdrsys westreg c: c:

Press the Enter key. The first Octel PC/CDR System Data Directory Creationmenu appears, similar to Figure 3-6.

2. To print a copy of this session, follow the prompts on the screen to enable theprinter.

3. Press any key to continue. The second Octel PC/CDR System Data DirectoryCreation menu appears, similar to Figure 3-7.

4. Press any key to continue or press the Ctrl and C keys (^C ) simultaneouslyto abort the MKCDRSYS utility. If the process is to continue, a screen similarto Figure 3-8 appears.

SECTION 3.4



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 3.30

If you would like a printed copy of this session then1) 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 Data Directory Creation Menu.

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 Data Directory Creation Menu.

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.

5. Make note of the instructions on the screen about accessing files. If printeroutput was enabled in step 2, follow the prompts on the screen to disable it.

6. Press any key to continue. The DOS prompt appears.

7. From the DOS prompt, type cdrhelp and press the Enter key to display allpreviously created CDR systems.

SECTION 3.4



3.5 REMOVE CDR SYSTEM DATA SUBDIRECTORIES

The RMCDRSYS utility removes CDR systems that were created using theMKCDRSYS command. This command deletes all files from the directoriesspecified, then removes all directories related to the specified CDR system name.To remove an established CDR system, perform the following steps:

1. At the DOS prompt, type the RMCDRSYS command using the followingsyntax:

rmcdrsys [systemname] [datadrive:] [progdrive:]

where

rmcdrsys is the command utility to remove a CDR system from the hard drive.

systemname is the name of the CDR system to remove.

datadrive: is the drive on which the directories reside.

progdrive: is the drive on which the \OCTELCDR directory resides.

Press the Enter key. The following prompt appears:

About to delete CDR system directory “c:\XXXXXXXX”and remove startup file “C:\ OCTELCDR\XXXXXXXX.BAT”

Press CTRL-C to abortPress any key to continue . . .

where

XXXXXXXX is the name of the CDR system to be deleted.

2. Press any key to delete the named CDR system and all of its related files andsubdirectories. The DOS prompt appears when the deletion is complete.

3. Once the CDR system has been deleted, its name must be deleted from allautomatic schedules (refer to section 6.4.1.2).

4. To return to the Octel PC/CDR System Menu, press the F6 key to disconnectthe link between the PC and the voice processor.

3.6 UPGRADE OCTEL PC/CDR SOFTWARE

When upgrading the Octel PC/CDR software, the previously downloaded data for allCDR systems created using the MKCDRSYS remains unchanged. The OctelPC/CDR system attributes are also not affected by the upgrade. The new softwareis copied over the old software.

The process to upgrade the Octel PC/CDR software is similar to the initial softwareinstallation. Perform the following steps to upgrade the software:

1. Insert the Octel PC/CDR diskette into a compatible disk drive on the PC to beused for the Octel PC/CDR software.

2. Change the drive indicator (normally a part of the DOS prompt) to the drivecontaining the Octel PC/CDR diskette. For example,

If the diskette is inserted into drive one, type a: at the C: prompt. Press theEnter key.

SECTION 3.5 – 3.6



3. At the A: prompt, type upgrcdr and press the Enter key. The Octel PC/CDRUpgrade Program menu appears with default options, as shown in Figure 3-9.The default values are generally used in an upgrade, but they should alwaysbe verified.

F1 – Help F10 – Proceed ESC – Cancel/Quit

Octel PC/CDR Upgrade Program(C)Copyright 1988–1992 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

Figure 3-9. Octel PC/CDR Upgrade Program Menu.

4. Use the following definitions to determine the correct value for each field. Asnecessary, move the cursor to the appropriate field and type in the value to bechanged.

The Source Drive Name: field shows the drive used to read the OctelPC/CDR software diskette. The drive being used to view this screen isindicated. This field cannot be changed.

The Boot Drive Name: field specifies from which drive the PC boots.This should be the letter designating the PC hard-disk drive.

The Destination Drive Name: field specifies the drive on which theOctel PC/CDR software is stored. This destination must be a hard-diskdrive or a part of a hard-disk drive with at least 1.8 MB currentlyavailable. (Additional storage space is required for downloaded andprocessed files. Refer to section 2.2.1.)

The Update autoexec.bat & config.sys?: field questions whether thePC boot file should be altered. Move the cursor to this field and press Yfor yes to update the AUTOEXEC.BAT and CONFIG.SYS files.

The Upgrade Octel PC/CDR Software?: field questions whether thePC software should be upgraded. Leave the default of Y to perform anupgrade.

5. Press the F10 key when all item changes are complete. A screen similar toFigure 3-10 appears.

This program is about to perform the following:

Upgrade “autoexec.bat” and “config.sys” files on Drive “C:” 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.6



6. When the Proceed with Upgrade? [y/n] prompt appears, select Y. Thesoftware upgrade begins and takes approximately 5 minutes.

As each file is upgraded, the file name appears on the screen; as the screenfills, data at the top scrolls off the screen. Figure 3-11 shows a listing of allthe files created by the UPGRCDR command.

********** Updating CONFIG.SYS **********File “C:\CONFIG.SYS” updated

********** Updating AUTOEXEC.BAT **********File “C:\AUTOEXEC.BAT” updated

********** Upgrading Octel PC/CDR software **********

C:\OCTELCDR\MIR\CDRDOWNL.XTSC:\OCTELCDR\MIR\CDRDOWNL.XTKC:\OCTELCDR\MIR\LINKSMT.XTSC:\OCTELCDR\MIR\LOGOFF.XTSC:\OCTELCDR\MIR\LANGUAGE.XTKC:\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.SYSSYSNAME.DAT 1 File(s) copiedCDRP.SN 1 File(s) copiedContents of upgrade disk loaded

After you have made changes to “autoexec.bat” and “config.sys”,reboot your computer. Then type MKCDRSYS for instructions on howto create Octel PC/CDR System Data Files.

Figure 3-11. Files Created by the UPGRCDR Command.

7. After the software is upgraded, remove the diskette from the source drive andstore it in a safe place. Keep this diskette as a backup.

8. Restart the PC by pressing the Ctrl , Alt , and Del keys simultaneously. Thenew AUTOEXEC.BAT and CONFIG.SYS files are then loaded into the PCmemory during the PC boot process.

3.7 HIGHLIGHTS

The Octel PC/CDR feature is verified in voice-processor system-managermenu 13.7.

The Octel PC/CDR software is loaded into the PC drive. It requires 1.8 MB ofstorage space for the software and additional storage space for downloadedand processed files.

A set of CDR system subdirectories is created for each voice processor thatdownloads data to the CDR PC.

SECTION 3.6 – 3.7

4

SOFTWARE ATTRIBUTES


CHAPTER FOURCONTENTS

4.1 OVERVIEW 4-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.2 ACCESS THE OCTEL PC/CDR SYSTEM MENU 4-1. . . . . . . . . . . . . . . . . . . . . . . .

4.2.1 CDR Command 4-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.2.2 System Name Command 4-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.3 CONFIGURE OCTEL PC/CDR PARAMETERS AND SYSTEM ATTRIBUTES 4-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.3.1 Log Octel PC/CDR Processing Output to Printer 4-4. . . . . . . . . . . . . . . . .

4.3.2 Erase Binary Collection Files After Collation 4-4. . . . . . . . . . . . . . . . . . . . .

4.3.3 Erase Binary and Collated Day Files 4-5. . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.3.4 Erase All Output and Log Files 4-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.3.5 Modify Automatic (or Scheduled) Output File Generation 4-5. . . . . . . . . .

4.3.6 Modify Output File Format Types 4-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.3.7 Modify Communications Parameters 4-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.7.1 Communications Port 4-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.7.2 Communication Speed (Baud) 4-8. . . . . . . . . . . . . . . . . . . . . . . . . 4.3.7.3 Connection Type 4-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.7.4 Modem Initialization String 4-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.7.5 Dial Prefix String 4-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.7.6 VPMOD Telephone Number 4-9. . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.7.7 Dial Suffix String 4-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.7.8 Terminal Emulation Type 4-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.7.9 VPMOD System Type 4-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.3.7.10 VPMOD Software Version Number 4-10. . . . . . . . . . . . . . . . . . . . 4.3.7.11 VPMOD System Password 4-10. . . . . . . . . . . . . . . . . . . . . . . . . . .

4.3.8 Modify Next Block To Download by Automatic Octel PC/CDR Processing 4-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.3.9 Modify Output File Format Level 4-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.4 TEST THE DIRECT CONNECTION BETWEEN THE PC AND THE VOICE PROCESSOR 4-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.5 HIGHLIGHTS 4-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section Page


TABLE

Table 4-1. Special-Emulation Function Keys 4-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

FIGURES

Figure 4-1. Octel PC/CDR Main Menu 4-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 4-2. CDR System Selection Menu 4-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 4-3. Octel PC/CDR System Menu, Password Not Set 4-2. . . . . . . . . . . . . . . .

Figure 4-4. Octel PC/CDR System Menu 4-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 4-5. Octel PC/CDR System Attributes Menu 4-4. . . . . . . . . . . . . . . . . . . . . . . .

Figure 4-6. Modify Automatic Output File Generation Menu 4-5. . . . . . . . . . . . . . . . .

Figure 4-7. Modify Output File Format Types Menu 4-6. . . . . . . . . . . . . . . . . . . . . . . .

Figure 4-8. Session Detail Output File Type Menu 4-6. . . . . . . . . . . . . . . . . . . . . . . . .

Figure 4-9. Modify PC Communications Parameters Menu 4-8. . . . . . . . . . . . . . . . . .

Figure 4-10. Octel PC/CDR System Attributes Menu for NextBlock to Download Option 4-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 4-11. Octel PC/CDR System Attributes Menu for ModifyOutput Format File Level Option 4-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Page

4


SOFTWARE ATTRIBUTES

4.1 OVERVIEW

The Octel PC/CDR software consists of several components that are required todownload, process, and back up the Octel PC/CDR output files. Before thesecomponents can function, the Octel PC/CDR system attributes must be configuredproperly.

While in the Octel PC/CDR software, toggle the entry in fields requiring a y or n(yes or no) response by selecting the option number for that field.

4.2 ACCESS THE OCTEL PC/CDR SYSTEM MENU

After the Octel PC/CDR software and system directories are installed on the PChard drive, access the Octel PC/CDR Main Menu by typing one of the followingcommands at the DOS prompt:

CDR

The individual CDR system name

4.2.1 CDR Command

Perform the following steps to access the Octel PC/CDR System Menu with theCDR command:

1. Type cdr at the DOS prompt and press the Enter key. The Octel logo andOctel PC/CDR banner screens appear.

2. To bypass these screens and proceed to the Main Menu, immediately pressthe Enter key. The Octel PC/CDR Main Menu appears, as shown in Figure4-1.

Octel PC/CDR Main Menu, REV 1.50

0 Exit to DOS

1 Select an Individual System for CDR Processing2 Automatic Scheduler Functions

Enter Option:

Figure 4-1. Octel PC/CDR Main Menu.

3. Select option 1 and press the Enter key to display a list of all the availableCDR systems. A screen similar to Figure 4-2 appears.

SOFTWARE ATTRIBUTES


CDR System Selection Menu

0 Return to Main Menu

1 EASTREG 3 SOUTHREG 5 WESTREG2 CENTREG 4 HEADQT

Enter Option:

Figure 4-2. CDR System Selection Menu.

4. Select the applicable CDR system by typing its corresponding number in theEnter Option: field. Press the Enter key. If the system-manager passwordhas not been established, a screen similar to Figure 4-3 appears.

Octel PC/CDR System Menu, REV 1.50 westreg

System Manager’s Password not setPress ENTER/RETURN to continue.

Figure 4-3. Octel PC/CDR System Menu, Password Not Set.

5. If the system-manager password has not been established, press the Enterkey to continue. If the system-manager password has been established, thepassword is requested. Type the password and press the Enter key. A screensimilar to Figure 4-4 appears.


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 4-4. Octel PC/CDR System Menu.

A warning message, similar to the following, appears above the Enter Option:field on this menu if the PC hard disk has less than 15% of its storage spaceavailable.

Warning – Disk C: 15% Free, 5,098 KBytes Available

If this message appears, refer to section 2.4 before proceeding to determinethe amount of storage space needed and then create free space as required.

SECTION 4.2

SOFTWARE ATTRIBUTES


4.2.2 System Name Command

Perform the following steps to access the Octel PC/CDR System Menu by typingthe individual CDR system name:

1. At the DOS prompt, type the name of the CDR system to be configured (asestablished using the MKCDRSYS command, section 3.4). Press the Enterkey. Type the CDR system name for access to the CDR system menus eachtime processing data and updating attributes for that particular CDR system isdesired. A screen similar to the one shown in Figure 4-3 appears. Until asystem-manager password is entered in the Octel PC/CDR System AttributesMenu (option 7, suboption 11), a message appears indicating that nopassword is required to enter the Octel PC/CDR system menus.

2. If the system-manager password has not been established, press the Enterkey to continue. If the system-manager password has been established, thepassword is requested. Type the password and press the Enter key. A screensimilar to Figure 4-4 appears.

4.3 CONFIGURE OCTEL PC/CDR PARAMETERS ANDSYSTEM ATTRIBUTES

The system attributes and parameters must be configured for each CDR systemcreated with the MKCDRSYS command. This process involves making choices thatrelate specifically to each CDR system, the CDR data, and its communicationsrequirements.

Verify that all of the attributes are properly set forthe specific CDR system’s requirements.Incorrectly set attributes can cause the softwareto function incorrectly.

Caution!

To configure CDR system parameters, perform the following steps for each CDRsystem created in section 3.4:

1. Access the Octel PC/CDR System Menu (Figure 4-4) by following theinstructions given in section 4.2.

2. From the Octel PC/CDR System Menu, select option 1 and press the Enterkey to update system attributes. A screen similar to Figure 4-5 appears.

3. To review or modify the Octel PC/CDR system attributes for this particular CDRsystem (in this example, westreg), refer to Figure 4-5 and type the optionnumber corresponding with the description of the attribute to be changed. Pressthe Enter key. With some options, the entry in the field toggles to other choiceseach time the option number is typed. Other options, when selected, requirethat a number be typed or additional screens displayed. Refer to sections 4.3.1through 4.3.9 for information about CDR system attribute options.

SECTION 4.2 – 4.3

SOFTWARE ATTRIBUTES


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) 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):

Figure 4-5. Octel PC/CDR System Attributes Menu.

4. When all changes to the attributes are made in the Octel PC/CDR SystemAttributes Menu, type 0 and press the Enter key to save the new attributesand return to the Octel PC/CDR System Menu (Figure 4-4). A message brieflyappears at the bottom of the screen indicating that the system parametershave been saved.

If inappropriate parameters are entered, press the Esc key to return to the OctelPC/CDR System Menu, and the new system attributes will not be saved.

5. Type 0 and press the Enter key to exit to DOS.

Sections 4.3.1 through 4.3.9 detail the options shown on the Octel PC/CDR SystemAttributes Menu.

4.3.1 Log Octel PC/CDR Processing Output to Printer

When the Octel PC/CDR programs are executed, the results appear on the screen. If YES is selected for option 1 and a printer is connected to the CDR computer,these results are also printed. The default of NO toggles to YES when the optionnumber is typed. Choose YES for this option, particularly for automatic or unattendedprocessing. If printed output is not desired, choose NO.

All Octel PC/CDR processing results are also sent to log files in the SYS sub-directory. These files are named in the form Lyymmdd.LOG, where yymmdd is thedate that processing occurred.

4.3.2 Erase Binary Collection Files After Collation

To conserve Octel PC/CDR disk-storage space, refer to Figure 4-5 and choose YES for option 2 so that the processing program automatically deletes the binarycollection files (BCFs) after they have been collated. BCFs are raw data files; afterthey have been processed, they are no longer needed. BCFs should be deletedafter processing, because they take up a great deal of disk space.

If NO is chosen, the first time the BCF is processed, it is renamed with a fileextension of PCF (Processed Collection File). PCFs must be deleted at a future

SECTION 4.3

SOFTWARE ATTRIBUTES


time, such as when the disk is full, when the PCFs have been backed up ontoanother disk, or when the data is no longer needed. Refer to section 7.2.4 forinformation about how to back up files.

Refer to section 4.3.3. for instructions about how to have BCFs and PCFs auto-matically deleted after a designated period of time.

4.3.3 Erase Binary and Collated Day Files

To keep BCFs and PCFs temporarily, refer to Figure 4-5, select option 3, and pressthe Enter key. This option retains the BCFs and PCFs for a specified number ofdays, then automatically deletes them. When option 3 is selected, the EraseBCF/CDF files after how many days (0 = permanent)? prompt appears. Type thenumber between 0 and 999 that represents the number of days the files should bekept before they are erased. If 0 is entered, the files are kept indefinitely.

4.3.4 Erase All Output and Log Files

Use option 4 to erase all output and log files automatically after a specified numberof days. This option allows time for files to be copied to floppy diskettes, thenautomatically erases the old files. Erased log files cannot be recovered, and erasedoutput files can only be re-created if the PCFs are still available.

Refer to Figure 4-5, select option 4, and press the Enter key. The Erase Log/Output files after how many days (0 = permanent)? prompt appears. Type thenumber between 0 and 999 that represents the number of days the files should bekept before they are erased. If 0 is entered, the files are kept indefinitely.

4.3.5 Modify Automatic (or Scheduled) Output File Generation

Perform the following steps to modify the output files that are created when thescheduled or automatic processing function is executed (this process is described insections 6.3 and 6.4):

1. Refer to Figure 4-5, select option 5, and press the Enter key. A screen similarto Figure 4-6 appears.

Modify Automatic Output File Generation westreg

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 No

10 Append Records to Forms Output File No

Enter Option:

Figure 4-6. Modify Automatic Output File Generation Menu.

SECTION 4.3

SOFTWARE ATTRIBUTES


2. To set the menu to generate the appropriate files, type the option number forthe first desired file, then press the Enter key. The Current Setting default ofNO toggles to YES when the option number is selected.

3. Repeat step 2 to select each output file to be generated. Select option 10 toadd new records to the current Forms Output File.

4. Type 0 and press the Enter key to return to the System Attributes Menu.

4.3.6 Modify Output File Format Types

Perform the following steps to examine or change the format (dBASE III or ASCII)of the output files:

1. Refer to Figure 4-5, select option 6, and press the Enter key. A screen similarto Figure 4-7 appears. The default file format is the dBASE III-compatibleformat. If an ASCII file format is desired, the setting must be changed.

Modify Output File Format Types westreg

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 compatible

10 Set Forms Output File Type dBASE III compatible

Enter Option:

Figure 4-7. Modify Output File Format Types Menu.

2. Type the option number of the output-file type to change (if necessary) at theEnter Option: prompt and press the Enter key. A screen similar to Figure 4-8appears. Figure 4-8 shows the file formats available for Session Detail Outputfiles.

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 4-8. Session Detail Output File Type Menu.

SECTION 4.3

SOFTWARE ATTRIBUTES


3. Type the number of the desired output format type at the Enter Option:prompt and press the Enter key.

4. Repeat steps 2 and 3 until the screen shows the correct type of file format forall output files.

5. Type 0 and press the Enter key to return to the System Attributes Menu(Figure 4-5).

4.3.7 Modify Communications Parameters

The Modify Communications Parameters option (option 7 on Figure 4-5) establishesthe PC attributes for linking the PC with the voice processor. The followingsuboptions must be specified correctly to link the PC successfully with the voiceprocessor:

Suboption 1 – Communication Port

Suboption 2 – Communication Speed (Baud)

Suboption 8 – Terminal Emulation Type

Suboption 9 – VPMOD System Type

Suboption 10 – VPMOD Software Version Number

Suboption 11 – VPMOD System Password

Verify that all of the attributes are properly set forthe specific CDR system’s requirements.Incorrectly set attributes can cause the softwareto function incorrectly.

Caution!

Modify suboptions 4 through 7 from the Modify PC Communications Parametersmenu shown in Figure 4-9, only if a modem is required to connect the PC with thevoice processor. These suboptions are required to direct the action of the modem.Most Hayes and Hayes-compatible modems can be used for communicationbetween the PC and the voice processor. The standard 9600-baud-modem valuesare the default settings for these modem dial strings (suboptions 4, 5, and 7). If adirect connection with the voice processor is used, the telephone-number setting(suboption 6) must be blank. The modem software configuration cannot be changedthrough the voice processor; it must be entered correctly in the Modify PCCommunications Parameters menu.

Echo on is a default setting for most modems; however, when connected to a voiceprocessor, the modem must be set to echo off. If the modem is set to echo on,data sent from a voice processor is returned to the voice processor. The dataechoed back to a voice processor can overflow the buffer, slow down the voiceprocessor, and cause the voice processor to restart. Consult the modem manual forthe proper codes to use.

SECTION 4.3

SOFTWARE ATTRIBUTES


Modify PC Communications Parameters westreg


1 Communication Port 22 Communication Speed (Baud) 96003 Connection Type Direct4 Modem Initialization String5 Dial Prefix String ATVOX1DT6 VPMOD Telephone Number7 Dial Suffix String |8 Terminal Emulation Type WY50SPEC9 VPMOD System Type Aspen

10 VPMOD Software Version Number 1.5111 VPMOD System Password

Enter Option:

Figure 4-9. Modify PC Communications Parameters Menu.

The following steps provide basic instructions for establishing the parameters withinoption 7 (Figure 4-5) and explain each communication parameter suboptiondisplayed in the Modify PC Communications Parameters menu (Figure 4-9).

1. Select option 7 from the Octel PC/CDR System Attributes Menu (Figure 4-5)and press the Enter key. The Modify PC Communications Parameters menu(Figure 4-9) appears. Review each option to verify that the parameters areproperly set for the specific requirements of the specified CDR system. Selectthe appropriate option number and type in the new information to update asnecessary.

2. After entering the correct attributes from the Modify PC CommunicationsParameters screen (Figure 4-9), type 0 and press the Enter key to return tothe System Attributes Menu.

Sections 4.3.7.1 through 4.3.7.11 describe the Modify PC CommunicationsParameters options.

4.3.7.1 Communication Port. Select option 1 and press the Enter key, then type the PCserial communications-port number (1, 2, 3, or 4) used to connect the CDR PC withthe voice processor.

4.3.7.2 Communication Speed (Baud). Select option 2 and press the Enter key, thenenter the appropriate communications speed, either 1200 or 9600 baud, used totransmit data from the voice processor to the PC. The PC and voice processorbaud rates must match. If the baud rate designated in this option does not matchthe baud rate of the voice processor, change one to match the other. If a directconnection with the voice processor or a 9600-baud modem is used, select 9600baud. Otherwise, choose 1200 baud.

4.3.7.3 Connection Type. Specify the type of connection to the voice processor in option 3of the Modify PC Communications Parameter Menu (Figure 4-9). Select option 3and enter d for a direct connection or m for a modem connection.

SECTION 4.3

SOFTWARE ATTRIBUTES


4.3.7.4 Modem Initialization String. Select option 4 and press the Enter key, then typethe character string that initializes the modem before the telephone number isdialed. Enter up to 20 characters. Specific values depend on the type of modeminstalled. Consult the modem manual for the proper codes. The following charactershave special meanings in this field and also apply to the dial prefix and suffixparameters:

Insert a carriage return.

Delay 1 second.

The caret and the character following the caretare interpreted as a single control character.

~^

|

4.3.7.5 Dial Prefix String. Select option 5 and press the Enter key, then enter the dialprefix string, up to 20 characters long, that precedes the number dialed. Thespecific value in this field depends on the modem installed. Consult the modemmanual for the proper codes.

4.3.7.6 VPMOD Telephone Number. Select option 6 and press the Enter key, then enterthe voice processor access telephone number. The telephone number entered inoption 6 is the telephone number that is dialed through a modem in the PC. Thetelephone number allows access to the voice processor through the system-manag-er port. Do not enter a value in this field if the PC is connected directly to thesystem-manager port.

4.3.7.7 Dial Suffix String. Select option 7 and press the Enter key, then enter a characterstring, up to 20 characters long, that is transmitted after the telephone number isdialed. Specific requirements vary with the particular modem. Consult the modemmanual for the proper codes.

4.3.7.8 Terminal Emulation Type. Select option 8 and press the Enter key, then specifythe type of terminal emulation used for communication between the PC and thevoice processor. Leave the default at WY50SPEC or type VT100, if appropriate. Do not change this parameter to any terminal type other than WY50SPEC orVT100 without explicit instructions from an Octel or distributor serviceengineer.

4.3.7.9 VPMOD System Type. Select option 9 and press the Enter key, then select thetype of voice processor used for this particular CDR system. The following choicesare available:

1 – Branch XP2 – Branch3 – Aspen4 – Maxum5 – Sierra

If the Maxum SE and Octel XC1000 are not specifically indicated on the list ofvoice-processor types, select option 4 for the Maxum SE or select option 5 for theOctel XC1000. The voice-processor type MUST be correct for proper operation.

SECTION 4.3

SOFTWARE ATTRIBUTES


4.3.7.10 VPMOD Software Version Number. Select option 10 and press the Enter key, thenspecify the voice-processor software-version number, as shown in system managermenu 13.4. Type the proper numerical value in the form of x.xx (for example, 1.50).The software revision MUST be correct for proper operation.

4.3.7.11 VPMOD System Password. Select option 11 and press the Enter key. Type thesame password that is required to access the voice processor. For security reasons,the password value does not show on the screen; instead, a series of Xs appears,one for each digit in the password code. Once an entry is made in this field, itwill be required for access to the Octel PC/CDR menus. The voice-processorpassword is required to allow the PC to link with the voice processor and for testingthe communication link between the PC and the voice processor, as described insection 4.4. A password is also required if the automatic-scheduling method ofprocessing is used.

When the system-manager access password to the voice processor is changed, theentry in this field must also be changed or access to the voice processor is denied.

4.3.8 Modify Next Block To Download by Automatic Octel PC/CDRProcessing

Change the entry in the Next Block to Download by Automatic Octel PC/CDRProcessing field (option 8 on Figure 4-5) only if the next block to be downloadeddiffers from the default entry. Normally, CDR buffer blocks need to be downloadedonly once. However, if a BCF is deleted from the PC before it is collated, the BCFmust be downloaded again and a previously downloaded block (or series of blocks)must be requested. If CDR buffer blocks must be downloaded to the PC again,change the download block counter number to reflect the new number. The CDFsare appended to include calls from the latest download. Refer to Chapter Two foradditional information about the CDR buffer.

Perform the following steps to specify the first block number to be downloaded:

1. Refer to Figure 4-5, select option 8, and press the Enter key to change thedownload counter. Figure 4-10 shows the Octel PC/CDR System AttributesMenu with an additional prompt at the bottom of the screen.


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) 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 Processing 12349 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 VPMOD’s Next Default Block NumberBlock Number? :

Figure 4-10. Octel PC/CDR System Attributes Menu for NextBlock to Download Option.

SECTION 4.3

SOFTWARE ATTRIBUTES


2. Type the number of the first block to be downloaded in the Block Number:?field at the bottom of the screen. Press the Enter key. The new block numbernow shows in the Current Setting column next to the Next Block toDownload by Automatic Octel PC/CDR Processing field.

To cancel the change, press the Esc key. The Octel PC/CDR SystemAttributes Menu without the additional prompts (Figure 4-5) reappears.

4.3.9 Modify Output File Format Level

Option 9 of the Octel PC/CDR System Attributes Menu (Figure 4-5) displays thefile-format level to be used for processed files. There are two formats available. Theonly difference between level one and level two is that some of the fields in leveltwo allow more digits to be entered than some of the fields in level one. Refer toAppendix A to identify the affected fields.

1. Refer to Figure 4-5, select option 9, and press the Enter key to change thefile-format level. A prompt requesting the file-format level appears at the bottomof the Octel PC/CDR System Attributes Menu, as shown in Figure 4-11.


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) 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): 9

Set CDR output file format level (1–2):

Figure 4-11. Octel PC/CDR System Attributes Menu for ModifyOutput Format File Level Option.

2. Enter the number for the desired file-format level and press the Enter key.

3. Type 0 and press the Enter key to return to the Octel PC/CDR System Menu(Figure 4-4). A message appears that the system parameters have beensaved.

If inappropriate parameters are entered, press the Esc key to return to the OctelPC/CDR System Menu, and the new system attributes will not be saved.

4.4 TEST THE DIRECT CONNECTION BETWEEN THE PC ANDTHE VOICE PROCESSOR

Connect the PC to the voice processor using the SMT cable and connectors, asshown in section 1.4, Figure 1-2 or Figure 1-3. Perform the following steps to test

SECTION 4.3 – 4.4

SOFTWARE ATTRIBUTES


the communication parameters and hardware connections and to use the CDR PCas a system-manager terminal:

1. At the DOS prompt on the PC, type a CDR system name as established insection 3.4; for example, westreg. Press the Enter key.

2. If a password has been established (section 4.3.7.11), it is requested now.Type the password and press the Enter key, or if the password has not beenestablished, press the Enter key to continue. The Octel PC/CDR SystemMenu (Figure 4-4) appears.

3. Select option 5 and press the Enter key. Menus and prompts appear andscroll off the screen as the PC and voice processor are linked.

4. If the password was not required in step 2, it is requested now. Type thepassword for the voice processor that is being accessed at the Please EnterSystem Manager Password: prompt and press the Enter key.

If the voice processor is operating and the link is properly established, theSMT Main Menu appears as the PC emulates the functions of the system-manager terminal. The status line at the bottom of the screen applies to theMIRROR II software.

If the link is not properly established, refer to section 4.3.7 and check thePC/CDR communications parameters, especially the communication port andbaud rate. Also refer to section 1.4.1 and check the cables and connectors.

Once the voice processor is properly connected to the PC and the SMT Main Menuis displayed, system-management functions can be performed from the PC terminaland keyboard.

When SMT menus are accessed from the PC, most SMTfunctions can be performed. Because critical menu entries can bealtered at this time, secure the CDR PC in the same manner asthe original SMT.

Caution!

The following system-manager functions cannot be performed from the PC:

Rebooting the voice-processor

Accessing menu 16 from more than one terminal (SMT or PC) at a time

Setting the date and time functions

Shutting down the voice processor

Do not perform a voice processor shutdown from the PC. Thebaud rate could change and status log entries could be lost.

Caution!

SECTION 4.4

SOFTWARE ATTRIBUTES


Because the MIRROR II software program emulates the SMT, the function keys, theBreak key, and the Esc key can be used for Wyse 50 functions. Refer to Table4-1 for keyboard equivalents that are effective when the SMT is accessed throughthe MIRROR II software program.

Table 4-1. Special-Emulation Function Keys.

Same (except F3, F4, F6a)

a F3 = Opens the MIRROR II command line F4 = Displays MIRROR II status screenF6 = Disconnects and returns to Octel PC/CDR

SMTTerminal Keys

WY50SPECEmulation Keys on PC

AlphabeticalNumericalFunctionBreakPrint SendShift + Print Send

SameSame

EscapePage DownPrint Screen

If while emulating the SMT the screen times out and darkens, press the Enter keyand reenter the password as prompted.

To return to the Octel PC/CDR menus, press the F6 key to disconnect the linkbetween the PC and the voice processor. Menus and prompts scroll off the screenas it returns to the Octel PC/CDR System Menu. Type 0 and press the Enter keyto exit to the DOS prompt.

4.5 HIGHLIGHTS

The Octel PC/CDR software must be properly configured before processingCDR data.

The proper communication parameters must be established between the PCand the voice processor before attempting to download.

BCFs should not be saved; they take up too much disk space.

The output-file format should be compatible with the customer-developedapplications database.

The communication link between the voice processor and the PC must betested before data is downloaded.

SECTION 4.4 – 4.5

5

CARBON COPY PLUSPROCEDURES


CHAPTER FIVECONTENTS

5.1 OVERVIEW 5-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.2 CONFIGURING CARBON COPY PLUS 5-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.2.1 Comm Port Address 5-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.2.2 Baud Rate 5-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.2.3 Modem Type 5-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.2.4 Password Table 5-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.3 CHANGING CARBON COPY PLUS PARAMETERS 5-3. . . . . . . . . . . . . . . . . . . . .

5.4 USING CARBON COPY PLUS 5-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.4.1 Responsibilities of the System Manager 5-5. . . . . . . . . . . . . . . . . . . . . . . . .

5.4.2 Responsibilities of the Service Representative 5-5. . . . . . . . . . . . . . . . . . .

5.4.3 Responsibilities of Both the System Manager and Service Representative 5-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.5 DISABLING CARBON COPY PLUS 5-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.6 HIGHLIGHTS 5-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section Page


FIGURES

Figure 5-1. Carbon Copy PLUS System Parameters Menu 5-2. . . . . . . . . . . . . . . . .

Figure 5-2. Available Modem Types Menu 5-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 5-3. Password Table Menu 5-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 5-4. Carbon Copy PLUS Customer-Dialogue Screen 5-5. . . . . . . . . . . . . . . . .

Figure 5-5. Carbon Copy PLUS Service-Dialogue Screen 5-6. . . . . . . . . . . . . . . . . . .

Page

5


CARBON COPY PLUS PROCEDURES

5.1 OVERVIEW

The Octel PC/CDR software package includes a version of Carbon Copy PLUSsoftware that provides additional service capabilities. Carbon Copy PLUS is amemory-resident program that allows a remotely located PC to be connected to theCDR PC through a modem. Carbon Copy PLUS is used only when a remoteconnection is necessary for system maintenance.

Carbon Copy PLUS requires the following:

At least 540K of PC memory

A separate service modem

Two communication ports (one for the service modem and the other for thelink to the voice processor).

5.2 CONFIGURING CARBON COPY PLUS

The Carbon Copy PLUS software program is loaded into the PC when the OctelPC/CDR software is installed. Carbon Copy PLUS must be configured to meet therequirements of the particular voice processor and modem before it is used.

Carbon Copy PLUS requires an internal or external modem. When using an externalmodem, the PC must be equipped with at least two serial communication ports (namedCOM1and COM2). One of the communication ports is used to communicate with thevoice processor; a different communication port is used for connection with the externalmodems. An internal modem appears to the PC as a serial port, with the same namingconvention (COM1 and COM2). If both MIRROR II and Carbon Copy PLUS areinstalled, make sure that each is configured with its own communication port.

Perform the following steps to configure Carbon Copy PLUS:

1. Type cd\octelcdr\cc at the DOS prompt and press the Enter key to enter the\OCTELCDR\CC subdirectory.

2. Type ccinstal at the DOS prompt and press the Enter key to run theCCINSTAL.EXE program. A screen similar to Figure 5-1 appears.

3. Make Carbon Copy PLUS changes by selecting the letter or number desig-nated for a specific parameter. The default parameters for Carbon Copy PLUSare selected at the Octel factory. Verify all parameters and adjust as neces-sary, paying particular attention to options A, B, C, and 4.

4. When all of the necessary changes have been made to the Carbon CopyPLUS System Parameters menu, press X to save the changes and exit. Toexit without saving changes, press Q to quit and then press Y for yes.

For details about Carbon Copy PLUS parameters, refer to sections 5.2.1 through 5.2.4.



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 5-1. Carbon Copy PLUS System Parameters Menu.

5.2.1 Comm Port Address

Select A to change the entry in the Comm Port Address field. Each time A ispressed, a new comm-port-address setting is displayed. Continue to press A untilthe desired setting appears.

If the setting Other is required, contact the local Octel or distributor servicerepresentative for assistance in completing this field.

5.2.2 Baud Rate

To change the baud rate, select B. Each time B is pressed, a new baud rate settingis displayed. Continue to press B until the desired setting appears. The baud rate inthis field must match the baud rate of the modem at the Octel or distributor supportoffice.

5.2.3 Modem Type

Select C to change the modem type if the entry in this field does not match theinstalled modem. The Available Modem Types menu appears, as shown inFigure 5-2.

The modem used for Carbon Copy PLUS must be compatible with the modem usedby the local Octel or distributor support office. Use the arrow keys to move thehighlighted cursor to the installed modem and press the Enter key. If the desiredmodem is not available, select the UK “AT” Compatible modem listed in the upperleft corner of the screen.

SECTION 5.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 5-2. Available Modem Types Menu.

5.2.4 Password Table

To access a customer’s PC from a remote location, the Octel or distributor servicerepresentative must enter a password. The format of the password used by the fieldservice engineer must match the format of the customer’s password. Modify thepassword table only if requested to do so by an Octel or distributor servicerepresentative. Perform the following steps if it is necessary to modify the passwordtable:

1. From the Carbon Copy PLUS System Parameter menu (Figure 5-1), press 4.The PASSWORD TABLE appears, similar to the screen shown in Figure 5-3.

2. Use the function keys to modify the password table and update it as neces-sary. Function-key descriptions are displayed on the screen.

3. Press the Enter key to save new data entered in a field.

4. Press F10 to return to the Carbon Copy PLUS System Parameters menu.

If a service representative is using Carbon Copy PLUS, Version 5.0, and thecustomer is using Carbon Copy PLUS, Version 4.0, the passwords do not match.For these two versions of Carbon Copy PLUS to communicate with each other, thepasswords must contain an initial alphabet character.

5.3 CHANGING CARBON COPY PLUS PARAMETERS

When changes are required to the Carbon Copy PLUS configuration parameters,follow the configuration instructions in section 5.2 and modify as needed.

SECTION 5.2 – 5.3



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 Password

F6 –– Special Phone Characters F9 –– Help

F10 – Exit to Main Menu

Password Callback Phone Number Password options

CC CCDOS :STD Keybd

PASSWORD TABLE

Figure 5-3. Password Table Menu.

5.4 USING CARBON COPY PLUS

Carbon Copy PLUS is used only when a remote connection from the PC to amodem at an Octel or distributor support office is necessary for system mainte-nance. Run Carbon Copy PLUS software only when directed to do so by an Octelor distributor service representative. Carbon Copy PLUS requires main memory(RAM) that could be used for Octel PC/CDR.

Perform the following steps to load the Carbon Copy PLUS software into memory:

1. Make sure that the modem is properly connected to a telephone line. If themodem is connected externally to the PC, make sure it is plugged in andpower is on.

2. Type cd\octelcdr\cc at the DOS prompt to enter the \OCTELCDR\CCsubdirectory. Press the Enter key.

3. Type cc at the DOS prompt and press the Enter key. The Carbon Copy PLUSintroduction screen is displayed. The last prompt on the screen now reads asfollows:

Carbon Copy is now installed. Press <ALT><RIGHT–SHIFT> forMenus .

The DOS prompt reappears on the screen.

4. At the DOS prompt, type cdr to begin the Octel PC/CDR application. Pressthe Enter key.

5. If Carbon Copy PLUS menus are desired while within the Octel PC/CDRapplication, press the Alt key and the right Shift key simultaneously.

SECTION 5.3 – 5.4



6. Return to the application from the Carbon Copy PLUS menu by pressing theEsc or F10 key.

For system maintenance, the Octel or distributor support offices use a remote PC toaccess the CDR PC. All calls to the CDR PC are initiated by an Octel or distributorservice representative.

5.4.1 Responsibilities of the System Manager

Perform the following steps to allow remote access to the CDR PC by an Octel ordistributor support representative:

1. If Carbon Copy PLUS has not already been configured, follow the steps insection 5.2.

2. Refer to section 5.4 to load Carbon Copy PLUS into memory.

3. Press the Alt key and the right Shift key simultaneously. The Carbon CopyPLUS dialogue screen appears, similar to the screen shown in Figure 5-4.

Your Dia-logue

Remote Operator’s Dialogue

Carbon Copy (CC V5.1)Microcom, Inc.

Licensed to:OCTEL Communications

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 5-4. Carbon Copy PLUS Customer-Dialogue Screen.

5.4.2 Responsibilities of the Service Representative

The service representative must have a special master version of the Carbon CopyPLUS software program to be able to access the CDR PC for remote maintenance.If it is necessary to update the parameters of the master Carbon Copy PLUSsoftware on the service PC, the service representative types ccinstal at the DOSprompt from the master-version subdirectory of the Carbon Copy PLUS software.

SECTION 5.4



From a PC using the master version of Carbon Copy PLUS, perform the followingsteps for remote access to the CDR PC:

1. Type cchelp from the DOS subdirectory that contains the master CarbonCopy PLUS software and press the Enter key. A screen similar to Figure 5-5appears.

Your Dia-logue

Remote Operator’s Dialogue

Carbon Copy (CCHELP V5.0)Meridian Technology, Inc.

Serial #: XXXXXXXX Licensed to:OCTEL COMMUNICATIONS

NO Data Link EstablishedAuto–Answer is not EnabledPrinter Assigned to: CCSpl File: ––NONE––

Time 08:30:50

[F1] Call CC User

[F3] Capture Screen / Session

[F4] Review/Replay Captured Image

[F6] Printer / Log / DOS Control

[F7] Terminal Emulation

[F8] Data Link Maintenance

[F10] Return to Application

Figure 5-5. Carbon Copy PLUS Service-Dialogue Screen.

2. Press the F1 key to call the customer. A window appears showing a list oftelephone numbers or office locations.

3. Select the location by using the arrow keys to move the highlighted cursor ortype the appropriate access telephone number. Press the Enter key.

5.4.3 Responsibilities of Both the System Manager and ServiceRepresentative

When the steps in sections 5.4.1 and 5.4.2 are performed, the connection is made.Instructions and responses can be passed back and forth between the systemmanager and the service representative by typing them on the screen (Figure 5-5).

To access the system manager’s Octel PC/CDR application or DOS prompt, thecustomer or service representative presses the F10 key and proceeds as directed.The service representative then views the application on the CDR PC. All promptsare shown on both monitors, regardless of who types the prompts.

To return to the dialogue screen, the customer or service representative presses theAlt key and the right Shift key simultaneously.

SECTION 5.4



5.5 DISABLING CARBON COPY PLUS

Carbon Copy PLUS can be disabled without having to reboot the PC. DisablingCarbon Copy PLUS removes the RAM resident program from the PC systemmemory.

Perform the following steps to disable Carbon Copy PLUS:

1. Type cd\octelcdr\cc at the DOS prompt to enter the \OCTELCDR\CCsubdirectory. Press the Enter key.

2. Type ccremove at the DOS prompt. Press the Enter key.

3. Press Y to remove Carbon Copy PLUS.

5.6 HIGHLIGHTS

The Carbon Copy PLUS software program is used for remote systemmaintenance by Octel or distributor service representatives.

Carbon Copy PLUS is a memory-resident program; therefore, it should bedisabled when not in use.

Calls to the CDR PC through Carbon Copy PLUS are initiated by an Octel ordistributor service representative.

SECTION 5.5 – 5.6

6

PROCESSINGMETHODS


CHAPTER SIXCONTENTS

6.1 OVERVIEW 6-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.2 USING MANUAL PROCESSING 6-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.2.1 Download Octel PC/CDR Data 6-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.2.2 Collate BCFs Into CDFs 6-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.2.3 Generate Output Files 6-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2.3.1 Session-Detail-Output (SDO) File-Processing Screen 6-8. . . . . 6.2.3.2 Unsuccessful-Transfer-Output (UTO) File-Processing

Screen 6-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2.3.3 Message-Detail Output (MDO) File-Processing Screen 6-10. . 6.2.3.4 Individual-Port-Statistics Output (PSO) File-Processing

Screen 6-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2.3.5 Forms-Output (FDO) File-Processing Screen 6-12. . . . . . . . . . .

6.3 USING AUTOMATIC PROCESSING 6-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.4 USING SCHEDULED AUTOMATIC PROCESSING 6-15. . . . . . . . . . . . . . . . . . . . .

6.4.1 Update Automatic Processing Schedules 6-16. . . . . . . . . . . . . . . . . . . . . . . 6.4.1.1 Add a New Schedule 6-16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.4.1.2 Edit an Existing Schedule 6-19. . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.4.1.3 Remove and Existing Schedule 6-19. . . . . . . . . . . . . . . . . . . . . . . 6.4.1.4 List Existing Schedules 6-19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.4.1.5 Print Existing Schedules 6-20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.4.1.6 Backup Schedule Parameter File 6-20. . . . . . . . . . . . . . . . . . . . . . 6.4.1.7 Restore Schedule Parameter File 6-21. . . . . . . . . . . . . . . . . . . . .

6.4.2 Start Automatic Scheduler Mode 6-22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.4.3 Update Schedule Password 6-23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.4.4 Update Automatic Scheduler Log Files 6-24. . . . . . . . . . . . . . . . . . . . . . . . . 6.4.4.1 List Schedule Log File 6-24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.4.4.2 Print Schedule Log File 6-25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.4.4.3 Backup Schedule Log File 6-25. . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.4.4.4 Restore Schedule Log File 6-26. . . . . . . . . . . . . . . . . . . . . . . . . . . 6.4.4.5 Erase Schedule Log File 6-27. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.5 USING THE SERVICE-LEVEL DOWNLOAD 6-27. . . . . . . . . . . . . . . . . . . . . . . . . . .

6.6 HIGHLIGHTS 6-30. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section Page


FIGURES

Figure 6-1. CDR Block Retrieval Transfer Screen 6-2. . . . . . . . . . . . . . . . . . . . . . . . . .


Figure 6-3. Manual Octel PC/CDR Processing Menu 6-3. . . . . . . . . . . . . . . . . . . . . . .

Figure 6-4. Octel PC/CDR File Download Settings Menu 6-4. . . . . . . . . . . . . . . . . . .

Figure 6-5. Manual-Collation Processing Screen 6-5. . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 6-6. Octel PC/CDR Output File Generation Menu 6-7. . . . . . . . . . . . . . . . . . .

Figure 6-7. Initial-Session-Detail Output-File-Processing Screen 6-7. . . . . . . . . . . . .

Figure 6-8. Session-Detail-Output File-Processing Screen After Files AreGenerated 6-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 6-9. Unsuccessful-Transfer-Output File-Processing Screen 6-9. . . . . . . . . . .

Figure 6-10. Message-Detail-Output File-Processing Screen 6-10. . . . . . . . . . . . . . . . .

Figure 6-11. Individual-Port-Statistics Output File-Processing Screen 6-11. . . . . . . . . .

Figure 6-12. Forms File-Processing Screen 6-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 6-13. Octel PC/CDR System Attributes Menu 6-13. . . . . . . . . . . . . . . . . . . . . . .

Figure 6-14. Modify Automatic Output File Generation Menu 6-13. . . . . . . . . . . . . . . .

Figure 6-15. Octel PC/CDR Main Menu 6-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 6-16. Octel PC/CDR Automatic Schedule Menu 6-16. . . . . . . . . . . . . . . . . . . . .

Figure 6-17. Octel PC/CDR Update Automatic Processing Schedules Menu 6-17. .

Figure 6-18. Automatic Octel PC/CDR Schedule Editor Menu 6-17. . . . . . . . . . . . . . .

Figure 6-19. Automatic Octel PC/CDR Schedule List 6-20. . . . . . . . . . . . . . . . . . . . . . .

Figure 6-20. Octel PC/CDR Processing Schedule Screen With Timer Running 6-23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 6-21. Octel PC/CDR Update Automatic Scheduler Log File Menu 6-24. . . . .

Figure 6-22. Example of a Displayed Schedule-Log File 6-25. . . . . . . . . . . . . . . . . . . .

Figure 6-23. SMT Menu 16.1.2, Database Access, Retrieve Call Detail Records 6-28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 6-24. SMT Menu 16.1.2, Database Access, Retrieve Call Detail Records, Showing Command Line 6-29. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 6-25. Octel PC/CDR Block Retrieval Transfer Screen 6-29. . . . . . . . . . . . . . . .

Page

6


PROCESSING METHODS

6.1 OVERVIEW

The Octel PC/CDR package offers the following four methods for downloading andprocessing CDR data:

Manual

Automatic

Scheduled automatic

Service-level download

The following processing steps are performed within each of the first threedownloading methods:

1. The PC is linked with the voice processor and Octel PC/CDR data isdownloaded into binary collection files.

2. The binary-collection files are collated.

3. Output files are generated.

The service-level download is used primarily by Octel and distributor servicerepresentatives for downloading specific data blocks. These files are then processedusing the manual method.

After output files are generated, they are viewed or printed through the OctelPC/CDR File Utilities menu, or they are imported into a database-applicationsprogram for sorting and formatting. Collated day files are viewed, searched, andprinted through the Service Utilities menu, described in Chapter Seven.

Establish the connection between the PC and the voice processor before down-loading and processing the Octel PC/CDR event records. Make sure that the PCcable is connected to the proper port on the voice-processor scanner board. Referto Figure 1-2 or 1-3 to verify the proper connection.

Check the Display Disk Status menu, reached from the Octel Octel PC/CDR FileUtilities Menu, before downloading data from the CDR buffer. Use the menu todetermine whether there is enough available disk-storage space on the PC harddisk for the downloaded data. (Refer to section 7.2.1 for more information about thismenu.) If the PC is about to run out of storage space while downloading data fromthe CDR buffer, the following prompt appears:

Less than 100 kbytes remaining on disk.

Shutting down as a precaution.

Last block processed: XXXXX

If this prompt appears, create more storage space on the PC disk by deletingunnecessary files or by installing a larger or additional hard disk before continuingwith the download.

PROCESSING METHODS


Refer to section 1.2 for additional steps to be performed before beginning thedownload process. Refer to Appendix E to interpret transmission messages thatmight occur while downloading data.

6.2 USING MANUAL PROCESSING

The manual-processing method uses each of the three processing steps individually.Use this method to become familiar with the processing steps and when setting upa new voice processor for downloading. With this method, each step is selectedand performed sequentially. Once the manual-processing method is familiar and theprocess is working properly, establish and use the automatic method. The automaticmethod performs processing in the same sequence as the manual method, butdoes not require user input for each step.

The Octel PC/CDR software package uses MIRROR II software to provide thecommunication link between the PC and the voice processor. The software transfersdata using the XMODEM file transfer protocol and the data-transfer-verificationmethod with the cyclical-redundancy-check (CRC) calculation.

While CDR data is downloading, the PC screen displays the number of blocks beingdownloaded on a screen similar to the one shown in Figure 6-1. These transmissionblocks differ in size from the CDR blocks stored in the CDR buffer in the voiceprocessor. Each block counted on this screen contains 128 bytes of data instead ofthe 2048 bytes stored within each CDR block in the buffer. Regardless of thenumber of the first block to be downloaded, the Block # column on the file-transferscreen begins counting with 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. Because each2048-byte CDR block is actually downloaded in 128-byte increments (2048/16),when the download is complete, the entry in the Block # column shows thatapproximately 2400 blocks (16 x 150) were downloaded.

Begin file transfer . .

Receiving C:\westreg\bcf\A920305A.BCF – using CRC

Block # % Complete Consec.errors Total errors

2400 –– none 1

Figure 6-1. CDR Block Retrieval Transfer Screen.

Data transmission is verified using the CRC calculation method. If a transmissiondiscrepancy occurs, the counter in the Total errors column is incremented, and theOctel PC/CDR software then instructs the voice processor to send the entire trans-mission block again. If the discrepancy occurs again, the counter in the Consec.errors column is incremented. Because the Octel PC/CDR software must receiveaccurate data blocks before continuing the process is aborted after 10 unsuccessfulattempts and the screen is returned to the CDR program.

SECTION 6.1 – 6.2

PROCESSING METHODS


The status of the CDR buffer before the download (as shown in SMT menu 16.1.1)is recorded in the log file. During the downloading process, the voice processormight display transmission messages on the PC screen. These messages are listedand explained in Appendix E.

6.2.1 Download Octel PC/CDR Data

To download Octel PC/CDR data manually, perform the following steps:

1. From the DOS prompt on the PC, type a valid CDR system name or cdr andpress the Enter key. (Refer to section 4.2 for additional instructions aboutaccessing the Octel PC/CDR System Menu.) The Octel PC/CDR SystemMenu appears, similar to the screen shown in Figure 6-2.


0 Exit


Enter Option:


2. Select option 2 from the Octel PC/CDR System Menu (Figure 6-2) and pressthe Enter key. A screen similar to Figure 6-3 appears. The options listed onthe Manual Octel PC/CDR Processing Menu are also the steps required toprocess CDR.

Manual Octel PC/CDR Processing Menu westreg

0 Return to System Menu

1 Link with VPMOD and Download Octel PC/CDR Data2 Collate Octel PC/CDR Binary Collection Files from VPMOD3 Generate Octel PC/CDR Output Files

Enter Option:

Figure 6-3. Manual Octel PC/CDR Processing Menu.

3. Select option 1 from the Manual Octel PC/CDR Processing Menu (Figure 6-3)and press the Enter key. A screen similar to Figure 6-4 appears.

SECTION 6.2

PROCESSING METHODS


Octel PC/CDR File Download Settings westreg

0 Proceed to Download (ESC to Return)

Current Setting1 Binary Collection File Name A920220A.BCF2 First Block Number to Download 17263 Number of Blocks to Download

Enter Option:

Figure 6-4. Octel PC/CDR File Download Settings Menu.

4. The next available BCF (binary collection file) name is automatically assignedand shows in the Current Setting column for option 1. BCFs are processed inascending file-name order and are stored in the BCF subdirectory. Modify thisfile name only if this BCF must be processed in a different sequence thanother existing BCFs in the BCF subdirectory. To modify this name, selectoption 1 and press the Enter key. Type in the new name and press the Enterkey again.

5. Modify the entry in the Current Setting column for option 2 only if blocks thatwere previously retrieved must be downloaded again. If this field is notchanged, the Octel PC/CDR software defaults to the block number of the firstblock in a sequence that has not already been downloaded.

The entry in this field must either be the number of a previously downloadedblock or the first block in a sequence that has not already been downloaded.If not, the download will fail. For example,

If blocks 1116 through 2242 have not been downloaded, a downloadcannot begin at block 2000. It must start at block 1116, or it must startwith a previously downloaded block.

Select option 2 and press the Enter key to specify the first block number todownload. Type the block number in the Current Setting column and pressthe Enter key again.

6. Select option 3 to specify the total number of blocks to retrieve. To downloadall blocks starting from the block number indicated in option 2, leave theCurrent Setting column blank for option 3. To download a specific number ofblocks, select option 3 and press the Enter key. Type in the number of blocksto retrieve and press the Enter key again.

If all blocks that have not been downloaded are requested, the block currentlybeing filled by the voice processor is also downloaded. The voice processorbegins filling a new block when the download is started. It does not return tofill the partially filled block.

7. Select 0 and press the Enter key to begin the CDR-data download. Type thesystem-manager password, if requested, and press the Enter key. (Thepassword is requested at this point if it was not established earlier in the OctelPC/CDR System Attributes Menu.) Various Octel PC/CDR and SMT menusappear on the screen as the PC performs the download. No action isnecessary until the download has been completed, and the prompt PressENTER/RETURN to continue. appears at the bottom of the screen.

If a download is not desired, press the Esc key to exit to the Octel PC/CDRSystem Menu (Figure 6-2).

SECTION 6.2

PROCESSING METHODS


8. When the blocks of data have been successfully transferred to the PC harddisk, the block number field stops incrementing and the message RetrievalComplete is displayed briefly at the bottom of the screen. When the summaryshowing the retrieved blocks and BCF file name appears, press the Enter keyto return to the Manual Octel PC/CDR Processing Menu (Figure 6-3).

6.2.2 Collate BCFs Into CDFs

The CDR data downloaded from the voice processor into binary-collection files(BCFs) must be collated into collated day files (CDFs) before CDR output files canbe created. The collation process sorts the BCF call-event records into separategroups of events associated with each call on each port. This process creates orappends already existing CDFs with the call events contained in the BCF sourcefiles. One CDF is created for every date that call events existed in the BCF. BCFsand CDFs are described in section 1.7.

To collate BCFs into CDFs, perform the following steps:

1. Select option 2 from the Manual Octel PC/CDR Processing Menu (Figure 6-3)and press the Enter key. The PC searches the CDR system subdirectory forBCFs that have not been collated and displays their file names. It also findsthe COLLATE.PSF file in the SYS subdirectory and includes it with the BCF tocreate the new CDF. (Pending-state files, PSFs, are described in section1.7.4.) A screen similar to the first three lines of Figure 6-5 appears.

Begin Collate ProcessingFound 2 Octel PC/CDR Binary Collection File(s):

A920222B A920223AProceed with the Collation of these Files? (y/n): Y

>>03–05–92 10:31:34 Collating CDR Files>>System: westreg

CDR Input File Creation System CDR Total Events Calls

File Name Date & Time ID # Blocks Events Rejected Passed

A920222B.BCF 02–22–92 1249 955–1054 1166 6 498A920223A.BCF 02–23–92 09:57:00 1054–1454 44380 0 86581249

Waiting to return to menu.Press ENTER/RETURN to continue.

10:29:16

Figure 6-5. Manual-Collation Processing Screen.

2. Press Y and the Enter key to begin collating.

During collation, a screen similar to Figure 6-5 develops. The processcontinues until all BCFs are collated. The BCF file name, creation date, andother summary information appears on the screen as each file is prepared forcollation.

SECTION 6.2

PROCESSING METHODS


If BCFs are collated from blocks that have been previously downloaded andcollated, a message similar to the following appears:

******************************************************************************* 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):

Press Y to skip the overlapping blocks. Press N to return the Manual OctelPC/CDR Processing Menu (Figure 6-3) to the screen.

For example,

Blocks 0 through 100 are downloaded and collated on July 26. On July 30, blocks 50 through 150 are downloaded. The preceding errormessage appears when the collate BCF option is selected. The Do you wish to skip overlapping blocks? question asks whether thepreviously collated blocks (blocks numbered from 50 through 100)should be skipped, because they have already been processed intoCDFs. Press Y to collate the new blocks only.

The collation is complete when the following prompt appears:

Waiting to return to menu. Press Enter to continue.

3. Press the Enter key to return to the Manual Octel PC/CDR Processing Menu(Figure 6-3).

After the BCFs have been collated, the final collation-data summary, similar to thedata shown in Figure 6-5, is added to the log file (in the SYS subdirectory) and canbe viewed or printed (refer to section 7.2.3).

The columns in the manual-collation processing screen (similar to Figure 6-5) showthe following CDR collation statistics:

CDR Input File Name. This column lists the BCF names as they are prepared forcollation.

File Creation Date & Time. These columns list the date and time when the BCFfiles were created. Numbers in the other columns are incremented while theBCFs are being collated.

System ID #. The voice-processor serial numbers are listed in this column. Thesenumbers are important if data from multiple voice processors is processed bythe same PC.

CDR Blocks. The number of the beginning and ending CDR blocks contained ineach BCF is listed in this column.

Total Events. The number of accumulated events within each BCF is listed foreach file name.

Events Rejected. Individual events sometimes cannot be associated with calls.These events cannot be processed, because the voice processor has notrecorded a beginning for a call. This column might indicate several rejectedevents at the time Octel PC/CDR is installed; however, after CDR is running,no events should be rejected. If rejected events are logged, save the BCF (orPCF) file and contact the local Octel or distributor support office for assis-tance. Rejected events are documented in the log file.

Calls Passed. This column lists the total calls successfully collated and placed inCDFs.

SECTION 6.2

PROCESSING METHODS


6.2.3 Generate Output Files

Output files contain CDR events organized by subject. CDR events are collected inthe CDR buffer based on selections made in SMT menu 16.1.4 (section 2.5.2).Output files can only be generated for record types that were previously selected inthis menu. Generate only the output files containing the required information, so thatPC disk-storage space is not filled unnecessarily. Not all output files are needed forevery application.

To generate output files, perform the following steps:

1. Select option 3 from the Manual Octel PC/CDR Processing Menu (Figure 6-3)and press the Enter key. The Octel PC/CDR Output File Generation Menuappears, similar to Figure 6-6.

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 Files

10 Generate Forms Output File Records

Enter Option:

Figure 6-6. Octel PC/CDR Output File Generation Menu.

2. Type the option number for the desired output file and press the Enter key. Ascreen similar to the one shown in Figure 6-7 appears. All CDFs that have notbeen processed for the selected output files appear, beginning on the thirdline. For example,

To select the Generate Session Detail Output Files option, type 1from the Octel PC/CDR Output File Generation Menu and press theEnter key. All collated day files (CDFs) that have not been processedfor session-detail output files are displayed (Figure 6-7).

Begin Session Detail ProcessingFound 2 New or Updating Collated Day File(s):

CD920227 CD920228Do you wish to proceed making Session Detail files? (y/n): Y

Figure 6-7. Initial-Session-Detail Output-File-Processing Screen.

3. To process these files, press Y and the Enter key. A summary screen, similarto Figure 6-8, develops as the files are collated. The fields on this screenvary, depending on the output file selected. Refer to sections 6.2.3.1 through6.2.3.5 for information about the interpretation of output-file-summary screens.

If the files are not to be processed, press N to return to the Octel PC/CDROutput File Generation Menu (Figure 6-6).

SECTION 6.2

PROCESSING METHODS


Begin Session Detail ProcessingFound 2 New or Updated Collated Day File(s):

CD920227 CD920228Do you wish to proceed making Session Detail files? (y/n): Y

>>03–05–92 10:34:39 Collating Session Detail Output Files>>System: westreg, File Format: 7

CDF Input System CallsTotal Calls & SessionsCalls

File Date ID # IgnoredCalls PassedFailed

02–27–92 1249 498 0


Other

100

Messages

Sent & Deleted

398 750 911 1024

Unsuc

Xfers

3202–28–92 1249 8658 0 1775 6883 34721 23487 21059 177

Figure 6-8. Session-Detail-Output File-Processing Screen After Files Are Generated.

4. Press the Enter key to return to the Octel PC/CDR Output File GenerationMenu (Figure 6-6).

5. Repeat steps 2, 3, and 4 until all desired output files are generated.

6. Type 0 to return to the Manual Octel PC/CDR Processing Menu (Figure 6-3).

Output-file-processing screen summaries are described in sections 6.2.3.1 through6.2.3.5.

6.2.3.1 Session-Detail-Output (SDO) File-Processing Screen. One SDO file is created foreach day that calls are found in the source CDF. Each time the Generate SessionDetail Output Files option is executed, a new session-detail output file is created oran existing file for that same date is appended. Section 1.7.6.1 defines SDOs.

The columns on the SDO file-processing screen (Figure 6-8) function as follows:

CDF Input File Date. Several CDFs can be produced from a single BCF,depending on how often data is downloaded from the voice processor. TheCDF date is shown in this column.

System ID #. This column lists voice-processor serial numbers. These numbersare especially important if multiple voice processors are networked and theirdata processed by the same PC.

Total Calls. This column shows the total number of calls contained in the CDF.

Calls Failed. This column should always show zero. If it contains another number,contact the local Octel or distributor support office for assistance.

Other Calls Ignored. The entries in this column usually show single-event calls,such as message-waiting calls, that do not contain any length of time. Calls inthe SDO are commonly used for billing; single-event calls are system-relatedand are not normally used for billing. For in-band integrations, the voiceprocessor goes off-hook, sends the message-waiting indicator to the PBX,then goes on-hook. The numbers in this column can be very high, becausethey can occur up to three times per message-waiting signal. RS-232integrations use another method to send message-waiting signals; it is notreported here.

SECTION 6.2

PROCESSING METHODS


Calls & Sessions Passed. This column lists the number of calls and sessionsprocessed from the CDF and placed in the output file.

Messages Sent & Deleted. These columns show the total number of message-send events (MS), AMIS message-send events (AMIS_SEND), and message-delete (MD) events. These events are described in Appendix C.

Unsuc Xfers (unsuccessful transfers). This column lists the number of attempts totransfer from a mailbox to another telephone number. Unsuccessful transfersoccur occasionally when callers use an ECP mailbox or automated attendantor because of a busy or ring-no-answer condition.

6.2.3.2 Unsuccessful-Transfer-Output (UTO) File-Processing Screen. UTO files providedetails of each unsuccessful occurrence of a monitored transfer from an automatedattendant or ECP mailbox to a telephone number. Section 1.7.6.2 defines UTOs.

An output-processing summary screen similar to Figure 6-9 appears after UTO filesare successfully generated.

Begin Unsuccessful Transfer ProcessingFound 2 New or Updated Collated Day File(s):

CD920227 CD920228Do you wish to proceed making Unsuccessful Transfer Output? (y/n): Y

>>03–05–92 10:34:39 Creating Unsuccessful Transfer Output Files>>System: westreg, File Format: 7

CDF Input System Total Unsuccessful

File Date ID # Calls Transfers

02–27–92 1249 498 32


02–28–92 1249 8658 177

Figure 6-9. Unsuccessful-Transfer-Output File-Processing Screen.

The columns on the UTO file-processing screen (Figure 6-9) function as follows:


System ID #. This column lists the voice-processor serial numbers. Thesenumbers are important if multiple voice processors are networked and theirdata processed by the same PC.

Total Calls. This column shows the total number of calls contained in the CDF foreach CDF file date.

Unsuccessful Transfers. This column lists the number of attempts to transferfrom a mailbox to another telephone number. Unsuccessful transfers occuroccasionally when callers use an ECP mailbox or an automated attendant orbecause of a busy or ring-no-answer condition.

SECTION 6.2

PROCESSING METHODS


6.2.3.3 Message-Detail Output (MDO) File-Processing Screen. MDO files providedetailed records for each message sent or deleted by a subscriber in a mailbox.Section 1.7.6.3 defines MDOs.

An output-processing summary screen similar to Figure 6-10 appears after MDOfiles are successfully generated.

Begin Message Detail ProcessingFound 1 New or Updated Collated Day File(s):

CD920227 CD920228Do you wish to proceed making Message Detail files? (y/n): Y

>>03–05–92 10:34:39 Creating Message Detail Output Files>>System: westreg, File Format: 7

CDF Input System Total Records

File Date ID # Calls Created

02–27–92 1249 498 1935


Messages

Sent & Deleted

911 1024

Messages

Returned

002–28–92 1249 8658 44548 23487 21059 2

Figure 6-10. Message-Detail-Output File-Processing Screen.

The columns on the MDO file-processing screen (Figure 6-10) function as follows:



Total Calls. The total number of calls contained in the CDF are listed here foreach CDF file date.

Records Created. This column lists the total number of records contained in theoutput file, including messages sent, messages deleted, and messagesreturned to sender.

Messages Sent & Deleted. These columns show the total numbers of message-send events (MS), AMIS message-transmit events (AM_XMT_MINFO),message-delete events (MD), and OctelNet send-events (BN_XMT_VOICE andBN_XMT_CP). These events are described in Appendix C.

Messages Returned. This column lists the number of networked messages thatare returned to the originating mailbox and node. Messages could be returnedbecause the destination voice processor or mailbox is full.

6.2.3.4 Individual-Port-Statistics Output (PSO) File-Processing Screen. PSO filesprovide the number of calls and the time, in seconds, that each port is in use forevery 15-minute period of the day. Section 1.7.6.4 defines PSOs.

SECTION 6.2

PROCESSING METHODS


An output-processing summary screen similar to Figure 6-11 appears after PSO filesare successfully generated.

Begin Port Statistics ProcessingFound 2 New or Updated Collated Day File(s): CD911224 CD911226Do you wish to proceed making Port Statistics? (y/n): Y

>>12–27–91 20:52:14 Creating Individual Port Statistics Output Files>>System: westreg, File Format: 7

CDF Input System Total

File Date ID # Calls

12–24–91 1249 2658


Sys. Events

25

Calls

Passed

263312–26–91 1249 104 2 102

Ignored

Warning: For Data Above, No Previous Day File Available.

Figure 6-11. Individual-Port-Statistics Output File-Processing Screen.

If the prompt Warning: For Date Above, No Previous Day File Available.appears, it means there might be a missing CDF or that there was no CDR datagenerated the day before the last date noted. For example,

The warning message appears because there is no CDF dated 12-25-91.Because 12-25-91 was a holiday, it is possible no CDR data was generatedthat day. If the skipped date was a normal working day, contact your localOctel or distributor support office for assistance.

The columns on the PSO file-processing screen (Figure 6-11) function as follows:


System ID #. This column shows the voice-processor serial numbers. Thesenumbers are important if multiple voice processors are networked and theirdata processed by the same PC.

Total Calls. The total number of calls contained in the CDF are listed here foreach CDF file date.

Sys. Events Ignored (system events ignored). This column lists event recordsthat are not included in processing, such as Octel PC/CDR system-manager-event records that are recorded, but not included when calculating other portstatistics.

Calls Passed. This column lists the number of calls processed from the CDF andplaced in the output file.

SECTION 6.2

PROCESSING METHODS


6.2.3.5 Forms-Output (FDO) File-Processing Screen. Voice processors with the optionalDTMF OctelForms application package collect forms data in their CDR buffers. FDOfiles contain touch-tone responses from callers to DTMF OctelForms questions. Inaddition, they contain the port number, date, time, sequence, mailbox, and questionnumber. The output-file-generation process results in the creation of the DTMFOctelForms database file. If a file with this name already exists, the file is ap-pended; otherwise, it is created. Section 1.7.6.5 defines FDOs.

An output-processing summary screen similar to Figure 6-12 appears after the FDOfile is successfully appended.

Begin Forms File ProcessingFound 1 New or Updated Collated Day File(s):

CD920312Do you wish to proceed appending to Forms File? (y/n): Y

>>03–15–92 10:34:39 Writing to Forms Master Database>>System: westreg, File Format: 7

CDF Input System Total

File Date ID # Calls

03–12–92 8169 12


Forms

Calls

0

Figure 6-12. Forms File-Processing Screen.

The columns on the FDO file-processing screen (Figure 6-12) function as follows:



Total Calls. The number of DTMF OctelForms calls processed in the CDF is listed here. Additionally, system events (such as IPL, date, and time) and CDR configuration actions (such as changes to SMT menu 16.1.4 and voice-processor reboot) are included in this number.

Forms Calls. This column indicates only the number of DTMF OctelForms callsprocessed in the CDF. Unlike the Total Calls column, this does not includeother system-manager tasks.

6.3 USING AUTOMATIC PROCESSING

The automatic CDR-processing method downloads, collates, and generates outputfiles in one step. This method operates using PC system attributes set beforeautomatic processing is executed.

SECTION 6.2 – 6.3

PROCESSING METHODS


Before using the automatic-processing method, consider the following:

If the CDR system attributes have not been established, refer to section 4.3.

Options 1, 2, 3, 4, 6, and 7 of the Octel PC/CDR System Attributes menu(Figure 6-13) are not used exclusively by the automatic-processing method.Check these options to ensure that they are set appropriately before any typeof processing is executed.


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) 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 Processing 9189 Modify Output File Format Level: 1


Figure 6-13. Octel PC/CDR System Attributes Menu.

Perform the following steps to use the automatic CDR-processing method:

1. From the DOS prompt on the PC, type a valid CDR system name or cdr andpress the Enter key. (Refer to section 4.2 for additional instructions aboutaccessing the Octel PC/CDR System Menu.) The Octel PC/CDR SystemMenu appears (Figure 6-2).

2. Select option 1 and press the Enter key to update system attributes. A screenappears, similar to the Octel PC/CDR System Attributes Menu (Figure 6-13).

3. Select option 5 and press the Enter key to select the output files to beautomatically generated after the download is performed. The ModifyAutomatic Output File Generation menu, similar to Figure 6-14, appears.

Modify Automatic Output File Generation westreg


1 Generate Session Detail Output File YES2 Generate Unsuccessful Transfer Output File YES3 Generate Message Detail Output File YES4 Generate Individual Port Statistics Output File YES

10 Append Records to Forms Output File YES

Enter Option:

Figure 6-14. Modify Automatic Output File Generation Menu.

4. Refer to Figure 6-14 and select the output files to be generated by typing theoption number corresponding to the desired output file and pressing the Enterkey. The YES and NO choices are toggled back and forth as each option isselected.

SECTION 6.3

PROCESSING METHODS


5. After the desired files are selected, select option 0 and press the Enter key toreturn to the Octel PC/CDR System Attributes Menu (Figure 6-13).

6. The first block that has not been downloaded is the default in the CurrentSetting column for option 8, Next Block to Download by Automatic OctelPC/CDR Processing . If it is necessary to choose a different beginning blockfor the download, refer to the system-attributes menu (Figure 6-13), selectoption 8 and press the Enter key. The following prompt appears at the bottomof the screen:

Enter the First Block Number to Download (0 to 65535) or Enter Nothing to receive VPMOD’s Next Default Block NumberBlock Number? :

If the entry for the Next Block to Download by Automatic Octel PC/CDRProcessing is changed, it must either be the number of a previouslydownloaded block or the first block in a sequence that has not already beendownloaded (the default block number). If it is not, the download will fail. Forexample,

If blocks 1726 through 1918 have not been downloaded, a downloadcannot begin at block 1900. It must start at block 1726 or it must startwith a previously downloaded block.

If desired, type a new beginning block number in this field and press theEnter key. To accept the default block number, press the Esc key or theEnter key.

7. Select option 0 and press the Enter key to save the changes and return tothe PC/CDR System Menu (Figure 6-2).

8. Select option 3 from the PC/CDR System Menu and press the Enter key tobegin automatic processing. The PC links with the voice processor andperforms the following (depending on the choices made in step 4):

CDR data is downloaded from the CDR buffer.

BCFs are collated.

Selected output files are generated.

Data is appended to the forms output file.

As each event is performed, the appropriate screen relating to the eventappears on the PC monitor. Section 6.2 explains each screen.

9. Repeat these steps if automatic processing is desired for additional voiceprocessors (CDR systems).

If no changes are required to the system attributes (steps 1 through 7), theautomatic-processing method can also be executed directly from the DOS promptby typing systemname -axxxx , where systemname represents the name assignedthe particular voice processor (section 3.4), and xxxx represents the voice-proces-sor system-manager password, for example, westreg -a7267 . This method returnsthe screen to the DOS prompt after processing is complete.

SECTION 6.3

PROCESSING METHODS


6.4 USING SCHEDULED AUTOMATIC PROCESSING

The Octel PC/CDR package can process data from multiple voice processorsautomatically at scheduled intervals. To use this method, the PC must bededicated to run a timer utility that can automatically download and processOctel PC/CDR files. As many as 10 different schedules can be created, with eachschedule specifying up to 10 different voice processors (CDR systems), programs,or batch files. The minimum time that can be set between downloads is 3 minutes.

The scheduled automatic-processing method uses all of the steps required toprocess CDR data, from downloading data from the CDR buffer through producingthe output files in the dBASE III or ASCII format.

A starting date, starting time, and a predetermined interval can be specified. Usingthis schedule data, the PC connects, downloads, disconnects, and processes CDRrecords from one or more voice processors or executes a program name orbatch-file name resident on the PC (or path). These batch files can be used forprocessing additional output files, such as bills or statistical analyses created by thesystem manager.

The automatic scheduler can download and process CDR data from more than onevoice processor using the Automatic Scheduler Functions menu and submenusaccessed from the Octel PC/CDR Main Menu, as shown in Figure 6-15.

Octel PC/CDR Main Menu, REV 1.50

0 Exit to DOS

1 Select an Individual System for CDR Processing2 Automatic Scheduler Functions

Enter Option:

Figure 6-15. Octel PC/CDR Main Menu.

Perform the following steps to access these menus:

1. At the DOS prompt, type cdr and press the Enter key. The Octel PC/CDRMain Menu appears.

2. Select option 2 and press the Enter key.

3. Until a schedule password is entered, the screen indicates that no passwordhas been established. Press the Enter key as indicated. If a password hasbeen established, type the password and press the Enter key. (The automatic-scheduler functions have a distinct password that is not necessarily thepassword previously set for system-manager functions.)

The Octel PC/CDR Automatic Schedule Menu appears, as shown in Figure6-16. This menu can also be accessed by typing schedcdr at the DOSprompt.

SECTION 6.4

PROCESSING METHODS


Octel PC/CDR Automatic Schedule Menu

0 Exit Menu1 Update Automatic Processing Schedules2 Start Automatic Scheduler Mode3 Update Schedule Password4 Update Automatic Scheduler Log Files

Enter Option:

Figure 6-16. Octel PC/CDR Automatic Schedule Menu.

The Octel PC/CDR Automatic Schedule Menu contains the following four options:

1 Update Automatic Processing Schedules . Use this option to createschedules; modify, remove, list, and print existing schedules; and back upand restore schedules.

2 Start Automatic Scheduler Mode. Select this option to turn on theautomatic schedule timer. If no schedules have been created, the automatic-processing-scheduler function cannot be started.

3 Update Schedule Password. Use this option if a password is desired.Enter a numeric password for access to all scheduling functions.

4 Update Automatic Scheduler Log Files. Update the associated log filesand access utilities for log file maintenance through this option.

Sections 6.4.1 through 6.4.4 discuss these options in detail.

6.4.1 Update Automatic Processing Schedules

Use option 1, Update Automatic Processing Schedules , to add automatic-processing schedules or to modify existing automatic-processing schedules. Thisoption also provides several file-maintenance utilities.

The automatic scheduler uses the current system attributes to connect and processoutput data files for each CDR system. Update system attributes, if necessary,before proceeding.

To access the Update Automatic Processing Schedules menu, refer to section 6.4and perform steps 1, 2, and 3. The Octel PC/CDR Automatic Schedule Menu(Figure 6-16) appears. Select option 1 and press the Enter key. The Octel PC/CDRUpdate Automatic Processing Schedules screen, shown in Figure 6-17, appears.Sections 6.4.1.1 through 6.4.1.7 describe the options on this menu.

6.4.1.1 Add a New Schedule. Before adding a schedule, make note of the CDR systemsto be included on the schedule. To obtain a list of all CDR system names, type cdrat the DOS prompt; then, from the Octel PC/CDR Main Menu (Figure 6-15), selectoption 1 and press the Enter key. A list of valid names appears. This list can alsobe displayed by typing cdrhelp from the DOS prompt.

Normally, all schedules are executed successfully. However, a CDR system can beincluded in more than one schedule, providing a backup to ensure that the requireddata is captured despite telephone-line problems or a voice processor that might betemporarily out of service when called the first time. Octel PC/CDR simply down-loads and processes additional data during any additionally scheduled runs. Forexample,

SECTION 6.4

PROCESSING METHODS


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 6-17. Octel PC/CDR Update Automatic Processing Schedules Menu.

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 voice processor (CDRsystem) because of telephone-line problems. However, when the 2:00 a.m.schedule is executed, the connection is possible and the download occurs. Ifboth downloads were successful, CDR data generated between midnight and2:00 a.m. would be included in the second set of files created.

Perform the following steps to add a schedule to the automatic scheduler:

1. From the Octel PC/CDR Update Automatic Processing Schedules menu(Figure 6-17), select option 1 and press the Enter key.

Each schedule must be assigned a unique number from 1 through 10. Type thenumber of the schedule to be created at the Schedule # to add (1–10, orESC): prompt that appears at the bottom of the screen and press the Enterkey.

When an available schedule number is entered, a screen similar to Figure6-18 appears. If an existing schedule number is entered, a prompt indicatesthat the schedule number is already in use and requests that anotherschedule number be entered.

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: 02–29–92 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:


Figure 6-18. Automatic Octel PC/CDR Schedule Editor Menu.

SECTION 6.4

PROCESSING METHODS


2. Refer to the Automatic Octel PC/CDR Schedule Editor Menu (Figure 6-18),select option 1, and press the Enter key to enter a schedule name. Type aname, up to 15 characters long, describing this schedule and press the Enterkey. The schedule name appears in the Current Setting for Schedule no. xcolumn next to the Schedule Name: field. Although the name is optional, it isrecommended that an easily remembered name be assigned to eachschedule. This name need not be the same as the CDR system name. If aname is entered in this field, it also appears in the schedule-log file. (Section6.4.4 discusses the schedule-log file.)

3. Select option 2 and press the Enter key to update the entry in the Date/Timeof Next Execution: field. The following prompt appears at the bottom of thescreen:

Enter the Date of the Next Execution (mm–dd–yy):

To change the default entry, type a new starting date at the prompt and pressthe Enter key. The Enter the Time of the Next Execution (hh:mm): promptappears.

Type the starting time in a 24-hour format (for example, type 10:00 a.m. as10:00 and 10:00 p.m. as 22:00) and press the Enter key.

The updated date and time are displayed in the Current Setting for Sched-ule no. x column next to the Date/Time of Next Execution: field.

The Date/Time of Next Execution: field is automatically updated after thecurrent schedule is executed.

4. To change the default entry of 1 day between executions to another interval,select option 3, Interval Between Executions: and press the Enter key. Thefollowing prompt appears at the bottom of the screen:

Enter the Time Interval Between Executions (ddd:hh:mm):

This parameter allows the system manager to specify the interval betweenrunning times of this schedule. The minimum time that can be set betweendownloads is 3 minutes. In this prompt, ddd represents the number of daysbetween scheduled automatic downloads and processings. The hh and mmrepresent hours and minutes. If the interval between scheduled automaticdownloads and processings is less than 1 day, enter the number of hours orminutes that should pass before the next download is to occur. For example,

If the schedule is executed every day at a specified time, type 1:00:00(execute the schedule every day). If the schedule is executed onceeach week, type 7:00:00 (every 7 days). If the schedule is executedevery 6 hours, type 0:06:00 (every 6 hours).

Type the number representing the interval between executions in the formatshown and press the Enter key. The revised interval is displayed in theCurrent Setting for Schedule no. x column, next to the Interval BetweenExecutions: field.

5. Select option 4 and press the Enter key to enter the name of the CDRsystem or program to be included on this schedule (for example, a batch filethat executes an application to process the data). Type in the name and pressthe Enter key.

The CDR system name now appears in the Current Setting for Scheduleno. x column next to the System/Program Name 1: field.

SECTION 6.4

PROCESSING METHODS


6. Repeat step 5 for options 5 through 13, until all CDR systems to be includedon this schedule have been listed.

When a schedule is executed automatically, the CDR systems are processedin the order in which they are listed on the schedule.

7. Type 0 and press the Enter key to save the changes and return to the OctelPC/CDR Update Automatic Processing Schedules screen (Figure 6-17). Tocancel the changes, press the Esc key.

Refer to section 6.4.2 for instructions about how to start the automaticscheduler.

6.4.1.2 Edit an Existing Schedule. Perform the following steps to change an existingschedule parameter:

1. From the Octel PC/CDR Update Automatic Processing Schedules menu(Figure 6-17), select option 2, and press the Enter key. The Schedule # toedit (1–10, or ESC) : prompt appears.

2. Type the number of the schedule to be edited and press the Enter key. If thenumber of a nonexistent schedule is entered, a prompt indicates that theschedule does not exist.

When a valid number is entered, the Automatic Octel PC/CDR ScheduleEditor Menu (Figure 6-18) appears, with the current schedule settingsdisplayed. Select the option number corresponding to the setting to bechanged, make the change desired, and press the Enter key.

3. Type 0 and press the Enter key to save the changes and return to the OctelPC/CDR Update Automatic Processing Schedules menu. To cancel thechanges, press the Esc key.

6.4.1.3 Remove an Existing Schedule. Perform the following steps to remove a schedulethat is no longer needed:

1. From the Octel PC/CDR Update Automatic Processing Schedules menu(Figure 6-17), select option 3 and press the Enter key. The Schedule # todelete (1–10, or ESC): prompt appears.

2. Type the schedule number to delete and press the Enter key. A prompt,confirming the number and schedule name (if used) to be deleted, appears.

3. Press Y to delete the schedule or press N to cancel the deletion.

6.4.1.4 List Existing Schedules. Perform the following steps to review all existingschedules:


The screen displays the first schedule, as shown in Figure 6-19. Additionalschedules appear sequentially as the Enter key is pressed. Press the Esc keyto discontinue the review and return to the Octel PC/CDR Update AutomaticProcessing Schedules menu (Figure 6-17).

SECTION 6.4

PROCESSING METHODS


Automatic Octel PC/CDR Schedule 1 – Region1

Date/Time of Next Execution: 02–30–92 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 6-19. Automatic Octel PC/CDR Schedule List.

2. When all the schedules have been reviewed, press the Enter key to return to theOctel PC/CDR Update Automatic Processing Schedules menu (Figure 6-17).

6.4.1.5 Print Existing Schedules. Perform the following steps to print all existingschedules:


2. When the Please make sure your printer is ONLINE. prompt appears at thebottom of the screen, verify that the printer is on line.

3. Press the Enter key to begin printing all schedules. After the schedules areprinted, the Octel PC/CDR Update Automatic Processing Schedules menureappears. To cancel the printout, press the Esc key.

If the printer is not properly connected or not on line, the screen displays thefollowing prompt:

Write fault error writing device PRNAbort, Retry, Ignore, Fail?

Press A to abort. The screen either returns to the Octel PC/CDR Main Menu(Figure 6-15), if the Automatic Scheduler Functions menu was accessed bytyping cdr , or to the DOS prompt, if the Automatic Scheduler Functions menuwas accessed by typing schedcdr . Type cdr or schedcdr at the DOS promptto try again.

6.4.1.6 Backup Schedule Parameter File. Perform the following steps to backup the CDRschedules to a diskette. This is a precautionary step, in the unlikely event that a PChard-disk problem occurs or if a schedule is inadvertently erased from the hard drive.

1. From the Octel PC/CDR Update Automatic Processing Schedules menu(Figure 6-17), select option 6 and press the Enter key. The following promptappears:

The automatic Octel PC/CDR schedules file will be backed up.

Do you wish to proceed with schedule file backup? (y/n):

SECTION 6.4

PROCESSING METHODS


2. Press Y and the Enter key to proceed. The following prompt appears:

Destination Drive for Backup (A: to E:) ?:

3. Type the appropriate letter for the drive being used and press the Enter key.

A prompt similar to the following appears:

Insert backup diskette 01 in drive A:

WARNING! Files in the target drive A:\ root directory will be erased Press any key to continue . . .

4. Insert a blank formatted diskette into the diskette drive, and press any key tocontinue. The backup process begins. If the diskette is filled, additionaldiskettes are requested.

Each backup diskette is automatically numbered by the operation. Thisnumber shows up as the volume name. Make sure to label the diskettes inthe order in which they are copied (for example, diskettes 01, 02, 03, and soon) so the numbers match the volume names.

5. After the schedules are copied to the diskette(s), the screen returns to theOctel PC/CDR Update Automatic Processing Schedules menu (Figure 6-17).Remove the back-up diskette, label it, and store it in a secure location.

6.4.1.7 Restore Schedule Parameter File. This option can only be used if a backup file to adiskette was previously created using option 6 of the Octel PC/CDR UpdateAutomatic Processing Schedules menu (Figure 6-17). If a backup of the scheduleswas created, use option 7, Restore Schedule Parameter File, to restore schedules tothe hard disk. Perform the following steps to restore a schedule to the PC hard disk:

1. From the Octel PC/CDR Update Automatic Processing Schedules menu (Figure6-17), select option 7 and press the Enter key. The following prompt appears:

The automatic Octel PC/CDR schedules file will be restored from the backup disk and the schedules in the restored file will REPLACE any currently active schedules.

Do you wish to proceed with schedule file restoration? (y/n):

Press Y and the Enter key to proceed.

2. At the Source Drive for Restore (A: to E:) ?: prompt, type the letter of thedrive containing the backup diskette and press the Enter key. A prompt similarto the following appears:

Insert backup diskette 01 in drive A:Press any key to continue . . .

3. Insert diskette 01 into the appropriate drive. If more than one diskette was usedto back up the schedules, make sure to insert them, when they are requested,in the order in which they were copied (diskette 01, 02, 03, and so on).

Press any key to restore the files to the hard disk. A message on the screenindicates the last date and time the files were backed up as the files arerestored.

4. After the schedules are restored to the hard disk, the screen returns to theOctel PC/CDR Update Automatic Processing Schedules menu (Figure 6-17).Remove the backup diskette and return it to a secure location.

5. Type 0 to return to the Octel PC/CDR Automatic Schedule Menu (Figure6-16).

SECTION 6.4

PROCESSING METHODS


6.4.2 Start Automatic Scheduler Mode

The date and time entered in option 2 of the Automatic Octel PC/CDR ScheduleEditor Menu (Figure 6-18) determines the time that automatic-processing begins.The Octel PC/CDR Processing Schedule (Figure 6-19) must be on the screenof the CDR PC for the previously defined schedules to be activated and forthe automatic processor to work. If desired, turn on the output-to-printer option(section 4.3.1) to print the processing steps for each scheduled CDR system asthey occur for monitoring at a later date.

If the CDR PC is to be left unattended while awaiting automaticprocessing, secure it in a locked room or disable the keyboard.Because the Octel PC/CDR Processing Schedule must remain onthe screen for the schedules to be executed at their respectivetimes, voice-processor and Octel PC/CDR security could becompromised.

Caution!

Choose one of the following methods to start the automatic-scheduler timer, so thatall existing schedules are executed at their respective starting times:

At the DOS prompt, type schedcdr –axxxx ; where xxxx is the automatic-processing-scheduler password, established using option 3, Update SchedulePassword (Section 6.4.3). Press the Enter key.

Type this command as the last line of the PC’s AUTOEXEC.BAT file, if thisprogram is to run automatically after power is turned on to the PC. Locatingthis command on the last line of AUTOEXEC.BAT ensures that the automatic-processing timer starts after a power failure.

Refer to the Octel PC/CDR Automatic Schedule Menu (Figure 6-16), selectoption 2 and press the Enter key.

After one of the above access methods is performed, a screen similar toFigure 6-20 appears.

The first line of the processing-schedule screen (Figure 6-20) shows the totalnumber of schedules waiting to be processed. The second line shows the numberand name, if used, of the next schedule to be processed. The next two lines showthe date, time, and interval previously set for this schedule. The System Namefields list the CDR systems or programs for which this schedule is to be run. Thelast line shows the time remaining before this schedule is activated and processingbegins.

Automatic processing takes place as scheduled, when the timer reaches000:00:00:00.

SECTION 6.4

PROCESSING METHODS


Octel PC/CDR Processing Schedule 2 Automatic Octel PC/CDR Schedules waiting to be processed.Next Schedule is 1 – Region1

Date/Time of Execution: 02–30–92 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 6-20. Octel PC/CDR Processing Schedule Screen With Timer Running.

6.4.3 Update Schedule Password

If established, a schedule password is required to access the Octel PC/CDRAutomatic Schedule Menu (Figure 6-16) and to execute all schedule functions. Theschedule password is not required and does not have to be the same as the pass-word used by the voice processor. However, establish a schedule password toensure that unauthorized users do not tamper with schedule processing. Perform the following steps to set the schedule password:

1. From the Octel PC/CDR Automatic Schedule Menu (Figure 6-16), select option3 and press the Enter key.

2. At the Enter New Schedule Password: prompt, type a password up to 15alphanumeric characters long and press the Enter key. Choose a passwordthat is easy to remember, but not easy to guess.

3. At the Enter Password Again for Verification: prompt, type the passwordagain and press the Enter key. Make note of the new password and save it ina secure location.

If the schedule password is forgotten, it cannot be recovered. Togain access to the scheduling menus, all of the schedules and theexisting schedule password must be deleted. All automatic-processing schedules would need to be re-created.

Caution!

SECTION 6.4

PROCESSING METHODS


If the password is forgotten, the only way the automatic scheduling menus can beaccessed again is by deleting the existing password and all of the schedules. Typeschedcdr –r at the DOS prompt. The following prompt appears:

WARNING: Deleting all schedules & password. Are you sure? (y/n):

To delete all schedules and the password, press Y and the Enter key, thenre-create the schedules (section 6.4.1), and establish a new password (section6.4.3).

6.4.4 Update Automatic Scheduler Log Files

A transaction-log file called SCHEDCDR.LOG is maintained in the OCTELCDR\LOGsubdirectory located on the hard disk. This file shows information about automatic-schedule transactions. Entries in the automatic schedule-log file are described inAppendix F.

To review this file and perform other functions associated with the SCHEDCDR.LOGfile, refer to section 6.4 and perform steps 1, 2, and 3 to access the Octel PC/CDRAutomatic Schedule Menu (Figure 6-16). Select option 4 and press the Enter key.The Octel PC/CDR Update Automatic Scheduler Log File menu appears, as shownin Figure 6-21.

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 6-21. Octel PC/CDR Update Automatic Scheduler Log File Menu.

Sections 6.4.4.1 through 6.4.4.5 discuss the scheduler-log-file options.

6.4.4.1 List Schedule Log File. Perform the following steps to list (view) the contents ofthe schedule-log file:

1. From the Octel PC/CDR Update Automatic Scheduler Log File menu (Figure6-21), select option 1 and press the Enter key to view the contents of theschedule-log file. The schedule-log file appears, similar to the example shownin Figure 6-22.

The entries in the schedule-log file vary. Refer to Appendix F for descriptionsof schedule-log-file entries. All entries show the date, time, and name or briefdescription of the action taken. For example, the schedule-log file shown inFigure 6-22 shows the following entries:

SCHEDEDT:Startup. This entry appears every time option 1 or 4 isselected from the Octel PC/CDR Automatic Schedule Menu (Figure 6-16).

SECTION 6.4

PROCESSING METHODS


>> 04-26-92 10:16 SCHEDEDT: Startup.>> 04-26-92 10:19 SCHEDEDT: Shutdown.

04-26-92 11:00: Begin Processing Schedule # 1 – sch1, System/Program # 1 – westreg


Figure 6-22. Example of a Displayed Schedule-Log File.

SCHEDEDT:Shutdown. This entry appears every time option 1 or 4 onthe Octel PC/CDR Automatic Schedule Menu (Figure 6-16) is selectedand then exited.

04-26-92 11:00: Begin Processing Schedule #1 . . . This entry showsthe date, time, and schedule number of the schedule being processed.

2. After reviewing the file, press the Enter or Esc key to return to the OctelPC/CDR Update Automatic Scheduler Log File menu (Figure 6-21).

The schedule-log file can also be viewed by typing the following command at theroot-directory DOS prompt:

type\octelcdr\log\schedcdr.log

To stop the information from scrolling down the screen, press the Ctrl and S keys simul-taneously (^S ). To continue scrolling, press the Ctrl and Q keys simultaneously (^Q ).

6.4.4.2 Print Schedule Log File. Perform the following steps to print the schedule-log file:

1. From the Octel PC/CDR Update Automatic Scheduler Log File menu (Figure6-21), select option 2 and press the Enter key.

2. Verify that the printer is on line.

3. Press the Enter key to begin printing.

6.4.4.3 Backup Schedule Log File. Make a schedule-log-file backup in case a PC hard-disk problem occurs or a schedule-log file is inadvertently erased from the harddrive. The current schedule-log file is erased and a new schedule-log file is openedwhen the backup is performed. Perform the following steps to back up the log file:

1. From the Octel PC/CDR Update Automatic Scheduler Log File menu (Figure6-21), select option 3 and press the Enter key. The following prompt appears:

The automatic Octel PC/CDR log file C:\OCTELCDR\LOG\Smmddyy.LOG will be backed up. A new log file will then be started.

Do you wish to proceed with log file backup? (y/n) :

2. Press Y to back up the log file and press the Enter key. The following promptappears:

Destination Drive for Backup (A: to E:) ?:

SECTION 6.4

PROCESSING METHODS


3. Insert a blank, formatted diskette into the diskette drive, and type theappropriate letter for this drive. Press the Enter key. A prompt similar to thefollowing appears:


WARNING! Files in the target drive A:\ root directory will be erased Press any key to continue . . .

4. Press any key to continue. The backup process begins. If the diskette is filled,additional diskettes are requested.

Each backup diskette is automatically numbered during the backup operation.This number shows as the volume name on the diskette. Make sure to labelthe diskettes in the order that they are used (for example, diskettes 01, 02,and so on), so the numbers match the volume names.

The SCHEDCDR.LOG file is copied to a file called BACKUP.001 on thediskette. The original SCHEDCDR.LOG file is erased, and a new log file withthe same name is created.

5. After the schedule is copied to the diskette(s), the screen returns to the OctelPC/CDR Update Automatic Scheduler Log File menu (Figure 6-21). Removethe backup diskette, label it, and store it in a secure location.

6.4.4.4 Restore Schedule Log File. Use option 4 if it is necessary to restore a previouslybacked up schedule-log file to the hard disk. This option can only be used if theschedule-log file was previously backed up to a diskette using option 3 of the OctelPC/CDR Update Automatic Scheduler Log File menu (Figure 6-21). View therestored schedule-log file by using the DOS type command. Perform the followingsteps to restore a schedule-log file to the PC hard disk:


Any archived log files on the backup disk will be restored to your fixed drive in directory C:\OCTELCDR\LOG\ using the namingconvention Smmddyy.LOG. The current log will NOT be replaced.

Do you wish to proceed with log file restoration? (y/n) :

2. Press Y and the Enter key to proceed.

3. Insert backup diskette 01 into the appropriate drive. At the Source Drive forRestore (A: to E:) ?: prompt, type the letter of the drive containing thisdiskette and press the Enter key. A prompt similar to the following appears:


4. Press any key to restore the files to the PC hard disk. A message on thescreen displays the last date and time the files were backed up.

If more than one diskette was used to back up the schedule-log file, makesure to insert the diskettes in the order in which they were copied (diskette 01,02, and so on), as the they are requested.

SECTION 6.4

PROCESSING METHODS


The restored schedule-log file is copied into the C:\OCTELCDR\LOGsubdirectory. The log file is named Smmddyy.LOG , where S represents theschedule-log file and mmddyy represents the month, day, and year theschedule-log file was originally backed up. View the restored schedule-log fileby using the DOS type command.

5. After the schedule-log files are restored to the hard disk, the screen returns tothe Octel PC/CDR Update Automatic Scheduler Log File menu (Figure 6-21).Remove the backup diskette and return it to a secure location.

6.4.4.5 Erase Schedule Log File. Schedule-log files should be deleted periodically toprovide additional disk-storage space for future log files. Refer to section 6.4.4.3 toback up the schedule-log files before deleting them, as erased files cannot berecovered. Perform the following steps to erase schedule-log files:


The automatic Octel PC/CDR log file will be erased and a new log file will then be started. The current log contents will NOT be saved.

Do you wish to proceed with log file erasure? (y/n) :

2. Press Y and the Enter key to erase the log file.

3. After the log file is deleted, the screen returns to the Octel PC/CDR UpdateAutomatic Scheduler Log File menu (Figure 6-21).

6.5 USING THE SERVICE-LEVEL DOWNLOAD

The service-level download is used primarily by Octel or distributor servicerepresentatives for troubleshooting. It creates the same binary collated files (BCFs)as all other forms of processing; however, specific data blocks must be selected fordownloading.

Use the manual processing method described in section 6.2 to process BCFscreated with the service-level download.

Access the voice-processor Main Menu either of two ways:

Through the Octel PC/CDR System Menu (Figure 6-2), option 5

By typing a special command at the DOS prompt

Select one of the following methods to execute the service-level download:

Method I: Access Through Octel PC/CDR System Menu

Perform the following steps to execute the service-level download through the OctelPC/CDR System Menu:

1. At the DOS prompt on the PC, type a valid CDR system name or cdr andpress the Enter key. (Refer to section 4.2 for additional instructions aboutaccessing the Octel PC/CDR System Menu.) The Octel PC/CDR SystemMenu appears (Figure 6-2).

SECTIONS 6.4 – 6.5

PROCESSING METHODS


2. From the Octel PC/CDR System Menu (Figure 6-2), select option 5 and pressthe Enter key to link with the voice processor for performing system-managerfunctions. Type the system-manager password if prompted. If the system-manager password was requested before this menu was shown, it is notrequested here. Several menus scroll across the screen before the SMT MainMenu appears.

3. From the voice-processor Main Menu, enter menu 16.1.2 to retrieve CDRrecords. A screen similar to Figure 6-23 appears.

Sequence Number of First Block to Retrieve: 955

Number of Blocks to Retrieve:

Menu 16 – Database AccessRetrieve Call Detail Records

Figure 6-23. SMT Menu 16.1.2, Database Access,Retrieve Call Detail Records.

4. The entry in the Sequence Number of First Block to Retrieve: field musteither be the number of a previously downloaded block or the first block in asequence that has not already been downloaded. If the entry is not one ofthese, the download will fail. For example,

If blocks 1726 through 1918 have not been downloaded, a downloadcannot begin at block 1900. It must start at block 1726 or it must startwith a previously downloaded block.

Type the first block number to retrieve and press the Enter key. The cursormoves to the next field.

5. In the Number of Blocks to Retrieve: field, type the number of blocks toretrieve and press the Enter key. The following prompt appears:

Begin file transfer. . . Initiate transfer on PC now. . .Press Ctrl-X/Return to cancel. . . Press any key when transfer iscomplete. . .

6. Press the F3 key. The cursor moves to the command line at the bottom of thescreen.

7. At the command line, type the command RX filename.BCF, as shown inFigure 6-24. Although BCF file names normally follow the conventionAyymmddi.BCF (defined in section 1.7.1) during the service-level download,any unique file name can be used. The BCF created with this download willbe given the file name that is defined here.

Press the Enter key to begin the download. A screen similar to Figure 6-25appears. This screen displays the flow of data being downloaded from thevoice processor to the PC by incrementing counters shown on the screen.

8. When the download is complete, the command line shows the following:

F3 for Command?, F4 for Status || Capture Off || WY 50

SECTION 6.5

PROCESSING METHODS


Sequence Number of First Block to Retrieve: 955

Number of Blocks to Retrieve: 100

Menu 16 – Database AccessRetrieve Call Detail Records

Command? RX filename.BCF

Begin file transfer . . . Initiate transfer on PC now . . .Press Ctrl–X/Return to cancel . . . Press any key when transfer is complete . . .

Figure 6-24. SMT Menu 16.1.2, Database Access,Retrieve Call 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 6-25. Octel PC/CDR Block Retrieval Transfer Screen.

Press the F6 key. The prompt Retrieval Complete flashes on the screen andthe link with the voice processor is disconnected. The screen returns to theOctel PC/CDR System Menu (Figure 6-2).

Method II: Access With Special DOS Command

The link with the SMT screen can be established by typing the following commandat the DOS prompt:

systemname –Lxxxx

where

systemname is the name chosen for the CDR system. (Type the commandcdrhelp at the DOS prompt to list all valid system names.)

–L is the parameter required to execute the communication link between the PCand the voice processor.

xxxx is the system-manager password. If no password or an incorrect password istyped here, the normal system-manager-password prompt appears.

Repeat steps 3 through 8 for Method I to complete the service-level download.

SECTION 6.5

PROCESSING METHODS


6.6 HIGHLIGHTS

The manual CDR processing method is used to set up and become familiarwith a new CDR system.

The automatic-processing method downloads data, collates data, andgenerates output files all in one step.

The automatic-processing scheduler processes data from multiple voiceprocessors (CDR systems) at scheduled times.

Service-level downloading retrieves specific data blocks from a voiceprocessor.

SECTION 6.6

7

UTILITIES


CHAPTER SEVENCONTENTS

7.1 OVERVIEW 7-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.2 FILE UTILITIES OPTIONS 7-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.2.1 Display Disk Status 7-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.2.2 Display Octel PC/CDR Files 7-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.2.3 View/Print Octel PC/CDR Files 7-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2.3.1 Selecting an Output File 7-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2.3.2 Viewing an Output File 7-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2.3.3 Printing an Output File 7-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.2.4 Back Up Octel PC/CDR Files 7-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.2.5 Erase Octel PC/CDR Files 7-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.2.6 Restore Octel PC/CDR Files 7-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.2.7 Use Service Utilities 7-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2.7.1 Searching a Collated Day File 7-9. . . . . . . . . . . . . . . . . . . . . . . . . 7.2.7.2 Copying a Binary-Collection File 7-12. . . . . . . . . . . . . . . . . . . . . . 7.2.7.3 Displaying a Binary Collection File 7-14. . . . . . . . . . . . . . . . . . . . 7.2.7.4 Displaying a Processed Collection File 7-16. . . . . . . . . . . . . . . . . 7.2.7.5 Displaying a Pending-State File 7-16. . . . . . . . . . . . . . . . . . . . . . .

7.3 HIGHLIGHTS 7-17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section Page


FIGURES


Figure 7-2. Octel PC/CDR File Utilities Menu 7-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 7-3. Main Menu of the View Octel PC/CDR Output Files 7-2. . . . . . . . . . . . .

Figure 7-4. File Selection Parameters submenu of the View OctelPC/CDR Output Files Menu 7-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 7-5. File Selection Parameters Screen with Output File Summary Shown in the Status Window 7-4. . . . . . . . . . . . . . . . . . . . . . . .

Figure 7-6. Print Selection Parameters of the View OctelPC/CDR Output Files Menu 7-5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 7-7. Octel PC/CDR File Backup Menu 7-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 7-8. Octel PC/CDR File Erase Menu 7-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 7-9. Octel PC/CDR Service Utilities Menu 7-9. . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 7-10. Search Collated Day File Utility Menu 7-10. . . . . . . . . . . . . . . . . . . . . . . . .

Figure 7-11. Select a Binary Collection File Menu 7-12. . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 7-12. COPYBCF Options Menu 7-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 7-13. DUMPBCF Options Menu 7-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 7-14. Select a Pending State File Menu 7-16. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Page

7


UTILITIES

7.1 OVERVIEW

The Octel PC/CDR software utilities are accessed from option 4 of the OctelPC/CDR System Menu, as shown in Figure 7-1. The utilities allow many functions,such as managing Octel PC/CDR files and displaying collated day files andpending-state files.


0 Exit


Enter Option:


7.2 FILE UTILITIES OPTIONS

From the Octel PC/CDR File Utilities Menu, shown in Figure 7-2, the systemmanager performs the following tasks:

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 7-2. Octel PC/CDR File Utilities Menu.

Display status of the disk

Display CDR files

View or print CDR output files

Back up CDR files

UTILITIES


Erase CDR files

Restore CDR files

Access the Service Utilities menu

From the Octel PC/CDR System Menu (Figure 7-1), select option 4 and press theEnter key to display the Octel PC/CDR File Utilities Menu (Figure 7-2). Theseoptions are described in the following sections.

7.2.1 Display Disk Status

The Display Disk Status option shows the total number of files and the amount ofdisk storage in use for both the CDR system subdirectories and the overall PC harddisk. It also shows the available disk-storage space remaining on the PC hard disk.To display the status of the PC hard disk, select option 1 from the Octel PC/CDRFile Utilities Menu (Figure 7-2) and press the Enter key.

7.2.2 Display Octel PC/CDR Files

To display all Octel PC/CDR files in each subdirectory of a particular CDR system,select option 2 from the Octel PC/CDR File Utilities Menu (Figure 7-2) and pressthe Enter key. Each subdirectory is displayed with a listing of the files it contains.Each time the Enter key is pressed, the next subdirectory is displayed.

7.2.3 View/Print Octel PC/CDR Files

Output files are selected and then viewed or printed from option 3 on the OctelPC/CDR File Utilities Menu (Figure 7-2). SDO and MDO files are always viewed andprinted in file-format level 2, regardless of how they are configured (refer to section4.3.9 and Appendix A for information about file-format levels).

From the Octel PC/CDR File Utilities Menu (Figure 7-2) select option 3 and pressthe Enter key to display the View Octel PC/CDR Output Files Main Menu, asshown in Figure 7-3.

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 7-3. Main Menu of the View OctelPC/CDR Output Files.

SECTION 7.2

UTILITIES


7.2.3.1 Selecting an Output File. An output file must be selected before it can be viewedor printed. Perform the following steps to select an output file:

1. From the View Octel PC/CDR Output Files Main Menu (Figure 7-3), selectoption 1 and press the Enter key. The File Selection Parameters submenuappears, similar to the one shown in Figure 7-4.

Status Window

File Type : 1File Format : 2File Date : 02/22/92

Esc – Exit F1 – Help F2 – Display Choices F10 – Proceed

No file open.

View Octel PC/CDR Output FilesFile Selection Parameters

Figure 7-4. File Selection Parameters submenu of the View OctelPC/CDR Output Files Menu.

2. From the File Type: field, press F2 to display a window showing the followingoutput-file types that can be selected:

1 – Billing (SDO)2 – Forms (FDO)3 – Message Detail (MDO)4 – Port Statistics (PSO)5 – Unsuccessful Transfer (UTO)6 – Log File Output

Use the arrow keys to select the number for the desired output-file name, thenpress the Enter key to copy the number selected into the File Type: field.

3. The cursor moves to the File Format: field. Press F2 to display a windowshowing the file formats that can be selected. Use the arrow keys to selectthe file format (ASCII, dBASE, or Log Data) in which the file to be selectedwas created. Press the Enter key to copy the number selected into the FileFormat: field.

4. The cursor moves to the File Date: field. Type a valid output-file date in theformat shown on the screen. For example, if an SDO file is namedB920726.DBF, type 07/26/92.

5. Press F10 to select the output file. The screen returns to the Main Menu ofthe View Octel PC/CDR Output Files option (Figure 7-3). The Status Windowat the bottom of the Main Menu screen displays summary information aboutthe selected output file, including the number of records it contains, as shownin Figure 7-5.

SECTION 7.2

UTILITIES


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: 02–22–92. FileType: 1 – Billing (SDO)

FileFormat: 2 – DBase Data File. 36 Records in File.

Figure 7-5. File Selection Parameters Screen with Output File Summary Shown in the Status Window.

If the requested output file is not found, the following message appears in theStatus Window:

Unable to open that file.Press any key to continue.

If this message appears, confirm that the requested file name is valid (section7.2.2 explains how to display file names) and that the format in which therequested file was created is selected (dBASE III, ASCII, or Log Data). Referto steps 3 and 4, and adjust the entries in the File Format: and File Date:fields as necessary.

7.2.3.2 Viewing an Output File. View a selected output file by performing the followingsteps:

1. Follow the steps in section 7.2.3.1 to select an output file. A screen similar tothe Main Menu of the View Octel PC/CDR Output Files option (Figure 7-5)appears, with information about the selected file showing in the status window.

2. Select option 2 and press the Enter key. The output file is displayed on thescreen. Refer to Chapter One and Appendix A for output-file interpretation.

3. Press the F1 key for information about moving the cursor around the screen.

4. Press the F10 or Esc key to return to the Main Menu (Figure 7-5).

7.2.3.3 Printing an Output File. Print a selected output file by performing the followingsteps:

1. Follow the steps in section 7.2.3.1 to select an output file. A screen similar toFigure 7-5 appears, with information about the selected file showing in thestatus window.

2. Select option 3 and press the Enter key. A submenu, Print SelectionParameters, appears, similar to Figure 7-6, with the cursor in the First Line toPrint: field.

SECTION 7.2

UTILITIES


Status Window

View Octel PC/CDR Output FilesPrint Selection Parameters

First Line to Print : 1Last Line to Print : 66First Column to Print : 1Last Column to Print : 80

Esc – Exit F10 – Proceed

FileDate: 02–22–92. FileType: 1 – Billing (SDO)

FileFormat: 2 – DBase Data File. 36 Records in File.

Figure 7-6. Print Selection Parameters of the View OctelPC/CDR Output Files Menu.

3. To modify any of the fields, move the cursor to the field to be changed, type thedesired number, and press the Enter key. The cursor moves to the next field.

4. When the information displayed in all fields is correct, press the F10 key.

The screen returns to the Main Menu (Figure 7-5), and the following promptappears in the status window:

Please make certain that your printer is online. Press any key to continue:

5. Verify that the printer is on line and press any key to begin printing.

If the printer is not on line, the following prompt appears in the status window:

Printing selected records. Press Esc to abort.Write fault error writing device LPT1Abort, Retry, Ignore, Fail?

If this prompt appears, type a and press the Enter key to return to the OctelPC/CDR File Utilities Menu (Figure 7-2), bring the printer on line, and return tosection 7.2.3.1 to reselect the output file for printing. Refer to Appendix A foroutput-file interpretation.

6. Press the Esc key to return to the Octel PC/CDR File Utilities Menu (Figure 7-2).

7.2.4 Back Up Octel PC/CDR Files

Routine storage maintenance is required for efficient CDR processing. Back up the filesin the CDR directories before erasing them from the hard disk (section 7.2.5) as aprecautionary measure in the unlikely event that a PC hard-disk problem could occur.

The Octel PC/CDR backup utility allows the BCF, CDF, output, system, and FDOdirectory files to be backed up. All or none of the files within these directories canbe backed up. The CDF, output, and system directory files can be selected by date.Perform the following steps to back up Octel PC/CDR files:

SECTION 7.2

UTILITIES


1. From the Octel PC/CDR File Backup Menu (Figure 7-2), select option 4 andpress the Enter key. A screen similar to Figure 7-7 appears.

Octel PC/CDR File Backup Menu westreg

0 Exit & Return to File Utility Menu Current Setting

1 Backup BCF Directory Files? (All/None) All2 Backup CDF Directory Files? (All/None/Date) All3 Backup Output Directory Files? (All/None/Date) All4 Backup System Directory Files? (All/None/Date) All5 Backup FDO Directory Files? (All/None) All

6 Destination Drive for Backup (A:/B:/Tape) A:

7 Begin Backup

Enter Option (Esc to Abort Changes):

Figure 7-7. Octel PC/CDR File Backup Menu.

2. To select directory files for backup, type the number corresponding to thedesired directory file and press the Enter key. A prompt appears, requestingthe files to be backed up: All, None, or Date (if applicable).

3. Type the first letter (a, n, or d ) of the word that represents which directory fileis to be backed up and press the Enter key. When a or n is typed and theEnter key is pressed, the corresponding entry in the Current Setting columnchanges to All or None .

When d is typed (to back up files by date), the following prompt appears:

All files up to but not including the date you enter will be selectedEnter the date (mm-dd-yy):

Type the desired date in the format mm-dd-yy and press the Enter key. Thedate is entered in the appropriate field of the Current Setting column. Filesdated before, but not including the specified date, are backed up.

Repeat this step until all of the entries in the Current Setting column arecorrect.

4. From the Octel PC/CDR File Backup Menu (Figure 7-7), select option 6 todesignate the the backup-file destination drive. Press the Enter key. Thefollowing prompt appears:

Backup Destination Drive:

5. Type the appropriate letter for the drive containing the blank, unformatteddiskette to which the files are to be backed up and press the Enter key. Thedrive designation is entered in the appropriate field of the Current Settingcolumn. The tape backup feature is not supported at this time.

6. Select option 7 and press the Enter key to begin the backup procedure. Thefollowing prompt, containing important information about the backup process,appears on the screen:

SECTION 7.2

UTILITIES


Backup of files will be performed using the DOS backup utility.You may be prompted repeatedly to “Insert backup disk in drive”and “Strike any key when ready.” This is normal. You may simplyleave the current diskette in the drive and press any key each time you are so prompted. It is only necessary to change diskettes when the number (01, 02, 03, etc.) of the requested backup diskettechanges. During the backup procedure, you must press ESC twice to abort the backup sequence. The backup procedure will then be abortedat the first opportunity.

About to begin backup. Press ESC to abort or any other key tocontinue.

7. Press any key to continue. A prompt similar to the following appears:


WARNING! Files in the target driveA:\ root directory will be erasedPress any key to continue . . .

8. Insert a blank, formatted diskette into the diskette drive. Press any key tocontinue.

9. As the backup is being performed, the backed-up file names appear on thescreen. If the following prompt appears,

Insert last backup diskette in drive A:Press any key to continue . . .

do not change the diskette, just press any key to continue according to theinstructions given in the prompt in step 6. Continue to press any key as thisprompt is repeated.

If the following prompt appears, the diskette is full:


WARNING! Files in the target driveA:\ root directory will be erasedPress any key to continue . . .

Insert another blank, formatted diskette into the diskette drive and press anykey to continue.

Each backup diskette is automatically numbered during the backup operation.This number shows as the volume name on the diskette. Make sure to labelthe diskettes in the order in which they are used (for example, 01, 02, and soon), so the numbers match the volume names.

10. When the backup is complete, the Octel PC/CDR File Backup Menu (Figure 7-7)returns to the screen. Remove the backup diskette and store it in a securelocation.

11. Select option 0 and press the Enter key to return to the Octel PC/CDR FileUtilities Menu (Figure 7-2).

7.2.5 Erase Octel PC/CDR Files

The PC hard disk holds large amounts of data, but can be quickly filled unlessunnecessary files are frequently deleted. Octel PC/CDR files can be deleted ingroups from the PC hard disk. Erased files cannot be recovered, so erase OctelPC/CDR files only after they have been backed up onto a diskette (section 7.2.4).

SECTION 7.2

UTILITIES


The Erase utility allows the system manager to erase BCF, CDF, output, system,and FDO directory files. All or none of the files within these directories can beselected. The CDF, output, and system directory files can also be selected by date.Perform the following steps to erase Octel PC/CDR files:

1. From the Octel PC/CDR File Utilities Menu (Figure 7-2), select option 5, andpress the Enter key. A screen similar to Figure 7-8 appears.

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 7-8. Octel PC/CDR File Erase Menu.

2. To select the files to be erased, type the number corresponding to the desireddirectory and press the Enter key. A prompt appears, requesting the files tobe erased: All, None, or Date (if applicable).

3. Type the first letter (a, n, or d) of the word that represents which of these filesare to be erased and press the Enter key. When a or n is typed, All or Noneis entered in the appropriate field of the Current Setting column.

When d is typed (to back up files by date), the following prompt appears:

All files up to but not including the date you enter will be selectedEnter the date (mm-dd-yy):

Type the desired date in the format mm-dd-yy and press the Enter key. Thedate is entered in the appropriate field of the Current Setting column. Filesdated before, but not including the specified date, are erased. Repeat this stepuntil all of the entries in the Current Setting column are correct.

4. To begin the erase process, refer to the Octel PC/CDR File Erase Menu(Figure 7-8), select option 6, and press the Enter key. The file names appearon the screen as they are erased.

If a file was not previously backed up (section 7.2.4), a prompt questionswhether that file should be erased. Type y to proceed and erase the file ortype n to save the file. Press the Enter key.

5. When the erase process is complete, the Octel PC/CDR File Erase Menu(Figure 7-8) returns to the screen. Select option 0 and press the Enter key toreturn to the Octel PC/CDR File Utilities Menu (Figure 7-2).

7.2.6 Restore Octel PC/CDR Files

Octel PC/CDR files that were backed up using option 6 on the Octel PC/CDR FileUtilities Menu (section 7.2.4) can be restored from the backup diskette. Perform thefollowing steps to restore archived Octel PC/CDR files:

SECTION 7.2

UTILITIES


1. From the Octel PC/CDR File Utilities Menu (Figure 7-2), select option 6 andpress the Enter key. A prompt similar to the following appears:

Please insert the first diskette of the backup set in drive A:


2. Insert the backup diskette into the same disk drive that was originally used toback up the files. Press the Enter key. A prompt similar to the followingappears:


3. Confirm that diskette 01 is in the disk drive and press any key to continue.

With DOS version 3.2, the backed-up files are displayed on the PC screen. Afile number is listed to the left of each file name. Select the files to restore bytyping the file number of each desired file and pressing the Enter key. Eachfile must be selected and restored individually.

With DOS version 3.3 and above, all files on the backup diskette are restored.The file-restore utility displays the backed-up files found on the diskette asthey are restored to the hard disk. If the backup requires more than onediskette, the additional diskettes are requested as needed.

7.2.7 Use Service Utilities

The service-utility option is primarily for file manipulation. This option allows thecollated day files to be searched, copied, and displayed. It also allows binarycollection files to be copied and displayed and pending-state files to be displayed.

From the Octel PC/CDR File Utilities Menu (Figure 7-2), select option 7 and pressthe Enter key to access the Octel PC/CDR Service Utilities Menu, as shown inFigure 7-9. The options on the menu are discussed in the following sections.

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 7-9. Octel PC/CDR Service Utilities Menu.

7.2.7.1 Searching a Collated Day File. Use the Search Collated Day File utility to look forspecific items in the collated day files (CDFs). With this utility, CDFs can be directedto a printer, the screen, or to a file as specified by the output-selection parameter. Ifno ranges are specified, all events are displayed. The search criteria and asummary of the requested data are included at the end of the file. This informationis displayed on the screen if the file is printed.

SECTION 7.2

UTILITIES


Access the Search Collated Day File Utility Menu through the Octel PC/CDRService Utilities Menu (Figure 7-9) or by typing a special command at the DOSprompt. Select one of the following methods:

Method I: Access Through Octel PC/CDR Service Utilities Menu

Perform the following steps to access the Search Collated Day File utility:

1. Select option 1 from the Octel PC/CDR Service Utilities Menu (Figure 7-9) andpress the Enter key. A screen similar to Figure 7-10 appears.

Search Collated Day File Utility Menu

Q QuitS Start SearchD Issue DOS command

––––––––––––––––––––––––––––––––––––Settings–––––––––––––––––––––––––––––––––––A VPMOD 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 7-10. Search Collated Day File Utility Menu.

2. Based on the definitions that follow, type the letter preceding the parameter tobe set or modified in the Settings and Search Criteria areas on the menu.

Each option selected presents either a secondary menu or further informationand a format in which to type the new or updated entry. Press the Enter keyafter each field is updated. Repeat until all parameters have been established.

The Search Collated Day File Utility Menu (Figure 7-10) options are defined asfollows:

Press Q and the Enter key to exit the menu.Press S and the Enter key to begin the search operation. Select thisoption after defining all other necessary parameters on the menu.Press D and the Enter key to execute a DOS command without leavingthe menu. For example, the DOS command dir c:\ [systemname]\cdfcan be executed to list valid CDFs (where [systemname] represents theCDR system name), or the cdrhelp command can be executed to listadditional CDR system names. The BCF subdirectory is the defaultdirectory. Press the Esc key at the Enter DOS command: prompt toreturn to the Search Collated Day File Utility Menu.

The following parameters, under the Settings heading on the Search CollatedDay File Utility Menu, define the selected file, output, and display settings. Anentry is required in each field.

The VPMOD System name: field normally defaults to the current CDRsystem name. Select A and press the Enter key. A new screenappears. Type the number corresponding to the desired CDR systemfrom the list that is displayed. Press the Enter key.

SECTION 7.2

UTILITIES


The Input CDF File: field defines the collated day file to be selected(the file name is based on the creation date). Select I and press theEnter key. A new screen appears, displaying a maximum of 50 filenumbers. Type the number corresponding to the desired CDF file andpress the Enter key.The Output selection: field directs output to a file, to the screen, or toa printer. If a file is selected for output, the program prompts for anoutput-file name. The path of the output file can also be specified. If apath is not specified with the output-file name, the output file isautomatically placed in the BCF subdirectory. Select O and press theEnter key. A new screen appears. Type the letter corresponding to thedesired output destination and press the Enter key.The Record display: field is for selecting text, hexadecimal, both textand hexadecimal, or summary-output format. Select R and press theEnter key to select the record-display option. A new screen appears.Type the letter corresponding to the desired record display and pressthe Enter key.

The following optional parameters, under the Search Criteria heading on theSearch Collated Day File Utility Menu, define search criteria for the selectedfile. If no search criteria is defined, all data will be included in the output file.

The Times: field allows searches for an event in the CDF that occurredat a specific time or within a specific range of times. A maximum ofthree times or three time ranges can be selected. Select T and pressthe Enter key to specify a time or a range of times. A new screenappears. Enter the time(s) in the format shown on the screen, using the24-hour clock format, and press the Enter key.The Ports: field allows searches for events on specific ports recorded inthe CDF. A maximum of three ports or three port ranges can beselected. Select P and press the Enter key for a specific port or arange of ports. A new screen appears. Enter the port(s) in the formatshown on the screen and then press the Enter key.The Mailboxes: field allows searches for events in specific mailboxesrecorded in the CDF. A maximum of three mailboxes or three mailboxranges can be selected. Select B and press the Enter key for a specificmailbox or a range of mailboxes. A new screen appears. Enter themailbox number(s) in the format shown on the screen and then pressthe Enter key.The Event Records: field allows searches for a maximum of threespecific events or three event ranges recorded in the CDF. Select E andpress the Enter key for a specific event or a range of events. A newscreen appears. Type the number corresponding to the desired event(s)in the format shown and press the Enter key.The Msg ID Address: field shows message IDs used and recorded inthe CDF. Select M and press the Enter key for maximum of threemessage IDs or three message ID ranges. A new screen appears.Type the number corresponding to the desired message ID(s) in theformat shown and press the Enter key.

3. After establishing the parameters for the search, select S and press the Enterkey to begin the search. The CDF file data is presented, as shown in theOutput selection: field.

4. After the search has been completed, press the Enter key to return to theSearch Collated Day File Utility Menu (Figure 7-10).

SECTION 7.2

UTILITIES


5. Press the Esc key to return to the Octel PC/CDR Service Utilities Menu(Figure 7-9).

Method II: Access From the DOS Prompt

Perform the following steps to access the Search Collated Day File Utility Menufrom the DOS prompt:

1. At the DOS prompt, type cdfs and press the Enter key. The Search CollatedDay File Utility Menu (Figure 7-10) appears.

2. Follow steps 2, 3, and 4 from the previous section to access the CDF.

3. Press the Esc key to return to the DOS prompt.

7.2.7.2 Copying a Binary-Collection File. Use this utility to isolate specific blocks in abinary-collection file (BCF) and to copy them to a smaller, more manageable file.When the new file is given the extension of .BCF, it can be viewed through theDisplay Binary Collection File utility (section 7.2.7.3) before it is collated. To copy acollated BCF (a processed collection file or PCF), first rename the file fromAyymmddi.PCF to Ayymmddi.BCF, using the DOS rename command.

Access the Copy Binary Collection File Utility Menu through the Octel PC/CDRService Utilities Menu or by typing a special command at the DOS prompt. Selectone of the following methods:


Perform the following steps to access the Copy Binary Collection File Utility Menu:

1. From the Octel PC/CDR Service Utilities Menu (Figure 7-9), select option 2and press the Enter key. If there are uncollated BCF files in the BCFsubdirectory for the current CDR system, the Select a Binary Collection Filemenu appears, similar to Figure 7-11. Select the number that corresponds tothe desired BCF and press the Enter key.

If all BCF files have been collated, the following message appears:

No data files to selectPress ENTER/RETURN to continue.

Press the Enter key. To continue, rename a previously collated file fromAyymmddi.PCF to Ayymmddi.BCF using the DOS rename command, thenreturn to the beginning of this step to try again.

Select a Binary Collection File

0 Return to Service Utility Menu

1 A920426B 2 A920427A

Enter Option:

Figure 7-11. Select a Binary Collection File Menu.

SECTION 7.2

UTILITIES


2. Select the file’s corresponding number for a binary-collection file. Press theEnter key. The COPYBCF Options menu appears, similar to Figure 7-12.

COPYBCF Options BCF File: c:\westreg\bcf\A920426

0 Run COPYBCF (ESC to Cancel)

1 Target File COPYBCF.OUT2 First Block to Copy3 Last Block to Copy

Enter Option:

Figure 7-12. COPYBCF Options Menu.

3. Select option 1 and press the Enter key. Any name and extension can beused for the target name. If the file extension .bcf is used, the file can beviewed through the Display Binary Collection File utility (section 7.2.7.3). Typethe target-file name and press the Enter key to enter the name in the TargetFile field.

4. To request specific blocks within the file, select option 2 and press the Enterkey. Type the beginning block number and press the Enter key to enter thenumber in the First Block to Copy field.

5. Select option 3 and press the Enter key. Type the ending block number andpress the Enter key to enter the number in the Last Block to Copy field. Ifno entry is made, all blocks are copied, beginning with the block numberdesignated in step 4.

6. After the target file and the number of blocks have been specified, type 0 andpress the Enter key to run the COPYBCF utility. The requested blocks arecopied, and a confirming message shows on the screen.

7. Press the Enter key to return to the Octel PC/CDR Service Utilities Menu(Figure 7-9).


Perform the following steps to access the Copy Binary Collection File Utility Menu:

1. From the DOS prompt, type cd\ and press the Enter key. The prompt showsthe root directory (for example, C:>).

2. Type cd and the CDR system name. Press the Enter key. The prompt nowincludes the CDR system name (for example, C:\WESTREG>).

3. Type cd bcf to move to the BCF subdirectory. Press the Enter key. Theprompt now shows the CDR system name with the BCF designation (forexample, C:\WESTREG\BCF>).

4. Type the COPYBCF command using the following syntax:

copybcf [source.bcf] [target.bcf] [–Fn ] [–Lm]

where

copybcf is the command to execute this utility.

SECTION 7.2

UTILITIES


source.bcf is the file name of the BCF to be copied. The typical BCFfile name has the format AyymmddA.BCF. Enter a valid BCF filename in this format.

target.bcf is the name of the destination file. This is the file to whichthe desired BCF is copied after the utility program is executed. Anyfile name except the source.bcf file name can be used. If the samefile name already exists in the subdirectory, the existing file isoverwritten. If the file name extension is .bcf, the file can be viewedthrough the Display Binary Collection File Utility Menu (section7.2.7.3).

–Fn defines the beginning block number of the section of interest.

–Lm defines the ending block number of the section of interest.

For example,

The file A920302A.BCF contains blocks numbered from 0 to 100. Tocopy blocks that are numbered from 25 to 50 within this file to a filenamed SORT.BCF, type the following command:

copybcf a920302a.bcf sort.bcf –F25 –L50

Blocks numbered from 25 to 50 from the file A920302A.BCF are nowstored in the file named SORT.BCF. These blocks can now beprocessed or viewed.

Press the Enter key to copy the file. The requested blocks are copied, and aconfirming message shows on the screen. If specific blocks were notdesignated, all blocks within the requested BCF file are copied.

5. Press the Enter key to return to the DOS prompt.

7.2.7.3 Displaying a Binary Collection File. Use this utility to examine the contents of abinary collection file (BCF). All BCFs within a CDR system’s BCF subdirectory canbe viewed, including BCFs copied as in section 7.2.7.2 and given a BCF extension.

Access the Display Binary Collection File Utility Menu through the Octel PC/CDRService Utilities Menu or by typing a special command at the DOS prompt.


Perform the following steps to access the Display Binary Collection File Utility Menu:

1. From the Octel PC/CDR Service Utilities Menu (Figure 7-9), select option 3 andpress the Enter key. The Select a Binary Collection File menu (Figure 7-11)appears.

2. Select a binary-collection file by typing the file’s corresponding number. Pressthe Enter key. A screen similar to Figure 7-13 appears.

SECTION 7.2

UTILITIES


DUMPBCF Options BCF File: westreg

0 Run DUMPBCF (ESC to Cancel)

1 Full Report? No2 Block Date & Time Summary Report No

Enter Option:

Figure 7-13. DUMPBCF Options Menu.

3. The default entry in the Full Report? field is No. To obtain a full report, select1 and press the Enter key. The corresponding field is changed to Yes.

4. The default entry in the Block Date & Time Summary Report field is No. Toobtain a summary report only, select option 2 and press the Enter key. Thedata field is changed to Yes. If a full report was selected in step 3, the entryin the Full Report? field changes to No when the entry in option 2 is changedto Yes. Select Yes for either option 1 or option 2 to display the BCF.

5. Type 0 and press the Enter key to run the DUMPBCF command to displaythe BCF. The BCF or BCF summary is displayed on the screen.

To stop the information from scrolling down the screen, press the Ctrl and Skeys simultaneously (^S ). To continue scrolling, press the Ctrl and Q keyssimultaneously (^Q ).



Perform the following steps to display a binary collection file:



3. Type cd bcf to move to the BCF subdirectory. Press the Enter key. Theprompt now shows the CDR system name with the BCF designation (forexample, C:\WESTREG\BCF>).

4. Type the DUMPBCF command using the following syntax:

dumpbcf [sysname] [filename.ext] [–F|–D] –L >[newfile]

where

dumpbcf 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 BCF to bedisplayed.

–F is an optional parameter that provides details, listing all OctelPC/CDR event records in the file.

SECTION 7.2

UTILITIES


–D is an optional parameter that shows date, time, and block-sizeinformation only.

–L is an optional parameter that specifies a pause before returning tothe DOS prompt.

>newfile is an optional parameter that creates a file with the desig-nated name instead of displaying it on the screen. To send the fileto the printer instead of displaying it on the screen, type >prn inplace of >newfile .

For example,

Type dumpbcf westreg a920918a.bcf –f >friday to create a file calledFRIDAY that contains all events in the WESTREG system BCF file dated9/18/92.

Press the Enter key to display or create the file. The requested BCF isdisplayed on the screen or a file is created.

To stop the information from scrolling down the screen when displayed, pressthe Ctrl and S keys simultaneously (^S ). To continue scrolling, press the Ctrland Q keys simultaneously (^Q ).


7.2.7.4 Displaying a Processed Collection File. Use the DUMPBCF utility to viewprocessed collection files (PCFs). PCFs are produced if No was selected for theBinary Collection Files Erased After Collation? field in the Octel PC/CDRSystem Attributes menu (refer to section 4.3.2 and Figure 4-5). If BCFs are noterased after collation, they are renamed with the extension .PCF.

To view a PCF, follow the instructions in section 7.2.7.3 to access the DisplayBinary Collection File Utility Menu from the DOS prompt, except type pcf instead ofbcf as the file-name extension.

7.2.7.5 Displaying a Pending-State File. Use the Display Pending State File Utility Menuto view the contents of a pending-state file. Pending-state files (PSFs) are definedin section 1.7.4. Access the Display Pending State File utility through the OctelPC/CDR Service Utilities Menu or by typing a special command at the DOS prompt.


Perform the following steps to access the Display Pending State File utility:

1. From the service-utilities menu (Figure 7-9), select option 4 and press theEnter key. The Select a Pending State File menu appears, similar toFigure 7-14.

Select a Pending State File

0 Return to Service Utility Menu

1 COLLATE 2 A920418B

Enter Option:

Figure 7-14. Select a Pending State File Menu.

SECTION 7.2

UTILITIES


2. Select a pending state file by typing the number corresponding to the desiredPSF. Press the Enter key. The PSF is displayed on the screen.




Perform the following steps to display a pending-state file from the DOS prompt:



3. Type cd bcf to move to the BCF subdirectory. Press the Enter key. Theprompt now shows the CDR system name with the BCF designation (forexample, C:\WESTREG\BCF>). If the required PSF is stored in the SYSsubdirectory, type cd\sys instead.

4. Type the DUMPSF command using the following syntax:

dumpsf [sysname] [filename.ext] >[newfile]

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.

>newfile is an optional parameter that creates a file with the designatedname, instead of displaying it on the screen. To send the file to theprinter instead of the screen, type >prn in place of >newfile .

Press the Enter key to display or create the file. The requested PSF isdisplayed on the screen or a file is created.



7.3 HIGHLIGHTS

The Octel PC/CDR File Utilities Menu is used to display, print, back up,restore, and erase Octel PC/CDR files.

The available storage space on the Octel PC/CDR disk is monitored throughthe Display Disk Status option.

The service-utility option is designed for manipulating files.

Collated day files can be searched and the results can be printed, copied to afile, or viewed from the screen.

SECTION 7.2 – 7.3

8

DTMF OCTELFORMS


CHAPTER EIGHTCONTENTS

8.1 OVERVIEW 8-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8.2 CHOOSE APPLICATIONS 8-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8.3 DETERMINE BUFFER SIZE 8-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8.4 ESTIMATE CDR BUFFER AND PC DISK STORAGE SPACE 8-2. . . . . . . . . . . . .

8.5 ESTIMATE DOWNLOAD AND PROCESSING TIME 8-4. . . . . . . . . . . . . . . . . . . . .

8.6 COLLECT CDR DATA 8-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8.7 PROCESS DTMF OCTELFORMS WITH OCTEL PC/CDR 8-5. . . . . . . . . . . . . . . .

8.8 SELECT OUTPUT FILES AND OUTPUT FILE FORMATS 8-5. . . . . . . . . . . . . . . .

8.9 PROCESS OUTPUT FILES 8-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8.10 HIGHLIGHTS 8-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

TABLES

Table 8-1. Example of Octel PC/CDR-Event Buffer Capacity and PC Disk-Space Requirements 8-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 8-2. Comparison of Two Processing Modes 8-6. . . . . . . . . . . . . . . . . . . . . . . . . .

Section Page

8


DTMF OCTELFORMS

8.1 OVERVIEW

DTMF OctelForms is an optional data-collection and processing software programthat allows questions to be recorded and the responses to the questions to beentered by pressing the touch-tone keys on a telephone. The responses are collectedin the CDR buffer and collated into an output file using the Octel PC/CDR softwareprogram. DTMF OctelForms and Octel PC/CDR can be used simultaneously on thevoice processor and the PC. Processing techniques are similar for both the DTMFOctelForms and Octel PC/CDR software programs. This chapter provides specificparameters for the setup and processing stages required to operate the programstogether. Use preceding chapters to understand the setup and processing techniquesin greater detail.

If a CDR system is already established in either DTMF OctelForms or OctelPC/CDR, use that same CDR system (as established with the MKCDRSYScommand explained in section 3.4) to produce output files from the collated dayfiles (CDFs) for the established voice processor. This process eliminates down-loading duplicate buffer blocks and manipulating CDFs located in other CDR systemsubdirectories. Refer to the DTMF Manual for additional information.

8.2 CHOOSE APPLICATIONS

Applications for Octel PC/CDR and DTMF OctelForms vary. A DTMF OctelFormsorder-entry application can require processing several times a day; Octel PC/CDRprocessing might be required for billing only once a month (although downloadingwould need to be done more frequently). Call tracking using Octel PC/CDR canrequire processing several times a day; DTMF OctelForms processing could only benecessary weekly.

The time between downloading data is determined by the voice processor CDR-buffercapacity. A larger buffer is required when the time period between downloadings islong or if the voice processor is highly active. On highly active voice processors, it isnecessary to download frequently, even though the downloaded files are not manipu-lated each time they are collected.

Binary collection files (BCFs) are created in the PC during downloading and areaccumulated during processing. The PC must have the storage capacity to containall the BCFs created when these output files are processed. The PC must alsohave the storage capacity for the files produced when processing output files.

8.3 DETERMINE BUFFER SIZE

Check system manager menu 16.1.1 to determine the current size of the CDR buffer.The Total Number of Blocks for CDR: field indicates the maximum buffer spaceavailable for the combined DTMF OctelForms and Octel PC/CDR applications.

DTMF OCTELFORMS


The buffer size can be increased from 2020 blocks to 7020 blocks, but it cannot bereduced in voice processors at software releases 10.43 and 1.1X through 1.5X.Contact the local Octel support office or Octel distributor for assistance if the voiceprocessor is at any other software level and the buffer size needs to be reduced. Ifthe buffer size must be increased, call the local Octel or distributor support office forassistance. Increasing the buffer size to 7020 on a Branch, Branch, XP, or Aspensubstantially reduces the available message-storage space.

8.4 ESTIMATE CDR BUFFER AND PC DISK STORAGE SPACE

DTMF OctelForms and Octel PC/CDR use the same PC to store downloaded data.Estimate the CDR buffer and PC disk-storage requirements by adding the require-ments for both the DTMF OctelForms and CDR systems. Perform the followingsteps to compute the storage requirements:

1. Estimate the total number of daily calls to the DTMF OctelForms mailbox(daily calls). Count the number of questions in the mailbox (questions). Thenumbers 41 and 17 are given quantities and are not to be changed. Use thefollowing equation to determine the estimated number of buffer blocks filledeach day:

(daily calls x 41) + (daily calls x questions x 17)Estimated blocks filled per day =

2048

For example, the DTMF OctelForms application is using a Maxum mailbox fora public survey. There are 20 questions in the mailbox. It is projected that 600people will call the application each day.

(600 x 41) + (600 x 20 x 17)Estimated blocks filled per day = = 112

2048

This example estimates that 112 buffer blocks are filled with DTMF eventseach day.

2. To estimate the total number of blocks filled each day, locate the estimated dailycalls to the voice processor in the Calls per Day column of Table 8-1. Add thecorresponding number from the Average CDR Blocks Filled per Day columnto the estimated blocks filled per day number computed for the DTMF Octel-Forms system (from step 1).

For example,

Estimated daily calls to the voice processor = 5000

5000 calls per day = an average of 215 CDR blocks filled per day

215 average CDR blocks filled per day +112 average DTMF OctelForms blocks filled per day (from step 1)

327 estimated total blocks filled per day

SECTION 8.3 – 8.4

DTMF OCTELFORMS


Table 8-1. Example of Octel PC/CDR-Event Buffer Capacity and PC Disk-Space Requirements.

2,500 110 18 65 0.2 10–255,000 215 9 32 0.3 20–457,500 320 6 21 0.4 30–70

10,000 430 4 16 0.5 40–9515,000 640 3 10 0.8 60–14020,000 855 2 8 1.0 80–19025,000 1,070 1 6 1.2 100–235

Callsper Day

AverageCDR Blocks

Filledper Day

Buffer Capacity,Days Downloading

& Processing Time at 9600 Baud,

Hr/Daya

PC Disk-SpaceRequirements

per Month,MB

2020-BlockBuffer

7020-BlockBuffer

This example is for a voice processor with light voice-mail usage and few special applications.

a Based on the program running on a PC/AT (8-MHz CPU) equipped with a hard disk with 35-ms average access time.

The information in Table 8-1 is based on a voice processor with lightvoice-mail usage. If the voice processor has moderate or heavy voice-mailusage or has special applications (such as ECP mailboxes), the buffer fillsmore rapidly and downloading needs to be done more frequently than noted.Also allow for a longer processing time and more PC disk space for storage.When the Octel PC/CDR and DTMF OctelForms software are first installed,monitor the CDR buffer daily to establish a pattern as to how quickly thebuffer fills, then perform downloads based on this pattern.

3. Locate the closest value to the total blocks filled per day (from step 2) in theAverage CDR Blocks Filled per Day column of Table 8-1(round-off ifnecessary). The corresponding number in the appropriate Buffer Capacity,Days column (2020 or 7020 blocks) determines the number of days worth ofbuffer-storage space available for the combined software programs. Forexample,

327 average CDR blocks filled per day = 21 days of storage spaceavailable in a 7020-block buffer (for a voice processor with lightvoice-mail usage and few special applications).

The CDR buffer will be filled in 21 days; therefore, CDR data shouldbe downloaded every 7 to 10 days, to ensure that the buffer is notoverfilled.

4. To determine the megabytes of PC-disk space to reserve for Octel PC/CDRdata, locate the number in the PC Disk-Space Requirements per Month, MBcolumn that corresponds to the number of days of storage space available(this number was determined in step 3). For example,

21 days of storage space = 30 to 70 MB of PC disk space required.

5. Confirm the storage space available on the PC hard disk by using one of thefollowing methods:

SECTION 8.4

DTMF OCTELFORMS


At the DOS prompt on the PC, type dir , and press the Enter key. Thelast entry in the directory shows how many bytes of storage space areavailable on the PC hard disk.

Check the Display Disk Status submenu reached from the OctelPC/CDR File Utilities Menu (Figure 7-2) to determine whether there isenough available disk-storage space on the PC hard disk. (Refer tosection 7.2.1 for more information about this menu.)

If the available space on the PC hard disk is less than the megabytes of PCdisk space required (determined in step 4), take action to increase the spaceavailable on the disk by deleting unnecessary files or installing an additional orlarger hard disk.

8.5 ESTIMATE DOWNLOAD AND PROCESSING TIME

Use the following equation to estimate how long it will take to download andprocess the data from the CDR buffer:

Total processing time = [days between downloading] x [processing time]

where

[days between downloading] is the number of days of storage space that wasdetermined in section 8.4, step 3.

[processing time] is the number in the Downloading and Processing Timeat 9600 Baud, Hr/Day column of Table 8-1. The number corresponds to thenumber computed for the total daily blocks filled in section 8.4, step 2, andfound in the Average CDR Blocks Filled per Day column.

For example,

Total processing time = 21 x 0.4 hours/day = 8.4 hours

The processing time estimates shown in Table 8-1 are the normal elapsed times fordownloading at 9600 baud and processing the data to create the four standardoutput files. If CDR event data is downloaded from the voice processor at 1200baud, multiply the total estimated time by 4.5 to determine the total downloadingtime required. To estimate downloading time only (at 9600 baud), allow 2 secondsper block. For example,

120 blocks x 2 seconds per block = 240 seconds

240 seconds 60 seconds per minute

= 4 minutes to download

8.6 COLLECT CDR DATA

DTMF OctelForms data is accumulated in the CDR buffer only after the voiceprocessor is configured correctly. The Call Detail Recording and DTMF FormsMailbox features (options 16 and 43, respectively) must be enabled (section 2.5.1)and the voice processor must be instructed to begin collecting CDR and DTMFOctelForms data records for output files (section 2.5.2).

SECTION 8.4 – 8.6

DTMF OCTELFORMS


8.7 PROCESS DTMF OCTELFORMS WITH OCTEL PC/CDR

The process of downloading and collating data is identical for both DTMF Octel-Forms and Octel PC/CDR. Both collect event data into the same voice-processorCDR buffer. Octel PC/CDR software sorts the data using the collation and output-file-generation routines. Both DTMF OctelForms and Octel PC/CDR download thedata in the CDR buffer to the PC and store the data in binary collection files(BCFs). Collated BCFs produce collated day files (CDFs). One CDF file containsboth DTMF OctelForms and Octel PC/CDR data. Only the output files are different.BCF, CDF, and output files are described in detail in Chapter One.

When processing DTMF OctelForms and Octel PC/CDR, consider the output filesthat must be produced frequently, and establish the download schedule for thosefiles. The minimum time between scheduled downloads is 3 minutes. Each time theCDR buffer is downloaded, all output-file information is placed in a BCF. To producean output file, the BCF must be collated into CDFs. CDFs contain all of theinformation needed to produce the output files selected in menu 16.1.4 (section2.5.2).

Chapter Six describes four methods for processing CDR data. These methods canbe combined to produce the output files for both DTMF OctelForms and OctelPC/CDR. Mode 1 and Mode 2 describe two options for producing output files:

Mode 1. Set the Octel PC/CDR software to automatically download, collate,and process the Forms output file only. When other output files are desired,produce them manually with the manual-processing method (refer to section6.2). Manual processing requires more steps; with manual processing, the PCstores duplicate CDF information for previously produced output files.

Mode 2. Set the Octel PC/CDR software to automatically download, collate,and process all output files required. The BCFs and CDFs can then bedeleted immediately from the PC. With this method, multiple output files mustbe imported into the applications database when the less-frequent output filesare processed. For example,

The DTMF OctelForms application needs to be downloaded andprocessed each day, while Octel PC/CDR data is needed only onceeach month. Even though the Octel PC/CDR data is needed only onceeach month, it is downloaded daily, every time the DTMF OctelFormsdata is downloaded. To process the full month of Octel PC/CDR data,all of the daily output files are imported into an application databaseand combined for a monthly total.

Table 8-2 lists some factors that help determine which mode to use. The majorconsideration is the difference in storage requirements between the CDFs and OctelPC/CDR output files versus the inconvenience of manually producing the OctelPC/CDR output files when they are needed.

8.8 SELECT OUTPUT FILES AND OUTPUT FILE FORMATS

Section 4.3 explains how to update the Octel PC/CDR system attributes. Follow thesteps outlined in section 4.3.5 to modify the selection of output files to be createdautomatically. Follow the steps in section 4.3.6 to select the format in which theoutput files are to be created.

SECTION 8.7 – 8.8

DTMF OCTELFORMS


Effort• Daily• Monthly

Table 8-2. Comparison of Two Processing Modes.

Negligible.

Manually process each CDR file

Negligible.

Import 30 sets of CDR files into applications

program (one for each day of the month).

Storage• BCFs• CDFs• CDR• Forms

No, erase after collation.

Yes, need for processing CDR files.

No, not processed yet.

No, processed daily.

No, erase after collation.

No, CDR files are processed already.

Yes, waiting processing.

No, processed daily.

Advantages There is only one set of CDR files for an application program to process.

Best use of PC storage, no duplicate data stored in the CDFs.

No difficult sets of very large CDR files to handle.

Disadvantages Very large singular CDR output files. Cannot store files larger than floppy- disk capacity.

Processed forms data remains on the PC in the CDF.

Multiple sets of CDR output files to import intoapplications database. Not difficult if usingwild-card characters to assist in import.

Mode 1 Mode 2Considerations

8.9 PROCESS OUTPUT FILES

Use manual, automatic, or automatic scheduler procedures for downloading,collating, and processing DTMF OctelForms and Octel PC/CDR output files. Theseprocessing methods are explained in detail in Chapter Six. Output files can then beimported into a database application program to sort the data and generate reports.They can also be viewed and printed using the utilities menus described in ChapterSeven.

8.10 HIGHLIGHTS

Octel PC/CDR and DTMF OctelForms data can be processed at the sametime.

The download and collation processes are identical for Octel PC/CDR andDTMF OctelForms applications.

The DTMF Manual contains additional information about DTMF OctelForms.

SECTION 8.8 – 8.10

APPENDIXES

A-iiiEdition Three, Update A (Release 2.0)Octel PC/CDR

APPENDIXESCONTENTS

A: OUTPUT-FILE STRUCTURES A-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B: CDF EVENT-RECORD DESCRIPTION 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. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Page

A

A-1Edition ThreeOctel PC/CDR

OUTPUT-FILE STRUCTURES

Use the tables in this appendix to interpret Octel PC/CDR output files. Names thatare listed in the Octel PC/CDR Field Name column in Table A-1, A-3, A-5, A-7, A-8,and A-9 appear on the screen and on files printed through the File Utilities menu.Names shown in the dBASE III Field Name column appear when a file with theextension .DBF is imported into the dBASE III software program. Chapter Onediscusses output files in detail.

A.1 SESSION-DETAIL OUTPUT-FILE STRUCTURE

The session-detail output files contain records for each call session. A session isdefined as the period of time when a caller is in a mailbox. A call can consist ofone or more sessions. Session-detail output-files are named with the conventionByymmdd.ASC or .DBF. Table A-1 defines the file structure.

Cumulative duration for a specific mailbox on a session-detail report is less than theoverall duration given in a system manager subscriber report (obtained throughsystem manager menu 14) because each report measures the start and end of acall from a different point. The two types of subscriber reports that indicate durationare the Individual Subscriber Usage Report and the Short Form SubscriberStatistics Report. Octel PC/CDR reports do not indicate the time required toestablish the port connection and log into a mailbox; the system manager reportsinclude this in the duration calculation.

The term tree , as used in this appendix, refers to the software that provides aninterface between a caller and the voice-processor. For example, the term open treesis the entry point reached when a call is made to the voice processor. Callers aregiven the opportunity to dial an extension to which they could be transferred or toidentify themselves as subscribers by pressing the # key.

OUTPUT-FILE STRUCTURESAPPENDIX A

A-2 Edition Three Octel PC/CDR

Table A-1. Session-Detail Output-File Structure.

Octel PC/CDRField Name

dBASE IIIField Name

DataType

FieldLength Description

SyId SYSID Char 4 Voice-processor serial number (last 4 digits)Prt PORTID Char 3 Port used for sessionDate DATE Char 6 Session start date (yymmdd)Time TIME Char 6 Session start time (hhmmss)Dur DURATION Num 5 Session duration (seconds)Mailbox MAILBOX Char 10 Mailbox number used in sessionCaller CALLER Char 16 Caller ID (automatic number identification), if knownCallee CALLEE Char 16a, b

32b, cCallee ID (dialed number identification); telephone

number from which the call to the voice processorwas forwarded

CT CALLTYPE Num 2 When outcall or network outcall, contains dialedtelephone number

AT ACCESSTYPE Num 2 Subscriber-access typeTC TERMCODE Num 2 Session-termination codeDestination DEST_ORGN Char 16 When session ends by transferring to another tele-

phone number or mailbox, contains telephonenumber or mailbox

When network call, contains remote-node serial numberand mailbox, with a + character between the values

BX UNSUCXFR Num 2 Total number of unsuccessful transfersMsent MSGSENT Num 5 Total number of messages sent

Mdel MSGDEL Num 5 Total number of messages deleteda File format level 1.b When the outcall number is longer than the number of digits allowed in the CALLEE field, the excessive leading digits are not recorded.c File format level 2.

OUTPUT-FILE STRUCTURES APPENDIX A


Some fields log codes that can be used to interpret the call session. Table A-2 liststhe code number and a description, by the fields that log codes.

Table A-2. Session-Detail Output-File Code Values and Descriptions.

CodeValue Description

Call Type (CT)

0 Call to the voice processor’s direct number from an outside caller1 Direct call to the voice processor from inside the PBX2 Direct call to the voice processor from attendant3 Forwarded calla to the voice processor from busy station number4 Forwarded calla to the voice processor from ring-no-answer or indicates an

incoming call on DID for in-band integration5 Outcall or pager call from the voice processor6 Outgoing network call from the voice processor7 Incoming network call from the voice processor8 Pager outcall9 AMIS outgoing call

10 AMIS incoming call90 System event call set date and time (DTS), initial program load (IPL)99 Unknown call type

Access Type (AT)

0 Subscriber password access1 Secretary password access2 Home password access3 Guest 1 password access4 Guest 2 password access5 Unidentified caller (telephone-answering) access

6 Outcalling without subscriber access8 Voice-messaging mode—no password input. Occurs on initial entry tutorial9 Open trees

10 Network/AMIS access—voice message transmitted11 Network access—special message transmitted12 Network access—copy of voice message transmitted13 Failed network/AMIS transmit

20 Network/AMIS access—voice message received21 Network access—special message received22 Network access—copy of voice message received

23 Failed network/AMIS receive

31 Pager sequence 1

32 Pager sequence 2

33 Pager sequence 3a On some PBX integrations, either call type code 3 or 4 can indicate that the call was forwarded under the

forward-all-calls status.



Table A-2. Session-Detail Output-File Code Values and Descriptions (Continued).


Access Type (AT) (Continued)

34 Pager sequence 4

35 Pager sequence 5

36 Pager sequence 6

37 Pager sequence 7

38 Pager sequence 8

39 Pager sequence 9

40 Pager sequence 10










91 System initial program load

92 System date/time set

99 Unknown

Term Code (TC)

0 Caller hangs up or is disconnected

1 Caller routed to a different mailbox

2 Caller transfers to an attendant from a mailbox by pressing “0”

3 Caller transfers to an extension from an ECP mailbox, auto attendant, orby dialing the number

4 Incoming call determined to be a network incoming call

5 Caller exits from mailbox, is still connected to the voice processor, andthen enters another mailbox

6 Caller exits from mailbox, is still connected to the voice processor (opensystem), but disconnects

10 Outcall unsuccessful because of busy line (includes pager outcalls)

11 Outcall unsuccessful because of ring-no-answer (includes pager outcalls)

12 Outcall unsuccessful because of fast busy (includes pager outcalls)

20 Successful network-message transmission, including original voicemessage and all copies transmitted

22 Unsuccessful network-message transmission—other network-transmissionerrors occurred



Table A-2. Session-Detail Output-File Code Values and Descriptions (Continued).


Term Code (TC) (Continued)

23 Unsuccessful network-message transmission, mailbox not found ondestination system

24 Unsuccessful network-message transmission, wrong mailbox type ondestination system

25 Unsuccessful network-message transmission, mailbox full on destinationsystem

26 Unsuccessful network-message transmission, mailbox future delivery fullon destination system

27 Unsuccessful network-message transmission, destination system full28 Unsuccessful network-message transmission, possible bad message

transmitted29 Unsuccessful network-message transmission, message determined bad30 Network-message-transmission call terminated at the request of system

manager31 Network-message-transmission call terminated, low signal measurement32 Network-message-transmission call terminated, low signal-to-noise ratio33 Network-message-transmission call terminated, other line problems34 Network-message-transmission call terminated at the request of other

systems35 Network-message-transmission call terminated, because of system error

(for example, system full)40 AMIS message retry-transmit later41 AMIS version not supported42 AMIS message invalid response43 AMIS system telephone number blocked by transmission-acceptance table44 No AMIS system telephone number in SMT45 AMIS system telephone number in SMT incorrect46 AMIS end of session failed because of timeout, frame error, protocol error,

or abort47 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 error49 AMIS receive message error (message record initial error, message record

error, or end message error)50 AMIS message returned to sender51 AMIS receiving START frame error52 AMIS receiving PHNUM (phone number) frame error53 AMIS MSGI (message information) frame error54 AMIS protocol error

81 Caller enters one bad password and voice processor terminates the call



Table A-2. Session-Detail Output-File Code Values and Descriptions (Concluded).


Term Code (TC) (Concluded)

82 Caller enters two bad passwords and voice processor terminates the call

83 Caller enters three bad passwords and voice processor terminates the call

91 Session terminated by system initial program load (IPL)

92 Session terminated by system-reset scanner channel

93 Session terminated by system trees restart

94 IPL power failure

95 IPL system 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 Unidentified call termination

A.2 UNSUCCESSFUL-TRANSFER-OCCURRENCEOUTPUT-FILE STRUCTURE

The unsuccessful-transfer-occurrence output file contains one record for everyoccurrence of an unsuccessful transfer. Unsuccessful transfer files are named withthe convention Xyymmdd.ASC or .DBF. Table A-3 shows the file structure. Table A-4indicates the reasons an attempted transfer was unsuccessful.

Table A-3. Unsuccessful-Transfer-Occurrence Output-File Structure.


dBASE IIIField Name

DataType


SyId SYSID Char 4 Voice processor serial number (last 4 digits)Prt PORTID Char 3 Port used for sessionDate XFRDATE Char 6 Date of occurrence (yymmdd format)Time XFRTIME Char 6 Time of occurrence (hhmmss format)Mailbox MAILBOX Char 10 Mailbox number attempting transferRC REASON Num 2 Unsuccessful transfer code

TnTried TM_TRIED Char 16 Attempted telephone number



Table A-4. Unsuccessful-Transfer-Occurrence Output-File Code Values and Descriptions.


2 Busy

3 Not answered

4 Fast busy or extension not in service

5 Transfer answered by voice processor

8 Operator busy

9 Operator does not answer

10 Operator fast busy

11 Operator transfer answered by voice processor

A.3 MESSAGE-DETAIL OUTPUT-FILE STRUCTURE

The message-detail output files contain records for every message that is sent fromor deleted in a mailbox or in a network call session. Message-detail output files arenamed with the convention Myymmdd.ASC or DBF. Table A-5 lists the field names,their data type, length, and description. Table A-6 shows the action-code values anddescriptions.

Table A-5. Message-Detail Output-File Structure.


dBASE IIIField Name

DataType


SyId SYSID Char 4 Voice processor serial number (last 4 digits)Prt PORTID Char 3 Port used for sessionDate DATE Char 6 Date of occurrence (yymmdd format)Time TIME Char 6 Time of occurrence (hhmmss format)Mailbox MAILBOX Char 10 Mailbox numberLen LENGTH Num 5 Total message length (seconds)

Ac ACTION Num 2 Message send/delete action code (Table A-6)SR S_R Num 2 Sender/receiver code (Table A-6)Atr ATTRIB Num 3 Information about message attributes (Table A-6)OthNod OTH_NODE Char 4a

24bNode number; if message sent, destination node

number; if messaged deleted, source node number;if not a networked message, blank

OthBox OTH_BOX Char 10a

16bDestination mailbox number, if message sentSource mailbox number, if message deleted

a File format level 1.b File format level 2.



Table A-6. Message-Detail Output-File Code Values and Descriptions.


Action Code

0 Message deleted by subscriber; message not previously archived1 Message deleted by subscriber; message previously archived2 Message deleted by voice processor; message not previously archived3 Message previously archived4 Message deleted by information service; not archived5 Message deleted by information service; archived

10 Message sent to another mailbox on this voice processor11 Message sent to another mailbox on another voice processor20 Mailbox not found21 Mailbox not a voice-messaging mailbox22 Mailbox full23 Mailbox future-delivery message limit full24 Receiving voice processor full25 Receiving voice-processor node deleted26 Receiving voice-processor node disabled with the request to return all

messages27 Message determined bad when received at destination voice processor28 Receiving voice-processor node unable to receive message because node

line continuously busy29 Receiving voice-processor node line does not answer (ring-no-answer)30 Receiving voice-processor node line continuously bad line50 Networked message transmission, no errors51 Networked message transmission, mailbox not found52 Networked message transmission, not a voice-messaging mailbox53 Networked message transmission, mailbox full54 Networked message transmission, future-delivery limit exceeded55 Networked message transmission, receiving system full58 Networked message transmission, message bad60 Networked message transmission, transmission (TX) error65 AMIS could not pass the failed start sequence66 AMIS wrong number67 Remote system does not support AMIS68 AMIS version not supported by remote system69 AMIS system-access telephone number rejected by remote system70 AMIS bad telephone number in SMT71 AMIS message too long72 AMIS message does not exist in remote system73 AMIS remote mailbox not accepting this message74 AMIS remote system sent cutoff75 AMIS bad message

99 Unknown



Table A-6. Message-Detail Output-File Code Values and Descriptions (Concluded).


Sender Only/Receiver (S_R)

0 Message sent from outside caller to subscriber’s mailbox1 Message sent from one subscriber’s mailbox to another subscriber’s mailbox2 Message sent from home mailbox to subscriber’s mailbox3 Message sent from guest 1 mailbox to subscriber’s mailbox4 Message sent from guest 2 mailbox to subscriber’s mailbox5 Message sent to home subscriber’s mailbox from subscriber’s mailbox6 Message sent to guest 1 mailbox from subscriber’s mailbox

7 Message sent to guest 2 mailbox from subscriber’s mailbox8 Message from information service to subscriber

20 Network message returned to sender’s mailbox50 Network transmission voice51 Network transmission copy52 Network transmission special message60 AMIS send

61 AMIS voice transmitted62 AMIS message returned to sender

99 Unknown

Attribute (ATTRIB)a

0 No attributes assigned to message4 Future delivery requested8 Message forwarded from another subscriber

16 Confirmation of nondelivery requested

32 Confirmation of delivery requested64 Message marked private

128 Message marked urgenta Add code values to determine which attributes are set. For example, for a message marked private (64), ur-

gent (128), and with confirmation of delivery requested (32), the total is 224.

A.4 INDIVIDUAL-PORT-STATISTICS OUTPUT-FILESTRUCTURE

The daily individual-port-statistics files contain two records for every 15-minuteperiod. The first record, labeled N, contains the number of calls that began on eachport for 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. Individual-port output files are named with the convention Pyymmdd.ASC or .DBF. Table A-7and Table A-8 describe the file structure for individual-port-statistics output files.



Table A-7. Individual-Port-Statistics Output-File Structure for Voice-Processing Modules.


dBASE IIIField Name

DataType


T TYPE Char 1 Value equals N (number of calls) or valueequals T (number of seconds/time)

SyId SYSID Char 4 Voice-processor serial numberDate 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)O1A PO1A Num 3 Number of calls or seconds (Port 1A)O1B PO1B Num 3 Number of calls or seconds (Port 1B)O1C PO1C Num 3 Number of calls or seconds (Port 1C)O1D PO1D Num 3 Number of calls or seconds (Port 1D)O2A PO2A Num 3 Number of calls or seconds (Port 2A)O2B PO2B Num 3 Number of calls or seconds (Port 2B)O2C PO2C Num 3 Number of calls or seconds (Port 2C)

O2D PO2D Num 3 Number of calls or seconds (Port 2D)O3A PO3A Num 3 Number of calls or seconds (Port 3A)O3B PO3B Num 3 Number of calls or seconds (Port 3B)O3C PO3C Num 3 Number of calls or seconds (Port 3C)O3D PO3D Num 3 Number of calls or seconds (Port 3D)O4A PO4A Num 3 Number of calls or seconds (Port 4A)O4B PO4B Num 3 Number of calls or seconds (Port 4B)

O4C PO4C Num 3 Number of calls or seconds (Port 4C)O4D PO4D Num 3 Number of calls or seconds (Port 4D)O5A PO5A Num 3 Number of calls or seconds (Port 5A)O5B PO5B Num 3 Number of calls or seconds (Port 5B)O5C PO5C Num 3 Number of calls or seconds (Port 5C)O5D PO5D Num 3 Number of calls or seconds (Port 5D)

. . . . .

. . . . .

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



Table A-8. Individual-Port-Statistics Output-File Structure for OctelXC1000 and Sierra.


dBASE IIIField Name

DataType


T TYPE Char 1 Value equals N (number of calls) or valueequals T (number of seconds/time)

SyId SYSID Char 4 Voice-processor serial numberDate 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)O1A PO1A Num 3 Number of calls or seconds (Port 1A)O1B PO1B Num 3 Number of calls or seconds (Port 1B)O1C PO1C Num 3 Number of calls or seconds (Port 1C)O1D PO1D Num 3 Number of calls or seconds (Port 1D)O1E PO1E Num 3 Number of calls or seconds (Port 1E)O1F PO1F Num 3 Number of calls or seconds (Port 1F)O1G PO1G Num 3 Number of calls or seconds (Port 1G)O1H PO1H Num 3 Number of calls or seconds (Port 1H)O1I PO1I Num 3 Number of calls or seconds (Port 1I)O1J PO1J Num 3 Number of calls or seconds (Port 1J)O1K PO1K Num 3 Number of calls or seconds (Port 1K)O1L PO1L Num 3 Number of calls or seconds (Port 1L)O2A PO2A Num 3 Number of calls or seconds (Port 2A)O2B PO2B Num 3 Number of calls or seconds (Port 2B)O2C PO2C Num 3 Number of calls or seconds (Port 2C)O2D PO2D Num 3 Number of calls or seconds (Port 2D)O2E PO2E Num 3 Number of calls or seconds (Port 2E)O2F PO2F Num 3 Number of calls or seconds (Port 2F)O2G PO2G Num 3 Number of calls or seconds (Port 2G)O2H PO2H Num 3 Number of calls or seconds (Port 2H)O2I PO2I Num 3 Number of calls or seconds (Port 2I)O2J PO2J Num 3 Number of calls or seconds (Port 2J)O2K PO2K Num 3 Number of calls or seconds (Port 2K)O2L PO2L Num 3 Number of calls or seconds (Port 2L)

. . . . .

. . . . .

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



A.5 FORMS OUTPUT-FILE STRUCTURE

The forms output-file structure contains data related to calls into the DTMF formsmailbox. Forms output files are named Forms.ASC or .DBF. Table A-9 describesthe file structure for the forms output files. For detailed information about usingforms output-file data, refer to the DTMF Manual.

Table A-9. Forms Output-File Structure.


dBASE IIIField Name

DataType


Prt PORT Char 3 Port used for session (disregard entriesfor port 255)a

Date DATE Char 6 Session start date (yymmdd format)Time TIME Char 6 Session start time (hhmmss format)

Seq SEQUENCE Num 3 Mailbox sequence trackingMailbox MAILBOX Char 10 Type 12 mailboxQues QUESTION Num 4 OctelForms question number, from

mailbox setup through the voiceprocessor

Answer ANSWER Char 16 Caller touch-tone responses to Octel-Forms questions

a Port 255 represents special information used by service engineers.

B

B-1Edition ThreeOctel PC/CDR

CDF EVENT-RECORD DESCRIPTION

All Octel PC/CDR event records contain the port number, the (coded) date and timewhen the event occurred, and other information pertinent to each record type. Thevoice-processor software release determines the event records displayed. Table B-1lists the record-type abbreviations and their corresponding descriptions listedalphabetically by record-type abbreviation. Table B-2 lists the record-type abbrevi-ations and their corresponding descriptions in numerical sequence by event-recordcode. Table B-3 shows the contents of each record type in the CDF (collated dayfile). Within these descriptions, the term AMIS refers to the intervendor networkprotocol, and the term OctelNet refers to Octel proprietary network protocol.References to port 255 refer to system events unrelated to ports on the voiceprocessor.


Table B-1. Event Records Alphabetized by Abbreviation.

Record-TypeAbbreviation

Event-RecordCode

Record-Type Description

AM_DIR_FULL 167 AMIS directory 90% fullAM_EAR_FULL 168 AMIS EAR (extended address record) array 90% fullAM_RCV_EOS 164 Received an end of AMIS sessionAM_RCV_FC 155 Received AMIS function codeAM_RCV_FR 157 Status of received AMIS frameAM_RCV_IC 162 Incoming AMIS callAM_RCV_INVPH 163 Received an invalid AMIS system-access telephone

numberAM_RCV_MSG 161 Received AMIS message-recording statusAM_RCV_MSGI 160 Received AMIS message attributeAM_RCV_PHNUM 159 Caller’s AMIS system-access telephone numberAM_RCV_RESP 156 Acknowledgment sent for AMIS-received frameAM_RCV_START 158 Received AMIS start sessionAM_RTS 166 AMIS message returned to senderAM_SEND 165 AMIS message queuedAM_XMT_EOM 146 Transmitted end of AMIS-message frameAM_XMT_EOS 147 Transmitted end of AMIS sessionAM_XMT_MBOX 144 AMIS logged bad sender’s mailbox numberAM_XMT_MINFO 143 Transmitted AMIS message informationAM_XMT_OC 140 Start of AMIS outcallAM_XMT_PHNUM 142 Transmitted AMIS voice-processor telephone numberAM_XMT_RESP 148 Acknowledgment received from voice processorAM_XMT_START 141 Transmitted AMIS start session

APPENDIX BCDR EVENT-RECORD DESCRIPTION

B-2 Edition Three Octel PC/CDR

Table B-1. Event Records Alphabetized by Abbreviation (Concluded).

Record-TypeAbbreviation

Event-RecordCode

Record-Type Description

AM_XMT_VOICE 145 AMIS transmitted voiceBN_EOS 89 OctelNet end of sessionBN_IC 65 Incoming call from OctelNet nodeBN_OC 64 Outcall to an OctelNet nodeBN_RCV_CP 83 OctelNet message copy receivedBN_RCV_HDR 81 OctelNet message header receivedBN_RCV_SP 82 OctelNet special message receivedBN_RCV_START 80 OctelNet receive mode startBN_RCV_VOICE 84 OctelNet voice receivedBN_RTS 90 OctelNet message returned to senderBN_XMT_CP 73 OctelNet message copy transmittedBN_XMT_HDR 71 OctelNet message header transmittedBN_XMT_SP 72 OctelNet special message transmittedBN_XMT_START 70 OctelNet transmit mode startedBN_XMT_VOICE 74 OctelNet message voice transmittedCALLER 16 Caller identificationCDRCFG 2 CDR configurationDTS 1 Set date and timeFCE 28 OctelForms mailbox end of sessionIC 17 Incoming callIPL 0 Voice-processor initial program loadMD 49 Message deleteMS 48 Message sentMW 18 Message waiting set/clearOC 19 Outcall to subscriber/pagerON_HOOK 20 Port goes on hookPWT 21 Password testPWT_RJCT 129 Bad password limitRSS 22 Reset scanner-board channelSEIZE 23 Seize port for outgoing callSMS 24 Session mode setTIGON 29 Used by Tigon onlyTNE 25 Trees normal entryTREES_FCD 132 Forms mailbox call dataTREES_FMB 131 Forms mailbox numberTREES_FQA 130 Forms mailbox question/answerTRS 26 Trees restart entryXFR 27 Transfer

APPENDIX B CDR EVENT-RECORD DESCRIPTION


Table B-2. Event Records in Numerical Sequence by Event-Report Code.

Event-RecordCode

Record-TypeAbbreviation Record-Type Description

0 IPL Voice processor initial program load1 DTS Set date and time2 CDRCFG CDR configuration

16 CALLER Caller identification17 IC Incoming call18 MW Message waiting set/clear19 OC Outcall to subscriber/pager20 ON_HOOK Port goes on hook21 PWT Password test22 RSS Reset scanner channel23 SEIZE Seize port for outgoing call24 SMS Session mode set25 TNE Trees normal entry26 TRS Trees restart entry27 XFR Transfer28 FCE OctelForms mailbox end of session29 TIGON Used by Tigon only48 MS Message sent49 MD Message deleted64 BN_OC Outcall to an OctelNet node65 BN_IC Incoming call from OctelNet node70 BN_XMT_START OctelNet transmit mode started71 BN_XMT_HDR OctelNet message header transmitted72 BN_XMT_SP OctelNet special message transmitted73 BN_XMT_CP OctelNet message copy transmitted74 BN_XMT_VOICE OctelNet message voice transmitted80 BN_RCV_START OctelNet receive mode start81 BN_RCV_HDR OctelNet message header received82 BN_RCV_SP OctelNet special message received83 BN_RCV_CP OctelNet message copy received84 BN_RCV_VOICE OctelNet voice received89 BN_EOS OctelNet end of session90 BN_RTS OctelNet message returned to sender

129 PWT_RJCT Bad password limit130 TREES_FQA Forms mailbox question/answer131 TREES_FMB Forms mailbox number132 TREES_FCD Forms mailbox call data140 AM_XMT_OC Start of AMIS outcall141 AM_XMT_START Transmitted AMIS start session142 AM_XMT_PHNUM Transmitted AMIS voice-processor telephone number143 AM_XMT_MINFO Transmitted AMIS message info

144 AM_XMT_MBOX AMIS logged bad sender’s mailbox number



Table B-2. Event Records in Numerical Sequence by Event-Report Code (Concluded).

Event-RecordCode

Record-TypeAbbreviation Record-Type Description

145 AM_XMT_VOICE AMIS transmitted voice146 AM_XMT_EOM Transmitted end of AMIS message frame147 AM_XMT_EOS Transmitted end of AMIS session148 AM_XMT_RESP Acknowledgment received from voice processor155 AM_RCV_FC Received AMIS function code156 AM_RCV_RESP Acknowledgment sent for AMIS received frame157 AM_RCV_FR Status of received AMIS frame158 AM_RCV_START Received AMIS start session159 AM_RCV_PHNUM Caller’s AMIS system-access telephone number160 AM_RCV_MSGI Received AMIS message attribute161 AM_RCV_MSG Received AMIS message-recording status162 AM_RCV_IC Incoming AMIS call163 AM_RCV_INVPH Received an invalid AMIS system-access telephone

number164 AM_RCV_EOS Received an end of AMIS session165 AM_SEND AMIS message queued166 AM_RTS AMIS message returned to sender167 AM_DIR_FULL AMIS directory 90% full168 AM_EAR_FULL AMIS EAR (extended address record) array 90% full



Table B-3. Event-Record Details.

Events 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 is logged with this event.

AM_RCV_EOS (Received an end of AMIS session)

Port: Voice-processor port number used

SF: Success/Failure code

0 – OK1 – Frame length error2 – Data error

LD: Length/Data, depends on SF value

AM_RCV_FC (Received AMIS function code)


Status: Status code for receive function code event

1 – Start session2 – System number3 – Message information4 – End message5 – Protocol extension6 – End session

255 – Unknown

AM_RCV_FR (Status of received AMIS frame)


Status: Status code for receive frame event

0 – OK1 – Checksum error2 – Disconnect3 – Timeout error4 – Frame length error5 – Data error6 – Function code error7 – Start digit timeout8 – Internal error

255 – Unknown

Data: Invalid data or invalid function code, otherwise unused

AM_RCV_IC (Incoming AMIS call)




Table B-3. Event-Record Details (Continued).

Events Description

AM_RCV_INVPH (Received an invalid AMIS telephone number)


Status: Status code for invalid telephone numbers

1 – Country code error2 – Not pound-terminated3 – Did not contain three pound signs4 – Data length error

255 – Unknown

Len: Length, used only if error in length of telephone number

AM_RCV_MSG (Received AMIS message-recording status)


Status: Message received status code

0 – OK1 – Message record initial error2 – Message recorded error3 – End message error

255 – Unknown

AM_RCV_MSGI (Received AMIS message attribute)


Msgt: 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: Message length received, in minutes

Send: Sender’s mailbox number

Recp: Recipient’s mailbox number

Status: Status code for message attributes

0 – OK1 – Message too long2 – No such mailbox3 – Not accepted4 – Mailbox full5 – Internal error

255 – Unknown




Events Description

AM_RCV_PHNUM (Caller’s AMIS telephone number)


Number: Telephone number

Status: 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 – Unknown

AM_RCV_RESP (Acknowledgment sent for AMIS received frame)


Status: 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 (Received AMIS start session)


Status: Status code for start session

0 – Successful1 – AMIS not installed on this system2 – Disk full3 – Version not supported4 – Protocol error

255 – Unknown

AM_RTS (AMIS message returned to sender)




TOD: Date and time stamp (delivery time in minutes since 1/1/84)

MsgID1: ID of first message segment




Events Description

AM_RTS (AMIS message returned to sender) (concluded)

MsgID2: ID of second message segment

Len: Total message-segment length

SegCount: Total number of segments in message

Number: Sender or recipient telephone number

PhType: Type of telephone number

Why: Reason for return

1 – Ring no answer2 – Busy3 – Bad line4 – Could not pass wakeup setup5 – Wrong number6 – Remote disk full7 – Remote not supporting AMIS8 – Remote not supporting version9 – Remote system rejected this call

10 – Telephone number wrong in SMT11 – Remote identify message too long12 – Remote mailbox not found13 – Remote mailbox won’t accept this message14 – Remote mailbox full15 – Remote sent cutoff16 – Bad message

255 – Unknown

AM_SEND (AMIS message queued)


Type: Type of message

0 – Real message255 – Unknown

Attr: Attribute of message

0 – Forwarded message

SR: Send/receive information

0 – From Octel subscriber to AMIS destination1 – From AMIS destination to Octel subscriber



TOD: Date and time stamp (in minutes since 1/1/84)



Len1: First message segment length

LenRest: Total length of remaining segments




Events Description

AM_SEND (AMIS message queued) (concluded)


Number: Sender or recipient telephone number

PhType: Type of telephone number

AM_XMT_EOM (Transmitted end of AMIS message frame)


Status: Status code for end of message transmit

0 – Successful2 – Message too long3 – Mailbox does not exist4 – Mailbox not accepting AMIS5 – Mailbox full6 – Internal error7 – Invalid response

255 – Unknown response

AM_XMT_EOS (Transmitted end of AMIS session)


Routine: For internal use only

Status: End of session status code

0 – Successful1 – Time out2 – Frame error3 – Protocol error4 – Abort

255 – Unknown

AM_XMT_MBOX (AMIS logged bad sender’s mailbox)


IUN: Mailbox IUN

AM_XMT_MINFO (Transmitted AMIS message information)




Len: Message length rounded to minute




Events Description

AM_XMT_MINFO (Transmitted AMIS message information) (concluded)

Status: 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)

Port: Voice-processor port number

Number: AMIS system access telephone number dialed

DialSequence:

AMIS dial sequence with authorization code

PhType: Telephone number type

0 – Local1 – Long distance2 – International3 – Private number

255 – Unknown number

Status: 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 (Transmitted AMIS voice-processor telephone number)


Number: AMIS system-access telephone number used

Status: 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)





Events Description

AM_XMT_RESP (Acknowledgment received from voice processor)


Status: Status code for response from remote system

0 – Time out getting start digit1 – Time out getting response frame2 – Remote disconnect3 – Check digit error in received frame4 – Remote sent accept5 – Remote sent retransmit6 – Remote sent timeout7 – Remote sent frame error8 – Remote sent protocol error9 – Remote sent abort

10 – Remote sent valid response number 2, 3, 4, or 511 – Remote sent invalid-response code12 – Retransmitted 3 times, remote wants again

AM_XMT_START (Transmitted AMIS start session)


Status: AMIS outcall-start status code

0 – Successful1 – Retry later2 – Disk full on receiving system3 – No networking4 – AMIS version not supported5 – Invalid response from receiving system


AM_XMT_VOICE (AMIS transmitted voice)




Len: First message segment length


Stime: Transmission start time

Etime: Transmission end time

Status: Status code for transmit voice

0 – Successful1 – Cutoff key received2 – Message deleted

255 – Unknown returned code




Events Description

BN_EOS (OctelNet end of session)


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 voice processor

254 – Session terminated on system errors255 – Session terminated on unknown errors

BN_IC (Incoming call from OctelNet node)


BN_OC (Outcall to an OctelNet node)


Node: Node number of node called (1-500)

Serial: Serial number

Number: Telephone number dialed

DialSequence: Dial sequence with authorization code

Stat: Outcall status code

0 – Outcall answered (receiver off-hook detected)1 – Busy detected2 – Fast busy detected3 – Ring-no-answer detected4 – Unknown (assumed answered)

255 – Outcall failed and port going on-hook

BN_RCV_CP (OctelNet message copy received)


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 message will be delivered




Events Description

BN_RCV_CP (OctelNet message copy received) (concluded)

Stat: Copy receive 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 voice processor full

254 – Message not copied, network transmission error255 – Message not copied, other error

BN_RCV_HDR (OctelNet message header received)


Source: Source mailbox number







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 exceeded

254 – Network transmission error255 – Unknown error

BN_RCV_SP (OctelNet special message received)


Type: Special message-type-indication code

0 – Confirmation of message delivery (the date/time fieldindicates when the confirmation of delivery request washeard)

1 – Confirmation of nondelivery (the date/time field indicateswhen the confirmation of delivery request was sent)






Events Description

BN_RCV_SP (OctelNet special message received) (concluded)

TOD: Date and time

Stat: Special message-receive status code

0 – Successful1 – Requested destination mailbox does not exist2 – Wrong mailbox type (not a voice-messaging mailbox)3 – Destination mailbox full4 – Destination box future-delivery limit exceeded


BN_RCV_START (OctelNet receive mode start)



Serial: Serial number of remote voice processor

BN_RCV_VOICE (OctelNet voice received)


MsgID: Internal message identifier

Len: Length of first voice segment (seconds; contains –1 if length ofsegment is too long for internal encoding)

Stime: Send start date and time

Etime: Receive start date and time

Stat: Header-received status code

0 – Successful, message received and sent to first mailbox1 – Not successful, destination mailbox deleted before

message could be sent to it3 – Not successful, destination mailbox became full before

message could be sent to it4 – Not successful, destination mailbox future-delivery limit

exceeded5 – Not successful, destination voice processor became full

during voice transmission/recording6 – Not successful, bad message or network transmission

problems during voice recording254 – Not successful, bad message or network transmission

problems after voice recording

BN_RTS (OctelNet message returned to sender)


Node: Target node number of attempted transmission

Serial: Serial number of the target node (if known)






Events Description

BN_RTS (OctelNet message returned to sender) (concluded)





TOD: Date and time message to be delivered

MsgID1: Internal message identifier, first segment

MsgID2: Internal message identifier, second segment

Len1:a Total number of seconds of original message or introductory message (contains –1 if length of segment is too long for internal encoding)

Len2:a Total number of seconds of original message (contains –1 if length of segment is too long for internal encoding or 0 if no segments follow the first)

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 line

255 – Unspecified return reason

BN_XMT_CP (OctelNet message copy transmitted)







a If Len2 is blank, Len1 equals the total number of seconds of the original message. However, if the message has beencopied, the original length moves to Len2, and the length of the introduction becomes the new Len1.




Events Description

BN_XMT_CP (OctelNet message copy transmitted) (concluded)

TOD: Date and time message will be deliveredStat: 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, voice processor full


BN_XMT_HDR (OctelNet message header transmitted)

Port: Voice-processor port numberSource: Source mailbox number

Dest: Destination (receiver) mailbox numberAttr: Message-attribute flag codes (sum of values)




TOD: 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 exceeded


BN_XMT_SP (OctelNet special message transmitted)

Port: Voice-processor port numberType: Special message-type-indication code

0 – Confirmation of message delivery (the date/time fieldindicates when the confirmation of delivery request washeard)

1 – Confirmation of nondelivery (the date/time field indicateswhen the confirmation of delivery request was sent)

Source: Source mailbox numberDest: Destination (receiver) mailbox number




Events Description

BN_XMT_SP (OctelNet special-message transmitted) (concluded)


Stat: Special-message-transmit status code0 – Successful1 – Requested destination mailbox does not exist2 – Wrong mailbox type (not a voice-messaging mailbox)3 – Destination mailbox full4 – Sending voice processor full


BN_XMT_START (OctelNet transmit mode started)



Serial: Serial number of remote voice processor

BN_XMT_VOICE (OctelNet message voice transmitted)


MsgID1: Internal message identifier, first segment

MsgID2: Internal message identifier, second segment

Len1:a Total number of seconds of original message or introductorymessage (contains –1 if length of segment is too long for internalencoding)

Len2:a Total number of seconds of original message (contains –1 if lengthof segment is too long for internal encoding or 0 if no messagesfollow the first)

SegCT: Total number of segments in message

Stime: Transmit start date and time

Etime: Transmit end date and time

Stat: Transmit status code0 – Successful, message transmitted and sent to first mailbox1 – Not successful, destination mailbox deleted before

message could be sent to it3 – Not successful, destination mailbox future-delivery limit

exceeded4 – Not successful, receiving voice processor became full

during voice transmission/recording to destination system6 – Not successful, bad message or network transmission

problems during voice transmission254 – Not successful, bad message or network transmission

problems after voice transmission

a If Len2 is blank, Len1 equals the total number of seconds of the original message. However, if themessage has been copied, the original length moves to Len2, and the length of the introductionbecomes the new Len1.




Events Description

CALLER (Caller identification)


ID: Calling party telephone number

CDRCFG (CDR configuration)

Bits: Hexadecimal dump showing the event record code. Thisinformation can be found in SMT menu 16.1.4.

DTS (Set date and time)


Old: System date and time before change

New: System date and time after change

Reason: Code indicating reason for change of clocks

0 – Clock setting in a newly installed voice processor1 – Clock not valid when voice processor booted, system

manager forced to set clock2 – Clock changed by system manager

FCE (OctelForms mailbox end of session)


IC (Incoming call)


IPL (Voice processor initial program load)

Port: Voice processor assigns port number 255

Boot: Boot code used on system manager terminal to boot voiceprocessor (ASCII code or null for autoboot)

Reason: Code indicating reason for IPL0 – Reason not known1 – Power failed2 – System crashed (Interrupt 3)3 – Memory parity failure4 – Voice processor shut down by system manager

DownTime: Shutdown time

Level: CDR format level of all following CDR records

Serial: Voice-processor serial number

MD (Message delete)





Events Description

MD (Message delete) (concluded)

Time: If message not archived when deleted, field indicates the date and timeof delivery

Box: Mailbox number from which message deleted

Why: Code indicates why message deleted

0 – Deleted by user1 – Deleted by purge task

Type: Code indicates type of message

0 – Real message255 – Unknown type (internal error)

Stage: Stage of delivery

0 – Delivered; includes internal stages (future delivery, networkreturned message, delivered, and heard)

1 – Archived message255 – Unknown (internal error)

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 receiver

MsgID1: Internal identifier of message segment

Len1:a Total number of seconds of original message or introductory message(contains –1 if length of segment is too long for internal encoding)

Len2:a Total number of seconds of original message (contains –1 if length ofsegment is too long for internal encoding or 0 if no messages follow thefirst)


MS (Message sent)


Time: Date and time when message will be delivered

DstBox: Mailbox number (receiver) to which message sent

SrcBox: Originating mailbox number from which message sent

Type: Code indicates type of message

0 – Real message255 – Unknown type (internal error)

a 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 the introduction becomes the new Len1.




Events Description

MS (Message sent) (concluded)




128 – Message marked urgent136 – Forwarded urgent message

Snd/Rcv: Code indicating sender and receiver type 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 receiverMsgID1: Internal identifier of first message segmentMsgID2: Internal message identifier (second segment)

Len1:a Total number of seconds of original message or introductory message(contains –1 if length of segment is too long for internal encoding)

Len2:a Total number of seconds of original message (contains –1 if length ofsegment is too long for internal encoding or 0 if no messages follow thefirst)

SegCT: Total number of segments in messageDstNode: Destination network node ID (0–this system or 1-500)SrcNode: Source network node ID (0–this system or 1-500)

MW (Message waiting set/clear)

Port: Voice-processor port numberBox: Mailbox number generating MW signalExt: Telephone number signaledDir: Code for setting and clearing MW indicator

0 – Set off1 – Set on

Stat: Set/Clear action result code

0 – PBX successfully told to turn light on1 – 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

a 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 the introduction becomes the new Len1.




Events Description

OC (Outcall to subscriber/pager)


Box: Mailbox number generating outcall

Sched: Outcall schedule used

0 – Temporary schedule1 – Outcall schedule 1 used2 – Outcall schedule 2 used

Number: Telephone number called

Pager: Pager code sequence used

0 – No pager used1 – Pager sequence 1 used2 – Pager sequence 2 used3 – Pager sequence 3 used

Stat: Result code of outcall

0 – Call answered1 – Telephone number dialed; busy2 – Telephone number dialed; ring-no-answer3 – Telephone number dialed; fast busy

ON_HOOK (Port goes on hook)


PWT (Password test)


Box: Mailbox number used for sign in

Result: Password result code

0 – Password valid1 – Password invalid2 – Password valid, but already signed into mailbox

PWType: Password type code used (if valid)

0 – User (subscriber) password code used1 – Secretary password code used2 – Home password code used3 – Guest 1 password code used4 – Guest 2 password code used

PWT_RJCT (Bad password limit)


Box: Mailbox number used for sign in

Threshold: Bad-password-disconnect threshold limit

RSS (Reset scanner channel)





Events Description

SEIZE (Seize port for outgoing call)


SMS (Session mode set)


Box: Mailbox number entered; indicates when a new mailbox has beenentered; blank if caller enters idle mode (open trees)

Mode: Session mode code

0 – Idle, not signed on—open trees1 – Telephone-answering mode2 – Voice-messaging mode

TIGON (Used by Tigon only)

TNE (Trees normal entry)


CallType: Call-type code indicates when an incoming call enters the voiceprocessor

0 – Direct call from outside the PBX/Centrex or for non-integrated systems

1 – Direct call from inside the PBX/Centrex2 – Direct call from attendant3 – Forwarded to the voice processor from a busy line4 – Forwarded to the voice processor from a ring-no-answer

line — either code 3 or 4 can be used for forwarding allcalls; varies by PBX

Caller: Calling party telephone number

Callee: Called party telephone number, if available

TREES_FCD (Forms mailbox call data)

Start: Date and time of beginning of call

Caller: Calling party telephone number

TREES_FMB (Forms mailbox number)


Mailbox: Forms mailbox number

TREES_FQA (Forms mailbox question/answer)


Question: Question reference number (If 9999, indicates caller pressed keyto return to first question in form or previous form)

Answer: Touch-tone response by caller to forms question

TRS (Trees restart entry)


Events Description



Table B-3. Event-Record Details (Concluded).

Events Description

XFR (Transfer)


Src: Source code indicates how the transfer telephone was determined0 – Explicit attendant number given1 – Attendant 1 extension (invalid attendant defined in

mailbox, department, or community)2 – Valid port group defined3 – Port group 1 (invalid port group is defined)4 – Extension given (ECP mailbox)5 – Mailbox attendant extension6 – Group attendant extension7 – Community attendant extension

Ext: Extension transferred to

Stat: Transfer status code0 – 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

voice processor6 – Operator blind transfer, no answer supervision7 – Operator transfer, answered8 – Operator transfer, telephone number busy9 – Operator transfer, telephone number not answered

10 – Operator transfer, telephone number fast busy11 – Operator transfer, telephone number detected, answered

by the voice processor

C

C-1Edition ThreeOctel PC/CDR

CDR EVENT BYTE SIZES BY RECORD GROUP

The tables in this appendix list the specific events included in each of the recordselections listed in Chapter Two, Figure 2-6. Consider the approximate bytes andthe available buffer and PC storage space when selecting record groups to becollected.


Table C-1. Bytes for Events in Session-Related Records.

Event Name DescriptionApprox.Bytes

CALLER Caller identification 15

CDRCFG CDR configuration 38DTS Set date and time 15IC Incoming call 7

IPL Voice-processor initial program load 24

OC Outcall to subscriber/pager 30

ON_HOOK Port goes on hook 7

PWT Password test 17

RSS Reset scanner-board channel 7

SEIZE Seize port for outgoing call 7

SMS Session mode set 16

TNE Trees normal entry 24

TRS Trees restart entry 7

XFR Transfer 17

Table C-2. Bytes for Events in Message Send/Delete Records.


AM_SEND AMIS message queued 56

CDRCFG CDR configuration 38DTS Set date and time 15

IPL Voice-processor initial program load 24MD Message delete 32

MS Message sent 47

APPENDIX CCDR EVENT BYTE SIZES BY RECORD GROUP

C-2 Edition Three Octel PC/CDR

Table C-3. Bytes for Events in Networking-Related Records.


AM_DIR_FULL AMIS directory 90% full 6

AM_EAR_FULL AMIS EAR (extended address record) array 90% full 6

AM_RCV_EOS AMIS received an end AMIS of session 9

AM_RCV_FC Received AMIS function code 8

AM_RCV_FR Status of received AMIS frame 9

AM_RCV_IC Incoming AMIS call 7

AM_RCV_INVPH Received an invalid AMIS system-access telephonenumber

9

AM_RCV_MSG Received AMIS message-recording status 8

AM_RCV_MSGI Received AMIS message attribute 27

AM_RCV_PHNUM Caller’s AMIS system-access telephone number 20

AM_RCV_RESP Acknowledgment sent for AMIS-received frame 8

AM_RCV_START Received AMIS start session 8

AM_RTS AMIS message returned to sender 52

AM_XMT_EOM AMIS transmitted end of AMIS message frame 8

AM_XMT_EOS Transmitted end of AMIS session 9

AM_XMT_MBOX AMIS logged bad sender’s mailbox number 9

AM_XMT_MINFO Transmitted AMIS message information 25

AM_XMT_OC Start of AMIS outcall 51

AM_XMT_PHNUM Transmitted AMIS voice-processor telephonenumber

20

AM_XMT_RESP Acknowledgment received from voice processor 8

AM_XMT_START Transmitted AMIS start session 8

AM_XMT_VOICE AMIS transmitted voice 28

BN_EOS OctelNet end of session 20

BN_IC Incoming call from OctelNet node 7

BN_OC Outcall to an OctelNet node 62

BN_RCV_CP OctelNet message copy received 20

BN_RCV_HDR OctelNet message header received 28

BN_RCV_SP OctelNet special message received 28

BN_RCV_START OctelNet receive mode started 19

BN_RCV_VOICE OctelNet voice received 22

BN_RTS OctelNet message returned to sender 54

BN_XMT_CP OctelNet message copy transmitted 20

BN_XMT_HDR OctelNet message header transmitted 28

BN_XMT_SP OctelNet special message transmitted 28

BN_XMT_START OctelNet transmit mode start 19

BN_XMT_VOICE OctelNet message voice transmitted 30

CDRCFG CDR configuration 38

DTS Set date and time 15


APPENDIX C CDR EVENT BYTE SIZES BY RECORD GROUP

C-3Edition ThreeOctel PC/CDR

Table C-4. Bytes for Events in Invalid Password-Disconnect Records.





PWT_RJCT Bad password limit 17

Table C-5. Bytes for Events in Message-Waiting Notification Records.





MW Message waiting set/clear 25

Table C-6. Bytes for Events in DTMF Forms Mailbox Records.




FCE OctelForms mailbox end of session 7

IPL Voice-processor initial program load 24TREES_FCD Forms mailbox call data 19

TREES_FMB Forms mailbox number 15

TREES_FQA Forms mailbox question/answer 17

Table C-7. Bytes for Miscellaneous Events.


TIGON For Tigon use only 17

D

D-1Edition ThreeOctel PC/CDR

SUBDIRECTORY FILES

These tables list the files copied during installation from the Octel PC/CDR disketteto the PC hard-disk drive. Table D-1 lists the files in the OCTELCDR subdirectory.Table D-2 lists the files in the MIR subdirectory. Table D-3 lists the files in the CCsubdirectory. The LOG subdirectory contains one file, SCHEDCDR.LOG. TheSCHEDCDR.LOG file is created after a scheduled download has occurred.

Table D-1. OCTELCDR Subdirectory Files.

File Names File Names

CDRCLEAN BAT COMPRSM EXEMKCDRSYS BAT COMPRSP EXERMCDRSYS BAT COMPRSU EXELOGO DAT COPYBCF EXESYSNAME DAT DUMPBCF EXECDFS EXE DUMPSF EXECDR EXE DV_MAIN EXECDRERASE EXE LOGO EXECDRHELP EXE MIRROR EXECDRMENU EXE SCHEDCDR EXECDRSYSNM EXE SCHEDEDT EXECHKREV EXE MIRROR HLPCOLLATE EXE CDRP SNCOMPRSB EXE ANSI SYSCOMPRSF EXE

Table D-2. MIR Subdirectory Files.


VT100 MEF CDRDOWNL XTSWY50SPEC MEF LINKSMT XTSCDRDOWNL XTK LOGOFF XTSLANGUAGE XTK

Table D-3. CC Subdirectory Files.


CC30 CFG CCINSTAL EXEMM30 CFG CCLOG EXEMODEM DSC CCREMOVE EXECC EXE CCSECURE EXE

E

E-1Edition ThreeOctel PC/CDR

TRANSMISSION MESSAGESThe following transmission messages can occur when downloading data from avoice processor.

E.1 TRANSMISSION MESSAGES FROM THE VOICEPROCESSOR

There are older unread blocks than the starting block specified.

REASON: A starting block number not sequentially following the last blockretrieved is not permitted, as this will create or leave a gap in theCDR record blocks downloaded from the voice processor.

ACTION: Enter either the next block number of data not previously retrieved oran earlier block number. Use SMT menu 16.1.1 to determine thesevalues.

Starting block number is not valid.

REASON: Either an improper starting block number was used in SMT menu16.1.2 or data has been overwritten.

ACTION: Use SMT menu 16.1.1 to display current, valid block numbers, thenrefer to section 6.2.1 or 6.3 to modify the starting block and restart thetransfer process. If data has been overwritten, use SMT menu 16.1.3to clear the overwrite counter and retry the process.

Unable to establish synchronization with receiver.

REASON: The communications port between the PC and the voice processor isnot functioning properly.

ACTION: Check data communications parameters. Retry file-transfer se-quence.

Cancelled by receiver.

REASON: The file-transfer process from the voice processor to the PC has beencanceled by the PC operator.

ACTION: Restart file-transfer process, beginning at the initial block number, ifthis is not correct.

Error transmission limit reached.

REASON: Transmission-error count exceeded system limits.

ACTION: Check connections between the PC and the voice processor.Possible malfunctioning modem, connectors, cabling, or ports.

E.2 TRANSMISSION MESSAGES FROM CDR PC

Timeout Waiting for Password Prompt.

REASON: The voice processor never returned the prompt Please Enter SystemManager Password .

ACTION: Restart downloading process. Possible poor line quality.

TRANSMISSION MESSAGESAPPENDIX E

E-2 Edition Three Octel PC/CDR

Incorrect Password, Fix In The PC/CDR System Parameters Menu.

REASON: Incorrect password is set in the communication parameters.

ACTION: Verify password set in communication parameters.

File Transfer Error – Aborted by User

REASON: The F3 key has been pressed.

ACTION: Restart downloading process.

File Transfer Error – Carrier Lost

REASON: The link between the voice processor and the PC is not functioning.

ACTION: Verify that modem link is functioning properly.

File Transfer Error – Local File Problem (Disk Full)

REASON: The hard disk on the PC is full. Data cannot be downloaded, becausethere is no storage space.

ACTION: Delete or back up files, then restart downloading process.

File Transfer Error – Timeout (No Response from VPMOD)

REASON: The voice processor is too busy.

ACTION: Restart downloading process when less traffic is on the system.

VPMOD Busy or Transmission Error

REASON: The remote link to the voice processor is already in use.

ACTION: Restart downloading process at later time. If this error occursrepeatedly, check connections between the PC and the voiceprocessor. Possible malfunctioning modem, connectors, cabling, orports.

File Transfer Terminate Due to VPMOD Busy

REASON: The main SMT port or the remote service-access port is already inuse.

ACTION: Verify that SMT ports are already in use. If they are in use, restart thedownloading process at a later time.

File Transfer Error – Transfer Not Initiated by VPMOD

REASON: There was an attempt to download an overwritten or empty block.

ACTION: If blocks are overwritten, access SMT menu 16.1.3 to clear the CallDetail Recording Lost Data Counter (refer to section 2.5.5).Otherwise, confirm that the first block to be downloaded is a validblock (section 6.2.1 or section 6.3).

F

F-1Edition ThreeOctel PC/CDR

SCHEDULE-LOG FILE ENTRIESThe entries in Appendix F are logged in the schedule log file when functions areperformed or errors occur related to the scheduled automatic processing of CDRdata or the maintenance of the scheduled-automatic-processing files (the schedulelog file and the schedule parameter file). This list is not complete, but includesthe log-file entries that occur the most often. Refer to Chapter Six for informa-tion about scheduled automatic processing.

In some instances, the date and time of the entry are noted. The date is repre-sented by mm-dd-yy , which is the month, day, and year, respectively. The time isrepresented by hh:mm , with hh representing the hour and mm representing theminutes, based on a 24-hour clock (for example, 13:18 is 1:18 p.m.).

>> mm-dd-yy hh:mm SCHEDCDR: Password Entry Failure.

REASON: The schedule password was incorrectly entered three times.

ACTION: Confirm password. Watch for unauthorized users.

>> mm-dd-yy hh:mm SCHEDCDR: Shutdown.

REASON: Occurs only after Octel PC/CDR Main Menu Option 2, AutomaticScheduler Functions, was exited.

ACTION: No action necessary.

>> mm-dd-yy hh:mm SCHEDCDR: Startup.

REASON: Option 2, Automatic Scheduler Functions, was selected from the OctelPC/CDR Main Menu.


>> mm-dd-yy hh:mm SCHEDEDT: Shutdown.

REASON: Occurs only after Option 1 or 4 from the Octel PC/CDR AutomaticSchedule Menu was exited.


>> mm-dd-yy hh:mm SCHEDEDT: Startup.

REASON: Option 1 or 4 from the Octel PC/CDR Automatic Schedule Menu wasselected.


mm-dd-yy hh:mm: Begin Processing Schedule # 1 - [schedule name], System/Program # [system/program number] – [CDR system name]

REASON: The date and time that processing of the designated schedule numberbegan. No additional entry is made when the process is completed or ifthe process is interrupted and not completed.


SCHEDULE-LOG FILE ENTRIES APPENDIX F

F-2 Edition Three Octel PC/CDR

mm-dd-yy hh:mm: New log opened after backup. Backed up file C:\OCTELCDR\LOG\ Syymmdd.LOG to drive A:.

REASON: The schedule log file was erased after it was backed up, using theBackup Schedule Log File option, and a new log file was opened.


mm-dd-yy hh:mm: Previous log contents erased. New log opened after erase.

REASON: The Erase Schedule Log File utility was used to erase the schedule log file.


Backed up file C:\OCTELCDR\SCHEDCDR.PAR to drive A:.

REASON: Schedule parameters were backed up, using the Backup ScheduleParameter File option.


Error restoring log file.

REASON: The backed-up log file is not on the diskette, or the file is corrupted.

ACTION: Confirm that the diskette contains the file backed up with the BackupSchedule Log File option.

Error restoring schedules file C:\OCTELCDR\SCHEDCDR.PAR.

REASON: The backed-up schedule file is not on the diskette, or the file is corrupted.

ACTION: Confirm that the diskette contains the file backed up with the BackupSchedule Parameter File option.

Restored file C:\OCTELCDR\SCHEDCDR.PAR from drive A:.

REASON: Schedule parameters were restored, using the Restore ScheduleParameters option.


Restored log files from drive A:.

REASON: The schedule log file was copied to the \OCTELCDR\LOG subdirectoryon the hard drive, using the Restore Schedule Log File option.


G-1Edition ThreeOctel PC/CDR

GLOSSARY

A

AA (automated attendant). See Automated attendant.

Alphanumeric. (1) Refers to either the entire set of 128 ASCII characters or the subset ofASCII characters that includes the 26 alphabetic characters and the 10 numericcharacters. (2) This term pertains to a character set that contains both letters andnumerals and usually other characters.

AMIS (audio message interchange specification) analog networking. An optionalsoftware package that allows subscribers with mailboxes on an Octel voice proces-sor to exchange messages with subscribers on other, non-Octel voice-messagingsystems. The AMIS protocol does not accept Octel delivery options such as privateand urgent delivery of messages, but AMIS network addresses can be added tosystem and personal-group distribution lists.

Application . (1) A software program, such as a database or spreadsheet, that performs atask. (2) In this manual, application also refers to ECP mailboxes and otherevent-producing features of the voice processor.

ASCII (American Standard Code for Information Interchange). Consists of 128 seven-bitbinary codes for upper- and lower-case letters, numbers, punctuation, and specialcommunication-control characters.

ASPEN. The name ASPEN (in capital letters) is used in some transmission messages andon some screens in the CDR program as a synonym for Octel’s voice-processors.

Asynchronous transmission. A method of communication that allows data to be sent atirregular intervals by preceding each character with a start bit and following it with astop bit.*

Automated attendant (AA). A voice-processor feature that prompts callers to enter anextension number for the PBX or Centrex. After the caller enters the extensionnumber, the automated attendant transfers the call.

Automatic processing. One of four methods in CDR for downloading and processing data.This processing method downloads, collates, and generates output files in one step,using system attributes that were set before automatic processing started.

Automatic scheduler. See Scheduled automatic processing.

* Webster’s New World Dictionary of Computer Terms, 3rd ed., Simon & Schuster, Inc., 1988.

GLOSSARY

G-2 Edition Three Octel PC/CDR

B

Backup. A copy of a program or data made in case the original is lost, damaged, orotherwise inaccessible.

Batch file. A text file for personal computers with the extension .BAT in the file name.When the name of the batch file is typed, DOS executes the commands in the file,such as loading other programs and changing parameters of the computer.

Baud rate. (1) Term used for the speed of signal transmission, in bits per second. Thesystem manager terminal operates at 1200 or 9600 baud and the printer operates at9600 baud. (2) Commonly used to mean bits per second, baud is officially definedas the pulse width in a data-communication stream.

BCF (binary collection file). This file is created when blocks are downloaded from theCDR buffer on the voice-processor to a personal computer. The BCF is included in aBCF subdirectory on the PC hard disk. The BCF file name contains the encodeddate on which the download occurred.

Binary. Numbering system with a base of two. Binary code is a code that uses two distinctcharacters, usually the numerals 0 and 1. A binary digit is a character used torepresent one of the two digits in the binary numbering system.

Binary collection file (BCF). See BCF.

Block. In CDR, a unit of storage within the CDR buffer. Blocks are filled with event records,and then the blocks are downloaded to a PC for processing. A block can holdapproximately 80 to 140 event records.

Buffer. See CDR buffer.

C

Call. A series of events that begin when the voice-processor port goes off-hook to receivean incoming call or initiate an outgoing call and end when the call is completed andthe port goes on-hook.

Call Detail Records (CDR). See CDR.

Caller. Anyone who attempts to access the voice processor, either by direct dialing or bysending a message to a subscriber on the voice processor.

Call events. See Events.

Call volume. The number of calls received by the voice processor within a given timeperiod.

Carbon Copy PLUS. A Meridian Technology software application used for communicationbetween PCs. The application is a memory-resident program that is part of the OctelPC/CDR software package. Carbon Copy PLUS allows a remotely located personalcomputer to be connected to the CDR personal computer through a modem.

B–C

GLOSSARY


CDF (collated day file). This file is created in CDR. The events in a BCF are sorted(collated) chronologically by event-completion time into CDFs.

CDR buffer. Call-detail event records are collected and stored in a special area of memory,called the CDR buffer, on the voice-processor drives. The buffer is sized at 2020 or7020 blocks when the voice processor is installed or the CDR software is added.Each block is 2048 bytes; therefore a buffer of 2020 blocks uses approximately 4megabytes of voice-processor system-drive storage space.

CDR (Call Detail Records). An optional Octel software feature that records events thatoccur in the voice processor, including events occurring from the time a port goesoff-hook to receive a call to the time the port goes on-hook when the call iscompleted. Events are stored as blocks in the CDR buffer on the voice processor.The blocks are downloaded to a PC and sorted into output files for viewing orprinting. System managers can use CDR records to track how calls are processed(including subscriber mailbox access and messages transmitted across a network),to bill users for voice-processor resources, and to help resolve issues related tosystem performance.

CDR PC. A personal computer that contains the Octel PC/CDR software. The manipulationof CDR data downloaded from the voice processor occurs on the CDR PC.

CDR system. A term that refers to the systemname parameter that is set using theMKCDRSYS command. Systemnames specify the particular voice processors thatdownload CDR data files to the personal computer. See also Systemname.

Central office (CO). Telephone company term for its switching office. It is the connectionpoint for public telephones and switching equipment for trunks that provide thenecessary talk-path connections.

Centrex. The software and hardware located in a central office to provide PBX service to acustomer, eliminating the need for PBX equipment on the customer site.

Class of service. A class of service determines the options available to subscribers on thevoice processor.

Collated day file (CDF). See CDF.

Collation . (1) To assemble in order. (2) In CDR, files are sorted chronologically by eventsthat occur from every call on every port for a given date.

Communication port. The PC serial port used to connect the CDR personal computer tothe voice processor.

CRC (cyclical redundancy check). A method of detecting data transmission errors.

Cyclical redundancy check (CRC). See CRC.

D

Default. Value assigned by the program or the voice-processor when another value has notbeen specified by the user.

C–D

GLOSSARY


Direct connection. A permanently connected physical communication link used for datacommunication. A direct connection usually cannot be longer than 50 feet. See alsoRemote Connection.

DOS (disk operating system). A commonly used PC operating system. DOS facilitatescommands used to manipulate and execute files contained in storage media.

DOS prompt. Greater-than sign that appears on a terminal screen in the leftmost column. Itusually indicates the selected disk drive and subdirectory. When properly pro-grammed, DOS commands are executed by entering the command name with theappropriate parameters.

Download. Method for transferring data stored in the voice processor’s CDR buffer to theCDR PC.

DTMF (dual-tone multifrequency). Tones generated by the touch-tone keys on a tele-phone. Unique tones are produced by each key. DTMF is a nationally acceptedabbreviation for dual-tone multifrequency. DTMF allows the sending of numericinformation (from a touch-tone telephone) by transmitting specific pairs of tones.

DTMF OctelForms. Optional data-collection and -processing software program used withthe voice processor. A DTMF OctelForm is a series of questions recorded in aDTMF forms mailbox and played to the caller in a specific sequence. The callerresponds to the questions by pressing the touch-tone keys on a telephone. Atrademarked name of Octel Communications Corporation, OctelForms is spelled inupper- and lower-case letters, as shown here.

E

ECP (Enhanced Call Processing). Software feature that allows the voice processor toroute calls to extensions on the PBX or to other voice-processor mailboxes. Therouting does not require operator assistance.

Emulation. (1) The simulation of a device in real time. (2) In CDR, the personal computercan be configured to respond as a system manager terminal (SMT).

Enhanced Call Processing. See ECP.

Enter key. The key on a computer keyboard, designated by the word Enter or Return .Press the Enter key to execute a statement or command.

Events. Occurrences and records of detailed information associated with a call thatactivates the voice processor. These event records include mailbox entry, passwordtest, port goes off-hook or on-hook, beginning of an outcall, or transfer to anothermailbox or telephone number.

F

FDO (forms-output) file. This file is created in CDR from DTMF data in a DTMF Octel-Forms mailbox. The file contains records of question numbers and callers’ re-sponses. See DTMF OctelForms.

D–F

GLOSSARY


Field. A field is part of a record and is the smallest unit normally manipulated by adatabase-management system. A field contains a single piece of information ofpredetermined length and format. A field can also be restricted to alphabet ornumeric characters.

Field service engineer. Field personnel who have successfully completed the OctelCommunications’ training program.

File name. (1) Name given to a particular file used by DOS. The format allows up to eightalphanumeric characters, with up to three alphanumeric characters for an extension.The first eight characters and the extension are separated with a period andcombined as the file name. (2) In this manual, file names in upper-case charactersindicate constants, and file names in lower-case characters indicate variables.

Forms-output (FDO) file. See FDO file.

Function key. A key labeled F1 through F12, located along the top of a keyboard.

G, H

Greeting. Recorded message identifying the location reached by the caller. The greeting isthe first announcement heard by callers when they reach the voice processor, ifthere was no answer from the number dialed.

I, J, K

In-band integration. Form of integration where personal greetings, message-waitingindication, and return to operator are obtained by sending DTMF tones between thePBX and the voice processor. In-band describes the way the call ID, call information,message-waiting, and return-to-operator commands are sent over the same channel(or band) as the voice.

Individual-port-statistics output (IPO) file. See IPO file.

IPO (individual-port-statistics output) file. This file contains daily statistics, collectedevery 15 minutes, for the total time each port was in use during a 15-minute periodand the number of calls placed within the period.

L

Link. Process of connecting two or more voice processors or other devices.

Log file. (1) A log file is created for each day that a CDR process, such as collate ordownload, is executed. 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 are named by thedate on which the processing occurred and are given the extension of .LOG (forexample, L920302.LOG). (2) A transaction-log file (also known as a schedule-log file)called SCHEDCDR.LOG, located in the OCTELCDR\LOG subdirectory, collectsinformation about automatic-schedule transmissions. This file continues to addinformation as entries are made until it is backed up to a diskette or erased.

F–L

GLOSSARY


M

Mailbox. (1) Repository of messages for a voice-processor subscriber from outside callersor other subscribers. Allows subscribers to exchange messages or informationwithout being in direct telephone contact. (2) Special mailbox types allow differentfunctions to be performed. For example, an ECP mailbox allows calls to be routed toextensions on the PBX or to other voice-processor mailboxes without operatorassistance.

Mailbox name. (1) Name for mailbox or subscriber entered in system manager menus 8and 9. (2) Name recorded by a subscriber for mailbox identification.

Mailbox number. The 3- to 10-digit number that identifies a voice-messaging mailbox.Internal subscribers are assigned a mailbox number that is usually the same as theirextension numbers. The number of digits is determined in menu 0.

Manual processing. One of four methods in CDR for downloading and processing data.This processing method uses three steps to perform downloads. Each step requiresuser input.

MDO (message-detail output) file. This file contains data records of messages sent ordeleted in the voice processor. The records contain information such as the serialnumber of the voice processor, the port number, date and time when a messagewas sent or deleted, the mailbox number, message length, and destination ororigination mailbox.

Menu. System manager terminal or CDR PC display that contains a list of various functionsfrom which the system manager can select to perform operations or establishparameters.

Message-detail output (MDO) file. See MDO file.

Message waiting. Feature that allows subscribers to know whether new messages havebeen left in their mailboxes, indicated by a light on the telephone or a stutter dialtone.

MIRROR II. A data-communication software product from SoftKlone Distributing Corporation.The application is used by Octel PC/CDR to set up a communication link betweenthe PC and the voice processor for transferring data.

Modem. An acronym for modulator/demodulator. (1) Device used to interface the system-manager terminal with a telephone line for remote system management and polling.Also used for connecting a remote system-manager terminal to the voice-processorCPU. A method for passing digital information in an analog format. (2) Device thatconverts digital signals into analog signals for transmission through telephone lines.

MTA (multiple terminal access). An optional feature that uses a port box to connectadministrator terminals to the Sierra or Octel XC1000. MTA allows up to sixadministrator terminals to access maintenance and administration menus simulta-neously from a single voice processor. Multiple terminal access requires the portbox, a PC, and software that supports the MTA feature.

Multiple terminal access (MTA). See MTA.

M–M

GLOSSARY


N

Networking. Optional feature that enables voice processors to transmit messages to eachother at preprogrammed times and frequencies. See AMIS and OctelNet.

Node. The end point of any branch of a network or a junction common to two or morebranches of a network. For the voice-processor network, each voice processor in thenetwork is a node.

Non-service affecting (NSA) alarm. See NSA alarm.

NSA (non-service affecting) alarm. An alarm that warns the system manager of acondition that could degrade service if left uncorrected. In CDR, an NSA alarm islogged when the CDR buffer has less than 20% of space available before un-retrieved data will be overwritten.

O

OctelForms. See DTMF OctelForms.

OctelNet. Optional application used to link Octel voice processors in remote locations,allowing subscribers to send messages across the network to remote nodes. Fornetworking between Octel and non-Octel systems, see AMIS Analog Networking.

Octel PC/CDR. See CDR.

Outcalling. The voice processor initiates a call to a telephone or pager.

Output files. In CDR, files into which voice processor CDR data is sorted after it isdownloaded to a PC and collated.

P, Q

Parameter file. See Schedule parameter file.

Password. (1) On the voice processor, a system-manager-terminal (SMT) access numberfrom 3 to 15 digits long. Two passwords can be used: one is the primary system-manager-mailbox password and the other is the secondary system-manager-mailboxpassword. (2) In CDR, a password is required to allow the personal computer to link to the voice processor for downloading data. The password used to access OctelPC/CDR menus, if required, is the same as the SMT password. This password isrequired if the automatic-scheduling method of processing is used. (3) In CDR, aschedule password can be established and required for entry into the automatic-scheduler menus. (4) Carbon Copy PLUS requires a password to access a customer’sPC from a remote location.

PBX (private branch exchange). The telephone-switching equipment located in a businessoffice designed to process incoming, outgoing, and internal telephone calls.

PC/CDR. See CDR.

N–P

GLOSSARY


PCF (processed collection file). A file created in Octel’s Call Detail Records software. Thedata in a binary collection file is sorted into collated day files. If the binary collectionfile is not automatically set to be deleted, it is renamed with the PCF extension. SeeBCF.

Pending state file (PSF). See PSF.

Port. (1) Point of entrance or exit for a communications channel into a telephone system orvoice processor. (2) Any input or output channel on a voice or data-switchingsystem. In a PBX, a port is required for each line, trunk, or peripheral deviceconnected to that PBX.

Processed collection file (PCF). See PCF.

PSF (pending state file). A file created in Octel’s Call Detail Records software. This filehold all event records for calls that are in progress when a download occurs.

R

Remote connection. A communication link with modems that is used for data communica-tion. Because modems are used, the distance between the end devices can be morethan 50 feet. See also Direct connection.

Root directory. A directory from which all subdirectories branch. Within the root directory ora subdirectory, other subdirectories and files can exist. In DOS, the root directory isdesignated with the drive letter designation and a back slash. For example, c:\>designates the DOS root directory for the C drive.

S

SA (service affecting) alarm. An LED indicator or an alarm on the system-managerterminal that warns the system manager of an existing condition that could causedata and messages to be lost. In CDR, a service-affecting alarm is logged when thebuffer has less than 10% of available space left before unretrieved data will beoverwritten.

Scheduled automatic processing. In CDR, data from one or more voice processors canbe processed automatically at scheduled time intervals. Ten different time scheduleseach specifying up to 10 voice processors (CDR systems), programs, or batch files,can be created, with a minimum time limit of 3 minutes between downloads. TheAutomatic Scheduler Functions menu is accessed from the Octel PC/CDR MainMenu.

Schedule-log file. See Log files.

Schedule parameter file. This file contains the schedules created for use with thescheduled-automatic-processing download method.

Scroll. (1) To advance or go back, horizontally or vertically, a specified number of lines orcolumns in a displayed file or menu. (2) To advance automatically, by line, as thescreen is filled, with the entries at the top of the screen disappearing as new entriesare made at the bottom of the screen.

P–S

GLOSSARY


SDO (session-detail output) file. This file is created in Octel’s Call Detail Record software.It contains event records of each time a mailbox was accessed, either in voice-messaging or telephone-answering mode, and when callers are logged into the voiceprocessor but not into a mailbox. An SDO file is created for each day calls aremade.

Segment. This term is used in Appendix B to define the entry in the SegCT: field. Eachtime an introduction is added to a message and it is sent to another mailbox, thesegment count increments by 1. A new message sent to a mailbox on the voiceprocessor is 1 segment long. If an introduction is added to the message and themessage is sent to a second mailbox (or several other mailboxes), the message isthen 2 segments long. If the second mailbox owner adds an introduction and sendsthe same message to a third mailbox (or several other mailboxes), it is 3 segmentslong.

Service-affecting (SA) alarm. See SA alarm.

Service-level download. A method of downloading and processing CDR data. This methodis used primarily by Octel or distributor service representatives for troubleshooting. Itcreates the same binary collated files (BCFs) as all other forms of processing,however, specific data blocks must be selected for downloading.

Service representatives. Octel or distributor field service engineers. In this manual, servicerepresentatives are those who have successfully completed the Octel Communication’straining program for service personnel.

Session. Begins when a caller enters a mailbox and ends when the caller exits the samemailbox. A single call often passes through multiple mailboxes (for example, in ECPapplications), so a call normally consists of one or more sessions.

Session-detail output (SDO) file. See SDO file.

SMT emulation. The capability of connecting the CDR PC to a voice processor using theMIRROR II software program. The emulation allows the system manager todownload blocks from the voice processor and to perform most system managertasks from the CDR PC.

SMT (system-manager terminal). Video-display terminal that allows the system manager toset up and change the voice processor, set operational parameters, and monitorvoice-processor performance.

Subscriber. Person who has been assigned a voice-mailbox number on a voice processor.Subscribers can be located on or off the premises and are not required to have atelephone extension. Subscribers have access to all voice-processor features allowedby their classes of service.

Syntax. The rules governing the structure of a language and its expressions.*

System attributes. Selected parameters that include communication settings for theconnection between the CDR PC and a voice processor. The system attributes alsodefine the output files that are created using automatic CDR-processing methodsand the format of the output files.

* Webster’s New World Dictionary of Computer Terms, 3rd ed., Simon & Schuster, Inc., 1988.

S–S

GLOSSARY


System manager. Person responsible for operating and maintaining the voice processorand the CDR application.

System-manager terminal. See SMT.

Systemname. A field in the MKCDRSYS (make CDR system subdirectories on the harddrive) command. Systemname is the unique name chosen to identify a particularvoice processor that downloads data to the CDR personal computer.

T

Traffic. In CDR, the number of calls processed by a voice processor.

Transaction log file. See Log file.

Tree. An Octel term for software that provides an interface between a caller and the voiceprocessor. The expression open trees refers to the entry point of a call into the voiceprocessor where callers have the option of dialing an extension number or identifyingthemselves as subscribers on the voice processor.

U

Unsuccessful-transfer output (UTO) file. See UTO file.

User. Person who uses the voice processor; for example, a subscriber or an outside caller.

UTO (unsuccessful-transfer output) file. This file contains statistics for failed attempts totransfer from an automated attendant or from an Enhanced Call Processing mailbox.Reasons for failure include a busy extension, ring-no-answer, the extension is not inservice, or the transfer was answered by the voice processor.

V

Voice mail. A technology that provides a communication link between subscribers who canenter a voice mailbox and send messages to and receive messages from othersubscribers on the voice-mail system. Voice mail provides message-routing optionsnot available in telephone-answering systems.

Voice-messaging mode. A voice-mail feature used by voice-processor subscribers toexchange messages or information with other subscribers without being in directtelephone contact with one another. In a single call to the voice processor, subscriberscan send messages, listen to messages sent by other subscribers or left by outsidecallers, reply to messages, and send copies of messages to other subscribers.

Voice-processing module. Octel product line offering convenient exchange of informationby telephone without requiring simultaneous participation by the caller and thereceiver. The term refers to the family of Octel voice-processing modules thatincludes Aspen, Branch, Branch XP, Maxum, and Maxum SE. The Sierra, OctelXC1000, and the VPC 100 are associated systems, but are not part of the voice-processing-module product line.

S–V

GLOSSARY


Voice processor. In the CDR Manual, a term that refers collectively to the Aspen, Branch,Branch XP, Maxum SE, and Maxum voice-processing modules, the Octel XC1000voice-information-processing platform, and the Sierra multiple-application platform.

VPMOD. A term used in some of the Octel PC/CDR menus to represent the voiceprocessor.

W, X, Y, Z

XMODEM. An error-correcting data-transmission protocol for transmitting files betweenpersonal computers.

V–Z

I-1Edition ThreeOctel PC/CDR

INDEXSymbols

^ in modem parameters, 4-9

| in modem parameters, 4-9

~ in modem parameters, 4-9

A

Access Type (AT) codes for SDO files, A-3, A-4

Action codes for MDO files, A-8

Alarms, CDR buffer, 2-5see also Error messages

AM_DIR_FULL record type, B-1, B-4bytes for events, C-2record details, B-5

AM_EAR_FULL record type, B-1, B-4bytes for events, C-2record details, B-5

AMIS analog-network data collection, 2-8

AM_RCV_EOS record type, B-1, B-4bytes for events, C-2record details, B-5

AM_RCV_FC record type, B-1, B-4bytes for events, C-2record details, B-5

AM_RCV_FR record type, B-1, B-4bytes for events, C-2record details, B-5

AM_RCV_IC record type, B-1, B-4bytes for events, C-2record details, B-5

AM_RCV_INVPH record type, B-1, B-4bytes for events, C-2record details, B-6

AM_RCV_MSGI record type, B-1, B-4bytes for events, C-2record details, B-6

AM_RCV_MSG record type, B-1, B-4bytes for events, C-2record details, B-6

AM_RCV_PHNUM record type, B-1, B-4bytes for events, C-2record details, B-7

AM_RCV_RESP record type, B-1, B-4bytes for events, C-2record details, B-7

AM_RCV_START record type, B-1, B-4bytes for events, C-2record details, B-7

AM_RTS record type, B-1, B-4bytes for events, C-2record details, B-7, B-8

AM_SEND record type, B-1, B-4bytes for events, C-1record details, B-8, B-9

AM_XMT_EOM record type, B-1, B-4bytes for events, C-2record details, B-9

AM_XMT_EOS record type, B-1, B-4bytes for events, C-2record details, B-9

AM_XMT_MBOX record type, B-1, B-3bytes for events, C-2record details, B-9

AM_XMT_MINFO record type, B-1, B-3bytes for events, C-2record details, B-9, B-10

AM_XMT_OC record type, B-1, B-3bytes for events, C-2record details, B-10

AM_XMT_PHNUM record type, B-1, B-3bytes for events, C-2record details, B-10

AM_XMT_RESP record type, B-2, B-4bytes for events, C-2record details, B-11

AM_XMT_START record type, B-1, B-3bytes for events, C-2record details, B-11

AM_XMT_VOICE record type, B-2, B-4bytes for events, C-2record details, B-11

INDEX

I-2 Edition Three Octel PC/CDR

ASCII output-file format, 4-6, 4-7

Aspen voice-processing modulessee Voice-processing modules

AT (Access Type) codes for SDO files, A-3, A-4

Attribute (ATTRIB) codes for MDO files, A-9

Attributes, systemsee System attribute

AUTOEXEC.BAT file, 3-2, 3-3

AUTOEXEC.OLD file, 3-2

Automated-attendant-mailbox unsuccessfultransfers, 1-13, 1-14

Automatic generation of output files, 4-5, 4-6

Automatic Octel PC/CDR Schedule Editor Menu,6-17 through 6-19

Automatic processing, 6-12 through 6-14checking disk-storage space before

downloading, 6-1described, 6-12DTMF OctelForms, 8-5output-file generation, 4-5, 4-6steps, 6-1using, 6-12 through 6-14

Automatic processing schedules, 6-16 through6-21

adding, 6-16 through 6-19backing up schedule parameter file, 6-20, 6-21deleting, 6-19editing, 6-19listing, 6-19, 6-20printing, 6-20restoring schedule parameter file, 6-21timer, 6-22, 6-23

Automatic Schedule Menu, 6-16

Automatic-scheduler timer, 6-22, 6-23

B

Backing upsee also RestoringOctel PC/CDR files, 7-5 through 7-7schedule log file, 6-25, 6-26schedule log-file entries, F-2schedule parameter file, 6-20, 6-21

Baud rateCarbon Copy PLUS, 5-2communications parameter, 4-8

BCFssee Binary collection files (BCFs)

BCF subdirectory, 1-11, 3-5 through 3-7

Billing filessee Session-detail output (SDO) files

Binary collection files (BCFs)collating manually, 6-5, 6-6copying, 7-12 through 7-14deleting, 1-9, 4-4, 4-5described, 1-9, 1-10displaying, 7-14 through 7-16maximum BCFs downloaded per day, 1-10naming convention, 1-10renaming as processed collection files (PCFs),

4-4, 4-5

Binary Collection Files Erased After Collation?field, 7-16

Block # column, 6-2

Block Date & Time Summary Report field, 7-15

Block Number: field, 4-11

“Block Numbers in BCF are out of Sequence”message, 6-6

Blockssee also RecordsCDR buffer numbering sequence, 2-4CDR buffer size

described, 1-9, 2-1 through 2-3DTMF OctelForms, 8-1, 8-2

defined, 1-3downloading CDR data, 6-2next block to download, 4-10, 4-11, 6-14overwriting in CDR buffer, 2-4, 2-5recording process for call events, 2-3

BN_EOS record typedescribed, B-2, B-3record details, B-12

BN_IC record type, B-2, B-3bytes for events, C-2record details, B-12

BN_OC record type, B-2, B-3bytes for events, C-2record details, B-12

A–B

INDEX


BN_RCV_CP record type, B-2, B-3bytes for events, C-2record details, B-12, B-13

BN_RCV_HDR record type, B-2, B-3bytes for events, C-2record details, B-13

BN_RCV_SP record type, B-2, B-3bytes for events, C-2record details, B-13, B-14

BN_RCV_START record type, B-2, B-3bytes for events, C-2record details, B-14

BN_RCV_VOICE record type, B-2, B-3bytes for events, C-2record details, B-14

BN_RTS record type, B-2, B-3bytes for events, C-2record details, B-14, B-15

BN_XMT_CP record type, B-2, B-3bytes for events, C-2record details, B-15, B-16

BN_XMT_HDR record type, B-2, B-3bytes for events, C-2record details, B-16

BN_XMT_SP record type, B-2, B-3bytes for events, C-2record details, B-16, B-17

BN_XMT_START record type, B-2, B-3bytes for events, C-2record details, B-17

BN_XMT_VOICE record type, B-2, B-3bytes for events, C-2record details, B-17

Boot Drive Name: fieldInstallation Program menu, 3-2Upgrade Program menu, 3-9

Branch voice-processing modulessee Voice-processing modules

Branch XP voice-processing modulessee Voice-processing modules

Buffersee CDR buffer

C

Cables, 1-5, 1-6

Call-detail-recording software-featureenablement, 2-8

Call Detail Records management packagesee Octel PC/CDR

CALLER record type, B-2, B-3bytes for events, C-1record details, B-18

Calls & Sessions Passed column, 6-9

Callsdefined, 1-3relationship to sessions and events, 1-4single-event calls, 6-8

Calls Failed column, 6-8

Calls Passed columnmanual-collation processing screen, 6-6PSO file-processing screen, 6-11

Call Type (CT) codes for SDO files, A-3

“Cancelled by receiver” message, E-1

Carbon Copy PLUS, 5-1 through 5-7baud rate, 5-2changing parameters, 5-3comm port address, 5-2configuring, 5-1 through 5-4described, 5-1disabling, 5-7menus

Available Modem Types, 5-2, 5-3Password Table, 5-3, 5-4System Parameters, 5-1, 5-2

MIRROR II with, 5-1modem type, 5-2, 5-3password table, 5-3, 5-4requirements, 5-1service-representative responsibilities, 5-5, 5-6subdirectory, 3-2system-manager responsibilities, 5-5, 5-6using, 5-4 through 5-6

Carbon Copy subdirectorylocation, 3-2files, D-1ccremove command, 5-7

CC commandsee Carbon Copy PLUS

B–C

INDEX


CC subdirectory, 3-2see Carbon Copy subdirectory

CDF Input File Date columnFDO file-processing screen, 6-12MDO file-processing screen, 6-10PSO file-processing screen, 6-11SDO file-processing screen, 6-8UTO file-processing screen, 6-9

CDFssee Collated day files (CDFs)

CDF subdirectory, 1-11, 3-5 through 3-7

CDR Blocks column, 6-6

CDR buffer, 2-1 through 2-5alarms, 2-5capacity and disk-space requirements (table),

8-3capacity in days (table), 2-2, 2-3, 2-6clearing lost data counter, 2-12defined, 1-3downloading to the PC, 2-3DTMF OctelForms, 8-1 through 8-4monitoring buffer-storage space, 1-2, 2-11numbering sequence, 2-4overwriting blocks, 2-4, 2-5recording process for call events, 2-3size, 1-9, 2-1 through 2-3

DTMF OctelForms, 8-1, 8-2

CDR_CFG record type, B-2, B-3bytes for events, C-1 through C-3record details, B-18

CDR command, 4-1, 4-2

CDR Disk Space Free: field, 2-11

CDR Input File Name column, 6-6

CDR management packagesee Octel PC/CDR

CDR system, 1-3

CDR System Selection Menu, 4-2

Central office switch, 1-1

Centrex, 1-1

Checklist, 1-2, 1-3

Clearing, lost data counter, 2-12see also Deleting

Code values and descriptionsevent-record detail codes, B-5 through B-23event-report codes

by record-type abbreviation, B-1, B-2in numerical sequence, B-3, B-4

message-detail output (MDO) files, A-8, A-9session-detail output (SDO) files, A-3 through

A-6unsuccessful-transfer output (UTO) files, A-7

Collated day files (CDFs)creating from binary collection files (BCFs),

manual processing, 6-5, 6-6deleting, 4-5described, 1-10, 1-11DOS access command, 7-12naming convention, 1-10searching, 7-10 through 7-12subdirectory, 1-11, 3-5

COLLATE.PSF file and subdirectory for storing,1-11

Collationcollating BCFs manually, 6-5, 6-6defined, 1-3deleting BCFs after, 1-9, 4-4, 4-5

Commandscc (Carbon Copy PLUS), 5-1 through 5-7ccremove, 5-7cdfs, 7-12cdr, 4-1, 4-2copybcf, 7-14dumpbcf, 7-16dumpsf, 7-17, 7-18

Comm Port Address field, 5-2

Communication Port field, 4-8

Communications parameters, 4-7 through 4-10Carbon Copy PLUS, 5-2, 5-3connection type, 4-8dial-prefix string, 4-9dial-suffix string, 4-9modem-initialization string, 4-9port, 4-8speed (baud rate), 4-8terminal emulation type, 4-9testing, 4-11 through 4-13voice processor

software version number, 4-10system password, 4-10system type, 4-9telephone number, 4-9

C–C

INDEX


Communication Speed (Baud) field, 4-8

Componentssee Hardware

CONFIG.OLD file, 3-2

CONFIG.SYS file, 3-2, 3-3

Configuringcables and connectors, 1-5, 1-6checklist, 1-2, 1-3hardware, 1-6ports, 1-5, 1-6software releases, 1-6voice processor for CDR data collection, 2-7

through 2-12

Connection Type field, 4-8

Connectors, 1-5, 1-6

Consec. errors column, 6-2

copybcf command, 7-14

COPYBCF Options menu, 7-13

Copy Binary Collection File Utility Menu, 7-12,7-13

Copying binary collection files (BCFs), 7-12through 7-14

CRC (cyclical-redundancy-check) calculation, 6-2

Creating subdirectoriesINSTCDR utility (program subdirectories), 3-1

through 3-5MKCDRSYS utility (data subdirectories), 3-5

through 3-7

CT (Call Type) codes for SDO files, A-3

Current Setting column, 6-4, 6-14

Cyclical-redundancy-check (CRC) calculation, 6-2

D

Date/Time of Next Execution: field, 6-18

dBASEfield names

forms-output (FDO) file, A-12individual-port-statistics output (PSO) files,

A-10, A-11message-detail output (MDO) files, A-7session-detail output (SDO) files, A-2unsuccessful-transfer output (UTO) files, A-6

output-file format, 4-6, 4-7

Deletingautomatic processing schedules, 6-19binary collection files (BCFs), 1-9, 4-4, 4-5clearing lost-data counter, 2-12collated day files (CDFs), 4-5data subdirectories, 3-8Octel PC/CDR files, 7-8output files, 4-5schedule log file, 6-27

Destination Drive Name: fieldInstallation Program menu, 3-3Upgrade Program menu, 3-9

Dial Prefix String field, 4-9

Dial Suffix String field, 4-9

Direct connectionconfiguration diagrams, 1-6physical-connection requirements, 1-5system attribute specification, 4-8testing, 4-11 through 4-13VPMOD Telephone Number field, 4-9

Directoriessee Subdirectories

Disabling Carbon Copy PLUS, 5-7

Diskssee Storage; Subdirectories

Display Binary Collection File Utility Menu, 7-14

Display Disk Status menu, 6-1, 7-2

Displayingautomatic processing schedules, 6-19, 6-20binary collection files (BCFs), 7-14 through

7-16disk status, 7-2Octel PC/CDR files, 7-2output files, 7-2 through 7-4pending state files (PSFs), 7-16 through 7-18processed collection files (PCFs), 7-16schedule log file, 6-24, 6-25valid systemnames, 1-4

Display Pending State File Utility Menu, 7-16,7-17

DOSsee also Commandscopying binary collection files (BCFs), 7-13,

7-14displaying binary collection files (BCFs), 7-15,

7-16

C–D

INDEX


DOS (continued)displaying pending state files (PSFs), 7-17,

7-18restoring files using different DOS versions,

7-9searching collated day files (CDFs), 7-12service-level download access, 6-29version required, 1-7

Downloadingsee also ProcessingCDR buffer to PC, 2-3checking disk-storage space, 6-1cyclical-redundancy-check (CRC) calculation,

6-2DTMF OctelForms data, 8-4, 8-5manually downloading CDR data, 6-2 through

6-5maximum BCFs downloaded per day, 1-10service-level download, 2-11, 2-12, 6-27

through 6-29

DTMF OctelForms, 8-1 through 8-6see also Forms-output (FDO) fileapplications, 8-1buffer size, 8-1, 8-2byte sizes for mailbox record events, C-3collecting CDR data, 8-4described, 8-1disk-space requirement, 8-2 through 8-4download time, 8-4enabling data collection, 2-8processing

modes, 8-5, 8-6output files, 8-6time, 8-4with Octel PC/CDR, 8-5, 8-6

DTS record type, B-2, B-3bytes for events, C-1 through C-3record details, B-18

dumpbcf command, 7-16

DUMPBCF Options menu, 7-15

dumpsf command, 7-17, 7-18

E

Echo setting for modem, 4-7

Editing automatic-processing schedules, 6-19

Enabling call-detail recording-software feature,2-8

Enhanced Call Processing (ECP) mailboxunsuccessful transfers, 1-13, 1-14

Equipmentsee Hardware

Erasingsee Deleting

Error messagesalarms, 2-5“Block Numbers in BCF are out of Sequence,”

6-6“Cancelled by receiver,” E-1“Error transmission limit reached,” E-1“File Transfer Error,” E-2“File Transfer Terminate Due to VPMOD Busy,”

E-2“Incorrect Password,” E-2“Less than 100 kilobytes remaining on disk,”

2-7“No Previous Day File Available,” 6-11schedule log file entries, 6-24, 6-25, F-1, F-2“Starting block number is not valid,” E-1“There are older unread blocks,” E-1“Timeout Waiting for Password Prompt,” E-1transmission messages, E-1, E-2“Unable to establish synchronization with

receiver,” E-1“Unable to open that file,” 7-4“VPMOD Busy or Transmission Error,” E-2warning for low storage space, 4-2, 6-1“Write fault error writing device LPT1,” 7-5“Write fault error writing device PRN,” 6-20

“Error transmission limit reached” message, E-1

Event recordssee also EventsAM_DIR_FULL, B-1, B-4, B-5, C-2AM_EAR_FULL, B-1, B-4, B-5, C-2AM_RCV_EOS, B-1, B-4, B-5, C-2AM_RCV_FC, B-1, B-4, B-5, C-2AM_RCV_FR, B-1, B-4, B-5, C-2AM_RCV_IC, B-1, B-4, B-5, C-2AM_RCV_INVPH, B-1, B-4, B-6, C-2AM_RCV_MSG, B-1, B-4, B-6, C-2AM_RCV_MSGI, B-1, B-4, B-6, C-2AM_RCV_PHNUM, B-1, B-4, B-7, C-2AM_RCV_RESP, B-1, B-4, B-7, C-2AM_RCV_START, B-1, B-4, B-7, C-2

D–E

INDEX


Event records (continued)AM_RTS, B-1, B-4, B-7, B-8, C-2AM_SEND, B-1, B-4, B-8, B-9, C-1AM_XMT_EOM, B-1, B-4, B-9, C-2AM_XMT_EOS, B-1, B-4, B-9, C-2AM_XMT_MBOX, B-1, B-3, B-9, C-2AM_XMT_MINFO, B-1, B-3, B-9, B-10, C-2AM_XMT_OC, B-1, B-3, B-10, C-2AM_XMT_PHNUM, B-1, B-3, B-10, C-2AM_XMT_RESP, B-2, B-4, B-11, C-2AM_XMT_START, B-1, B-3, B-11, C-2AM_XMT_VOICE, B-2, B-4, B-11, C-2BN_IC, B-2, B-3, B-12, C-2BN_OC, B-2, B-3, B-12, C-2BN_RCV_CP, B-2, B-3, B-12, B-13, C-2BN_RCV_HDR, B-2, B-3, B-13, C-2BN_RCV_SP, B-2, B-3, B-13, B-14, C-2BN_RCV_START, B-2, B-3, B-14, C-2BN_RCV_VOICE, B-2, B-3, B-14, C-2BN_RTS, B-2, B-3, B-14, B-15, C-2BN_XMT_CP, B-2, B-3, B-15, B-16, C-2BN_XMT_HDR, B-2, B-3, B-16, C-2BN_XMT_SP, B-2, B-3, B-16, B-17, C-2BN_XMT_START, B-2, B-3, B-17, C-2BN_XMT_VOICE, B-2, B-3, B-17, C-2CALLER, B-2, B-3, B-18, C-1CDR_CFG, B-2, B-3, B-18, C-1 through C-3DTMF forms mailbox records, C-3DTS, B-2, B-3, B-18, C-1 through C-3FCE, B-2, B-3, B-18, C-3IC, B-2, B-3, B-18, C-1invalid password-disconnect records, C-3IPL, B-2, B-3, B-18, C-1 through C-3MD, B-2, B-3, B-18, B-19, C-1message send/delete records, C-1message-waiting-notification records, C-3MS, B-2, B-3, B-19, B-20, C-1MW, B-2, B-3, B-20, C-3networking-related records, C-2OC, B-2, B-3, B-21, C-1ON_HOOK, B-2, B-3, B-21, C-1PWT, B-2, B-3, B-21, C-1PWT_RJCT, B-2, B-3, B-21, C-3RSS, B-2, B-3, B-21, C-1SEIZE, B-2, B-3, B-22, C-1session-related records, C-1SMS, B-2, B-3, B-22, C-1

tablesalphabetized by abbreviation, B-1, B-2byte sizes, C-1 through C-3details, B-5 through B-23numerical sequence, B-3, B-4

TNE, B-2, B-3, B-22, C-1TREES_FCD, B-2, B-3, B-22, C-3TREES_FMB, B-2, B-3, B-22, C-3TREES_FQA, B-2, B-3, B-22, C-3TRS, B-2, B-3, B-22, C-1XFR, B-2, B-3, B-23, C-1

Event Records: field, 7-11

Eventssee also Event recordsbyte sizes

invalid password-disconnect records, C-3mailbox records, C-3message send/delete records, C-1message-waiting notification records, C-3networking-related records, C-2session-related records, C-1

defined, 1-3rejected events, 6-6relationship to sessions and calls, 1-4searching collated day files (CDFs), 7-11single-event calls, 6-8

Events Rejected column, 6-6

Exitingdisabling Carbon Copy PLUS, 5-7shutting down the voice processor, 4-12

F, G

FCE record type, B-2, B-3bytes for events, C-3record details, B-18

FDO filesee Forms-output (FDO) file

Field namesforms-output (FDO) file, A-12individual-port-statistics output (PSO) files,


File Backup Menu, 7-6

File Creation Date & Time column, 6-6

E–F

INDEX


File Date: field, 7-3

File Download Settings menu, 6-4

File Erase Menu, 7-8

File Format: field, 7-3

File namesdefined, 1-3naming conventions

binary collection files (BCFs), 1-10collated day files (CDFs), 1-10forms-output (FDO) file, 1-17individual-port-statistics output (PSO) files,

1-16in this manual, 1-3log files, 1-11message-detail output (MDO) files, 1-15pending state files (PSFs), 1-11processed collection files (PCFs), 1-10session-detail output (SDO) files, 1-13unsuccessful-transfer output (UTO) files,

1-14

Filessee also File names; Subdirectories; Utilities;

specific files by name or typeAUTOEXEC.BAT, 3-2, 3-3backing up

Octel PC/CDR files, 7-5 through 7-7schedule log file, 6-25, 6-26schedule parameter file, 6-20, 6-21

CC subdirectory files, D-1collection files, 1-9 through 1-17CONFIG.SYS, 3-2, 3-3copying binary collection files (BCFs), 7-12

through 7-14created during installation, 3-4created during upgrade, 3-10deleting

binary collection files (BCFs), 1-9, 4-4, 4-5collated day files (CDFs), 4-5log files, 4-5Octel PC/CDR files, 7-8output files, 4-5

displayingbinary collection files (BCFs), 7-14, 7-15Octel PC/CDR files, 7-2output files, 7-2 through 7-4pending state files (PSFs), 7-16 through

7-18processed collection files (PCFs), 7-16schedule log file, 6-24, 6-25

log files

deleting, 4-5described, 1-11naming convention, 1-11SCHEDCDR.LOG, 3-2, 6-24 through 6-27schedule log file, 3-2, 6-24 through 6-27,

F-1, F-2subdirectory, 3-5

MIR subdirectory files, D-1naming conventions, 1-3, 1-10, 1-11, 1-13

through 1-16OCTELCDR subdirectory files, D-1output files

automatic generation, 4-5, 4-6code values and descriptions, A-3 through

A-9defined, 1-3deleting, 4-5described, 1-11 through 1-17file structures, A-1 through A-12format level, 4-11format types, 4-6, 4-7manual generation, 6-7 through 6-12naming conventions, 1-13 through 1-17printing, 7-2 through 7-5processing DTMF OctelForms files, 8-6record groups required, 2-10selecting, 7-3, 7-4, 8-5types, 7-3viewing, 7-2 through 7-4

record-processing sequence, 1-8, 1-9restoring

Octel PC/CDR files, 7-9schedule log file, 6-26, 6-27schedule parameter file, 6-21

schedule parameter file, 6-20, 6-21searching collated day files (CDFs), 7-10

through 7-12subdirectory files, D-1

File Selection Parameters menu, 7-3

“File Transfer Error” message, E-2

“File Transfer Terminate Due to VPMOD Busy”message, E-2

File Type: field, 7-3

File Utilities Menu, 7-1 through 7-18Backup Octel PC/CDR Files option, 7-5

through 7-7described, 7-1Display Disk Status option, 7-2Display Octel PC/CDR Files option, 7-2

F–F

INDEX


File Utilities Menu (continued)Erase Octel PC/CDR Files option, 7-8Restore Octel PC/CDR Files option, 7-9Service Utilities option, 7-9 through 7-18View/Print Octel PC/CDR Files option, 7-2

through 7-5

First Block to Copy field, 7-13

First Line to Print: field, 7-5

Fixed disksee Storage; Subdirectories

Formatoutput-file format level, 4-11output-file format types, 4-6, 4-7

Forms Calls column, 6-12

Forms-output (FDO) filesee also DTMF OctelForms; Output filesautomatically appending records, 4-5, 4-6deleting, 4-5described, 1-16, 1-17example, 1-17field names, A-12file-processing screen, 6-12file structure, A-12format type, 4-6, 4-7manual generation, 6-12naming convention, 1-17record groups required, 2-10subdirectory, 1-17, 3-5

Full Report? field, 7-15

H

Hard disksee Storage; Subdirectories

Hardwaresee also specific components by nameconfigurations, 1-6PC requirements, 1-7physical-connection requirements, 1-5

I, J

IBM DOSsee DOS

IC record type, B-2, B-3bytes for events, C-1record details, B-18

“Incorrect Password” message, E-2

Individual-port-statistics output (PSO) filessee also Output filesautomatic generation, 4-5, 4-6deleting, 4-5described, 1-15, 1-16example, 1-16field names, A-10, A-11file-processing screen, 6-11file structure, A-9 through A-11format type, 4-6, 4-7manual generation, 6-10, 6-11naming convention, 1-16record groups required, 2-10subdirectory, 1-16, 3-5

Input CDF File: field, 7-11

Installation Program menu, 3-2, 3-3

InstallingCarbon Copy PLUS, 5-1 through 5-4checklist, 1-2, 1-3Octel PC/CDR into PC, 3-1 through 3-5

AUTOEXEC.BAT changes, 3-2, 3-3CONFIG.SYS changes, 3-2, 3-3files created, 3-4Octel PC/CDR Installation Program menu,

3-2, 3-3steps, 3-2 through 3-5subdirectories created, 3-1, 3-2

upgrading Octel PC/CDR software, 3-8through 3-10

Install Octel PC/CDR Software?: field, 3-3

INSTCDR.EXE utilityAUTOEXEC.BAT changes, 3-2, 3-3CONFIG.SYS changes, 3-2, 3-3files created, 3-4menu, 3-2, 3-3subdirectories created, 3-1, 3-2

Interval Between Executions: field, 6-18

IPL record type, B-2, B-3bytes for events, C-1 through C-3record details, B-18

KKeyboard, Wyse 50 emulation, 4-13

LLast Block to Copy field, 7-13

“Less than 100 kilobytes remaining on disk”message, 2-7

F–L

INDEX


Listingsee Displaying

Log filesdeleting, 4-5described, 1-11naming convention, 1-11SCHEDCDR.LOG, 3-2, 6-24 through 6-27schedule log file

described, 3-2, 6-24 through 6-27entries, 6-24, 6-25, F-1, F-2

subdirectory, 3-5

Logging processing output to printer, 4-4

LOG subdirectory, 3-2

Lost data counter, 2-12

–L parameter, 6-29

M

Mailboxes: field, 7-11

Main Menu (Octel PC/CDR), 4-1, 6-15

Main Menu (View Octel PC/CDR Output Files),7-2

Manual processing, 6-2 through 6-12checking disk-storage space before

downloading, 6-1collating BCFs into CDFs, 6-5, 6-6described, 6-2, 6-3downloading Octel PC/CDR data, 6-3 through

6-5output-file generation, 6-7 through 6-12steps, 6-1

Maxum SE voice-processing modulessee Voice-processing modules

Maxum voice-processing modulessee Voice-processing modules

MDO filessee Message-detail output (MDO) files

MD record type, B-2, B-3bytes for events, C-1record details, B-18, B-19

Menu 13, 2-8

Menu 16clearing lost-data counter, 2-12monitoring buffer-storage space, 2-11

Retrieve Call Detail Records option, 2-11,2-12, 6-28, 6-29

selecting CDR records to be processed, 2-9through 2-11

service-level download, 2-11, 2-12, 6-28, 6-29

Menussee also specific menus by name or numberCarbon Copy PLUS

Available Modem Types menu, 5-2, 5-3Password Table menu, 5-3, 5-4System Parameters menu, 5-1, 5-2

Octel PC/CDRAutomatic Octel PC/CDR Schedule Editor

Menu, 6-17 through 6-19Automatic Schedule Menu, 6-16CDR System Selection Menu, 4-2COPYBCF Options menu, 7-13Copy Binary Collection File Utility Menu,

7-12, 7-13Display Binary Collection File Utility Menu,

7-14Display Disk Status menu, 6-1Display Pending State File Utility Menu,

7-16, 7-17DUMPBCF Options menu, 7-15File Backup Menu, 7-6File Download Settings menu, 6-4File Erase Menu, 7-8File Selection Parameters menu, 7-3File Utilities Menu, 7-1 through 7-18Installation Program menu, 3-2, 3-3Main Menu (Octel PC/CDR), 4-1, 6-15Main Menu (View Octel PC/CDR Output

Files), 7-2Modify Automatic Output File Generation

menu, 4-5, 4-6, 6-13Modify Output File Format Types menu, 4-6Modify PC Communications Parameters

menu, 4-7 through 4-10Output File Generation Menu, 6-7Print Selection Parameters menu, 7-5Processing Menu, 6-3Search Collated Day File Utility Menu, 7-10

through 7-12Select a Binary Collection File menu, 7-13Select a Pending State File menu, 7-17Service Utilities Menu, 7-9Session Detail Output File Type menu, 4-6,

4-7System Attributes Menu, 4-4, 4-10, 4-11,

6-13System Data Directory Creation menus,

3-6, 3-7

L–M

INDEX


Menus, Octel PC/CDR (continued)System Menu, 4-1 through 4-3, 6-3, 6-27

through 6-29, 7-1Update Automatic Processing Schedules

menu, 6-17Upgrade Program menu, 3-9

system manager terminalfunctions that cannot be performed from

the PC, 4-12menu 13, 2-8menu 16, 2-9 through 2-12, 6-28, 6-29

Message-detail output (MDO) filessee also Output filesautomatic generation, 4-5, 4-6code values and descriptions, A-8, A-9data included in file, 1-14, 1-15deleting, 4-5described, 1-14, 1-15example, 1-15field names, A-7file-processing screen, 6-10file structure, A-7format type, 4-6, 4-7manual generation, 6-10naming convention, 1-15record groups required, 2-10subdirectory, 1-15, 3-5

Messagessee also Error messagesbyte sizes for message send/delete record

events, C-1data collection, 2-10searching collated day files (CDFs), 7-12storage space, 1-9transmission messages, E-1, E-2

Messages Returned column, 6-10

Messages Sent & Deleted columnMDO file-processing screen, 6-10SDO file-processing screen, 6-9

Message-waiting notificationdata collection, 2-10event byte sizes, C-3

MIRROR IICarbon Copy PLUS with, 5-1subdirectory, 3-1Wyse 50 special-emulation function keys on

PC, 4-13

MIR subdirectoryfiles, D-1location, 3-1

MKCDRSYS utilitydata subdirectory creation, 3-5 through 3-7subdirectories created, 3-5syntax, 3-5, 3-6system attribute configuration, 4-3 through

4-11

Modembaud rate, 4-8, 5-2Carbon Copy PLUS

parameters, 5-2, 5-3requirement, 5-1

comm port address, 5-2communications parameters, 4-7 through 4-10connection type, 4-8dial prefix string, 4-9dial suffix string, 4-9echo setting, 4-7initialization string, 4-9port, 4-8requirement, 1-7type, 5-2, 5-3

Modem Initialization String field, 4-9

Modem Type field, 5-2, 5-3

Modify Automatic Output File Generation menu,4-5, 4-6, 6-13

Modify Output File Format Types menu, 4-6

Modify PC Communications Parameters menu,4-7 through 4-10

Communication Port field, 4-8Communication Speed (Baud) field, 4-8Connection Type field, 4-8Dial Prefix String field, 4-9Dial Suffix String field, 4-9Modem Initialization String field, 4-9Terminal Emulation Type field, 4-9testing communications parameters, 4-11

through 4-13VPMOD Software Version Number field, 4-10VPMOD System Password field, 4-10VPMOD System Type field, 4-9VPMOD Telephone Number field, 4-9

Monitoring CDR buffer-storage space, 1-2, 2-11

MS-DOSsee DOS

Msg ID Address: field, 7-12

M–M

INDEX


MS record type, B-2, B-3bytes for events, C-1record details, B-19, B-20

MW record type, B-2, B-3bytes for events, C-3record details, B-20

NNames

file-naming conventionsbinary collection files (BCFs), 1-10collated day files (CDFs), 1-10forms-output (FDO) file, 1-17individual-port-statistics output (PSO) files,

1-16log files, 1-11message-detail output (MDO) files, 1-15pending state files (PSFs), 1-11processed collection files (PCFs), 1-10session-detail output (SDO) files, 1-13in this manual, 1-3unsuccessful-transfer output (UTO) files,

1-14renaming BCFs as PCFs, 4-4, 4-5schedule name, 6-18systemnames

accessing System Menu, 4-3defined, 1-4listing valid names, 1-4service-level download command, 6-29

Networkingsee also AMIS analog network; OctelNetbyte sizes for event records, C-2data collection, 2-10outcalls, 1-12

Next Block to Download: field, 4-10, 4-11, 6-14

Non-service-affecting (NSA) alarms, 2-5

“No Previous Day File Available” message, 6-11

NSA alarms, 2-5

Number of Blocks Overwritten: field, 2-11

Number of Blocks to Retrieve: field, 6-28

OOC record type, B-2, B-3

bytes for events, C-1record details, B-21

OCTELCDR\CC subdirectoryfiles, D-1location, 3-2

OCTELCDR\LOG subdirectory, 3-2

OCTELCDR\MIR subdirectoryfiles, D-1location, 3-1

OCTELCDR subdirectoryfiles, D-1location, 3-1

OctelNet data collection, 2-10

Octel PC/CDRbenefits to system managers, 1-1, 1-2checklist for installation, configuration, and

processing, 1-2, 1-3contents of package, 1-7enabling software feature, 2-8equipment configurations, 1-6field names


A-10, A-11message-detail output (MDO) files, A-7session-detail output (SDO) files, A-2unsuccessful-transfer output (UTO) files,

A-6installing in PC, 3-1 through 3-5menus

Automatic Octel PC/CDR Schedule EditorMenu, 6-17 through 6-19

Automatic Schedule Menu, 6-16CDR System Selection Menu, 4-2COPYBCF Options menu, 7-13Copy Binary Collection File Utility Menu,

7-12, 7-13Display Binary Collection File Utility Menu,

7-14Display Disk Status menu, 6-1Display Pending State File Utility Menu,

7-16, 7-17DUMPBCF Options menu, 7-15File Backup Menu, 7-6File Download Settings menu, 6-4File Erase Menu, 7-8File Selection Parameters menu, 7-3File Utilities Menu, 7-1 through 7-18Installation Program menu, 3-2, 3-3Main Menu (Octel PC/CDR), 4-1, 6-15Main Menu (View Octel PC/CDR Output

Files), 7-2

M–O

INDEX


Octel PC/CDR, menus (continued)Modify Automatic Output File Generation

menu, 4-5, 4-6, 6-13Modify Output File Format Types menu,

4-6Modify PC Communications Parameters

menu, 4-7 through 4-10Output File Generation Menu, 6-7Print Selection Parameters menu, 7-5Processing Menu, 6-3Search Collated Day File Utility Menu, 7-10

through 7-12Select a Binary Collection File menu, 7-13Select a Pending State File menu, 7-17Service Utilities Menu, 7-9Session Detail Output File Type menu, 4-6,

4-7System Attributes Menu, 4-4, 4-10, 4-11,

6-13System Data Directory Creation menus,

3-6, 3-7System Menu, 4-1 through 4-3, 6-3, 6-27

through 6-29, 7-1Update Automatic Processing Schedules

menu, 6-17Upgrade Program menu, 3-9

overview, 1-1, 1-2processing DTMF OctelForms, 8-5, 8-6record-processing sequence, 1-8, 1-9requirements, 1-4 through 1-8

PC, 1-7physical-connection, 1-5software, 1-7, 1-8

software attributes, 4-1 through 4-13steps for installation and configuration, 3-1system attributes and parameters, 4-3 through

4-11terms defined, 1-3, 1-4upgrading, 3-8 through 3-10

Octel XC1000 voice-information-processingplatform

see also Voice-processing module; Voiceprocessor

CDR buffer size, 1-9, 2-1 through 2-3physical-connection requirements, 1-5system type for communications, 4-9

ON_HOOK record type, B-2, B-3bytes for events, C-1record details, B-21

Open trees, A-1

Other Calls Ignored column, 6-8

Outcall events in SDO files, 1-12

Output File Generation Menu, 6-7

Output filessee also specific file typesautomatic generation, 4-5, 4-6code values and descriptions

message-detail output (MDO) files, A-8,A-9

session-detail output (SDO) files, A-3through A-6

unsuccessful-transfer output (UTO) files,A-7

defined, 1-3deleting, 4-5described, 1-11 through 1-17field names


A-10, A-11message-detail output (MDO) files, A-7session-detail output (SDO) files, A-2unsuccessful-transfer output (UTO) files,

A-6file structures


A-9 through A-11message-detail output (MDO) files, A-7session-detail output (SDO) files, A-1, A-2unsuccessful-transfer output (UTO) files,

A-6format level, 4-11format types, 4-6, 4-7manual generation, 6-7 through 6-12naming conventions, 1-13 through 1-17printing, 7-2 through 7-5processing DTMF OctelForms files, 8-6record groups required, 2-10selecting, 7-3, 7-4, 8-5types, 7-3viewing, 7-2 through 7-4

Output selection: field, 7-11, 7-12

Overwriting dataCDR buffer, 2-4, 2-5clearing lost-data counter, 2-12

O–O

INDEX


P

Pager outcalls, 1-12

Parameters, systemsee System attributes

Passwordssee also Securitybyte sizes for invalid password-disconnect

record events, C-3Carbon Copy PLUS password table, 5-3, 5-4data collection for invalid password

disconnects, 2-10forgotten, 6-23schedule password, 6-23, 6-24system-manager password, 4-2, 4-10voice-processing module, 4-10

Password Table menu, 5-3, 5-4

PBXs (private branch exchanges), 1-1

PC/CDRsee Octel PC/CDR

PC-DOSsee DOS

PCFssee Processed collection files (PCFs)

PCssee Personal computers (PCs)

Pending state files (PSFs)COLLATE.PSF file, 1-11described, 1-11displaying, 7-16 through 7-18naming convention, 1-11subdirectories, 1-11, 3-5

Personal computers (PCs)baud rate, 4-8Carbon Copy PLUS requirements, 5-1CDR buffer downloading schedule, 2-3direct-connection test, 4-11 through 4-13installing Octel PC/CDR, 3-1 through 3-5recommendations, 1-1, 1-7remote access, 5-1 through 5-7requirements

disk space, 2-5 through 2-7, 8-2 through8-4

hardware, 1-7physical connection, 1-5processing time, 2-5 through 2-7software, 1-7, 1-8

system-manager functions that cannot beperformed, 4-12

transmission messages, E-1, E-2Wyse 50 special-emulation function keys, 4-13

Portssee also Individual-port-statistics output (PSO)

filesCarbon Copy PLUS requirements, 5-1comm port address for Carbon Copy PLUS,

5-2communications port, 4-8configurations, 1-5, 1-6searching collated day files (CDFs), 7-11separate ports for SMT and PC, 1-5shared by SMT and PC, 1-5

Ports: field, 7-11

Port statistics filessee Individual-port-statistics output (PSO) files

Printingautomatic processing schedules, 6-20output files, 7-2 through 7-5processing results, 4-4schedule log file, 6-25

Print Selection Parameters menu, 7-5

Private branch exchanges (PBXs), 1-1

Processed collection files (PCFs)binary collection files (BCFs) renamed as, 4-4,

4-5described, 1-10displaying, 7-16naming convention, 1-10

Processingautomatic processing

checking disk-storage space beforedownloading, 6-1

described, 6-12output-file generation, 4-5, 4-6steps, 6-1using, 6-12 through 6-14


checklist, 1-2, 1-3DTMF OctelForms

modes, 8-5, 8-6with Octel PC/CDR, 8-5, 8-6output files, 8-6processing time, 8-4

P–P

INDEX


Processing (continued)manual processing


collating BCFs into CDFs, 6-5, 6-6described, 6-2, 6-3downloading Octel PC/CDR data, 6-3

through 6-5output-file generation, 6-7 through 6-12steps, 6-1using, 6-2 through 6-12

overview, 6-1, 6-2PC processing-time requirement, 2-5 through

2-7recording process for call events, 2-3scheduled automatic processing, 6-14 through

6-27checking disk-storage space before

downloading, 6-1described, 6-15output-file generation, 4-5, 4-6schedule log file entries, 6-24, 6-25, F-1,

F-2starting automatic scheduler mode, 6-22,

6-23steps, 6-1updating automatic scheduler log files, 6-24

through 6-27updating schedule password, 6-23, 6-24updating schedules, 6-16 through 6-21using, 6-14 through 6-27

service-level download, 6-27 through 6-29accessing through System Menu, 6-27

through 6-29accessing with DOS command, 6-29checking disk-storage space before

downloading, 6-1described, 6-27Retrieve Call Detail Records option, 2-11,

2-12, 6-28, 6-29

Processing Menu, 6-3

PSFssee Pending state files (PSFs)

PSO filessee Individual-port-statistics output (PSO) files

PWT record type, B-2, B-3bytes for events, C-1record details, B-21

PWT_RJCT record type, B-2, B-3bytes for events, C-3record details, B-21

Q

Quittingdisabling Carbon Copy PLUS, 5-7shutting down the voice processor, 4-12

R

Record display: field, 7-11

Recordssee also Blocks; Event recordsgroups required for output files, 2-10processing sequence, 1-8, 1-9selecting records to be collected, 2-9 through

2-11

Records Created column, 6-10

Rejected events, 6-6

Remote accesssee Carbon Copy PLUS

Removingsee Deleting

Requirements, 1-4 through 1-8Carbon Copy PLUS, 5-1personal computers (PCs)

disk space, 2-5 through 2-7, 8-2 through8-4

hardware, 1-7physical connection, 1-5processing time, 2-5 through 2-7software, 1-7, 1-8

physical-connection, 1-5record groups required for output files, 2-10software, 1-7, 1-8

Restoringsee also Backing upOctel PC/CDR files, 7-9schedule log file, 6-26, 6-27schedule log file entries, F-2schedule parameter file, 6-21

Retrieve Call Detail Records option, 2-11, 2-12,6-27 through 6-29

Retrieving recordssee Downloading

RMCDRSYS utility, 3-8

syntax, 3-8

RSS record type, B-2, B-3bytes for events, C-1record details, B-21

P–R

INDEX


S

SA alarms, 2-5

SCHEDCDR.LOG file, 3-2, 6-24 through 6-27see also Schedule log file

Scheduled automatic processing, 6-14 through6-27


described, 6-15output-file generation, 4-5, 4-6schedule log file, 3-2, 6-24 through 6-27

backing up, 6-25, 6-26deleting, 6-27entries, 6-24, 6-25, F-1, F-2listing, 6-24, 6-25printing, 6-25restoring, 6-26, 6-27

starting automatic scheduler mode, 6-22, 6-23steps, 6-1updating schedule password, 6-23, 6-24updating schedules, 6-16 through 6-21

adding new schedules, 6-16 through 6-19backing up schedule parameter file, 6-20,

6-21deleting schedules, 6-19editing schedules, 6-19listing schedules, 6-19, 6-20printing schedules, 6-20restoring schedule parameter file, 6-21

Schedule Editor Menu, 6-17 through 6-19

Schedule log file, 3-2, 6-24 through 6-27backing up, 6-25, 6-26deleting, 6-27entries, 6-24, 6-25, F-1, F-2listing, 6-24, 6-25printing, 6-25restoring, 6-26, 6-27

Schedule Name: field, 6-18

Schedule parameter filebacking up, 6-20, 6-21restoring, 6-21

Schedule password, 6-23, 6-24

Schedulesautomatic processing schedules, 6-16 through

6-21adding, 6-16 through 6-19backing up schedule parameter file, 6-20,

6-21deleting, 6-19editing, 6-19

listing, 6-19, 6-20printing, 6-20restoring schedule parameter file, 6-21timer, 6-22, 6-23

CDR buffer downloading, 2-3password, 6-23, 6-24schedule log file, 3-2, 6-24 through 6-27

backing up, 6-25, 6-26deleting, 6-27entries, 6-24, 6-25, F-1, F-2listing, 6-24, 6-25printing, 6-25restoring, 6-26, 6-27

SDO filessee Session-detail output (SDO) files

Search Collated Day File Utility Menu, 7-10through 7-12

Searching collated day files (CDFs), 7-10 through7-12

Security, running automatic processingunattended, 6-22

see also Passwords

SEIZE record type, B-2, B-3bytes for events, C-1record details, B-22

Select a Binary Collection File menu, 7-13

Select a Pending State File menu, 7-17

Selectingbinary collection files (BCFs), 7-13CDR records to be processed, 2-9 through

2-11output files, 7-3, 7-4, 8-5pending state files (PSFs), 7-17

Sender Only/Receiver (S_R) codes for MDO files,A-9

Sequence Number of First Block to Retrieve: field,6-28

Service-affecting (SA) alarms, 2-5

Service-level download, 6-27 through 6-29accessing through System Menu, 6-27 through

6-29accessing with DOS command, 6-29checking disk-storage space before

downloading, 6-1described, 6-27Retrieve Call Detail Records option, 2-11,

2-12, 6-28, 6-29

S–S

INDEX


Service representativeCarbon Copy PLUS responsibilities, 5-5, 5-6service-level download, 6-27 through 6-29

Service Utilities Menu, 7-9Copy Binary Collection File option, 7-12

through 7-14Display Binary Collection File option, 7-14

through 7-16Display Pending State File option, 7-16

through 7-18Search Collated Day File option, 7-10 through

7-12

Session Detail Output File Type menu, 4-6, 4-7

Session-detail output (SDO) filessee also Output filesautomatic generation, 4-5, 4-6code values and descriptions, A-3 through A-6data included in file, 1-12deleting, 4-5described, 1-12, 1-13example, 1-13field names, A-2file-processing screen, 6-8, 6-9file structure, A-1, A-2format type, 4-6, 4-7manual generation, 6-7 through 6-9naming convention, 1-13outcall events, 1-12record groups required, 2-10subdirectory, 1-13, 3-5

Sessionsbyte sizes for events, C-1defined, 1-4relationship to calls and events, 1-4

Shutting down the voice processor, 4-12

Sierra multiple-applications platformsee also Voice processorCDR buffer size, 1-9, 2-1 through 2-3physical-connection requirements, 1-5software requirements, 1-8

Single-event calls, 6-8

Size of CDR bufferdescribed, 1-9, 2-1 through 2-3DTMF OctelForms, 8-1, 8-2

SMS record type, B-2, B-3bytes for events, C-1record details, B-22

SMTsee System manager terminal (SMT)

Softwaresee also DTMF OctelFormsattributes, 4-1 through 4-13configurations for software releases, 1-6requirements, 1-7, 1-8

Source Drive Name: fieldInstallation Program menu, 3-2Upgrade Program menu, 3-9

S_R (Sender Only/Receiver) codes for MDO files,A-9

Starting automatic-scheduler timer, 6-22, 6-23

“Starting block number is not valid” message, E-1

Storagesee also Backing up; CDR buffer;

Subdirectorieschecking disk-storage space before

downloading, 6-1directory-tree structure, 3-6disk-space requirements

described, 2-5 through 2-7DTMF OctelForms, 8-2 through 8-4

displaying disk status, 7-2monitoring CDR buffer-storage space, 1-2,

2-11warning for low storage space, 4-2, 6-1

Subdirectoriessee also Storage; specific subdirectories by

namebinary collection files (BCFs), 3-5collated day files (CDFs), 1-11, 3-5creating

INSTCDR utility, 3-1 through 3-5MKCDRSYS utility, 3-5 through 3-7

deleting data subdirectories, 3-8directory-tree structure, 3-6displaying Octel PC/CDR files, 7-2forms-output (FDO) file, 1-17, 3-5individual-port-statistics output (PSO) files,

1-16, 3-5log files, 3-5message-detail output (MDO) files, 1-15, 3-5Octel PC/CDR data, 3-5

creating, 3-5 through 3-7deleting, 3-8

S–S

INDEX


Subdirectories (continued)Octel PC/CDR software

creating, 3-1 through 3-5described, 3-1, 3-2

pending state files (PSFs), 1-11, 3-5session-detail output (SDO) files, 1-13, 3-5subdirectory files, D-1system attribute files, 3-5unsuccessful-transfer output (UTO) files, 1-14,

3-5

Sys. Events Ignored column, 6-11

SYS subdirectory, 1-11, 3-5 through 3-7

System attributes, 4-3 through 4-11automatic output-file generation, 4-5, 4-6communications parameters, 4-7 through 4-10

connection type, 4-8dial prefix string, 4-9dial suffix string, 4-9modem initialization string, 4-9port, 4-8speed (baud rate), 4-8terminal emulation type, 4-9testing, 4-11 through 4-13voice-processor parameters, 4-9, 4-10

defined, 1-4deleting files

binary collection files (BCFs), 4-4, 4-5collated day files (CDFs), 4-5log files, 4-5output files, 4-5

logging processing output to printer, 4-4menu, 4-4, 4-10, 4-11, 6-13next block to download, 4-10, 4-11, 6-14output-file format level, 4-11, 6-11output-file format types, 4-6, 4-7steps for configuring, 4-3, 4-4testing the direct connection, 4-11 through 4-13

System Attributes Menu, 4-4automatic-processing method, 6-13Modify Output Format Level option, 6-11Next Block to Download option, 4-10, 6-14

System Data Directory Creation menus, 3-6, 3-7

System ID # columnFDO file-processing screen, 6-12manual-collation processing screen, 6-6MDO file-processing screen, 6-10PSO file-processing screen, 6-11SDO file-processing screen, 6-8UTO file-processing screen, 6-9

System managerCarbon Copy PLUS responsibilities, 5-5, 5-6functions that cannot be performed from the

PC, 4-12Octel PC/CDR benefits, 1-1, 1-2password, 4-2, 4-10

System manager terminal (SMT)see also Menusemulation type, 4-9functions that cannot be performed from the

PC, 4-12physical-connection requirements, 1-5Wyse 50 special-emulation function keys on

PC, 4-13

System Menu, 4-1 through 4-3, 6-3file utilities, 7-1service-level download access, 6-27 through

6-29

Systemnamesaccessing System Menu, 4-3defined, 1-4listing valid names, 1-4service-level download command, 6-29

System/Program Name: fields, 6-18

T

TablesCDR buffer capacity

disk-space requirements, 8-3in days, 2-2, 2-3, 2-6

code values and descriptionsmessage-detail output (MDO) files, A-8,

A-9session-detail output (SDO) files, A-3

through A-6unsuccessful-transfer output (UTO) files,

A-7event records

alphabetized by abbreviation, B-1, B-2details, B-5 through B-23in numerical sequence by event-report

code, B-3, B-4file structures



S–T

INDEX


Tables (continued)output-file record groups, 2-10password table, 5-3, 5-4PC processing-time and disk-space

requirements, 2-6, 2-7Wyse 50 special-emulation function keys on

PC, 4-13

Target File field, 7-13

Term Code (TC) codes for SDO files, A-4 throughA-6

Terminalsee System manager terminal (SMT)

Terminal Emulation Type field, 4-9

“There are older unread blocks” message, E-1

“Timeout Waiting for Password Prompt” message,E-1

Timer, automatic-scheduler, 6-22, 6-23

Times: field, 7-11

TNE record type, B-2, B-3bytes for events, C-1record details, B-22

Total Calls columnFDO file-processing screen, 6-12MDO file-processing screen, 6-10PSO file-processing screen, 6-11SDO file-processing screen, 6-8UTO file-processing screen, 6-9

Total errors column, 6-2

Total Events column, 6-6

Total Number of Blocks for CDR: field, 8-1, 8-2

Transmission messagessee also Error messages“Cancelled by receiver,” E-1from CDR PC, E-1, E-2“Error transmission limit reached,” E-1“File Transfer Error,” E-2“File Transfer Terminate Due to VPMOD Busy,”

E-2“Incorrect Password,” E-2“Starting block number is not valid,” E-1“There are older unread blocks,” E-1“Timeout Waiting for Password Prompt,” E-1“Unable to establish synchronization with

receiver,” E-1from voice processor, E-1

“VPMOD Busy or Transmission Error,” E-2

Trees, A-1

TREES_FCD record type, B-2, B-3bytes for events, C-3record details, B-22

TREES_FMB record type, B-2, B-3bytes for events, C-3record details, B-22

TREES_FQA record type, B-2, B-3bytes for events, C-3record details, B-22

Troubleshootingsee Error messages

TRS record type, B-2, B-3bytes for events, C-1record details, B-22

U

“Unable to establish synchronization withreceiver” message, E-1

“Unable to open that file” message, 7-4

Unsuccessful-transfer output (UTO) filessee also Output filesautomatic generation, 4-5, 4-6code values and descriptions, A-7data included in file, 1-14deleting, 4-5described, 1-13, 1-14example, 1-14field names, A-6file-processing screen, 6-9file structure, A-6format type, 4-6, 4-7manual generation, 6-9naming convention, 1-14record groups required, 2-10subdirectory, 1-14, 3-5

Unsuccessful Transfers column, 6-9

Unsuc Xfers column, 6-9

Update autoexec.bat & config.sys?: fieldInstallation Program menu, 3-3Upgrade Program menu, 3-9

Update Automatic Processing Schedules menu,6-17

T–U

INDEX


UpdatingAUTOEXEC.BAT file, 3-3, 3-9automatic processing schedules, 6-16 through

6-21automatic scheduler log files, 6-24 through

6-27CONFIG.SYS file, 3-3, 3-9Octel PC/CDR software upgrade, 3-8 through

3-10schedule password, 6-23, 6-24

Upgrade Octel PC/CDR Software?: field, 3-9

Upgrade Program menu, 3-9

Upgrading Octel PC/CDR software, 3-8 through3-10

UPGRCDR utility, 3-8 through 3-10files created, 3-10menu, 3-9

Utilities, 7-1 through 7-18backing up Octel PC/CDR files, 7-5 through

7-7deleting Octel PC/CDR files, 7-8disk-status display, 7-2displaying Octel PC/CDR files, 7-2printing Octel PC/CDR files, 7-2 through 7-5restoring Octel PC/CDR files, 7-9service utilities, 7-9 through 7-18

copying binary collection files (BCFs), 7-12through 7-14

displaying binary collection files (BCFs),7-14 through 7-16

displaying pending state files (PSFs), 7-16through 7-18

displaying processed collection files(PCFs), 7-16

searching collated day files (CDFs), 7-10through 7-12

viewing Octel PC/CDR files, 7-2 through 7-4

UTO filessee Unsuccessful-transfer output (UTO) files

VViewing

see Displaying

Voice-mail usageCDR buffer capacity, in days, 2-2, 2-3PC disk space requirement, 2-6

Voice-processing modulessee also Voice processorCDR buffer size, 1-9, 2-1 through 2-3defined, 1-1password, 4-10physical-connection requirements, 1-5

software requirements, 1-8software-version number, 4-10system type, 4-9telephone number, 4-9

Voice processorsee also Octel XC1000 voice-information-

processing platform; Sierra multiple-applications platform; Voice-processingmodules

baud rate, 4-8configuring for CDR data collection, 2-7

through 2-12clearing lost-data counter, 2-12enabling software feature, 2-8monitoring CDR buffer storage, 2-11Retrieve Call Detail Records option, 2-11,

2-12selecting call detail record, 2-9 through

2-11steps, 2-7, 2-8

defined, 1-1direct-connection test, 4-11 through 4-13shutting down, 4-12system type for communications, 4-9transmission messages, E-1

“VPMOD Busy or Transmission Error” message,E-2

VPMODssee Voice-processing modules

VPMOD Software Version Number field, 4-10

VPMOD System name: field, 7-11

VPMOD System Password field, 4-10

VPMOD System Type field, 4-9

VPMOD Telephone Number field, 4-9

WWarnings

see Alarms; Error messages

“Write fault error writing device LPT1” message,7-5

“Write fault error writing device PRN” message,6-20

Wyse 50 terminal emulation, 4-13

X, Y, ZXFR record type, B-2, B-3

bytes for events, C-1record details, B-23

U–Z

Documents

OCTEL CALL DETAIL RECORDS MANUAL