Lucent Technologies DEFINITY Enterprise Communications Server Release 8.2 Administration For Network Connectivity Manual

							Networking Screens 
271
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
A  Screens Reference
Retry Attempt 
Counter (N2) Specifies the number of times (0–7) to send one frame when this frame is not 
confirmed for a period of time. Default is 2.
Frame Size (N1)Specifies the number of bytes (135–263) in a frame. Default is 135. If the value is 
135, there can be up to 1080 bits within a frame. This value is suitable for all adjuncts 
and for DCS.
Retransmission (T1) 
Timer (1/10 seconds)The T1 timer is started at the beginning or the end of the transmission of a frame. At 
the end of this timer (0–250), retransmission of a frame is initiated according to the 
procedures for link set-up and disconnection or information transfer. Default is 10.
Idle (T4) Timer (1/10 
seconds) The T4 timer is a system parameter that represents the time a DTE allows without 
frames being exchanged on the data link (0–250). Default is 30.
Number of Outstanding 
PacketsSpecifies the number of packets (2–7) that can be sent without confirmation. Default 
is 2.
Restart (T20) Timer 
(seconds)The T20 timer is a DTE time-limit (0–500) started when DTE issues a restart 
indication and terminated when the restart request is received or confirmed. Default is 
8.
Reset (T22) Timer 
(seconds) The T22 timer is a DTE time-limit (0–500) started when DTE issues a reset indication 
and terminated when the reset request is received or confirmed. Default is 10. 
						

							Networking Screens A  Screens Reference
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
272
Data Module - type pdm (used for BX.25 connections with the r model)
This form applies only to the r model.
This form assigns a Modular Processor Data Module (MPDM) data module (700D, 
7400B, 7400D or 8400B). The MPDM is an external hardware device that provides a 
Data Communications Equipment (DCE) interface for connection to equipment such 
as data terminals, CDR output devices, on-premises administration terminal, Message 
Server, Property Management System (PMS), AUDIX, and host computers. It also 
provides a Digital Communications Protocol (DCP) interface to the digital switch. 
Use the tdm data module type to assign an MTDM, which provides an EIA Data 
Terminal Equipment (DTE) interface for connection to off-premises private line trunk 
facilities or a switched telecommunications network and a DCP interface for 
connection to the digital switch. 
Common FieldsSee Common Data Module Fields (256) for descriptions of fields on this screen that 
are not listed below.
Secondary data moduleSpecifies whether this PDM is the primary or secondary data module. 
Page 1 of 1
DATA MODULE
Data Extension: 30  Name: 27  BCC:
Type: pdm_________  COS: 1  Remote Loop-Around Test? n
Port: _______  COR: 1  Secondary data module? n
ITC: restricted__  TN: 1  Connected to: dte
ABBREVIATED DIALING
List1:
SPECIAL DIALING OPTION:
ASSIGNED MEMBER (Station with a data extension button for this data module)
Ext Name
1: 1002  27 character station name
Valid Value Usage
y/nEnter y if this PDM is the secondary data module used for 
Dual I-channel AUDIX networking. Enter n if this is the 
primary PDM, or if this data module is not used for AUDIX 
networking. The primary data module must be administered 
before the secondary data module may be added. If Port is 
X, this field must be set to n. 
						

							Networking Screens 
273
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
A  Screens Reference
Communication-Interface Processor Channel
Proc ChanDisplays the BX.25 virtual channel number or the TCP/IP listen port channel to carry 
this processor (virtual) channel.
EnableType y to enable a processor channel. Type n (default) to disable a processor channel.
                        PROCESSOR CHANNEL ASSIGNMENT
Proc                Gtwy     Interface  Destination  Session    Mach
Chan  Enable  Appl.  To  Mode  Link/Chan   Node       Port  Local/Remote  ID
  1:     _  ________   _    __  _____  _________  0____  ___   ___    __
  2: _  ________   _    __  _____  _________  0____  ___   ___    __
  3: _  ________   _    __  _____  _________  0____  ___   ___    __
  4: _  ________   _    __  _____  _________  0____  ___   ___    __
  5: _  ________   _    __  _____  _________  0____  ___   ___    __
  6: _  ________   _    __  _____  _________  0____  ___   ___    __
  7: _  ________   _    __  _____  _________  0____  ___   ___    __
  8: _  ________   _    __  _____  _________  0____  ___   ___    __
  9: _  ________   _    __  _____  _________  0____  ___   ___    __
 10: _  ________   _    __  _____  _________  0____  ___   ___    __
 11: _  ________   _    __  _____  _________  0____  ___   ___    __
 12: _  ________   _    __  _____  _________  0____  ___   ___    __
 13: _  ________   _    __  _____  _________  0____  ___   ___    __
 14: _  ________   _    __  _____  _________  0____  ___   ___    __
 15: _  ________   _    __  _____  _________  0____  ___   ___    __
 16: _  ________   _    __  _____  _________  0____  ___   ___    __
