Avaya IP Telephony

As an administrator, you can configure attributes listed in the table given here for monitoring the Avaya IP telephony infrastructure discovered on the network. This topic includes the following sections:

• Configure Call Monitoring
• Configure Data Access
• Configure Discovery Settings for Avaya Primary Servers
• Configure IP Phones
• Configure Polling
• Configure Reporting

To access the administration console:

1. Log on to the NNMi console as an administrator.
2. From the Workspaces navigation pane, click Configuration > iSPI for IP Telephony Configuration > Avaya Configuration. The administration console for Avaya IP telephony appears.

The administration console displays configuration options for the following attributes:

Attribute	Description
Call Monitoring	Allows you to configure the call monitoring options of Avaya IP Telephony devices. You can also use this option to view the existing call monitoring configurations.
Data Access	Allows you to configure the NNM iSPI for IP Telephony to access the various categories of management data from the Avaya IP Telephony servers in your deployment environment. You can also use this option to view the existing data access configurations.
Discovery	Allows you to configure the discovery settings for the Avaya primary servers. You can also use this option to view the existing discovery configurations.
IP Phone	Allows you to configure tasks such as specifying the range of IP phones to be excluded from monitoring and enable the custom attributes for the Avaya IP Phones. You can also use this option to view the existing configurations.
Polling	Allows you to configure the polling options of Avaya IP Telephony device states and statistics. You can also use this option to view the existing polling configurations.
Reporting	Allows you to configure the different types of reports for the Avaya IP Telephony network such as Call Details Record (CDR), Phone Media Access Control (MAC), Port Network Load, and Route Pattern Usage. You can also use this option to view the existing reporting configurations.

Configure Call Monitoring

You can use the NNMi Avaya Call Monitoring Configuration form to configure the following:

• Monitor the voice QOS metrics and MOS values for calls in the Avaya IP Telephony network
• The termination cause codes that need to be monitored for a specific call in the Avaya IP Telephony network

Configure the QOS/MOS Threshold Values

The Call Monitoring Configuration link on the Avaya Configuration pane enables you to configure the monitoring of voice QOS metrics and MOS values for calls in the Avaya IP Telephony network. The Thresholds for QOS/MOS Monitoring tab on the NNMi Avaya Call Monitoring Configuration form allows you to specify the threshold values. On violation of set threshold for any of these parameters for any monitored call, the NNMi generates an incident conveying the resulting values and the set threshold.

To configure the QOS/MOS monitoring threshold values for Avaya IP telephony calls:

1. On the NNMi Avaya Configuration console, click Call Monitoring Configuration. The NNMi Avaya Call Monitoring Configuration form opens.
2. Click the Thresholds for QOS/MOS Monitoring tab. The Thresholds for QOS/MOS Monitoring tab page opens.

3. Specify the required details in the fields provided under the Thresholds for QOS/MOS Monitoring section of the page. The following table describes the fields that appear under the section:

   By default, no threshold values are set for these parameters and threshold-based monitoring is disabled. You can enable monitoring and incident generation when you specify the valid threshold values.

   QOS/MOS Monitoring Parameter	Description
   1Jitter	The jitter threshold (in milliseconds) to be configured.
   1PPL	The Percentage Packet Loss (PPL) threshold to be configured. For example, to specify a percentage packet loss threshold of 50%, type 50.
   1Latency	The latency (in milliseconds) threshold to be configured.
   1Avg MOS	The average Mean Opinion Source (MOS) value to be configured. This value must be within the range of 0.0 to 5.0.

   ¹To disable the monitoring, specify 0.0.

4. Click Apply Changes. The NNMi updates the QOS/MOS monitoring configuration values.

Configure Communication Manager

The Add Communication Manager Specific QOS Configuration section on the Thresholds for QOS/MOS Monitoring tab page enables you to configure QOS and MOS monitoring threshold values for the specific Communication Manager (CM) of your choice. After you specify threshold values specific to a CM, the NNMi lists these threshold values in the Current Configurations section and uses them for the specific CM, instead of the threshold values specified in the Thresholds for QOS/MOS Monitoring section.

To configure Communication Manager—specific QOS and MOS monitoring threshold values:

1. On the Thresholds for QOS/MOS Monitoring tab page, go to Communication Manager Specific Thresholds for QOS/MOS Monitoring pane > Add Communication Manager Specific QOS Configuration section.

2. Under the Add Communication Manager Specific QOS Configuration section, specify the required details in the fields provided. The following table describes the fields under the section:

   Field Name	Description
   CM IP Address	The remote IP address of the Communication Manager. Make sure that you specify the same IP address that you provided while configuring the data access for RTCP reception for Avaya IP Telephony. If your network supports Network Address Translation (NAT) or Port Address Translation (PAT), specify the external IP address (public address) here.
   Jitter	The jitter threshold (in milliseconds) to be configured for the CM.
   PPL	The Percentage Packet Loss (PPL) threshold to be configured for the cluster. For example, to specify a percentage packet loss threshold of 50%, type 50.
   Latency	The latency threshold (in milliseconds) to be configured for the CM.
   Avg MOS	The average Mean Opinion Source (MOS) value to be configured for the CM. This value must be within the range of 0.0 to 5.0.

   For more information about the QOS and MOS monitoring parameters, see Configuring the QOS and MOS Threshold Values for Call Monitoring.

3. Click Add/Modify. This adds the configuration for the CM in the Current Configurations section.

To modify Communication Manager Specific QOS and MOS monitoring threshold values:

1. From the Current Configurations section, select the CM-specific configuration that you want to modify .
2. Click Modify.
3. In the Add Communication Manager Specific QOS Configuration section, make the required changes. You cannot modify the CM IP Address value.
4. Click Add/Modify. The CM-specific configuration is updated with the new values.

To delete Communication Manager Specific QOS and MOS monitoring threshold values:

1. From the Current Configurations section, select the CM-specific configuration that you want to delete.
2. Click Delete. The CM-specific threshold values for the CM are deleted. After removing the CM-specific threshold value configuration, the NNMi uses the values you provided in the system-wide Thresholds for QOS/MOS Monitoring section.

To export configurations to the Global Manager:

• Click Export All Config to Global Manager. This sends all the available configuration information listed in the Current Configuration section, irrespective of the check boxes selected, to the Global Manager. If a global manager is not configured, the NNMi does not populate any data.

Configure the Call Termination Cause Codes to be Monitored

The Call Monitoring Configuration link on the Avaya Configuration pane enables you to configure the termination cause codes that need to be monitored for a specific call in the Avaya IP Telephony network. If there are a number of unprocessed Call Details Records (CDRs) in the Communication Manager, configuring the cause codes, before configuring CDR data access, can generate several incidents.

You can specify the following types of call termination cause codes:

• Success Cause Codes: Lists the cause codes for call terminations that occurred without a call failure. For example, 'Long Duration Call', 'Intraswitch call'.
• Failure Cause Codes: Lists the cause codes for call terminations that occurred due to a call failure. For example, 'Destination Busy', 'Facilities Unavailable'.

After you specify the codes that you want to be monitored, the NNMi generates the CallTerminationReason incident only when the call termination occurs due to one of the specified call termination cause codes.

To configure the monitoring of call termination cause codes:

1. On the NNMi Avaya Configuration console, click Call Monitoring Configuration. The NNMi Avaya Call Monitoring Configuration form opens.
2. Click the Call Termination Cause Monitoring tab. The Call Termination Cause Monitoring tab page opens.
3. From the types of call termination cause codes sections, select the codes that you want to monitor, and then click (the Move Items to Selected List icon). The sections displayed are:
• Success Cause Codes
• Failure Cause Codes
• To select multiple random cause codes, press the Ctrl key and select the required codes.
• To select a series of cause codes, press the Shift key and the select the series of cause codes.
• To move a selected cause code from the monitored cause code list back to the cause code selection list, select the cause code and click ( the Move Items to Non-selected List icon).
The default version of the property file — avaya-cdr-termination-cause-codes.properties — is available in the following directory:
• %NNMDataDir%\\shared\\ipt\\conf\avaya

The property file can be used to add new termination cause codes that are not listed in the types of call termination cause codes section. After you add a new termination cause code, make sure to restart the IPT jboss application server to reflect the change.

4. Click Apply to complete the configuration.

Configure Data Access

You can use the NNMi Avaya Data Access Configuration form to configure the following types of data for Avaya IP telephony:

• Call Details Record (CDR)
• RTP Control Protocol (RTCP) Reception
• Secure Shell (SSH)

You can also use this form to modify or delete an existing data access point.

Access the CDR Data

You can use the NNMi Data Access Configuration form to configure the CDR data access for Avaya. Configuring the data access for Avaya with CDR enables the NNMi to provide the following reports:

• Avaya IP Telephony CDR reports
• Avaya IP Telephony Call Types and Termination Reasons reports
• Avaya IP Telephony Trunk Activity reports
• Avaya IP Telephony Media Gateway Call reports

To configure CDR access for Avaya:

