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

							Intuity Translations for DCS AUDIX 
241
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
4  Networking Example
Intuity
 Translations for DCS AUDIX
This screen is administered on Intuity, not on the DEFINITY ECS.
CMS Administration
See CentreVu
Ò Call Management System, Software Installation and Setup, 585-215-866 for administration 
procedures for the CMS server.
Switch Interface Administration
Switch Link Type:_LAN
_ Switch:_Definity_____
Extension Length:_4
___ Country:_United States_Host Switch Number:_1___
Audix Number:_1___
Switch  IP Address/Host Name TCP Port Switch IP Address/Host Name TCP Port
Number Number
1__
192.168.200.11_______ 5002__11____  ___.___.___.________ ______
2__
192.168.200.11_______ 5021__12____  ___.___.___.________ ______
3__192.168.200.11_______ 5031__13____  ___.___.___.________ ______
4__192.168.200.14_______ 5041__14____  ___.___.___.________ ______
5__
_____________________ ______15____  ___.___.___.________ ______
:
10_
_____________________ ______20____  ___.___.___.________ ______ 
						

							CMS Administration 4  Networking Example
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
242 
						

							243Administration for Network Connectivity555-233-504 — Issue 1 — April 2000  CID: 77730
A    Screens Reference
This appendix gives detailed field descriptions for a selection of DEFINITY administration 
screens (forms). The screen descriptions are divided into two groups — a) Networking Screens, 
which are needed for network administration and are used in other chapters of this document, 
and b) Other Network-related Screens, which are related to network administration but not 
referred to elsewhere in this document. Field descriptions for other DEFINITY screens can be 
found in the Administrator’s Guide, 555-233-506.
Networking Screens
Node Names, page 245
IP Interfaces, page 247.
IP Routing, page 251
IP Media Parameters, page 255
Data Modules, page 256: 
ethernet, page 262
ppp, page 263
proc-intf, page 266
X.25, page 269
pdm, page 272
Processor Channel Assignment, page 273
Circuit Packs, page 277
Signaling Group and Administered NCA TSC Assignment, page 280
ISDN TSC Gateway Channel Assignments, page 291
Note:All Trunk Group screens are described in DEFINITY ECS R8 
Administrator’s Guide, 555-233-506. 
						

							 A  Screens Reference
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
244
Other Network-Related DEFINITY Screens
Communication Interface Links, page 293
Data Modules: netcon, analog-dm, page 295
Extended Trunk Access (ETA) Call Screening, page 298
Extension Number Portability Numbering Plan, page 299
Hop Channel Assignments, page 300
Node Number Routing, page 302
Message Waiting Indication Subscriber Number Prefixes, page 303
Synchronization Plan, page 304
Uniform Dialing Plan, page 307 
						

							Networking Screens 
245
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
A  Screens Reference
Networking Screens
Node Names
In this context, a node is defined as any of the following — a C-LAN port, a bridge or router, a CMS ethernet 
port, or an Intuity AUDIX, or other MSA (Message Server Adjunct) network interface card. The AUDIX and 
MSA node name and IP address must be entered on page 1 of the screen. The data for all other node types, 
including CMS, must be entered on pages 2–6.
The Node Names form holds up to 8 Audix node names with up to 7 characters each, up to 7 MSA node names 
(up to 7 characters each) on page 1. It holds up to 160 non-specific node names (up to 15 characters each) for 
DCS, CMS, or bridge/router nodes, on pages 2–6.
The node names and IP addresses in any network should be assigned in a logical and consistent manner from the 
point of view of the whole network. These names and addresses should be assigned in the planning stages of the 
network and should be available from the customer system administrator or from a Lucent representative.
NOTE:
Enter node names for Intuity AUDIX and MSA adjuncts 
on page 1.
Enter node names for CMS, switches, and routers 
starting on page 2.
page 1
Audix or MSA NameIdentifies the name of the AUDIX or Message Server Adjunct (MSA) node.
                                                                 page 1 of 6
                                 NODE NAMES
   Audix Name      IP address          MSA Names      IP Address
