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

							Troubleshooting IP Solutions 
51
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
2  H.323 Trunks
The solution to this problem is to set up a separate signaling group for each trunk 
group, as shown in Figure 3. More generally, set up a separate signaling group for 
each set of trunk groups that have common attributes.
Figure 2. Shared signaling group
Figure 3. Separate signaling group
No MedPro resources 
available
If two switches are connected via an H.323 trunk and all MedPro resources are in use 
on the call-destination switch when a call is made, the call will fail even when a 2nd 
preference is administered in the routing pattern on the source switch. This can be 
avoided by setting the first preference look ahead routing (LAR) to “next” in the 
routing pattern.
C-LAN sharingDepending on the network configuration, a single C-LAN board has the capacity to 
handle the signaling for multiple applications. For example, the call center Call 
Management System (CMS) would typically use a small portion of a C-LAN’s 
capacity so the same C-LAN could easily handle the signaling for other IP endpoints 
at the same time. There are many variables that affect the number of C-LAN and 
TN802B (MedPro) circuit packs that you will need for your network configuration. 
To accurately estimate the C-LAN and MedPro resources needed, a network 
configuration tool is available from Lucent. See Appendix D, Capacities and 
Performance for a summary of this tool.
Traffic congestion is potentially a problem when multiple IP Interfaces (such as 
C-LAN, MedPro, PCs, CMS) share a network and some of the endpoints are heavily 
used. This problem can be minimized by using a switched network and assigning 
endpoints (such as CMS) to a separate LAN/WAN segment.
TGA1
TGA2TGB2TGB1
Switch A
Switch B SGA1SGB1
Trunk Group
for Channel
Selection =
TGB1
Private NW
Public NW
TGA1
TGA2TGB2TGB1
Switch A
Switch B SGA1
SGA2
SGB1
Trunk Group
for Channel
Selection =
TGB1
SGB2
Trunk Group
for Channel
Selection =
TGB2
Private NW
Public NW 
						

							Troubleshooting IP Solutions 2  H.323 Trunks
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
52
IP Softphone Problem Solving
Codecs used with 
NetmeetingVoice quality for the road-warrior application of DEFINITY IP softphone will vary 
depending on several factors. Poor voice quality can be caused by the use of the 
high-compression codecs (G.723 or G.729) in situations where the low-compression 
codec (G.711) should be used. This can happen unexpectedly when using NetMeeting 
— when the G.711 is set as the preferred codec on the switch, NetMeeting may fail to 
use it. Since there is no way to monitor which codec is being used, the only way to 
determine that this is the problem is to disable all but the G.711 codecs. Then, if calls 
no longer work, it can be concluded that NetMeeting is failing to use the G.711. The 
solution to this problem is to reinstall NetMeeting.
Telecommuter use of 
phone linesThe telecommuter application of the IP Softphone requires the use of two phone lines: 
one for the IP connection to DEFINITY, which is used for softphone registration and 
call signaling, and the other for a PSTN connection, which DEFINITY uses as a 
callback number to establish the voice path. How you allocate your phone lines to 
these two functions may make a difference.
For example, assume that you have telephone services provided by the local phone 
company, such as voice mail, associated with one of your lines and not the other. In 
this case, you should use the line with the services to make the initial IP connection to 
register the softphone and use the line without the services as the POTS callback for 
the voice path. Otherwise, there could be undesirable interactions between the 
softphone and the local services. For example, if your telecommuter application is 
registered and you were using your POTS callback line for a personal call when a 
business associate dialed your work extension, the business associate would hear your 
home voice mail message.
NetMeeting drops 
unanswered callsFor calls made to a NetMeeting softphone, if the call is not answered or if coverage is 
not administered, after about 5 rings NetMeeting drops the call and the station stops 
ringing but the caller continues to hear ringback. To avoid this situation, make sure 
that coverage is administered for the NetMeeting softphone.
NetMeeting ignores 
out-of-band tonesNetMeeting ignores any H.323 digits received out-of-band, so it never hears DTMF 
from DEFINITY, which always strips DTMF from the audio path and plays it 
out-of-band with H.323.
For example, if you are on a call on a NetMeeting softphone and the calling party 
presses a number or character on their keypad, you will not hear the tone. 
						

							53Administration for Network Connectivity555-233-504 — Issue 1 — April 2000  CID: 77730
