Lucent Technologies DEFINITY Enterprise Communication Server Release 8.2 Administrators Guide

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Managing data calls 
407 Data Modules — general 
15
CALLMASTER phones that have a connection to a data terminal or personal 
computer. The data modules integrate data and voice into the DCP protocol 
required to interface with the switch via a port on a digital-line circuit pack. Use 
the 7400B+ or 8400B+ instead of an MPDM when you need asynchronous 
operation at speeds up to 19.2-kbps to provide a DCP interface to the switch for 
data terminals and printers. The 7400B+ and 8400B+ do not support synchronous 
operation and keyboard dialing. Dialing is provided using the standard Hayes 
command set.
7400D
This data module supports synchronous operation with AUDIX, CMS, and DCS. 
It provides synchronous data transmissions at speeds of 19.2-Kbps full duplex.
7400C High Speed Link
The 7400C high-speed link (HSL) is a data-service unit that allows access to DCP 
data services. It provides synchronous data transmission at speeds of 56- and 
64-Kbps and provides a link to high-speed data networks. Used for Group 4 fax 
applications that include electronic mail and messaging, and electronic storage of 
printed documents and graphics. Use the 7400C for video teleconferencing and 
LAN interconnect applications.
7500 Data Modules
The 7500 Data Module connects data-terminal equipment (DTE) or 
data-communications equipment (DCE) to the ISDN network. The 7500 Data 
Module supports EIA 232C and V.35 interfaces and RS-366 automatic-calling 
unit interface (for the EIA 232C interface only).
The 7500 has no voice functions. Configure in the following ways:
nAsynchronous DCE
300, 1200, 2400, 4800, 9600, 19200-bps
nSynchronous DCE
1200, 2400, 4800, 9600, 19200, 56000, 64000-bps
nAsynchronous DTE (used for modem pooling)
up to 19200-bps
The 7500 Data Module is stand-alone or in a multiple-mount housing. 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Managing data calls 
408 Administered Connection 
15
Asynchronous Data Module 
NOTE:
The alias station command cannot be used to alias data modules.
Use the Asynchronous Data Module (ADM) with asynchronous DTEs as a data 
stand for the 7500 and 8500 Series of ISDN-BRI phones, thus providing 
connection to the ISDN network. The ADM provides integrated voice and data on 
the same phone and supports data rates of 300, 1200, 2400, 4800, 9600, and 
19200-bps. This module also supports the Hayes command set, providing 
compatibility with PC communications packages.
Related topics
Refer to ‘‘
Data modules’’ on page 558 for more information.
Administered Connection
An Administered Connection (AC) is a connection between two access or data 
endpoints. DEFINITY ECS automatically establishes and maintains the 
connection based on the attributes you administer. ACs provides the following 
capabilities.
nSupport of both permanent and scheduled connections
nAuto Restoration (preserving the active session) for connections routed 
over Software Defined Data Network (SDDN) trunks
nAdministrable retry interval (from 1 to 60 minutes) per AC
nAdministrable alarm strategy per AC
nEstablishment/retry/auto restoration order based on administered priority
Detailed description
Establish an AC between the following:
nTwo endpoints on the same switch
nTwo endpoints in the same private network, but on different switches
nOne endpoint on the controlling switch and another endpoint off the private 
network
In all configurations, administer the AC on the switch having the originating 
endpoint. For an AC in a private network, if the two endpoints are on two different 
switches, normally the connection routes via Automatic Alternate Routing (AAR)  
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Managing data calls 
409 Administered Connection 
15
through tie trunks (ISDN, DS1, or analog tie trunks) and intermediate switches. If 
required, route the connection via Automatic Route Selection (ARS) and 
Generalized Route Selection (GRS) through the public network. The call routes 
over associated ISDN trunks. When the far-end answers, a connection occurs 
between the far-end and the near-end extension in the 
Originator field on the 
AC screen.
Because the system makes an administered connection automatically, you do not 
use the following:
nData Call Setup
Do not assign a default dialing destination to a data module when it is used 
in an AC.
nData Hotline
Do not assign a hotline destination to a data module that is used in an AC.
nTerminal Dialing
Turn off terminal dialing for data modules involved in an AC. This prevents 
display of call-processing messages (INCOMING CALL,...) on the 
terminal.
Access endpoints
Access endpoints are non-signaling trunk ports. They neither generate signaling to 
the far-end of the trunk nor respond to signaling from the far-end. Designate an 
access endpoint as the originating endpoint or destination endpoint in an AC. 
Typical AC applications
The following are typical AC applications:
nA local data endpoint connection to a local or remote-access endpoint. 
Examples: an MPDM ACCUNET digital service connecting to SDDN via 
an ISDN trunk-group DS1 port; an MPDM ACCUNET digital service 
connecting to an ACCUNET Switched 56 Service via a DS1 port.
nA local-access endpoint connecting to a local or remote-access endpoint. 
Examples: a DSO cross-connect and a 4-wire leased-line modem to a 
4-wire modem connection via an analog tie trunk. 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Managing data calls 
410 Administered Connection 
15
nA local data endpoint connecting to a local or remote data endpoint such as 
a connection between two 3270 data modules.
NOTE:
The following guidelines do not include AAR and ARS, or GRS 
administration information for routing AC calls over trunk groups. 
Refer to the respective feature elsewhere in this book for that 
information.
Establishing Administered Connections
The originating switch attempts to establish an AC only if one of the following 
conditions exist:
nAC is active.
nAC is due to be active (either a permanent AC or time-of-day requirements 
are satisfied if it is a scheduled AC).
nOriginating endpoint is in in-service or idle state.
If the originating endpoint is not in service or is idle, no activity takes place for the 
AC until the endpoint transitions to the desired state. The originating switch uses 
the destination address to route the call to the desired endpoint. When the switch 
establishes two or more ACs at the same time, the switch arranges the connections 
in order of priority.
AC attempts can fail for the following reasons:
nResources are unavailable to route to the destination.
nA required conversion resource is not available.
nAccess is denied by class of restriction (COR), facilities restriction level 
(FRL), or bearer capability class (BCC). Or, an attempt is made to route 
voice-band-data over SDDN trunks in the public switch network.
nDestination address is incorrect.
nDestination endpoint is busy.
nOther network or signaling failures occur.
In the event of a failure, an error is entered into the error log, which generates an 
alarm, if it is warranted by your alarming strategy. You can display AC failures via 
the
 status-administered connection command. 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Managing data calls 