1. audix 
_         ___.___.___.___ 1. msa__ _         ___.___.___.___
2. _______         ___.___.___.___ 2. _______         ___.___.___.___
3. _______         ___.___.___.___ 3. _______         ___.___.___.___
4. _______         ___.___.___.___ 4. _______         ___.___.___.___
5. _______         ___.___.___.___ 5. _______         ___.___.___.___
6. _______         ___.___.___.___ 6. _______         ___.___.___.___
7. _______         ___.___.___.___ 7. _______         ___.___.___.___
8. _______         ___.___.___.___
Valid entries Usage
1-7 alphanumeric characters with no 
embedded spaces. 
Defaults: 
audix, msa (csi, si)
blank (r)Used as a label for the associated IP 
address. The node names must be unique 
on each switch. 
						

							Networking Screens A  Screens Reference
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
246
IP AddressThe IP address associated with the node name. (Not needed for X.25 connections).
Pages 2 – 6
NameThe name of the adjunct or switch node. Valid entries are alpha-numeric and/or 
special characters for identification. Default is blank.
IP AddressThe IP address for the node named in the previous field.
                                                                  Page 2 of 6
                                 NODE NAMES
 Name                  IP Address           Name              IP Address
 1. Default        
      0. 0. 0. 0. 17. _______________    ___.___.___.___
 2. _______________    ___.___.___.___  18. _______________    ___.___.___.___
 3. _______________    ___.___.___.___  19. _______________    ___.___.___.___
 4. _______________    ___.___.___.___  20. _______________    ___.___.___.___
 5. _______________    ___.___.___.___  21. _______________    ___.___.___.___
 6. _______________    ___.___.___.___  22. _______________    ___.___.___.___
 7. _______________    ___.___.___.___  23. _______________    ___.___.___.___
 8. _______________    ___.___.___.___  24. _______________    ___.___.___.___
 9. _______________    ___.___.___.___  25. _______________    ___.___.___.___
10. _______________    ___.___.___.___  26. _______________    ___.___.___.___
11. _______________    ___.___.___.___  27. _______________    ___.___.___.___
12. _______________    ___.___.___.___  28. _______________    ___.___.___.___
13. _______________    ___.___.___.___  29. _______________    ___.___.___.___
14. _______________    ___.___.___.___  30. _______________    ___.___.___.___
15. _______________    ___.___.___.___  31. _______________    ___.___.___.___
16. _______________    ___.___.___.___  32. _______________    ___.___.___.___
Valid entries Usage
1-15 alphanumeric characters 
with no embedded spaces.Used as a label for the associated IP address. The 
node names must be unique on each switch.
Valid entries Usage
32-bit address expressed 
in dotted-decimal notation 
— four decimal numbers 
each in the range 1–255 
separated by a decimal 
point.A unique IP address is assigned to each port on the 
C-LAN circuit pack that is used for a connection.
Each node name is associated with a unique IP 
address except in the following circumstance: If the 
network includes a gateway switch that connects to 
non-IP nodes (via X.25 or ISDN), then switches on 
the IP side of the gateway would list all nodes on the 
non-IP side of the gateway with the (same) IP address 
of the gateway; that is, several nodes could be listed 
on the Node Names screen with the same IP address.
See Chapter 1 for more information about IP 
addresses. 
						

							Networking Screens 
247
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
A  Screens Reference
IP Interfaces 
Use the IP Interfaces screen to define an interface to the LAN from either the C-LAN 
or MedPro circuit packs. The physical interface is port 17 on the C-LAN board and is 
a network interface card on the MedPro. This screen specifies the IP address (via the 
Node Names screen), subnet mask, default gateway address, and the network region 
for each IP interface on the local DEFINITY ECS.
Note:The C-LAN and MedPro circuit packs must be administered on the 
Circuit Packs screen before they can be administered on this screen.
Inter-region IP 
connectivity allowed?Specifies whether or not IP endpoints registered in one region can use media 
processing resources (MedPro) in another region.
change ip-interfaces                                            Page   1 of   2 
                                                                                
IP Interfaces
Inter-region IP connectivity allowed?  n
Enable Net
Eth Pt Type   Slot  Code Sfx Node Name   Subnet Mask  Gateway Addr Rgn
y   C-LAN  01A10 TN799 B  clan-a1    255.255.255.0   192.168.10 .100 1
   y  MEDPRO 01A13 TN802 B  med-a1    255.255.255.0   192.168.10 .100 1
y  MEDPRO 01A16 TN802 B  med-a2    255.255.255.0   192.168.20 .100 1
y   C-LAN  01A09 TN799 B  clan-a2    255.255.255.0   192.168.10 .100 2
   y  MEDPRO 01B13 TN802 B  med-a3    255.255.255.0   192.168.10 .100 2
y   C-LAN  01A09 TN799 B  clan-b2    255.255.255.0   192.168.20 .100 2
   n    255.255.255.0      .   .   .      
