Contents

________________________________________________________________________

iii

Contents v

_______________________________________________________________________________________

_______________________________________________________________________________________

About This Document

_______________________________________________________________________________________

_______________________________________________________________________________________

This document describes most major aspects of networking AUDIX?? Voice Messaging Systems. Its purpose is to assist any group or person involved with the implementation of an AUDIX network. If it does not contain the information you desire, please ???ll out the feedback form with your comments and send it to the originating organization.

INTENDED AUDIENCE

This document is intended for account teams, the Business Communications Systems Design Center (BCSDC), the Technical Service Center (TSC), the Sales and Technical Response Center (STRC), ???eld technicians, and hotline personnel.

PREREQUISITE SKILLS OR KNOWLEDGE

No prerequisite skills or knowledge are presumed. However, it is recommended that someone with networking experience be available to assist anyone that is new to this type of implementation.

HOW THIS DOCUMENT IS ORGANIZED

Information in this document is organized as follows.

???Chapter 1, Introduction, describes the network interfaces, an overview of how a network is implemented, and the AUDIX system requirements that pertain to any type of AUDIX network.

???Chapter 2, Dedicated EIA RS-232 Networks, provides examples and requirements when using direct cabling to transmit data between adjuncts and PCs using the Electronic Industries Association (EIA) RS-232 protocol.

???Chapter 3, Switched EIA RS-232 Networks, provides examples and requirements when using a switched connection through a modem (to a tip and ring circuit) or through a data module [to a Digital Communications Protocol (DCP) circuit] to the switch.

???Chapter 4, DCP Mode 1 Networks ??? 56 Kbps, provides examples and requirements when using AT&T???s DCP Mode 1 for interlocation data transmission.

???Chapter 5, DCP Mode 2 Networks ??? Modem Pooling, provides examples and requirements when using AT&T???s DCP Mode 2 for interlocation data transmission.

???Chapter 6, DCP Mode 3 Networks ??? 64 Kbps, provides examples and requirements when using AT&T???s DCP Mode 3 for colocated or interlocation data transmission.

xvii

_______________________________________________________________________________________

_______________________________________________________________________________________

CONVENTIONS USED IN THIS DOCUMENT

The following typographic conventions are used in this document:

???Information that appears on your terminal screen ??? including displays, ???eld names, prompts, and error messages ??? is shown in constant-width type. Information that you are to type just as it appears in the document is shown in constant-width bold type. For example:

In the machine name ???eld, type audix.

???Terminal keys that you press are shown in curved-edge boxes. For example, an instruction to press the return, carriage return, or equivalent key appears in this document as:

Press ENTER .

???Two or three keys that you are to press at the same time (that is, you are to hold down the ???rst key while pressing the second key and, if appropriate, the third key as well) are enclosed together, separated

by hyphens, in a curved-edge box. For example, an instruction to press and hold CTRL while typing the letter d appears in this document as:

Press CTRL-d .

???Variables for which you or the system substitute a word speci???c to your own application are shown in italic type. For example, an error message that appears on the screen with the name of your own speci???c ???lename might appear generically in this document as:

Your ???le <???lename> is formatted incorrectly.

TRADEMARKS AND SERVICE MARKS

The following trademarked products are mentioned in this document:

???5ESS?? Switch is a registered trademark of AT&T

???AUDIX?? System is a registered trademark of AT&T

???DATAPHONE?? is a registered trademark and service mark of AT&T

???DEFINITY?? Communications System is a registered trademark of AT&T

???DIMENSION?? PBX is a registered trademark of AT&T

1. Introduction

_______________________________________________________________________________________

_______________________________________________________________________________________

AUDIX Networking enables an organization to transmit messages between two or more AUDIX systems, making the group of systems appear as one large system. One-Cabinet AUDIX systems, Two-Cabinet AUDIX systems, and AUDIX Large systems can be used. These systems can be located on the same site or spread out over several locations in the same or different cities. A single network can have up to 101 systems (a local system can be connected to up to 100 remote systems).

When considering adding more than one system to a single switch, keep in mind that although several systems can be networked at a single location, the systems may or may not be able to be installed as fully integrated AUDIX systems (that is, with a data link installed between the AUDIX system and the switch). The number of directly connected AUDIX adjuncts depends on the switch:

???System 75 and DEFINITY Communications System Generic 1, Generic 3i, and Generic 3s support one directly connected AUDIX system.

???System 85 R2V2 and R2V3 support up to four AUDIX adjuncts.

???System 85 R2V4 and DEFINITY Generic 2 and Generic 3r support up to eight AUDIX adjuncts.

Any additional AUDIX systems must be installed as stand-alone systems.

THE NETWORK INTERFACE

An AUDIX system provides three types of network connections, using either the Electronic Industries Association (EIA) RS-232 protocol or AT&T???s DCP. They are:

???Dedicated RS-232: AUDIX systems communicate through direct cabling. No connection to the switch is required. Communication between AUDIX systems is straight RS-232. Any channel connected in this manner cannot be shared with other adjuncts or with other AUDIX system applications. This connection requires AUDIX R1V5 or later software and a TN539 or TN539B ACCE circuit pack.

???Switched RS-232: AUDIX systems communicate through dial-up modems. Communication between systems is via analog facilities. Channels connected in this manner can be shared with other systems or with the AUDIX Call Detail Recording Package (CDR). This connection requires AUDIX R1V5 or later software and a TN539 or TN539B ACCE circuit pack.

Special Application: The RS-232 channels can be converted to DCP before entering the switch. This is done with a data module instead of the modem. This, too, is a dial-up connection; all six AUDIX network channels appear at the switch as DCP channels.

1-1

1-2 Introduction

________________________________________________________________________________________________

________________________________________________________________________________________________

???Switched DCP: AUDIX systems communicate through dial-up DCP connections at the switch. Communication between systems can be via digital or analog facilities. DCP modes 1, 2, and 3 are supported. Channels connected in this manner can be shared with other systems for networking and for other AUDIX system applications. This connection requires AUDIX R1V3 or later software and an ACC (TN366 or TN366B) or ACCE (TN539 or TN539B) circuit pack.

The TN539 or TN539B ACCE circuit pack provides two RS-232 channels and four DCP channels. Both types are two-way communications links. The type or types of connections used depend on the location and number of AUDIX systems involved, the type of switch(es) involved, networking facilities, and whether or not the customer wants to use the Text Services Interface and/or Call Detail Recording applications.

LOCAL NETWORKING

In a local network setup, one or more AUDIX systems work with a single switch. The local system can be networked with up to 100 other remote AUDIX adjuncts. In this setup, the local system is the one to which the administration terminal the system administrator is using is connected; all other systems are considered remote. All AUDIX subscribers can be assigned the same (or no) pre???xes and separate extension numbers, or different pre???xes to distinguish among local systems.

A one-cabinet 16-port AUDIX system can provide services to up to 2000 local subscribers; a two-cabinet 32-port system can handle twice as many. When AUDIX systems are integrated into a local network, they take on the appearance of one large AUDIX system. The AUDIX systems can reside together in the same equipment room with the switch, or in different locations according to the type of connections made.

1-4 Introduction

________________________________________________________________________________________________

________________________________________________________________________________________________

AUDIX Software

An AUDIX network can consist of a mixture of R1V3, R1V4, R1V5, R1V6, and R1V7 systems. If desired, you may upgrade your AUDIX-L to R1V5 or upgrade your AUDIX one- or two-cabinet system to the latest software version. See the System Description manual (585-305-201) for ordering codes.

ACC/ACCE

The AUDIX Communications Controller (ACC) or AUDIX Communications Controller Enhanced (ACCE) is the circuit pack that provides the interconnections for AUDIX networking. It must be installed in slot 03 of a one- or two-cabinet AUDIX system and in slot 16 of an AUDIX Large Data Base Processor (DBP) carrier (J58888K).

This section describes the ACC or ACCE circuit packs currently in existence. All new AUDIX systems ordered with networking are shipped with the latest circuit pack available, currently the TN539B AUDIX Communications Controller Enhanced (ACCE). However, a new AUDIX system can be added to an existing network where the earlier TN366, TN366B, or TN539 circuit packs are used.

TN366 ACC

This circuit pack provides four DCP channels. It must be a TN366 vintage 5 or later. This circuit pack is no longer orderable, but if the customer has an older vintage and wishes to upgrade, this circuit pack is available through QPPCN 330DR (comcode 103279840). It will work with R1V3 and later software.

TN366B ACC

This circuit pack provides four DCP channels. It will work with R1V3 or later software. This circuit pack is no longer orderable (comcode 106186588).

The TN366B is a TN366 that has been enhanced for the following reasons:

???The TN366B will work with modem pools that use 7400A DSUs; the original TN366 will not.

???The TN366B will work with the MERLIN II Communications System which is used as a DCP interface for non-DCP switches; the TN366 will not.

???When a Generic 2 universal module serves as the host switch, the TN366B allows access to all four DCP channels; the TN366 does not.

Introduction 1-5

_______________________________________________________________________________________

_______________________________________________________________________________________

TN539 ACCE

This circuit pack provides four DCP channels and two RS-232 channels. It will work with R1V5 and later software. The Vintage 7 TN539 permits six simultaneously active ports. Vintage 4 and earlier of the TN539 permits four simultaneously active ports. This circuit pack is no longer orderable (comcode 103281473). It provides all the functionality of the TN366 or TN366B with the following additions:

???Multi-stage dialing

???DCP Mode 1 (56 Kbps) interface

???RS-232 interface

TN539B ACCE

This pack replaces the TN366, TN366B, or TN539 circuit pack (comcode 106757768). It provides all the functionality of the previous networking boards as well as 56 and 64 Kbps loopback testing capabilities.

All new systems ship with a TN539B ACCE. In addition, you may wish to upgrade an earlier board to a TN539B ACCE for the following reasons:

???You have a TN366 or TN366B ACC and you wish to use the two RS-232 ports available on the TN539B.

???You have a TN366 or TN366B ACC and you wish to obtain the additional activity status information available on the maintenance : network form in R1V7 (for example, if you are using the R1V7 network turnaround feature).

???You have a TN366 or TN366B ACC or a TN539 ACCE and you wish to upgrade to a TN539B ACCE for performance reasons. A TN539B is required at both the sending and receiving machine in order to achieve increased performance.

???You have a TN539 ACCE running DCP Mode 1 (56 Kbps) connections and you wish to replace it with the TN539B in order to take advantage of the AUDIX R1V7 loop-around testing capabilities and possible performance improvements (see the previous item).

All TN539B ACCE orders (new or upgrade) include two H600-330, Group 1 null-modem adapters and one H600-331, Group 2 cable. See the System Description manual (585-305-201) for ordering codes.

1-6 Introduction

________________________________________________________________________________________________

________________________________________________________________________________________________

Other AUDIX Circuit Pack Requirements

Certain circuit packs must be present and certain other packs must be of a speci???c vintage or issue.

One-Cabinet and Two-Cabinet AUDIX System

In slot 01 of the base cabinet the AUDIX system must have the following:

??? TN506B circuit pack (comcode 105222301).

In slot 04 of the base cabinet the AUDIX system must have the following:

???TN472C vintage 2 (white wire 10-17) or later circuit pack (comcode 105474126). This is the Data Base Processor Central Processing Unit (DBP-CPU).

In slot 06 of the base cabinet the AUDIX system must have the following:

???UN160B vintage 2 or later circuit pack (comcode 105319818). This is the Data Base Processor Interface (DBPI).

AUDIX Large System

In slot 01 of the DBP carrier (J58888K) the AUDIX system must have the following:

??? TN506B circuit pack (comcode 105222301).

In slots 04-07 and 12-14 of the DBP carrier the AUDIX system must have the following:

??? TN508 (vintage 4 or higher); up to seven packs.

In slot 08 of the DBP carrier the AUDIX system must have the following:

??? TN509C circuit pack (comcode 105319286). This circuit pack is available through QPPCN 444DR.

In slot 10 of the control carrier (J58888H) the AUDIX system must have the following:

??? UN160B circuit pack (comcode 105319818).

In slot 08 of the power carrier (J58888L) the AUDIX system must have the following:

??? 495JB power converter (comcode 104016746).

Rear Connector Panel and Backplane

The network cabling requires a connector on the back of the AUDIX system cabinet. This connector must be attached to the backplane. Certain versions of the backplane require wire modi???cation.

1-10 Introduction

________________________________________________________________________________________________

________________________________________________________________________________________________

451A ADAPTERS, 8-PIN

