3Com Corporation reserves the right to revise this documentation and to make changes in content from time to time
without obligation on the part of 3Com Corporation to provide notification of such revision or change.
3Com Corporation provides this documentation without warranty of any kind, either implied or expressed, including, but
not limited to, the implied warranties of merchantability and fitness for a particular purpose. 3Com may make
improvements or changes in the product(s) and/or the program(s) described in this documentation at any time.
UNITED STATES GOVERNMENT LEGENDS:
If you are a United States government agency, then this documentation and the software described herein are provided to
you subject to the following:
United States Government Legend: All technical data and computer software is commercial in nature and developed
solely at private expense. Software is delivered as Commercial Computer Software as defined in DFARS 252.227-7014 (June
1995) or as a commercial item as defined in FAR 2.101(a) and as such is provided with only such rights as are provided in
3Com’s standard commercial license for the Software. Technical data is provided with limited rights only as provided in DFAR
252.227-7015 (Nov 1995) or FAR 52.227-14 (June 1987), whichever is applicable. You agree not to remove or deface any
portion of any legend provided on any licensed program or documentation contained in, or delivered to you in conjunction
with, this User Guide.
Unless otherwise indicated, 3Com registered trademarks are registered in the United States and may or may not be
registered in other countries.
3Com, the 3Com logo, Boundary Routing, EtherDisk, EtherLink, EtherLink II, LANplex, LinkBuilder, Net Age, NETBuilder,
NETBuilder II, OfficeConnect, Parallel Tasking, SmartAgent, SuperStack, TokenDisk, TokenLink, Transcend, and ViewBuilder
are registered trademarks of 3Com Corporation. ATMLink, AutoLink, CoreBuilder, DynamicAccess, FDDILink, FMS,
NetProbe, and PACE are trademarks of 3Com Corporation. 3ComFacts is a service mark of 3Com Corporation.
Artisoft and LANtastic are registered trademarks of Artisoft, Inc. Banyan and VINES are registered trademarks of Banyan
Systems Incorporated. CompuServe is a registered trademark of CompuServe, Inc. DEC and PATHWORKS are registered
trademarks of Digital Equipment Corporation. Intel and Pentium are registered trademarks of Intel Corporation. AIX, AT,
IBM, NetView, and OS/2 are registered trademarks and Warp is a trademark of International Business
Machines Corporation. Microsoft, MS-DOS, Windows, and Windows NT are registered trademarks of
Microsoft Corporation. Novell and NetWare are registered trademarks of Novell, Inc. PictureTel is a registered trademark of
PictureTel Corporation. UNIX is a registered trademark of X/Open Company, Ltd. in the United States and other countries.
Other brand and product names may be registered trademarks or trademarks of their respective holders.
CONTENTS
CONTENTS
ABOUT THIS GUIDE
Finding Information ............................................................................................................xiii
About This Guide contains an overview of the IP Telephony Manager User
Guide, describes where to find specific information, lists conventions and
related documentation, and explains how to contact CommWorks
Corporation.
This guide describes how to install, configure, and operate IP Telephony
Manager, as well as how to use it to troubleshoot and maintain components of
the CommWorks IP Telephony Platform. Its primary audience is operations
personnel.
CommWorks issues release notes with some products—visit our website at
http://totalservice.commworks.com. If the information in the release notes
differs from the information in this guide, use the information in the release
notes.
Finding InformationThe following table lists the location of specific information.
Tab le 1 Content Description
If you are looking forGo to
System overviewChapter 1
Hardware and software requirementsChapter 1
Software installation proceduresChapter 1
Configuration information using IP Telephony ManagerChapter 2
Performance monitoring instructionsChapter 2
Console window menu descriptionChapter 3
Firmware upgrade procedures and general maintenance informationChapter 4
Error messagesAppendix A
IP Telephony Manager commands from the UNIX command lineAppendix B
GlossaryAppendix C
xivABOUT THIS GUIDE
ConventionsThe following tables list conventions in this guide.
Tab le 2 Notice Icon Description
IconNotice TypeDescription
Information NoteInformation that contains
CautionInformation to alert you to
WarningInformation to alert you to
ESDInformation to alert you to
important features or
instructions.
potential damage to a
program, system, or device.
potential personal injury or
fatality. May also alert you
to potential electrical
hazard.
take proper grounding
precautions before handling
a product.
Related
Documentation
Tab le 3 Text Convention Descriptions
ConventionDescription
Text represented as a
screen display
Text represented as
menu or sub-menu
names.
Text represented by
This typeface represents displays that appear on your terminal
screen, for example: Netlogin:
This typeface represents all menu and sub-menu names within
procedures, for example:
On the File menu, click New.Thistypeface represents a variable. For example: <filename>.
<filename>
The following documents contain information about the components of the
CommWorks IP Telephony Platform:
■ CommWorks IP Telephony System Software Installation Guide
■ CommWorks IP Telephony Overview Guide
■ CommWorks IP Telephony Hardware Installation Guide
■ Total Control 1000 Media Gateway Guide
■ CommWorks 4200 Gatekeeper Guide
■ CommWorks 4220 SIP Proxy Server Guide
■ CommWorks 7220 Accounting Server Guide
■ CommWorks 7230 Billing Support Server Guide
■ CommWorks 7210 Directory Mapping Server and CommWorks 7240
Web Provisioning Server Guide
Contacting CommWorks xv
■ CommWorks IP Telephony Parameter (MIB) Reference Guide
■ CommWorks IP Telephony Trap (Alarm) Reference Guide
■ CommWorks 4007 SS7 Signaling Gateway Operation and Maintenance
Guide
Contacting
CommWorks
For information about Customer Service, including support, training, code
releases and updates, contracts, and documentation, visit our website at
http://totalservice.commworks.com.
Refer to the Documentation CD-ROM for information about product warranty.
Before contacting CommWorks Technical Support, have this information
available:
■ Contract number
■ Problem description
■Symptoms
■Known causes
■ CommWorks products
■Software and hardware versions
■Serial numbers
■ Trouble clearing attempts
1
INSTALLATION
This chapter contains an overview of IP Telephony Manager and installation
procedures for UNIX.
This chapter contains the following topics:
■ Overview
■ Management Workstation
■ Prerequisites
■ Before You Begin
■ Removing Previous Versions
■ Installing IP Telephony Manager
■ Starting IP Telephony Manager
■ Connecting to Entities
■ Integrating with HP OpenView
■ Linking CommWorks Objects
OverviewIP Telephony Manager, previously known as Total Control Manager is a
software application that runs on a UNIX management station. This application
remotely manages CommWorks Network Application Cards (NACs) and
Network Interface Cards (NICs) through a Network Management Card (NMC)
installed on the CommWorks 5210 IP Telephony Platform.
Two protocols govern these management functions: Simple Network
Management Protocol (SNMP) between the NMC and the management
station, and a proprietary CommWorks protocol between the NMC and the
managed cards.
IP Telephony Manager communicates with the NMC through SNMP rules.
Because the other NACs in the hub do not use SNMP agent software, the
NMC acts as a proxy agent between these cards and the management station.
Standard SNMP traps can be enabled to send a trap message (or event
notification) to one or more management stations. The management stations
use these traps to create logs, trigger alarms, and initiate actions.
18CHAPTER 1: INSTALLATION
The management station uses Management Information Bases (MIBs), defined
for each card in the hub, to issue commands to the NMC. The NMC executes
the commands and obtains the results using a proprietary CommWorks
protocol. The NMC uses SNMP to send these results to the management
station.
The NMC communicates with each installed card using a proprietary
Management Bus Protocol (MBP). The NMC provides configuration
management for each NAC in the hub and can set each parameter for a NAC
to a specific value. The NMC also configures parameters to predetermined
values when a NAC is installed in the hub. To help manage the configuration,
the NMC can query the current value of parameters for each NAC and
download software for upgrades.
Management
Workstation
You can use HP OpenView or the CommWorks 5000 Network and Service
Management System to monitor the status of all elements of the CommWorks
platform and to act as an alarm server.
Use IP Telephony Manager to configure and monitor all the components of the
CommWork’s platform, such as configuring operational parameters,
upgrading software, and backing up and restoring configurations.
Table 4 lists the additional management software for your workstation.
Tab le 4 Management Software
Software PackageOperating SystemFunction
Network management
application, such as HP
OpenView
CommWorks 5000SUN SolarisNetwork monitoring and bulk operations
HP-UX
SUN Solaris
General network monitoring and alarm
services
PrerequisitesTable 5 lists the hardware requirements needed to achieve the best
performance from IP Telephony Manager.
Tab le 5 Hardware Prerequisites
Operating SystemHardware
SUN PlatformSPARC 20 Workstation, or more recent offering from SUN
64 MB of RAM (minimum)
1 GB Hard Disk Space (Space must be available on one partition.
Swap space is recommended to be at or above 200 MB.)
CD-ROM Drive
Color Monitor
Ethernet Interface
Before You Begin19
Tab le 5 Hardware Prerequisites (continued)
Operating SystemHardware
HP PlatformHP 712/100 or higher Model 712 Workstation
64 MB RAM (minimum)
1 GB Hard Disk Space (Space must be available on one partition.
Swap space is recommended to be at or above 200 MB.)
CD-ROM Drive
Color Monitor
Ethernet Interface
Table 6 lists the software requirements needed to achieve the best
performance from IP Telephony Manager.
Tab le 6 Software Prerequisites
Operating SystemSoftware
SUN PlatformSolaris 2.6, or 2.7 with X11R6
Java Runtime Environment by Sun (shipped with Solaris 7)
Motif Runtime Kit (SUNWmfrun Package)
HP OpenView Windows (OVW) Network Node Manager 6.1
(optional)
HTML Browser (Netscape etc.)
HP PlatformHP-UX 10.20 or higher
HP OpenView Windows Network Node Manager 6.1
(optional)
HTML Browser (Netscape etc.)
Java Runtime Environment by Sun
If you are installing HP OpenView for the first time, temporarily disable
autodiscovery. Do not allow OpenView to discover the devices on your
network automatically. This eases integration with IP Telephony Manager. You
can enable autodiscovery after you install IP Telephony Manager.
Before You BeginBefore installing IP Telephony Manager on your system:
■ Read the readme file (located at /cdrom/cdrom0/tcm/tcm_sol). It contains IP
Telephony Manager installation notes.
■ If you are integrating IP Telephony Manager with HP OpenView Network
Node Manager, install and start HP OpenView.
■ Remove any previous versions of IP Telephony Manager.
This chapter assumes you are running the Korn shell. For installation
instructions for the C or Bourne shells, refer to the readme file.
20CHAPTER 1: INSTALLATION
If you are using HP OpenView, you must install it before you install IP
Telephony Manager. If not, HP OpenView does not integrate correctly. Make
sure IP Telephony Manager and HP OpenView are installed on the same
system. Remember to disable HP OpenView autodiscovery before you do a first
time install/integration of IP Telephony Manager with HP OpenView.
Removing Previous
Versions
Option 1To remove a previous version of IP Telephony Manager without erasing your
Option 2To completely remove a previous version of IP Telephony Manager, including all
When you remove IP Telephony Manager, you can either save your existing
configuration, data, and log files (retaining chassis IP addresses and
configuration information) or erase these files when you remove IP Telephony
Manager.
CommWorks recommends that you save the existing configuration, data, and
log files - (Option 1).
existing IP Telephony Manager database files:
1 Typ e cd $TCMHOME.
2 Typ e ./Remove.
IP Telephony Manager database files:
1 Typ e cd $TCMHOME.
2 Typ e ./Remove -c.
Installing IP
Telephony Manager
To install IP Telephony Manager:
1 Move to the drive and directory that contains the installation files.
2 Create a directory for the software installation.
3 Set the TCMHOME variable to point to that directory.
4 Log in to the UNIX workstation as root.
5 Insert the CommWorks CD.
6 Mount the cdrom drive if necessary.
7 Typ e: cd <working directory> (for example, cd /cdrom/cdrom0/tcm/tcm_sol).
Installing IP Telephony Manager21
8 From the command line prompt, type the following commands and press
Return after each:
TCMHOME=<installation directory> (for example, /opt/tcm)
export TCMHOME
mkdir -p $TCMHOME
cd cdrom/cdrom0/tcm_sol (for HP, tcm_ux)
./install
A message appears:
The script will make adjustments, only as needed, to
system files in /etc/imit.d, the crontab, /etc/services,
and /usr/lib/x11.
If TCM is later removed, these adjustments will be
undone to restore the original state.
Setting PATH and
LD_LIBRARY_PATH
Do you wish to continue [y/n]
9 Typ e y, and then press Return.
The installation proceeds, listing files as they are installed. The following
message appears to indicate the installation has completed successfully:
TCM installation is complete
You can now enable HP Overview autodiscovery on your system.
Before you can start IP Telephony Manager, you must add $TCMHOME to the
PATH statement and indicate the location of the IP Telephony Manager library
files as follows:
From the command line prompt, type the following commands and press
Return after each:
PATH=$PATH:$TCMHOME/bin
export PATH
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$TCMHOME/lib
export LD_LIBRARY_PATH
22CHAPTER 1: INSTALLATION
Starting IP Telephony
Manager
After you complete the installation and modify the path statement, you can
start IP Telephony Manager.
To start the IP Telephony Manager, from the command line prompt, type one
of these commands:
# xtcmvfpd
or
# xtcmvfpd <target chassis IP address>
The first command causes a list of the chassis components to display. You can
then select the component that you want to start. The second command
specifies the IP address of the component that you want started.
The IP Telephony Manager graphical user interface (GUI) opens a virtual display
of the target chassis. If the virtual display does not appear, set and export the
paths according to the instructions in this chapter.
For a complete description of the menus on the GUI, refer to Chapter 3
Navigating and Using the System
.
Connecting to
Entities
CommWorks IP Telephony Manager lets you configure and monitor any
CommWorks IP Telephony entity (for example the Media Gateway,
Gatekeeper, Accounting Server, Billing Support Server.) on your system. To
connect to the individual entities:
1 Start IP Telephony Manager.
2 Click File, and click Open, and then click New from the IP Telephony Manger
Console window.
3 Enter the name and IP address of the entity.
4 Verify that the community strings are as follows:
■ Read-only is public (case sensitive)
■ Read/write is private (case sensitive)
To modify these default settings, refer to Chapter 4, topic: Changing the SNMP
Community Strings.
5 Click OK.
Connecting to Entities23
To view the entity after the it is connected using IP Telephony Manager:
1 Start IP Telephony Manager.
2 Click File and then click Open from the IP Telephony Manger Console
window.
3 Select the entity from the list.
4 Click OK.
The entity appears in graphical form. When selected, the entity is blue; when
deselected, the entity is black.
Determining
Gatekeeper and Media
Gateway Connectivity
To test Gatekeeper to Media Gateway connectivity, use the following
procedure.
1 Using IP Telephony Manager Console window, select the edge server card.
2 On the menu bar, select Performance and then Performance Monitor.
The Select Entity window appears.
3 Select the entity 3Com Gateway and then click OK.
The Performance window appears.
Figure 1 Performance Window
4 Select Gatekeepers from the Functional Group.
5 Select Current Gatekeeper IP address and click Add. Click OK.
A real time table appears and displays the selected Gateway and the
Gatekeeper to which it is registered. The IP address of the Gatekeeper to
which it is registered also appears.
24CHAPTER 1: INSTALLATION
Integrating with HP
OpenView
The IP Telephony Manager installation script installs OpenView integration files
to the appropriate OpenView Network Node Manager subdirectories.
OpenView integration occurs as part of the IP Telephony Manager installation,
when the OpenView environmental variables are set beforehand. To integrate
IP Telephony Manager with OpenView manually, follow the procedure below.
1 Set the OpenView environmental variables.
# cd /opt/OV/bin
# . ./ov.envvars.sh
2 Test the environmental variables.
# cd $OV_BIN
# pwd
Solaris responds as follows:
/opt/OV/bin
3 Change to the directory that contains the integration files.
# cd $TCMHOME/ovw
4 Install the integration files.
# ./Install
You can run the $TCMHOME/ovw/Install script at any time. You do not need
to run $TCMHOME/ovw/Remove before running $TCMHOME/ovw/Install
again.
HP OpenView integrates the IP Telephony Manager icons; this lets you access IP
Telephony Manager from HP OpenView.
Fixing Incorrect MapsIf you populate CommWorks devices in OpenView before you installed IP
Telephony Manager, IP Telephony Manager integration does not change the
component type from a non-CommWorks type to a CommWorks chassis type.
You cannot do this automatically in HP OpenView. For best results, delete and
rediscover the CommWorks devices.
You can also use the OpenView ovtopofix -r -o <object id> command.
CommWorks object IDs 1.3.6.1.4.1.429.2.1 through 1.3.6.1.4.1.429.2.9 must
each be individually specified.
Integrating with HP OpenView25
If CommWorks devices were populated in OpenView before IP Telephony
Manager was installed, the network map will not display the CommWorks
bitmaps correctly after IP Telephony Manager integration. This occurs even if
the CommWorks menu options are not enabled and the isUSREntNetHub
capability is not set to True. For best results, delete and rediscover the
CommWorks devices.
Removing HP
OpenView Integration
Erasing IP Telephony
Manager
Verifying the
Installation
To remove OpenView integration:
1 Login as root.
2 Type the following:
cd $TCMHOME/ovw
./Remove -r
While all CommWorks files are removed from HP OpenView, no changes are
made to the runtime databases. One of the primary purposes of removal is to
prepare for a new installation.
To erase IP Telephony Manager from HP OpenView, replace the current maps
with new ones. You can also delete and rediscover all the CommWorks devices
from each map.
Start IP Telephony Manager with the following commands:
> TCMHOME=<installation directory>
> export TCMHOME
> PATH=$PATH:$TCMHOME/bin
> export PATH
> ./xtcmvfpd <TCH IP_Address/HostName>
IP Telephony Manager opens.
For a complete description of the menus on the GUI, refer to Chapter 3
Navigating and Using the System
.
26CHAPTER 1: INSTALLATION
Linking CommWorks
Objects
If you choose to install HP OpenView, you must install it before IP Telephony
Manager. This lets you start IP Telephony Manager directly from HP OpenView.
To link CommWorks objects in HP OpenView to IP Telephony Manager, use the
following procedure.
1 Typ e:
#cd $OV_BIN
#./ovstart
#./ovw
2 Go to the chassis to be linked, and then click on it.
3 Right click and select Symbol Properties from the pop-up menu.
4 Under Behavior, click Execute.
5 Under Application Action, click USRRobotics: USRVFPD.
6 Click Target Objects, click Add, and then click OK.
7 Click OK on the window that appears.
8 Double-click the object with the chassis IP address.
The chassis graphical user interface appears.
2
CONFIGURATION
This chapter describes how to configure CommWorks IP Telephony Manager.
This chapter contains the following topics:
■ Management Station Configuration
■ Component Configuration
■ Synchronizing Network Time
■ Auto Response
■ Setting Authorized Stations
■ Defining a Range of IP Addresses for Authorized Access
■ Threshold Monitoring Configuration
Management Station
Configuration
■ Saving and Restoring Configurations
Refer to Chapter 3 for a complete description of the IP Telephony Manager
menus.
Unless otherwise specified, this document uses the generic term edge server to
refer to either the edge server card or the EdgeServer Pro card.
You should not need to configure your management station after installing IP
Telephony Manager for UNIX. IP Telephony Manager adds the following files to
locations as set up in $OV_BIN/ov.envvars.sh:
Tab le 7 Files added to HP OpenView Windows Directories
Category File location
Field definitions$OV_FIELDS/C/usr_fields
Application registration$OV_REGISTRATION/C/USRobotics
CommWorks-specific
The IP Telephony Manager Console window is used to select target
components whenever you are performing configuration, sending commands,
or upgrading components through software download.
Launching the
Configuration Tool
There are two ways to launch the Configuration Tool:
■ From the IP Telephony Manager Console, select a target from the IP
Telephony Manager Console window, and then from the Configuration
menu, select Programmed Settings.
■ From the UNIX command line, type xtcmconf followed by the IP address or
hostname of the target device and the target slots and channels (refer to
Synchronizing
Network Time
Appendix B Command Line Interface
You must synchronize the system time of each component in the network
accurate tracking of the IP telephony traffic. To achieve system
for more details).
synchronization, set each Gatekeeper, SIP Proxy Server, and Back-end Server to
Greenwich Mean Time (GMT) and use the Network Time Protocol (NTP) on all
system components.
Setting the Time ZoneFor each Gatekeeper, SIP Proxy Server, and Back-end Server in the IP telephony
network, set the time zone to GMT.
Recording the NTP IP
Addresses
1 From the Windows desktop, click Start, then Settings, and then click Control
Panel.
2 Double-click Date/Time.
The Date/Time Properties window appears.
3 Click Time Zone.
4 From the drop-down list, select [GMT] Greenwich Mean Time: Dublin,
Edinburgh, Lisbon, London.
5 Click OK.
NTP uses a primary and a secondary NTP time server for system time. You can
use the IP addresses of NTP time servers that are local to your network, or you
can use public NTP time servers. The IP addresses of public NTP time servers are
available on the internet. Use the following procedure to record a primary and
secondary NTP time server address.
Selecting Local NTP Servers
If your local network includes local NTP time servers, record the IP address of
the primary NTP time server and the secondary NTP time server.
Synchronizing Network Time29
Selecting Public NTP Servers
1 From any computer with internet access, access the following website:
http://www.eecis.udel.edu/~mills/ntp/clock1.htm
2 From the website, record the IP addresses for two separate active servers. One
is used as the primary NTP server, and the other is used as the secondary NTP
server. We recommend choosing NTP server locations that are as close to the
Media Gateway chassis as possible.
Setting the NTP
Parameters
Use NTP to synchronize the time across the network. The NTP parameters must
be set for the HiPer NMC card in each Media Gateway chassis, the
Gatekeepers, SIP Proxy Servers, and the Back-end Servers.
All Media Gateway chassis components are automatically synchronized
through the controlling HiPer NMC after it is configured for NTP.
Setting the NTP Parameters for the HiPer NMC
For the HiPer NMC card in each Media Gateway chassis, do the following:
1 Using IP Telephony Manager, open the Media Gateway chassis.
2 Select the HiPer NMC card.
3 Click Configuration, then Programmed Settings from the IP Telephony
Manager Console window.
4 Select Network Time Protocol from the Parameter Group drop-down list.
The Network Time Protocol windows appears.
Figure 2 Media Gateway Network Time Protocol Window
30CHAPTER 2: CONFIGURATION
5 Enter the Primary and Secondary NTP IP Addresses (refer to Recording the NTP
IP Addresses).
6 Set the Operational Mode to Unicast.
7 Click Set.
Setting the NTP Parameters for the Other Entities
For each Gatekeeper, SIP Proxy Server, and Back-end Server:
1 Using IP Telephony Manager, open the targeted server.
2 Select the server icon.
3 Select Configuration, then Programmed Settings from the IP Telephony
Manager Console window.
4 Select 3Com SNMP Agent from the Select Entity drop-down list.
5 Click OK.
6 Select Network Time Protocol.
A window similar to the following appears:
Figure 3 Server Network Time Protocol Window
7 Enter the Primary and Secondary NT IP addresses (refer to Recording the NTP IP
Addresses).
8 Set the Operational Mode to Unicast.
9 Click Set.
10 Click Exit.
Loading...
+ 114 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.