Managing Media Devices

Unified communications systems require specialized devices to route calls from the PSTN, to handle conference calls, and to transcode media streams. Examples include voice gateways, session border controllers, mediation servers, conferencing servers, and unified messaging servers.
cucm41
HID_ManageOtherDevices
Unified communications systems require specialized devices to route calls from the PSTN, to handle conference calls, and to transcode media streams. Examples include voice gateways, session border controllers, mediation servers, conferencing servers, and unified messaging servers.
  • In Cisco or Avaya environments, voice gateways route VoIP calls to and from the PSTN. Voice gateways provide important information about call performance and quality.
  • In Microsoft Lync environments, media devices play an essential role in call routing and processing, but do not provide metrics by SNMP.
    Unified Communications Monitor
     monitors the performance of the call legs that media devices handle and includes their metrics in performance reports.
Contents
Voice Gateway List
The Voice Gateway List identifies the Cisco and Avaya voice gateway devices that
Unified Communications Monitor
has discovered.
Unified Communications Monitor
 discovers voice gateways when a user makes or receives a call involving the PSTN.
The Voice Gateway List provides the following information.
  • Voice Gateway
    . The name of the gateway device.
  • IP Domain
    . The IP domain that is associated with this device. The IP domain is created in CA Performance Center. This field is available only when
    Unified Communications Monitor
     is registered to a CA Performance Center instance where at least one IP domain is defined.
  • Monitoring Status
    . Whether data from this device is included in reports.
  • SNMP Profile
    .
     
    (
    Cisco SPAN only
    ) The name of the SNMP profile that is associated with this device. The SNMP profile contains SNMP security information, such as the community string, which is required to poll voice gateway devices. Unless you changed it, the collector uses a default profile for SNMPv1 or SNMPv2C.
  • Voice Interfaces
    .
     
    The number of voice interfaces that the collector detected on this voice gateway.
  • Address
    . The IP address of the device in dotted notation, such as 10.10.2.34.
  • Perform routine traceroute
    . When enabled, routine traceroutes run to this device every four hours to establish a baseline of data about common paths through the network. Routine traceroute testing is enabled for each new Cisco gateway device. Routine traceroute testing is disabled for Avaya voice gateways, which do not perform call setup. The option is automatically disabled when the monitoring status is Disabled.
Add, Change, or Delete Voice Gateways
Unified Communications Monitor
 automatically discovers Cisco or Avaya voice gateways on your network when those devices handle calls. However, you can manually add voice gateways to the database in the following circumstances:
  • Analog telephones in your system are connected to Cisco VG-224 gateways. These devices can appear incorrectly in reports unless you add them as voice gateways.
  • Your network includes voice gateways that are in different SNMP communities, or that support different versions of SNMP. You can associate a voice gateway definition with an SNMP profile that contains gateway-specific security parameters.
  • You suspect that SNMP community information is incorrect. When you add a voice gateway, review the SNMP security parameters and verify that the collector can poll the device.
  • You want to create custom groups of devices and Locations in CA Performance Center. Groups let you grant view access to
    Unified Communications Monitor
     data when you configure user accounts. You can include voice gateways in user permission groups.
Note
: You cannot add gateway voice interfaces.
Unified Communications Monitor
 automatically polls the gateways and discovers information about available voice interfaces.
You can change the properties of Cisco and Avaya voice gateways that the collector detects on your network. You can also change the properties of voice gateways that you add to the database.
Unified Communications Monitor
 automatically rediscovers deleted voice gateways when calls are sent through the gateways.