411 Administered Connection 
15
As long as an AC is due to be active, the originating switch continues to establish 
an AC unless the attempt fails because of an administrative error (for example, a 
wrong number) or service-blocking condition (for example, outgoing calls 
barred).
nThe frequency with which failed attempts are retried is determined by the 
administered retry interval (1 to 60 minutes) for each AC.
nRetries are made after the retry interval has elapsed regardless of the 
restorable attribute of the AC.
nACs are retried in priority order.
nWhen you change the time of day on the switch, an attempt is made to 
establish all ACs in the waiting-for-retry state.
Dropping Administered Connections
An AC remains active until one of the following occurs:
nThe AC is changed, disabled, or removed.
nThe time-of-day requirements of a scheduled AC are no longer satisfied.
nOne of the endpoints drops the connection. This could be because of user 
action (in the case of a data endpoint), maintenance activity resulting from 
an endpoint failure, busying out of the endpoint, or handshake failure. If the 
endpoints are incompatible, the connection is successful until handshake 
failure occurs.
NOTE:
An AC between access endpoints remains connected even if the 
attached access equipment fails to handshake.
nAn interruption (for example, facility failure) occurs between the 
endpoints.
If an AC drops because it was disabled/removed or is no longer due to be active, 
no action is taken. If an AC drops because of changed AC attributes, an immediate 
attempt is made to establish the connection with the changed attributes if it is still 
due to be active. Existing entries in the error/alarm log are resolved if they no 
longer apply. If handshake failure resulted in the dropping of the connection, in 
the case of an AC involving at least one data endpoint, no action is taken for that 
AC until the change administered-connection
 command is executed. 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Managing data calls 