Valid entries Usage
1-128 (csi model)
1-256 (si model)
1-384 (r model)Enter information about the processor channel in the row 
corresponding to the processor channel number you want 
to use. Any Processor Channel number can be used in the 
range appropriate for the switch model.
For connections to adjuncts, processor channel numbers 1, 
2, 3, etc. are typically used. For connections between 
switches, it may be convenient to use processor channel 
numbers that are indicative of the endpoints of the 
connection. For example, processor channel 13 for a 
connection between switch 1 and switch 3.
Valid entries Usage
y/nEnter y when assigning the processor channel. This field must 
be set to n before you can change any of the processor channel 
parameters. 
						

							Networking Screens A  Screens Reference
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
274
Appl.Identifies the switch application used on this link.
Gtwy ToUsed for gtwy-tcp applications only. Identifies the processor channel that this 
processor channel is serving as a gateway to.
ModeIdentifies whether the IP session is passive (client) or active (server).Valid entries Usage
audix, dcs, fp-mwi, gateway, 
gtwy-tcp, mis, msaamwl, 
msaclk, msahlwc, msallwc, 
msamcs, qsig-mwi, and blankThe gateway application is used for conversion 
between ISDN and either  TCP/IP or BX.25. 
The gtwy-tcp application is used for 
conversion between BX.25 and TCP/IP.
These application types are used on the 
gateway switch only.
Valid entries Usage
1-128 (csi model)
1-256 (si model)
1-384 (r model)Two processor channels on the gateway switch are needed 
to set up a gtwy-tcp gateway, which converts between 
X.25 and TCP/IP protocols. For each of the two gtwy-tcp 
processor channels, the Gtwy To field points to the other 
gtwy-tcp processor channel. 
For example, if processor channels 5 and 17 are used for a 
gtwy-tcp gateway, Gtwy To for processor channel 5 
would be set to 17 and Gtwy To for processor channel 17 
would be set to 5.
Valid 
entriesUsage
c (client)
s (server)
blankThis field must be blank if the type of interface link is x.25 (r model) 
or procr-intf (si model). This field cannot be blank if the type of 
interface link is ethernet or ppp.
Set the Mode to s for ppp or ethernet connections to CMS. Set 
opposite values (cs) on the endpoints for ppp or ethernet 
connections between switches or between a switch and Intuity 
AUDIX. 
						

							Networking Screens 
