Integration de la technologie Voix sur IP CISCO-CALL-MANAGER-STANDALONE


ServicePilot voip-cisco-call-manager-standalone


# Cisco Call Manager Standalone

Overview

The ServicePilot Cisco Call Manager Standalone package collects information for Cisco Unified Communications Managers.

Description

The Cisco Call Manager Standalone package uses SNMP to query Cisco Unified Communications Managers. Standalone or Publisher and Subscriber components can be monitored. The statistics gathered in this way include:

  • System information
  • CPU, Memory, Process and Disk utilization
  • Network interface statistics

The Cisco Call Manager Standalone package also configures the ServicePilot Agent to obtain Cisco Unified Communications Manager inventory and performance details using Cisco AXL connections. Details collected depend on the device type:

  • Publisher
    • License Information
    • Locations
    • SIP Devices
  • Subscriber
    • Call Activity
    • Registered Devices
    • H323 Gateways
    • GateKeeeper Gateways
    • Database Replication
    • Conferences
    • MGCP Gateways
    • Channel Activity

The Cisco Call Manager Standalone package will also configure the ServicePilot Agent to enable an FTP server, to which CDR and CMR records are to be transferred by the CUCM on a schedule. These details are used as the basis for call statistics and call quality statistics.

The Cisco Call Manager Standalone package can also check Cisco Disaster Recovery files. The files will be copied from the backup server defined to an empty local directory using SFTP. ServicePilot Manager will then monitor the state of the backup. Ticking the Summary checkbox will also provide summary information for all Cisco servers that are being backed-up.

Requirements

  • Network Flows - It is is necessary to ensure network connectivity between ServicePilot and the monitored device. In case of a network infrastructure using a firewall, all the ports below must be opened:

    • UDP/161 (SNMP): Between ServicePilot Manager and Cisco Unified Communications Managers
    • ICMP/Echo Request (Ping): Between ServicePilot Manager and Cisco Unified Communications Managers
    • TCP/8443 (AXL): Between ServicePilot Manager and Cisco Unified Communications Managers
    • Microsoft SQL database access: Between ServicePilot Agent and Cisco Unified Communications CDR database. Only for Cisco Unified Communications v4.
    • TCP/21 (Default) (FTP Control): Between Cisco Unified Communications Manager Publishers v5 and above and ServicePilot Agent
    • TCP/1024-65535 (FTP Data): Between ServicePilot Agent and Cisco Unified Communications Manager Publishers v5 and above (Active mode)
    • TCP/22 (SSH-SFTP): Between ServicePilot Manager and Cisco Unified Communications Disaster Recovery file backup server
    • UDP/162 (SNMP Trap): (Optional) Between Cisco Unified Communications Managers and ServicePilot Agent
    • ServicePilot Manager Web server access (by default TCP/80 when using HTTP or TCP/443 when using HTTPS although this port is configurable): Between ServicePilot Agent and ServicePilot Manager
  • Third Party Configuration

    • In the Cisco Unified Serviceability web pages, the SNMP V2 community string and access needs to allow ServicePilot Manager to access the Cisco devices
    • From CUCM version 7.1(2) onwards the predefined Cisco Unified CM Administration User Group Standard RealtimeAndTraceCollection should be used. For older releases create a new group with Standard AXL API Access and Standard CCM Admin Users Roles.
    • An AXL Application User, member of the group above, for access to the Cisco equipment by ServicePilot Agent
    • CDR and CMR collection configured:
      • CDR Enabled Flag: True
      • CDR Log Calls with Zero Duration Flag: True
      • Call Diagnostics Enabled: Enabled Only When CDR Enabled Flag is True
    • Cisco CDR Billing Application Server Parameters set to send details to ServicePilot Agent FTP server
    • An SFTP login on the backup server if monitoring Cisco Disaster Recovery files
  • ServicePilot Requirements

    • ServicePilot Manager minimum version: 8.5
    • ServicePilot Agent minimum version: 8.5 installed and configured
    • A Call Quality by Zone Or Network resource imported into the configuration for the ServicePilot Agent

Installation

Before adding a resource to monitor, make certain that all pre-requisites are in place and if a ServicePilot Agent is required, that it is communicating correctly with the ServicePilot Manager.