Follow these steps:
  1. Click
    Administration
    ,
    Data Collection
    ,
    Media Devices
    ,
    Voice Gateways
    in the navigation bar.
  2. To add or change a voice gateway
    , perform the following steps.
    1. Click
      New
      to add a voice gateway, or select the voice gateway that you want to change and click
      Edit
      . You can select multiple voice gateways to simultaneously change the SNMP Profile (including the
      from collector
       field) and the
      Monitoring Status
      fields for those gateways.
    2. Complete the following fields as necessary:
      • Name
        . A name for the voice gateway. Typically, the DNS host name, although you can enter any name. If you do not know the DNS host name, enter the IP address in the
        Address
        field and click
        DNS
        .
      • Address
        . The IP address of the device in dotted notation, such as 10.10.2.34. If you do not know the IP address, enter the server DNS host name in the
        Name
        field and click
        IP
        .
      • IP Domain
        . The IP domain that is associated with this device. The IP domain is created in CA Performance Center. This field is available only when
        Unified Communications Monitor
         is registered to a CA Performance Center instance where at least one IP domain is defined.
      • SNMP Profile
        (
        Cisco SPAN only
        ). Select the SNMP profile for this gateway. The SNMP profile contains security information, such as the SNMP community string, to let the collector query the MIB of this gateway device. The default SNMP profile is used unless you select a custom profile from the list. Unless you changed it, the default SNMP profile uses the "public" community string. Click Verify SNMP to instruct the collector to try to contact the gateway using the specified SNMP profile. By default, the collector that detected the voice gateway is used for the verification. We recommend using the default collector. If verification fails, select another collector from the
        from Collector
        list and try again. 
        Note
        :If you are monitoring by IP domain, the IP domain with which the collector associates call data is appended to the collector host name.
      • Monitoring Status
        . Whether data from this device is included in reports. The following options are available: 
        • Enabled: Calls from this device are monitored. 
        • Disabled: Calls from this device are not monitored. Data from the calls is discarded. 
        • Enabled (Sending Only): Monitoring is enabled only for calls from through this gateway: from the PSTN to phones in monitored Locations.
      • Perform routine traceroutes for the baseline
        . When enabled, routine traceroutes run to this device every four hours to establish a baseline of data about common paths through the network. Routine traceroute testing is enabled for each new Cisco gateway device. Routine traceroute testing is disabled for Avaya voice gateways, which do not perform call setup. The option is automatically disabled when the monitoring status is
        Disabled
        .
      • Description
        . (Optional) A description to help identify this device, such as its location, capabilities, or past performance.
      • Voice Interfaces
        . Click
        Edit
        to change the properties of voice interfaces for the gateway. Complete the following fields, and then click
        OK
        .
      • Name
        . The name for the gateway voice interface. By default, the interface name is based on information from the gateway and the naming convention of the trunking equipment. You can supply a more easily remembered name for this field.
      • Discovered Capacity
        . The maximum number of simultaneous calls that this interface can support, according to information discovered by the collector. The collector finds information about interface capacity using different methods for each type of gateway device or protocol. The discovered capacity is collected from the gateway MIB.
        Note
        : In many cases, the collector retrieves capacity information during the initial polling of the gateway. However, the collector does not retrieve changes in capacity information. Enter any changed information in this field.
      • Override Channel Capacity
        . By default, this value is the same as the
        Discovered Capacity
        . You can change the discovered capacity for reasons that depend on your environment. For example, the device MIB can misreport the interface capacity. Or for capacity-planning purposes, you want to see usage statistics in
        Unified Communications Monitor
         reports that reflect a different call capacity for an interface.
        Tip
        :The Voice Interface reports use the channel capacity information to calculate interface usage as a percentage of capacity. These reports are less accurate when the device MIB incorrectly reports channel capacity.
    1. Save the voice gateway.
      The
      Voice Gateway List
      displays the new voice gateway.
  1. To delete a voice gateway
    , perform the following steps.
    1. Select the voice gateway that you want to delete, and click
      Delete
      . You can select multiple voice gateways.
    2. Click
      Delete
      . The gateway is removed from the database and is no longer used to identify calls or call data in reports.
Import Voice Gateway Definitions
When your network contains many voice gateways, use the import feature to add device definitions. Use this feature for the initial
Unified Communications Monitor
 configuration and for subsequent additions of gateways. Only voice gateways that support SNMPv1 or SNMPv2C can be imported. You must manually add voice gateways that support SNMPv3.
The import interface does not let you edit or delete gateways that are already in the system. After you import the definitions, you can edit and delete them from the Voice Gateway List.
For each SNMP community string in the
.csv
file,
Unified Communications Monitor
 checks for the corresponding SNMP profile. If no corresponding profile is found,
Unified Communications Monitor
 creates a profile for the community string.