275
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
A  Screens Reference
Interface LinkIdentifies the physical link carrying this processor (virtual) channel.
Interface ChanIdentifies the BX.25 virtual channel number or the TCP/IP listen port channel to carry 
this processor (virtual) channel.
Destination NodeIdentifies the switch or adjunct at the far end of this link. Valid entries Usage
1-25 (csi, si)
1-33 (r)For the csi model, all links (up to 25) must be used for tcp/ip 
connections.
For the si model, links numbered 1 through (4 times the number 
of PI circuit packs) can be either x.25 or tcp/ip. The rest of the 
links (up to 25) must be tcp/ip.
For the r model, links numbered 1 through (4 times the number 
of PGATE circuit packs) can be either x.25 or tcp/ip. The rest 
of the links (up to 33) must be tcp/ip.
Valid entries Usage
1-64 (x.25)
0, 5000-64500 
(ethernet or ppp)The channel number 0 means any available port can be used 
(which will be automatically selected by the system). 
For TCP/IP connections, the following values are 
recommended:
•5001 CMS (Appl. = mis)
•5002 Intuity AUDIX (Appl. = audix)
•5003 DCS (Appl. = dcs, not a gateway)
These three values should be reused for multiple 
instances of these applications; for example, if there are 
two Intuity AUDIX’s, use 5002 for both; or if there are 
four DEFINITY ECS’s, use 5003 for all four. The 
combination of Link, Interface Channel, and Mach ID 
must be unique.
•6000 + (Appl. = gtwy-tcp)
The Interface Channel number must be unique for the 
gtwy-tcp and gateway application types.
Valid entries Usage
A node name previously 
entered on the Node 
Names screen or blank.This must be a name entered on the Node Names screen. 
For ppp connections, it must match the Destination 
Node Name entered on the ppp Data Module screen. 
						

							Networking Screens A  Screens Reference
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
276
Destination Port Identifies the port number of the destination.
Session LocalA number used by the system to identify one end of a connection.
Session RemoteSee Session Local, above.
Mach IDThe machine identification number.Valid entries Usage
0, 5000-64500The channel number 0 means any available port can be 
used (which will be automatically selected by the system).
Valid entries Usage
1-128 (csi)
1-256 (si)
1-384 (r)The Local and Remote Session numbers can be any value 
between 1 and 256, but they must be consistent between 
endpoints. For each connection, the Local Session number on 
the local switch must equal the Remote Session number on the 
remote switch and vice versa.
It is allowed, and sometimes convenient, to use the same 
number for the Local and Remote Session numbers. For 
example, it is frequently convenient (but not necessary) to use 
the processor channel number for both the session numbers.
For the qsig-mwi and fp-mwi applications, the Local 
Session numbers must be unique on the switch. For other 
applications, it is allowed, but not recommended, to use the 
same Session numbers for two or more connections.
Valid entries Usage
1-63 (si model) For switches and Intuity AUDIX, the Machine ID is the 
Local Node Number on the dial plan. For the qsig-mwi 
and fp-mwi applications, the Machine ID is the index used 
on the Message Waiting Indication Subscriber Number 
Prefixes screen. Machine ID is not used for the CMS adjunct. 
						

							Networking Screens 
277
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
A  Screens Reference
Circuit Packs
This screen administers circuit packs to carrier slots before the circuit packs are 
actually installed in the carrier or cabinet. This allows the system to be configured 
(administered) when the circuit packs have not yet been physically inserted in their 
appropriate slots. Before any voice terminals, attendant consoles, or trunks can be 
administered in the system, the correct type of circuit pack must be installed in the 
appropriate slot, or using the Circuit Pack screen, a circuit pack must be assigned to 
the slot.
The Circuit Pack Administration screens do not have to be completed if the system 
cabinet is equipped with the circuit packs at the time of administration. However, for 
switch node carriers, these screens must be administered.
Note:For initial installation procedures, circuit packs should only be assigned 
slots per the hardware Configuration Layout record (obtained from the 
factory or Customer Services Support Organization). Arbitrarily 
assigning circuit packs to slots should not be attempted because this 
eventually requires (at the time of installation and test) realignment of the 
circuit packs and reworking associated wiring to agree with the software 
translations or new software translations to agree with the shipped 
hardware configuration.
Note:Each page of the screen represents one carrier within the cabinet 
specified on the command line. For G3si, all carriers and slots appear 
even if they are not included in the actual hardware. This supports 
reconfiguration.
CabinetThis field shows the cabinet number as entered on the command line.
                                                                   Page 1 of X
                                CIRCUIT PACKS
          Cabinet: __                           Carrier: _
   Cabinet Layout: ____________________    Carrier Type: _________________
   Slot Code   Sf Mode Name  Slot Code  Sf Mode Name
    00: ______ _  11: MEDPRO _  RESERVED-IP
    01: ______ _  12: MEDPRO _  RESERVED-IP
    02: ______ _  13: TN802_ B  MAPD
    03: ______ _  14: ______ _ 
    04: ______ _  15: ______ _ 
    05: ______ _  16: ______ _ 
    06: ______ _  17: ______ _ 
    07: ______ _  18: ______ _ 
    08: ______ _  19: ______ _ 
    09: ______ _  20: ______ _ 
    10: ______ _  21: ______ _ 
    ’#’ indicates circuit pack conflict.
