Avaya PROGNOSIS IP s Supplément
JC; Reviewed:
SPOC 6/16/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
1 of 30
IPTM96-CM601
Avaya Solution & Interoperability Test Lab
Application Notes for Integrated Research PROGNOSIS IP
Telephony Manager 9.6 with Avaya Aura® Communication
Manager - Issue 1.0
Abstract
These Application Notes describe the procedures for configuring Integrated Research
PROGNOSIS IP Telephony Manager 9.6 to interoperate with Avaya Aura® Communication
Manager 6.0.1.
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 multi-site enterprises
and managed service providers of IP telephony solutions, PROGNOSIS IP Telephony
Manager offers a multi-customer, multi-PBX perspective, enabling a significant reduction in
complexity when managing complex IP telephony environments.
PROGNOSIS integrates directly to Communication Manager using Secure Shell (SSH). At the
same time, it processes Real-time Transport Control Protocol (RTCP) and Call Detail
Recording (CDR) information from Communication Manager.
Information in these Application Notes has been obtained through DevConnect compliance
testing and additional technical discussions. Testing was conducted via the DevConnect
Program at the Avaya Solution and Interoperability Test Lab.
JC; Reviewed:
SPOC 6/16/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
2 of 30
IPTM96-CM601
1. Introduction
These Application Notes describe the compliance tested configuration used to validate Integrated
Research PROGNOSIS IP Telephony Manager with Avaya Aura® Communication Manager.
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
Communication Manager.
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 three methods to monitor a
Communication Manager system.
System Access Terminal (SAT) - The PROGNOSIS IP Telephony Manager uses a pool
of SSH connections to the SAT using the IP address of the Avaya Server. By default, the
solution establishes three concurrent SAT connections to the Communication Manager
system and uses the connections to execute SAT commands.
Real Time Transport Control Protocol (RTCP) Collection - The PROGNOSIS IP
Telephony Manager collects RTCP information sent by the Avaya IP Media Processor
(MEDPRO) boards, media gateways, IP Telephones and IP Softphones.
Call Detail Recording (CDR) Collection - The PROGNOSIS IP Telephony Manager
collects CDR information sent by Communication Manager.
2. General Test Approach and Test Results
The general test approach was to use PROGNOSIS GUI to display the configurations of the
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 S8800 and
S8300D Servers. Calls were placed between various Avaya endpoints and PROGNOSIS GUI
was used to display the RTCP and CDR information collected.
JC; Reviewed:
SPOC 6/16/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
3 of 30
IPTM96-CM601
2.1. Interoperability Compliance Testing
For feature testing, PROGNOSIS GUI was used to view the configurations of Communication
Manager such as port networks, cabinets, media gateways, ESS, LSP, trunk groups, route
patterns, CLAN, MEDPRO and DS1 boards, IP network regions, stations, processor occupancy,
alarm and error information. During testing, a call generator was used to load the
Communication Manager systems by placing incoming calls through two E1 ISDN-PRI trunks to
the system in Site A and terminating the calls as IP stations on the system in Site B. For the
collection of RTCP and CDR information, the endpoints included Avaya IP, digital and analog
telephones, Avaya A175 Desktop Video Device and Avaya one-X® Communicator users. The
types of calls made included intra-switch calls, inbound/outbound inter-switch IP trunk calls,
transferred calls and conference calls.
For serviceability testing, reboots were applied to the PROGNOSIS IP Telephony Manager
Server and Avaya Servers to simulate system unavailability. Interchanging of the Avaya S8800
Servers and failover to ESS and LSP were also performed during testing.
2.2. Test Results
All test cases passed successfully.
2.3. Support
For technical support on Integrated Research PROGNOSIS IP Telephony Manager, contact the
Integrated Research Support Team at:
Hotline: +61 (2) 9921 1524
Email: support@prognosis.com
JC; Reviewed:
SPOC 6/16/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
4 of 30
IPTM96-CM601
3. Reference Configuration
Figure 1 illustrates the test configuration used to verify Integrated Research PROGNOSIS IP
Telephony Manager interoperability with Communication Manager. It consists of a
Communication Manager system running on a pair of Avaya S8800 Servers with two Avaya
G650 Media Gateways, an Avaya G430 Media Gateway with Avaya S8300D Server as a Local
Survivability Processor (LSP) and an Avaya G250-BRI Media Gateway. An Enterprise
Survivable Server (ESS) running on Avaya S8800 Server was also configured for failover
testing. A second Communication Manager system runs on an Avaya S8300D Server with an
Avaya G450 Media Gateway. Both systems have Avaya IP (H.323 and SIP), digital and analog
telephones, and Avaya one-X®Communicator users configured for making and receiving calls.
IP Trunks connect the two systems together to allow calls between them. Avaya Aura® System
Manager and Avaya Aura® Session Manager provided SIP support to the Avaya SIP telephones
and Avaya A175 Desktop Video Device. Integrated Research PROGNOSIS IP Telephony
Manager was installed on a server running Microsoft Windows Server 2003 with Service Pack 2.
Both the Monitoring Node and GUI software are installed on this server. The Avaya 4548GT-
PWR Ethernet Routing Switch provides Ethernet connectivity to the servers, media gateways
and IP telephones.
Figure 1: Test Configuration
JC; Reviewed:
SPOC 6/16/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
5 of 30
IPTM96-CM601
4. Equipment and Software Validated
The following equipment and software were used for the sample configuration provided:
Equipment
Software
Avaya S8800 Servers
Avaya Aura® Communication Manager
6.0.1
(Service Pack 1.01 00.1.510.1-18857)
Avaya G650 Media Gateways
- TN2312BP IP Server Interface
- TN799DP C-LAN Interface
- TN2302AP IP Media Processor
- TN2602AP IP Media Processor
- TN2214CP Digital Line
- TN793CP Analog Line
- TN2464BP DS1 Interface
- TN2464CP DS1 Interface
-
HW07, FW053 and
HW15 FW054
HW01, FW039 and
HW01 FW040
HW20 FW121 and
HW20 FW117
HW02 FW058 and
HW02 FW041
HW08 FW015
HW09 FW010
HW05 FW024
HW02 FW024
Avaya G250-BRI Media Gateway
30.18.1
Avaya G430 Media Gateway
- MM712AP DCP MM
- MM714AP Analog MM
- MM711AP Analog MM
- MM710AP DS1 MM
31.18.1
HW04 FW009
HW04 FW073
HW31 FW093
HW05 FW021
Avaya S8300D Server as LSP
6.0.1
(Service Pack 1.01 00.1.510.1-18857)
Avaya S8800 Server as ESS
6.0.1
(Service Pack 1.01 00.1.510.1-18857)
Avaya S8300D Server
Avaya Aura® Communication Manager
6.0.1
(Service Pack 1.01 00.1.510.1-18857)
Avaya G450 Media Gateway
- MM722AP BRI Media Module (MM)
- MM712AP DCP MM
- MM714AP Analog MM
- MM717AP DCP MM
- MM710BP DS1 MM
31.18.1
HW01 FW008
HW07 FW009
HW10 FW093
HW03 FW009
HW11 FW049
Avaya Aura® System Manager
6.1 Service Pack 2
Avaya Aura® Session Manager
6.1 Service Pack 2
Avaya 9600 Series IP telephones
- 9630, 9640, 9650, 9670G
3.1 SP2 (H.323) or
2.6 SP4 (SIP)
Avaya 1608 IP telephones
1.300B (H.323)
Avaya 6221 analog telephones
-
JC; Reviewed:
SPOC 6/16/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
6 of 30
IPTM96-CM601
Equipment
Software
Avaya digital telephones
- 1416
- 2420
SP1
-
Avaya A175 Desktop Video Device
1.0
Avaya one-X® Communicator
6.0 SP1 (H.323)
Avaya 4548GT-PWR Ethernet Routing
Switch
V5.4.0.008
Integrated Research PROGNOSIS IP
Telephony Manager
9.6.1 Patch 11
5. Configure Communication Manager
This section describes the steps needed to configure Communication Manager to interoperate
with Integrated Research PROGNOSIS IP Telephony Manager. This includes creating a login
account and a SAT User Profile for PROGNOSIS to access Communication Manager and
enabling RTCP and CDR reporting. The steps are repeated for each Communication Manager
system, ESS and LSP Servers.
5.1. Configure SAT User Profile
A SAT User Profile specifies which SAT screens may be accessed by the user assigned the
profile and the type of access to each screen. As PROGNOSIS IP Telephony Manager does not
modify any system configuration, create a SAT User Profile with limited permissions to assign
to the PROGNOSIS login account.
Step
Description
1.
Enter the add user-profile ncommand, where nis the next unused profile number. Enter
a descriptive name for User Profile Name and enable all categories by setting the Enbl
field to y. In this configuration, the user profile 21 is created.
add user-profile 21 Page 1 of 41
USER PROFILE 21
User Profile Name: IPTM
This Profile is Disabled? n Shell Access? n
Facility Test Call Notification? n Acknowledgement Required? n
Grant Un-owned Permissions? n Extended Profile? n
Name Cat Enbl Name Cat Enbl
Adjuncts A y Routing and Dial Plan J y
Call Center B y Security K y
Features C y Servers L y
Hardware D y Stations M y
Hospitality E y System Parameters N y
IP F y Translations O y
Maintenance G y Trunking P y
Measurements and Performance H y Usage Q y
Remote Access I y User Access R y
JC; Reviewed:
SPOC 6/16/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
7 of 30
IPTM96-CM601
Step
Description
2.
On Pages 2 to 41 of the USER PROFILE forms, set the permissions of all objects to rm
(read and maintenance). This can be accomplished by typing rm into the field Set All
Permissions To. Submit the form to create the user profile.
add user-profile 21 Page 2 of 41
USER PROFILE 21
Set Permissions For Category: To: Set All Permissions To: rm
'-'=no access 'r'=list,display,status 'w'=add,change,remove+r 'm'=maintenance
Name Cat Perm
aar analysis J rm
aar digit-conversion J rm
aar route-chosen J rm
abbreviated-dialing 7103-buttons C rm
abbreviated-dialing enhanced C rm
abbreviated-dialing group C rm
abbreviated-dialing personal C rm
abbreviated-dialing system C rm
aca-parameters P rm
access-endpoints P rm
adjunct-names A rm
administered-connections C rm
aesvcs cti-link A rm
aesvcs interface A rm
JC; Reviewed:
SPOC 6/16/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
8 of 30
IPTM96-CM601
5.2. Configure Login Group
Create an Access-Profile Group to correspond to the SAT User Profile created in Section 5.1.
Step
Description
1.
Using a web browser, enter https://<IP address of Avaya Server> to connect to the Avaya
Server being configured and log in using appropriate credentials.
JC; Reviewed:
SPOC 6/16/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
9 of 30
IPTM96-CM601
Step
Description
2.
Click Administration > Server (Maintenance). This will open up the Server
Administration Interface that will allow the user to complete the configuration process.
JC; Reviewed:
SPOC 6/16/2011
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
10 of 30
IPTM96-CM601
Step
Description
3.
From the navigation panel on the left side, click Administrator Accounts under
Security. Select Add Group and click Submit.
Ce manuel convient aux modèles suivants
1
Table des matières
Autres manuels Avaya Logiciel
Avaya
Avaya IP Office Phone Manager Manuel utilisateur
Avaya
Avaya IP Office CTI Link Manuel
Avaya
Avaya one-X Quick Edition Manuel utilisateur
Avaya
Avaya IP Office Phone Manager Manuel utilisateur
Avaya
Avaya 40DHB0002USAR Manuel utilisateur
Avaya
Avaya OAISYS NetSuite 4.2 Supplément
Avaya
Avaya 4600 Series Manuel de service
Avaya
Avaya IP Office Phone Manager Manuel utilisateur
Avaya
Avaya Integrated Management Manuel technique
Avaya
Avaya IP Office 3.2 Manuel utilisateur
Avaya
Avaya IP Office (R3.0) Manuel utilisateur
Avaya
Avaya 3.7 Manuel utilisateur
Avaya
Avaya IP Office Phone Manager Supplément
Avaya
Avaya C460 SMON Manuel utilisateur
Avaya
Avaya CCM 3.1 Manuel utilisateur
Avaya
Avaya IP Office Phone Manager Supplément
Avaya
Avaya IP Agent Manuel utilisateur
Avaya
Avaya Interaction Center Manuel
Avaya
Avaya Unified Messenger Manuel utilisateur
Avaya
Avaya MultiVantage Manuel utilisateur
Manuels Logiciel populaires d'autres marques
Canon
Canon ZR950 Manuel utilisateur
Samsung
Samsung Auto Backup Manuel utilisateur
Polycom
Polycom Vortex EF2201 Instructions d'installation et d'utilisation
Brocade Communications Systems
Brocade Communications Systems Brocade 8/12c Manuel utilisateur
Novell
Novell SP2 - S Mode d’emploi
Lexmark
Lexmark Apps Manuel de service