Submit a ticketCall us

Announcing NCM 7.7
With NCM 7.7, you can examine the rules that make up an access control list for a Cisco ASA device. Then you can apply filters to display only rules that meet the specified criteria, order the rules by line number or by the hit count, and much more.
See new features and improvements.

Home > Success Center > VoIP & Network Quality Manager (VNQM) > VoIP and Network Quality Manager creates multiple new sessions on the Avaya Call Manager

VoIP and Network Quality Manager creates multiple new sessions on the Avaya Call Manager

Created by Beatrix.Turan, last modified by MindTouch on Jun 23, 2016

Views: 37 Votes: 2 Revisions: 3

Overview

VoIP and Network Quality Manager creates multiple new sessions on the Avaya Call Manager in a short period of time.

Environment

  • This issue occurs on Avaya Call Managers user with VoIP and Network Quality Manager.

 

Cause 

The default polling frequency for the Avaya Call Manager is 5 minutes, and the default phone batch size for Avaya is 50. With these values, the statistical polling occurs every 5.76 seconds, and during each polling occurrence, a new session is created in the Avaya Communication Manager.

Resolution

Modify the following in the database to reduce the number newly created sessions.

Warning: SolarWinds strongly recommends that you only edit database tables as instructed. Any additional modifications to the database may result in system performance issues or may create an error state.

 

  1. Reduce the polling frequency from the default 5 minute:
    1. In the Orion Web Console, click Settings > VoIP & Quality Settings > Edit VoIP & Network Quality Manager settings.
    2. In the Call Manager section, increase the Polling Interval to 180, 300, or 480 minutes.
  2. Additionally, increase the value of the "CCMAvayaPhoneBatchSize" entry in the VoIPConfig table. Run the following command, and replace X with 500 or 750, depending on the size of your environment:

    UPDATE dbo.VoipConfig SET VALUE=X where Name='CCMAvayaPhoneBatchSize'
  3. Depending on the phone count in your environment, increase the value of the "CCMMaxPhones" entry in the VoIPConfig table from the default value of 2500.

    Run the following command, and replace the value X with the phone count corresponding to your environment. For example, if you have multiple call managers with connected phones, select the call manager with the maximum number of phones, and use that phone count as the value for X.

    UPDATE dbo.VoipConfig SET VALUE=X where Name='CCMMaxPhones'
  4. After applying these changes, restart the SolarWinds Orion services in the Orion Service Manager.

 

 

 

Last modified
04:35, 23 Jun 2016

Tags

Classifications

Public