Valid entries Usage
Display-only field.  
						

							Networking Screens A  Screens Reference
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
278
CarrierThis field shows the letter of the carrier (A through E) circuit packs are being 
administered on.
Cabinet LayoutThis field is only displayed for G3r. This field describes the physical layout of the 
cabinet.
Carrier TypeThis field shows the type of carrier.
Note:Note: For G3r, if the Carrier Type (as administered through the Cabinet 
Administration screen) does not match the physical hardware, the Code 
fields may display question marks.
SlotThe slot equates to the physical slot of the given carrier; the number of slots displayed 
depends on the system being configured.
•For G3r, the number of slots represent all administrable slots available for the 
given carrier type.
•For G3si, all slots that could possibly be administered are displayed, even if they 
do not apply to the current configuration of the system. This is to accommodate 
the situation when a system is being reconfigured. Valid entries Usage
Display-only field. 
Valid entries Usage
Display-only field.  Values that may display are five-carrier and 
single-carrier-stack.
Valid entries Usage
Display-only field. Values that may display are dup-switch-node, 
expansion-control, not-used, port, 
processor, and switch-node.
Valid entries Usage
Display-only field. 
						

							Networking Screens 
279
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
A  Screens Reference
CodeEnter the circuit pack code. If there is a physical circuit pack installed in the slot, the 
entry must match that of the circuit pack. If there is equipment administered on a slot, 
the equipment must be removed from the circuit pack before the circuit pack can be 
changed or removed.
SfxEnter the circuit pack suffix, if applicable.
ModeThis is a display-only field that shows the circuit pack mode, if applicable.
Note:
NameThis is a display-only field showing the alphanumeric name of the circuit pack (such 
as Digital Line).
Note:Note: When the circuit pack physically inserted in the slot differs from 
what has been administered on this screen, a # displays between the Sfx 
and Name fields. Valid entries Usage
TN followed by a 3- or 
4-digit number of a valid 
DEFINITY circuit pack.
a valid ADXxxx number
a valid ASAIxx number
a valid DIGx number
LGATE
TN802For the IP Interface assembly (TN802B/MAPD). 
There must be at least two empty slots preceding the 
slot administered as code TN802. The Code field for 
these empty slots will automatically be populated 
with DSMAPD, which must be changed to 
MEDPRO for the MedPro mode of the IP 
Interface/TN802B.
Valid entries Usage
B to Z
blank
Valid entries Usage
Display-only field.
Valid entries Usage
Display-only field. 
						

							Networking Screens A  Screens Reference
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
280
Signaling Group
The Signaling Group screen defines the signaling parameters for ISDN-PRI, H.323, and ATM signaling groups.
Type ISDN-PRIThe ISDN-PRI Signaling Group screen identifies groups of DS1 interface B-channels 
for which a given D-channel or D-channel pair carries associated signaling 
information. The Non-Facility Associated Signaling (NFAS) feature allows a 
D-channel to convey signaling information for B-channels that are located on DS1 
facilities other than the one containing the D-channel. With NFAS, a signaling group 
does not necessarily correspond to a single DS1 interface. The Signaling Group 
screen is administered to show how B-channels and D-channels are related.
The Signaling Group screen also supports Facility Associated Signaling (FAS). The 
screen establishes the fact that a D-channel carries signaling information for all 
B-channels on its associated DS1 interface, and for no others.
In addition, the screen administers Temporary Signaling Connections (TSC) used in 
support of DCS Over ISDN-PRI D-channel (includes ISDN-PRI D-channel DCS 
AUDIX).
Screen for ISDN-PRI Non-Facility Associated Signaling
Screen for ISDN-PRI Facility Associated Signaling
                                                            Page 1 of 5
                            SIGNALING GROUP
Group Number: 2              Group Type: isdn-pri
                    Associated Signaling? n          Max number of NCA TSC: 0  
                       Primary D-Channel:             Max number of CA TSC: 0  
                     Secondary D-Channel:          Trunk Group for NCA TSC:    
       Trunk Group for Channel Selection:         X-Mobility/Wireless Type: NONE
          Supplementary Service Protocol: a
         Trunk Brd      Interface ID          Trunk Brd      Interface ID
          1:                                 11:                    
          2:                                 12:                    
          3:                                 13:                    
          4:                                 14:                    
          5:                                 15:                    
          6:                                 16:                    
          7:                                 17:                    
          8:                                 18:                    
          9:                                 19:                    
         10:                                 20:     
                                                            Page 1 of 5
                            SIGNALING GROUP
Group Number: 2              Group Type: isdn-pri
                    Associated Signaling? y          Max number of NCA TSC: 0  
                       Primary D-Channel:             Max number of CA TSC: 0  
                                                   Trunk Group for NCA TSC:    
       Trunk Group for Channel Selection:         X-Mobility/Wireless Type: NONE
          Supplementary Service Protocol: a