1. On the NNMi Avaya Configuration console, click Data Access Configuration. The NNMi Avaya Data Access Configuration form opens.
2. Click the CDR Access tab.
3. In the Add/Modify CDR Access Configuration section, specify the required details in the fields provided on the page. The following table describes the fields on the page:

   Field Name	Description
   CM IP Address	Indicates the IP address of the Communication Manager server from which the NNMi can download the CDR files.If the primary CM is deployed in duplex redundant pair, this is not the virtual or active IP address of the primary CM; this is the IP address of one of the two physical CM servers in duplex pair. If your network supports Network Address Translation (NAT) or Port Address Translation (PAT), you must specify the external IP address (public address) here.
   CDR Format	Indicates the CDR format configured on the Communication Manager server. See the CDR system parameters configuration settings on your Avaya CM to select the correct format.If the CDR Format on the primary Server is Customized, then the CustomizedCDRFormat.properties file can be used the specify the CDR fields and its offsets. If the CDR Format on the primary server is Customized, you can use the CustomizedCDRFormat.properties file to specify the CDR fields and the offsets. For more information about creating a customized CDR file format, see Creating a Customized File.
   Circuit ID Modified	Select True, if the CDR format chosen on the Communication Manager server is in one of the following formats and if the Communication Manager server is configured to write the modified circuit ID (Trunk Group Member Number) in the CDR records: 59 character Printer TELESEER ISDN-Printer ISDN-TELESEER Check the CDR system parameters configuration settings on your Avaya CM and make sure that you choose the correct settings here.
   Date Format	If you select a Customized CDR format, then specify the format of the date strings in the CDR records according to the configuration you specified for the date format in the communication manager server configuration. You can select DDMM or MMDD. DD specifies the date and MM specifies the numeric month. See the CDR system parameters configuration settings on your Avaya CM and select the same date format configured there.
   Format Specification File Path	If you select a Customized CDR format, then specify the absolute path of the customized CDR format specification file on the NNMi server. You must prepare this file for each communication manager server before configuring the NNMi for accessing CDR data from each communication manager server. For more information about creating the customized CDR format specification file, see Creating Customized CDR Format Specification File. You can use the same customized CDR format specification file for all Avaya CMs in your environment only when you are sure that the CDR formats are same for all Avaya CMs. If you have two or more Avaya CMs with different customized CDR formats, you must create distinct customized CDR format specification files on the NNMi system for each Avaya CM and specify the absolute path to the customized CDR format specification file. See the CDR system parameters configuration settings on all Avaya CMs to verify the CDR formats on the CMs.
   Time Zone	Select the time zone of the Avaya CM from the list.
   Configured for Survivability	Select True if file- based or survivable CDRs are configured on the communication manager for which you are specifying CDR data access configuration. Select False if CDR streaming using Reliable Session Protocol (RSP) is configured on the communication manager for which you are specifying CDR data access configuration. See the CDR system parameters configuration settings on your Avaya CM to select the correct choice. If Survivability or file based CDR is configured, you must create one more data access configuration entry for the IP address of the other physical Avaya CM server if the primary CM is a duplex redundant pair of servers. If survivability or file based CDR is not configured and CDR streaming using RSP is configured on the Avaya CM, a single data access configuration using physical IP address of one of the two CM servers in duplex redundant pair would suffice. If you select True for this option, you must provide the Secure File Transfer Protocol (SFTP) credentials to be used by NNMi to download the CDR files programmatically: SFTP User Name: Type the SFTP user name to be used for CDR downloads. Check the Avaya CM web based administration to know the correct user name to be used for CDR access. SFTP Password: Type the SFTP password for the user name specified. If you select False for this option, you must specify the following information to configure CDR data access using RSP: CDR Port Number: Type the CDR port number configured on the Avaya CM. Check the CDR IP services configuration on the Avaya CM to determine the CDR port number configured on the CM. You must provide the same port number configured in the Remote Port field of the CDR IP services configurations screen on the CM. RSP Connectivity Timer: Type the RSP Connectivity Timer value configured on the Avaya Communication Manager. Check CDR IP services configuration on the Avaya CM to determine the value configured on the CM. You must provide the same value configured in the Connectivity Timer field of the CDR IP Services configurations screen on the CM. RSP Packet Response Timer: Type the RSP Packet Response Timer value. Check CDR IP services configuration on the Avaya CM to determine the value configured on the CM. You must provide twice the value specified in the Packet Response Timer field in CDR IP Services configurations screen on the CM. Is CDR data sent through a CLAN or Processor Ethernet or any other IP node configured on Avaya CM?: Select No if the CDR data is sent directly from the physical Avaya CM. Select Yes if the CDR data is sent through a CLAN, Processor, Ethernet, or any other IP node. You must specify the following information if you select Yes for this option: IP Address of remote IP Node: The IP address of CLAN, Processor, Ethernet, or any other IP node through which the CDR data is sent. Make sure that you provide the IP address of the same node that is configured for this purpose in the Avaya CM. Check CDR IP services configuration and IP node names configurations done on the Avaya CM to determine the IP address of the remote node. The name of this IPv4 node appears as local node on the CDR IP services configuration screen of the CM. You can ascertain the IP address of this IPv4 node by checking the IP node names configurations on the Avaya CM. If Survivability or file based CDR is configured, you must create entry for the IP address of the other physical Avaya CM server if the primary CM is a duplex redundant pair of servers.If survivability or file based CDR is not configured and CDR streaming using RSP is configured on the Avaya CM, a single data access configuration using physical IP address of one of the two CM servers in duplex redundant pair would suffice.

4. Click Add/Modify. The Current Configurations section lists the details of the Communication Managers configured for CDR access.

To modify an Avaya IP Telephony CDR access configuration:

1. On the NNMi Avaya Data Access Configuration form, from the Current Configurations section of the CDR Access tab, select the configuration that you want to modify.
2. Click Modify .
3. In the Add/Modify CDR Access Configuration section, make the required changes. You cannot modify the CM IP Address value.
4. Click Add/Modify. The modified configuration is listed in the Current Configurations section.

To delete an Avaya IP Telephony CDR access configuration:

1. On the NNMi Avaya Data Access Configuration page, from the Current Configurations section of the CDR Access tab, select the configuration that you want to delete.
2. Click Delete. The selected configuration is deleted from the Current Configurations section.

Create Customized CDR Format Specification Files

If the format for the CDR is specified as customized in the Communication Manager server, you must create a format specification file that provides the CDR parsing information to the NNMi. This file must include the field names along with the respective offsets in the CDR. The file must display the result for the command display system-parameters cdr run on the Communication Manager server as shown in the Sample Customized CDR Format Specification section. The NNMi includes a sample customized CDR format specification file at the following location:

• %NNM_DATA_DIR%/shared/ipt/conf/CustomizedCDRFormat.properties ( the %NNM_DATA_DIR% represents the NNMi data directory in your NNMi deployment environment)

Sample Customized CDR Format Specification

# This file is for specifying customized Avaya CDR records format.

# Line starting with # is ignored.

# Each line contains one field name and its position in CDR file.

# If a fields length is more than one character, the start and end position

# must be separated using "-" (hyphen).

# IMPORTANT: The positioning starts with 0.

# Examples:

# Dialed Number= 9-16 => Dialed number field starts at position 10 and ends at 17.

# cond-code = 18 => Condition code is one character available at position 19 in CDR file.

date=0-5

code-dial=20-23

code-used=25 - 28

calling-num=49-63

# in-TAC is incoming Trunk Access Code

clg-num/in-tac=100-114

dialed-num=30-47

cond-code=18 #Condition code is one character

duration=

sec-dur=12-16

in-crt-id=78-80

in-trk-code=65-68

out-crt-id=82-84

# Time is HHMM format in 4 digits

time=7-10

auth-code=70-76

acct-code=

Configure RTCP Reception

You can use the NNMi Data Access Configuration form to configure the RTP Control Protocol (RTCP) reception Configuration for Avaya.

Configuring RTCP reception for Avaya enables the NNMi to provide the following features:

• Monitoring Voice Quality: Graph Average MOS
• Monitoring Voice Quality: Graph Average Packet Loss
• Monitoring Voice Quality: Graph Jitter
• Monitoring Voice Quality: Graph Latency

• Avaya IP Telephony RTP Session Metrics reports

To configure RTCP access for Avaya:

1. On the NNMi Avaya Configuration console, click Data Access Configuration. The NNMi Avaya Data Access Configuration form opens.
2. Click the RTCP Reception tab.
3. In the Add/Modify RTCP Reception Configuration section, specify the required details in the fields provided on the page. The following table describes the fields on the page:

Field Name	Description
Enable Reception	Select this check box to enable the NNMi to receive and process the RTCP packets.
Vendor	Indicates the name of the vendor for the RTCP reception configuration.
Sender Type	Indicates the type of the sender.
IP address on iSPI for IP Telephony system	Indicates the IP address of the NNMi server where you want to receive RTCP packets from the Avaya end points controlled by the Communication Manager. If your network supports Network Address Translation (NAT) or Port Address Translation (PAT), you must specify the external (public) IP address here.
Type of IP address on iSPI for IP Telephony system	Indicates the IP address type for the NNMi server. Only IPv4 addresses are currently supported.
UDP Port on iSPI for IP Telephony system	Indicates the port number on the NNMi server where you want to receive RTCP packets from the Avaya end points controlled by the Communication Manager. Ensure that you enable the RTCP port on the firewalls of the networks hosting NNMi, Avaya Communication Manager, and the IP phones. Ensure that you configure NNMi server as an endpoint and RTCP receiver in Avaya Communication Manager.
IP Address of the Communication Manager	Indicates the remote IP address of the Communications Manager. If your network supports Network Address Translation (NAT) or Port Address Translation (PAT), you must specify the external IP address (public address) here.
Type of IP address of the Communication Manager	Indicates the remote IP address type of the Communications Manager.
Tenant	Indicates the name of the tenant. You can select the name of the tenant from the drop-down list.
Enable Reporting	Select this check box to configure the NNMi to start generating the reports for RTP session metrics.

• You must specify all the details listed to set up an RTCP reception configuration.
• Make sure that you perform the required configuration on the Avaya Communication Manager Server administration tool to specify the listed local IP address and the local port to be the destination of the RTCP packets sent by the end points (IP Phones, H248 Media Gateways, MedPros) configured on the Communication Manager. For more details on the configuration, see the Avaya documentation
• Make sure that the RTCP reception is configured for the end points on the communication manager that is seeded on the same NNMi server . Do not configure reception of RTCP from communication manager end points unless the communication manager is also seeded on the NNMi server. For more information on partitioning of RTCP reception across different NNMi regional manager instances in a GNM environment, see the NNMi Deployment Guide.
4. Click Add/Modify. The Current Configurations section lists the details of the Communication Managers configured for RTCP Reception.

To modify an Avaya IP Telephony RTCP reception configuration:

1. On the NNMi Avaya Data Access Configuration form, from the Current Configurations section of the RTCP Reception tab, select the configuration that you want to modify.
2. Click Modify .

3. In the Add/Modify RTCP Reception Configuration section, select or deselect the Enable Reception and the Enable Reporting check boxes.You cannot modify the other details.

4. Click Add/Modify. The modified configuration is listed in the Current Configurations section.

To delete an RTCP reception configuration:

1. On the NNMi Avaya Data Access Configuration form, from the Current Configurations section of the RTCP Reception tab, select the configuration that you want to delete.
2. Click Delete . The selected configuration is deleted from the Current Configurations section.

Configure SSH Access

You can use the NNMi Data Access Configuration form to configure the required Secure Shell (SSH) access details for Avaya. You must configure these details for all the Communication Manager servers in your deployment environment including the standby duplex servers. You can configure the SSH access details by adding the physical IP addresses and the associated credentials for SSH access for all the servers.

Configuring SSH access for Avaya enables the NNMi to discover and poll the IP addresses for Avaya IP phones.

To configure the SSH access details for Avaya:

1. On the NNMi Avaya Configuration console, click Data Access Configuration. The NNMi Avaya Data Access Configuration form opens.
2. Click the SSH Access tab.
3. In the Add/Modify SSH Configuration section, specify the required details in the fields provided on the page. The following table describes the fields on the page:

Field Name	Description
CM IP Address	Indicates the IP address of the Communication Manager server. If your network supports Network Address Translation (NAT) or Port Address Translation (PAT), you must specify the external IP address (public address) here.
SSH Type	Indicates the type of application used to access data on the primary communication manager server. The NNMi currently supports only System Access Terminal (SAT) application. You cannot edit the value in this box.
User Name	Indicates the SSH user name to log on to the primary Communication Manager server.
Password	Indicates the password for the user name specified.
SSH Port	Indicates the port number on the primary Communication Manager server to which SSH connections can be established from the NNMi server.
SSH Timeout	Indicates the number of seconds to wait while attempting to execute a command, before canceling the attempt and generating an error.
Host Key	Indicates the host key of the primary Communication Manager server. The NNMi supports RSA Level 2 key. An example of RSA Level 2 key is 44 ec ab bc a4 2b a7 47 c5 b0 f4 5a 6f ef 97 d4 (do not specify the bit length of the host key). Contact your administrator of the primary communication manager server to know your RSA Level 2 key.

4. Click Add/Modify. The Current Configurations section lists all the signaling servers configured for SSH access.

To modify an SSH access configuration for Avaya:

1. On the NNMi Avaya Data Access Configuration form, from the Current Configurations section of the SSH Access tab, select the configuration that you want to modify.
2. Click Modify.
3. In the Add/Modify SSH Configuration section, make the required changes. You cannot modify the CM IP Address and the SSH Port values.
4. Click Add/Modify. The modified configuration is listed in the Current Configurations section.

To delete an SSH access configuration for Avaya:

1. On the NNMi Avaya Data Access Configuration form, from the Current Configurations section of the SSH Access tab, select the configuration that you want to delete.
2. Click Delete. The selected configuration is deleted from the Current Configurations section.

Configure Discovery Settings for Avaya Primary Servers

Configure Discovery Cycle

By default, NNMi discovers nodes every 24 hours to identify the changes on your network. This includes the discovery of the IP telephony nodes. The discovery of the Avaya primary servers every 24 hours might result in high system resource utilization, which can impact the call processing.