3 C-LAN Administration
This chapter describes how to administer TCP/IP data connections between DEFINITY ECS 
switches using the C-LAN circuit pack. This chapter does not cover the use of the IP Interface 
circuit pack for H.323 connectivity.
Overview
This chapter provides an update of the R7 administration procedures, which were 
described in Chapter 2, “DCS Administration,” of issue 1 of this book. The R8 
changes described in this chapter are:
•R8 administration procedures using the changed ethernet Data Module screen and 
the new IP Interfaces screen
•use of IP Routes, which, in some cases, are not needed in R8 when they were 
needed in R7
•additional procedures for administering CMS and Intuity AUDIX
TCP/IP connections (ppp or ethernet) require DEFINITY ECS Release 7 or later 
hardware and software. ISDN and BX.25 connections are supported on switches 
upgrading to R8 and pre-R7 switches can be connected to R8 switches via ISDN or 
BX.25. However, new systems are not sold with X.25 connections. Therefore, all 
switches in the configuration are assumed to be upgraded to release R7 or later.
Supported Switches and Adjuncts
Csi-model switches cannot have X.25 connections. New R8si and R8r switches 
cannot have new X.25 connections but pre-R7 switches with X.25 connections can be 
upgraded to R8 and keep the X.25 connections.
The vs model of DEFINITY ECS cannot be upgraded to R8 — R6.3 is the last release 
supported for the vs model. However, pre-R7 releases of the vs model will be 
supported (via X.25 and ISDN, not TCP/IP) in customer networks that include R8 
versions of the csi, si, and r models.
The call management system (CMS) and Intuity adjuncts can be connected to the 
DEFINITY ECS R8csi with an ethernet connection and to the si and r models with 
either an ethernet or Bx.25 connection. Procedures for administering these 
connections are not covered in this book. They are documented in CentreVu CMS 
Switch Connections and Administration (585-215-876) for CMS and in Intuity 
Messaging Solutions, LAN Integration with DEFINITY ECS (585-313-602) for 
Intuity. CMS administration is covered in Centre CMS Software Installation and 
Setup, 585-215-866. 
						

							Overview 3  C-LAN Administration
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
54
Checklist for Prerequisite Administration
This is a checklist of things that need to be completed before you can proceed with the 
network administration tasks. Review this checklist before starting the administration 
tasks. 
4Checklist Item
The prerequisite administration needed depends on whether the system is new or 
is being upgraded from an R7 or pre-R7 system to R8. Use the following map to 
determine which steps to perform.
For more information about the checklist items, refer to Appendix A or the 
appropriate upgrades book in References, page 56.
UPGRADES ONLY: Steps 1–6 apply only to systems being upgraded to R8 
from an R7 or pre-R7 release. For new systems, skip to step 7.
1  Save translations on customer flash card (csi or si models) or tape (r 
model). For R7 systems, skip to step 5.
2  This step is for the si model only. It preserves ISDN-PRI connections, 
which (for R7 and later) are carried on the NetPkt circuit pack instead of 
the PI or PACCON circuit packs. ISDN-PRI connections are preserved 
transparently on the csi and r models.
If:
the si switch has existing ISDN-PRI connections that the customer wants to 
keep, complete the following steps:
~De-administer the ISDN-PRI connections:
•busy the ISDN links
•remove comm-interface links of type ISDN
•remove comm-interface processor channels that use ISDN links
•remove data modules using those links
~Save translations on a “working” flash card
Otherwise:
skip to step 3.
1 of 3
1 2 3  4 5 6 7 
New
R7
Pre-R7 si with
Other Pre-R7 ISDN connections
to be preserved 
						

							Overview 
