Lucent Technologies DEFINITY Enterprise Communications Server Release 8.2 Instructions Manual

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1.1
June 2000
Managing data calls 
417 Data Restriction 
15
nIntercom — Automatic and Dial
An extension with Data Privacy or Data Restriction active cannot originate 
an intercom call. The user receives an intercept tone.
nMusic-on-Hold Access
If a user places a call with Data Privacy on hold, the user must withhold 
Music-on-Hold to prevent the transmission of tones that a connected data 
service might falsely interpret as a data transmission.
nPriority Calls
If a user activates Data Privacy, Priority Calls are denied on analog 
telephones. However, Priority Calls appear on the next available line 
appearance on multiappearance telephones.
Data Restriction
Data Restriction protects analog-data calls from being disturbed by any of the 
system’s overriding or ringing features or system-generated tones.
Data Restriction applies to both voice and data calls.
Once you administer Data Restriction for an analog or multiappearance telephone 
or trunk group, the feature is active on all calls to or from the terminal or trunk 
group.
NOTE:
Do not assign Data Restriction to attendant consoles.
Administering Data Restriction
1. On the Station screen, set the Data Restriction field to y. Refer to ‘‘
Station’’ 
on page 894 for more information.
2. Choose one of the following trunk groups and set the Data Restriction field 
to y. Refer to ‘‘
ISDN trunk group’’ on page 750 and ‘‘Trunk Group’’ on 
page 980 for more information.
nAccess
nAdvanced Private-Line Termination (APLT)
nCircuit Pack (CP)
nCustomer-Premises Equipment (CPE)
nDirect Inward Dialing (DID)
nForeign Exchange (FX) 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1.1
June 2000
Managing data calls 
418 Data Restriction 
15
nIntegrated Services Digital Network-Primary Rate Interface 
(ISDN-PRI)
nRelease-Link Trunk (RLT)
nTandem
nTie
nWide Area Telecommunications Service (WATS)
Interactions - Data Restriction
nAttendant Call Waiting and Call Waiting Termination
If Data Restriction is active, Call Waiting is denied.
nBusy Verification
Busy Verification cannot be active when Data Restriction is active.
nIntercom — Automatic and Dial
An extension with Data Privacy or Data Restriction activated cannot 
originate an intercom call. The user receives an Intercept tone.
nMusic-on-Hold Access
If a user places a call with Data Restriction on hold, The user must 
withhold Music-on-Hold to prevent the transmission of tones that a 
connected data service might falsely interpret as a data transmission.
nPriority Calls
Priority Calls are allowed if the analog station is idle. Call Waiting 
(including Priority Call Waiting) is denied if the station is busy. However, 
Priority Calls appear on the next available line appearance on 
multiappearance telephones.
nService Observing
A data-restricted call cannot be service observed. 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1.1
June 2000
Managing data calls 
419 Data-Only Off-Premises Extensions 
15
Data-Only Off-Premises Extensions
Data-Only Off-Premises Extensions allows users to make data calls involving 
data communications equipment (DCE) or digital terminal equipment (DTE) 
located remotely from the system site.
A Data-Only Off-Premises Extension uses an on-premises modular trunk data 
module (MTDM). The system communicates with remote data equipment through 
the private-line facility linking the on-premises MTDM and the remote data 
equipment.
Users can place data calls to this type of data endpoint using Telephone Dialing or 
Data Terminal (Keyboard) Dialing. Since there is no telephone at the remote site, 
originate data calls from the remote data terminal using Keyboard Dialing only.
Administering Data-Only Off-Premises 
Extensions
1. On the Processor/Trunk Data Module screen, administer all fields. 
Refer to ‘‘
Data modules’’ on page 572 for more information.
Considerations
nThe system does not support communications between two TDMs. Modem 
Pooling is similar to a TDM, it cannot be used on calls to or from a 
Data-Only Off-Premises Extension.
Interactions
nTelephone Dialing
An on-premises multiappearance telephone may have a Data Extension 
button associated with the TDM used for a Data-Only Off-Premises 
Extension. The telephone user and the remote user share control of the data 
module. Actions of the user at the telephone may affect the remote user.
— 1-Button Transfer to Data
The telephone user can transfer a call to the Data-Only Off-Premises 
Extension. The Data Extension button lamp on the telephone lights 
and the Call in Progress lamp on the data module lights during a 
data call.
— Data Call Preindication
The multiappearance telephone user presses the idle associated Data 
Extension button to reserve a data module. The data module is busy 
to all other users. When the user reserves a data module, the lamp 
associated with the Data Extension button winks and lights at any 
other associated telephones. A remote user receives the BUSY 
message when attempting to originate a call. 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1.1
June 2000
Managing data calls 
420 Data Modules — general 
15
— Return-to-Voice
To establish a data call, the telephone user presses the associated 
busy Data Extension button to transfer the call to the telephone. The 
data module associated with the Data Extension button is 
disconnected from the call. The Call in Progress lamp on the data 
module goes dark.
Data Modules — general
A Data Module is a connection device between a basic-rate interface (BRI) or 
digital-communications protocol (DCP) interface of the switch and data-terminal 
equipment (DTE) or data-communications equipment (DCE).
The following types of data modules can be used with the system:
nAnnouncement data module
nData line data module
nProcessor/trunk data module (P/TDM)
nNetcon data module (G3si configurations only) Refer to DEFINITY ECS 
Administration for Network Connectivity for more information.
nProcessor interface data module (G3si configurations only). Refer to the 
DEFINITY ECS Administration for Network Connectivity for more 
information.
nSystem port data module (G3r configurations only)
nX.25 data module (G3r configurations only). Refer to DEFINITY ECS 
Administration for Network Connectivity for more information.
n7500 data module
nWorld Class BRI data module
nEthernet data module. Refer to DEFINITY ECS Administration for 
Network Connectivity for more information.
nPoint-to-Point Protocol (PPP) data module. Refer to DEFINITY ECS 
Administration for Network Connectivity for more information.
NOTE:
The 51X series Business Communications Terminals (BCTs) are not 
administered on the Data Module screen. The 510 BCT (equivalent to a 
7405D with a display and built-in DTDM), 515 BCT (equivalent to a 7403D 
integrated with 7405D display module function, data terminal and built-in 
DTDM), and the 7505D, 7506D, and 7507D have a DCP interface but have 
built-in data module functionality. Both are administered through the Station 
screen. 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1.1
June 2000
Managing data calls 
421 Data Modules — general 
15
Detailed description of data modules
TTI allows data modules without hardware translation to merge with an 
appropriate data module connected to an unadministered port. The 
unadministered port is given TTI default translation sufficient to allow a terminal 
connected to the data module (connected to the port) to request a TTI merge with 
the extension of a data module administered without hardware translation. 
NOTE:
TTI is not useful for Announcement and X.25 hardware. 
Administration Without Hardware supports PDM, TDM, Data-Line, 
Announcement, and X.25 data modules.
NOTE:
The 513 BCT has an EIA interface rather than a DCP interface (no built in 
data module, attachable telephone, or telephone features). The 513 BCT is 
not administered; only the data module to which the 513 BCT is connected 
is administered.
7400A/7400B+/8400B+ Data Module
Use the 7400A data module instead of an MTDM when you support combined 
Modem Pooling. The 7400A data module supports asynchronous operation at 
speeds up to 19200-bps, and provides a DCP interface to the switch and an EIA 
232C interface to the associated modem. The 7400A operates in stand-alone mode 
as a data module.
7400B+ and 8400B+ data modules support asynchronous-data communications 
and operate in stand-alone mode for data-only service or in linked mode, which 
provides simultaneous voice and data service. The 7400B+ and 8400B+ provide 
voice and data communications to 7400D series phones and 602A1 
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. 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1.1
June 2000
Managing data calls 
422 Data Modules — general 
15
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.
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 572 for more information. 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1.1
June 2000
Managing data calls 
423 Administered Connection 
15
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) 
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. 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1.1
June 2000
Managing data calls 
424 Administered Connection 
15
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.
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. 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1.1
June 2000
Managing data calls 
425 Administered Connection 
15
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.
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. 
						

							DEFINITY ECS Release 8.2
Administrator’s Guide  555-233-506  Issue 1.1
June 2000
Managing data calls 
426 Administered Connection 
15
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.
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.