Keep the Avaya primary server discovery interval at a value that is greater than the default discovery cycle for NNMi. The default recommended discovery interval for the Avaya primary servers is 90 days (2160 hours) if there are no configuration changes on the Avaya primary servers. If you have made any changes on the network, you can do a configuration poll manually at any time to rediscover the primary servers.

To configure the discovery cycle for Avaya primary servers:

1. On the NNM iSPI for IP Telephony Avaya Configuration console, click Discovery Configuration. The NNM iSPI for IP Telephony Avaya Discovery Configuration form opens.
2. In the Primary Servers section, specify the required details in the fields provided on the page. The following table describes the fields on the page:

   Field Name	Description
   Use NNMi node discovery interval	Clear the check box. This check box is selected by default. If you select this check box, NNMi runs the discovery process for the Avaya primary server according to the discovery interval configured for NNMi. You must always keep this check box selected before you do a configuration poll manually. You must clear this check box to type a different discovery interval.
   Discovery Interval	Indicates the discovery interval (in hours). The default interval is 2160 hours (90 days). The NNM iSPI for IP Telephony does a periodic discovery of Avaya primary servers based on this interval.
   Pause state pollers during discovery	Select this check box to pause the state pollers on a node till the discovery cycle completes for the node. This helps in reducing the system resource usage during discovery. By default, the NNM iSPI for IP Telephony does not pause the state pollers during discovery. Before you pause the state pollers, you must consider the following points: If you pause the state pollers, the state pollers do not trigger SNMP collection on a node that is being discovered. The NNM iSPI for IP Telephony does not generate any incidents for some of the state changes on a node during its discovery. For any state changes for the following entities, the NNM iSPI for IP Telephony does not update the management console with the relevant information: Primary Servers State IP Phone Registration State IPSI Service State MedPros Control Link state & Ethernet Link State Port Network Load Route Pattern Usage Trunk Group Usage DSP Resource Codec Signaling Group Service CM Processor Occupancy

3. Click Apply Changes.

Configure IP Phones

You can use the NNMi Avaya IP Phone Configuration form to configure the following:

• The range of IP Phone extensions to be excluded from monitoring
• The list of IP Phones to be included for generating incidents at the Registration State Change
• The custom attribute settings for the IP Phones

You can also use this form to modify or delete an existing configuration.

Exclude Avaya Phones from Monitoring

You can specify the range of extensions for phones to be excluded from being monitored for Avaya IP telephony network. After you specify the range of extensions for Avaya, the NNMi stops monitoring the specified phones. These phones are still discovered in the subsequent discovery cycles, but not shown on the inventory views.

To specify the range of extensions for Avaya phones to be excluded:

1. On the NNMi Avaya Configuration console, click IP Phone Configuration. The NNMi Avaya IP Phone Configuration form opens.
2. In the Exclusion Configuration > Add/Modify IP Phone Exclusion Filter section, specify the required details in the fields provided on the page. The following table describes the fields on the page:

   Field Name	Description
   CM IP Address	Indicates the IP address of the Communication Manager for which you want to specify the list of phones to be excluded. If your network supports Network Address Translation (NAT) or Port Address Translation (PAT), you must specify the external IP address (public address) here.
   Filter	Indicates the IP phones extension range to be excluded. To specify the range of phones to be excluded, follow these points: Use the hyphen (-) to specify a range of extensions to be excluded. For example, if you want to exclude extensions from 8000 to 8005, you can specify as 8000-8005 in the Filter field. Use asterisk (*), the wildcard character, to specify a set of extensions. For example, if you want to exclude all the extensions that start with 8, you can specify as 8* in the Filter field. Use question mark (?), the wildcard character, to specify extensions that contain specific numerals at specific locations in the extension. For example, if you want to exclude all the extensions that end with 00, you can specify as ???00 in the Filter field.

3. Click Add/Modify. The configured communication managers for which you want to exclude the list of phones are listed in the Current Configurations section.

To modify a specified range of Avaya extensions to be excluded:

1. On the Exclusion Configuration section of the NNMi Avaya IP Phone Configuration form, from the Current Configurations section, select the configuration that want to modify.
2. Click Modify.
3. In the Add/Modify IP Phone Exclusion Filter section, make the required changes. You cannot modify the CM IP Address value.
4. Click Add/Modify. The modified configuration is listed in the Current Configurations section.

To delete a specified range of Avaya extensions to be excluded:

1. On the Exclusion Configuration section of the NNMi Avaya IP Phone Configuration form, from the Current Configurations section, select the configuration that want to delete.
2. Click Delete. The selected configuration is deleted from the Current Configurations section.

IP Phones for Registration State Change Incident Generation

You can specify a list of IP phones for which the registration state change incident must be generated. You can specify the range based on the Communication Manager that includes the IP phones.

To specify the list of Avaya IP phones for registration state change incident generation:

1. From the Workspaces navigation pane, iSPI for IP Telephony Configuration...> Avaya Configuration. The NNMi Avaya Configuration Console opens.
2. Click IP Phone Configuration. The NNMi Avaya IP Phone Configuration form opens.
3. In the Inclusion Configuration > Add/Modify Filters for IP Phones for which Registration State Change Incidents are to be Generated section, specify the required details in the fields provided on the page. The following table describes the fields on the page:

   Field Name	Description
   CM IP Address	Indicates the IP address of the Communications Manager that includes the list of phones for which the registration state change incident must be generated.
   Filter	Indicates the extension range to be included. For more information about the extension range, see Specifying the Range of Extensions for Avaya Phones to be Excluded from Monitoring.

4. Click Add/Modify. The Current Configurations section lists the configured Communication Managers for which you want to generate the incident for registration state changes.

You can select a CM IP address from the list and click Modify to modify the existing configuration. However, you cannot modify the CM IP Address value.

You can select a CM IP address and click Delete to delete the existing configuration.

To modify an existing Inclusion Configuration:

1. On the Inclusion Configuration section of the NNMi Avaya IP Phone Configuration form, from the Current Configurations section, select the configuration that want to modify.
2. Click Modify.
3. In the Add/Modify Filters for IP Phones for which Registration State Change Incidents are to be Generated section, make the required changes.
4. Click Add/Modify. The modified configuration is listed in the Current Configurations section.

To delete an existing Inclusion Configuration:

1. On the Inclusion Configuration section of the NNMi Avaya IP Phone Configuration form, from the Current Configurations section, select the configuration that want to delete.
2. Click Delete. The selected configuration is deleted from the Current Configurations section.

Configure IP Phones Custom Attribute Settings

You can use the NNMi Avaya IP Phone Configuration form to configure the custom attributes settings for the IP Phones. You may enable the custom attributes for the Avaya IP Phones only if these phones are already discovered and stored in the NNMi database. After you enable the custom attributes for Avaya IP Phones, you can see the phone icons for all the discovered Avaya IP Phones in the NNMi topology maps.

To enable the custom attributes for Avaya IP Phones:

1. From the Workspaces navigation pane, click Configuration > iSPI for IP Telephony Configuration > Avaya Configuration. The NNMi Avaya Configuration Console opens.
2. Click IP Phone Configuration. The NNMi Avaya IP Phone Configuration form opens.
3. In the Discovery Configuration section, select the Enable Phone Custom Attribute Setting check box.
4. Click Apply Changes.

Configure Polling

You can use the NNM iSPI for IP Telephony Avaya Polling Configuration form to enable polling and set intervals for various pollers that are grouped based on the target to be polled. The pollers are grouped as follows:

• Communication Manager Polling to poll the Avaya Communication Managers
• Media Gateway Polling to poll the Avaya Media Gateways

Configure the Communication Manager Polling

To configure the polling of a Communication Manager:

1. On the NNM iSPI for IP Telephony Avaya Configuration console, click Polling Configuration. The NNM iSPI for IP Telephony Avaya Polling Configuration form opens.
2. In the Communication Manager Polling section, specify the required details in the fields provided on the page. The following table describes the fields on the page:

   Field Name	Description
   Configuration for CLAN and IP Phone Association Monitoring	Allows you to configure the continuous polling of the association between the Avaya IP Phones and the Avaya Control LAN (CLAN) on the network. The available options are as follows: Enable Polling: Select this check box to enable the polling of the CLAN to find the CLAN and IP Phone association. Interval: Indicates the interval (in seconds) to poll the CLAN. The default value is 300 seconds.
   Configuration for IP Phones Registration State Monitoring	Allows you to configure the continuous polling of the registration state change of the Avaya IP Phones on your network. The available options are as follows: Enable Polling: Select this check box to enable the polling of the Avaya IP Phones. Interval: Indicates the interval (in seconds) to poll the Avaya IP Phones. The default value is 300 seconds.
   Configuration for IP Phones IP Address Change Monitoring	Allows you to configure the continuous polling of the IP address change of the Avaya IP Phones on your network. The available options are as follows: Enable Polling: Select this check box to enable the polling of the Avaya IP Phones. Interval: Indicates the interval (in seconds) to poll the Avaya IP Phones. The default value is 900 seconds.
   Configuration for Monitoring of Various States of Media Processors	Allows you to configure the continuous polling of the various states of Avaya Media Processors (MedPros, Prowlers) on the network. The available options are as follows: Enable Polling: Select this check box to enable the polling of the media processors. Interval: Indicates the interval (in seconds) to poll the media processors. The default value is 600 seconds.
   Configuration for Monitoring of Various States of the IP Server Interfaces (IPSI)	Allows you to configure the continuous polling of the various states of Avaya IP Server Interfaces (IPSI) on the network. The available options are as follows: Enable Polling: Select this check box to enable the polling of the Avaya IP server interface objects. Interval: Indicates the interval (in seconds) to poll the IP server interfaces. The default value is 600 seconds.
   Configuration for Monitoring Inter-Region Connection States for IP Network Regions	Allows you to configure the continuous polling of the state of health for the connectivity of the IP Network Region with all the other logically connected IP Network Regions. The available options are as follows: Enable Polling: Select this check box to enable the polling of the IP Network Regions. Interval: Indicates the interval (in seconds) to poll the IP Network Regions. The default value is 300 seconds.
   Configuration for Monitoring DSP Summaries for IP Network Regions	Allows you to configure the continuous polling of the hourly DSP usage and the related summary of the DSP resources deployed in the Network Region. The available options are as follows: Enable Polling: Select this check box to enable the polling of the IP Network Regions. Interval: Indicates the interval (in seconds) to poll the IP Network Regions. The default value is 1800 seconds.
   Configuration for Monitoring CODEC Summaries for IP Network Regions	Allows you to configure the continuous polling of the hourly CODEC usage and the related summary of the CODEC resources deployed in the Network Region. The available options are as follows: Enable Polling: Select this check box to enable the polling of the IP Network Regions. Interval: Indicates the interval (in seconds) to poll the IP Network Regions. The default value is 1800 seconds.
   Configuration for Monitoring the State of Duplex Primary Servers	Allows you to configure the continuous polling of the state (Active/Standby) of the paired Avaya primary servers on the network. The available options are as follows: Enable Polling: Select this check box to enable the polling of the primary server. Interval: Indicates the interval (in seconds) to poll the primary server. The default value is 300 seconds.
   Configuration for Survivable Server State Monitoring	Allows you to configure the continuous polling of the state (Active/Standby) of the Avaya survivable servers such as Local Survivable Servers (LSP) for every Primary Avaya Communications Manager server on the network. The available options are as follows: Enable Polling: Select this check box to enable the polling of the survivable server. Interval: Indicates the interval (in seconds) to poll the survivable server. The default value is 300 seconds.
   Configuration for Monitoring Route Pattern Usage Metrics	Allows you to configure the continuous polling of the route pattern usage on the network. The available options are as follows: Enable Polling: Select this check box to enable the polling of the route pattern usage. Interval: Indicates the interval (in seconds) to poll the route pattern usage. The default value is 1800 seconds.
   Configuration for Monitoring Trunk Group Usage Metrics	Allows you to configure the continuous polling of the trunk group usage metrics on the network. The available options are as follows: Enable Polling: Select this check box to enable the polling of the trunk group usage. Interval: Indicates the interval (in seconds) to poll the trunk group usage. The default value is 1800 seconds.
   Configuration for Monitoring States of Trunk Group Members and Signaling Groups	Allows you to configure the continuous polling of the state of the trunk group members. The available options are as follows: Enable Polling: Select this check box to enable the polling of the state of the trunk group members. Interval: Indicates the interval (in seconds) to poll the state of the trunk group members. The default value is 1800 seconds.
   Configuration for Port Network Load Statistics Monitoring	Allows you to configure the continuous polling of the load statistics of the port network. The available options are as follows: Enable Polling: Select this check box to enable the polling of the load statistics of the port network. Interval: Indicates the interval (in seconds) to poll the load statistics of the port network. The default value is 1800 seconds.
   Configuration for Processor Occupancy Statistics Monitoring	Allows you to configure the continuous polling of the occupancy statistics of the processor. The available options are as follows: Enable Polling: Select this check box to enable the polling of the occupancy statistics of the processor. Interval: Indicates the interval (in seconds) to poll the occupancy statistics of the processor. The default value is 1800 seconds.