Tip
: Create your SNMP profiles before importing voice gateway definitions.
For SNMP community strings not specified in the .csv file, the collector uses the default SNMP profile to contact the associated gateway. If you create SNMP profiles, you can set one of them as the default before importing the .csv file. Otherwise, the default profile for SNMP v1/2c is used. The default profile uses the “public” community string.
The monitoring status of imported voice gateways is always set to
Enabled
. Edit an imported definition to change the monitoring status.
IP domain definitions are not included in the supported syntax. IP domains are determined on a per-collector basis and are assigned to gateways as they are detected during monitoring. The
IP Domain
field lets you instruct the collector to associate voice gateways with a domain container. To expose the IP Domain field, define an IP domain in CA Performance Center.
The import procedure takes data from a file in comma-separated values (
.csv
) format. The correct syntax is to separate items with commas (,) and no spaces. The syntax for the data you want to import is described in the following table:
Data Type and Syntax
Notes and Examples
Voice gateway definition
(complete):
Voice gateway name,IP address,SNMP community,Description,Traceroute
Use quotation marks to enclose strings that contain commas, double quotation marks, or other punctuation.
The voice gateway name can be different from its host name.
Include the word “Traceroute” to enable the option to “Perform routine traceroutes for baseline.” To disable this option, do not include the word "Traceroute."
Examples:
Houston Data Center,10.12.34.56,private,"Data center, gateway router",Traceroute
HoustonDataCtr01,10.12.34.56,private,Data center gateway router
Austin_HQ_FXO,10.123.45.67,ultra5ecur3PW,VGW at HQ,Traceroute
Voice gateway definition
(no SNMP community, no description):
Voice gateway name,IP address,,,Traceroute
SNMP community, description, and traceroute are optional. The default SNMP profile is used.
Examples:
Houston Data Center,10.12.34.56,,,Traceroute
HoustonDataCtr01,10.12.34.56
Austin_HQ_FXO,10.123.45.67,,,Traceroute
Voice gateway definition
(no description):
Voice gateway name,IP address,SNMP community,,Traceroute
Voice gateway description and traceroute are optional.
Examples:
Houston Data Center,10.12.34.56,private
HoustonDataCtr01,10.12.34.56,private,,Traceroute
Austin_HQ_FXO,10.123.45.67,ultra5ecur3PW,,Traceroute
Voice gateway definition
(no SNMP community):
Voice gateway name,IP address,,Description,Traceroute
SNMP community string is optional. If no string is supplied, the collector uses the default SNMP profile.
Examples:
Houston Data Center,10.12.34.56,,"Data center, gateway router",Traceroute
HoustonDataCtr01,10.12.34.56,,Data center gateway router
Austin_HQ_FXO,10.123.45.67,,VGW at HQ,Traceroute
Follow these steps:
  1. Create a
    .csv
    file that contains your voice gateway definitions.
  2. Click
    Administration
    ,
    Data Collection
    ,
    Media Devices
    ,
    Voice Gateways
    in the navigation bar.
  3. Click
    Import
    .
  4. (
    Optional
    ) Select a custom domain for the
    IP Domain
    field. This field is available only when you define IP domains in CA Performance Center.
  5. In the
    File Name
    field, navigate to the .csv file that contains your gateway definitions.
  6. Click
    Next
    .
    Unified Communications Monitor
     analyzes the file and reports any syntax errors.
  7. Correct any errors in the file and save it. Then repeat steps 5 and 6.
    When no errors are found, the import operation is finished. A confirmation page opens. The appropriate database objects are created.
  8. Click
    OK
    .
    The
    Voice Gateway List
    displays the new gateways.
Other Media Device List
A unified communications deployment can include many different devices, from various vendors, to support voice and video calls, conferencing, and voice mail.
Unified Communications Monitor
 discovers these devices when calls pass through them. You can also manually add devices to the
