Avaya PROGNOSIS IP Application Notes

Integrated research prognosis ip telephony manager 9.6 with avaya aura communication manager

Advertisement

Avaya Solution & Interoperability Test Lab
Application Notes for Integrated Research PROGNOSIS IP
Telephony Manager 9.6 with Avaya Aura® Communication
Manager - Issue 1.0
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
Abstract
Solution & Interoperability Test Lab Application Notes
©2011 Avaya Inc. All Rights Reserved.
1 of 30
IPTM96-CM601

Advertisement

Table of Contents
loading

Summary of Contents for Avaya PROGNOSIS IP

  • Page 1 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.
  • Page 2  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.
  • Page 3 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.
  • Page 4: Reference Configuration

    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.
  • Page 5: Equipment And Software Validated

    3.1 SP2 (H.323) or - 9630, 9640, 9650, 9670G 2.6 SP4 (SIP) Avaya 1608 IP telephones 1.300B (H.323) Avaya 6221 analog telephones JC; Reviewed: Solution & Interoperability Test Lab Application Notes 5 of 30 SPOC 6/16/2011 ©2011 Avaya Inc. All Rights Reserved. IPTM96-CM601...
  • Page 6: User Profile

    IP F Translations O Maintenance G Trunking P Measurements and Performance H Usage Q Remote Access I User Access R JC; Reviewed: Solution & Interoperability Test Lab Application Notes 6 of 30 SPOC 6/16/2011 ©2011 Avaya Inc. All Rights Reserved. IPTM96-CM601...
  • Page 7 C abbreviated-dialing system C aca-parameters P access-endpoints P adjunct-names A administered-connections C aesvcs cti-link A aesvcs interface A JC; Reviewed: Solution & Interoperability Test Lab Application Notes 7 of 30 SPOC 6/16/2011 ©2011 Avaya Inc. All Rights Reserved. IPTM96-CM601...
  • Page 8 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.
  • Page 9 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: Solution & Interoperability Test Lab Application Notes 9 of 30 SPOC 6/16/2011 ©2011 Avaya Inc. All Rights Reserved. IPTM96-CM601...
  • Page 10 3. From the navigation panel on the left side, click Administrator Accounts under Security. Select Add Group and click Submit. JC; Reviewed: Solution & Interoperability Test Lab Application Notes 10 of 30 SPOC 6/16/2011 ©2011 Avaya Inc. All Rights Reserved. IPTM96-CM601...
  • Page 11 Section 5.1 Step 1. Click Submit. This completes the creation of the login group. JC; Reviewed: Solution & Interoperability Test Lab Application Notes 11 of 30 SPOC 6/16/2011 ©2011 Avaya Inc. All Rights Reserved. IPTM96-CM601...
  • Page 12 1. From the navigation panel on the left side, click Administrator Accounts. Select Add Login and SAT Access Only to create a new login account with SAT access privileges only. Click Submit. JC; Reviewed: Solution & Interoperability Test Lab Application Notes 12 of 30 SPOC 6/16/2011 ©2011 Avaya Inc. All Rights Reserved. IPTM96-CM601...
  • Page 13  Force password/key change on next login: Select No Click Submit to continue. This completes the configuration of the login. JC; Reviewed: Solution & Interoperability Test Lab Application Notes 13 of 30 SPOC 6/16/2011 ©2011 Avaya Inc. All Rights Reserved. IPTM96-CM601...
  • Page 14: Media Gateway

    Use Default Server Parameters? Y 3. Repeat Step 2 for all IP network regions that are required to be monitored. JC; Reviewed: Solution & Interoperability Test Lab Application Notes 14 of 30 SPOC 6/16/2011 ©2011 Avaya Inc. All Rights Reserved. IPTM96-CM601...
  • Page 15 Step Description 1. Enter the change ip-interface procr command to enable the processor-ethernet interface on the Avaya Server. Set Enable Interface to y. This interface will be used by Communication Manager to send out the CDR information. change ip-interface procr...
  • Page 16  Remote Port: 50000 [Note: The Remote Port may be set to a value between 5000 and 64500 inclusive. 50000 is the default port number used by PROGNOSIS and the PROGNOSIS server uses the same port number for all Avaya Servers sending CDR information to it.]...
  • Page 17 Record Call-Assoc TSC? n Digits to Record for Outgoing Calls: dialed Privacy - Digits to Hide: 0 CDR Account Code Length: 15 JC; Reviewed: Solution & Interoperability Test Lab Application Notes 17 of 30 SPOC 6/16/2011 ©2011 Avaya Inc. All Rights Reserved. IPTM96-CM601...
  • Page 18: Intra-Switch Cdr

    Queue Length: 0 Service Type: tie Auth Code? n Member Assignment Method: auto Signaling Group: 6 Number of Members: 20 JC; Reviewed: Solution & Interoperability Test Lab Application Notes 18 of 30 SPOC 6/16/2011 ©2011 Avaya Inc. All Rights Reserved. IPTM96-CM601...
  • Page 19 2. To configure the Communication Manager systems to be monitored, expand Configurations of the Monitoring Node, right-click on AVAYA_PBX and select Properties. JC; Reviewed: Solution & Interoperability Test Lab Application Notes 19 of 30 SPOC 6/16/2011 ©2011 Avaya Inc. All Rights Reserved. IPTM96-CM601...
  • Page 20 Manager systems with the names AVAYAHQ and SYSB-PBX and with the IP addresses of the Avaya Servers 10.1.10.230 and 10.1.60.10 respectively. The PROGNOSIS Monitoring Node will use SSH to connect to port 5022 of the Avaya Servers. ADD PBX ( \AVAYAHQ, ip=10.1.10.230 ) ADD PBX ( \SYSB-PBX, ip=10.1.60.10 )
  • Page 21 4. To configure the ESS and LSP Servers to be monitored, expand Configurations of the Monitoring Node, right-click on AVAYA_LSP and select Properties. JC; Reviewed: Solution & Interoperability Test Lab Application Notes 21 of 30 SPOC 6/16/2011 ©2011 Avaya Inc. All Rights Reserved. IPTM96-CM601...
  • Page 22 ADD LSP ( LSPREMOTE2, ip=10.1.40.10, primary-controller=\AVAYAHQ ) ADD LSP ( ESS1, ip=10.1.10.239, primary-controller=\AVAYAHQ ) Click Start to proceed. JC; Reviewed: Solution & Interoperability Test Lab Application Notes 22 of 30 SPOC 6/16/2011 ©2011 Avaya Inc. All Rights Reserved. IPTM96-CM601...
  • Page 23 6. To configure the SAT login account and password, expand Configurations of the Monitoring Node, right-click on PASSWORDS and select Properties. JC; Reviewed: Solution & Interoperability Test Lab Application Notes 23 of 30 SPOC 6/16/2011 ©2011 Avaya Inc. All Rights Reserved. IPTM96-CM601...
  • Page 24 7. Click the + ‘plus’ button to add a new password entry for each of the configured systems in Steps 3 and 5. The Entry Name must be of the form Avaya-SAT:<pbx-name>. For the system with the name AVAYAHQ, enter Avaya-SAT:AVAYAHQ for Entry Name, uncheck Password Only, and enter the login account created in Section 5.3 for...
  • Page 25: Verification Steps

    0000/00/00 00:00:00 Forward Seq. No: 0 Backward Seq. No: 0 CDR Buffer % Full: 0.00 0.00 Reason Code: OK JC; Reviewed: Solution & Interoperability Test Lab Application Notes 25 of 30 SPOC 6/16/2011 ©2011 Avaya Inc. All Rights Reserved. IPTM96-CM601...
  • Page 26 1. After logging into PROGNOSIS GUI, click on the Home button on the toolbar to display the Welcome screen. In the Monitor section, click Avaya CM > Monitor PBXs to display the list of Communication Manager Servers configured in Section 6.
  • Page 27 Step Description 2. In the Avaya Systems page, verify that the SAT field for each configured Communication Manager shows 3 connections. JC; Reviewed: Solution & Interoperability Test Lab Application Notes 27 of 30 SPOC 6/16/2011 ©2011 Avaya Inc. All Rights Reserved.
  • Page 28 Step Description 3. Make a call between two Avaya IP telephones that belong to an IP Network Region that has been configured to send RTCP information to the PROGNOSIS server. Verify that the Voice Streams section shows two active voice streams reflecting the quality of the call.
  • Page 29: Additional References

    9. Additional References [1] Avaya Aura™ Communication Manager Feature Description and Implementation, Release 6.0, Issue 8.0, June 2010, Document Number 555-245-205. [2] Administering Avaya Aura Communication Manager, June 2010, Release 6.0, Issue 6.0, Document Number 03-300509. The following PROGNOSIS documents are provided by Integrated Research.
  • Page 30 2011 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.

This manual is also suitable for:

Aura communication manager 6.0.1

Table of Contents