3. Click Apply Changes.

Configure the Media Gateway Polling

To configure the polling of a Media Gateway:

1. From the Workspaces navigation pane, click Configuration > iSPI for IP Telephony Configuration... > Avaya Configuration. The NNM iSPI for IP Telephony Avaya Configuration Console opens.
2. Click Polling Configuration. The NNM iSPI for IP Telephony Avaya Polling Configuration form opens.
3. In the Media Gateway Polling section, specify the required details in the fields provided on the page. The following table describes the fields on the page:

   Field Name	Description
   Configuration for Monitoring the Media Gateway States	Allows you to configure the continuous polling of the state of the media gateways. The available options are as follows: Enable Polling: Select this check box to enable the polling of the state of the media gateways. Interval: Indicates the interval (in seconds) to poll the media gateways. The default value is 300 seconds.
   Configuration for Monitoring the Media Gateway Module States	Allows you to configure the continuous polling of the state of the media gateway modules. The available options are as follows: Enable Polling: Select this check box to enable the polling of state of the media gateway modules. Interval: Indicates the interval (in seconds) to poll the media gateway modules. The default value is 300 seconds.
   Configuration for Monitoring the Media Gateway VoIP Engines States	Allows you to configure the continuous polling of the VoIP engine state of the media gateways. The available options are as follows: Enable Polling: Select this check box to enable the polling of the VoIP engine state of the media gateways. Interval: Indicates the interval (in seconds) to poll the VoIP engine of the media gateways. The default value is 300 seconds.
   Configuration for Monitoring the Media Gateway DSP Core States	Allows you to configure the continuous polling of the DSP core state of the media gateways. The available options are as follows: Enable Polling: Select this check box to enable the polling of the state of the DSP core state of the media gateways. Interval: Indicates the interval (in seconds) to poll the DSP core state of the media gateways. The default value is 300 seconds.

4. Click Apply Changes.

Configure Reporting

The Reporting Configuration link on the Avaya Configuration console enables you to configure the following types of reports:

• CDR
• Phone Media Access Control (MAC)
• Trunk Activity
• Trunk Group Usage
• Processor Occupancy Summary
• Port Network Load
• IP Network Region DSP/Codec Summary
• Route Pattern Usage

Configure CDR Reporting

You can use the NNM iSPI for IP Telephony Avaya Reporting Configuration form to configure CDR reporting for Avaya IP Telephony networks. However, you have to install and enable the iSPI Performance for Metrics to enable CDR reporting by the NNM iSPI for IP Telephony.

To configure Avaya CDR reporting:

1. On the NNM iSPI for IP Telephony Avaya Configuration console, click Reporting Configuration. The NNM iSPI for IP Telephony Avaya Reporting Configuration form opens.
2. In the Reports Using CDR Data section, specify the required details in the fields provided on the page. The following table describes the fields on the page:

   Field Name	Description
   Enable Reporting	Select this check box to enable the Avaya CDR reporting.
   Number of Calls to Write	Indicates the number of processed calls to be sent to NPS or the Global Manager in an instance in the field. The default value is 5000.
   Calling and Called party Numbers in Reports	Select this check box to display the calling party number and the called party numbers in the Call Details reports.
   Forward to Global Manager	Select this check box if you want the processed call information to be sent from the current management server to the global manager. This option is enabled by default.

3. Click Apply Changes.

Enable Phone MAC Reports

You can use the NNM iSPI for IP Telephony Avaya Reporting Configuration form to enable or disable IP Phone MAC comma separated value reports. These reports include information about the IP phones that are added, deleted, or shifted (moved) in the network. After you enable this report, the NNM iSPI for IP Telephony generates this report when a phone is added, removed, or moved on the network.

You must make sure that IP phone discovery is enabled in NNMi for this reporting to work.

To configure IP Phone MAC reporting:

1. From the Workspaces navigation pane, click Configuration > iSPI for IP Telephony Configuration... > Avaya Configuration. The NNM iSPI for IP Telephony Avaya Configuration Console opens.
2. Click Reporting Configuration. The NNM iSPI for IP Telephony Avaya Reporting Configuration form opens.
3. In the Phone MAC Reports section, specify the required details in the fields provided on the page. The following table describes the fields on the page:

   Field Name	Description
   Enable Reporting	Select this check box to enable the Avaya IP phone MAC reporting.
   Access Switches	Indicates the name of the configuration file that contains the comma-separated list of access switch IP addresses. This field is mandatory if you want the phone MAC reports to include the details regarding the phone shifting in the network. The file is present at the following location: Windows platforms: nnmDataDir\shared\ipt\conf Non Windows platforms: /var/opt/OV/shared/ipt/conf
   Forward to Global Manager	Select this check box if you want the phone MAC reporting information to be sent from the current management server to the global manager. This option is enabled by default.

