Panasonic Section 520 User Manual

Section 520 - TSAPI Installation and Feature Description

The contents of this document are subject to change without notice and do not constitute a
commitment on the part of Panasonic Telecommunication System Company (PTSC). Every effort
has been made to ensure the accuracy of this document. However, due to ongoing product
improvements and revisions, Panasonic cannot guarantee the accuracy of printed material after
the date of publication nor can it accept responsibility for errors or omissions. Panasonic will
update and revise this document as needed.

The software and hardware described in this document may be used or copied only in accordance
with the terms of the license pertaining to said software or hardware.

Copyright 2000 by Panasonic Telecommunication Systems Company



ii Issued April 2000 DBS-92-520

Contents

Chapter 1. Overview of Telephony Services for the DBS . . . . . . . . . . . 1

Chapter 2. Limitations and Specifications . . . . . . . . . . . . . . . . . . . . . . . 3

Chapter 3. Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Telephone System Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Installing the API Circuit Card/Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Programming the DBS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

DBS Driver Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Loading Panadrvr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Setting up Telephony Services Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Chapter 4. Driver Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Basic Call Control Services:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Telephony Supplementary Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Status Reporting Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Call Event Reports (Unsolicited) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Chapter 5. Maintenance and Troubleshooting. . . . . . . . . . . . . . . . . . . 19

Alarm Log Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

“FATAL” Messages: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

“WARNING” Messages: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

“CAUTION” Messages: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

“ERROR” Messages: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

“AUDIT TRAIL” Messages: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

The Panadrvr Menu System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

1: Display DBS Extension/Port Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

2: Display Error Counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Bad/No Resp to Select Req. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Naks to Select Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Aborted DBS select tries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

DBS rx data timeouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Answer Requests to DBS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

DBS packets Nakd by PC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Driver selected, DBS no send data timeouts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Packets Nakd by DBS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

DBS-92-520 Issued April 2000 iii

Table of Contents Section 520 - TSAPI

Answer requests from DBS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

PC packet sends aborted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

RX Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

TX Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

GetBuf Fails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

WatchDog Timeouts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Port Reconfigurations Received . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

DBS Resets Rx’d . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Carrier Detect Losses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

3: Display Status Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Packets Sent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Packets Received . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Commands Sent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Commands Received . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Bytes Sent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Bytes Received . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Network Sent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Network Received. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

4: Display Resource Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

5: Display ACS Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Total of Open Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Stream Open Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Stream Close Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Stream Abort Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Stream Other Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Stream Open Confirms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Stream Open Denies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Peak Opened Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Invalid Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Active Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

6: Display CSTA Stats/Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Total Requests Granted. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Total Requests Denied . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Total Requests Unsupported. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

DBS Response Timeouts (fail) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

DBS Send Errors (fail) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Lost Positive Confs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Lost Negative Confs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Lost Query Confirmations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Answer Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Clear Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Clear Conn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Conf Call. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Hold Call. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Make Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

iv Issued April 2000 DBS-92-520

Section 520 - TSAPI Table of Contents

Query MWI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Query DND. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Query FWD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Query LNR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Retr. Call. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Set MWI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Set DND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Set FWD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Trans Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

MonitorDev. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Monitor Stop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

GetApiCaps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

ChgFilter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

7: Display DBS Status/Info. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Confirmations Positive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Confirmations Negative . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Confirmations Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Events Tone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Events TSAPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Events Unknown. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

DBS Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

8: N/A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

9: ShutDown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

a: Display Resource Names/IDS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

b: Display Driver Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

c: Port Monitor Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

d: Change Max Call Time Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

e: Call Processing Toggles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

1. Disable (Enable) CSTA ClearCall Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

2. Disable (Enable) Send Service Initiated Events due to Makecall Request. . . . . . . 39

3. Disable (Enable) Send Failed Events on Busy Tone . . . . . . . . . . . . . . . . . . . . . . . 39

4. Disable (Enable) Event Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

f: Display API Control Signals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

g: Display Call Processing Stats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Present Active Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Present Active Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Peak Active Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Peak Active Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Initial Cache Count. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Active Cache Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Present Cache Count. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Last Call ID Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Maximum Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Max Monitors/Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Max Monitors/Stream. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