Add resource using Views Configuration web interface

  1. As an administrative user of ServicePilot, open the ServicePilot web interface.
  2. Navigate to Administration. The Configuration > Views web page will open.
  3. Click on the view in which to place the new resource in the Views hierarchy on the left of the interface. The View editor section will show the existing view contents.
  4. From the Packages list on the right of the interface, click and drag the voip-cisco-call-manager-standalone package into the View editor and let go.
  5. The Resource properties dialog box will open to allow resource configuration.
  6. Click OK to close the Resource properties dialog box. Note that the dialog box will not close if required parameters are not set.
  7. Click Save to apply the new resource to ServicePilot configuration.

Key field notes

In the Monitoring Policies tab, specify the policy or policies to apply to the resource

  1. Basic Parameters tab:

    1. IP address/FQDN: Specify the IP address, host name or FQDN for the Cisco Call Manager, as resolvable by the machine on which ServicePilot Agent is running
    2. Customer Name (matching VoIP Zone): If ServicePilot has been set up in multi-tenant environment, then the customer name is to be presented here, otherwise this field is to be left blank.
  2. CCM Connection tab:

    1. Enable AXL Collection: Tick to enable monitoring using AXL
    2. AXL Version: Select the AXL version in use
    3. AXL Host (If NAT): Specify the AXL host if NAT is configured
    4. AXL Login: Specify the AXL Login
    5. AXL Password: Specify the AXL Password
    6. AXL Port: Specify the AXL port where the Cisco equipment will respond to requests
  3. Resources tab, tick to enable the different resource monitoring options:

    1. Call Activity
    2. Registered Devices
    3. H323 Gateways
    4. Gatekeepers
    5. SIP Devices
    6. MGCP Gateways
    7. Channel Activity
    8. Locations
    9. Conferences
    10. License Information
  4. Call Log tab:

    1. Read Call Log: Tick to enable call log monitoring
    2. CDR Path: Specify the path from which to collect CDR data
    3. Use Local time: Tick to use the local time of ServicePilot Manager in statistics
    4. Ignore calls with duration=0: Ignore call with duration of 0 seconds in the statistics
    5. External extension pattern: A pipe separated list of Like Operator patterns to Specify an extension as external to the enterprise. Starting the list with an ! will reverse the meaning, so then list internal extensions instead (Default: 0|+). See the Like Operator (Visual Basic).
    6. Mask Extensions: Tick to enable masking of user portion in numbers
    7. Mask n last digits: Specify the number of trailing digits to mask
    8. When extension contains at least n digits: Specify the minimum length of an extension for masking to take effect
  5. Voice Quality tab:

    1. Good Jiter: Specify the maximum value of Jitter (in ms) for a good call
    2. Good Latency: Specify the maximum value of Latency (in ms) for a good call
    3. Good Packet Loss Rate: Specify the maximum rate of packet loss (in %) for a good call
    4. Good MOS Score: Specify the minimum MOS Score for a good call
    5. Medium Jiter: Specify the maximum value of Jitter (in ms) for a Medium call
    6. Medium Latency: Specify the maximum value of Latency (in ms) for a Medium call
    7. Medium Packet Loss Rate: Specify the maximum rate of packet loss (in %) for a Medium call
    8. Medium MOS Score: Specify the minimum MOS Score for a Medium call

Notes

Indicators description

Calls Quality

Number and Percentage of Good, Average and Bad quality calls.Calls are categorized as either good, average or bad according to thresholds defined in the ServicePilot Agent.

Calls Activity

  • Calls Active (An hold call is not considered as an active call. An Active call can be considered as a call with participants talking)
  • Calls In Progress (An active or hold call is considered as in progress)
  • Calls Attempted (An attempted call occurs any time that a phone goes off hook and back on hook, regardless of whether any digits were dialled, or whether it connected to a destination)
  • Authenticated Calls Active (An authenticated call designates one in which all the endpoints that are participating in the call are authenticated. An authenticated phone uses the Transport Layer Security (TLS) authenticated Skinny signaling protocol)

Gatekeeper Gateways

  • ARQs Attempted (Admission Request messages that are attempted by using the configured gatekeeper or its alternate gatekeepers)
  • ACFs Received (Admission Confirm messages that are received from the configured gatekeeper or its alternate gatekeepers).
  • RAS Retries (Number of retries due to loss or delay of all RAS acknowledgment messages on the configured gatekeeper or its alternate gatekeepers)
  • Video Out Of Resources (total number of video-stream requests to the configured gatekeeper or its alternate gatekeepers that failed, most likely due to lack of bandwidth)

Nous pouvons vous aider

ou appelez-nous au +33 2 40 60 13 30