4. Click Apply Changes.

You can access these reports from the following location:

• Windows Platforms: nnmDataDir\shared\ipt\PhoneMacReports\reports
• Non Windows Platforms: /var/opt/OV/shared/ipt/PhoneMacReports/reports

In High Availability environments, you can access these reports from the following location:

• On Windows

  <Shared_Drive>\NNM\dataDir\ipt\PhoneMacReports\reports

• On UNIX/Linux

  /nnm_mount_point/NNM/dataDir/ipt/PhoneMacReports/reports

  In this instance, <Shared_Drive> (Windows) or /nnm_mount_point (UNIX/Linux) is the

  directory location for mounting the NNMi shared disk.

The reports follow the following nomenclature standard: <ipt_server_name>_<vendor name>_AddPhones_<date>.csv

• ipt_server_name: indicates the name of the NNM iSPI for IP Telephony server if the server is a remote server and the report is generated at the global manager. For local servers, this value gets replaced by the identifier Local.
• vendor name: indicates the name of the vendor, Cisco or Avaya.
• date: indicates the date in mmddyy format when the report was generated.

You can identify if the report is generated for a phone added, moved, or removed by the following identifier in the report name:

• AddPhones: generated for phones added.
• RemovePhones: generated for phones removed from the network.
• MovePhones: generated for phones moved in the network.

The report displays the following details as comma-separated values for a phone addition, removal, or a move.

Report Data	Description
Time stamp	The time at which the change was detected.
Phone extension	The phone extension that was added, removed, or moved.
Phone IP address	The IP address of the phone.
Call Controller IP address	The IP address of the present call controller associated with the phone.
Current switch IP address	The IP address of the present switch.
Current switch interface	The interface name of the present switch.
Previous switch IP address	The IP address of the previous switch associated with the phone.
Previous switch interface	The interface name of the previous switch.

Enable Trunk Activity Reports

You can use the NNM iSPI for IP Telephony Avaya Reporting Configuration form to enable trunk activity reports.

To configure trunk activity reporting:

1. From the Workspaces navigation pane, click Configuration > iSPI for IP Telephony Configuration... > Avaya Configuration. The NNM iSPI for IP Telephony Avaya Configuration Console opens.
2. Click Reporting Configuration. The NNM iSPI for IP Telephony Avaya Reporting Configuration form.
3. In the Trunk Activity Report section, select the Enable Reporting check box.
4. Click Apply Changes.

Enable Trunk Group Usage Reports

You can use the NNM iSPI for IP Telephony Avaya Reporting Configuration form to enable trunk group usage reports.

To configure trunk group usage reporting:

1. From the Workspaces navigation pane, click Configuration> iSPI for IP Telephony Configuration... > Avaya Configuration. The NNM iSPI for IP Telephony Avaya Configuration Console opens.
2. Click Reporting Configuration. The NNM iSPI for IP Telephony Avaya Reporting Configuration form opens.
3. In the Trunk Group Usage Report section, select the Enable Reporting check box
4. Click Apply Changes.

Enable Processor Occupancy Summary Reports

You can use the NNM iSPI for IP Telephony Avaya Reporting Configuration form to enable or disable processor occupancy summary reports.

To configure processor occupancy summary reporting:

1. From the Workspaces navigation pane, click Configuration> iSPI for IP Telephony Configuration... > Avaya Configuration. The NNM iSPI for IP Telephony Avaya Configuration Console opens.
2. Click Reporting Configuration. The NNM iSPI for IP Telephony Avaya Reporting Configuration form opens.
3. In the Processor Occupancy Summary Report section, select the Enable Reporting check box
4. Click Apply Changes.

Enable Port Network Load Reports

You can use the NNM iSPI for IP Telephony Avaya Reporting Configuration form to enable or disable port network load reports.

To configure port network load reporting:

1. From the Workspaces navigation pane, click Configuration > iSPI for IP Telephony Configuration... > Avaya Configuration. The NNM iSPI for IP Telephony Avaya Configuration Console opens.
2. Click Reporting Configuration. The NNM iSPI for IP Telephony Avaya Reporting Configuration form opens.
3. In the Port Network Load Report section, select the Enable Reporting checkbox.
4. Click Apply Changes.

Enable IP Network Region DSP/Codec Summary Report

You can use the NNM iSPI for IP Telephony Avaya Reporting Configuration form to enable or disable IP network region DSP/Codec summary reports.

To configure IP network region DSP/Codec summary reporting:

1. From the Workspaces navigation pane, click Configuration > iSPI for IP Telephony Configuration... > Avaya Configuration. The NNM iSPI for IP Telephony Avaya Configuration Console opens.
2. Click Reporting Configuration. The NNM iSPI for IP Telephony Avaya Reporting Configuration form opens.
3. In the IP Network Region DSP/Codec Summary Report section, select the Enable Reporting check box.
4. Click Apply Changes.

Enable Route Pattern Usage Report

You can use the NNM iSPI for IP Telephony Avaya Reporting Configuration form to enable or disable route pattern usage reports.

To configure route pattern usage reporting:

1. From the Workspaces navigation pane, click Configuration > iSPI for IP Telephony Configuration... > Avaya Configuration. The NNM iSPI for IP Telephony Avaya Configuration Console opens.
2. Click Reporting Configuration. The NNM iSPI for IP Telephony Avaya Reporting Configuration form opens..
3. In the Route Pattern Usage Reporting section, select the Enable Reporting check box..
4. Click Apply Changes.