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

							DCS over IP Trunk 
441
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
F  IP Trunk Installation and
Administration
4  In the dialog box, enter the NT networking computer names for the systems on 
which alerts should be received. For example: ICB189-85, ICB189-14.
Note:Do not specify the IP address of the system. You must specify the NT 
networking computer name. If another person is responsible for LAN 
administration, consider making this a joint activity.
To set up the receiving machines
1  On each system which received alerts, start the Messenger service. Refer to steps 
1–3 in the first procedure above.
To receive alerts on systems in a different domain (from the IP trunk system that is 
generating the alerts) you must use LMHOST services
1  In Windows NT, go to the c:\winnt\system32\drivers\etc subdirectory.
2  Locate the lmhosts.sam file.
3  Edit this file. Add an entry (row) at the end of the file for each system that will 
receive alerts from this IP trunk application. Each entry (row) contains the IP 
address and NT networking computer name of the receiving system, separated by 
a tab character. Each entry (row) must be followed by a hard return.
Your entries might look like this:
Every machine on which alerts should be received must have an entry (row) in this 
file.
Save the file and copy it to lmhosts (without any extension).
Note:Most text editors, such a NotePad, automatically add an extension to the 
file name when it is saved. You must save the file without an extension, 
or rename it to lmhosts with no file extension.135.17.189.85 ICB189-85
135.17.189.11 ICB189-11
135.17.189.14 ICB189-14 
						

							DCS over IP Trunk F  IP Trunk Installation and
Administration
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
442
Alert types
IP trunk generates alerts when:
•The IP trunk service stops.
•The DSP card does not respond.
•The Dial Plan has changed.
•The access rules have changed.
•The initialization file (its.ini) is missing.
•The dial/routing plan file (gk.ini) is missing.
Testing AlertsYou can test alerts by generating a “dial plan has changed” alert.
To generate a “dial plan has changed” alert:
1  Open Configuration Manager.
2  Click the Dial/Routing Plan tab.
3  Add a new machine entry and click Add.
Viewing error messages
The IP trunk application logs error messages and stores the error messages and 
warnings in the Windows NT Event Viewer.
Note:Set System logs and the Application logs to Overwrite Events as Needed 
for the NT Event Viewer.
To view error messages and warnings in the Windows NT Event Viewer: 
1  Click Start, Programs, Administrative Tools.
2  Click Event Viewer. If necessary, click Log, Application to view the application 
window.
The Event Viewer application window displays with a list of events, the date and 
time the events occurred, and the source, category, and event number.
3  Double-click the event that you want to view.
Details about the selected event display in the Event Detail dialog box.
4  Click Close. 
						

							DCS over IP Trunk 
443
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
F  IP Trunk Installation and
Administration
Troubleshooting IP trunk
If IP calls are not going through, try these basic procedures before contacting an 
authorized Lucent Technologies Service Center for assistance.
Check the IP trunk 
serviceCheck that the IP trunk service is running. 
1  Go to the Windows NT™ Control Panel
2  Double-click on the Services icon to launch the Services Control Manager.
3  Scroll down the list of NT services and make sure the status of IP Trunk service is 
“started.” 
If the service is not running, go to the Services Control Manager. Select IP Trunk 
Service and click the Start button. If the service does not start, note the error message 
displayed on the screen, launch the Windows NT Event Viewer and save the logs 
related to this error. Contact your Lucent representative for further assistance.
After the IP trunk service is started, proceed to the next section.
Check physical 
connectionsCheck the physical connections on: 
~RJ-45 connection to LAN 
~Analog telephone line to external modem
~Video cable from monitor to video connection on switch (if applicable)
~Keyboard/mouse cables (if applicable)
All the vital connections are labeled from the factory on the cable set used with the 
MAPD circuit pack.
Check LAN functionsCheck LAN functions. The following table summarizes the basic tests. Execute the 
DOS test commands in your NT command window.
Network 
Test 
FunctionDOS Test Command 
(type at the DOS prompt 
for your computer) Reasons for Failure
Current 
network 
configuration 
settingsUse ipconfig or ipconfig 
/all 
Settings typed incorrectly. 
Record settings and verify 
settings with network 
administrator
Network 
interface card 
functionalityPing IP loopback address 
(or IP trunk’s own IP 
address)
For example, ping 
127.0.0.1•IP address typed 
incorrectly
•Improper TCP/IP software 
installation
•Duplicate network IP 
address (may happen with 
your own IP address)
1 of 2 
						

							DCS over IP Trunk F  IP Trunk Installation and
