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

							31Administration for Network Connectivity555-233-504 — Issue 1 — April 2000  CID: 77730
2  H.323 Trunks
This chapter describes how to set up and perform initial administration of IP Trunks between 
DEFINITY ECS switches and between DEFINITY and non-DEFINITY switches that support the 
H.323 V2 signaling protocols. The IP trunk connections described in this chapter use the TN802B 
circuit pack in the MEDPRO mode. See Appendix F for administration of trunk connections that 
use the TN802 or TN802B in the IP Trunk mode.
Overview
This section provides a summary of DEFINIY IP Solutions for DEFINITY ECS Release 8.2.
IP Solutions 
DEFINITY ECS IP Solutions provide TCP/IP connectivity for two types of trunks and three types of IP 
Softphones. On DEFINITY ECS, 
IP Solutions use the TN802B IP Interface assembly for voice processing and the 
TN799B C-LAN for signaling. The TN802B IP Interface includes a Windows NT server that resides on the 
TN802B circuit pack inside the DEFINITY ECS.
The TN802B IP Interface, introduced in Release 8, can be administered to operates in either the MedPro mode 
(for H.323-compliant ISDN PRI-equivalent trunk connections) or IP Trunk mode (for DS1-emulation 
connections). It will typically be used in the MedPro mode. The IP Trunk mode is provided for compatibility 
with existing R7 IP Trunk connections.
The TN802 IP-Interface introduced in Release 7, which operates only in the IP Trunk mode, can be upgraded via 
firmware download to the TN802B. 
The following table lists the IP Solutions configurations and the circuit packs and software used with each.
IP SolutionsCircuit Pack Requirements Software 
Requirements
R7 R8
TrunksH.323 Trunk–TN802B in medpro mode
with TN799B–
IP Trunk TN802TN802B in ip trunk mode 
with TN799B–
IP 
SoftphonesRoad-warrior 
application–TN802B in medpro mode
with TN799BDEFINITY IP Softphone,
Microsoft NetMeeting
*
* The IP Softphones should work with other audio applications that are fully H.323 v2-compliant.
DEFINITY IP Solutions was developed and tested with Microsoft NetMeeting.
Telecommuter 
application– TN799B DEFINITY IP Softphone
CentreVu IP Agent – TN799B DEFINITY IP Softphone 
						

							Overview 2  H.323 Trunks
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
32
IP-Connected Trunks
IP-connected trunks allow trunk groups to be defined as ISDN-PRI-equivalent tie 
lines between switches over an IP network.
Trunks using IP connectivity provide cost-reduction and simplified management. 
Benefits include a reduction in long distance voice and fax expenses, facilitation of 
global communications, full-function networks with data and voice convergence, and 
network optimization by using the existing network resources. 
H.323 TrunkThe TN802B IP Interface in Medpro mode enables H.323 trunk service using IP 
connectivity between two DEFINITY ECS systems. H.323 trunk groups can be 
configured as DEFINITY-specific tie trunks supporting ISDN trunk features such as 
DCS+ and QSIG, or as generic tie trunks permitting interconnection with other 
vendors’ H.323 v2-compliant switches, or as direct-inward-dial (DID) type of 
“public” trunk providing access to the switch for unregistered users. A variety of 
signaling options can be chosen by the system administrator.
IP TrunkThe IP Trunk mode (of the TN802B IP Interface) will typically be chosen for 
interoperability with existing TN802 (as opposed to the TN802B) IP Interface circuit 
packs. IP Trunk mode can be used only between two DEFINITY switches. Each IP 
Interface circuit pack in IP Trunk mode provides a basic twelve-port package that can 
be expanded up to a total of 30 ports.
IP Softphones
DEFINITY IP Softphones operate on a PC equipped with Microsoft Windows 
95/98/NT and with TCP/IP connectivity to DEFINITY ECS. DEFINITY IP Solutions 
supports three IP Softphone configurations:
•Road-warrior application of IP Softphone — a PC running the DEFINITY IP 
Softphone application and an H.323v2-compliant audio application, with a single 
IP connection to a DEFINITY server.
•Telecommuter application of IP Softphone — a PC running the DEFINITY IP 
Softphone application with an IP connection to the DEFINITY server, and a 
standard telephone with a separate PSTN connection to the DEFINITY server.
•CentreVu IP Agent — same as the Dual-Connection IP Softphone with the 
addition of call-center agent features that enable agents to work at home.
The DEFINITY IP Softphone can also operate in a “native H.323” mode, which is a 
PC-based single phone with limited features. 
Documentation on how to set up and use the IP Softphones is included on the 
CD-ROM containing the IP Softphone software. The documentation includes a 
Getting Started quick reference, an overview and troubleshooting document, and 
context-sensitive help integrated with the softphone software.
Procedures for administering the DEFINITY ECS server to support IP Softphones are 
given in DEFINITY ECS R8.2 Administrator’s Guide, 555-233-506. 
						

							H.323 Trunk Administration 