412 Administered Connection 
15
Administered Connections failure: Auto
Restoration and Fast Retry
When an active AC drops prematurely, you must invoke either auto restoration or 
fast retry to determine whether auto restoration is attempted for an active AC.
If you option AC for auto restoration and the connection was routed over SDDN 
trunks, auto restoration is attempted. During restoration, connections are 
maintained between the switch and both endpoints. In addition to allowing the 
active session to be maintained, AC also provides a high level of security by 
prohibiting other connections from intervening in active sessions. Auto restoration 
generally completes before the 60-second endpoint holdover interval. If auto 
restoration is successful, the call might be maintained (no guarantee). The 
restoration is transparent to the user with the exception of a temporary disruption 
of service while restoration is in progress. A successful restoration is reflected by 
the restored state on the status AC screen. Although the restoration was 
successful, the data session may not have been preserved.
If auto restoration is not active or if the AC is not routed over SDDN trunks, the 
switch immediately attempts to reestablish the connection (fast retry). The switch 
also attempts a retry if the originating endpoint initiated the drop. With fast retry, 
connections are not maintained on both ends. Fast Retry is not attempted for an 
AC that was last established via fast retry, unless the AC is active for at least two 
minutes.
If auto restoration or fast retry fails to restore or reestablish the connection, the 
call drops and the AC goes into retry mode. Retry attempts continue, at the 
administered retry interval, as long as the AC is due to be active.
Administering Administered Connections
1. Choose one of the following data modules and administer all fields:
nData Line Data Module (use with Data Line circuit pack)
nProcessor/Trunk Data Module (use with one of the following:)
— MPDMs, 700D, 7400B, 7400D, or 8400B
MTDMs, 700B, 700C, 700E, or 7400A
nProcessor Interface Data Module (refer to DEFINITY ECS 
Administration for Network Connectivityfor more information)
nX.25 Data Module (refer to DEFINITY ECS Administration for 
Network Connectivity for more information)
n7500 Data Module (use with ISDN Line 12-BRI-S-NT or ISDN 
Line 12-BRI-U-NT circuit pack)
nWorld Class Core BRI Data Module (use with wcbri) 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Managing data calls 
413 Administered Connection 
15
2. On the DS1 Circuit Pack screen, administer all fields. Refer to ‘‘DS1 
Circuit Pack’’ on page 599 for more information. (Use with switch node 
carriers.)
3. On the Access Endpoint screen, administer all fields. Refer to ‘‘
Access 
Endpoint’’ on page 467 for more information.
4. Choose one of the following trunk groups and administer all fields. Refer to 
‘‘
ISDN trunk group’’ on page 738 and ‘‘Trunk Group’’ on page 967 for 
more information.
nISDN-BRI
nISDN-PRI
nTie
5. On the Class of Restriction screen, administer all fields. Refer to ‘‘
Class of 
Restriction’’ on page 520 for more information.
6. On the Class of Service screen, administer all fields. Refer to ‘‘
Class of 
Service’’ on page 532 for more information.
7. On the Dial Plan Record screen, administer the Local Node Number field 
with a number from 1-63 that matches the DCS switch node number and 
the CDR node number. Refer to ‘‘
Dial Plan Record’’ on page 593 for more 
information.
8. On the Administered Connection screen, administer all fields. Refer to 
‘‘
Administered Connection’’ on page 471 for more information.
9. On the Station screen, assign one button as ac-alarm. Refer to ‘‘
Station’’ on 
page 882 for more information.
10. On the Attendant Console screen, assign one button as ac-alarm. Refer to 
‘‘
Attendant Console’’ on page 484 for more information.
Interactions
nAbbreviated Dialing
Use Abbreviated Dialing entries in the 
Destination field. Entries must 
comply with restrictions.
nBusy Verification of Stations and Trunks
This feature does not apply to access endpoints because they are used only 
for data.
nCall Detail Recording
For an AC that uses a trunk when CDR is active, the origination extension 
is the originator of the call. 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Managing data calls 
414 Administered Connection 
15
nClass of Restriction
Reserve a COR for AC endpoints and SDDN trunks. This restricts 
endpoints that are not involved in AC from connecting to SDDN trunks or 
endpoints involved in AC.
nClass of Service/Call Forwarding
Assign to an AC endpoint a COS that blocks Call Forwarding activation at 
the endpoint.
nDigital Multiplexed Interface (DMI)
Use DMI endpoints as the destination in an AC. DMI endpoints do not 
have associated extensions, so do not use them as the originator in an AC.
nFacility Test Calls
The feature does not apply to access endpoints because an access endpoint 
acts as an endpoint rather than as a trunk.
nModem Pooling
If you require a modem in an AC, one is inserted automatically. If no 
modem is available, the connection is dropped.
nNon-Facility Associated Signaling (NFAS) and D-Channel Backup
Auto restoration for an AC that is initially routed over an NFAS facility 
may fail if the only backup route is over the facility on which the backup 
D-channel is administered. The backup D-channel may not come into 
service in time to handle the restoration attempt.
nSet Time Command
When you change the system time via the set time
 command, all scheduled 