Administration
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
444
Maintaining the performance of the IP trunk server
Follow these guidelines to maintain optimal performance on your IP trunk server. 
•Check that the server has at least 64 MB of RAM installed. 
•Check that the C drive has the following virtual memory allocation:
•Initial Size (MB): 50
•Maximum Size (MB): 750
•Check that the performance boost for the foreground application is set to “None.”
•Check that any applications that consume lots of CPU cycles and are not needed 
to run the server, such as screen saver utilities, are not running on the server.
•Check that CDR and/or trace files are not consuming all of the disk space. 
•Is there little or no space available on the C drive? In Configuration Manager, 
Service Logs tab, check that the ”free disk space” threshold parameter is set 
correctly (that is, to a value other than zero). Local 
network 
connectivityPing IP address of default 
gateway (available from 
your LAN administrator)
For example, ping 
192.20.239.1
•IP address typed 
incorrectly
•LAN cable not plugged 
into network card
•Wrong gateway (default 
gateway on different 
subnet)
•Gateway machine is down
Wide Area 
Network 
connectivity
•Ping IP address of known 
machine outside the local 
default gateway (can use 
remote IP trunk 
application or any 
machine)
•Use traceroute to 
determine which 
intermediate gateway is 
malfunctioning
For example, tracert 
192.20.239.1
•Gateway machine error
•Intermediate gateway 
machine errors Network 
Test 
FunctionDOS Test Command 
(type at the DOS prompt 
for your computer) Reasons for Failure
2 of 2 
						

							DCS over IP Trunk 
445
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
F  IP Trunk Installation and
Administration
Configuring Microsoft NetMeeting™ on a PC
After NetMeeting 2.0 is installed, the first time you start it the Configuration Wizard 
prompts you to provide general information. After you provide the general 
information, you must change some audio settings. Procedures for these tasks follow.
Providing general 
information for the 
Configuration WizardThe first time you start NetMeeting, follow these steps.
1  To start NetMeeting, from the Windows Task bar click 
Start>Programs>NetMeeting (default location). 
Note:You may follow a different procedure to start NetMeeting depending on 
how your system is set up.
2  When prompted by the Configuration Wizard, respond as follows: 
•Choose not to log on to a directory server.
•Provide your name, e-mail address, and other information.
•Categorize your information as “For Business Use” or as appropriate.
•Choose LAN or appropriate modem speed, (for example, 28.8.) for network 
connection.
•Click the Starting Recording button and speak into the microphone so that 
NetMeeting can adjust the audio settings. This can also be accomplished using the 
Audio Tuning Wizard from the main user interface. 
						

							DCS over IP Trunk F  IP Trunk Installation and
Administration
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
446
Changing Audio 
SettingsTo change the audio settings so that NetMeeting operates properly with the IP trunk 
application, follow these steps.
1  From the Tools menu choose Options and then select the Audio tab. The Audio 
tab settings appear as shown in Figure 5.
Figure 11. Audio Tab Settings in Options Dialog Box
2  Click the check box for Enable full duplex audio so I can speak while receiving 
audio.
If this option is dimmed, it is not accessible to change. This means your sound 
card is not full duplex. You need to install updated sound card drivers to make the 
card full duplex.
3  Click the check box for Use H.323 gateway and type the IP address of the IP 
trunk in the corresponding field.
4  In the same Options window, select the Calling tab and clear the Refresh directory 
listing check box.
5  Click OK to save your changes and close the Options dialog box. 
						

							DCS over IP Trunk 
447
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
F  IP Trunk Installation and
Administration
Making Calls to the IP 
trunk application from 
NetMeetingBefore you place a call, make sure the following settings are correct.
•If You Have a LAN Connection:
•Make sure the TCP/IP settings are correct on the client machine. To verify this, 
open an NT command window and ping the IP trunk.
•If You Have a Modem Connection:
Make sure you have the correct dial-up networking settings for the remote RAS 
server that you are connecting to. You should be able to get these settings from 
the network administrator of the remote PPP/RAS server. Once the dial-up 
connection is made, you can ping the IP trunk.
To place a call:
1  On the Windows Taskbar, clicking Start>Programs>NetMeeting to start 
NetMeeting. This path may vary depending on the configuration and operating 
system of your computer.
The NetMeeting main window appears. 
						

							DCS over IP Trunk F  IP Trunk Installation and