DBS-92-520 Issued April 2000 v

Table of Contents Section 520 - TSAPI

h: N/A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

i: Set Debug Trace Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

1. Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

2. Debug . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

3. Caution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

4. Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

j: N/A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

k: Change MWI Activator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

l: Display Active Call List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

CallID: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Type:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Port:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

State: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

m: N/A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

n: N/A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

o: Open (Close) Log File (N/A) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

p: Display Transfer Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

q: Display Monitor IDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

r: Display Conference Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

s: Display Runtime Config Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

t: Insert Comment into log file (N/A). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

u: Display Call Times. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

vi Issued April 2000 DBS-92-520

Chapter 1. Overview of Telephony Services for the DBS

Most businesses already use computers and telephones extensively in their
day-to-day operations. With few exceptions, however , business telephone and
computer systems have historically remained independent entities - no
interaction or common communication was possible between the two types of
systems. Recent advances in technology have made possible the merger of the
two systems into a cohesive and more effective communications and
operational office tool. The technology which makes this possible is called
Computer Telephony Integration (CTI).

The possibilities for CTI are endless. For instance:

- inbound callers may be routed to the most appropriate customer
representative based on the caller’s ph one number. As the call is
answered, the representative’s computer screen automatically
displays the customer’s information.

- a computer-based phone directory may be used to not only look
up a phone number but also initiate the call.

- the vast array of PBX features may be more easily utilized using
computer screen icons and prompting instead of complicated
telephone feature access codes and procedures.

What are the advantage to CTI?

- increased access to information

- improved sharing of information

- more effective communication

- more effective use of the telephone system

- more timely response

- improved customer satisfaction

One of the most significant emerging standards in CTI is the Telephony
Services Application Programming Interface from Novell®.

Telephony Services provides computer applications with third-party call
control capabilities. These applications may act on behalf of one user or a
group of users. With this group orientation, Telephony Services affords easy
distribution and transfer of calls and reporting of call handling

DBS-92-520 Issued April 2000 1

Chapter 1. Overview of Telephony Service for the DBS Section 520 - TSAPI

s

With Telephony Services, a Novell Netware® Network is required. To
communicate with the DBS, a Panasonic DBS driver called “Panadrvr”
(developed as a Netware Loadable Module or NLM) is installed on the
telephony server. Application developers designing to Netware Telephony
Services specifications can design products that communicate to the DBS
driver via the Novell Tserver NLM, which is also installed on the telephony
server.

The DBS talks with Panadrvr using a serial link from the Panasonic dual-port
API Card. There is no physical link between the telephones and the
networked computers. However, a logical link is established on the telephony
server to relate a telephone to a networked computer.

Novell

Telephony

Server

NovellNetwork

Outside C O
Trunk Lines

Serial

Com m unication

Line

APIPort

TRK1 TRK2 TR K3 EC1 EC2 EC3 EC4 EC5 EC6 EC7 EC 8 EC/TRK SCC CPC AUX1 AUX2

DBS

...

Logical

C onnection

...

Telephone Extensions

2 Issued April 2000 DBS-92-520

Chapter 2. Limitations and Specifications

DBS/Telephony Services Item Capacity

Maximum DBS extension ports monitored 50 minimum
Maximum individual monitors per extension

port
Maximum monitors per client on network 8
Maximum Outstanding CSTA requests

(Applications must wait for either a positive
or negative response from Panadrvr prior to
issuing further requests.)

Maximum wait between client applications
requests and driver response

Maximum allowable dialed digits in a
MakeCall Request

Maximum open CSTA sessions 100

• Release 1.0 of Panasonic Telephony Services supports only Panasonic
DBS digital telephones.

• For information needed for development of DBS Telephony Services
applications, see the DBS Telephony Services Programming Guide
(Section 470), available through your DBS regional salesperson.

3

1

45 seconds

32

DBS-92-520 Issued April 2000 3

Section 520-TSAPI Chapter 2. Limitations and Specifications

This page intentionally left blank.

4 Issued April 2000 Doc. No. 570X00101

Chapter 3. Installation

Overview

