Application Notes for Integrated Research PROGNOSIS IP

Avaya Solution & Interoperability Test Lab
Application Notes for Integrated Research PROGNOSIS IP
Telephony Manager with Avaya Communication Manager
- Issue 1.0
Abstract
These Application Notes describe the procedures for configuring Integrated Research
PROGNOSIS IP Telephony Manager to interoperate with Avaya Communication Manager.
PROGNOSIS IP Telephony Manager is a performance management solution for multi-vendor
IP telephony solutions. PROGNOSIS IP Telephony Manager provides visibility of Avaya and
other vendor’s IP Telephony solutions from a single console. Targeted at Managed Service
Providers of IP telephony solutions, PROGNOSIS IP Telephony Manager offers a multicustomer, multi-PBX perspective, enabling a significant reduction in complexity when
managing multiple IP Telephony vendors.
PROGNOSIS integrates directly to Avaya Communication Manager using Secure Shell (SSH).
At the same time, it processes Real-time Transport Control Protocol (RTCP) information from
Avaya Communication Manager and Avaya IP Telephones.
Information in these Application Notes has been obtained through compliance testing and
additional technical discussions. Testing was conducted via the DeveloperConnection Program
at the Avaya Solution and Interoperability Test Lab.
JC; Reviewed:
SPOC 1/22/2007
Solution & Interoperability Test Lab Application Notes
©2007 Avaya Inc. All Rights Reserved.
1 of 15
PROGNOSIS-CM
1. Introduction
These Application Notes describe the compliance-tested configuration used to validate Integrated
Research PROGNOSIS IP Telephony Manager 9.0.0 with Avaya Communication Manager
3.1.2.
The PROGNOSIS IP Telephony Manager is based on the PROGNOSIS product-family
architecture for the scalable monitoring of business critical systems. The PROGNOSIS product
consists of:
•
One or more PROGNOSIS Monitoring Nodes (Server Nodes). These are servers used
by the PROGNOSIS product to collect, relay and store information collected from the
monitored systems. In some case the monitoring node may actually exist as an agent
running on the monitored system but in the case of Avaya Communication Manager, all
monitoring nodes are separate servers.
•
The PROGNOSIS GUI is a Microsoft Windows client program which is used to connect
to a PROGNOSIS monitoring node and display the information collected by the
monitoring node. The PROGNOSIS GUI may either be installed on a monitoring node or
on a separate computer.
The PROGNOSIS IP Telephony Manager product uses two methods to monitor an Avaya
Communication Manager system.
•
System Access Terminal (SAT)
The PROGNOSIS IP Telephony Manager uses a pool of threads to establish SSH
connections to the SAT using the IP address of the media servers. By default, the solution
attempts to establish three concurrent SAT connections to an Avaya Communication
Manager system. The solution uses the connections to execute SAT commands on the media
server.
•
RTCP Collection
The PROGNOSIS IP Telephony Manager collects RTCP information sent by Avaya
Communication Manager IP Media Processor boards, media gateways and IP Telephones.
Figure 1 illustrates the sample configuration used to verify Integrated Research PROGNOSIS IP
Telephony Manager interoperability with Avaya Communication Manager. It consists of an
Avaya Communication Manager system running on a pair of Avaya S8720 Media Servers with
an Avaya G650 Media Gateway and a second system running on an Avaya S8300B Media
Server with an Avaya G700 Media Gateway. Both systems have Avaya IP, Digital and analog
telephones, and Avaya IP Softphone and IP Agent users configured for making and receiving
calls. IP Trunks connects the two systems together to allow calls between them. Integrated
Research PROGNOSIS IP Telephony Manager was installed on a server running Microsoft
JC; Reviewed:
SPOC 1/22/2007
Solution & Interoperability Test Lab Application Notes
©2007 Avaya Inc. All Rights Reserved.
2 of 15
PROGNOSIS-CM
Windows Server 2003 Standard with Service Pack 1. Both the Monitoring Node and GUI
software are installed on this server. All the systems and telephones are connected using two
Avaya C364T-PWR Converged Stackable Switches for network connectivity.
Figure 1: Sample Configuration
2. Equipment and Software Validated
The following equipment and software were used for the sample configuration provided:
Equipment
Avaya S8720 Media Servers
Avaya G650 Media Gateway
• TN2312BP IP Server Interface
• TN799DP C-LAN Interface
• TN2302AP IP Media Processor
Avaya S8300B Media Server
Avaya G700 Media Gateway
Avaya 4600 series IP telephones
Avaya 9600 series IP telephones
Avaya 6200 series analog telephones
Avaya 2400 series digital telephones
Avaya IP Softphone
Avaya IP Agent
JC; Reviewed:
SPOC 1/22/2007
Software
3.1.2 (R013x.01.2.632.1)
HW15, FW036
HW01, FW017
HW20, FW115
3.1.2 (R013x.01.2.632.1)
25.33.0
R2.7
R1.1
R5.2 Service Pack 1
R6.0.14.526
Solution & Interoperability Test Lab Application Notes
©2007 Avaya Inc. All Rights Reserved.
3 of 15
PROGNOSIS-CM
Avaya C364T-PWR Converged Stackable Switches
Integrated Research PROGNOSIS IP Telephony Manager
Microsoft Windows Server 2003 Standard
4.5.14
9.0.0
Service Pack 1
3. Configure Avaya Communication Manager
This section describes the steps needed to configure Avaya Communication Manager to
interoperate with Integrated Research PROGNOSIS IP Telephony Manager. This section
describes the steps to create a login account for PROGNOSIS to access Avaya Communication
Manager, the assigning of permissions to the login account and the steps to enable RTCP
reporting.
3.1. Configure SAT Login Account
PROGNOSIS IP Telephony Manager logs into Avaya Communication Manager to monitor the
configuration, usage and health of the system. As PROGNOSIS IP Telephony Manager does not
modify any system configuration, creating a separate SAT login account with limited
permissions is recommended.
Step Description
1. Enter the add login login-id command, where login-id is the name of login account to be
created. Set Login Type to customer and Service Level to non-super-user.
add login iptelmgr
Page
1 of
1
LOGIN ADMINISTRATION
LOGIN BEING ADMINISTERED
Login's Name: iptelmgr
Login Type: customer
Service Level: non-super-user
Days To Disable After Inactivity:
Disable Following a Security Violation? y
LOGIN'S PASSWORD INFORMATION
Login's Password:
Reenter Password:
Change Password at First Login? n
Password Aging Cycle Length (Days):
LOGOFF NOTIFICATION
Facility Test Call Notification? y
Remote Access Notification? y
JC; Reviewed:
SPOC 1/22/2007
Acknowledgement Required? y
Acknowledgement Required? y
Solution & Interoperability Test Lab Application Notes
©2007 Avaya Inc. All Rights Reserved.
4 of 15
PROGNOSIS-CM
2. Enter the change permissions login-id command, where login-id is the login account
created in Step 1. Set Display Admin. and Maint. Data and System Measurements to y.
change permissions iptelmgr
Page
1 of
COMMAND PERMISSION CATEGORIES
Login Name: iptelmgr
COMMON COMMANDS
Display Admin. and Maint. Data? y
System Measurements? y
System Mgmt Data Transfer Only? n
ADMINISTRATION COMMANDS
Administer Stations? n
Administer Features? n
Administer Trunks? n
Administer Permissions? n
Additional Restrictions? n
MAINTENANCE COMMANDS
Maintain Stations? n
Maintain Switch Circuit Packs? n
Maintain Trunks? n
Maintain Process Circuit Packs? n
Maintain System? n
Maintain Enhanced DS1? n
1
3.2. Configure RTCP Monitoring
To allow PROGNOSIS IP Telephony Manager to monitor the quality of IP calls, configure
Avaya Communication Manager to send RTCP reporting to the IP address of the PROGNOSIS
server.
Step Description
1. Enter the change system-parameters ip-options command. In the RTCP MONITOR
SERVER section, set Default Server IP Address to the IP address of the PROGNOSIS
IP Telephony Manager server. Set Default Server Port to 5005 and Default RTCP
Report Period(secs) to 5.
change system-parameters ip-options
IP-OPTIONS SYSTEM PARAMETERS
IP MEDIA PACKET PERFORMANCE THRESHOLDS
Roundtrip Propagation Delay (ms)
High:
Packet Loss (%)
High:
Ping Test Interval (sec):
Number of Pings Per Measurement Interval:
RTCP MONITOR SERVER
Default Server IP Address: 10 .1
Default Server Port: 5005
Default RTCP Report Period(secs): 5
800
40
20
10
Page
1 of
2
Low: 400
Low: 15
.10 .105
AUTOMATIC TRACE ROUTE ON
Link Failure? y
H.248 MEDIA GATEWAY
Link Loss Delay Timer (min): 5
H.323 IP ENDPOINT
Link Loss Delay Timer (min): 5
Primary Search Time (sec): 75
Periodic Registration Timer (min): 20
JC; Reviewed:
SPOC 1/22/2007
Solution & Interoperability Test Lab Application Notes
©2007 Avaya Inc. All Rights Reserved.
5 of 15
PROGNOSIS-CM
Step Description
2. Enter the change ip-network-region n command, where n is IP network region number
to be monitored. Set RTCP Reporting Enabled to y and Use Default Server
Parameters to y.
Note: Only one RTCP MONITOR SERVER can be configured per IP network region.
change ip-network-region 1
Page
1 of
19
IP NETWORK REGION
Region: 1
Location: 1
Authoritative Domain: sglab.com
Name: SP Main
MEDIA PARAMETERS
Intra-region IP-IP Direct Audio: yes
Codec Set: 1
Inter-region IP-IP Direct Audio: yes
UDP Port Min: 2048
IP Audio Hairpinning? y
UDP Port Max: 65535
DIFFSERV/TOS PARAMETERS
RTCP Reporting Enabled? y
Call Control PHB Value: 46
RTCP MONITOR SERVER PARAMETERS
Audio PHB Value: 46
Use Default Server Parameters? y
Video PHB Value: 26
802.1P/Q PARAMETERS
Call Control 802.1p Priority: 6
Audio 802.1p Priority: 6
Video 802.1p Priority: 5
AUDIO RESOURCE RESERVATION PARAMETERS
H.323 IP ENDPOINTS
RSVP Enabled? n
H.323 Link Bounce Recovery? y
Idle Traffic Interval (sec): 20
Keep-Alive Interval (sec): 5
Keep-Alive Count: 5
3. Repeat Step 2 for all IP network regions that are required to be monitored.
JC; Reviewed:
SPOC 1/22/2007
Solution & Interoperability Test Lab Application Notes
©2007 Avaya Inc. All Rights Reserved.
6 of 15
PROGNOSIS-CM
4. Configure Integrated Research PROGNOSIS IP Telephony
Manager
This section describes the configuration of Integrated Research PROGNOSIS IP Telephony
Manager required to interoperate with Avaya Communication Manager.
Step Description
1. On the Integrated Research PROGNOSIS IP Telephony Manager server, click Start→All
Programs→ PROGNOSIS IP Telephony Manager→PROGNOSIS GUI to start the
PROGNOSIS GUI application. Enter a valid Windows user account and password to log
in to the Monitoring Node.
2. To configure Avaya Communication Manager systems to be monitored, expand
Configurations of the Monitoring Node, right-click on AVAYA_PBX and select
Properties.
JC; Reviewed:
SPOC 1/22/2007
Solution & Interoperability Test Lab Application Notes
©2007 Avaya Inc. All Rights Reserved.
7 of 15
PROGNOSIS-CM
Step Description
3. In the Configurations tab, add an entry for each Avaya Communication Manager system
to be managed. The template to add a system is given in the PROGNOSIS GUI
application. In this sample configuration, the following entries are added for the two
Avaya Communication Manager systems with the names S8720-PBX and S8300-PBX
and with the IP addresses of the Media Servers 10.1.50.10 and 10.1.60.10 respectively.
The PROGNOSIS Monitoring Node will use SSH to connect to port 5022 of the Media
Servers by default.
ADD PBX ( \S8720-PBX, ip=10.1.50.10 )
ADD PBX ( \S8300-PBX, ip=10.1.60.10 )
Click Start to proceed.
JC; Reviewed:
SPOC 1/22/2007
Solution & Interoperability Test Lab Application Notes
©2007 Avaya Inc. All Rights Reserved.
8 of 15
PROGNOSIS-CM
Step Description
4. To configure the SAT login account and password, expand Configurations of the
Monitoring Node, right-click on PASSWORDS and select Properties.
JC; Reviewed:
SPOC 1/22/2007
Solution & Interoperability Test Lab Application Notes
©2007 Avaya Inc. All Rights Reserved.
9 of 15
PROGNOSIS-CM
Step Description
5. Click the + ‘plus’ button to add a new password entry for each of the configured system
in Step 3. The Entry Name must be of the form avaya-sat:<pbx-name>. For the system
with the name S8720-PBX, enter avaya-sat:S8720-PBX for Entry Name, uncheck
Password Only, and enter the login account created in Section 3.1 for Username and
Password. Repeat to add another entry for the second system S8300-PBX. Click Start to
proceed.
5. Interoperability Compliance Testing
The interoperability compliance test included feature and serviceability testing.
The feature testing evaluated the ability of the PROGNOSIS IP Telephony Manager to correctly
retrieve the configuration, performance, alarms and errors from an Avaya Communication
Manager system. In addition, the ability of PROGNOSIS IP Telephony Manager to receive and
process RTCP information from Avaya Communication Manager and Avaya IP endpoints was
also validated.
The serviceability testing introduced failure scenarios to see if PROGNOSIS IP Telephony
Manager is able to resume service after failure recovery and media server interchange.
JC; Reviewed:
SPOC 1/22/2007
Solution & Interoperability Test Lab Application Notes
©2007 Avaya Inc. All Rights Reserved.
10 of 15
PROGNOSIS-CM
5.1. General Test Approach
The general test approach was to use PROGNOSIS GUI to display the configurations of Avaya
Communication Manager systems and verify against what is displayed on the SAT interface. The
SAT interface is accessed by using either telnet or Secure Shell (SSH) to the Avaya Media
Server. Calls were placed between various Avaya endpoints and the PROGNOSIS GUI was used
to display the RTCP information collected.
For feature testing, PRONOSIS GUI was used to view the configurations of Avaya
Communication Manager such as media gateways, cabinets, port networks, trunk groups, route
patterns, CLAN, MEDPRO and DS1 boards, IP network regions, stations, processor occupancy,
alarm and error information. Various conditions such as media gateway, port network, trunk
group, trunk member and endpoint failures were created to see if PROGNOSIS IP Telephony
Manager was able to detect the outage. For the collection of RTCP information, the endpoints
included Avaya IP, digital and analog telephones, and Avaya IP Softphone and IP Agent users.
For serviceability testing, reboots were applied to the PROGNOSIS IP Telephony Manager
server and Avaya Communication Manager Media Servers to simulate system unavailability.
Interchange of the Avaya S8720 Media Servers were also performed during testing.
5.2. Test Results
All test cases passed successfully. Integrated Research PROGNOSIS IP Telephony Manager
successfully interoperates with Avaya Communication Manager.
6. Verification Steps
This section provides the tests that can be performed to verify proper configuration of Avaya
Communication Manager and Integrated Research PROGNOSIS IP Telephony Manager.
6.1. Verify Avaya Communication Manager
Verify that PROGNOSIS IP Telephony Manager has established three concurrent SSH
connections to the SAT by using the status logins command.
status logins
USER LOGIN INFORMATION
Login
Type
*dadmin SYS-PORT
iptelmgSYS-PORT
iptelmgSYS-PORT
iptelmgSYS-PORT
JC; Reviewed:
SPOC 1/22/2007
Location
Aux
Active Command
ID
SSH
SSH
SSH
SSH
135.27.8.190
10.1.10.105
10.1.10.105
10.1.10.105
stat logins
1
3
4
5
Solution & Interoperability Test Lab Application Notes
©2007 Avaya Inc. All Rights Reserved.
11 of 15
PROGNOSIS-CM
6.2. Verify Integrated Research PROGNOSIS IP Telephony Manager
The following steps are done using the PROGNOSIS GUI.
Step Description
1. After logging into PROGNOSIS GUI, click on the Home button on the toolbar to display
the Welcome screen. In the Monitor section, click Entire Network→Avaya→PBX to
display the list of Avaya Communication Manager Media Servers configured in Section 4
Step 3.
JC; Reviewed:
SPOC 1/22/2007
Solution & Interoperability Test Lab Application Notes
©2007 Avaya Inc. All Rights Reserved.
12 of 15
PROGNOSIS-CM
Step Description
2. In the Avaya System page, verify that the SAT field for each configured Avaya
Communication Manager shows 3 connections.
JC; Reviewed:
SPOC 1/22/2007
Solution & Interoperability Test Lab Application Notes
©2007 Avaya Inc. All Rights Reserved.
13 of 15
PROGNOSIS-CM
7. Support
For technical support on Integrated Research PROGNOSIS IP Telephony Manager, contact the
Integrated Research Support Team at:
•
•
•
Phone: +61 (2) 9966 1066
Fax: +61 (2) 9921-1042
Email: support@prognosis.com
8. Conclusion
These Application Notes describe the procedures for configuring the Integrated Research
PROGNOSIS IP Telephony Manager 9.0.0 to interoperate with Avaya Communication Manager
Release 3.1.2. In the configuration described in these Application Notes, the PROGNOSIS IP
Telephony Manager established SSH connections to the SAT to view the configurations of
Avaya Communication Manager and to monitor for failures. PROGNOSIS IP Telephony
Manager also processed the RTCP information to monitor the quality of IP calls. During
compliance testing, all test cases were completed successfully.
9. Additional References
The following document can be found at http://support.avaya.com:
•
Administrator Guide for Avaya Communication Manager, 03-300509, Issue 2, February
2006
JC; Reviewed:
SPOC 1/22/2007
Solution & Interoperability Test Lab Application Notes
©2007 Avaya Inc. All Rights Reserved.
14 of 15
PROGNOSIS-CM
©2007 Avaya Inc. All Rights Reserved.
Avaya and the Avaya Logo are trademarks of Avaya Inc. All trademarks identified by ® and ™
are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the
property of their respective owners. The information provided in these Application Notes is
subject to change without notice. The configurations, technical data, and recommendations
provided in these Application Notes are believed to be accurate and dependable, but are
presented without express or implied warranty. Users are responsible for their application of any
products specified in these Application Notes.
Please e-mail any questions or comments pertaining to these Application Notes along with the
full title name and filename, located in the lower right corner, directly to the Avaya
DeveloperConnection Program at devconnect@avaya.com.
JC; Reviewed:
SPOC 1/22/2007
Solution & Interoperability Test Lab Application Notes
©2007 Avaya Inc. All Rights Reserved.
15 of 15
PROGNOSIS-CM