Administration
Administration for Network Connectivity
CID: 77730 555-233-504 — Issue 1 — April 2000
448
2  In the NetMeeting main window, click the Call icon located in the upper left-hand 
corner of the tool bar. 
The New Call dialog box appears.
3  In the Address box, type the phone number you want to call.
Type the number exactly as you dial it from a regular phone. Do not use spaces or 
hyphens between numbers.
If your IP trunk application is configured to require an access code, verify the 
correct dialing sequence with the switch administrator.
4  In the Call using box, select H.323 Gateway from the pull-down menu.
5  Click the Call button to dial and initiate the call.
6  Use the microphone and headphones to talk to the person on the receiving end.
Placing a test 
telephone callAfter starting the IP Trunk service, place a test telephone call to the remote switch.
Setting up alerts on IP 
trunksWhenever something happens on IP trunks that might affect service quality, 
Windows NT™ displays an alert in a popup window. You can select the IP address 
for the alert messages and notify a computer other than the IP Trunk display screen. 
NT alerts allow you to monitor IP Trunk service on one or more switches.
Viewing error 
messagesThe IP Trunk application logs Error Messages and will store the error messages and 
warnings in the Windows NT Event Viewer.
Note:Log settings for the NT Event Viewer should be set to Overwrite Events 
as Needed for both the System and the Application logs.
Troubleshooting IP 
Tru nkIf IP calls are not going through, try these basic procedures before contacting an 
authorized Lucent Technologies Service Center for assistance.
•Check the IP Trunk service
•Check physical connections
•Check LAN functions 
						

							449
Administration for Network Connectivity
555-233-504— Issue 1 — April 2000 CID: 77730
IP Trunk Worksheets 
IP Trunk Worksheets
Worksheet 1: Two Site Solution: Both DEFINITY T1
SITE 1  SITE 2 
Field 
CodeField Name Field Value1A International Access Code
1B Country Code
1C Long Distance Access Code
1D Area Code
1E Exchange
1F ARS Feature Access Code
1G IP Address
1H PBX-to-IP trunk Route Pattern 
Number
1I PBX-to-IP Trunk Group Num-
ber
1J PSTN Trunk Group Number
(for PSTN fallback)
Field 
CodeField Name Field Value2A International Access Code
2B Country Code
2C Long Distance Access Code
2D Area Code
2E Exchange
2F ARS Feature Access Code
2G IP Address
2H PBX-to-IP trunk Route Pattern 
Number
2I PBX-to-IP Trunk Group Num-
ber
2J PSTN Trunk Group Number
(for PSTN fallback) 
						

							Administration for Network Connectivity
CID: 77730 555-233-504— Issue 1 — April 2000
450
   IP Trunk Worksheets
Worksheet 2: Two Site Solution: DEFINITY T1 Administration
(No Off-Premise Dialing at Remote Site Only)
SITE 1*Set this value to the total length of the number the user will dial, not 
including ARS feature access code (for example, 9). 
SITE 2 *Set this value to the total length of the number the user will dial, not 
including ARS feature access code (for example, 9). 
PBX Admin If Sites 1 and 2 are in:
Add ARS 
analysis entry 
with:Fill in with 
your actual 
valuesDifferent 
CountrySame 
country, 
different 
area codeSame 
area 
code
Dialed String 1A2B2D2E 1C2D2E 2E
Total Mn ***
Total Mx ***
Rte Pat 1H1H1H
Create route pattern number  with:
First route Second routeGroup No: 1I Group No: 1J
No. Del Digits: blank No. Del Digits: blank
Inserted Digits: blank Inserted Digits: blank
PBX Admin If Sites 1 and 2 are in:
Add ARS 
analysis entry 
with:Fill in with 
your actual 
valuesDifferent 
CountrySame 
country, 
different 
area codeSame 
area 
code
Dialed String 2A1B1D1E 2C1D1E 1E
Total Mn ***
Total Mx ***
Rte Pat 2H2H2H
Create route pattern number  with:
First route Second routeGroup No: 2I Group No: 2J
No. Del Digits: blank No. Del Digits: blank
Inserted Digits: blank Inserted Digits: blank