33
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
2  H.323 Trunks
H.323 Trunk Administration
This section describes the administration steps needed to setup H.323 trunks. The first subsection covers the 
enabling administration that needs to be in place before the trunk administration can be done. The second 
subsection gives a summary of the H.323 trunk administration and the last subsection gives the detailed steps. 
The screens used for this administration are described in detail in Appendix A, Screens Reference.
Screen fields not mentioned here are administered as in previous releases. 
Enabling Administration
Before you can administer an H.323 trunk, a few customer options and circuit pack parameters need to be 
properly set. In addition, there are some optional maintenance and IP parameters that can be administered. These 
enabling settings are summarized here.
Optional Features 
(System Parameters 
Customer Options)The Optional Features screen must be administered by the init login. Open the screen 
with the change command (ch sys cu) and set the following fields:
page 1
•
G3 Version = V8 
•Maximum H.323 Trunks = number purchased; must be greater than 0.
page 3
•
H.323 Trunks? = y
•ISDN-PRI? = y
Circuit PackThe C-LAN and IP Interface assembly circuit packs must be administered on the 
Circuit Pack screen. Open the Circuit Pack screen with the change command (ch ci) 
and enter the board codes in available port slots:
C-LAN
•
Code = TN799
•Sfx = B
•Name = C-LAN
IP Interface assembly — enter in a slot with at least two empty slot before it
•
Code = TN802
•Sfx = B
•Name = MAPD Board {entered automatically by system}
The two slots immediately before this slot are automatically populated as follows:
•Code = DSMAPD {displays automatically}
Change DSMAPD to MEDPRO {the IP Interface board defaults to the IP Trunk 
mode, which is specified by the DSMAPD in this field. Changing this field to 
MEDPRO changes the board’s mode to MEDPRO}
•Sfx = {blank}
•Name = Reserved - IP {displays automatically} 
						

							H.323 Trunk Administration 2  H.323 Trunks
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
34
Maintenance-Related 
System ParametersFour parameters on the Maintenance-Related System Parameters screen set threshold 
values for network performance: 
page 4
•
Roundtrip Propagation Delay (sec)  High: 800_  Low: 400_
•Packet Loss (%)  High: 40__ Low: 15__
•Ping Test Interval (sec): 20 
•Pings per Measurement Interval: 10 
These parameters have no effect unless the bypass function is activated on the 
Signaling Group screen. If the bypass function is activated for a signaling group, 
ongoing measurements of network activity collected by the system are compared with 
these values. If the values of these parameters are exceeded by the current 
measurements, the bypass function terminates further use of the network path 
associated with the signaling group. The following actions are taken when thresholds 
are exceeded:
•existing calls are maintained
•incoming calls are allowed
•outgoing calls are blocked on this signaling group; if so administered, blocked 
calls are diverted to alternate routes (either IP or circuits) as determined by the 
administered routing patterns
You can use the default values set for these parameters, or you can change them to fit 
the needs of your network. The Maintenance-Related System Parameters screen can 
be administered by the init, inads, or craft logins. Open the screen with the change 
command (ch sys ma).
IP ParametersThe IP Media Parameters screen allows you to specify the type of codec used for 
voice encoding and companding (compression/decompression). The main difference 
between codecs is in the compression algorithm used: some codecs compress the 
voice data more than others. A greater degree of compression results in lower 
bandwidth requirements on the network, but may also introduce transmission delays 
and lower voice quality.
The default codec is set for G711. The G711 provides the highest voice quality 
because it does the least amount of compression, but it uses the most bandwidth. The 
G711 default setting can be changed to one of four other codecs if the G711 does not 
meet your desired voice-quality/bandwidth tradeoff specification. Also, if the far-end 
switch is a not a DEFINTIY ECS, you may need to change the codec to match one 
that is supported by that switch.
The order in which the codecs are listed on this screen is the order of preference of 
usage. A trunk call between two DEFINITY switches will be set up to use the first 
common codec listed on the two IP Parameters screens.
NOTE: The codec ordering 
must be the same on DEFINITY switches at 
both ends of an H.323 trunk connection. The 
set of codecs listed need 
not be the same, but the 
order of the listed codecs must be the same. 
						

							H.323 Trunk Administration 