F/F (COMES WITH THE

CONNECT FIELD

AMPHENOL 50-PIN8-PIN to 6-WIRE

MALE CONNECTORS

MALE CONNECTOR

A

CONNECT TO DEDICATED

OR SWITCHED RS-232

ENDPOINTS

B

RS-232 25-PIN

MALE CONNECTORS

5.0 FT (1.524 M)

Figure 1-3. H600-331, Group 1 AUDIX Networking Breakout Cable

1-12 Introduction

________________________________________________________________________________________________

________________________________________________________________________________________________

R1V6 Release

Major changes brought about by AUDIX R1V6 software and the vintage 7 TN539:

???With the R1V3, R1V4, and R1V5 software releases, only four channels could be simultaneously active. AUDIX systems with R1V6 software and a vintage 7 TN539 or TN539B ACCE can use all six networking ports simultaneously (however, System 75, Generic 1, Generic 3, and MERLIN II can still only access two of the four DCP channels).

R1V7 Release

Major changes brought about by AUDIX R1V7 software and the TN539B board:

???The new TN539B ACCE board can provide faster throughput than previous networking boards for networks with heavy traf???c.

???The R1V7 software and the TN539B ACCE board permit 56 or 64 Kbps loopback testing; the serving of???ce can send data to an AUDIX port and, if the connection is up, the AUDIX system will echo the data back to the serving of???ce. See Chapter 14, AUDIX Network Testing for details.

???On R1V7 systems, the network turnaround feature can be administered. This option is activated using

the system : translation : machine : audix/amis/call delivery form; it can

be administered on a system-wide or per-machine basis.

???If network connection turnaround is implemented, the local machine will call a remote machine and do the following: notify the remote system of its updated subscriber information, request updated subscriber information from the remote system, and send voice mail and updated message status information to the remote system. Then network connection will then be turned around and the remaining events will occur: the remote system will request updated subscriber information from the local system, notify the local system of its updated subscriber information, and send voice mail and updated message status information to the local system.

???If the network turnaround feature is not implemented, the local machine will call a remote machine and do the following: notify the remote system of its updated subscriber information, request updated subscriber information from the remote system, and send voice mail and updated message status information to the remote system. The call will then be disconnected.

The network turnaround feature reduces system overhead time and long-distance charges by allowing all of these events to occur with a single call rather than two calls. If cost control from a central point is not critical, greater ef???ciency can be gained by implementing the network connection turnaround feature. The connection can only be turned around once during a single call.

2. Dedicated EIA RS-232 Networks

_______________________________________________________________________________________

_______________________________________________________________________________________

AUDIX networking can be implemented using a dedicated Electronic Industries Association (EIA) RS-232 interface. This chapter presents dedicated RS-232 con???gurations supported by AT&T. These examples show AUDIX using RS-232 at both ends. For networks with RS-232 and DCP mixed, see Chapter 7,

Mixtures of RS-232 and DCP Networks.

If your customer develops their own method, contact the Business Communications Systems Design Center (BCSDC) to make sure the method is feasible. Each of the con???gurations presented here is accompanied by the equipment required for the AUDIX systems.

CONSIDERATIONS

If a customer is considering using dedicated RS-232 connections in their AUDIX network, keep the following in mind:

???Only local networking con???gurations are supported.

???A maximum of three AUDIX systems can be networked via this method.

???AUDIX software must be R1V5 or later.

???The customer needs a TN539 or TN539B networking board.

???This type of network can operate at speeds up to 64 Kbps (depending on distance).

GENERAL INFORMATION

Figure 2-1, Dedicated RS-232 Network of Two AUDIX Systems, shows two AUDIX systems networked using dedicated RS-232 connections. The transmission schedules (that is, the times set up for one system to connect to another for the purpose of transmitting messages) can be set so the systems will not attempt to use the channel at the same time. If they do attempt simultaneous transmissions, the system denied access

2-1

2-2 Dedicated EIA RS-232 Networks

________________________________________________________________________________________________

________________________________________________________________________________________________

to the channel will retry automatically.

Normally both RS-232 channels are required for networking. If only one channel is used, the other channel can be used for the AUDIX Call Detail Recording (CDR) feature. However, this con???guration is only appropriate for networks with low traf???c volume. If a customer chooses to use a channel for CDR, AT&T recommends running CDR only during non-peak hours, thereby leaving two ports available for networking during peak hours. See Figure 2-2, Dedicated RS-232 Network of Two AUDIX Systems and a PC (Low Traf???c Only). A switched RS-232 con???guration is always preferable for networks that do not have very low traf???c.

If another system must be added to Figure 2-1, this can be done as shown in Figure 2-3, Dedicated RS-232 Network of Three AUDIX Systems (Low Traf???c Only). If a PC is required in this case, at least one channel from each system must be converted to a switched connection. See Figure 2-4, Dedicated RS-232 Network of Three AUDIX Systems and a PC. Instead of switching cables as with con???gurations such as Figure 2-2, the PC has dial-up access to any AUDIX system in the network. There is more information on switched connections in the next section.

When there are more systems and/or PCs than channels, contention for the channels may occur. This situation can usually be avoided, however, by scheduling the transfer of data at different times of the day. See Chapter 13, AUDIX System Administration for details on how to set up transmission schedules. Even when contention does occur, an AUDIX system will try to establish a connection two more times. If still unable to make the connection, the AUDIX system will try again at the next scheduled interval or when the transmission queue becomes full.

RS-232

Figure 2-1. Dedicated RS-232 Network of Two AUDIX Systems

_______________________________________________________________________________________

_______________________________________________________________________________________

Figure 2-2. Dedicated RS-232 Network of Two AUDIX Systems and a PC (Low Traf???c Only)

Figure 2-3. Dedicated RS-232 Network of Three AUDIX Systems (Low Traf???c Only)

3. Switched EIA RS-232 Networks

_______________________________________________________________________________________

_______________________________________________________________________________________

AUDIX networks can be implemented using a switched Electronic Industries Association (EIA) RS-232 connection. Networks can also be implemented by converting the RS-232 channels into switched Digital Communications Protocol (DCP) connections. This chapter presents supported con???gurations for both methods. The examples show an AUDIX system using RS-232 at both ends. See Chapter 7, Mixtures of RS-232 and DCP Networks, for RS-232/DCP combinations.

If your customer develops their own method, contact the Business Communications Systems Design Center (BCSDC) to make sure the method is feasible. Each of the examples presented here is accompanied by the equipment required for the AUDIX systems and for the switches the AUDIX systems serve.

CONSIDERATIONS

If a customer is considering using switched RS-232 connections in their AUDIX network, keep the following in mind:

???Local or remote networking con???gurations are supported.

???Two or more AUDIX systems can be networked via this method.

???AUDIX software must be R1V5 or later.

???The customer needs a TN539 or TN539B networking board.

???In this type of network speeds can be up to 19.2 Kbps; speeds are limited by the modems or data modules the customer chooses to use.

???The customer will need data modules or Hayes-compatible modems for each AUDIX channel to be switched.

3-1

3-4 Switched EIA RS-232 Networks

________________________________________________________________________________________________

________________________________________________________________________________________________

AUDIX System Requirements For Switched RS-232 Using Modems

Each AUDIX system must be running R1V5 or later software. Each AUDIX system must be equipped with a TN539 or TN539B ACCE circuit pack. The AUDIX Networking Breakout cable (H600-331, Group 2) is required at each AUDIX system.

MODEM

RS-232

T/R

H600-331

GROUP 2

AUDIX

MODEM

RS-232

Figure 3-2. Switched RS-232 Network for a Single Switch

Switch (or Customer) Requirements For Switched RS-232 Using

Modems

Each switched RS-232 channel requires one of the following Hayes??-compatible modems:

???AT&T 2296A

???AT&T Paradyne 3820

???AT&T Paradyne DM424

???MICROCOM QX 3296/C (not orderable through AT&T)

_______________________________________________________________________________________

_______________________________________________________________________________________

The modem requires a connection through one of the switch???s analog ports or can connect directly to a CO line. Switch analog port circuit packs are:

???System 75, Generic 1, and Generic 3: TN742 or TN746B analog line circuit

???System 85 and Generic 2 traditional module: SN222, SN228, or SN228B analog line circuit

???System 85 and Generic 2 universal module: TN742 or TN746B analog line circuit

TO ANALOG PORTS

RS-232

MODEM

RS-232

T/R

Figure 3-3. Switched RS-232 Network for Separate Locations

If the modems must be located greater than 5.0 feet (1.524 meters) from the AUDIX system, an M25A RS- 232 extender cable is required for each. The modem must be within 50 feet (15.24 meters) of the AUDIX system. The tip/ring circuit should be engineered by a switch representative.

_______________________________________________________________________________________

_______________________________________________________________________________________

SWITCHED RS-232 USING DATA MODULES FOR DCP

By using a data module instead of a modem, the RS-232 channel becomes a DCP channel, at least as far as the switch and the switch network is concerned. RS-232 channels can be converted to DCP mode 1, DCP mode 2, or DCP mode 3. See Figure 3-5, Converting RS-232 Channels to DCP.

???To convert to DCP mode 1 (56 Kbps) or DCP mode 3 (64 Kbps), use a Modular Processor Data Module, Model M1* (MPDM/M1*). In either of these cases, the channels can only be used for incoming calls; they cannot be used for outgoing calls. All outgoing calls must use the DCP ports.

???To convert to DCP mode 2, use a 7400A or 7400B Data Service Unit (DSU). In this case, the channels can be used for incoming or outgoing calls.

Converting RS-232 channels to DCP is particularly useful for System 75, Generic 1, Generic 3, and MERLIN II where a DCP network is desired. Adding the two converted channels to the regular two DCP channels creates a total of four DCP channels. (If the customer desires, these channels can be left as RS- 232 channels giving two RS-232 and two DCP channels, again for a total of four channels. See Chapter 7,

Mixtures of RS-232 and DCP Networks, for examples.)

Figure 3-5. Converting RS-232 Channels to DCP

4. DCP Mode 1 Networks ??? 56 Kbps

_______________________________________________________________________________________

_______________________________________________________________________________________

AUDIX networks can be implemented using AT&T???s Digital Communications Protocol (DCP) Mode 1. This type of network is only used when the AUDIX systems to be networked are not colocated and, therefore, they require some type of interlocation facility to pass data. (For local networking, see Chapter 6, DCP Mode 3 Networks ??? 64 Kbps.) This chapter presents supported 56 Kbps con???gurations; all other 56 Kbps con???gurations must be designed by Custom Development.

The examples show an AUDIX system using DCP at both ends. See Chapter 7, Mixtures of RS-232 and DCP Networks, for RS-232/DCP combinations. Each of the examples presented in this chapter is accompanied by the equipment required for the AUDIX systems and for the switches that the AUDIX systems serve.

CONSIDERATIONS

If a customer is considering using DCP Mode 1 connections in their AUDIX network, keep the following in mind:

???Only remote networking con???gurations are supported.

???Two or more AUDIX systems can be networked via this method.

???AUDIX software must be R1V5 or later. However, R1V7 software is recommended because of the networking feature enhancements and 56 Kbps loopback testing capabilities included in that load when a TN539B ACCE board is used.

???AUDIX systems running R1V5 or R1V6 software require an MPDM/M1* for loopback testing. AUDIX R1V7 systems only require an MPDM/M1* if the two RS-232 ports are to be converted for 56 Kbps use.

???The customer needs a TN539 or TN539B ACCE networking board; the TN539B is recommended because of the 56 Kbps loopback testing capabilities included in that load when AUDIX R1V7 software is used.

???Transmission in this type of network is full-duplex, synchronous, at 56 Kbps.

???The customer will need access to 56 Kbps robbed-bit facilities to a static or dynamic serving of???ce (SO).

???The customer will also need a DCP interface on the switch to connect with the AUDIX and a DS1 interface on the switch to connect with the 56 Kbps network.

4-1

4-2 DCP Mode 1 Networks ??? 56 Kbps

________________________________________________________________________________________________

________________________________________________________________________________________________

GENERAL INFORMATION

To use DCP Mode 1 as the transmission protocol, the switch must be set up to access a switched network at 56 Kbps via robbed-bit facilities. These special access lines can be either Dataphone Digital Service (DDS) or ACCUNET T1.5, SDN service providing access to either a static or dynamic Serving Of???ce (SO), or compatible services provided by other vendors. Currently the System 75, System 85, DEFINITY Generic 1, Generic 2, or Generic 3 can provide this type of access. However, System 85 (R2V3 or R2V4) does not support dynamic access. Up to six channels on the 56 Kbps service facility may be required at any one time for System 85 and Generic 2 and up to four channels for System 75, Generic 1, and Generic 3.

Figure 4-1, DCP Mode 1 Network Using Switched 56 Service, shows an arrangement where AUDIX networking is accomplished via 56 Kbps services. Figure 4-2, PC Added to A DCP Network, shows a network of R1V5 or later AUDIX systems with RS-232 access. When RS-232 is available, the customer has a choice of connecting a PC for the CDR feature via dedicated or switched RS-232 (dedicated RS-232 is shown in Figure 4-2).

_______________________________________________________________________________________

_______________________________________________________________________________________

RS-232

(NOT EQUIPPED)

Figure 4-1. DCP Mode 1 Network Using Switched 56 Service

4-4 DCP Mode 1 Networks ??? 56 Kbps

________________________________________________________________________________________________

________________________________________________________________________________________________

Static Access

Static SDDN (non-ISDN) allows customers currently subscribing to SDN voice applications to transmit data on the same access arrangement by designating a subgroup de???ned for data terminations. Customers using this con???guration must have a trunk subgroup (TSG) dedicated to SDDN 56 Kbps between the customer premises and a central of???ce. They must also have a System 75 R1V3 Issue 2.1 or later, a System 85 R2V3 or R2V4, or a DEFINITY Generic 1, Generic 2, or Generic 3 switch.

The central of???ce must provide one of the following:

???SDN, T1.5, or DDS and Switched Digital Service (SDS), or compatible service offered by another vendor

???A 4ESS supporting 56 Kbps service

A customer with T1.5 access to a central of???ce tariffed for SDN and T1.5 that does not home to a 4ESS with SDS cannot use this option.

Dynamic Access

Dynamic SDDN (non-ISDN) allows customers that currently subscribe to SDN voice applications to transmit data on the same access arrangement by pre???xing a 115 feature code in front of a telephone number. This allows customers to alternately transmit voice and data on one access line; a separate trunk group for 56 Kbps data is not required.

The T1.5 is dedicated to SDN and is therefore not exclusively 56 Kbps. The central of???ce must route to a 4ESS that supports 56 Kbps via digital connectivity. This access may only be offered on circuits without echo cancellation.

The dynamic arrangement is not possible from locations using DDS access. DDS lines must terminate in a central of???ce that has been tariffed for SDN, DDS, and SDS.

System 85 R2V3 and R2V4 do not support dynamic access. System 75 R1V3 and and DEFINITY Generic 1, Generic 2, and Generic 3 do support dynamic access. However, if a customer wants to use a Generic 2 for Switched 56 Kbps networking, contact the BCSDC for help.

_______________________________________________________________________________________

_______________________________________________________________________________________

AUDIX SYSTEM REQUIREMENTS FOR DCP MODE 1

Each AUDIX system requiring access to a switched 56 network must be running R1V5 or later software. Each AUDIX system must also be equipped with a TN539 or TN539B ACCE circuit pack, the AUDIX Networking Breakout cable (H600-331, Group 1 or Group 2). Also, if the RS-232 ports are to be used for DCP Mode 1 transmission, an MPDM/M1* with an RS-232 interface card is required. If loopback testing is to be conducted for an R1V5 or R1V6 AUDIX system, an MPDM/M1* with a V.35 interface card is required. In addition, each AUDIX system must be within 5000 cable feet (1525 meters) of the switch???s DCP interface.

AUDIX

RS-232

ACCESS

Figure 4-2. PC Added to a DCP Network

4-6 DCP Mode 1 Networks ??? 56 Kbps

________________________________________________________________________________________________

________________________________________________________________________________________________

SWITCH (OR CUSTOMER) REQUIREMENTS FOR DCP MODE 1

To implement AUDIX networking over static or dynamic switched 56 Kbps facilities, the customer???s switch must have a DCP interface to connect with the AUDIX system and a DS1 interface to connect with the 56 Kbps switched network.

Whether a customer is using static or dynamic 56 Kbps, the point-of-presence switch needs to be translated to match the switch, (including wink in/wink out). The RNXs are set up by the customer and added to the network by Network Systems.

Contact the Business Communications Systems Design Center (BCSDC) to design ISDN.

NOTE

The following equipment is typical for 56 Kbps facility access:

???Digital Line Circuits for the AUDIX network

???DS1 Interface

???For R1V5 or R1V6, a Modular Processor Data Module, Model M1* (MPDM/M1*) ACCUNET data module with V.35 interface card (for loopback testing)

Static Access Switch Requirements

The requirements for networking AUDIX systems via static 56 Kbps facilities depend on the customer???s premise switch:

???System 75

???The switch must be R1V3 2.1 or later.

???All tone detectors must be TN748C (V4 or later).

???DEFINITY Generic 1 and Generic 3

???Any release will support static 56 Kbps access.

???All tone detectors must be TN748C (V4 or later).

_______________________________________________________________________________________

_______________________________________________________________________________________

???System 85

???The switch must be R2V3 or R2V4

???All tone detectors must be at least an SN255.

???DEFINITY Generic 2

???Any release will support static 56 Kbps access.

???For universal modules, the detector must be a TN748C (V4 or later). For traditional modules, the detector is a SN255.

Dynamic Access Switch Requirements

The requirements for networking AUDIX systems via dynamic 56 Kbps facilities depend on the customer premise switch:

???System 75

???The switch must be R1V3 2.1 or later.

???All tone detectors must be TN748C (V4 or later).

???DEFINITY Generic 1 and Generic 3

???Any release will support dynamic 56 Kbps access.

???All tone detectors must be TN748C (V4 or later).

???System 85

???Does not support dynamic access.

???DEFINITY Generic 2

???Any release will support dynamic 56 Kbps access.

???For universal modules, the detector must be a TN748C (V4 or later). For traditional modules, the detector is a SN255.

For help in designing dynamic switched 56 Kbps networking with a Generic 2, contact the BCSDC.

DATA RATES FOR DCP MODE 1

All of the con???gurations shown in this chapter operate at 56 Kbps.

5. DCP Mode 2 Networks ??? Modem Pooling

_______________________________________________________________________________________

_______________________________________________________________________________________

AUDIX networks can be implemented using AT&T???s Digital Communications Protocol (DCP) Mode 2. This type of network is only used when the AUDIX systems to be networked are not colocated and, therefore, require some type of interlocation facility to pass data. This arrangement makes use of the switch???s modem pool or can be implemented using stand-alone modem pools. This chapter presents supported con???gurations. The examples show the AUDIX system using DCP at both ends. See Chapter 7,

Mixtures of RS-232 and DCP Networks, for RS-232/DCP combinations.

If a customer develops their own method, contact the Business Communications Systems Design Center (BCSDC) to make sure it is feasible. Each of the examples presented here is accompanied by the equipment required for the AUDIX systems and for the switches that the AUDIX systems serve.

CONSIDERATIONS

If a customer is considering using DCP Mode 2 connections in their AUDIX network, keep the following in mind:

???Only remote networking con???gurations are supported.

???Two or more AUDIX systems can be networked via this method.

???AUDIX software must be R1V3 or later.

???The customer needs a TN366, TN366B, TN539, or TN539B networking board.

???Transmission in this type of network is full-duplex or half-duplex, synchronous or asynchronous, at speeds up to 9600 bps.

???The customer will need rack-mounted or standalone modem pool.

5-1

5-2 DCP Mode 2 Networks ??? Modem Pooling

________________________________________________________________________________________________

________________________________________________________________________________________________

GENERAL INFORMATION

DCP Mode 2 networking uses the DCP interface between the AUDIX system and the switch. Analog or voice-grade data facilities are used between customer locations. When the switch is a System 85 or DEFINITY Generic 2, the AUDIX system can use up to six ports at any given time. When the switch is a System 75, Generic 1, or Generic 3, up to four ports may be used at any given time.

Figure 5-1, Typical Rack-Mounted Modem Pool Using D-Lead Control, shows a modem pool where a D- Lead is used between the modems and data modules. This arrangement is usually shared by two or more switch applications. The customer can use this arrangement for AUDIX systems so long as the equipment and their option settings are compatible. (Compatible equipment is provided later in this chapter. Compatible option settings are provided in Chapter 11, DCP Mode 2 Installation and Administration.) The customer could also use what is called stand-alone modem pooling. See Figure 5-2, Typical Stand-Alone Modem Pool (No D-Lead Control).

Figure 5-1. Typical Rack-Mounted Modem Pool Using D-Lead Control

_______________________________________________________________________________________

_______________________________________________________________________________________

Figure 5-2. Typical Stand-Alone Modem Pool (No D-Lead Control)

In Figure 5-2, the modems and data modules are typically the models that are contained in their own housings and placed on shelves or on top of other cabinets. However, they could be the rack-mounted versions where they are cabled as stand-alone modem pools (no D-Lead). Stand-alone modem pools are usually dedicated for a particular application.

Figure 5-3, DCP Mode 2 Network (Modem Pooling), shows a DCP Mode 2 network where the switches are either System 75, System 85, Generic 1, Generic 2, or Generic 3.

_______________________________________________________________________________________

_______________________________________________________________________________________

AUDIX SYSTEM REQUIREMENTS FOR DCP MODE 2

Each AUDIX system must be running R1V3 or later software and must be equipped with one of the following:

???TN366 AUDIX Communications Controller (ACC) circuit pack

???TN366B ACC circuit pack

???TN539 ACC Enhanced (ACCE) circuit pack

???TN539B ACCE circuit pack

The AUDIX Networking Breakout cable (H600-331, Group 1 or Group 2) provides access to the DCP channels at the AUDIX system. Also, each AUDIX system must be within 5000 cable feet (1525 meters) of the switch???s DCP interface.

SWITCH (OR CUSTOMER) REQUIREMENTS FOR DCP MODE 2

The switch must have a DCP interface and some type of modem pool to provide access to the analog or voice-grade-data interlocation facilities. For System 75, System 85, DEFINITY Generic 1, Generic 2, or Generic 3, the modem pool may be:

???Rack-mounted with a D-Lead

???Rack-mounted or shelf-mounted as a stand-alone modem pool (no D-Lead)

5-6 DCP Mode 2 Networks ??? Modem Pooling

________________________________________________________________________________________________

________________________________________________________________________________________________

Basic Switch Needs

The switch must have the following circuit packs to support modem pooling:

???System 75, Generic 1, Generic 2 (universal module), or Generic 3:

???TN748C Tone Detector (System 75 requires a vintage 1 or vintage 3 board; Generic 1 and Generic 3 require vintage 3) ??? required in all carriers of a System 75, but not all carriers of a Generic 1 or Generic 3. (Do not use the TN748B, TN748D vintage 1, or the TN756.) For System 75, Generic 1, and Generic 3, this board does not require assignment, but for Generic 2, it does (use channels 4 and 8).

???TN727 Network Controller (System 75) or TN777 Network Controller (Generic 1 and Generic 3) is required.

???MT 771B Maintenance Test Circuit (Generic 2 universal module; equivalent to the SN261).

???System 85 or Generic 2 (traditional module):

???SN253 Auxiliary Tone Plant (one in each module used)

???SN255B or SN255C Tone Detector

???SN261B or SN261C Analog/Digital Facility Test Circuit

DCP Interface for the AUDIX Network Channels

The following digital lines are required to terminate the AUDIX network channels at the switch:

???System 75, Generic 1, or Generic 3:

Two TN754 Digital Line ports are required for the AUDIX DCP channels. Two more ports are required if the AUDIX RS-232 channels are to be converted to DCP.

???Generic 2 (universal module):

Two TN754 Digital Line ports are required for the AUDIX DCP channels. Two more ports are required if the AUDIX RS-232 channels are to be converted to DCP.

???System 85 or Generic 2 (traditional module):

Two SN270B General Purpose Port (GPP) ports are required for the AUDIX DCP channels. Two more ports are required if the RS-232 channels are to be converted to DCP.

5-8 DCP Mode 2 Networks ??? Modem Pooling

________________________________________________________________________________________________

________________________________________________________________________________________________

Modems and Data Modules

The following modems can be used in a modem pool for AUDIX networking. One modem is required for each modem pool pair.

???AT&T 2296A (rack-mounted or stand-alone modem pool). If used in a stand-alone modem pool, an auto-dialer module is required.

???MICROCOM QX 3296/C (stand-alone modem pool).

???AT&T Paradyne 3820 (stand-alone modem pool).

???AT&T Paradyne DM424 (stand-alone modem pool).

The following data modules can be used in a modem pool used by AUDIX systems. One data module is required for each modem pool pair.

??? 7400A Data Service Unit (rack-mounted or stand-alone modem pool)

??? MTDM (rack-mounted modem pool)

In selecting modems or data modules for modem pooling, it is important to note that once a speci???c model is chosen for use on one end of the remote network, only certain models will work on the other end of the remote connection. Combinations that have been tested are listed in the following tables. Combinations that work are marked as ??????OK,?????? and those that do not work are marked ??????FAIL.??????

6. DCP Mode 3 Networks ??? 64 Kbps

_______________________________________________________________________________________

_______________________________________________________________________________________

AUDIX networks can be implemented using AT&T???s Digital Communications Protocol (DCP) Mode 3. This arrangement can be used when the AUDIX systems are colocated (serving the same switch) or when they are at separate customer sites. This chapter presents supported local and remote networking con???gurations. The examples show the AUDIX system using DCP at both ends. See Chapter 7, Mixtures of RS-232 and DCP Networks, for RS-232/DCP combinations.

If your customer develops their own method, contact the Business Communications Systems Design Center (BCSDC) to make certain it is feasible. Each of the examples presented here is accompanied by the equipment required for the AUDIX systems and for the switches that the AUDIX systems serve.

CONSIDERATIONS

If a customer is considering using DCP Mode 3 connections in their AUDIX network, keep the following in mind:

???Local or remote networking con???gurations are supported.

???Two or more AUDIX systems can be networked via this method.

???AUDIX software must be R1V3 or later. For remote con???gurations, R1V7 software is recommended because of the 64 Kbps loopback testing capabilities included in that load.

???The customer needs a TN366, TN366B, TN539, or TN539B networking board. For remote con???gurations, the TN539B is recommended because of the 64 Kbps loopback testing capabilities included in that board.

???Transmission in this type of network is full-duplex, synchronous, at 64 Kbps.

???For remote con???gurations, the customer will need access to 64 Kbps public or private telephone network facilities; these should normally be a T1 carrier with DS1 services.

6-1

_______________________________________________________________________________________

_______________________________________________________________________________________

Figure 6-1. DCP Mode 3 Network for a Single Switch

6-4 DCP Mode 3 Networks ??? 64 Kbps

________________________________________________________________________________________________

________________________________________________________________________________________________

Figure 6-2. DCP Mode 3 Network for a Non-DCP Switch

SWITCH (OR CUSTOMER) REQUIREMENTS FOR DCP MODE 3

Switch requirements depend on whether the systems are serving the same switch or are serving different switches.

Colocated Requirements

One of the following switches must be used and equipped with a DCP interface for termination of the AUDIX DCP channels:

???System 75, Generic 1, Generic 2 (universal module), or Generic 3:

Two TN754 Digital Line ports are required per AUDIX system. Although not required, it is recommended that the circuits be on separate packs so all four network channels will not be lost in the event a single pack goes bad.

_______________________________________________________________________________________

_______________________________________________________________________________________

???System 85 or Generic 2 (traditional module):

Two SN270B General Purpose Ports are required per AUDIX system. Although not required, it is recommended that the ports be on separate packs. Then not all four network channels will be lost in the event a single pack goes bad.

???MERLIN II (for colocated systems only)

Two ports on an 008D Digital Line card; the MERLIN II must be equipped as speci???ed earlier in this chapter in AUDIX System Requirements for DCP Mode 3.

When the AUDIX RS-232 channels are converted to DCP, two more ports are required.

Interlocation Requirements

In addition to the requirements listed in the previous paragraphs, a T1 Carrier (DS1 Interface set for Alternate Voice/Data) or the B-channels of an Integrated Systems Digital Network (ISDN) span must be provided for networking between locations.

The BCSDC will design networks using ISDN.

NOTE

The switch must have the following circuit packs:

???System 75, Generic 1, Generic 2 (universal module), or Generic 3:

???TN748C Tone Detector (System 75 requires a vintage 1 or vintage 3 board; Generic 1 and Generic 3 require vintage 3) ??? required in all carriers of a System 75, but not all carriers of a Generic 1 or Generic 3. (Do not use the TN748B, TN748D vintage 1, or the TN756.) For System 75, Generic 1, and Generic 3, this board does not require assignment, but for Generic 2, it does (use channels 4 and 8).

???TN727 Network Controller (System 75) or TN777 Network Controller (Generic 1 and Generic 3) is required.

???MT 771B Maintenance Test Circuit (Generic 2 universal module; equivalent to the SN261).

???System 85 or Generic 2 (traditional module):

???SN253 Auxiliary Tone Plant (one in each module used)

???SN255B or SN255C Tone Detector

???SN261B or SN261C Analog/Digital Facility Test Circuit

6-6 DCP Mode 3 Networks ??? 64 Kbps

________________________________________________________________________________________________

________________________________________________________________________________________________

AUDIX systems could use up to six channels at any one time. Figure 6-3, DCP Mode 3 Network for Multiple Locations, shows the DS1 arrangement. For requirements on the switch for DS1, refer to the latest issue of DEFINITY Communications System & System 75/85 DS1/DMI/ISDN-PRI Reference (585-025- 101). If the customer has a non-DCP switch and wishes to use DCP Mode 3 for interlocation communication, see DCP Mode 3 Network For a 5ESS Switch later in this chapter.

DATA RATES FOR DCP MODE 3

This arrangement operates at speeds of 64 Kbps.

Figure 6-3. DCP Mode 3 Network for Multiple Locations

_______________________________________________________________________________________

_______________________________________________________________________________________

DCP MODE 3 FOR A 5ESS SWITCH

Figure 6-4, DCP Mode 3 Network for a 5ESS Switch, shows how a Generic 2 provides the DCP and DS1 interfaces for a 5ESS Centrex switch (an example of a non-DCP switch). The customer has installed the AUDIX system to serve their employees which reside on the Centrex. A ??????bare-bones?????? Generic 2 is installed for its DCP, DS1, modem pooling, and alternate routing capabilities only. No stations reside on the Generic 2. The Generic 2 does the following:

???Provides a 64 Kbps digital network path between the two AUDIX systems shown.

???Provides a 64 Kbps digital network path to an AUDIX system located outside the 5ESS environment.

???Generic 2 software (R2V5) provides the ability to designate the digital path as the ???rst-choice facility with the analog path providing backup (see the Automatic Alternate Routing feature).

MODEM

POOL

Figure 6-4. DCP Mode 3 Network for a 5ESS Switch

7. Mixtures of RS-232 and DCP Networks

_______________________________________________________________________________________

_______________________________________________________________________________________

This chapter presents supported con???gurations using RS-232 and DCP connections on the same AUDIX system. If your customer develops their own method, contact the Business Communications Systems Design Center (BCSDC) to make certain it is feasible. Look to the previous chapters for the requirements of the following networks.

CONSIDERATIONS

An AUDIX network can be implemented using both RS-232 connections and Digital Communications Protocol (DCP) connections. A single AUDIX system can use both types, or an RS-232 connection can be used at one AUDIX system to talk to another AUDIX system that uses DCP connections.

RS-232 AND DCP AT THE SAME AUDIX SYSTEM

Figure 7-1, RS-232 and DCP at the Same AUDIX, shows how the two AUDIX RS-232 channels and the four AUDIX DCP channels are used on the same AUDIX system. This is particularly useful for a System 75, System 75 XE, Generic 1, Generic 3, or MERLIN II, where only two of the four AUDIX DCP channels can be accessed. In this example, the RS-232 channels are used for communication between the two colocated systems at the top of the ???gure. The DCP channels are used for these systems to communicate with the off-site system at the bottom of the ???gure. In a larger network, where several AUDIX systems to be networked are off-site, it might be advantageous to make the RS-232 channels switched connections as in Figure 7-2, High-Speed Switched RS-232 and DCP AUDIX Connections. This provides a greater degree of access to these systems.

Figure 7-3 shows the DCP channels of the colocated AUDIX systems being used for communication with an off-site AUDIX system. One of the RS-232 channels is used for communication between the colocated systems and the other is used to connect to a PC. The PC could be used to run the Call Detail Recording software package.

7-1

7-2 Mixtures of RS-232 and DCP Networks

________________________________________________________________________________________________

________________________________________________________________________________________________

RS-232 AND DCP AT SEPARATE LOCATIONS

Figure 7-4 shows a case where one of the customer???s AUDIX systems is tied to a DCP switch and the other tied to a non-DCP switch. The system located with the non-DCP switch is brand new, running R1V5 or later software and equipped with a TN539 or TN539B for RS-232 access. The other system is running R1V4 software and equipped with a TN366B (no RS-232 access). Since the DCP switch is equipped with modem pooling, the modem pools are used to convert DCP into analog (t/r) for transmission to the other AUDIX system. If the DCP switch did not have modem pooling, the customer should upgrade to R1V5 or later software.

Figure 7-1. RS-232 and DCP at the Same AUDIX

_______________________________________________________________________________________

_______________________________________________________________________________________

Public/Private

Interlocation

Facilities

Figure 7-2. High-Speed Switched RS-232 and DCP AUDIX Connections

8. EIA RS-232 Cabling

_______________________________________________________________________________________

_______________________________________________________________________________________

This chapter shows how to cable the AUDIX RS-232 ports to another AUDIX system using direct cabling or by cabling through the switch. These ports can be converted to Digital Communications Protocol (DCP) ports before entering the switch, if desired. This is attractive to System 75, DEFINITY Generic 1, Generic 3, and MERLIN II installations using DCP for interlocation communications since these switches can only access two of the four DCP ports.

DEDICATED RS-232 CABLING

Figure 8-1, Dedicated RS-232 Connection (Within 10 Feet), shows how to cable a dedicated RS-232 AUDIX connection when the AUDIX systems are within 10 cable feet. Figure 8-2, Dedicated RS-232 Connection (Within 50 Feet), shows that an RS-232 extender cable is used when the distance between systems is greater than 10 cable feet apart, but less than 50 feet. Figure 8-3, Dedicated RS-232 Connection (Using Z3A ADUs) shows how to install and wire a dedicated connection that requires data sets to extend the distance capability beyond 50 feet.

Within 50 feet (15.25 meters), the data rate may be up to and including 19.2 Kbps. Within 20 feet (6.1 meters), the data rate may be up to and including 64 Kbps. When data sets are used, check the documentation provided with the data sets for supported data rates.

8-1

8-4 EIA RS-232 Cabling

________________________________________________________________________________________________

________________________________________________________________________________________________

GREATER THAN 50 FT (15.25 M)

Figure 8-3. Dedicated RS-232 Connection (using Z3A ADUs)

SWITCHED RS-232 CABLING

Figure 8-4, Switched RS-232 to an Analog Switch Port, shows how a modem is used to interface the AUDIX system to a DCP or non-DCP switch. Figure 8-5, Switched RS-232 to a DCP Switch Port, shows how a data set is used to interface the AUDIX system to a DCP switch. Option settings for the modems and data modules are given after the ???gures.

Figure 8-4. Switched RS-232 to an Analog Switch Port

Figure 8-5. Switched RS-232 to a DCP Switch Port

8-8 EIA RS-232 Cabling

________________________________________________________________________________________________

________________________________________________________________________________________________

RS-232 to DCP Conversion

This type of connection is shown for a DCP switch in Figure 8-5, Switched RS-232 to a DCP Switch Port.

???To convert an RS-232 channel to DCP mode 2, use a 7400A or 7400B Data Service Unit (DSU). In this case, the channels can be used to originate and receive calls at speeds up to and including 19.2 Kbps.

An initialization string for the 7400A or 7400B will have to be entered on the AUDIX system : translation : network port form.

???If a 7400A is used, make sure it is optioned for Data Communications Equipment (DCE). Lift off the cover and check the vertical card at the front. If it reads DCE, the 7400A is okay. If not, remove the card, turn it around, and reinstall it. If a 7400B is used, it does not require this step. It is always optioned for DCE.

To set up the 7400A, go to the front panel and press the next/no button until the set interface options comes up. Then press the yes button and choose INT=AT COMM.

???For a 7400B, set switch 1 to ON if there is no telephone connected to the data module. To get to switch 1, lift the cover off the modem.

???To convert an RS-232 channel to DCP mode 1 (56 Kbps) or DCP mode 3 (64 Kbps), use a Modular Processor Data Module, Model M1* (MPDM/M1*). In either of these cases, the channels can only be used for incoming calls; they cannot be used for outgoing calls. All outgoing calls must use the DCP ports. Make sure the MPDM/M1* has the option settings shown in the following table.

_______________________________________________________________________________________

_______________________________________________________________________________________

Table 8-1. MPDM/M1* Option Settings

SWITCH ADMINISTRATION

The only administration required at the switch is the translation of the new analog or DCP ports for communication with the appropriate endpoints. For analog port translations, see the appropriate switch documentation. For DCP port translations, see Chapter 9, DCP Cabling and Administration.

9. DCP Cabling and Administration

_______________________________________________________________________________________

_______________________________________________________________________________________

This chapter provides explanations and illustrations for the cabling, translation, and use of the AUDIX networking channels for supported host switches. If you are setting up a connection requiring interlocation facilities, use this chapter to set up the Digital Communications Protocol (DCP) channels from the AUDIX system to the switch, then go to Chapter 10, DCP Mode 1 Installation and Administration, Chapter 11,

DCP Mode 2 Installation and Administration, or Chapter 12, DCP Mode 3 Installation and Administration to set up the interlocation facilities.

ACC(E) WIRING TO THE SWITCH

For a System 75, System 85, DEFINITY Generic 1, Generic 2, or Generic 3, the DCP circuits at the switch are normally wired to the cross-connect ???eld using 25-pair cable. If you are connecting the AUDIX system to a MERLIN II, D8W-87 modular cord is always used (that is, the cross-connect ???eld is not required).

System 75, System 85, and DEFINITY Communications Systems

For the System 75, System 85, and DEFINITY Generic 1, Generic 2, or Generic 3, the AUDIX DCP ports must be wired to the switch through the cross-connect ???eld. Figure 9-1, DCP Cabling to the Switch Using the H600-331, Group 2 Cable, shows how this is done.

9-1

_______________________________________________________________________________________

_______________________________________________________________________________________

SWITCH ADMINISTRATION

The BCSDC will design hunt groups for AUDIX networking so the customer does not need to do so. Always use the extension numbers and hunt sequences provided by the BCSDC for AUDIX networking administration.

The AUDIX networking port administration covered in this section is used in all AUDIX networking setups. The following switch administration is required:

???At the System 75, Generic 1, and Generic 3, you will be assigning two channels. These switches use only I-channel 1 of each DCP circuit. At the AUDIX system, they appear as Channels 1 and 3. Channels 2 and 4 are not currently used.

???System 85 and Generic 2 use both I-channels of each circuit, so you will be assigning four channels. At the AUDIX system, they appear as Channels 1 through 4.

???The MERLIN II does not require administration for AUDIX DCP channels. The jacks used on the 008D module have ???xed dialing codes. At the AUDIX system, the MERLIN II connections appear only as Channels 2 and 4 (only I-channel 2 is used with each DCP circuit). Channels 1 and 3 are not used.

System 75, Generic 1, and Generic 3 Administration

Use the following procedure to assign the AUDIX DCP channels (terminated at two DCP circuits).

1.Use ??????add data-module xxxxx?????? to assign a DCP port where xxxxx is a 1- to 5-digit unused extension.

2.Set Type to pdm.

3.Set Port to the location of the TN754 circuit that is wired to the AUDIX DCP port (cable H600-331, Group 1; connector 1, 2, A, or B).

4.Press ENTER .

5.Repeat steps 1 through 4 for each DCP port used.

6.Use ??????add hunt-group next?????? to assign a hunt group.

9-6 DCP Cabling and Administration

________________________________________________________________________________________________

________________________________________________________________________________________________

Use the hunt groups the BCSDC has designed for AUDIX networking.

NOTE

7.Set Group Extension to another unused extension. Use a DID extension if the AUDIX system is to be accessed from a remote AUDIX system.

8.Set Group Type to ucd.

9.Set Message Center to none.

10.Set ACD to n.

11.Press ENTER .

12.Go to Page 2 and assign the DCP extensions to this hunt group. If you are converting the AUDIX RS-232 ports to DCP, you will have four networking extensions.

System 85 Administration

System 85 can use both I-channels of the DCP port. This provides access to all four AUDIX DCP networking ports. The DCP circuits are assigned as follows using the Maintenance and Administration Panel (MAAP).

1.Assign a class of service (cos) for the AUDIX networking ports that has touch-tone dialing and data protection ??? permanent enabled (use Proc 010, Word 1 and Proc 010, Word 3).

* Fields 2 through 10 may be assigned for toll fraud protection.

$ For remote networking con???gurations, if the AUDIX networking extension is dialing AAR or ARS to reach a remote AUDIX system, make sure an appropriate FRL is assigned to the AUDIX networking extensions??? cos (Proc 010, Word 3, Field 23).

_______________________________________________________________________________________

_______________________________________________________________________________________

2.Assign all four extensions (or six if you are converting RS-232 ports to DCP) to Bearer Capability Class-Of-Service (BCCOS) 6 as shown in Figure 9-5, Manager II Administration of a DCP Port (Proc 000, Word 3). The extension number shown is only an example.

5.Bearer Capability Class of Service: 6

6.Universal Code Calling ID: ---

Figure 9-5. Manager II Administration of DCP Port (Proc 000, Word 3)

10. DCP Mode 1 Installation and Administration

_______________________________________________________________________________________

_______________________________________________________________________________________

In most cases where the customer wishes to use this type of network, it will be because the network connections are already in place. T1 facilities connect the Private Branch Exchange (PBX) to a network point-of-presence switch which in turn is connected to the 56 Kbps facilities. Additional trunk circuits may have to be added to handle the additional traf???c. The Business Communications Systems Design Center (BCSDC) must make this determination.

SWITCH COMPONENT INSTALLATION

See the appropriate switch and/or feature documentation for installing circuit packs and wiring trunks on the switch.

SWITCH ADMINISTRATION

Check to make certain the customer???s switch and the central of???ce switch are compatible. For DCP Mode 1 networking, the trunk group used to transport the AUDIX calls must be DS1 and the DS1 pipe must employ robbed-bit signaling.

4ESS Administration

If not already done, the 4ESS must be translated for 56 Kbps operation as follows:

???The 4ESS facilities must be translated for robbed-bit transmission.

???If the 4ESS is using AMI, the System 75, System 85, or DEFINITY Communications System must be translated for ZCS (not B8ZS).

???The trunk types on the 4ESS and switch must match (for example, both may be translated as wink/wink type trunks).

10-1

10-2 DCP Mode 1 Installation and Administration

________________________________________________________________________________________________

________________________________________________________________________________________________

System 75, Generic 1, and Generic 3 Administration

Administration depends on whether the customer is using static (high-speed data only) or dynamic (voice and high-speed data) switched 56 access.

???Static Access: For static (high-speed data only) 56 Kbps switched access, the switch must be administered as follows:

???Using the add trunk-group form, set the comm type to DATA and administer the switch for wink in/wink out.

???Using the change system-parameters features form, set the off-premise tone detect to 25.

???Using the change ds1 circuit pack form, set the signaling mode ???eld to robbed-bit and set either ZCS or B8ZS to match the CO.

???Dynamic Access: For dynamic (voice and high-speed data) 56 Kbps switched access, the switch must be administered as follows:

???Using the add trunk-group form, set the comm type to RBAVD, the baud rate (or bit rate) to 19.2, and administer the switch so it matches the central of???ce trunk type.

???Using the change system-parameters features form, set the off-premise tone detect to 25.

???Using the change ds1 circuit pack form, set the signaling mode ???eld to robbed-bit and set either ZCS or B8ZS to match the CO.

10-4 DCP Mode 1 Installation and Administration

________________________________________________________________________________________________

________________________________________________________________________________________________

Generic 2 Administration

The following Manager II translations need to be completed for a Generic 2 for static switched 56 Kbps networking. For Generic 2 translations using dynamic 56 Kbps networking, contact the BCSDC.

1.Using Procedure 100, Word 1, make the assignments shown in Fields 1 through 9. The trunk group (76) and the dial access code/trunk ID code shown are only examples; enter the appropriate values supplied by the BCSDC.

To administer members of the trunk group, use Procedure 116.

NOTE

If you need to change the signaling type, use Procedure 100, Word 3.

ENHANCED MODE - PROCEDURE: 100, WORD: 1

TRUNK GROUP TRANSLATION

1. Trunk Group: 76

DIAL ACCESS CODE/TRUNK ID CODE

2.Digit 1: 7

3.Digit 2: 5

4.Digit 3: 1

5.Digit 4: -

6.Trunk Type: 41

7.Dial Access Restriction: 0 Access is allowed using DAC

8.Personal CO Line Appearance: 0 Not used for CO line appearance

9.Public Network Access/Egress: 1 Enabled

Figure 10-1. Manager II Mode 1 Administration (Proc 100, Word 1)

_______________________________________________________________________________________

_______________________________________________________________________________________

2.Using Procedure 100, Word 2, assign BCCOS 7 to the trunk group (trunk group 76 is only an example).

ENHANCED MODE - PROCEDURE: 100, WORD: 2

TRUNK GROUPS - MODEM POOLING AND BCCOS

MODEM POOLING

3.Originate Mode: _

4.Answer Mode: _

5.Modem Type: _

6.First Choice: _

7.Test Type: _

Figure 10-2. Manager II Mode 1 Administration (Proc 100, Word 2)

_______________________________________________________________________________________

_______________________________________________________________________________________

LOOPBACK TESTING

AT&T Network Systems requires loopback capabilities in order to test and support AUDIX networking over switched digital services (SDS). With R1V7 software and a TN539B ACCE, this test can be enabled via the maintenance : network form. On R1V5 and R1V6 systems, an MPDM/M1* is required for loopback testing.

Loopback Testing for R1V7

On AUDIX R1V7 systems, you can test the connection between the local AUDIX system and the 56 Kbps serving of???ce (SO), as shown in Figure 10-4, 56 Kbps Network Loop-Around Test. Normally only the four DCP ports are tested, but if you have an MPDM/M1* connected to ports 5 and 6, they may also be tested using the AUDIX maintenance : network form.

While a channel is in loopback mode, it will be unavailable to send information to remote systems or receive information from remote systems. Incoming calls will be answered, but the calling system will be unable to establish a connection; eventually it will drop the call and attempt to call back at its next scheduled transmission time.

Also, if you put a channel in loopback mode, any active calls will be dropped. It is therefore recommended that before you perform this test you check the status of the channel. It is also not a good idea to perform this test during peak traf???c times.

1. Go to the maintenance : network form. Set select test to 7 to test a 56 Kbps network

2.Have the serving of???ce place a call to the telephone number assigned to the channel you speci???ed on the maintenance : network form. If the test is successful, any data the serving of???ce sends over the AUDIX channel will be echoed back.

3.Go to the maintenance : network form. Set select test to 9 to take the channel out of

10-8 DCP Mode 1 Installation and Administration

________________________________________________________________________________________________

________________________________________________________________________________________________

MAINTENANCE: NETWORK FORM:

NETWORK LOOPAROUND START 56/64 Kbps

Figure 10-4. 56 Kbps Network Loop-Around Test

Loopback Testing for R1V5 and R1V6

For R1V5 and R1V6, loopback capabilities are provided by an MPDM/M1*.

Setting Up the MPDM/M1*

To install the MPDM/M1*, complete the following steps:

1.If the customer did not order an MPDM/M1*, modify the MPDM to support 56 Kbps by completing the following steps.

_______________________________________________________________________________________

_______________________________________________________________________________________

a.Install the 56 Kbps D-181509 kit by following the instructions included with the kit. The D-kit is used to modify the MPDM so it will work with 56 Kbps facilities.

b.Install the V.35 DTR card in the MPDM. The V.35 card allows a call to be answered without an attached DTE device.

To see if the V.35 card has already been installed, power up the MTDM without having a DTE attached. The Terminal Ready LED on the MPDM will be on if the V.35 DTR interface has previously been installed.

c.Solder two loops or build and connect a male loopback plug to make the connections shown in Figure 10-5, V.35 Male Connector.

V.35 MALE CONNECTOR

P (Tx1)

R (Rx1)

S (Tx2)

T (Rx2)

Figure 10-5. V.35 Male Connector

2.Install the MPDM/M1* by following the instructions that come with the data module.

3.Set all MPDM option switches to OFF (left) except the following:

???Set OFF/56K to 56K

???Set ASYNCH/SYNC to SYNC

???Set EXT/INT to INT

???Set OFF/ANET to ANET

???Set OFF/AANS to AANS

10-10 DCP Mode 1 Installation and Administration

________________________________________________________________________________________________

________________________________________________________________________________________________

Performing Loopback Test

AT&T Network Systems requires loopback capabilities in order to test and support AUDIX networking over switched digital services (SDS).

In order to conduct a loopback test, you must have installed the loopback MPDM/M1*. One MPDM/M1* is required per customer location, not per AUDIX system. (The MPDM/M1* must have the V.35 interface described earlier in this chapter.) You will also need to disconnect the AUDIX Networking Breakout Cable (H600-331, Group 2) from the AUDIX system for the duration of the test, so the system will have no networking capabilities during the test. See Figure 10-6, Loopback Test with the H600-331, Group 2 Cable. (If you are using the H600-331, Group 1 cable, you will only need to use one of the DCP lines. See Figure 10-7, Loopback Test with the H600-331, Group 1 Cable.)

When a loopback test is to be conducted, complete the following steps:

1.Busy out the AUDIX networking ports as follows:

a.If the RS-232 ports are converted to DCP using an MPDM/M1*, set the SELFTEST/NORMAL switch on the MPDM to SELFTEST.

b.Use the maintenance : network form to busy out all of the AUDIX networking ports.

2.Connect the loopback MPDM/M1* (with the V.35 interface card) as follows:

???If you are using the H600-331, Group 2 Cable, do one of the following:

???If a 356A adapter is available (see Figure 10-6, Loopback Test with the H600-331, Group 2 Cable), disconnect the Amphenol 50-pin male connector from the ACC D05 port on the AUDIX system. Connect the Amphenol connector to the 25-pair male connector 356A adapter using a 50-pin female-to-female Amphenol adapter. Plug one end of the D8W-87 cord into slot 1 of the 356A adapter, and the other end into the MPDM/M1* data module. This makes DCP channels 1 and 2 available for the loopback test.

???If a 356A adapter is not available, patch a 103A adapter to the DCP interface for the ???rst physical port (ELL) at the cross-connect ???eld. Plug one end of the D8W-87 cord into the 103A adapter, and the other end into the MPDM/M1* data module. This makes DCP channels 1 and 2 available for the loopback test.

???If you are using the H600-331, Group 1 Cable, borrow one of the AUDIX DCP ports as shown in Figure 10-7, Loopback Test with the H600-331, Group 1 Cable.

3.Put the loopback MPDM/M1* (with the V.35 interface) into normal mode.

4.Have Network Systems conduct the loopback test on the port connected to the loopback MPDM/M1*. Once the MPDM/M1* answers the call, put it into remote loopback mode.

5.When the test is completed, have Network Systems disconnect the call or press the ORIGINATE/DISCONNECT switch on the loopback MPDM.

6.Connect the network breakout cable (H600-331, Group 1 or Group 2) back to the AUDIX system as before the test.

11. DCP Mode 2 Installation and Administration

_______________________________________________________________________________________

_______________________________________________________________________________________

This chapter explains how to install and translate stand-alone modem pools and rack-mounted (D-Lead) modem pools. Once the modem pools are installed and translated, any problems should be directed to the Technical Service Center (TSC).

INSTALLING A 2296A AND MTDM IN A MODEM POOL

The following shows how to install and administer 2296A modems and MTDM data modules in their multi-mount con???guration. This arrangement uses a standard 72-inch cabinet with multiple mounts.

Do not apply power to the cabinet or any related equipment until all components are installed and ready for service.

WARNING

Install the Modem Pool Cabinet

The modem pool cabinet requires a 57 to 63 Hz, 105 to 129 VAC circuit. Expect to draw a maximum of 1200 watts. (This circuit should come from the same AC Distribution panel that powers the AUDIX, and power should not be controlled by the switch. The circuit should not share power with room lighting or other electrical devices that could cause electrical interference.)

A power strip should be installed at the back of the cabinet along the bottom left-hand side. The vertical side rails on the left and right sides of the cabinet go in the ???fth hole from the front. The equipment mounting ???anges on the rails face the front.

Install the Multiple Mountings

Each mounting plugs into the cabinet power strip and will draw 52 watts of power. The mountings operate in an ambient temperature range of 40 to 120 degrees F (4.44 to 48.8 degrees C) and a relative humidity range of 5 to 95 percent, noncondensing. The altitude limit is 10,000 feet above sea level.

Figure 11-1, 72-Inch Data Cabinet and Multiple Mountings, shows how the mountings are to be installed. The 105A mounting can be modi???ed to ???t in a 19- or 23-inch space by changing bracket positions.

11-1

11-2 DCP Mode 2 Installation and Administration

________________________________________________________________________________________________

________________________________________________________________________________________________

Test-???t an empty mounting between the rails and determine which holes in the rails will be used. Leave 1/2 inch between mountings. Start a screw in each of these holes, leaving 1/4-inch gap between the screw-head and rail. Install the mounting using the screws as hooks to hold it in place. Start a screw at the top of each side of the mounting and tighten. Tighten the bottom screws.

Figure 11-1. 72-Inch Data Cabinet and Multiple Mountings

Install the Modems and Data Sets

Each modem and data set plugs into the mounting and will draw 30 watts of power. The modems and data sets also operate in an ambient temperature range of 40 to 120 degrees F (4.44 to 48.8 degrees C) and a relative humidity range of 5 to 95 percent, noncondensing. The altitude limit is 10,000 feet above sea level.

_______________________________________________________________________________________

_______________________________________________________________________________________

Figure 11-2, Modem Pooling Cabinet with MTDMs (Front View), shows the front of a 105A and a 46A2 mounting. The shared Liquid Crystal Display (LCD) front panel of the 105A is for setting options inside each modem. The MTDMs require a 46A2 mounting (shown in Figure 11-2). The 7400A data sets require a 77A mounting (shown in Figure 11-5 Installation procedures for the 7400A are given in the 7400A DSU Installation and Settings (D-Lead Control) section later in this chapter.

Figure 11-2. Modem Pooling Cabinet with MTDMs (Front View)

11-4 DCP Mode 2 Installation and Administration

________________________________________________________________________________________________

________________________________________________________________________________________________

Use the following steps to install the modems and data sets.

1.Before installing a 2296A modem, check the feature package module located in the right-hand slot (modem standing on end). This should be a 140C1 (V1.1 or V1.2 no longer purchasable), 140F (V1.1), or 140F2 (V1.0) Memory Module.

The Automatic Calling Unit (ACU) and AUTOCALL modules are not required and should be removed if present. The Microcom Networking Protocol (MNP) module is only required if the data rate is 19.2 Kbps. In most AUDIX modem-pooling setups, the data rate is 9600 bps.

2.Install the 2296A modems in 105A slots. Start at the left. The modems must contact their backplane connector. Set the following options located at the top of the 2296A faceplate under the sliding panel:

The LCD display will be used to set internal options once power is applied.

3.Before installing the MTDMs, verify that they contain the new processor and TRIC 4 chips (see Figure 11-3, MTDM Location of TRIC 4 Chips). If not, they must be upgraded before they can be used. See Chapter 5, DCP Mode 2 Networks ??? Modem Pooling, for upgrades.

4.Set the following options on the MTDM circuit card:

5.Install the MTDM data sets in 46A2 slots. Start at the left. Each MTDM is paired with a modem. The MTDMs must make contact with the backplane connector.

_______________________________________________________________________________________

_______________________________________________________________________________________

VERIFY THAT THE DAUGHTER

BOARD USES TRIC 4 CHIPS (CODED 229EJ)

JUMPER NO. 9 PLACED IN NEW

POSITION AS SHOWN (SEE IC3

EXPLODED VIEW BELOW)

IC4 FROM

D181470

Figure 11-3. MTDM Location of TRIC 4 Chips

6.Set the following options on the face of the MTDM. The arrows (< for left, > for right) indicate which direction the rockers should be set. The speed shown is 9600 bps.

_________________________________________

11-6 DCP Mode 2 Installation and Administration

________________________________________________________________________________________________

________________________________________________________________________________________________

Install the Multi-Mount Cables

Figure 11-4, Modem Pooling Cabinet Cabling, shows the rear view of the modem-pool cabinet. Cables should be installed as shown. For details, see the following procedures:

1.Connect the D Lead Control cable (RS-232C to 25-pair) from the DATA MODE CONTROL connector on the 105A to the MODEM CONTROL connector on the 46A2.

2.Connect one end of a 25-pair cable to the RJ21X PERMISSIVE connector on the 105A.

3.Connect the other end of this cable to the switch cross-connect ???eld. Use the following table to patch a tip and ring pair to a switch analog port.

Record the telephone number of each modem on the space above the display panel.

_______________________________________________________________________________________

_______________________________________________________________________________________

ONE OF 8

NOTE: This ???gure shows the MTDM rack on top.

Figure 11-2 shows it on bottom.

Figure 11-4. Modem Pooling Cabinet Cabling

11-14 DCP Mode 2 Installation and Administration

________________________________________________________________________________________________

________________________________________________________________________________________________

INSTALLING STAND-ALONE MODEM POOLS

Stand-alone modem pools can be used with System 75, System 85, Generic 1, Generic 2, and Generic 3. Although cabled as a stand-alone modem pool, the modems and data sets can still be mounted in racks if you have spare rack-type units that must be utilized.

System 75/85, System 75 XE, Generic 1, Generic 2, and Generic 3

If the AUDIX is equipped with the TN366B, TN539, or TN539B stand-alone modems and data sets can be used instead of the equipment associated with a switch???s modem pool (that is, data cabinet, mountings, and D-Lead control). Use one of the following modems along with a 7400A DSU:

???AT&T Paradyne 3820 modem

???AT&T Paradyne DM424 modem

???AT&T 2296A modem

Figure 11-7, Analog Network Using Stand-Alone Modems and Data Sets, shows how the modem and data set are cabled. Check the modem and data set options before installing them. Options are given on the following pages. The 7400A requires power from a rack-mount or from a separate unit.

104A

MODEM

M25B RS-232 (M/M)

Figure 11-7. Analog Network Using Stand-Alone Modems and Data Sets

11-20 DCP Mode 2 Installation and Administration

________________________________________________________________________________________________

________________________________________________________________________________________________

ADMINISTERING THE SWITCH FOR MODEM POOLING

This section describes switch administration for a System 75, System 85, or DEFINITY Generic 1, Generic 2, or Generic 3.

If you are adding modem pool members, ???ll in the following before starting. For System 75, System 75 XE, Generic 1, Generic 2 (universal module), and Generic 3, locate the TN circuit packs shown below. For System 85 and Generic 2 (traditional module), locate the SN packs:

???TN754 or SN270B connected to MTDM-1 ____________________ (equipment location)

???TN754 or SN270B connected to MTDM-2 ____________________ (equipment location)

???TN754 or SN270B connected to MTDM-3 ____________________ (equipment location)

???TN754 or SN270B connected to MTDM-4 ____________________ (equipment location)

???TN742/TN746B or SN243B connected to 2296A-1 ____________________ (equipment location)

???TN742/TN746B or SN243B connected to 2296A-2 ____________________ (equipment location)

???TN742/TN746B or SN243B connected to 2296A-3 ____________________ (equipment location)

???TN742/TN746B or SN243B connected to 2296A-4 ____________________ (equipment location)

System 75, Generic 1, and Generic 3 Administration

Use the following steps to administer the switch for modem pooling:

1.Using change system-parameters feature, set Off-Premises Tone Detect Timeout Interval to 25 seconds.

2.Using add modem-pool next (for System 75 or Generic 1) or add modem-pool xxxx (for Generic 3, where xxxx is the next available number), set Group Type to combined and press

ENTER . The screen will be ???lled in as shown in Figure 11-8, System 75, Generic 1, and Generic 3 Modem Pool Assignments.

Make the entries as shown. Analog and digital assignments correspond to the equipment locations of the TN742 or TN746B and the TN754 circuits, respectively. When all entries are made, press

ENTER .

11-22 DCP Mode 2 Installation and Administration

________________________________________________________________________________________________

________________________________________________________________________________________________

3.Procedure 100, Word 2 (for the digital side):

a.Enter the trunk group number (tgroup1) in Field 1.

b.Set the data rate for each speed optioned for the data modules in the modem pool in Fields 2 through 10.

c.Set Synchronous to 0 for asynchronous operation (Field 11 = 0).

d.Set Duplex to 0 for full duplex (Field 12 = 0).

e.Set Modem Pool Mode - Originate to 1 (Field 13 = 1).

f.Set Modem Pool Mode - Answer to 1 (Field 14 = 1).

g.Set Modem Pool - Modem Type to 1 (Field 15 = 1).

h.Set Modem Pool - Clock to 0 (Field 16 = 0).

i.Set Modem Pool - First Choice to 1 (Field 17 = 1).

j.Set Test Type to 0 (to turn off periodic on-line testing) or 1 (to allow periodic on-line testing) (Field 18). Currently only R2V3 systems should have Field 18 set to 1. On other systems, Field 18 should be 0.

k.Set Host Access Clock to 0 (Field 19 = 0).

* = data rate (translate 64 Kbps in addition to optioned rates, usually 9600 bps) $ = test type (see item j above)

4.Procedure 100, Word 1 (for the analog side):

a.Enter the trunk group number (tgroup2) in Field 1. A dial access code is not required (Fields 2 through 5).

b.Set Trunk Type to 101 (Field 6 = 101).

c.Set Dial Access Restriction to 0 (Field 7 = 0).

d.Set CO Line Appearance to 0 (Field 8 = 0).

11-24 DCP Mode 2 Installation and Administration

________________________________________________________________________________________________

________________________________________________________________________________________________

Generic 2 Administration

The following Manager II translations need to be completed on Generic 2 to implement modem pooling.

1.Using Procedure 100, Word 1, make the assignments shown in Fields 1 through 9 for the digital side of the modem pool. Refer to Figure 11-9, Manager II Administration for Digital Side of Modem Pooling (Proc 100, Word 1).

The trunk group (130) and the dial access code/trunk ID code shown are only examples; enter the appropriate values supplied by the BCSDC.

ENHANCED MODE - PROCEDURE: 100, WORD: 1

TRUNK GROUP TRANSLATION

1. Trunk Group: 130

DIAL ACCESS CODE/TRUNK ID CODE

2.Digit 1: 2

3.Digit 2: 1

4.Digit 3: 5

5.Digit 4: -

6.Trunk Type: 102 Digital data modem pool (18)

7.Dial Access Restriction: 0 Access is allowed using DAC

8.Personal CO Line Appearance: 0 Not used for CO line appearance

9.Public Network Access/Egress: 0 Disabled

Figure 11-9. Manager II Administration for Digital Side of Modem Pooling (Proc 100, Word 1)

_______________________________________________________________________________________

_______________________________________________________________________________________

2.Using Procedure 100, Word 2, make the assignments shown in Fields 1 through 7. Assign a custom BCCOS to the trunk group (trunk group 130 and a custom BCCOS of 10 are shown only as examples). The custom BCCOS should mirror the default BCCOS 1 as shown in Figure 11-10,

Manager II Administration for Digital Side of Modem Pooling (Proc 100, Word 2).

ENHANCED MODE - PROCEDURE: 100, WORD: 2

TRUNK GROUPS - MODEM POOLING AND BCCOS

MODEM POOLING

3.Originate Mode: 1

4.Answer Mode: 1

5.Modem Type: 1

6.First Choice: 1

7.Test Type: 0

Figure 11-10. Manager II Administration for Digital Side of Modem Pooling (Proc 100, Word 2)

_______________________________________________________________________________________

_______________________________________________________________________________________

4.Using Procedure 014, Word 2, select the data rates that will be used by the data modules in the modem pool. Figure 11-12, Manager II Administration for Digital Side of Modem Pooling (Proc 014, Word 2), shows data rates of 64 Kbps and 9600 bps and a custom BCCOS of 10 (these values are shown as examples only).

ENHANCED MODE - PROCEDURE: 014, WORD: 2

BEARER CAPABILITY CLASS OF SERVICE - DATA OPTIONS

1. Bearer Capability COS: 10

DATA RATE

2.64000 bps: 1 Supported

3.56000 bps: 0 Not supported

4.19200 bps: 0 Not supported

5.9600 bps: 1 Supported

6.4800 bps: 0 Not supported

7.2400 bps: 0 Not supported

8.1200 bps: 0 Not supported

9.300 bps: 0 Not supported

10.Low Speed: 0 Not supported

11.Synchronous: 0 Asynchronous

12.Duplex: 0 Full duplex

13.Clock: 0 Internal

14.Default Data Rate: 9 64000 bps

Figure 11-12. Manager II Administration for Digital Side of Modem Pooling (Proc 014, Word 2)

_______________________________________________________________________________________

_______________________________________________________________________________________

6.Using Procedure 100, Word 2, make the assignments shown in Fields 1 through 7. Assign BCCOS 5 to the trunk group (trunk group 131 is only an example). Refer to Figure 11-14, Manager II Administration for Analog Side of Modem Pooling (Proc 100, Word 2).

ENHANCED MODE - PROCEDURE: 100, WORD: 2

TRUNK GROUPS - MODEM POOLING AND BCCOS

MODEM POOLING

3.Originate Mode: -

4.Answer Mode: -

5.Modem Type: -

6.First Choice: -

7.Test Type: -

Figure 11-14. Manager II Administration for Analog Side of Modem Pooling (Proc 100, Word 2)

12. DCP Mode 3 Installation and Administration

_______________________________________________________________________________________

_______________________________________________________________________________________

Digital Communications Protocol (DCP) Mode 3 uses 64 Kbps, end-to-end, packet-mode operation for data transmission. It may be used in the following setups:

???Local Networking: If you are installing a DCP Mode 3 network for two or more colocated (local) AUDIX systems (the AUDIX systems are connected to the same switch), refer to Chapter 9, DCP Cabling and Administration. There you install and translate each AUDIX system with the extension numbers required for each network channel. There are no requirements except extension numbers for a local AUDIX network.

???Remote Networking: If you are installing a DCP Mode 3 network that requires interlocation facilities, these facilities are typically T1 Carrier employing common (clear) channel signaling or an Integrated Systems Digital Network (ISDN) pipe.

This chapter covers administration and testing for DCP Mode 3 AUDIX networking setups.

SWITCH COMPONENT INSTALLATION

See the appropriate switch and/or feature documentation for installing circuit packs and wiring trunks on the switch.

SWITCH ADMINISTRATION

See the appropriate switch and/or feature documentation for ISDN administration. For DS1 administration of either local or remote AUDIX networking setups, see the following sections.

System 75, Generic 1, and Generic 3 Administration

The DS1 circuit pack uses the Common Channel Signaling mode to provide 23 trunks for data transmission and one channel for signaling. The DS1 trunk group must be assigned for AV/D.

At this time, use standard AV/D DS1 administration. Any speci???c assignments that become necessary for AUDIX networking will be covered in future issues of this document.

12-1

12-2 DCP Mode 3 Installation and Administration

________________________________________________________________________________________________

________________________________________________________________________________________________

System 85 Administration

The DS1 circuit pack uses the Common Channel Signaling mode to provide 23 trunks for data transmission and one channel for signaling. The DS1 trunk group must be assigned for AV/D using the following MAAP procedures.

1.For local and remote AUDIX setups: Assign a bearer capability of mode 0 data to the class of service for the AUDIX networking extensions (Proc 010, Word 4, Field 3 = 4).

2.Assign a trunk group and trunk type using Procedure 100, Word 1. Assign members to the trunk group using Procedure 116.

3.For remote AUDIX setups only: The trunk group used to transport the AUDIX networking call must be DS1, and the DS1 pipe must employ 24th channel signaling.

a.Enter the trunk group number (tgroup) in Field 1.

b.Make sure Touch Tone In and Touch Tone Out are set to 1 (Fields 6 and 7 = 1).

c.AVD must be set to 1 (Field 17 = 1).

4.For remote networking con???gurations using AAR or ARS: If the local AUDIX DCP extensions dial AAR or ARS to reach a remote AUDIX system, make sure the FRL assigned to the AUDIX networking extensions??? cos is of a suf???cient value to get over the pattern and preference to allow calls from mode 0 data endpoints (Proc 309, Word 5, Field 10 = 1, or Proc 321, Word 5, Field 9 = 1).

Generic 2 Administration

This section describes the Manager II translations that must be completed on Generic 2 to implement DCP Mode 3 networking on AUDIX systems.

1.For local and remote AUDIX setups: You should have already assigned BCCOS 6 to the AUDIX DCP extensions in Chapter 9. Refer to Chapter 9 if necessary and check Figure 9-5, Manager II Administration of a DCP Port (Proc 000, Word 3).

2.For remote AUDIX setups only: The trunk group used to transport the AUDIX networking call must be DS1, and the DS1 pipe must employ 24th channel signaling.

12-4 DCP Mode 3 Installation and Administration

________________________________________________________________________________________________

________________________________________________________________________________________________

LOOPBACK TESTING FOR INTERLOCATED SYSTEMS

If the AUDIX systems to be networked are at different locations (interlocated) and a serving of???ce (SO) will provide 64 Kbps service, you will need to test the connection between the local AUDIX system and the 64 Kbps serving of???ce (SO), as shown in Figure 12-2, 64 Kbps Network Loop-Around Test. If you have R1V7 software, you can do this via the maintenance : network form for the DCP ports (ports 1-4). If you have an MPDM/M1* connected to ports 5 and 6, they may also be tested for 64 Kbps operation using this form.

While a channel is in loopback mode, it will be unavailable to send information to remote systems or receive information from remote systems. Incoming calls will be answered, but the calling system will be unable to establish a connection; eventually it will drop the call and attempt to call back at its next scheduled transmission time.

Also, if you put a channel in loopback mode, any active calls will be dropped. It is therefore recommended before you perform this test you check the status of the channel. It is also not a good idea to perform this test during peak traf???c times.

1. Go to the maintenance : network form. Set select test to 8 to test a 64 Kbps network

2.Have the serving of???ce place a call to the telephone number assigned to the channel you speci???ed on the maintenance : network form. If the test is successful, any data the serving of???ce sends over the AUDIX channel will be echoed back.

3.Go to the maintenance : network form. Set select test to 9 to take the channel out of

_______________________________________________________________________________________

_______________________________________________________________________________________

MAINTENANCE: NETWORK FORM:

NETWORK LOOPAROUND START 56/64 Kbps

Figure 12-2. 64 Kbps Network Loop-Around Test

13. AUDIX System Administration

_______________________________________________________________________________________

_______________________________________________________________________________________

Before you can administer an AUDIX system for networking, the ACC or ACCE must be installed. If not done already, install the AUDIX Communications Controller (ACC or ACCE) circuit pack and make sure it is administered using the maintenance : network and the system : translation : network port form. form. Then use this chapter to administer the AUDIX system in association with one or more other AUDIX systems for networking.

REMOTE UPDATES

Each AUDIX system in a network has its own data base with information on both local subscribers and remote subscribers. The system administrator may use the remote updates feature to make certain that every AUDIX data base has the same information for all subscribers across the network. When an AUDIX system sends remote update information for a subscriber to another system, it sends the voiced name, ASCII name, extension, and (for R1V5 and later systems) the community ID.

The remote updates will only be sent for subscribers whose extension numbers fall within the extension ranges administered on the system : translation : machine : audix/amis/call delivery form. For example, AUDIX A may be administered with an address range from 3000 to 3999. If AUDIX B???s remote pro???le for AUDIX A only lists a subset of this range (such as extensions 3000 to 3100), AUDIX B will only request partial or complete updates for extensions 3000 to 3100 from AUDIX A.

Partial Updates

The AUDIX systems in the network can be administered so partial updates happen automatically. If all systems in the network are so administered, any time a subscriber pro???le is added, deleted, or modi???ed from a system in the network, that system will automatically notify all other systems in the network of the change.

13-1

_______________________________________________________________________________________

_______________________________________________________________________________________

The network turnaround feature reduces system overhead time and long-distance charges by allowing all of these events to occur with a single call rather than two calls. If cost control from a central point is not critical, greater ef???ciency can be gained by implementing the network connection turnaround feature. The connection can only be turned around once during a single call.

If the system has an ACCE board installed, you can monitor the status of the network turnaround feature using the activity ???eld on the maintenance : network form (see Chapter 14 for an illustration of this form).

SYSTEM PROFILES

To administer a network, the local machine, and each remote machine to which the local machine is connected, must have a pro???le administered on the local system. The system : translation : machine : audix/amis/call delivery form is much like the subscriber : local form, except that it is used to set up pro???les for individual AUDIX systems rather than for individual subscribers. The pro???le for the system to which the administration terminal is connected should already be set up with some default values. These values may have to be changed now that the system will be part of a network. See Setting Up the Local AUDIX System Pro???le in this chapter. Once the local pro???le is set up, a remote pro???le must be set up for each remote system in the network. See Setting Up a Remote AUDIX System Pro???le in this chapter.

SETTING UP THE LOCAL AUDIX SYSTEM PROFILE

Enter sys trans ma au on the path line. Press RETURN . The screen should display a blank system : translation : machine : audix/amis/call delivery form. Press ENTER . The form should be ???lled in with the values already assigned to the local system. See Figure 13-1, Local AUDIX System Pro???le.

The customer or the Account Team should provide you with a copy of the Administrator???s Worksheet ???lled in with values to be entered on this form. If not, use the copy provided at the end of this chapter and ???ll in the values as you go. The following paragraphs provide guidelines for administering the local AUDIX system.

13-4 AUDIX System Administration

________________________________________________________________________________________________

________________________________________________________________________________________________

Form Fields

displayed in this ???eld. After you log off and log back on, this name will also be displayed in the upper left-hand corner of the AUDIX system screen.

If you change the name of the local AUDIX system and it is running R1V5 or later software, reset the ACCE: access the maintenance : network form, enter a 5, and press CHANGE or RUN . If you change the name of the local AUDIX system and it is running R1V3 or R1V4 software, restart the AUDIX system via the startup form.

???local/remote

This display-only ???eld should show l, for local system.

_______________________________________________________________________________________

_______________________________________________________________________________________

???password

Enter 5 to 10 alphanumeric characters. This password does not have to be unique. Record it on paper so that it is not forgotten ??? you will need it when administering the other systems in the network. The password will not be displayed the next time you enter the form.

If you change the password and the AUDIX system is running R1V3 or R1V4 software, run the network data audit. To run the audit, see the maintenance : audits : fp form. If the system is running R1V5 or later software, this step is not necessary.

???extension length

This ???eld should already be set to the correct length, the length of the switch extensions used by the local subscribers.

???voice name

This ???eld indicates the presence of a recorded machine name fragment; no assignment is required at this time. Instructions for recording names are given later in this chapter.

???voice ID

This is a display-only ???eld showing the identi???er associated with this machine???s name fragment. The identi???er is used when recording the fragment. The local AUDIX voice ID is always 0.

???default community

The default community of AUDIX system subscribers for this machine. A community contains those subscribers who are able to send voice mail messages as permitted on the system : sending restriction form. This value can be overridden for individual subscribers on the subscriber : local form.

Using this ???eld and the system : sending restriction form, you can permit subscribers to send, or prevent them from receiving, digital networking messages on a community-of-interest basis. See the AUDIX Feature Descriptions for details about the sending restrictions feature.

???network connection type

This ???eld is only used when this system calls itself for testing purposes.

This is the type of connection the AUDIX system will attempt to set up for the test call.

???Enter dcp if the system has only Digital Communications Protocol (DCP) connections to the switch.

???Enter rs232a if the system has only switched RS-232 connections to the switch. Check the option settings on the modems or data sets for synchronous or asynchronous to be sure. If they are set for synchronous, enter rs232s.

???If the system has DCP and RS-232 connections, enter dcp for now.

???data rate

This ???eld is only used when this system calls itself for testing purposes.

_______________________________________________________________________________________

_______________________________________________________________________________________

7.The remote system will request updated subscriber information from the local system (if the local system previously noti???ed the remote system that it had updates to send). The local system will then send its updated subscriber information to the remote system.

8.The remote system will send voice mail to the local system.

9.The remote system will send updated message status information to the local system.

Set this ???eld to n if you do not want to implement network turnaround. In this case, only steps 1 through 4 will occur.

???send to non-administered recipients (y/n)?

The default value is y. If this ???eld is y, when a subscriber addresses a message to a remote extension that does not map to a remote subscriber known by the local AUDIX system, the local AUDIX system will add this potential subscriber to its data base and then send the message to every remote system in the network for which the subscriber address is valid.

The AUDIX system does this in case a new subscriber has been added somewhere in the network and this remote system has not been made aware of it either through administrator communication or through remote updates. If the subscriber is found on a remote AUDIX machine, the local AUDIX system will deliver this message to the valid remote machine(s) and validate this new subscriber. If a valid remote subscriber cannot be found, the subscriber record will be deleted eventually by one of the system audits and the AUDIX system will change the status of the message from ??????undelivered?????? to ??????undeliverable?????? in the message sender???s voice mailbox.

If this ???eld is n, when a subscriber addresses a message to a remote extension or name that does not map to a remote subscriber known by the local AUDIX system, the local AUDIX system will not send the message. The subscriber who is attempting to address the message will be noti???ed that the extension is invalid.

If the network administrators keep open lines of communication (or there is just one administrator for the entire network), chances are good that each system will be kept up-to-date. Therefore, the customer would want an n entered here so the local AUDIX system is not burdened with ???nding a subscriber that probably does not exist in the ???rst place. (What usually has happened is that a user has misdialed.)

13-10 AUDIX System Administration

________________________________________________________________________________________________

________________________________________________________________________________________________

Saving Local System Data

When you have ???nished entering data in the ???elds, press CHANGE or RUN . If the system is running R1V5 or later software, any changes or additions to this form are put to use immediately. R1V3 and R1V4 require that the network data audit be run. To run the audit, see the maintenance : audits : fp form.

SETTING UP A REMOTE AUDIX SYSTEM PROFILE

Log in to the local AUDIX system using the display terminal and enter sys trans ma au on the path line. Press RETURN . A blank machine pro???le will be displayed. See Figure 13-2, Remote AUDIX System Pro???le, for a sample of what you will be entering. The customer or the Account Team should provide you with a copy of the Administrator???s Worksheet ???lled in with values to be entered on this form. If not, use the copy provided at the end of this chapter and ???ll in the values as you go. The following paragraphs provide guidelines for administering remote AUDIX systems.

Figure 13-2. Remote AUDIX System Pro???le

_______________________________________________________________________________________

_______________________________________________________________________________________

Form Fields

??? machine name

Enter the name of the remote system. Press ENTER to make sure this name is not already assigned. At

the bottom of the form you should see ??????doesn???t exist??????.

???local/remote

This is a display-only ???eld. It will display r once the remote system is administered on the local system.

???password

Enter 5 to 10 alphanumeric characters. This password does not have to be unique. Record it on paper so that it will not be forgotten. You will need it when administering the other systems in the network. It will not be displayed the next time you enter this form.

???extension length

Enter the length of the extensions used for this remote system.

???voice name

This ???eld indicates the presence of a recorded machine name fragment; no assignment is required at this time. Instructions for recording names are given later in this chapter.

???voice ID

This is a display-only ???eld showing the identi???er associated with this machine???s name fragment. The identi???er is used when recording the fragment. The remote AUDIX system voice ID is between 1 and 100.

???default community

The default community of AUDIX system subscribers for this machine. A community contains those subscribers who are able to send voice mail messages as permitted on the system : sending restriction form. This value can be overridden for individual subscribers on the subscriber : remote form.

Using this ???eld and the system : sending restriction form, you can permit subscribers to send, or prevent them from receiving, digital networking messages on a community-of-interest basis. See the AUDIX Feature Descriptions for more information about the sending restrictions feature.

_______________________________________________________________________________________

_______________________________________________________________________________________

On the remote AUDIX system, if the updates in ???eld on the system : translation :

machine : audix/amis/call delivery form is set to y, it will accept updated data base information from the local AUDIX system (provided the local system???s updates out ???eld is set to y).

On the remote AUDIX system, if the updates out ???eld on the system : translation :

machine : audix/amis/call delivery form is set to y, it will send updated data base information to the local AUDIX system (provided the local system???s updates in ???eld is set to y).

The Remote Updates feature of AUDIX Networking must be active (see the system : translation : remote updates form).

If these ???elds are left n after testing, this remote system will not notify this local system of changes to its data base nor will this local system send update information to this particular remote system. (neither partial nor complete updates will be permitted).

???network turnaround (y/n)?

Set this ???eld to y to implement network turnaround. (This ???eld must also be set to y on the local machine pro???le for network connection turnaround to work).

If network connection turnaround is implemented, the local machine will call this remote machine and the following sequence of events will occur:

1.The local system will notify this remote system that it has updated subscriber information to send.

2.The local system will request updated subscriber information from this remote system (if this remote system previously noti???ed the local system that it had updates to send). This remote system will then send its updated subscriber information to the local system.

3.The local system will send voice mail to this remote system.

4.The local system will send updated message status information to this remote system.

5.The network connection will then be turned around and the remaining events will occur:

6.The remote system will notify the local system that it has updated subscriber information to send.

7.The remote system will request updated subscriber information from the local system (if the local system previously noti???ed the remote system that it had updates to send). The local system will then send its updated subscriber information to the remote system.

8.This remote system will send voice mail to the local system.

9.This remote system will send updated message status information to the local system.

Set this ???eld to n if you do not want to implement network connection turnaround for this speci???c remote machine. In this case, only steps 1 through 4 will occur.

13-16 AUDIX System Administration

________________________________________________________________________________________________

________________________________________________________________________________________________

???send to non-administered recipients (y/n)?

The default value is y. If this ???eld is y, when a subscriber addresses a message to a remote extension that does not map to a remote subscriber known by the local AUDIX system, the local AUDIX system will add this potential subscriber to its data base and then send the message to every remote system in the network for which the subscriber address is valid.

The AUDIX system does this in case a new subscriber has been added somewhere in the network and this remote system has not been made aware of it either through administrator communication or through remote updates. If the subscriber is found on a remote AUDIX machine, the local AUDIX system will deliver this message to the valid remote machine(s) and validate this new subscriber. If a valid remote subscriber cannot be found, the subscriber record will be deleted eventually by one of the system audits and the AUDIX system will change the status of the message from ??????undelivered?????? to ??????undeliverable?????? in the message sender???s voice mailbox.

If this ???eld is n, when a subscriber addresses a message to a remote extension or name that does not map to a remote subscriber known by the local AUDIX system, the local AUDIX system will not send the message. The subscriber who is attempting to address the message will be noti???ed that the extension is invalid.

If the network administrators keep open lines of communication (or there is just one administrator for the entire network), chances are good that each system will be kept up-to-date. Therefore, the customer would want an n entered here so the local AUDIX system is not burdened with ???nding a subscriber that probably does not exist in the ???rst place. (What usually has happened is that a user has misdialed.)

Saving Remote System Data

When you are ???nished entering the data, press CHANGE or RUN . Any changes or additions to this form are put to use immediately unless the system is running R1V3 or R1V4 software; in this case, run a network data audit (see the maintenance : audits : fp form).

Exit the form and re-enter it to verify that the changes were accepted. Notice that the password is no longer displayed.

_______________________________________________________________________________________

_______________________________________________________________________________________

???For an AT&T Paradyne model 3820 modem connected to the RS-232 ports (not in a modem pool), enter the following for 9600 bps asynchronous operation. The same string should be used for the modem at the called system:

at&f0 &d2 m0 \n1 \q3 s0=1 s2=128 s76=1 s78=1 s41=3 &w0

???A Telebit T1000 stand-alone modem may be connected to the RS-232 ports (not in a modem pool). When the modem is ???rst installed, power it up, open the front panel, and push the RESET button. This puts the modem in conventional mode. You can then enter the following dial string for 9600 bps asynchronous operation. The same string should be used for the modem at the called system:

at &fm0 &d2 &c1 &k3 s0=1 s2=128 &w0 &y0

For T1000 modems only, the System 75, Generic 1, or Generic 3 analog stations form must have the distinctive audible alert ???eld set to n.

???modem initialization status

This display-only ???eld should be blank. If it is not blank, it is displaying the status of a previous initialization and it will be updated when you save your data.

???DCP ports ??? data rate for incoming mode 2 calls or 0 if channel not used

This ???eld does not apply for systems with the TN366 or TN366B. For systems with the TN539 or TN539B, this ???eld indicates the data rate that the TN539 or TN539B will specify in response to a "data options query" from the switch for an incoming DCP Mode 2 call (a call that uses modem pooling to access this remote system). Permissible values are 0, 1200, 2400, 4800, 9600, and 19200. If the DCP channels are not to be used, enter 0 in each ???eld. For System 75, Generic 1, or Generic 3, enter 0 for channel 2 and channel 4.

If the AUDIX system is using a 7400A or 7400B to talk with another AUDIX system that also uses a 7400A/B, the incoming DCP mode 2 data speed should match the speed set on the 7400A/B.

If the AUDIX system is receiving mode 2 calls from other AUDIX systems as well, and these systems use speeds different from the 7400A/B, multiple speeds can be entered on the form. Contact the BCSDC for information on using multiple speeds.

Saving Data

After you have completed this form, press CHANGE or RUN to save any changes or additions.

If initialization strings were entered, the AUDIX system will now send these strings to the modems to initialize them. The modem initialization status ???elds show ??????pending??????. After a few seconds, press

ENTER to display the status of this new initialization attempt. If ??????pending?????? is still displayed, repeat the wait-and-press ENTER procedure until some result is displayed. When a result is displayed, press SHIFT and TAB at the same time to get to the modem initialization status ???elds. Then press f5 (???eld help) for an explanation of the result.

13-22 AUDIX System Administration

________________________________________________________________________________________________

________________________________________________________________________________________________

ADMINISTERING SYSTEM LIMITS

Access the traffic : feature : day form by typing tr f d on the path line. Press RETURN .

Record the number displayed in the subscribers : local ???eld. You might add to this number the number of local subscribers the customer expects to add over the next 12 months; record the total. Also record the expected total of remote subscribers in the network (subscribers that reside somewhere in the network other than on the local system).

Next, access the system : limits form by typing sy li on the path line. Press RETURN . Administer the following ???elds.

Form Fields

???subscribers, local

Set this ???eld to the number (or expected number) of local subscribers, up to a maximum of 4000 (see Figure 13-4, The System Limits Form).

???administered remote

Enter the number of administered and nonadministered remote subscribers that are expected to be included in the entire network, up to a maximum of 28,000. Do not put in a larger number than necessary.

This ???eld is used for two purposes:

???To calculate the system data (sdat) ???lesystem size requirements for all remote subscribers (both administered and nonadministered)

???To calculate recommended ???lesystem size requirements for the other ???lesystems on the form for only the administered remote subscribers

Because of this dual purpose, the system : limits form should be used in two steps, as described in the next section.

Calculating Filesystem Sizes

To calculate ???lesystem space requirements for all remote AUDIX subscribers (both administered and nonadministered), use the following procedure:

1.Move the cursor to the subscribers, local ???eld and type the total number of administered local subscribers (for example, 2000).

_______________________________________________________________________________________

_______________________________________________________________________________________

2. Move the cursor to the subscribers, administered remote ???eld and type the total number of administered and nonadministered remote subscribers (for example, 6000). Press F1 (CHANGE or RUN).

3.Record the value displayed for the system data ???lesystem. This recommended ???lesystem size should accommodate all remote subscribers in the network (both administered and nonadministered).

4.Return to the subscribers, administered remote ???eld and type the number of

administered remote subscribers (for example, 4000). Press F1 (CHANGE or RUN).

5.The ???elds at the bottom of the screen indicate the recommended ???lesystem sizes for this system based on the limits you just entered. Record the recommended values for all the ???lesystems except the system data ???lesystem (which you calculated previously).

messages, total in all mailboxes: ______ awaiting delivery: ______

RECOMMENDED FILESYSTEM SIZES (IN BLOCKS), BASED ON LIMITS

Figure 13-4. The System Limits Form

_______________________________________________________________________________________

_______________________________________________________________________________________

MOVING A SUBSCRIBER BETWEEN AUDIX SYSTEMS IN A

NETWORK

At some time, you may need to move a subscriber (or a group of subscribers) from one AUDIX system to another in an AUDIX network. The recommended way to move a subscriber(s) from AUDIX system 1 to system 2 is shown below.

Make sure the remote update ???elds on the system : translation : machine :

audix/amis/call delivery and system : translation : remote updates forms are set to y for the entire network.

1. Remove the subscriber(s) from system 1 using the subscriber : local form and the DELETE key.

2.Run the mailing lists audit using the maintenance : audits : fp form on the local and remote systems. These audits will delete references to the removed subscriber(s) from any mailing lists on system 1. Then run the subscriber data audit. This audit will prevent errors or redundancy in the subscriber data. This reduces the chances of introducing problems into the network.

3.Do one of the following:

???Run a connection test using the maintenance : network form. One at a time, connect to all systems in the network. This test will notify the other systems of an update pending.

Now at each of the other systems, run a connect test to system 1. The subscribers removed from system 1 should now be deleted as remote subscribers at the other systems.

???If the network is not heavily loaded with voice mail between systems and the transmission intervals of the systems are set to 5 or 10 minutes, you can just wait for 30 minutes or so to make sure each system has had a chance to call all other systems.

4.Log in to system 2. Check the subscriber : remote form to verify that the removed subscriber(s) do not exist on this system. If the subscriber(s) still exist, remove them manually with

the DELETE key. If you are moving a range of subscribers, you will want to remove their range of extension numbers from system 1???s pro???le. Do this at system 1 (local machine pro???le) and at system 2 (remote machine pro???le).

Now you are ready to add the subscriber(s) to system 2.

1.Check the pro???le for system 2 (local machine pro???le). If the subscriber extension(s) is not part of one of the de???ned ranges, alter one of the ranges or add a new one. Be careful not to create an overlap of another range.

2.Repeat step 1 at all other systems on system 2???s pro???le (a remote pro???le for the other systems). This includes system 1.

14. AUDIX Network Testing

_______________________________________________________________________________________

_______________________________________________________________________________________

If you have just installed a network, go to the section of this chapter entitled Testing the Network Connections. If you are troubleshooting a network, go to Checking Administration Log Entries and

Troubleshooting the Network. Figures 14-1, 14-2, 14-3, and 14-4 show the maintenance : network form for various AUDIX software releases. This is the form you will use for network tests. Keep the following in mind when you perform network tests:

???There are six types of tests:

???Channel Internal Loop-Around Test ??? This test checks a single channel on the networking board. The test is local to the system being tested (Test 2).

???Modem Loop-Around Test ??? This test checks a single RS-232 channel and the modem connected to it, if so equipped. This test would not be used for RS-232 channels. The test is local to the system being tested (Test 6 ??? R1V5 or later RS-232 only).

???Network Loop-Around Start 56/64 Kbps Test ??? This test checks the transmission path from a 56 robbed-bit or 64 Kbps service of???ce (SO) facility to the local AUDIX system. The test can be conducted for any of the six AUDIX channels. To conduct the test for channels 5 or 6 (RS-232 channels) you need an MPDM/M1* between the AUDIX system and the PBX.

???Remote Connection Test ??? This test checks the transmission path from one system to another (Test 1; machine name = a remote system machine name; dialing string is ???xed). The dial string is set on the system : translation : machine : audix/amis/call delivery. Modem initialization strings are set on the system : translation : network port form.

???Near End Connection Test ??? This is a loop-around test; the local system calls itself [Test 1; machine name = the local system machine name and dial string is the network access code of the AUDIX Communications Controller (ACC) board]. When modem pooling is used in the network, the local modem pool is included in this test.

???Local Connection Test ??? This is a loop-around test; the local system calls itself [Test 1; machine name = the local system machine name and dial string is the extension number of the ACC board]. This test does not include modem pool facilities.

???The tests and, more speci???cally, the troubleshooting procedures, involve checking modem or data module settings, cabling, switch translations, and AUDIX system translations.

???AUDIX R1V3, R1V4, and R1V5 software limit the number of simultaneously active channels to four. To use all six channels simultaneously, an AUDIX system must have R1V6 or later software and a TN539 vintage 7 or TN539B ACCE.

???System 75, Generic 1, and Generic 3 only use channels 1 and 3 regardless of the AUDIX software used. The MERLIN II only uses channels 2 and 4. Do not try to use these channels for any tests.

This chapter also provides procedures for testing the Remote Updates feature and for testing voice mail between systems.

14-1

14-2 AUDIX Network Testing

________________________________________________________________________________________________

________________________________________________________________________________________________

1.connection test (machine name)

2.channel internal looparound test (channel)

3.channel busyout (channel)

4.channel enable (channel)

5.board reset

Figure 14-1. The Maintenance Network Form (R1V3 and R1V4)

1.connection test (machine name required)

2.channel internal looparound test (channel number required)

3.channel busyout (channel number required)

4.channel enable (channel number required)

5.board reset

6.modem looparound (channel number required)

Figure 14-2. The Maintenance Network Form (R1V5)

_______________________________________________________________________________________

_______________________________________________________________________________________

1.connection test (machine name required)

2.channel internal looparound test (channel number required)

3.channel busyout (channel number required)

4.channel enable (channel number required)

5.board reset

6.modem looparound (channel number required)

Figure 14-3. The Maintenance Network Form (R1V6)

1.connection test (machine name required)

2.channel internal looparound test (channel number required)

3.channel busyout (channel number required)

4.channel enable (channel number required)

5.board reset

6.modem looparound (channel number required)

7.network looparound start, 56 Kbps (channel number required)

8.network looparound start, 64 Kbps (channel number required)

9.network looparound stop (channel number required)

Figure 14-4. The Maintenance Network Form (R1V7)

14-4 AUDIX Network Testing

________________________________________________________________________________________________

________________________________________________________________________________________________

TESTING THE NETWORK CONNECTIONS

Once the network cabling and translations have been established between the local AUDIX system and one of the remote AUDIX systems, you are ready for the following:

1.Perform a connection test from the local system to the remote system (remote connection test). Remember that a remote system is any system in the network other than the system being tested. Even though a colocated system is not normally thought of as a remote system, to the local system it is.

2.If the remote connection test fails, perform the appropriate loop-around connect test (near-end connection test, local connection test, or 56/64 Kbps network loop-around test). The loop-around tests should be performed from the local system and, if nothing is found, performed from the remote system as well.

3.If the remote connection test and the loop-around test both fail, perform the internal channel and/or modem loop-around tests, as appropriate.

If at any time you get a ??????failed?????? response to a test, check the system : log form for possible reasons for the failure.

Step 1: Performing Remote Connection Tests

If you want to perform a test of the transmission path from the local system to a remote AUDIX system, select the appropriate remote connection test:

???Remote DCP connection test

???Remote switched RS-232 connection test

???Remote switched RS-232 converted to DCP connection test

???Remote dedicated RS-232 connection test

Step 1A: Testing Remote DCP Connections

This test involves a path similar to Figure 14-5, Remote Connection Test (Digital Path to Another AUDIX system) (DCP Mode 1 or 3) or Figure 14-6, Remote Connection Test (Analog Path to Another AUDIX system) (DCP Mode 2 ??? modem pooling). In the case of a colocated network, the path looks like Figure 14-7, Remote Connection Test (Colocated AUDIX system) (DCP Mode 3).