This chapter describes how to install Telephony Services for use with the
DBS. The first part of this chapter describes installation of the API hardware
and procedures for programming the DBS. The second part of the chapter
describes how to install the Panadrvr Telephony Services NetWare Loadable
Module (NLM) on the Novell Server.

Requirements

• One VB-43941 Telephony Services Kit. This kit includes a Panasonic API

Card, the API Serial Connector (two ports), and one 3 1/2” floppy disk
containing the Panadrvr Telephony Services DBS Driver.

• DBS CPC-B or CPC-A II Version 7.1 or later.

• A Novell 3.12 or 4.X 486 (or greater) server containing at least 8

megabytes of RAM and an available serial port of at least 9600 baud
capacity (16550 UART required).

• One customized serial cable (provided). The RS232 limit of 50 feet should

not be exceeded.

Telephone System Installation

The DBS communicates with the Novell server using a serial link. The VB­43941 TSAPI circuit card and API Serial Connector board provide the serial
connection on the DBS. A serial port is required on the Novell Server.

Note:

the DBS Telephone Technician.

Installing the API Circuit Card/Connector

Install the API in the DBS as follows:

1. Power off the DBS.

2. Insert the API card in the DBS as shown in Figure 1. The SW1 Switch

The Telephone System Installation procedures must be performed by

must be in the RAM HOLD (UP) position. Install the API card in either
the AUX1 or AUX2 slot positions with single cabinet configurations or in
the AUX1 slot position of the master cabinet with the dual cabinet
configuration.

DBS-92-520 Issued April 2000 5

Chapter 3. Installation Section 520 - TSAPI

Figure 1. DBS API Circuit Card/ Serial Connector Installation

1

X

U

A

1

X

U

A

3. Attach the API serial port connector to the side of the DBS cabinet with

two screws.

4. Connect the API serial port connector white cables as follows:

API Serial Port Connector API Circuit Card Connector

Port 1 (CN102) Port 1 (CN2)
Port 2 (CN103) Port 2 (CN3)

6 Issued April 2000 DBS-92-520

Section 520 - TSAPI Chapter 3. Installation

5. Connect the provided serial cable from Port 1 (or Port 2) to the serial port

on the Network Server. The cable must be configured as shown in Figure
2 below. The API port used must match the DBS API Port Type setting
specified in FF1 2# (41-42)# 1# (0-1)# and the port specified with the
NetWare Loadable Module driver “Panadrvr”. See “Programming the
DBS” on page 8 and “DBS Driver Installation” on page 9 for more
information.

Note:

If the distance from the DBS to the server exceeds 50 feet, line

extenders or short range modems are required.

Figure 2. Telephony Services Serial Cable Pinout

DB-25
Male

TD
RD

CTS
RTS

DSR
DCD

SG
DTR

22
33

47
54
6
8
75

20

1
6

8

RD
TD

RTS
DTR

DB-9
Female

SG
DCD
DSR

CTS

6. Power on the DBS.

DBS-92-520 Issued April 2000 7

Chapter 3. Installation Section 520 - TSAPI

API Port Number

41 = Port 1
42 = Port 2

Port Type:

1 = Telephony Services protocol

0 = Standard API protocol (default)

Baud Rate:

1 = 19200

0 = 9600 (default)

API Port Number

41 = Port 1
42 = Port 2

Programming the DBS

1. Enter the DBS programming mode

2. Set the API port to

Program
Name

Address FF1 2# 1# (41 or 42)# 1# (0-1)#

Note:

3. Set the Telephony Services API Port Baud rate to the desired baud rate as

follows:.

Program
Name

Address FF1 2# 1# (41 or 42)# 2# (0-1)#

API Port Type

The Telephony Services NLM defaults to use the first port (41).

API Baud Rate

Telephony Services

as follows:.

8 Issued April 2000 DBS-92-520

Note:

recommended that the baud rate be set to19200. If both API ports are
used, it is recommended that both baud rates be set to 9600 bps.

If Telephony Services is the only connection to the API card, it is

Section 520 - TSAPI Chapter 3. Installation

DBS Driver Installation

Overview

Caution

Netware Technician.