35
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
2  H.323 Trunks
You can also use the Audio IP port number range field to specify a block of port 
numbers to be used for audio connections. Then, if your network is equipped with the 
appropriate data filtering devices, audio data can be segregated from other data traffic 
to improve quality of service.
Open the screen with the change command (ch ip-p) and set the following fields:
•Codec type = {enter as many of the following types as supported by this switch, in 
the preferred order of usage — G711A, G711Mu, G723-6.3k, G723-5.3k, 
G.729A}. Refer to the following table of bandwidth requirements to decide which 
codecs to administer:
•Audio IP port number range = 
UDP Port Range 
Min: 2048 
Max: 65535
The G711 codecs use either an A-law or Mu-law companding algorithm. The Mu-law 
algorithm is used in the U.S. and Japan; the A-law is typically used in other countries.
Best Service RoutingThe call center Best Service Routing (BSR) feature can be implemented using H.323 
trunks. You can use H.323 trunks for just the polling function or for both the polling 
and interflow functions. Since polling requires only a small amount of data exchange, 
the additional network traffic is insignificant. However, the interflow function 
requires a significant amount of bandwidth to carry the voice data. Depending on the 
other uses of the LAN/WAN and its overall utilization rate, the voice quality could be 
degraded to unacceptable levels.
Lucent recommends that if H.323 trunks are used for BSR interflow, this traffic 
should be routed to a low-occupancy or unshared LAN/WAN segment. Alternatively, 
you might want to route internal interflow traffic (which may have lower 
quality-of-service requirements) over H.323 trunks and route customer interflow 
traffic over circuit-switched tie trunks.Codec Bandwidth Requirement
G711 A-law @ 64Kbps 117.6 Kbps
G711 Mu-law @ 64Kbps 117.6 Kbps
G723 @ 6.3Kbps 31.1 Kbps
G723 @ 5.3Kbps 29.6 Kbps
G729A @ 8Kbps 33.6 Kbps 
						

							H.323 Trunk Administration 2  H.323 Trunks
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
36
H.323 Trunk Administration — Task Summary
After the enabling administration is complete, you can administer the H.323 IP trunks. The screens and fields 
that need to be administered are listed below. 
NOTE:  This is only a list of screens and the fields that need to be 
administered. The values that need to be entered in these fields are 
described in the next section.
Node namesA node name and IP address must be entered on the Node Names screen for each 
C-LAN and IP Interface board on the local switch. For each far-end node that the 
H.323 trunks on the local switch will connect to, a node name and IP address must be 
entered for the far-end gatekeeper, which is a C-LAN board if the far-end is a 
DEFINITY switch. Enter values in these fields:
~Node Name
~IP Address
IP InterfacesEach DEFINITY switch in an IP network has one IP Interfaces screen. One line on 
this screen must be administered for each C-LAN and each IP Interface board. Enter 
values in these fields:
~Network regions are interconnected? 
~Enable
~Ty p e
~Slot
~Code
~Sfx
~Node Name
~Subnet Mask
~Default Gateway Address 
~Region
Ethernet Data ModuleA data module screen, type ethernet, must be administered for each C-LAN board on 
the switch. Enter values in these fields:
~Ty p e
~Port
~Link
~Name
~Network uses 1’s for broadcast address? 
						

							H.323 Trunk Administration 