ACs are examined. If the time change causes an active AC to be outside its 
scheduled period, the AC is dropped. If the time change causes an inactive 
AC to be within its scheduled period, the switch attempts to establish the 
AC.
If any AC (scheduled or continuous) is in retry mode and the system time 
changes, the switch attempts to establish the AC.
nSystem Measurements
Access endpoints are not measured. All other trunks in an AC are measured 
as usual. 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Managing data calls 
415 Modem Pooling 
15
Modem Pooling
Modem Pooling allows switched connections between digital-data endpoints (data 
modules) and analog-data endpoints via pods of acoustic-coupled modems. The 
analog-data endpoint is either a trunk or a line circuit.
Data transmission between a digital data endpoint and an analog endpoint requires 
conversion via a modem, because the DCP format used by the data module is not 
compatible with the modulated signals of an analog modem. A modem translates 
DCP format into modulated signals and vice versa.
Modem Pooling feature provides pools of integrated-conversion modems and 
combined-conversion modems.
Integrated-conversion modem pools have functionality integrated on the Pooled 
Modem circuit pack, providing two modems. Each one emulates a TDM cabled to 
a 212 modem. Integrated are modem pools not available in countries that use 
A-law companding.
Combined-conversion modem pools are TDMs cabled to any TDM-compatible 
modem. Combined-conversion modem pools can be used with all systems.
The system can detect the needs for a modem. Data calls from an analog-data 
endpoint require that the user indicate the need for a modem, because the system 
considers such calls to be voice calls. Users indicate this need by dialing the 
data-origination access code field on the Feature Access Code screen before 
dialing the digital-data endpoint.
The system provides a Hold Time parameter to specify the maximum time any 
modem can be held but not used (while a data call is in queue).
Administering Modem Pooling
For Integrated modem poolings:
1. On the Modem Pool Group screen, administer all fields. Refer to ‘‘
Modem 
Pool Group’’ on page 817 for more information.
2. On the Feature Access Code screen, administer the Data Origination 
Access Code field. Refer to ‘‘
Feature Access Code’’ on page 619 for more 
information.
3. On the Data Module screen, administer all fields. Refer to ‘‘
Data modules’’ 
on page 558 for more information. 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1
April 2000
Managing data calls 
416 Modem Pooling 
15
For Combined modem poolings:
1. On the Modem Pool Group screen, administer all fields. Refer to ‘‘
Modem 
Pool Group’’ on page 817 for more information.
2. On the Feature Access Code screen, administer the Data Origination 
Access Code field. Refer to ‘‘
Feature Access Code’’ on page 619 for more 
information.
Considerations
nOn data calls between a data module and an analog-data endpoint, 
Return-to-Voice releases the modem and returns it to the pool. The 
telephone user connects to the analog-data endpoint.
nFor traffic purposes, the system accumulates data on modem-pooling calls 
separate from voice calls. Measurements on the pools also accumulate.
nModem Pooling is not restricted. Queuing for modems is not provided, 
although calls queued on a hunt group retain reserved modems. 
nAvoid mixing modems from different vendors within a combined pool 
because such modems may differ in transmission characteristics. 
nEach data call that uses Modem Pooling uses four time slots (not just two). 
As a result, heavy usage of Modem Pooling could affect TDM 
bus-blocking characteristics.
nTandem switches do not insert a pooled modem. The originating and 
terminating switches insert a pooled modem.
Interactions
nCall Detail Recording
Data call CDR records the use of modem pools on trunk calls.
nData Call Setup
Data calls to or from a TDM cannot use Modem Pooling.
nData Privacy and Data Restriction
The insertion of a modem pool does not turn off Data Privacy or Data 
Restriction.
nData-Only Off-Premises Extensions
Calls to or from a Data-Only Off-Premises Extension cannot use Modem 
Pooling, when this type of digital-data endpoint uses a TDM.