The Panasonic Telephony Services DBS driver ‘Panadrvr’ is a NetWare
Loadable Module created to run on a Novell 3.12 or 4.X 486 (or greater)
server with at least 8 megabytes of RAM and equipped with a serial port of
9600 baud plus capacity (16550 UART required).

The driver is distributed on a single 1.44MB diskette. The diskette contains a
root directory and two sub-directories as shown.

: Installation of the DBS Driver must be performed by a Novell

The root directory consists of a single ‘readme’ file which contains release
information and last minute release changes. This ‘readme’ file also contains
the differences between the trace and non-trace versions of the driver.

The release directory contains the non-trace enabled version of the driver and
is the driver of choice for most, if not all, customers.

The trace directory contains the trace-enabled version of the driver and
should be installed only when deemed necessary by Panasonic Technical Sup­port.

Note:

Installation

To install the Panasonic Telephony Services DBS driver, read the ‘readme’
file on the Panadrvr diskette and then copy the appropriate version of the
driver from the diskette to the \SYSTEM directory of the 3.12 or 4.x Novell
server.

Library Dependencies

Panadrvr requires 3 runtime libraries on the server:
and

tsrv.nlm

present at runtime. If these nlms are not present or cannot be loaded, the

This version is also valuable to application developers.

clib.nlm, aiocomx.nlm,

. Panadrvr will attempt to self-load these nlms if they are not

DBS-92-520 Issued April 2000 9

Chapter 3. Installation Section 520 - TSAPI

Novell loader will advise of unresolved external symbols and Panadrvr will
not be loaded.

Loading Panadrvr

Before Panadrvr can be loaded, Telephony Services must be installed and
running and a client logged into the server as Administrator or Supervisor.
During the installation process, Panadrvr is copied to the system directory of
the server.

The Panadrvr NLM can be loaded manually by entering it on the command
line, or automatically by adding the load command to the

In either case, the syntax for the load command is as follows:

autoexec.ncf

file.

Load Options

Panadrvr has several load time options. To display a list of these options,
type:

Options must be separated from each other by a space, as shown in the
following example.

Notes:

• It is recommended that the

each time Panadrvr is loaded. If Panadrvr is to be loaded automatically , add
these options to the load command line in

• Command line options specified after the configuration file is read

override any options specified in the configuration file.

load Panadrvr

load Panadrvr?

load Panadrvr security=2 api=2 baud=19200 setmwi=100 port=1

<options>

api, baud

, and

security
autoexec.ncf

options be specified

.

Option: api=

Range: 1 or 2
Default: 1
Runtime modifiable: No
Purpose: Specifies which DBS API port is set up for Telephony Services.

This must match the DBS setting.

10 Issued April 2000 DBS-92-520

Section 520 - TSAPI Chapter 3. Installation

Option: port=

Range: 1 to 8
Default: 1
Runtime modifiable: No
Purpose: Specifies which serial port on the server PC is connected to the

DBS for Telephony Services.

Option: baud=

Range: 9600 or 19200
Default: 9600
Runtime modifiable: No
Purpose: Specifies the DBS API baud rate. This must match the DBS

setting.

Option: security=

Range: 1 to 3
Default: 2 (Medium)
Runtime modifiable: No
Purpose: Specifies the CSTA stream control security level. The values 1,

2, and 3 translate to CSTA ranges High (all commands checked for
validity), Medium (login only checked for validity), and None (no checks
performed), respectively. Most client applications require level 2 or
above.

Option: setmwi=

Range: 10-699
Default: -1 (disabled)
Runtime modifiable: Yes
Purpose: Specifies the act ivator extension of a CS TA set message waiting

indicator request. Normally supplied through private data, most
applications are not written to support this option for Panasonic -- this
allows the command to be honored by the driver and passed to the DBS.
If not set, and private data not supplied, the command is rejected.

Option: sendfail=

Range: 0 or 1
Default: 1 (Enabled)
Runtime modifiable: Yes
Purpose: Specifies whether the driver should send CSTA failed events to

the application when receiving busy tone from the DBS on a given
monitored extension

DBS-92-520 Issued April 2000 11