55
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
3  C-LAN Administration
3  Remove old circuit packs:
~Turn off the power.
~For the csi model, remove the Processor (TN798) circuit pack (Don’t 
remove the processor circuit pack if it is a TN798B).
~For the si model, remove the Processor (TN790), PACCON (TN778), 
and NETCON (TN777) circuit packs. If there are X.25 connections 
that the customer wants to keep, leave the PI (TN765) circuit pack in 
the switch; otherwise remove it.
~For the r model, if there are X.25 connections that the customer wants 
to keep, leave the PGATE (TN755) circuit pack in the switch; 
otherwise, remove it.
4  Install new circuit packs on all switches upgrading from a pre-R7 
software load to R8:
~For csi models: install the TN798B (processor) and TN799B 
(C-LAN) circuit packs.
~For si models: install the TN790B (processor), TN794 (NetPkt), and 
TN799B (C-LAN) circuit packs. For any PPN or EPN that will be 
carrying packet data, replace the TN776 (Expansion Interface) with 
the TN570B or TN570C circuit pack. 
~For r models: install TN799B (C-LAN.)
The C-LAN circuit pack is required for TCP/IP (ppp and ethernet) 
connections. In all cases, the R8 software will run without the TN799B 
(C-LAN) circuit pack; all other new circuit packs are required for R8.
5   Install the R8.1 Software on all switches upgrading to R8.1
6  Copy translations from translations flash card or tape (G3r). Use the 
“working” flash card if step 3 was performed.
NEW and UPGRADE Systems — the following items apply to both new systems 
and systems being upgraded to R8 from a previous release. For more information 
about the checklist item, refer to the appropriate installation book in References, 
page 56.
 
7   Established physical connections at each node.
8  Set software version on the System Parameters Customer Options form.
General Administration for new installations — the following translations should 
already be in place for existing systems and usually should not need to be changed 
for an upgrade to R8 unless new nodes are being added to the network. Refer to 
appendix A for more information about these tasks.
9  DS1 circuit packs administered 4Checklist Item
2 of 3 
						

							Overview 3  C-LAN Administration
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
56
Configurations
The task descriptions are presented in six relatively simple configurations. Each 
configuration describes how to administer either a 2-switch connection or a 3-switch 
gateway connection. The procedures for administering these configurations can be 
used either individually or in groups as “building blocks” for constructing most 
networks involving DEFINITY ECS R8 and pre-R7 switches.
The following table lists the configurations described in this chapter. 
The first 2 configurations are simple 2-switch networks. The next two are 3-switch 
networks with Switch 1 serving as a gateway between different signaling types for 
connection 1 and connection 2. The last two configurations are ppp–ethernet 
networks; 5B, is the same as 5A except the Switch 1 has two C-LAN boards instead 
of one.
10  Signaling group administered
~page 1 — Trunk board address and Interface ID
~Page 2 — Administered NCA TSC assignment
11  Synchronization plan administered
12  Trunk groups assigned
13  Dial plan administered
14  Uniform dial plan administered
15  AAR analysis administered
16  Route pattern administered
17  Hunt groups assigned 4Checklist Item
3 of 3
Config-
urationSwitch
2Connection 
1Switch
1Connection 
2Switch
3Page
1 R7si ppp R7rpage 60
2 R7csi ethernet R7r 
(+CMS)page 73
3 si bx.25 R7r ethernet R7sipage 99
4 csi isdn R7si ppp R7csipage 124
5A R7csi ppp R7r ethernet R7sipage 146
5B R7csi ppp R7r
(2 C-LAN 
boards)ethernet R7sipage 171 
						

							Overview 
