This update focuses on lifting the game of our VQM data, providing new leading-edge visibility.  We are also delivering TCP protocol validation support on our new Protocol Validation – Preview page.

 

At a glance:

  • We are launching Voice Quality Management – Preview and it features:
    • AI troubleshooting diagnostics
    • Faster, and easier to use filtering
    • Gorgeous bi-directional stream details and path graphing at a single click
  • Call Details Records and CMS Call History is now fully integrated with our VQM data, including stream path, graphics, and configuration details
  • Protocol Validation – Preview has been updated to now support TCP protocols:
      • TCP
      • Raw Socket
      • SSH
  • More fixes and enhancements to Manage Equipment
  • Standardized navigation and context menus for our Customer Landing pages

New Functionality

Voice Quality Management – Preview

Voice Quality Management – Preview provides richer on-screen real-time filtering, allowing users to filter out 100,000s  of data rows to a mere few within a second.  Viewing details for a stream now shows:

  • Stream configuration data, with AI diagnostic troubleshooting and highlighting of problematic settings
  • Current and related stream path
  • Current and related stream details

Voice Quality integration with Call Detail Records

By matching up extensions, stream start and end times, and applying several other smart heuristics, our engineers have been able to link voice quality to call detail records.  The same information available on the VQM page, is now also available on the CDR page

 

 

Protocol Validation – Preview now supports TCP protocols

 

Protocol Validation – Preview has been updated to include the TCP-based protocols, specifically SSH, Raw Socket, and SMTP.

SSH/Telnet

A typical example would be to check SSH connectivity to a server on the network. Usually this would be internal, with SSH not available via a publicly accessible host.

Input parameters are Port (default is 22), and a user name and password. Protocol Validation will attempt to connect using those credentials, and raise an alarm on failure. Possible response codes, included in the alarm information, include:

• Failed: 11001 No such host is known
• Failed: Authentication failure, check user name and password is correct
• Failed: 11061 No connection could be made because the target machine actively refused it

Error codes are standard windows socket error code available here: https://docs.microsoft.com/en-us/windows/win32/winsock/windows-sockets-error-codes-2

Raw Socket

For some applications, connectivity is via proprietary connections, with the standard protocols (HTTP/S, SSH, Telnet, etc.) not supported. For example, an Avaya agent application on a desktop which communicates to a server via proprietary protocol. In this case, a mechanism is required to query the server, to check whether it is alive.

Raw TCP Socket is a step below the standard protocols, and can be used to query the server via a basic TCP socket connection.

This protocol checks whether a socket can be opened on the designated target, and if not raises an alarm with response code:
• Failed: 11061 No connection could be made because the target machine actively refused it

SMTP

SMTP protocol validation can be used to test connectivity to an SMTP server and do a EHLO test query.

If there is no response the following alarm is raised:

  • Failure: Unable to connect to SMTP server on port <port number>

 

Enhancements to Endpoint Data Summary Dashlet

The Endpoint Data Summary dashlet has been updated to include a count of endpoints where:

  1. VLAN = 0
    • These endpoints can contribute to poor voice quality, since VLAN 0 is the broadcast VLAN and does not support QoS
  2. DSCP ≠ 46
    • DSCP is used to define priority for network traffic. For best results it’s recommended that DSCP is set to 46 (expedited forwarding).

To see which specific endpoints might be mis-configured – click on the Endpoints link to be taken to the Phone Data Report.

 

 

Upgraded navigation and context menu on Customer Landing page

Both the top-menu, and navigation menu for Service Desk on the Customer Landing page has been streamlined, for easier use and consistency with the business partner navigation menu.

 

Bug Fixes

Fixes to Manage Equipment page

  • Mange Equipment -> Avaya Communication Manager
    • When editing a ‘Media Gateway’, under Avaya Communication Manager, the media gateway password is now obscured, consistent with password management practices throughout VSM.
    • Previously, if a Media Gateway was removed, this was not updated in VSM, and it remained visible and configurable.  This has now been fixed
    • When configuring Media Gateways, under Manage Equipment -> Avaya Communication Manager -> Edit, additional options have been added allowing user to disable auto connectivity, and reset passwords
  • When adding a Generic Device under the Manage Equipment page, and configuring it to use SNMP v3, the username would become mandatory after switching to a different SNMP version. This has now been fixed.
  • There was an issue where SNMP v3 credentials were not being correctly applied – this has now been fixed.
  • Manage Equipment -> Cisco – previously it was not possible to add a Cisco Ethernet Switch device.  This functionality has now been added.

Fixes to Call Details page

  • There was an issue on the CDR page, where the filter was pre-populated with unusable data, instead of being blank.  This has been fixed, and the default filter is blank.
  • Previously, on the CDR page, when creating a filter using Incoming or Outgoing calls for criteria, this was not correctly shown on the grid. This has now been fixed.

Agent Station Data Report

There was an issue with the Agent/Station Data Report, where the majority of staffed agents were shown has having no station data.

This issue was caused where there were hyphenated extension numbers, and has now been fixed.

 

Network Connectivity Summary Dashlet

Previously, there was an issue on the Network Connectivity Summary dashlet, where only selected equipment types were being shown, despite more configured.

This issue has now been fixed. The Network Connectivity Summary dashlet will show all configured equipment.