37
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
2  H.323 Trunks
Signaling GroupEach H.323 trunk must be assigned to a signaling group. Enter values in these fields:
page 1
~
Group Type
~Trunk Group for Channel Selection 
~Near-end Node Name
~Near-end Listen Port 
~Far-end Node Name (Optional)
~Far-end Listen Port (Optional
~LRQ Required?
~Calls Share IP Signaling Connection?
~Bypass If IP Threshold Exceeded?
Page 2 — Administered NCA TSC Assignment
NCA TSCs need to be administered only if this signaling group is to be used for DCS, 
AUDIX, MASI, or as Gateway. Administration of TSCs is the same as in previous 
releases.
Trunk GroupEach H.323 trunk must be assigned to a trunk group, which is assigned to a signaling 
group. Enter values in these fields:
page 1
~
Group Type
~Carrier Medium
~Service Type
~Codeset to Send Display
~TestCall ITC
~TestCall BCC
page 2
~
Used for DCS?
~PBX ID
~DCS Signaling
page 4—trunk group members assignment
~
Port
~Code
~Name 
~Night
~Sig Grp 
						

							H.323 Trunk Administration 2  H.323 Trunks
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
38
IP Media ParametersEach DEFINITY switch in an IP network has one IP Media Parameters screen. Use 
this screen to enter:
~the types of codecs (for audio processing) available on this switch
~the preferred order of use of the codec types
~the range of port numbers available for audio connections
Network RegionsThe Region field on the IP Interfaces screen allows you to set up segregated groups of 
C-LAN and IP Interface (Medpro) resources. This feature can be used in a variety of 
ways. For example, you could use regions to allocate specific C-LAN and IP Interface 
boards to H.323 trunks and others to stations; or you could use regions to avoid 
multimedia traffic over low bandwidth or high-latency network links.
H.323 Trunk Administration — Task Detail
This section describes the tasks that need to be completed to administer an H.323 trunk. Sample values are used 
to populate the fields to show the relationships between the screens and fields.
Task 1 — Assign Node Names
This task assigns node names and IP addresses to each node in the network that this 
switch communicates with via IP connections. A Node Names screen must be 
administered on each DEFINITY switch in an IP network.
A node is defined as any of the following — a C-LAN ethernet or ppp port, a bridge 
or router, a CMS ethernet port, or an Intuity AUDIX or other MSA 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 must be entered on pages 2–6.
For H.323 connections, each MedPro ethernet port (IP interface) on the local switch 
only must also be assigned a node name and IP address on this form.
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 switches, routers, and CMS starting on page 2. 
						

							H.323 Trunk Administration 
39
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
2  H.323 Trunks
Begin
Task 1 Steps
> Open Node Names screen — enter ch node-n
> Go to page 2 of the screen
> Enter values.
> Submit the screen
End
change node-names  Page 2 of 6 
NODE NAMES 
Name  IP Address  Name  IP Address
clan-a1
______ 192.168.10_.31_ ___________ ___.___.___.___
clan-a2
______ 192.168.20_.31_ ___________ ___.___.___.___
default 0 .0 .0 .0  ___________ ___.___.___.___
medpro-a1
___192.168.10_.81_ ___________ ___.___.___.___
medpro-a2
___192.168.20_.81_ ___________ ___.___.___.___
medpro-a3___192.168.10_.82_ ___________ ___.___.___.___
medpro-b1___192.168.10_.83_ ___________ ___.___.___.___
___
___.___.___.___ ___________ ___.___.___.___
Field Conditions/Comments
Name Enter unique node names for:
•Each C-LAN ethernet port on the network
•Each IP-Interface (Medpro) board on the local switch.
The default node name and IP address is used to set up a default 
gateway, if desired. This entry is automatically present on the Node 
Names screen and cannot be removed.
When the Node Names screen is saved, the system automatically 
alphabetizes the entries by node name.
IP Address Enter a unique IP addresses for each node named in the previous 
field. 
						

							H.323 Trunk Administration 2  H.323 Trunks
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
40
Task 2 — Define IP Interfaces
The IP interface for each C-LAN and MedPro board on the switch must be defined on 
the IP Interfaces form. Each DEFINITY switch in an IP network has one IP Interfaces 
form.
Begin
Task 2 Steps
> Open IP Interfaces form — enter  ch ip-i
> Enter values
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  medpro-a1 255.255.255.0   192.168.10 .100 1
y  MEDPRO 01A16 TN802 B  medpro-a2 255.255.255.0   192.168.20 .100 1
y   C-LAN  01A09 TN799 B  clan-a2  255.255.255.0   192.168.20 .100 2
   y  MEDPRO 01B13 TN802 B  medpro-a3 255.255.255.0   192.168.10 .100 2
y   MEDPRO 01B09 TN802 B  medpro-b1  255.255.255.0   192.168.10 .100 2
   n  255.255.255.0      .   .   . 
Field Conditions/Comments
Inter-region IP 
connectivity 
allowed?Enter y to allow IP endpoints (phones and trunks) to use 
MedPro resources administered in regions that are 
different from the endpoints’ regions.
Enable Eth Pt The 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.
Type Enter c-lan or medpro.
Slot Enter the slot location for the circuit pack.
Code Display only. This field is automatically populated with 
TN799 for C-LAN or TN802 for MedPro.
Sfx Display only. This field is automatically populated with B 
for the TN802 and TN799.
Node name Enter the unique node name for the IP interface. The node 
name entered here must already be administered on the 
Node Names screen
1 of 2