n    255.255.255.0      .   .   .      
n    255.255.255.0      .   .   .      
Valid Values Usage
y/nEnter y to allow IP endpoints (phones and trunks) to use 
MedPro resources administered in regions that are different 
from the endpoints’ regions.
The MedPro and C-LAN boards are assigned to the regions 
specified in the Net Rgn field. Endpoints are assigned to the 
same region as the C-LAN boards they use.
The DEFINITY system first allocates MedPro resources that 
are assigned to the same regions as the endpoints. If demand 
for MedPro resources exceeds supply within the local region, 
available MedPro resources from other regions are used if this 
field is set to y, or call blockage occurs if this field is set to n. 
						

							Networking Screens A  Screens Reference
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
248
Enable Eth PtUsed to enable or disable the C-LAN or MedPro IP Ethernet port. 
Ty p eSpecifies the type of circuit pack for the IP network interface (C-LAN or MedPro).
SlotSpecifies the location of the circuit pack for the IP network interface in the standard 
CCcss format (CC = cabinet number, c = carrier letter, ss = slot number). 
CodeDisplay only. Specifies the board code of the circuit pack for the IP interface. This 
field is automatically populated with TN799 for C-LAN or TN802 for MedPro.
SfxDisplay only. Specifies board code suffix. This field is automatically populated with 
B for the TN802 and the TN799.
Node NameThe unique node name for the IP interface. The node name must be on the Node 
Names screen (pages 2–6 only; node names on page 1 of the Node Names screen 
cannot be used in this field).Valid Values Usage
y/nThe Ethernet port must be enabled (y) before it can be used. The 
port must be disabled (n) before changes can be made to its 
attributes on this screen.
If an enabled Ethernet port is changed to disabled, all signaling 
and/or media connections will be removed and the associated 
calls will be torn down.
The busy-out command applied to the circuit pack for the 
interface overrules the Enable Eth Pt field. 
						

							Networking Screens 
249
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
A  Screens Reference
Subnet MaskThe subnet mask determines which part of an IP address is the network identifier and 
which part is the host identifier. The subnet mask is associated with the IP address 
administered on the Node Names screen for the IP interface identified by the Node 
Names field on this screen.
See Chapter 1 for more information on IP addresses and subnetting.
Gateway AddressSpecifies the address of a network node that will serve as the default gateway for the 
IP interface. Valid Values Usage
The valid values of the subnet 
mask depend on the IP address 
that the subnet mask is applied to 
— in this case, the IP address on 
the Node Names screen that is 
associated with the name entered 
in the Node Name field. 
In general, each octet value must 
be one of the following numbers: 
255 or 0, corresponding to the 
network and host portions of an 
IP address; or 192, 224, 240, 248, 
or 252, corresponding to using 2, 
3, 4, 5, or 6 bits from the host ID 
for the subnet ID.This field can be used to subdivide a network 
into 2 or more subnetworks. 
The subnet mask consist of a string of n 
contiguous 1’s followed by a string of 32–n 
contiguous 0’s. When applied to a 32-bit IP 
address, the subnet mask indicates that the first 
n bits of the address form the network ID and 
the next 32–n bits form the host ID portion of 
the address.
The following default values for the subnet 
mask are used for no subnetting: 
Class A addresses:  255.0.0.0
Class B addresses: 255.255.0.0
Class C addresses: 255.255.255.0
Valid Value Usage
An IP address of a 
bridge or router on 
the network that is 
directly connected to 
the IP interface.
The gateway address 
must be administered 
on the Node Names 
screen.The default gateway enables communication with nodes 
on (sub)networks that are different from the (sub)network 
of the IP interface. A default gateway makes use of 
explicit IP routes unnecessary.
If left blank, this node (this IP interface) can communicate 
with nodes on different (sub)networks only if explicit IP 
routes (on the IP Routing screen) are defined — 
communication with nodes on the same (sub)network is 
not affected. With the Gateway Address left blank, you 
can enable communications with individual nodes on 
other (sub)networks by creating host IP routes to them. Or 
you can enable communication with all nodes on a 
different (sub)network by defining a network IP route to 
that (sub)network. You can define a combination of 
network and host IP routes to enable communications to 
all nodes on some (sub)networks and individual nodes on 
other (sub)networks. 
						

							Networking Screens A  Screens Reference
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
250
Net RgnSpecifies the network region assigned to the IP interface. 
Valid Values Usage
1–10
Default is 1.The Region field on the IP Interfaces screen 
allows you to set up segregated groups of 
MedPro resources. This feature can be used in 
a variety of ways. For example, you could use 
regions to allocate specific MedPro boards to 
H.323 trunks and others to stations; or you 
could use regions to avoid traffic over low 
bandwidth or high-latency network links.