DECvoice DTC04 System Technical Manual Order Number EK-DTC04-TM-002 digital equipment corporation maynard, massachusetts
nd Edition, March 1989 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license.
Contents About This Manual 1 ix Installation 1.1 Unpacking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3 Device Addresses Assignments . . . . . . . . . . . . . . . . . . . . . . 1.3.1 Assignment Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3.2 Address Assignment Examples . . . . . . . . . . . . . . . . . . . . 1.3.2.1 Using SYSGEN to configure a system . . .
Contents–iv 3 Software Interface 3.1 Q-bus Interface . . . . . . . . . . . . . 3.1.1 Control and Status Register . . 3.2 Resetting the DECvoice Module . 3.3 Data Transfer Scheme . . . . . . . . 3.3.1 Rings . . . . . . . . . . . . . . . . . . . 3.3.1.1 Buffer Structure . . . . . . . . . 3.3.2 Interrupts . . . . . . . . . . . . . . . 3.3.2.1 Interrupt Scheme . . . . . . . . 3.3.3 Commands and Messages . . . 3.3.3.1 Command Format . . . . . . . 3.3.3.2 Message Format . . . . . . . . . 3.4 Initialization . .
Contents–v 4.2.2 4.2.2.1 4.2.2.2 4.2.2.3 4.2.3 4.2.3.1 4.2.3.2 4.2.3.3 4.2.3.4 . . . . . . . . . 61 61 62 62 62 62 62 62 63 5.1 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.2 Diagnostic Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.2.1 DECvoice Test Programs . . . . . . . . . . . . . . . . . . . . . . . . . 5.2.1.1 VOX$TEST.EXE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.2.1.2 VOX$DIAL.EXE . . . . . . . . . . . . . . . .
Contents–vi C C.1 C.2 C.3 Communication Requirements FCC Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Communication Requirements in Canada . . . . . . . . . . . . . . Service Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 80 81 Glossary Index Examples 1–1 Configuring a System with Two DECvoice Modules . . . . . . . 18 Figures 1–1 1–2 1–3 1–4 Switchpack Locations on the Module . . . . . . . . . . . . . . . Setting the CSR Address Switches . .
Contents–vii 4–1 4–2 4–3 A–1 20-Pin Connector . . . . . . . . . . . . Signaling Byte From the Module Signaling Byte to the Module . . . SLD 20-Pin Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 63 63 74 DECvoice Components . . . . . . . . . . . . Common CSR settings for DECvoice . CSR Address Assignments . . . . . . . . .
About This Manual This manual describes the DECvoice DTC04 system hardware, including installation, system microcode, and maintenance. The system hardware includes the DECvoice DTC04 Q-bus module, telephone line interface assembly, and cables. Please read this document before you install the system. Intended Audience This manual is for Digital Field Service personnel and technically sophisticated users of the DECvoice system. Organization This manual is divided into five chapters and three appendixes.
x About This Manual Appendix A, "Connector Pinouts," shows pin diagrams and signal names for the Q-bus and telephone line interface connectors. Appendix B, "Telephonics," lists and details the telephonic characteristics of the DECvoice system. Appendix C, "FCC Requirements," details the FCC requirements and service requirements for the DECvoice system. Conventions The following conventions are used in this document: Caution Provides information to prevent damage to equipment.
About This Manual United States customers may order documents from: Digital Equipment Corporation Peripherals and Supplies Group P.O. Box CS2008 Nashua, NH 03061 Outside the United States, customers should contact their local Digital sales office.
1 Installation This chapter describes how to unpack, install, and test the DECvoice system hardware. 1.1 Unpacking The DECvoice system hardware includes the DTC04 Q-bus module, telephone line interface (TLI) assembly, and two 20-pin ribbon cables. Unpack each box and check the equipment against the shipping list. Carefully examine the module and TLI assembly for loose components, breaks in the etch, or other signs of damage.
2 Installation Table 1–1 lists the components included in the DECvoice system.
Installation 3 1.2 Installation NOTE Please read Appendix C, FCC Requirements, before you connect DECvoice modules to a telephone line. Install the DECvoice hardware into the Q-bus backplane as follows: 1. Set the addresses for the control status register (CSR) and the device interrupt vector as follows: a. Set the switches on switchpacks E68, E67, and E59 (Figure 1–1) so that the module responds to its assigned address.
4 Installation Figure 1–1 shows the locations of the switchpacks on the module.
Installation Figure 1–2 shows how to set the switches for the CSR address.
6 Installation Table 1–2 shows common CSR settings for DECvoice modules.
Installation 7 Install the DTC04 module board into the Q-bus backplane. The module is a quad-slot board that plugs into an AB/AB or AB/CD slot. NOTE When using an AB/CD slot, make sure there are no modules other than DECvoice modules using the CD slot plugged in above or below a DECvoice module. Figure 1–4 is a block diagram of a Q-bus backplane that shows all the valid locations for a DECvoice module.
8 Installation Verify The CSR and vector settings as follows: If using the MicroVAX Diagnostic Monitor (MDM): a. Refer to the "MDM Release Note" and the other documentation that you received with your MDM kit for instructions on how to boot MDM. You must use release 125 of MDM or greater to test DECvoice modules. (For more troubleshooting and diagnosis information, see Chapter 5 in this manual.) b. If you set the DECvoice modules to the proper CSR setting, they appear in the configuration display.
Installation 9 Install the TLI assembly. You can install the TLI assembly in the holes on a bulkhead panel. Usually, you install the TLI assembly in a pair of B-size holes on the panel. These holes are normally labeled A and B. Figure 1–5 shows where to install the TLI assembly for each system. The following list describes where to install the TLI assembly for each system: • For systems with BA23 bulkhead panels (pedestal or single-box rackmount), the TLI installs in an A + B pair of holes.
10 Installation MA-0549-88 Figure 1–5 Valid Locations for TLI Assembly on a Bulkhead Panel Connect the cables. Each TLI assembly can support two DTC04 modules. The 20-pin cable connectors on the module and TLI assembly are keyed.
Installation Figure 1–6 shows how to plug the cable into the module.
12 Installation Figure 1–7 shows how to plug the cable into the TLI assembly. Make sure you plug the cable in with the ribbon away from the module surface. MA-0551-88 Figure 1–7 Cable Connector to TLI Assembly Figure 1–8 shows how the TLI assembly and module appear in a system.
Installation 13 1.3 Device Addresses Assignments On Q-bus systems, a range of addresses in the top 4K words is reserved as floating address space for options. The range of addresses is from xxx600108 to xxx637768 . The xxx means all top address bits = 1. The first part of the list of devices that you can assign floating address space to is in Table 1–3. The rank represents the sequence of address assignment for the devices.
14 Installation Table 1–3 (Cont.
Installation 15 Table 1–3 (Cont.
16 Installation Table 1–3 (Cont.) CSR Address Assignments Rank Device Size (Decimal) Modulus (Octal) 56 IAV11-B 4 10 57 M7763 4 10 58 IEQ11 8 20 59 ADQ32 16 40 60 DTC04 1 2 1.3.1 Assignment Rules The assignment rules for addresses and devices are as follows: 1. Assign addresses, starting at xxx60010, according to the sequence of Table 1–3. 2. Assign device and gap addresses according to the octal modulus as follows: a.
Installation 17 1.3.2 Address Assignment Examples This section provides two examples of device address assignment for DECvoice. The first example shows how to use the VMS SYSGEN utility to configure new Q-bus devices into the system. SYSGEN is a utility available in the VMS operating system. Only VMS version V5.0 or later can recognize the DECvoice DTC04 Q-bus module. SYSGEN automatically assigns device and vector addresses. The second example shows the proper switch settings for a sample configuration.
18 Installation 5. To check how SYSGEN has configured the system, type CTRL Z at the DEVICE> prompt. Then exit SYSGEN.
Installation 19 The SYSGEN display in Example 1–1 shows that for the first DECvoice the CSR is 761242, and the Vector is 320. The switchpack settings for the first DECvoice are as follows: The settings for switchpack E67 (moving from S6 to S1) are 0 0 0 1 0 1. The settings for switchpack E68 (moving from S6 to S1) are 0 1 0 0 0 1. The settings for switchpack E59 (moving from S6 to S1) are 0 1 1 0 1 0. For the second DECvoice the CSR is 761244, and the Vector is 330.
20 Installation Table 1–4 Floating Vector Address Assignments Rank Device Size (Decimal) Modulus (Octal) 1 DC11 4 10 1 TU58 4 10 2 KL111 4 10 2 DL11-A1 4 10 2 DL11-B1 4 10 2 DLV11-J 16 10 2 DLV11, DLV11-F 4 10 3 DP11 4 10 4 DM11-A 4 10 5 DN11 2 4 6 DM11-BB/AA 2 4 7 DH11 modem control 2 4 8 DR11-A, DRV11-B 4 10 9 DR11-C, DRV11 4 10 10 PA611 (reader + punch) 8 10 11 LPD11 4 10 12 DI07 4 10 13 DX11 4 10 14 DL11-C to DLV11-F 4 10 1
Installation 21 Table 1–4 (Cont.
22 Installation Table 1–4 (Cont.
Installation Table 1–4 (Cont.
24 Installation 1.5 Verifying the Installation Chapter 5 of this document describes the troubleshooting, testing and diagnostic procedures available for DECvoice. For information on verifying the installation, refer to Chapter 5.
2 System Overview This chapter provides an overview of the the DECvoice DTC04 system. The DECvoice system is an integrated hardware and software product that provides a MicroVAX II computer with a voice application platform. The complete system includes hardware and software components. Figure 2-1 is a functional block diagram of the system.
26 System Overview MA-0554-88 Figure 2–2 DECvoice DTC04 Module and TLI Assembly The hardware components include the DECvoice DTC04 Q-bus module and telephone line interface (TLI) assembly with cables. Figure 2-2 shows the hardware components. The software components include the DECvoice Run-Time Library (RTL), ancilliary control process (ACP), device driver, and system firmware. This document deals mainly with the hardware.
System Overview 27 • Digitized speech recording and playback, including full bandwidth and low-bit-rate voice encoding • Control of the TLI that includes DTMF tone signal detection, call progress detection, and outward pulse and DTMF dialing 2.1.2 TLI Assembly The TLI assembly connects the DTC04 module to the telephone network.
28 System Overview The assembly can install into any of the following components. • BA23 pedestal or single-box rack • BA123 world box • H9642 cabinets 2.3 Functional Description This section describes how the DTC04 module and the TLI assembly operate. 2.3.1 DTC04 Module The DTC04 module consists of three functional blocks: the main processor, signal processor, and Q-bus interface. These blocks communicate through interrupts and 64 Kbyte windows into the main processor’s 1 Mbyte memory space.
System Overview • Performs the analysis half of the speech recognition system. • Performs the analysis half of call progress detection. • Controls the telephone line interface. • Generates tone dialing. 29 Q-bus Interface The Q-bus interface consists of a slave section and a memory interface section. The slave section contains the control and status register and sends interrupts to the host. The memory interface section provides communication between the Q-bus and module. 2.3.
30 System Overview Communication with the DTC04 Module The TLI communicates with the DTC04 module through the Intel SLD interconnect. The SLD interconnect is a serial bus that sends 32 bits in each direction every 125 microseconds. The 32 bits are divided into four 8-bit bytes: the primary voice and data byte, the secondary voice and data byte, the control byte, and the signalling byte. The voice and data bytes contain the actual voice data sent and received over the telephone line.
System Overview 31 Storage Conditions Temperature 5° C (41° F) to 50° C (122° F) Relative Humidity 10% to 95% with maximum wet bulb temperature 32° C (90° F) and minimum dew point 2° C (36° F) Operating Conditions Temperature 10° C (50° F) to 40° C (104° F) Relative Humidity 10% to 90% with maximum wet bulb temperature 32° C (90° F) and minimum dew point 2° C (36° F)
3 Software Interface This chapter describes the software interface that the DECvoice hardware uses with the host system. Specifically, this chapter describes: • communication between DECvoice and the host • data movement between DECvoice and the host • initialization of the DECvoice DTC04 module • DECvoice read-only memory commands 3.1 Q-bus Interface The Q-bus interface controls communication between the DECvoice DTC04 module and the host system.
Software Interface 33 NOTE DECvoice treats all write cycles to the CSR as complete word cycles. DECvoice does not support the writing of individual bytes to the CSR. Figure 3-1 shows the CSR. Table 3-1 describes the bit assignments in the CSR. MA-0555-88 Figure 3–1 The Q-bus Control and Status Register Table 3–1 CSR Bit Assignments Bits Name Function 03:00 Module state (MS) This field passes the complete module state from the main microprocessor microcode to the host.
34 Software Interface Table 3–1 (Cont.) CSR Bit Assignments Bits Name Function 05 Memory enable (ME) ME is a read-write bit. When ME is set, the Q-bus can access the module memory. When ME is reset, the Q-bus cannot access the module memory. The ME bit is cleared when the Q-bus is initialized (BINIT) or when the module is powered up. NOTE The ME bit prevents all the DECvoice modules in a system from responding to memory location 0 at power-up.
Software Interface 35 Table 3–1 (Cont.) CSR Bit Assignments Bits Name Function 13:08 Memory bank (MB) MB is a read-write field. The MB field provides the bank selection bits (21 through 16) to the module memory address decoder. For example, suppose the memory bank field is set to 1216 and the memory enable bit is set. In this case, the module responds to Q-bus memory references for locations 12000016 through 12FFFF16 . The addressing of the module memory is programmable.
36 Software Interface Table 3–2 Module State Field Values Value Name Meaning 0 RESET The module is held in the reset state. 1 READY The module is ready for operation. 2 BROKEN The module has a hardware problem. 3 PARITY There is a parity error in the module’s RAM. 4 TRAP The module hardware detected a microcode error. 5 BUG The module microcode detected a microcode error. 6 RING The module detected an error with the host software. 7 ROM The module detected a ROM checksum error.
Software Interface 37 3.3 Data Transfer Scheme This section describes the shared-memory scheme used to move data between the host system and the DTC04 module. 3.3.1 Rings Data moves between the host and the module through two unidirectional rings. These rings use a total of 64 Kbytes of memory in the module. This memory is shared by the host and the module. Each ring uses 32 Kbytes of the shared memory. NOTE The last 256 bytes of each 32 Kbyte area are reserved.
38 Software Interface Figure 3-2 shows the structure of command and message rings in shared memory.
Software Interface 39 3.3.1.1 Buffer Structure Figure 3-3 shows the structure of each buffer in the command and message rings. Figure 3–3 Buffer Structure Flag The flag field in the buffer determines whether the sender or the receiver owns the buffer. When the host initializes the shared memory, all of the buffers are marked as owned by the sender. A sender passes data to a receiver as follows: 1. Waits until enough buffers are available to send the data, starting with the buffer at the load pointer. 2.
40 Software Interface The flag field contains four flags (bits 0 through 3). The rest of the bits in the field must be 0 or the result is undefined. The sender can change any flag in the field, except the LIR flag. The receiver can only change the OWN flag. Table 3-4 describes each flag. Table 3–4 Flag Field Flags Flag Name Bit Function OWN 0 This flag indicates the current owner of the buffer. If the flag is 0, the sender owns the buffer. If the flag is 1, the receiver owns the buffer.
Software Interface 41 Data[ ] The data field contains the actual data being sent or received. Figure 3-4 summarizes how the host enters command data into the command ring. (The module enters message data into the message ring the same way.
42 Software Interface 3.3.2 Interrupts There are two ways to manage data flow between the host and the DTC04 module. One way is to use the fixed fields at the beginning of each data buffer in the command and message rings. This method is described in Section 3.3.1. Using these fixed fields, the host can perform all ring management by polling each ring to find out when buffers are full or empty. The other way to manage data flow is to use interrupts. The DTC04 module implements interrupts.
Software Interface 43 3.3.3 Commands and Messages This section describes the formats of commands and messages. The host uses the command ring in shared memory to send commands to the module. The module uses the message ring in shared memory to send messages to the host. A message is a reply to a previous command. Typically, a command can cause DECvoice to return many messages. The module processes the commands in the order they enter the ring.
44 Software Interface Slot The DECvoice module provides an environment for the execution of subsystems. A subsystem is a group of processes that performs a function. For example, all the processes that translate text to speech are contained in a subsystem. Each subsystem loaded into the module is associated with a slot. The slot is used to locate and to identify a particular subsystem for a particular task.
Software Interface 45 3.3.3.2 Message Format A message consists of a fixed-size header, followed by a variable length block of data. Figure 3-6 shows the format of messages. MA-0560-88 Figure 3–6 Message Format MSGTAG The MSGTAG field holds a copy of the MSGTAG field in the command that prompted DECvoice to return a message. The message tag informs the driving software which messages belong with which commands. DECvoice does not interpret the message tag.
46 Software Interface 3.4 Initialization The host must initialize the module before using it. Initialization occurs in three stages. 1. The host initializes the module’s data transport system. 2. The host loads the module microcode into the module’s private memory, then starts executing the microcode. 3. The microcode synchronizes with the telephone line interface hardware, then reads back that hardware’s identification code. 3.4.
Software Interface 47 6. The module acknowledges the alert by clearing the module alert bit in the CSR. Then the module begins to process commands received from the host. 3.4.2 Stage 2 The host loads the microcode into the module’s private memory, then executes the microcode as follows: 1. The host sends a STATUS command to the module to get the base address and size of the block of shared memory that is available for allocation. 2.
48 Software Interface 3.5 Basic ROM Commands This section describes commands that the host can use to move data into the module’s shared memory and check the module’s current status. This section covers three basic commands: LOAD, JUMP, and STATUS. 3.5.1 LOAD The LOAD command copies a block of data into the module’s main memory. During initialization, the host uses this command to copy the base microcode image into main memory.
Software Interface 49 OP This field contains the operation code that identifies the command as the LOAD command. The OP code for the LOAD command is 0. Status This field contains status information about the execution of the command. The module writes values into this field that indicate whether or not the command executed successfully. Offset This field contains the offset half of the 80186 address where the command data block is placed.
50 Software Interface 3.5.2 JUMP This command transfers control of execution from the resident ROM on the module to the loaded microcode. Figure 3-8 shows the structure of the JUMP command. MA-0562-88 Figure 3–8 JUMP Command Format MSGTAG The message tag informs the driving software which messages belong with which commands. DECvoice does not interpret the message tag. The message tag is only significant to the driving software.
Software Interface 51 Offset This field contains the offset half of the 80186 address where execution begins. This value is copied into the module’s IP register. The complete address for the command data is segmented into two halves, offset and base. Only the offset half of the address is incremented during a jump operation. Base This field contains the base half of the 80186 address where execution begins. This value is copied into the module’s CS register. 3.5.
52 Software Interface OP This field contains the operation code that identifies the command as the STATUS command. The code for the STATUS command is 4. Status This field contains status information about the execution of the command. The module writes values into this field that indicate whether or not the command executed successfully. 3.5.3.2 Status Message Figure 3-10 shows the format of the STATUS message.
Software Interface 53 Type This field contains the type code that identifies the message as a reply to the STATUS command. The code for the message type is 4. Status This field contains status information about the generation of the message. The module writes values into this field that indicate whether or not the module successfully generated the message. ROMID This field contains the version number of the firmware in slot 0.
54 Software Interface RAMSIZE If the STATUS command is sent to the bootstrap and diagnostic ROM, this field contains the number of paragraphs of memory available for the host to allocate. This feature lets the host initialize its memory allocation map without knowing the location or size of the memory the ROM is using. If the STATUS command is sent to the base microcode, this field is always 0.
4 Telephone Interface This chapter describes the telephone line interface (TLI) that DECvoice uses to connect to the telephone network. The chapter is divided into two main sections: subscriber line datalink (SLD) interface and North American TLI interface. 4.1 SLD Interface DECvoice uses a modified version of the Intel SLD protocol to control communication with the telephone network. The Intel SLD is a threewire interface for synchronous data transfer between a master and a slave device.
56 Telephone Interface SDIR The SDIR signal controls the direction of transmission over the SLD line. When the SDIR line is asserted, the SLD line transfers data to the slave device. When the SDIR line is not asserted, the SLD line transfers data to the master device. SLD The SLD line is the data line for the system. The SLD line supports a 512 Kbits/s rate, as defined by the SCL clock signal.
Telephone Interface 57 4.1.1 SLD System In an Intel SLD master-slave system, the master controls the rate and direction of data flow by generating clock and directional signals. The slave reads the clock and direction signals. In the DECvoice system, the TLI assembly serves as the master and the DTC04 module as the slave. The TLI controls the rate and direction of data transfer between the telephone network and the module.
58 Telephone Interface This separation makes it possible to have TLI assemblies that are not mounted in the Q-bus IO connector panel. If there is any length of cable between the TLI assembly and the module, it is necessary to have separate send and receive data wires. The two wires are called TX DATA H and RX DATA H (Table 4-1). The module sends data to the TLI over the TX DATA H line. The TLI sends its identification code and other data to the module over RX DATA H.
Telephone Interface 59 4.1.3 Connection Between the Module and TLI This section describes the actual connection between the DTC04 module and the TLI assembly. The module and TLI are connected over a 20-pin cable. Figure 4-1 is a diagram of the connector. Table 4-1 describes each pin assignment. MA-0565-88 Figure 4–1 20-Pin Connector Table 4–1 Pin Assignments Pin Name Function 1 +12 V Supplies +12 V to TLI assembly. 2 +5 V Supplies +5 V to TLI assembly.
60 Telephone Interface Table 4–1 (Cont.) Pin Assignments Pin Name Function 7 SCL H This line is for the clock signal. The TLI drives this line, controlling the rate of data movement over the TX DATA H and RX DATA H lines. 8 GND Ground. 9 SDIR H This line is for the direction signal. The TLI drives this line, controlling the direction of data movement over the TX DATA H and RX DATA H lines. 10 GND Ground. 11 TX DATA H (SLD H) The module uses this line to send data to the TLI assembly.
Telephone Interface 61 4.2 North American Telephone Line Interface This section briefly describes the DECvoice TLI designed for use in North America. 4.2.1 TLI to Telephone Line Connection The circuit that connects the TLI to the telephone network must meet certain North American telephone regulations, provide access to the network, and protect the TLI circuitry. The TLI connects to the telephone line through modular telephone jacks for RJ11 service.
62 Telephone Interface 4.2.2.2 Identification The TLI sends an identification code to the DTC04 module. If two modules are connected to a TLI, the TLI sends the same identification code to each module. This identification is factory set to identify the TLI as a North American analog loop start interface. 4.2.2.3 Reset When the module asserts the TLI RESET signal to the TLI, the TLI cannot accept any calls. This prevents the TLI from connecting to the telephone network while the module is resetting. 4.2.
Telephone Interface 63 4.2.3.4 Signaling Byte This section describes how DECvoice uses the signaling byte during a module write operation (from module to TLI) and a module read operation (from TLI to module). Module Write Operation The DTC04 module sends the signaling byte to the TLI to control the output of the signaling pins on the 29C50 chip. Figure 4-2 shows how the bits in the signaling byte correspond to the pins on the 29C50 chip.
5 Troubleshooting and Diagnostic Procedures This chapter contains two sections: • Section 5.1, Troubleshooting, contains a troubleshooting table to help you find and solve hardware problems. • Section 5.2, Diagnostic Procedures, describes the diagnostic programs available to check the operating status of the DECvoice module and telephone line interface (TLI). There are two subsets of diagnostic programs: DECvoice test programs and the MicroVAX diagnostic monitor (MDM) program. 5.
Troubleshooting and Diagnostic Procedures 65 Table 5–1 (Cont.) Troubleshooting Table Problem Possible Cause Corrective Action On VAX/VMS V5.0 or V5.0-1, the WINDOW_ SYSTEM is zero. Change the WINDOW_SYSTEM sysgen parameter to 1, and reboot the system. Refer to the VAX/VMS SYSGEN manual for information on how to change this parameter.
66 Troubleshooting and Diagnostic Procedures Table 5–1 (Cont.) Troubleshooting Table Problem Possible Cause Corrective Action DECvoice device (VXA0:, VXB0:, and so on) is visible when you issue a "SHOW DEVICE VX" command, but on VAX/VMS, modules fail with device timeout errors, and on MDM, modules fail with "COULD NOT GENERATE HOST INTERRUPT" errors. The DECvoice device VECTOR is set incorrectly. Shutdown and power off the system, remove the module(s) and check the vector settings.
Troubleshooting and Diagnostic Procedures 67 Table 5–1 (Cont.) Troubleshooting Table Problem Possible Cause Corrective Action The DECvoice device (VXA0:, VXB0:, and so on) is visible when you issue DCL "SHOW DEVICE VX" command but is marked as offline Lack of system page table entries ( SPTE ) for the driver buffers. Do not attempt to access an offline DECvoice. Each DECvoice requires 128 SPTEs to function.
68 Troubleshooting and Diagnostic Procedures Table 5–1 (Cont.) Troubleshooting Table Problem Possible Cause Corrective Action In a newly installed system or in a system that has just had the Q22-bus hardware reconfigured, the system hangs or drops off the VAXcluster shortly after the DECvoice ACP OPCOM "starting" message is displayed. Invalid Q22-bus configuration. For information about configuring the Q22-bus, see Section 1.3 in this manual.
Troubleshooting and Diagnostic Procedures 69 5.2 Diagnostic Procedures This section describes the diagnostic programs available to check the operating status of the DECvoice module and telephone line interface (TLI). 5.2.1 DECvoice Test Programs The DECvoice test programs let users check the operating status of the DTC04 module and the TLI. These programs are included with the DECvoice software package in the SYS$SYSROOT:[VOX$DTC.SYSTEM] directory. There are three programs available: VOX$TEST.
70 Troubleshooting and Diagnostic Procedures After the VOX$TEST symbol is declared, operators can test individual modules by including the device in the command line. Operators can test the DECvoice device VXB0: by typing the following: $ VOX$TEST VXB0: 5.2.1.2 VOX$DIAL.EXE This standalone test program runs the DTC04 module through a program that verifies the TLI and telephone wiring. Users must have operator privileges to run VOX$DIAL.EXE. VOX$DIAL.EXE is run the same way as VOX$TEST.EXE. VOX$DIAL.
Troubleshooting and Diagnostic Procedures 71 The configuration display shows the current ROM revisions and the TLI type. In this display, DECvoice modules appear as DTC04. 4. Test the existing system to make sure it is running properly. For information on testing and troubleshooting, see the MicroVAX Systems Maintenance Guide 5. After the test runs successfully, remove the tape cartridge or diskette and turn the I/O power switch off (0).
A Connector Pinouts A.1 Q-bus Connector The module connects only to the AB row of the Q-bus. However, the module does connect to the power pins in the CD row. The module also reroutes the DMG(IO) and IAK(IO) signals in the CD rows, so that these signals are passed to the next slot in the bus. Table A-1 lists the pin assignments for the module plugged into the AB row of the Q-bus.
Connector Pinouts 73 Table A–1 (Cont.
74 Connector Pinouts A.2 SLD Connector The SLD connector is a 20-pin, ribbon cable connector. Figure A-2 is a diagram of the connector. Table A-2 lists the pin assignments for each pin on the SLD connector.
Connector Pinouts 75 Table A–2 (Cont.
B Telephonics DECvoice works with standard analog loopstart telephone lines. Each individual DECvoice system acts like a separate subscriber telephone terminal on the telephone network. This appendix describes the telephonic characteristics of the DECvoice DTC04 system. B.1 Connection DECvoice telephone lines are connected using RJ11 telephone service in the USA, and using CA11 telephone service in Canada. B.2 Certification DECvoice is certified to comply with Part 68 of the FCC rules.
Telephonics 77 B.4 Ring Detection Ringer Equivalence The DECvoice ring detection circuit has a ringer equivalence of .3B, as determined by FCC test methods. The ring detection circuit has a load number of 10 by DOC test methods. Ring Characteristics DECvoice detects rings with frequencies between 15.3 Hz and 68.0 Hz and voltages between 40 and 150 volts rms. B.5 Tone Detection DECvoice can detect DTMF signals. DTMF signals are the signals that a Touch-Tone phone creates.
78 Telephonics Tone Levels The DTMF tones must typically be at least 12 dB louder than the noise floor and 16 dB louder than any other tone within the DTMF detection band. Each frequency of the DTMF tone must be between -5 dBm and -26 dBm when measured at the DECvoice telephone line connections. B.6 Wink Detection DECvoice can detect momentary losses in loop current. DECvoice can use these losses to detect that the other end of the telephone call has cleared down.
C Communication Requirements C.1 FCC Requirements 1. The Federal Communications Commission (FCC) has established rules that permit this device to be directly connected to the telephone network. Standardized jacks are used for these connections. This equipment should not be used on party lines or coin lines. 2. If this device is malfunctioning, it may also be causing harm to the telephone network.
80 Communication Requirements C.2 Communication Requirements in Canada The Canadian Department of Communications (DOC) label on the DECvoice CK-DTC04 identifies certified equipment. This certification means that the equipment meets certain telecommunications network protective, operational, and safety requirements. The DOC does not guarantee the equipment will operate to the user’s satisfaction.
Communication Requirements 81 CAUTION Do not try to make such connections yourself. Contact the appropriate electric inspection authority or electrician. C.3 Service Requirements In the event of equipment malfunction, all repairs should be performed by Digital or an authorized agent. It is the responsibility of the user requiring service to report the need for service to Digital or to one of our authorized agents.
Glossary Algorithm conversion The conversion from one voice encoding algorithm to another. DECvoice supports three voice encoding algorithms: full bandwidth 64 Kbits/s law, full bandwidth 64 Kbits/s A-law, and 16 Kbits/s subband compressed encoding. Ancilliary Control Process (ACP) A software component of the DECvoice system. Backplane A connector block that printed circuit boards plug into. A printed circuit board containing the bus. Binary A number system that uses only two digits: 0 and 1.
Glossary 83 Byte A group of eight binary digits (bits). Call progress detection The monitoring of a call to determine if the call was answered, the line was busy, or no one was home (the call timed out). Computer system A combination of hardware, software, and external devices that performs specific operations or tasks. Console terminal The terminal that you use when installing software and running diagnostic programs.
84 Glossary DECvoice system An integrated hardware and software product that provides a computer with a voice application platform. Device The general name for any entity connected to a system that can receive, store, or transmit data. Diagnostic program A program that detects and identifies abnormal system hardware operation. The MicroVAX Diagnostic Monitor software used to test a system contains several diagnostic programs.
Glossary 85 Initialization The process that the host performs on DECvoice at the beginning of a working session. On initialization, the host allocates and assigns a channel to the DECvoice module, sets up communciation between the DECvoice module and device driver, runs the DECvoice on-board diagnostics, and optionally loads all the default DECvoice subsystems. Interface A device or piece of software that lets the DECvoice system communicate with the Q-bus or telephone network.
86 Glossary Message handle The identifier of a particular DECvoice message. Applications use the message handle to access and reference a particular message. The message handle contains specific information about a message including the message size (in bytes), length (in milliseconds), endcoding algorithm, reference count, language, RTL version number, creation date, and date of last modification. North American Telephone Line Interface A telephone network interface designed for use in North America.
Glossary 87 Signal processor A digital signal processor providing 64 Kbytes of high speed static random access memory, and a shared-memory interface to perform speech processing. A Texas Instruments TMS320C25 or TMS320 family chip that is part of the DTC04 module. SLD interconnect A serial bus used to transmit voice, data and control information. Software Programs executed by the DECvoice system to perform a chosen or required function. (Compare Hardware.
88 Glossary TLI to DTC04 module connection The telephone line interface connects to the module through a modification of the Intel Subscriber Line Datalink (SLD) protocol. TLI to telephone line connection The circuit that connects the telephone line interface to the telephone network and meets certain North American telephone regulations. The TLI connects to the telephone line through modular telephone jacks for RJ11 service.
Index A Address vector settings, 19 Associated documents, x C CA11 connection, 76 Certification, 76 Commands, 43 format, 43 JUMP, 50 LOAD, 48 STATUS, 50 Communication Requirements Canadian, 80 U.S.
Index–2 Installation, 3 Intel SLD control chip, 62 Interface North American TLI, 61 SLD, 55 Interrupts, 42 Interrupt scheme, 42 Interrupt vector address assignments, 19 J JUMP command, 50 L LOAD command, 48 M MDM diagnostics, 70 Messages, 43 format, 45 Module connector, 59 initialization, 46 specifications, 30 N North American TLI interface, 61 O Order numbers, 2 Overview of system, 25 P Part numbers, 2 Pin assignments for Q-bus connector, 72 Pin assignments for SLD connector, 74 Pulse dialing, 78
Index–3 T Telephone interfaces, 55 Telephone Line Interface (TLI) features, 27 functional description, 29 identification, 62 installation, 3 physical description, 27 reset, 62 Telephonic characteristics of DECvoice, 76 TLI to DTC04 module connection, 61 TLI to telephone line connection, 61 Tone detection, 77 frequencies, 77 levels, 78 timing, 77 Touch-tone, 77 Troubleshooting procedure, 64 table, 64 Troubleshooting procedures, 64 U Unpacking, 1 V Vector address assignment, 19 Voice byte, 62 Voice signal