57
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
3  C-LAN Administration
TCP/IP connections (ppp or ethernet) require DEFINITY ECS Release 7 or later 
hardware and software. ISDN and BX.25 connections are supported on switches 
upgrading to R8 and pre-R7 switches can be connected to R8 switches via ISDN or 
BX.25. However, new systems will not be sold with X.25 connections. Therefore, all 
switches in the five configurations are assumed to be upgraded to release R7 or later 
except the si connected via BX.25 and the csi connected via ISDN in configurations 3 
and 4 — these 2 switches could be either R7 or pre-R7 versions.
Organization of this chapter
The descriptions of the configurations have a common format. Each configuration 
section has the following subsections:
•Configuration overview
•Task summary
•Checklist of prerequisite tasks
•Configuration diagram
•Administration tasks
The subsections are described below.
Configuration OverviewEach of the configuration sections begins with a brief description of the network 
represented by the configuration. This section includes a high-level diagram and a 
description of the switches and their connections for each node in the network.
Task SummaryLists the tasks that need to be performed to administer this configuration.
1  Review checklist
2  Assign node names
3  Assign links
4  Assign processor channels
Procedures for completing each of these tasks are described in detail following this 
summary.
Configuration DiagramA detailed diagram of the configuration is shown after the task summary. The 
diagram is in two parts — one part showing the software-defined connections and the 
other part showing the hardware connections. The diagram shows many of the 
parameters that are entered on the administration screens
. 
						

							Overview 3  C-LAN Administration
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
58
In the hardware part of the diagram, the paths for voice and signaling data are shown 
by dashed or dotted lines. The data for voice and call-setup signaling usually takes a 
different path through the switch hardware from the path for DCS and ISDN signaling 
data. These two types of data are distinguished in the hardware part of the diagram by 
the following convention.
A dashed line,  , indicates voice and call-setup data. 
A dotted line,   , indicates DCS signaling data.
In the software part of the diagram, the virtual path from processor to processor 
between two nodes is traced by dashed lines. The path starts at a processor channel on 
one node, through the link/interface-channels on each node, to the processor channel 
on the connected node.
Administration tasksThis section gives the detailed steps for administering the connections between 
switches. For each configuration, there are several tasks and each task consists of 
several steps. All of the tasks needed to administer all the nodes in the network are 
included in each configuration.
The administration task sections list the steps for completing a screen (or form) and 
show a representation of the filled-in screen. Many of the field values shown in the 
screens are examples — you will use different values that are appropriate for your 
system. Information about the fields and their values — when and why different 
values are used — is given for each screen. More detailed information about the 
screens and their fields is given in Appendix A.
Supported Switches and Adjuncts
Csi-model switches cannot have X.25 connections. New R8si and R8r switches 
cannot have new X.25 connections but pre-R7 switches with X.25 connections can be 
upgraded to R8 and keep the X.25 connections.
The vs model of DEFINITY ECS cannot be upgraded to R8 — R6.3 is the last release 
supported for the vs model. However, pre-R7 releases of the vs model will be 
supported (via X.25 and ISDN, not TCP/IP) in customer networks that include R8 
versions of the csi, si, and r models.
The call management system (CMS) and Intuity adjuncts can be connected to the 
DEFINITY ECS R7csi with an ethernet connection and to the si and r models with 
either an ethernet or Bx.25 connection. Procedures for administering these 
connections are not covered in this book. They are documented in CentreVu CMS 
Switch Connections and Administration (585-215-876) for CMS and in Intuity 
Messaging Solutions, LAN Integration with DEFINITY ECS (585-313-602) for 
Intuity. CMS administration is covered in Centre CMS Software Installation and 
Setup, 585-215-866. 
						

							Overview 
59
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
3  C-LAN Administration
Intuity AUDIX LAN Setup Summary
The following list summarizes the steps for setting up an Intuity AUDIX on a LAN.
1  Assign node name and IP address
2  Assign UNIX machine name, IP address, configure LAN card. 
“Networking Administration, TCP/IP Administration”
3  Assign country and switch type
“Switch Interface Administration, Switch Selection”
4  Assign extension length, Host Switch Number (switch node from dial plan), 
Audix Number, Switch Number IP address of the switch, and TCP Port.
“Switch Interface Administration, Call Data Interface Administration, Switch 
Link Administration.”
5  Reboot the Intuity AUDIX
“Customer/Services Administration, System management, System Control, 
Shutdown System.”
6  Set up the DCS Network Time Zones
7  “Audix Administration, change switch-time-zone.”
CMS LAN Setup Summary
The following list summarizes the steps for setting up a CMS server.
1  Edit the /etc/hosts file to add switch names and IP addresses
2  Set up a second NIC
3  Add a default router
4  Set up the local/remote port
5  Choose between x.25 and TCP/IP signaling
6  For X.25, define which physical port is used on CMS
7  For TCP/IP, assign the switch host name or IP address and TCP port number 
						

							Configuration 1: R8r  R8si 3  C-LAN Administration
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
60
Configuration 1: R8r   R8si 
Configuration 1 is a ppp connection between a DEFINITY ECS R8r and a 
DEFINITY ECS R8si switch in a DCS network.
 
Task Summary
Complete the following tasks for Switch 1 and Switch 2:
1  Review prerequisite administration checklist
2  NODE 1 administration
 a  Assign node names
 b  Assign link (via a data module) to node-2
 c  Assign processor channels
3  NODE 2 administration
 a  Assign node names
 b  Assign link to (via a data module) node-1
 c  Assign processor channels
4  Enable links and processor channels
Switch 1Switch 2
ppp
     R8si DEFINITY ECS  DEFINITY
ECS R8r
node-2 node-1DS1
C-LAN
DS1
C-LAN