Other Devices
category.
The
Other Devices
category includes the following types of devices:
  • Microsoft mediation servers, edge servers, conferencing servers, and unified messaging servers
    .
    Unified Communications Monitor
     monitors the performance of the call legs that Microsoft devices handle. Both VoIP and video call performance metrics from these call legs are included in the media device views in
    Unified Communications Monitor
     performance reports. SNMP is not used to contact these servers, therefore:
    • Baseline traceroute data is not available.
    • The servers are not included in the configurations for performance thresholds.
  • Devices that do not contribute to call performance reporting, such as unsupported types of voice gateways
    . You can manually add these devices so that they are included in a device inventory, for example.
  • Devices that you want to monitor individually, although they are part of a larger group
    . For example: You configure a Location that includes the servers that support your high-end video conferencing system, such as Cisco TelePresence or Polycom PVX. However, a defined Location provides granularity only to the subnet level in reports. Reports correlate calls to a Location and subnet, but not to the individual servers in that subnet. If you define the video conferencing devices as Other Devices,
    Unified Communications Monitor
     can easily associate video conference calls with their respective devices.
The Other Device List provides the following information about discovered media devices, and media devices you add to the database.
  • Device
    .
     
    The DNS host name of the device.
  • IP Domain
    . The IP domain that is associated with this device. The IP domain is created in CA Performance Center. This field is available only when
    Unified Communications Monitor
     is registered to a CA Performance Center instance where at least one IP domain is defined.
  • Monitoring Status
    . Whether data from this device is included in reports.
  • Address
    . The IP address of the device in dotted notation, such as 10.10.2.34.
  • Type
    . The type of media device, such as IP phone, IP PBX, unified messaging server, mediation server, or session border controller (SBC).
  • Description
    . The date and time when
    Unified Communications Monitor
     discovered this device.
Add, Change, or Delete Other Media Devices
Unified Communications Monitor
 discovers media devices on your network when those devices handle calls within the system. You can add media devices to the database so that you can easily identify them in reports. You can also place these devices in custom permission groups in CA Performance Center, when
Unified Communications Monitor
 is a registered data source.
You can change the properties of the devices that
Unified Communications Monitor
 detects on your network. You can also change the properties of devices that you add to the database.
You can delete media devices from the database. Although you delete an active device,
Unified Communications Monitor
 automatically rediscovers the device when calls are sent through the device.
Follow these steps:
  1. Click
    Administration
    ,
    Data Collection
    ,
    Media Devices
    ,
    Other Devices
    in the navigation bar.
  2. To add or change a media device
    , perform the following steps.
    1. Click
      New
      , or select the media device whose properties you want to change and then click
      Edit
      .
    2. Complete the following fields as necessary:
      • Name
        . A name for the media device. Typically, the DNS host name, although you can enter any name. If you do not know the host name, enter the IP address in the
        Address
        field and click
        DNS
        .
      • Address
        . The IP address of the media device. Use dotted notation, such as 10.10.2.34. If you do not know the IP address, enter the server DNS host name in the
        Name
        field and click
        IP
        .
      • IP Domain
        . The IP domain that is associated with this device. The IP domain is created in CA Performance Center. This field is available only when
        Unified Communications Monitor
         is registered to a CA Performance Center instance where at least one IP domain is defined.
      • Description
        . A description to help identify this device, such as its location, capabilities, or past performance.
      • Type
        . The type of media device, such as IP phone, IP PBX, unified messaging server, mediation server, or session border controller (SBC). Use the
        Type
        field for identification purposes. For example, you can create an inventory of servers, including servers that do not contribute to call performance reporting, such as unified messaging servers. These servers are classified as Voice Gateway (Unsupported), but the information in the
        Type
        field provides a more precise description.
        Note
        : Some devices play multiple roles. After
        Unified Communications Monitor
         is registered to CA Performance Center, devices are assigned generic types, such as server or router. If this value is inaccurate for a discovered device, you can edit the device to select another type. Or you can select
        Unspecified
        , an option that causes the collector to rediscover the device from monitored call traffic and reassign it a type.
      • Monitoring Status
        . Whether data from this device is included in reports. 
        • Enabled: Calls from this device are monitored. 
        • Disabled: Calls from this device are not monitored. Data from the calls is discarded. 
        • Enabled (Sending Only): Monitoring is enabled only for calls from through this gateway: from the PSTN to phones in monitored Locations.
    3. Save the device.
      The
      Other Device List
      reflects your changes.
  3. To delete a media device
    , perform the following steps.
    1. Select the media device that you want to delete. You can select multiple devices.
    2. Click
      Delete
      .
    3. Click
      Delete
      . The device is removed from the database and is no longer included in reports.