Iqdialogue Asm 4.0 User's Guide - Sug-Diaasm-007

IQDialogue® ASM 4.
0
User’s Guide
Corporate Headquarters
IneoQuest Technologies, Inc.
170 Forbes Boulevard
Mansfield, MA 02048
http://www.ineoquest.com
Telephone, USA:
+1 508 339 2497
FAX Telephone Number, USA
+1 508 339 4727
Document Number: SUG-DIAASM-007

April 13, 2017
Notice
The information in this guide is subject to change without notice.

INEOQUEST TECHNOLOGIES, INCORPORATED SHALL NOT BE LIABLE FOR TECHNICAL OR
EDITORIAL ERRORS OR OMISSIONS CONTAINED HEREIN; NOR FOR INCIDENTAL OR
CONSEQUENTIAL DAMAGES RESULTING FROM THE FURNISHING, PERFORMANCE, OR USE OF
THIS MATERIAL.
ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS DOCUMENT ARE BELIEVED
TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY
PRODUCTS.
This guide contains information protected by copyright. No part of this guide may be photocopied or
reproduced in any form without prior written consent from IneoQuest Technologies, Inc.
The software described in this guide is furnished under a license agreement or nondisclosure agreement.
The software may be used or copied only in accordance with the terms of the agreement.
IneoQuest Technologies retains the right to change any of the specifications in this document at any time
without prior notice.
Product names mentioned herein may be trademarks and/or registered trademarks of their respective
companies.
© 2017 IneoQuest Technologies, Incorporated. All Rights Reserved.
IneoQuest Technologies, Inc., 170 Forbes Boulevard, Mansfield, Massachusetts 02048 USA
Patent No.: US 7,321,565, B2 and other patents pending
The following are trademarks of IneoQuest Technologies, Inc.:
IneoQuest Technologies, Expedus, DVA, iVMS, Singulus, IQDVx, IQMediaAnalyzer Pro, Cricket,
IQDialogue, IQMediaMonitor, Geminus, Surveyor, Inspector, Spectator
Microsoft, Windows, Excel, and Internet Explorer are either registered trademarks or trademarks of
Microsoft Corporation in the United States and/or other countries.
Adobe, Acrobat, and Flash are either registered trademarks or trademarks of Adobe Systems Incorporated
in the United States and/or other countries.
Mozilla and Firefox are registered trademarks of the Mozilla Foundation.
IneoQuest Technical Publications is a 2011, 2012, and 2016 APEX Award for Publication Excellence
winner.
IMPORTANT
NETWORK SECURITY
AND
PROPER USE OF INEOQUEST VIDEO ANALYSIS PROBE PRODUCTS1
Introduction
IneoQuest video analysis probe products detect streaming media data flows on networks and
measure a variety of key parameters. Measurement results and alerts can be sent to one or more
centralized servers, enabling users to view and compare measurements from end-to-end
throughout a distribution network to detect, locate and take corrective action on a wide range of
fault types.
Proper Use of IneoQuest Products

Users access information acquired and consolidated in IneoQuest products via server software
incorporated in both probe and management products. These hosts, like other networked
equipment, may be subject to a wide variety of security threats from the Internet. IneoQuest
products are designed for use, and must be used, only behind a properly configured border
router and firewall within a secure network infrastructure.2
The failure to take appropriate IT security precautions, and/or the use of IneoQuest products
outside a secure IT environment, may result in unauthorized access to customer data and systems,
and loss of functionality, warranty coverage, and support service coverage. IneoQuest is not
responsible for network vulnerabilities due to such failures nor their resulting consequences.
If you have questions about the use of IneoQuest Products, please contact IneoQuest Technical
Support at 1-866-464-4636 or techsupport@ineoquest.com.
1. This note relates to use of IneoQuest’s Singulus, Singulus Lite, Cricket, Geminus, DVA, Surveyor,
Inspector, and IQDialogue probe types and the AMP, iVMS, iVMS ASM, cVOC, PLM, iDMS, Spectator,
and cPAR management platforms. For more information about these and other products, please contact
your IneoQuest Technologies representative or contact us via our website at www.IneoQuest.com.
2. For more information regarding network security precautions, see generally “Guidelines on Securing
Public Web Servers,” Special Publication 800-44, Version 2, National Institute of Standards and
Technology (NIST), http://csrc.nist.gov/publications/nistpubs/800-44-ver2/SP800-44v2.pdf, including
Section 8, “Implementing a Secure Network Infrastructure.”
Contents
1 Technical Support Information

1.1 Address and Telephone Numbers........................................................................................ 1-1
1.2 Internet Addresses............................................................................................................... 1-1
1.3 About this Document .......................................................................................................... 1-1
1.3.1 Documentation Feedback........................................................................................ 1-2
2 Overview
2.1 Product Definition............................................................................................................... 2-1
2.2 Product Overview ............................................................................................................... 2-1
2.2.1 Key Features ........................................................................................................... 2-2
2.2.2 Monitoring and Analysis......................................................................................... 2-3
3 Product Installation
3.1 System Requirements.......................................................................................................... 3-1
3.2 Requirements for Smooth Streaming Publishing Support .................................................. 3-2
3.3 Requirements for Active Client Monitoring ....................................................................... 3-2
3.4 Client Request or Content Distribution Monitoring (Association Mode) Configuration ... 3-2
3.5 iVMS ASM Integration....................................................................................................... 3-3
4 Web Interface Session Monitoring

4.1 Menu Layout and Filters ..................................................................................................... 4-2
4.2 Interface and Traffic Monitoring Details ............................................................................ 4-3
4.3 Streaming Protocols ............................................................................................................ 4-4
4.3.1 Apple HLS Traffic .................................................................................................. 4-4
4.3.2 Microsoft Smooth Streaming Traffic ...................................................................... 4-7
4.3.3 OTT (Over-The-Top) Internet Video Traffic .......................................................... 4-9
4.3.4 MobiTV Traffic..................................................................................................... 4-10
4.3.5 RTMP .................................................................................................................... 4-11
4.3.6 Mediaroom ............................................................................................................ 4-13
4.3.7 Adobe HDS ........................................................................................................... 4-14
4.3.8 RTP/RTCP............................................................................................................. 4-16
4.3.9 NDS....................................................................................................................... 4-17
4.3.10 DASH.................................................................................................................... 4-19
5 Libpcap Support
5.1 Libpcap Playback and Capture ........................................................................................... 5-1
6 Disk and Database Logging

6.1 Database Transactions Logging and Sizing ........................................................................ 6-1
6.2 Database Purging ................................................................................................................ 6-1
IQDialogue ASM 4.0 User’s Guide — SUG-DIAASM-007 i

7 Software Upgrade
7.1 Appliance Based Platform .................................................................................................. 7-1
8 Northbound Services (NBS) GUI, Dashboards, and Alarming

8.1 Accessing the NBS GUI ..................................................................................................... 8-1
8.1.1 Java Requirements .................................................................................................. 8-1
8.1.2 Logging into the NBS GUI ..................................................................................... 8-2
8.2 Home/Key Performance Indicators (KPI)........................................................................... 8-2
8.2.1 Transactions ............................................................................................................ 8-2
8.2.1.1 Alarm Events ........................................................................................... 8-3
8.2.1.2 HTTP Sessions Initiated .......................................................................... 8-4
8.2.1.3 HTTP Publishing Sessions ...................................................................... 8-5
8.2.1.4 HTTP Errors 4XX ................................................................................... 8-6
8.2.1.5 HTTP Errors 5XX ................................................................................... 8-8
8.2.1.6 Response Failure Rate ............................................................................. 8-8
8.2.1.7 Publishing Failure Rate ........................................................................... 8-8
8.2.1.8 Active Alarms.......................................................................................... 8-8
8.2.2 Distribution ............................................................................................................. 8-9
8.2.2.1 VeriStream Metric Distribution ............................................................... 8-9
8.2.2.2 Bandwidth Usage................................................................................... 8-10
8.2.2.3 Client Type Distribution ........................................................................ 8-11
8.2.2.4 Top 10 Manifest Distribution ................................................................ 8-11
8.2.3 Alarms Timeline.................................................................................................... 8-12
8.2.4 RTSP ..................................................................................................................... 8-12
8.2.5 RTMP .................................................................................................................... 8-13
8.2.6 Smooth Streaming................................................................................................. 8-13
8.2.7 HLS ....................................................................................................................... 8-14
8.2.8 HDS....................................................................................................................... 8-15
8.2.9 DASH.................................................................................................................... 8-16
8.3 Realtime Census................................................................................................................ 8-17
8.3.1 All Clients ............................................................................................................. 8-17
8.3.2 Active Clients........................................................................................................ 8-29
8.4 Active Client ..................................................................................................................... 8-29
8.4.1 Request Configuration .......................................................................................... 8-31
8.4.1.1 Add, Delete, Import, Export, and Video Uplink Options...................... 8-33
8.4.1.2 Authentication ....................................................................................... 8-34
8.4.1.3 Video Uplink for Adaptive Bitrate (ABR) Flows.................................. 8-35
8.4.1.4 Grouping................................................................................................ 8-37
8.4.1.5 Active Client Session Logging.............................................................. 8-37
8.4.1.6 Active Client Recent Alarms................................................................. 8-38
8.4.1.7 Traceroute.............................................................................................. 8-39
8.4.1.8 Configure Options ................................................................................. 8-40
8.4.1.9 Grouping Management Features ........................................................... 8-40
8.4.2 Active Requests (AR) Logs .................................................................................. 8-42
8.4.3 Playlist Management............................................................................................. 8-44
8.5 Query................................................................................................................................. 8-47
ii IQDialogue ASM 4.0 User’s Guide — SUG-DIAASM-007

8.6 Reporting........................................................................................................................... 8-51
8.7 Configuration .................................................................................................................... 8-51
8.7.1 System Configuration ........................................................................................... 8-51
8.7.1.1 IQD Packet Filter................................................................................... 8-53
8.7.1.2 IQD Settings “http.uri.edit.list” Parameter............................................ 8-54
8.7.1.3 IQD Settings “http.only.save.masters” Parameter................................. 8-57
8.7.1.4 IQD Settings “census.intracdn.query.max.records” Parameter ............. 8-57
8.7.2 Publishing Alarm Config ...................................................................................... 8-58
8.7.2.1 Alarms ................................................................................................... 8-58
8.7.2.2 Tuples .................................................................................................... 8-59
8.7.3 Alias Configuration............................................................................................... 8-59
8.7.3.1 Asset Alias............................................................................................. 8-60
8.7.3.2 NIC Alias............................................................................................... 8-61
8.7.3.3 Origin Server Alias................................................................................ 8-62
8.7.3.4 Publishing Flows ................................................................................... 8-62
8.7.3.5 RTMP Alias ........................................................................................... 8-64
8.8 About................................................................................................................................. 8-65
9 Reporting Screens
9.1 Reporting Tab...................................................................................................................... 9-2
9.1.1 Automated Report Definitions Tab ......................................................................... 9-2
9.1.2 Generated Reports Tab............................................................................................ 9-3
9.2 Automating a Report ........................................................................................................... 9-4
9.3 Report Configuration .......................................................................................................... 9-6
9.4 The Reports ......................................................................................................................... 9-7
9.4.1 Active Client Report by Token ............................................................................... 9-7
9.4.1.1 Report Input............................................................................................. 9-7
9.4.2 Active Client Report by URI .................................................................................. 9-9
9.4.2.1 Report Input............................................................................................. 9-9
9.4.3 Client Sessions Report .......................................................................................... 9-11
9.4.3.1 Report Input........................................................................................... 9-11
9.4.4 User-Agent Report ................................................................................................ 9-14
9.4.4.1 Report Input........................................................................................... 9-14
9.4.5 Bandwidth Usage .................................................................................................. 9-16
9.4.5.1 Report Input........................................................................................... 9-16
9.4.6 HTTP Errors by Server ......................................................................................... 9-18
9.4.6.1 Report Input........................................................................................... 9-18
9.4.7 Alarms & Errors.................................................................................................... 9-20
9.4.7.1 Report Input........................................................................................... 9-20
9.4.8 HLS Manifest Detail ............................................................................................. 9-22
9.4.8.1 Report Input........................................................................................... 9-22
9.4.9 Publishing Outage Report ..................................................................................... 9-25
9.4.9.1 Report Input........................................................................................... 9-25
9.4.10 Client IP/UA Pairings Report ............................................................................... 9-26
9.4.10.1 Report Input........................................................................................... 9-26
IQDialogue ASM 4.0 User’s Guide — SUG-DIAASM-007 iii

Appendix A Video Uplink Client Setup
A.1 Virtual Uplink Setup .......................................................................................................... A-1
Appendix B Active Client and Alarm Configuration Descriptions

B.1 IQDialogue ASM Active Client Settings ............................................................................B-1
B.2 IQDialogue ASM Alarm Descriptions and Settings ...........................................................B-6
Glossary of Terms .......................................................................................................................... GL-1
Index............................................................................................................................................ Index-1
iv IQDialogue ASM 4.0 User’s Guide — SUG-DIAASM-007

Technical Support Information
1 Technical Support Information
Updated documentation, software, and information for this and other products are available
on the IneoQuest Web site or FTP server. If you do not have access to the IneoQuest FTP
server, contact your IneoQuest sales representative, IneoQuest Support, or a qualified
IneoQuest reseller for assistance.
1.1 Address and Telephone Numbers
Address, USA:
IneoQuest Technologies Inc.
170 Forbes Blvd.
Mansfield, MA
02048
Telephone, USA:
+1 508 339 2497
FAX Telephone Number, USA
+1 508 339 4727
Toll-Free Technical Support Telephone, USA:
+1 866 464 4636
1.2 Internet Addresses
E-Mail:
techsupport@ineoquest.com
URL:
FTP Server:
https://iq-ftp.ineoquest.com
1.3 About this Document
This document, IQDialogue® ASM 4.0 User’s Guide, provides operating and
troubleshooting instructions for IQDialogue ASM, an adaptive bitrate streaming monitoring
solution. For information regarding any other of IneoQuest’s products, please consult the
appropriate document.
IQDialogue ASM 4.0 User’s Guide — SUG-DIAASM-007 1-1

Technical Support Information
1.3.1 Documentation Feedback

We encourage you to provide feedback, comments, and suggestions so that we can improve
the documentation. Send e-mail to techpubs-comments@ineoquest.com with the following
information:
• Document title
• Document number (located on the cover page and document footer)
• Page number(s)
• Software version (for software documentation comments)
• Your name and company
1-2 IQDialogue ASM 4.0 User’s Guide — SUG-DIAASM-007

Overview
2 Overview
2.1 Product Definition
IQDialogue ASM (IQD ASM) is a service assurance probing platform for monitoring
Adaptive Bitrate video using a combination of both passive and active monitoring
techniques at various demarcation points throughout the video distribution workflow. With
IQD ASM technology, IneoQuest performs deep analysis of adaptive streaming video
distribution to provide 24x7 monitoring and alarming, enabling service providers to
measure the quality of the video delivery and troubleshoot impairment conditions to achieve
the highest video streaming experience.
IQD ASM provides a rich user interfaces to display comprehensive Adaptive Bitrate (ABR)
video data in familiar Web and Java based formats. Various views within the probe interface
allow for real-time performance analysis as well as detailed historical evaluation of each
adaptive video session, manifest, and chunk.
2.2 Product Overview
IQDialogue ASM provides real-time visual representation of all ABR messaging and
signaling. Video classification is performed in real-time on protocol type, content and
sessions status, with easy to understand color coding and asset aliasing. Configurable alarm
threshold settings and SNMP traps manage the system’s northbound notification, including
IneoQuest’s iVMS ASM and AMP platforms.
IQD ASM contains monitoring features that provide unique analysis capabilities in three
primary locations – Publishing, Intra-CDN (post origin serer) and Edge Cache, as well as
active monitoring capabilities to simulate client devices.
• Publishing – To ensure that all adaptive bitrate video is published from the packager to
the origin without error, IQDialogue ASM continuously monitors every variant of every
published asset. Alarming conditions notify operators of flow outages, missing
encryption keys, manifest and segment HTTP load errors, and MPEG PID loss.
• Intra-CDN – Content delivery networks are used to distribute video assets to the viewing
audience. Proper operation of the origin server and caching servers content is critical to
successful video distribution and the health of the delivery network. Whether using your
own CDN or a third party CDN, IQDialogue ASM provides extensive visibility in to the
performance of the origin server responding to video requests from shield or
mid-caches. IQDialogue ASM is uniquely positioned to categorize CDN performance
and provide detailed information to ensure proper operation, ensuring that all requests
are fulfilled and identifying error conditions for root cause analysis.

Overview
• Edge Cache – Positioned at the edge cache, IQDialogue ASM obtains session level
visibility to every user request, collecting metrics to determine the customer experience
associated with multiscreen services. IQD ASM edge cache monitoring enables
performance analysis and problem isolation by serving area, device, content type and
user session.
• Active Client – Beyond monitoring every user session using passive monitoring
throughout the distribution network, IQDialogue ASM also offers the ability to verify
content availability and adaptive protocol conformance by simulating client sessions for
configured video content. The Active Client function of the IQD ASM probe actively
requests content like a client device to validate that assets are available and assess the
quality of service delivery. In this function, the Active Client inspects each manifest file
and downloads every video chunk while performing various protocol checks to notify
the operator on key issues that could impact viewer experience, such as stale manifests,
unavailable encryption keys, chunks unable to be downloaded as well as potential buffer
underrun conditions that would lead to media player buffering.
In the IQDialogue ASM graphical interface, users can easily navigate from key performance
indicators, to real-time views and deep dive analysis of historical issues with just a click of a
button. Protocol and message filtering can be performed on a variety of factors to provide
detailed and targeted analysis.
2.2.1 Key Features

• 24x7 monitoring, alarming and logging of video assets
• Passive monitoring up to full 10G line rate traffic
• Up to 1Gpbs active monitoring of adaptive bitrate streams
• Dynamic parsing and conformance monitoring of playlists
• Supports Apple® HLS, Adobe HDS, Microsoft® Smooth Streaming, MPEG DASH,
RTSP, RTMP, and web publishing (HTTP put and webdav)
• Rich and extensible Dashboard GUIs with actionable Key Performance Indicators
(KPIs)
• Capable of full packet capture of monitored traffic
• Virtual Uplink to stream HLS content
• Auto-detection of signaling and vendor protocols with minimal configuration required
• Support for IneoQuest’s patented QoS metric, VeriStream
• Active Client and Alias configuration import and export via CSV
• Reports alarm and metric data to iVMS ASM for correlation and aggregation with
end-to-end monitoring system
• Verimatrix authentication and decryption
• Northbound SNMP Traps
• Report generation for sessions, errors, and alarms for historical analysis and trending

Overview
2.2.2 Monitoring and Analysis

• HTTP requests and responses timing and status code tracking, alarming, logging
• VeriStream QoS measurements and analysis of both passive and active monitored video
sessions
• Key Performance Indicators, including –
– Alarm Events
– Active Client Alarm Events
– Initiated Sessions
– HTTP Errors 4xx
– HTTP Errors 5xx
– Response Failure Rate
– Publishing Failure Rate
– Total Server Bandwidth
– VeriStream Distribution
– Client Type Distribution
– Top 10 Manifest Distribution
– HTTP Requests Per Server
• Real-Time Measurements and Metrics
– Number of Flows
– Number of Assets
– Chunks
– Manifests Requested
– Instant Bitrate
– Streams By VeriStream 1 – 5
– HTTP Errors 4xx
– HTTP Errors 5xx
– Request count by Manifest
– Manifest Request by Host
• Publishing Alarm Conditions
– Duplicate Manifest
– No Encryption Key
– Flow Outage
– RTMP Flow Outage
– MPEG-2 Non-conformance
– PUT Transfer Time
– Missing Chunk Error

Overview
– Chunk Per Minute Error

• Post-Origin Alarm Conditions
– 4XXFailure
– 4XXFailureThreshold
– 5XXFailure
– Chunk Variation
– Chunk Count Error
– Chunk Size Error
– Duplicate Chunk Requested
• Edge Cache Alarm Conditions
– 4XXFailure
– 5XXFailure
– Chunk Variation
– Chunk Count Error
– Chunk Size Error
• Active Client Alarm Conditions
– 4XXFailure
– 5XXFailure
– VeriStream Threshold Exceeded
– Request Failed
– Manifest Load Error
– Manifest No Content Error
– Manifest Parse Error
– Unable To Load Stream Chunk
– Manifest Same Content Error
– Connection Error
– Verimatrix Initialization and Decryption Error
– Bad VeriStream Chunk Count

Product Installation
3 Product Installation
This chapter provides the following information:

• Section 3.1, System Requirements
• Section 3.2, Requirements for Smooth Streaming Publishing Support
• Section 3.3, Requirements for Active Client Monitoring
• Section 3.4, Client Request or Content Distribution Monitoring (Association Mode)
Configuration
• Section 3.5, iVMS ASM Integration
3.1 System Requirements
IQDialogue ASM is provided in the form of an “appliance” product. There are two
appliances available, one providing 1-4Gb/sec of monitoring capacity, and another
providing 10Gb/sec of monitoring capability. The appliances are a hardened hardware
platform (1RU/2RU) which are specially prepared and configured to host IQDialogue ASM.
Beyond the monitoring capacity and physical footprint of the appliances, the features and
functionality are the same.
No special installation process or configuration of the appliance is required. The IneoQuest
support team will pre-configure the appliance (IP addressing and monitoring ports) based on
the provided and specific customer requirements.
Any changes to the default configuration of the appliance can be applied, but should be
coordinated with the help of the IneoQuest support team (techsupport@ineoquest.com).
The 1-4Gb/sec appliance provides six Gigabit Ethernet ports. Four Gigabit interfaces can be
used for either passive or active adaptive bitrate video monitoring. The two remaining
Gigabit Ethernet ports can serve as a management interface used to connect to the
IQDialogue ASM server and remote management.
A Web browser (such as Mozilla Firefox or Microsoft’s Internet Explorer), with support for
JavaScript, must also be installed on the personal computer acting as the client agent.
Multiple clients can access the same instance of IQDialogue ASM, with no concurrent user
limitations, beyond the performance limitations of the computing platform. Refer to the
IQDialogue ASM 4.0 Release Notes for the tested and approved Web browser versions and
Java requirements.
The IQDialogue appliance also provides an ILOM (Integrated Lights Out Management)
facility. Instructions and support for the setup and configuration of the ILOM can be
obtained by contacting techsupport@ineoquest.com .

3.2 Requirements for Smooth Streaming

Publishing Support
The unique nature of encoders publishing content to an IIS origin server requires special
configuration on the IQDialogue ASM for better support.
• The IP address of each encoder’s publishing output interface must first be configured
appropriately in the “Encoder Publishing” tab.
• After configuration IQDialogue ASM must be manually restarted to complete the
configuration change. Please contact the IneoQuest support team for help with this
procedure, at techsupport@ineoquest.com.
• In most cases, the encoder(s) Smooth Streaming services/sessions must be started
“after” the IQDialogue ASM is restarted with the updated configuration. Failure to
restart Smooth Streaming services may cause the currently active flows to be
unrecognized for long periods of time.
3.3 Requirements for Active Client Monitoring
When licensed, the IQDialogue ASM probe can perform active client requests (Adobe HDS,
Apple HLS, and Microsoft Smooth Streaming) for adaptive bitrate video using one of the
gigabit interfaces. This interface must be selected and configured appropriately (IP address,
etc.). This configuration is performed on several components and it’s recommended that you
contact the IneoQuest support team before proceeding with this change.
• One of the Gigabit Ethernet interfaces must be configured at the operating system level
with an appropriate IP address, please contact the IneoQuest support team for help with
this procedure at techsupport@ineoquest.com.
• The configuration file “/etc/iqd.conf” must be edited accordingly to link the appropriate
interface to use:
– The line entry “#ASM_CLIENT_INTERFACE=” must be uncommented and
configured with the IP address of the interface to use
• IQDialogue ASM must then be manually restarted for this change to take place. Please
contact the IneoQuest support team for help with this procedure, at
techsupport@ineoquest.com.
3.4 Client Request or Content Distribution

Monitoring (Association Mode) Configuration
IQDialogue ASM monitors ABR traffic requests at many different points in the network. In
most cases, IQD ASM should be localized to either monitoring Client requests (end-users)
to edge caches or for content distribution traffic between encoder /publisher/packager to
origin, origin to mid-caches, origin to edge-caches or mid-caches to edge-cache.

Isolating the monitored traffic allows IQDialogue to either create logical end-user viewing
sessions in the census and reporting, or to treat every HTTP GET request as individual
HTTP transfers requests. These two modes of operation are association mode and
non-association mode.
The IQDialogue ASM probe can be manually forced in either mode by using the
“http.associate.sessions” configuration value in the “IQD Settings” section of the
Configuration tab.
• Association Mode – When “http.associate sessions” is enabled, IQDialogue will
associate chunk/fragment requests together to create a logical end-user viewing session.
• Non-Association Mode – When “http.associate.sessions” is disabled, IQDialogue will
treat every HTTP Get request as an individual session. The only exception to this is if
IQDialogue ASM detects unique cookies or tokens used by the IQD ASM Active Client
function in the probe. If detected, even when “http.associate.sessions” is disabled,
IQDialogue will create logical sessions for those requests.
HTTP based publishing content is not affected by this mode or feature.
3.5 iVMS ASM Integration
There is no configuration required on the IQDialogue ASM probe for it to properly interface
with an IneoQuest iVMS ASM system. All of the configuration is performed on the
iVMS ASM.


Web Interface Session Monitoring
4 Web Interface Session Monitoring
IQDialogue ASM makes use of a Web based user interface to access detailed probe
information and monitoring data during product setup and troubleshooting investigations.
The Web interface is reached from a browser using the IP address of the probe and port
8080. For example, if the management IP address of the IQDialogue ASM probe is
“192.168.1.100”, the URL to connect to is “http://192.168.1.100:8080”. Figure 4-1 displays
the main operating screen.
Figure 4-1: IQDialogue ASM Main Operating Screen
This chapter provides the following information:

• Section 4.1, Menu Layout and Filters
• Section 4.2, Interface and Traffic Monitoring Details
• Section 4.3, Streaming Protocols

4.1 Menu Layout and Filters
At the top of the page, you will see the “Edition” name and the version number of
IQDialogue ASM.
You are also presented with the four main sections of operations:
• Session Monitoring
• File Capture
• Setup
• String Filter
This is an option to perform a “String Filter” on the parsed events. The “string” value
can be an IP address, a MAC address, etc. This allows for quick troubleshooting and
targeting of specific traffic types or events in the monitoring window.
Several other ancillary functions are provided through the use of “buttons”:
• Reset: Eliminates all data currently resident in volatile memory for the IQDialogue
ASM Server (faults and aged entries).
• Clear: Eliminates aged (grayed-out) or non-significant data from the user interface.
The following icon “ ” (green or red), provides the operator with the status of the
IQDialogue ASM Web interface engine. This is particularly useful when accessing
IQDialogue ASM remotely or when multiple users are connected to the same IQDialogue
ASM server instance. If the icon is red, then IQDialogue ASM needs to be restarted.
The “Running” option permits the operator to “freeze” the information displayed on the
screen. When monitoring active systems, the display might get updated with so much
information that it might make it hard to track specific messages. By turning-off this option,
you freeze the user interface, but not the background processing of events, or the database
storage of transactions.
The “Delay(ms)” value enables the operator to select the preferred refresh rate of the
information displayed. The value is expressed in milliseconds, and although values of less
than 200ms are accepted, below that threshold some events processed might not get
displayed on the screen due to the timing and performance of the JavaScript processing
engine in the browser of the client.
You can also select the “types” of traffic, transactions, and events of interest to be shown:
• ASM Census: Provides a high-level overview of the types of ABR traffic being
analyzed.
• RTSP/Control: Provides detailed analysis of RTSP based messaging traffic.
• HLS / Publish: Provides detailed analysis of Apple HLS based traffic. The “Publish”
filter will only show the HLS Publishing flows (WEBDAV) from an ABR encoder to an
origin server.

• Smoothstreaming / Publish: Provides detailed analysis of Microsoft Smooth Streaming

based traffic. The “Publish” filter will only show the Smooth Streaming Publishing
flows from an ABR encoder to an origin server.
• RTMP: Provides visibility into RTMP (Real Time Messaging Protocol) transactions.
• RTCP/Report: Provides visibility into RTCP (RTP Control Protocol) transactions. This
particular feature is available through special licensing only, please contact IneoQuest at
techsupport@ineoquest.com for more information.
• Faults Only View: Provides visibility into the faults.
• MobiTV: Provides visibility into MobiTV client requests. Support for MobiTV is
experimental at this time. Please contact IneoQuest at techsupport@ineoquest.com for
more information.
• Mediaroom: Provides visibility into the legacy Microsoft Mediaroom VOD progressive
download mechanism. This particular feature is available through special licensing only,
please contact IneoQuest at techsupport@ineoquest.com for more information.
• DASH: Provides visibility into the DASH adaptive streaming protocol. DASH is still an
immature protocol, and as such subject to various changes in implementation. For
proper support please contact IneoQuest at techsupport@ineoquest.com to validate your
implementation.
• NDS: Provides visibility into adaptive streaming traffic using the “NDS” protocols.
• RTP: Provides visibility into RTP encapsulated traffic.
• Adobe HDS: Provides visibility into the Adobe HDS streaming protocol.
• OTT: Provides visibility into “Over-The-Top” video transfers. Support for OTT traffic is
experimental and subject to change due to the inherent nature of Internet based video
technology. Please contact IneoQuest at techsupport@ineoquest.com for more
information or specific monitoring requirements.
Note: This view/information is only applicable for unecrypted OTT video. Since most
OTT services transitioned to using HTTPS connection, these screens will not be
populated
4.2 Interface and Traffic Monitoring Details
At the bottom of the page, you are shown which network interface(s) is(are) currently being
used to monitor the traffic, packets, and traffic statistics per monitoring interface, and the
delay (if any) in buffering transactions for database logging.
Row entries in any of the filter tables are color coded for quick visual interpretation and
sorting. Refer to the following list for a description of the various colors:
• Red: A transaction, flow, or event that was deemed erroneous or that failed. Red entries
also represent errors that would generate an SNMP trap from the IQDialogue ASM
Northbound Services Agent.
• Green: A transaction, flow, or event that succeeded, or traffic of a certain type being
observed at a rate greater than 1 packet per 10 seconds.

• Light Green: Light green rows indicate that traffic (of a specific type or on a specific
interface) was recently analyzed, but no packets have been seen in the last 10 seconds.
• Grey: Grey represents a stale entry. A stale entry is older than 30 seconds. These entries
are automatically purged from the interface after 60 seconds, but can also be manually
purged by clicking on the “clear” button.
• Orange: Orange is used to identify transactions that have yet to see a response back
from a server/client. It represents a waiting stage of 5 seconds. IQDialogue ASM (for
appropriate transactions) will wait 5 seconds for a reply before classifying it as a failed
transaction.
4.3 Streaming Protocols
Each of the supported protocols are represented in the IQDialogue ASM Web Interface.
Based on the selected protocol in the top level menu, the bottom pane displays details of all
applicable streaming sessions. This section provides details of each field displayed by
protocol type.
4.3.1 Apple HLS Traffic

Figure 4-2 provides an example of Apple HLS traffic monitoring:
Figure 4-2: Apple HLS Traffic Monitoring
The layout format is:

• NIC: The interface number (as seen on the setup page) on which the traffic was
monitored.
• Pump: The “Pump” thread number that is processing this session. This information is
for the benefit of IneoQuest engineering personnel.
• Client:Port: listing of the IP address and port of the client making the Apple HLS
request, or in this case of Publishing the IP and port of the ABR encoder.
• Server:Port: listing of the IP address and port of the server receiving the Apple HLS
request, or in this case of Publishing the IP and port of the origin server receiving the
content.
• Bytes: The number of bytes sent by both the client and server.
• Packets: The number of packets sent by both the client and server.
• Seqno: The sequence number of the last packet exchange between the client and server.
• Window/Count(<256): The TCP Window size of the HTTP exchange.
• Dups OOSeq: The number of duplicate packets and/or Out-Of-Sequence packets
analyzed for the particular HTTP session.
• Part #: The logical number of parts (often referred to as chunk) analyzed by IQDialogue
for a particular Apple HLS session. When a chunk in question is an index (also called a
manifest) file, a “+” button is provided. When pressed a pop-up window will appear to
detail the contents of the index file, as shown in Figure 4-3.

Figure 4-3: Index File Contents
• T1/T2/T3/T4: The time-based calculation markers between chunk requests required to

compute the IneoQuest VeriStream metrics. Please contact IneoQuest at
techsupport@ineoquest.com for more information on the VeriStream metric. It should
be noted that VeriStream metrics are not calculated on the Publishing of Apple HLS
content.
• FRB(sys) / FRB(ft): The IneoQuest VeriStream metrics for system and file transfers.
Please contact IneoQuest at techsupport@ineoquest.com for more information on the
VeriStream metric. It should be noted that VeriStream metrics are not calculated on the
Publishing of Apple HLS content.
• Quality (kbps): The quality column is calculated from the bitrate (in kbps) of the chunk
size and transfer. It is meant to be used as an indication of the encoded bitrate of the flow
being requested by the client. It should be noted that quality metrics are not shown for
the Publishing of Apple HLS content in the web GUI, but are available from the NBS
GUI client.
• Request / Response: The HTTP meta-data from the client and server request and
response.
• Status: Timestamp of the last seen message, and the HTTP/TCP transaction state (i.e.,
Finsent, Finback, etc.).

4.3.2 Microsoft Smooth Streaming Traffic

Figure 4-4 provides an example of Microsoft Smooth Streaming analysis.
Figure 4-4: Microsoft Smooth Streaming Analysis

monitored.
• Client :Port: listing of the IP address and port of the client making the Microsoft
Smooth Streaming request, or in this case of Publishing the IP and port of the ABR
encoder.
• Server :Port: listing of the IP address and port of the server receiving the Microsoft
Smooth Streaming request, or in this case of Publishing the IP and port of the origin
server receiving the content.

• Part #: The logical number of parts (often referred to as chunk) analyzed by IQDialogue
ASM for a particular Microsoft Smooth Streaming session. When a chunk in question is
an index (also called a manifest) file, a “+” button is provided. When pressed a pop-up
window will appear to detail the contents of the index file as shown in Figure 4-5.
Figure 4-5: Index File Contents

mailto:techsupport@ineoquest.com for more information on the VeriStream metric. It
should be noted that VeriStream metrics are not calculated on the Publishing of
Microsoft Smooth Streaming content.
Please contact IneoQuest at mailto:techsupport@ineoquest.com for more information on
the VeriStream metric. It should be noted that VeriStream metrics are not calculated on
the Publishing of Microsoft Smooth Streaming content.
• Offset / Duration: The chunk offset and duration. The duration refers to the time length
of the audio/video chunk being transferred.
size and transfer, as well as the chunk type (audio or video). It is meant to be used as an
indication of the encoded bitrate of the flow being requested by the client. It should be
noted that quality metrics are not shown for the Publishing of Microsoft Smooth
Streaming content in the Web GUI, but are available from the NBS GUI client.

response.
• Status: Timestamp of the last seen message and the HTTP/TCP transaction state (i.e.,
Active, Finsent, Finback, etc.).
4.3.3 OTT (Over-The-Top) Internet Video Traffic

Figure 4-6 provides an example of OTT Stream traffic monitoring.
NOTE: This view/information is only applicable for unecrypted OTT video. Since most
OTT services transitioned to using HTTPS connection, these screens will not be
populated
Figure 4-6: OTT Stream Traffic Monitoring

monitored.
• Client :Port: listing of the IP address and port of the client making the OTT video
request.
• Server :Port: listing of the IP address and port of the server receiving OTT video
request.

• Part #: The logical number of parts (often referred to as chunk) and/or HTTP
“byte-ranges” analyzed by IQDialogue ASM for a particular OTT session.
techsupport@ineoquest.com for more information regarding the VeriStream metric. It
should be noted that full VeriStream metrics are not calculated on OTT content because
of the obfuscation or encryption of the index file request.
VeriStream metric. It should be noted that full VeriStream metrics are not calculated on
OTT content because of the obfuscation or encryption of the index file request.
size and transfer. It is meant to be used as an indication of the encoded bitrate of the flow
being requested by the client. It should be noted that quality metrics are not shown for
the Publishing of Apple HLS content in the Web GUI, but are available from the NBS
GUI client.
response.
4.3.4 MobiTV Traffic

Figure 4-7 provides an example of MobiTV traffic monitoring.
Figure 4-7: MobiTV Traffic Monitoring

monitored.
• Client :Port: listing of the IP address and port of the client making the MobiTV video
request.
• Server :Port: listing of the IP address and port of the server receiving MobiTV video
request.
• Part #: The logical number of parts (often referred to as chunk) and/or HTTP
“byte-ranges” analyzed by IQDialogue ASM for a particular session. Not fully
supported at this time (as of IQDialogue ASM release 1.1.58).
techsupport@ineoquest.com for more information on the VeriStream metric. It should
be noted that full VeriStream metrics are not calculated on MobiTV content at this time.
VeriStream metric. It should be noted that full VeriStream metrics are not calculated on
MobiTV content at this time.
• Bitrate/Avg(mbps): An estimated average bitrate calculation of the requested media.
response.
• Status: Timestamp of the last seen message, and the HTTP/TCP transaction state (i.e.,
4.3.5 RTMP
Figure 4-8 provides an example of RTMP traffic monitoring.

Figure 4-8: RTMP Traffic Monitoring

monitored.
• Client :Port: listing of the IP address and port of the client making the MobiTV video
request.
• Server :Port: listing of the IP address and port of the server receiving MobiTV video
request.
• Audio/Video FLV: The amount of data (in bytes) monitored as distinct audio and video
packets within the RTMP encapsulation.
• Client Sync/Server Sync: The status of the RTMP session in progress. Note, if
IQDialogue ASM was not able to monitor the start of the session it will display “off
Sync”.
• Bitrate/Avg (Mbps): The current and average bitrate of the RTMP session in Mbps.
• Trick Play: The status of the RTMP session in progress. Note, if IQDialogue ASM was
not able to monitor the start of the session it may affect detecting the current state.
• Status: Timestamp of the last seen message, and the RTMP transaction state (i.e., Idle,
active, etc.).

4.3.6 Mediaroom
Figure 4-9 provides an example of Mediaroom Legacy VOD traffic monitoring.
Figure 4-9: Mediaroom Legacy VOD Traffic

Monitoring

monitored.
• Client :Port: listing of the IP address and port of the client making the Mediaroom VOD
Streaming request.
• Server :Port: listing of the IP address and port of the server receiving the Mediaroom
Streaming request.
• Part #: this field is not used or pertinent for Mediaroom VOD transactions. When an
HTTP request in question is an index (also called a manifest) file, a “+” button is
provided. When pressed a pop-up window will appear to detail the contents of the index
file as shown below in Figure 4-10.

Figure 4-10: Mediaroom Legacy VOD Traffic

Monitoring
• T1/T2/T3/T4: The time-based calculation markers between byte-range requests.

This value is not used for Mediaroom VOD transactions and should remain as “0”.
• Offset / Duration: The chunk offset and duration. The duration refers to the time length
of the audio/video chunk being transferred.
indication of the encoded bitrate of the flow being requested by the client.
response.
4.3.7 Adobe HDS

Figure 4-11 provides an example of Adobe HDS traffic monitoring.

Figure 4-11: Adobe HDS Traffic Monitoring

monitored.
• Client :Port: listing of the IP address and port of the client making the Adobe HDS
request.
• Server :Port: listing of the IP address and port of the server receiving the Adobe HDS
request.
• Part #: The logical number of parts (often referred to as chunk or fragment) analyzed by
IQDialogue ASM for a particular Adobe HDS Streaming session. When a chunk in
question is an index (also called a manifest) file, a “+” button is provided. When pressed
a pop-up window will appear to detail the contents of the index file as shown below in
Figure 4-12.

Figure 4-12: Index File Details

techsupport@ineoquest.com for more information on the VeriStream metric.
VeriStream metric.
• Bitrate/Avg (Mbps): The quality column is calculated from the bitrate (in Mbps) of the
chunk size and transfer, as well as the chunk type (audio or video).
response.
4.3.8 RTP/RTCP
Figure 4-13 provides an example of Adobe RTP traffic monitoring.

Figure 4-13: RTP Traffic Monitoring

monitored.
• Client :Port: listing of the IP address and port of the client initiating the RTP session.
• Server :Port: listing of the IP address and port of the server receiving the RTP session.
• Payload Type: The RTP payload type advertised in the RTP packets, as per the RFC
definitions.
• Pkt Missing: Count of missing RTP packets as detected by IQDialogue based on
sequence number of packets.
• OOSeq: The number of Out-Of-Sequence packets analyzed for the particular RTP
session.
• Status: Timestamp of the last seen message and the RTP transmission state (i.e., In
Progress, Finsent, Finback, etc.).
4.3.9 NDS
Figure 4-14 provides an example of NDS traffic monitoring.

Figure 4-14: NDS Traffic Monitoring

monitored.
• Client :Port: listing of the IP address and port of the client making NDS request.
• Server :Port: listing of the IP address and port of the server receiving the NDS request.
IQDialogue ASM for a particular NDS Streaming session. When a chunk in question is
window will appear to detail the contents of the index file as shown in Figure 4-15.

Figure 4-15: NDS Index File Details

VeriStream metric.
response.
4.3.10 DASH
Figure 4-16 provides an example of DASH traffic monitoring.

Figure 4-16: DASH Traffic Monitoring

monitored.
• Client :Port: listing of the IP address and port of the client making DASH request.
• Server :Port: listing of the IP address and port of the server receiving the DASH request.
IQDialogue ASM for a particular NDS Streaming session. When a chunk in question is
window will appear to detail the contents of the index file as shown below in
Figure 4-17.

Figure 4-17: DASH Index File Details

VeriStream metric.
response.


Libpcap Support
5 Libpcap Support
5.1 Libpcap Playback and Capture
Another option available is “File Capture”. This section is where you can capture network
traffic (in the same style and format as Ethereal/Wireshark®). Figure 5-1 provides a view of
this page.
Figure 5-1: “File Capture” Page
The different sections are:

• Capture NIC: In this field, you select the Capture Network Interface Card (NIC).
• Capture Filter: You type in the filter limitations in this field and click Set Filter.
• Capture Filter Result: This field displays the filter setting results.

Libpcap Support
• Capture File: In this field, you provide the path and filename of the libpcap capture file
that you want to create during the monitoring or emulation. The path is referenced as
“c:\program files\ineoquest\iqdialogue\captures”, as long as the default installation
parameters are used. On Solaris it can be found in “/export/home/iqdialogue/captures”
and on Linux in “/home/iqdialogue/captures”. Capture files are limited to 2 Gigabyte
per file in order to retain Wireshark compatibility (maximum file sizes).
• Download Capture file: In this field, you can select which file previously captured to
download. You can also select a file from the drop-down list and click on the Delete
button to remove it from the file system.

Disk and Database Logging
6 Disk and Database Logging
6.1 Database Transactions Logging and Sizing
IQDialogue ASM makes extensive use of a back-end database to store metadata about every
packet, flow and transaction monitored.
IQDialogue ASM will automatically “purge” the database of any transactions older than
seven days (always keeping seven days of data accessible in the database). The retention
period can be changed and increased, to a maximum of 31 days, in the “Configuration” tab
menu (see Section 8.7, Configuration).
NOTE: No changes, modifications, alterations are to be performed on the IQDialogue
ASM database schema and tables, nor to any of the triggers and/or stored
procedures without contacting IneoQuest support services at
techsupport@ineoquest.com. Any such change could render the application
inoperative and invalidate support.
6.2 Database Purging
Through the use of the IQDialogue ASM Northbound GUI Services, the operator can define
multiple parameters as to the amount of time transactions are kept in the database. Entries
older then the defined period will be purged according to the configured schedule
This can ensure that the database does not keep growing infinitely, and also ensures proper
levels of performance from the application.

Disk and Database Logging

Software Upgrade
7 Software Upgrade
Performing an IQDialogue ASM software upgrade will re-initialize the system database. As
a result, historical performance and alarming data is purged from the system. All system
configuration settings will be maintained through the upgrade process so reconfiguration is
not necessary.
If the IQDialogue ASM is reporting to an iVMS ASM system, aggregated historical data
will remain available until the purge as configured on the iVMS ASM.
A Maintenance Operations Procedures (MOP) document can be provided with detailed
instructions of the upgrade process. Please contact IneoQuest at
techsupport@ineoquest.com for details or a copy of this documentation.
7.1 Appliance Based Platform
Before upgrading to a newer release, the previous IQDialogue ASM server software must be
removed using the procedures defined in the provided MOP.
NOTE: Upgrades to existing systems should only be performed after a MOP has been
issued by IneoQuest.

Software Upgrade

Northbound Services (NBS) GUI, Dashboards, and Alarming
8 Northbound Services (NBS) GUI,

Dashboards, and Alarming
This chapter provides details about the Northbound Services (NBS) user interface.
• Section 8.1 Accessing the NBS GUI
• Section 8.2 Home/Key Performance Indicators (KPI)
• Section 8.3 Realtime Census
• Section 8.4 Active Client
• Section 8.5 Query
• Section 8.6 Reporting
• Section 8.7 Configuration
• Section 8.8 About
8.1 Accessing the NBS GUI
IQDialogue ASM provides a Java applet to manage the IQDialogue ASM and get graphical
representation of the ABR activity, alarms, and configurations. This Java applet provides
visibility to the Key Performance Indicators (KPI), Census, Dashboards, Alarming, Reports,
and Configuration.
8.1.1 Java Requirements

IQDialogue ASM NBS GUI client is a Java Web Start application requiring that Java SE
Runtime Environment 8 must be installed on the computer accessing the GUI. When the
IQDialogue ASM probe is upgraded, the Java Cache needs to be cleared before accessing
the updated IQDialogue NBS GUI client application.
NOTE: If you are going to log into the NBS GUI for the first time, the URL of the IP
address and port information (8172) of the IQDialogue ASM must be added as a
security exception in the Java Control Panel on your computer. For example, if
the management IP address of the IQDialogue ASM probe is “192.168.1.100”,
the URL to connect to it would be “http://192.168.1.100:8172”. Instructions for
managing the Java Control Panel Exception Site List are located at
https://www.java.com/en/download/faq/exception_sitelist.xml.

8.1.2 Logging into the NBS GUI

Step 1 Open a Web browser and enter the URL from the IP address of the probe, and use port
8172. For example, if the management IP address of the IQDialogue ASM probe is
“192.168.1.100”, the URL to connect to it would be “http://192.168.1.100:8172”.
Upon launching NBS, a login screen appears as shown in Figure 8-1.
Figure 8-1: NBS Login Screen
Step 2 Enter your Username. The default username for NBS is nbsmon.
Step 3 Enter your Password. The password for the nbsmon account is also nbsmon.
Step 4 Enter or select the Host. This is the IP address or hostname of the IQDialogue ASM
probe to connect to.
Step 5 Click Connect.
Once logged-in, you have access to the full NBS selections.
8.2 Home/Key Performance Indicators (KPI)
The Home (KPI) section is sub-divided into three (with special licensing up to seven) views
for ease of use:
8.2.1 Transactions
The Transactions tab provides KPIs relating to the number of events by protocols types, as
shown in Figure 8-2.

Figure 8-2: Full NBS Access
8.2.1.1 Alarm Events

Alarm Events provides visibility into the alarms raised by the probe based on the configured
monitoring parameters. Alarm Events are shown for the last hour, day, and seven days. The
maximum value of the KPI, as well as the visual “red” threshold for each value is defined in
the “Configuration” tab. To obtain detailed listings of the alarms in any time period, “click”
the appropriate bar in the Alarm Event graph. This action will initiate a pop-up window with
more information, as shown in Figure 8-3.

Figure 8-3: Alarm Event Distribution Pop-up

Window
8.2.1.2 HTTP Sessions Initiated

HTTP Sessions Initiated shows the number of Adaptive Bitrate HTTP sessions that have
started in the last minute, hour, and day. This is not to be confused with the number of
current sessions currently being monitored. The KPI represents all sessions initiated which
may or may not still be active. The maximum value of the KPI, as well as the visual “red”
threshold for each value is defined in the “Configuration” tab. To obtain detailed listings of
the HTTP Sessions Initiated in any time period, “click” the appropriate bar in the HTTP
Sessions Initiated graph. This action will initiate a pop-up window with more information,
as shown in Figure 8-4.

Figure 8-4: HTTP Flow Count Pop-up Window
8.2.1.3 HTTP Publishing Sessions

HTTP Publishing Sessions provides visibility into the number and type (Apple HLS and
Microsoft Smooth Streaming) of Adaptive Bit Rate (ABR) Publishing being analyzed by
IQDialogue ASM. See the example shown in Figure 8-5.

Figure 8-5: HTTP Publishing Sessions
8.2.1.4 HTTP Errors 4XX

HTTP Errors 4XX provides details on the HTTP errors in the 400 range that have been
analyzed by IQDialogue ASM. The maximum value of the KPI, as well as the visual “red”
threshold are defined in the “Configuration” tab. When the KPI is “clicked”, a pop-up
window appears with several options to show the errors by client requests, by publishing, or
on a time-graph. Furthermore, the top level pop-up window for the client requests and
publishing requests can also be “clicked” to get detailed listing about all the events. An
Export button is provided to extract the data in a comma separated values (CSV) format.
Example screenshots are provided in Figure 8-6 and Figure 8-7.

Figure 8-6: HTTP Errors
Figure 8-7: HTTP Errors Display

8.2.1.5 HTTP Errors 5XX

HTTP Errors 5XX provides details on the HTTP errors in the 500 range that have been
analyzed by IQDialogue ASM. The maximum value of the KPI, as well as the visual “red”
threshold are defined in the “Configuration” tab. When the KPI is “clicked”, a pop-up
window appears with several options to show the errors by client requests, by publishing, or
on a time-graph. Furthermore, the top level pop-up window for the client requests and
publishing requests can also be “clicked” on to get detailed listing about all the events. An
export button is provided to extract the data in a CSV format.
8.2.1.6 Response Failure Rate

Response Failure Rate is the percentage of HTTP request failures over a rolling time
window. Shown are the total number of HTTP requests, the number of successful requests,
and the number of failed requests. The maximum value of the KPI, as well as the visual
“red” vertical threshold are defined in the “Configuration” tab.
8.2.1.7 Publishing Failure Rate

Publishing Failure Rate is the percentage of HTTP Publishing event failures over a rolling
time window. Shown are the total number of HTTP Publishing events, the number of
successful events, and the number of failed events. The maximum value of the KPI, as well
as the visual “red” vertical threshold are defined in the “Configuration” tab.
8.2.1.8 Active Alarms

Additionally, in the “Transactions” sub-tab of the KPI tab you will find an “Active Alarms”
section, as shown in Figure 8-8, that can be expanded or collapsed with the “arrow” in the
top-right corner.
Figure 8-8: Active Alarms
The “Active Alarms” tab provides a view into the number and state of publishing alarms.
All stateful publishing alarms are shown in the table. The bar graph on the left provides
information on the number of such events in the last minute, hour and day. Additionally, it
can be “clicked” on to provide more detailed information. Once a publishing issue is
resolved, the alarm will automatically clear. Publishing alarms can be manually cleared by
right-clicking the entry and selecting “Clear Alarm” or “Clear All Alarms”. Stateful
publishing alarms can be seen and configured in the “Alarms” tab of the NBS.

8.2.2 Distribution
The Distribution tab provides KPIs relating to the client types, bandwidth usage and popular
assets, as shown in Figure 8-9.
Figure 8-9: Distribution
8.2.2.1 VeriStream Metric Distribution

VeriStream Metric Distribution displays the various VeriStream state of ABR chunk
requests. Please contact IneoQuest at techsupport@ineoquest.com for more information on
the VeriStream metric. Right-clicking the KPI allows the user to select the time-period to be
reflected. The time period selections are real-time, last hour, and last day. See Figure 8-10
for an example of VeriStream Metric Distribution.

Figure 8-10: VeriStream Metric Distribution
8.2.2.2 Bandwidth Usage

Bandwidth Usage shows the total amount of bandwidth being analyzed by IQDialogue
ASM across all monitoring interfaces. The maximum value of the KPI is defined in the
“Configuration” tab. See Figure 8-11 for an example of Bandwidth Usage KPI. By
“Clicking” on the KPI, a pop-up window will provide the amount of bandwidth monitored
on a per interface basis.
Figure 8-11: Bandwidth Usage

8.2.2.3 Client Type Distribution

Client Type Distribution shows the HTTP Client types (based on the user-agent provided in
the HTTP requests), for a selected time-period. By right-clicking on the KPI, the user can
select the time-period to be reflected. The time period selections are real-time, last hour, and
last day. Figure 8-12 provides an example of Client Type Distribution.
Figure 8-12: Client Type Distribution
8.2.2.4 Top 10 Manifest Distribution

Top 10 Manifest Distribution shows the most requested content (based on the number of
index/manifest requested) for a selected time-period. By right-clicking on the KPI, you can
select the time-period to be reflected. The time period selections are last hour and last day.
Figure 8-13 provides an example of Top 10 Manifest Distribution.
Figure 8-13: Top 10 Manifest Distribution

8.2.3 Alarms Timeline

The Alarms Timeline graph provides access to a 7 day historical view of error rate, aligning
trouble investigations with overall system performance or short-term analysis of system
performance for reporting video network performance to stakeholders. The Alarms view
depicts errors over time with real-time updates. Slider controls focus the view on a shorter
time window for deeper analysis. See Figure 8-14.
Figure 8-14: Alarms
8.2.4 RTSP
RTSP shows the number of Real Time Streaming Protocol (RTSP) events detected and
analyzed by the IQDialogue ASM probe, over selected time periods, as shown in
Figure 8-15.

Figure 8-15: RTSP Events
8.2.5 RTMP
RTMP shows the number of Real Time Messaging Protocol (RTMP) sessions currently
active and being analyzed by the IQDialogue ASM probe, as shown in Figure 8-16. The KPI
can be “clicked” on to provide detailed information about each active session.
Figure 8-16: RTMP Sessions
8.2.6 Smooth Streaming

The Smooth Streaming tab page shows the Request Count by Manifest, Manifest Requests
by Host, and HTTP Transactions including Manifest and Manifest Parts in the top pane. The
bottom pane displays the Alarms Processed and the time that the last trap was sent. See
Figure 8-17 for an example.

Figure 8-17: Smooth Streaming Tab Display
You can look up a Status Code for HTTP Transactions in the Manifest and Manifest Parts by
selecting the line and right-clicking your mouse. A context menu item appears with a
selection to look up the status code.
8.2.7 HLS
The HLS tab page shows the Request Count by Manifest, Manifest Requests by Host, and
HTTP Transactions including Manifest and Manifest Parts in the top pane. The bottom pane
displays the Alarms Processed and the time that the last trap was sent. See Figure 8-18 for
an example.

Figure 8-18: HLS Tab Display
8.2.8 HDS
The HDS tab page shows the Request Count by Manifest, Manifest Requests by Host, and
an example.

Figure 8-19: HDS Tab Display
8.2.9 DASH
The DASH tab page shows the Request Count by Manifest, Manifest Requests by Host, and
an example.

Figure 8-20: DASH Tab Display
8.3 Realtime Census
In the Realtime Census tab you gain visibility to the real-time ABR sessions currently in
progress. There are two sub-tabs: All Clients and Active Clients.
8.3.1 All Clients

The All Clients sub-tab screen is divided into the following three sections:
• Top Pane
• Top Census Pane
• Bottom Census Pane
Figure 8-21 shows an example of the All Clients sub-tab page.

Figure 8-21: All Clients Sub-tab Page
• Top pane
– The top pane provides a list of “filters” which can mask all other traffic except
for the one selected. The filters are grouped in two categories:
 Streams: To select a specific streaming format
 Filters
 Errors: For any HTTP errors in the 400 or 500 range
 String Filter: for specific data in the columns shown in the upper
central pane, as shown in Figure 8-22.

Figure 8-22: String Filter
 HTTP Gets: To select or deselect visibility to HTTP get requests

 HTTP Publishing: To select or deselect visibility to HTTP
Publishing traffic
– Also provided are three buttons:
 Reset: Used to remove all filters and bring back to default view
 Pause: Used to “Pause” the live view. Only the “view” is paused,
IQDialogue ASM is still processing data in the background
 Query: This button can be used to display in the census window the
active sessions analyzed between a selectable time-frame, as shown in
Figure 8-23.

Figure 8-23: Census Query
• Top Census pane

– The top census pane provides a high-level view of the various real-time sessions
being analyzed. The fields shown are:
 Start/End Time: The time stamp at which IQDialogue ASM detected the
start and end time of the ABR sessions
 Source/Destination: The source and destination IP address and port
numbers for the ABR sessions
 HTTP Type
 GET: For a client making a request
 PUT: For a publishing flow
 AC: For an Active Client session
On both the ASM Census and Active Client screens, the Active Client
monitoring sessions are displayed with additional information for several
possible conditions. Active Client sessions, sessions identified as HTTP Type
“AC” will be highlighted with the appropriate color coding as defined by the
condition and color index shown in Table 8-1 and Table 8-2.

Table 8-1. Session Table (Top)
Color Description
Flow is timing out
Flow has been redirected
Table 8-2. Session Details (Bottom)
Color Description
VS Columns are greyed out if the flow is of type RTMP/RTP/RTSP
Chunk is tagged with Discontinuity marker
Chunk is tagged as add splice
VS column color if the values is causing bad VS values
 User Agent: The user-agent field taken from the client’s HTTP requests
 Format: The type of session (Apple HLS, Microsoft Smooth Streaming,
etc.) Status: Shown in the “status” column are the VeriStream metrics for
the last 8 requested chunks in the client session (for publishing sessions
the status is always “Balanced” (dark green), and not available for certain
non-HTTP based protocols such as RTP. Please contact IneoQuest at
techsupport@ineoquest.com for more information on the VeriStream
metric.
 Manifest Requested: The number of times that the client issues a request
for a manifest or index file. For an Apple HLS publishing session this
value represents the number of times a new manifest was published to an
origin servers for a particular flow. For a Smooth Streaming publishing
session this represents the number of times the ABR encoder requested
the manifest file from the IIS origin server.
 Manifest URI: The URI path and filename of the requested content, or
published content. This field and value can be aliased into any other
name of interest. Performing a “mouse-over” on an aliased entry will
display the full URI path.
 Chunks: The number of media segments or fragments requested or
published, for a given session.
 Avg Bitrate(kb/sec): An estimated average media bitrate of the session
being analyzed. This is not the HTTP transfer rate, but an approximation
of the actual media bitrate of the particular asset.

 4xx errors: The number of HTTP errors in the 400 range for any given
session.
 5xx errors: The number of HTTP errors in the 500 range for any given
session
– When an entry is right-clicked, several options are provided:
 Filter: manually create a filter based on data from this session. See
Figure 8-24: Filter Selections
 Manifest Information: Displays the number of times, names and content

of the manifest files requested by a client, or published by an ABR
encoder. See Figure 8-25 for an example.

Figure 8-25: Manifest Details
 Create Manifest Alias: Allows the user to create an alias for the
URI/Manifest being requested or published. Once created the entry is
published and saved in the “Asset Alias” tab. See Figure 8-26 for an
example. When the user wants to alias multiple manifests to a single or
common alias name the usage of the character “%” is accepted as a
wildcard.
Figure 8-26: Add Alias
 MasterID: This value and option is used when requested by the

IneoQuest support team for troubleshooting purposes only.
 Create Alarms: When a “Publishing” flow is selected the user can select
to create different publishing alarms for the selected flow. See
Figure 8-27 for an example. The possible alarms are:

 “Publishing Duplicate Manifest” – An alarm is generated when

multiple encoders are publishing the same asset to the same origin
server.
 “Publishing Flow Outage” – An alarm is generated when the selected
flow has no activity for an extended period of time, configurable in
the Configuration tab alarm section.
 “HLS Publishing No Key” – An HLS specific alarm is generated
when a manifest file that should contain a “key” entry does not.
Figure 8-27: Census Create Alarms
 RTMP Info: Provides information on RTMP flows currently in progress,

as seen in Figure 8-28.

Figure 8-28: Census RTMP Info
 Create RTMP Alias: Allows the creation of an RTMP alias for a given
RTMP publishing flow, as seen in Figure 8-29. Only the source IP
address and the destination port are required.
Figure 8-29: Census RTMP Alias
 RTP Info: Provides information on RTP flows currently in progress.

 Create RTP Alias: Allows the creation of an RTP alias for a given RTP
publishing flow, as seen in Figure 8-30. Only the source IP address and
the destination port are required.

Figure 8-30: Census RTP Alias
• Bottom Census pane

– When an entry in the top census pane is clicked and highlighted, more details
about the given session are provided in the bottom pane. Figure 8-31 provides an
example.
Figure 8-31: Bottom Census
These details can include:

 IQ Part #: This column will display the logical chunk number seen by
IQDialogue ASM for this given session. The value is in two parts, the
first number being the chunk, the second number being the logical TCP
session number observed by IQDialogue ASM for this chunk in this
session.
 Chunk Transfer Start/Stop Time: The time stamp at which the request
for the chunk was made, and the end time at which it was fully received.
 Chunk Transfer Time (ms): The amount of time taken to transfer the file,
chunk or fragment from the source to the destination.

 Status: Shown in the “status” column is the VeriStream metrics for

requested chunk (for publishing sessions and non-HTTP based sessions
the status is always “Balanced”). Please contact IneoQuest at
techsupport@ineoquest.com for more information on the VeriStream
metric.
 Format: The type of chunk, or byte-range in the case of OTT content.
Not all stream formats can be decoded to show this value.
 Size (bytes): The size in bytes of the chunk, file or fragment being
requested or published
 FBRSYS: VeriStream value for the requested chunk. Please contact
IneoQuest at techsupport@ineoquest.com for more information on the
VeriStream metric. Not all stream protocols can provide a VeriStream
value.
 FBRFT: VeriStream value for the requested chunk. Please contact
IneoQuest at techsupport@ineoquest.com for more information on the
VeriStream metric. Not all stream protocols can provide a VeriStream
value.
 HTTP Status: The HTTP Status code for the transaction of the chunk,
file or fragment
 Transfer (kb/sec): When possible (based on the stream type) the media
bitrate value of the content.
 File Name: The file name of the chunk, fragment or file being requested,
byte-range requested or the fragments requested, based on format type.
 Token: In cases where IQDialogue ASM can detect and extract a unique
token or cookie from the session, it will be displayed in this column. The
token can exist in the HTTP request URI from the client, or preferably as
a cookie value from the requesting client.
– When an entry is right-clicked, two copy (copy to clipboard) options are
provided:
 Copy
 Token: Copy the token value to clipboard. This can be used for
pasting into the token field for an Active Client Report by Token. See
Section 9.4.1 Active Client Report by Token.
 Filename: Copy the filename to clipboard. This can be used to search
data that is exported from IQDialogue ASM after running a query
from the ASM Query tab. See Section 8.5 Query.
 Lookup Status Code: Provides the lookup of the HTTP status code
See Figure 8-32 for an example.

Figure 8-32: Copy Options
• Top/Bottom Census pane column filter and sizing options

– At the far right of both the Top and Bottom census panes, a small icon is
provided to select which columns to display, and to “pack” the columns for
better sizing and visibility based on the resolution of the end-user’s computer.
See Figure 8-33. The “Status Code Definitions” provides a listing of
well-defined HTTP status codes.
Figure 8-33: Select and Pack Columns

8.3.2 Active Clients

The Active Clients sub-tab screen provides the following information:
• Flow
• Start
• End
• Token
• URL
• Up Time
• Manifest Errors
• Chunk Errors
• DNS Lookup Time (ns)
Figure 8-34 provides an example of the Active Clients sub-tab page.
Figure 8-34: Active Clients Sub-tab Page
8.4 Active Client
IQDialogue ASM can be configured to perform http requests (as a client) for Apple HLS
and Microsoft Smooth Streaming content. See Figure 8-35 for an example of the Active
Client tab.

Figure 8-35: Active Client Tab
Active Client Error Retry

When configuring Active Client operation for testing ABR assets, it is best practice to
continue retrying if the IQDialogue ASM test function encounters streaming errors. The
retry mechanism is configured using active.client.error.rtry on the Configuration tab, within
Active Client settings. Changes in IQDialogue ASM v4.00.00 software enables the retry
parameter by default.
Encoder Reset Alarm

When a video encoder resets it causes a break in the publishing process, resulting in
manifest files that may have fewer than typical video chunks available for download and
potential playback issues. If chunks are not available before the playback buffer is empty
client devices will certainly experience video stalls and buffering.
Using the Active Client functions of IQDialogue ASM, encoder resets conditions can be
identified through the new Encoder Reset Alarm so operators can isolate faulty encoders
and take corrective actions, eliminating user impact. To enable this new alarm, set the
alarm.ac.encoder.reset.error value on the Configuration tab Active Client.

8.4.1 Request Configuration

In the “Request Configuration” sub-tab you can configure the necessary parameters as well
as view the status of active client flows. There are two classes of active client requests, one
for VOD style assets (the top window) and another for “live” or “Broadcast” style assets
(bottom window).
Active Client “Request Configuration” columns are described as follows:
• Active: Indicator that tells the state of the flow.
– Blank: Not Running.
– Green: Running.
– Red: Shutting down.
– Orange: Request is in pause mode.
• URL: The URL to connect to so that content can be requested.
• Content Type: The type of content the flow represents.
– HLS: Apple HLS type flow.
– Smoothstreaming: Microsoft Smooth Streaming type flow.
– HDS: Adobe HDS type flow.
• Repeat Count/Duration/Delay:
– Repeat Count: The number of times to loop the requests of the flow. A value of 0
means loop indefinitely.
– Duration: The amount of time in seconds to join a flow.
– Delay: The amount of time in seconds to delay between manifest requests.
Table 8-3 describes Repeat Count, Duration, and Delay results.
Table 8-3. Repeat Count/Duration/Delay
Repeat
Duration Delay Result
Count
0 0 0 Continue indefinitely.
X 0 0 Continue for X loops.
0 X 0 Continue for X seconds.
X X 0 Continue for X loops joining for X seconds.
Continue indefinitely with a delay of X seconds

0 0 X
between manifest requests.

Table 8-3. Repeat Count/Duration/Delay (Continued)
Repeat
Duration Delay Result
Count
Continue X loops with a delay of X seconds between
X 0 X
manifest requests.
Continue indefinitely, join for X seconds and delay X

0 X X
seconds between manifest requests.
Continue X loops, join for X seconds and delay X

X X X
seconds between manifest requests.
• User Agent: The user agent used in the request. There are several predefined selections,
but a user agent can also be created by the user by typing in the drop-down box in the
Add Active Request dialog box (see Figure 8-36).
• Authentication: The authentication scheme to use when making requests. Several
options are available, right clicking on the table entry presents a menu.
– None: No authentication.
– Basic: Basic http authentication. You will be prompted for a user name and
password.
– Wowza: Wowza authentication.
• VU (Video Uplink) Destination: The port to use when the content is sent via Video Up
link.
On the Active Client view, sessions are identified by the condition and color index in
Table 8-4.
Table 8-4. Session Color and Description
Color Description
Active Client flow was auto created – While monitoring publishing

transactions, new Active Client entries can be auto created when the
IQDialogue ASM recognize the presence of a new flow. Configuration
settings (Configuration  Active Client group menu) control the behavior
of entering the new flow in the Active Client list and auto joining.
Remote Video Link (RVL) enabled for the identified flow
Errors occurred during this streaming session

8.4.1.1 Add, Delete, Import, Export, and Video Uplink Options

Several options are available in the “Request Configuration” sub-tab such as:
• : Used to create a new active client request entry.
• : Used to delete an existing active client request entry, by selecting it and

dragging it to the icon.
• : Used to import a list of active client requests previously saved from

IQDialogue ASM, from a “.csv” file format.
• : Used to export the current list of active client request entries configured in the
probe.
• : Used to export Video Uplink. Refer to Section 8.4.1.3 Video Uplink for
Adaptive Bitrate (ABR) Flows.
When adding a new entry, the dialog box appears as shown in Figure 8-36.
Figure 8-36: Active Client Entry
The configuration options are:

• URL: The full URL path for the index or manifest file required by the client. For
example: http://192.168.1.10/hls.m3u8
• Clip / Live Stream: Used to define if the asset is a VOD style asset or a live broadcast

• Duration: Length of time to join the flow. A value of “0” is for a permanent connection
• Repeat Count: With a default of “0” on a “Clip”, the active client will make a single
request for the asset when activated. With a default of “0” on a “Live Stream” the active
client will remain joined to the live broadcast.
• Delay (Seconds): When used in conjunction with the “Repeat Count” parameter, the
active client can be configured to wait a certain amount of time (in seconds) in between
each join requests.
• Stream Content: Used to define either Apple HLS, Adobe HDS, MPEG DASH or
Microsoft Smooth Streaming
• User-Agent: The selection of a pre-configured or user-defined HTTP user-agent to use
for these client requests. To create a user-defined entry simply edit the input box with the
desired value
Once an active client request has been created, other options then become available for
configuration, as shown in Figure 8-37.
Figure 8-37: Available Options
Many of the configuration fields can also be directly edited, as long as the session is not
currently active.
In the first column called “Active” the user is presented with a status indicator for this
particular session:
• When the session is inactive the “Active” column will be empty
• When a session is “Active” a “green” progress indicator will be present (as shown in
Figure 8-37)
• When a session is in the process of terminating a “red” progress indicator will be present
• When a session is waiting (for example when configured to join/wait/rejoin) the
progress indicator will be shown as “orange”
8.4.1.2 Authentication
The “Authentication” field can be used to select the specific authentication method, as
shown in Figure 8-38. Simply right click the “Authentication” box to get access to the
methods available. Once selected, a pop-up dialog box will be provided to enter the
username and password required.

Figure 8-38: Authentication Selection
8.4.1.3 Video Uplink for Adaptive Bitrate (ABR) Flows

This IQDialogue ASM release supports Remote Video Uplink (RVL) functionality to
forward up to 10 simultaneous HTTP Live Streaming (HLS) ABR based flows to an
IneoQuest Expedus DVA IP for further analysis. This functionality enables operators to
assess quality of experience (QoE) aspects of a video stream after the media files traverse
the content delivery network.
To utilize the Video Uplink function, the media files must be unencrypted video. A constant
flow of unencrypted video could be used with the IQDialogue ASM Video Uplink feature in
conjunction with Expedus DVA IP to constantly measure the impact of the content delivery
network on QoE aspects.
NOTE: To configure Video Uplink on a Active Client, the streaming session must be
stopped.
Follow these steps to configure Video Uplink.
Step 1 From the Active Client screen, select “Configure Video Uplink”. See Figure 8-39.
Figure 8-39: Select “Configure Video Uplink”
Step 2 In the dialog box that appears, enter the Destination IP address (the IP of the device that
will receive the content) and the Default Port (Select an available port). Click OK. See

Figure 8-40: Video Uplink Configuration Dialog Box
Step 3 Select an HLS asset to enable. Right-click your mouse on the asset to bring up the
context menu and select Enable in the “Video Uplink” submenu. See Figure 8-41 for an
example.
Figure 8-41: Select “Enable”
The asset will become color coded green to quickly identify which assets are configured.
See Figure 8-42 for an example.
Figure 8-42: Video Uplink Enabled Asset
For additional information regarding Video Uplink client setup, refer to Appendix A, Video
Uplink Client Setup.

8.4.1.4 Grouping
The “Group” field can be used to logically group multiple active client entries so that they
can be managed from a single logical entity. From the selection (as shown in Figure 8-43),
you can create a new group, add to an existing group or remove from an assigned group.
Figure 8-43: Active Client Grouping Selection
8.4.1.5 Active Client Session Logging

Quickly access a detailed transaction log for each Active Client session by selecting the
session and then use the right-click context menu. Selecting “View Logs” returns a window
detailing all logging for the specific Active Client with easy-to-use filters to select the
category of viewed information. See Figure 8-44 for an example.
NOTE: Active Client sessions must be setup for logging (Configuration  Active Client
 active.client.logging) before information will be available.

Figure 8-44: Select View Logs
8.4.1.6 Active Client Recent Alarms

View Active Client alarms using the right-click context menu available for every Active
Client session. Selecting “View Alarms” returns a window detailing all recent alarms for
quick retrieval of per-stream errors without having to run manual queries. See Figure 8-45
for an example.

Figure 8-45: Select View Alarms
8.4.1.7 Traceroute
Find the route from the IQDialogue ASM server to the destination URL by performing a
traceroute directly from the Active Client session right-click context menu (see
Figure 8-46). You can also view the history of previous traceroutes. Identifying the hops
from the IQDialogue ASM to the media file locations could be the next step in diagnosing
issues.
Figure 8-46: Select Traceroute

8.4.1.8 Configure Options

Select “Configure Options” in the right-click context menu. See Figure 8-47. Currently,
options are only available for HDS flows.
Figure 8-47: Select Configure Options
8.4.1.9 Grouping Management Features

In the top right section of the active client tab you are presented with more “Grouping”
management features (as shown in Figure 8-48).
Figure 8-48: Active Client Grouping
When selecting the “Manage Groups” option a pop-up will appear where you can create,
remove or update logical groups (as shown in Figure 8-49).

Figure 8-49: Manage Active Client Grouping
Once created you can click on the “Manage Group Mappings” to assign specific active
client sessions to your logical groups (as shown in Figure 8-50).
Figure 8-50: Manage Active Client Group Mappings

You select a “Client Group” on the left from the pull-down menu, and then you select an
entry from the “Available Client URIs” window on the right, and by using the arrow buttons
you can assign or remove the mappings from the “Client Group” of interest.
The “Configure Auto Join” feature enabled IQDialogue ASM to automatically create Active
Client entries for Publishing flows that are detected, and then automatically start joining
them. When the user clicks on the option a pop-up dialog box appears (as seen in
Figure 8-51).
Figure 8-51: Configure Auto Join
8.4.1.9.1 Active Client Group Association on Import

Active Client Groups allow multiple Active Clients to be managed simultaneously for
ease-of-use when many client monitoring sessions are configured. The import/export
functionality of the Active Client configuration is extended to include group associations to
make the configuration even easier.
8.4.2 Active Requests (AR) Logs

The “AR Logs” sub-tab provides you with the ability to select an active flow and view all or
a specific selection of the log report. See Figure 8-52 for an example the AR Logs page.

Figure 8-52: AR Logs Page
At the top of the page, click the drop-down arrow and select an active flow. See Figure 8-53
for an example.
Figure 8-53: Select an Active Flow
By selecting a radio option button you can choose to view all or a specific selection of the
log report. Selections include:
• All
• Info

• Debug
• Warning
• Error
• Severe
Figure 8-54 displays the AR Logs page.
Figure 8-54: Example AR Logs Results
8.4.3 Playlist Management

The growing list of ABR video content for both Live and VoD services is a challenge to
active monitoring because of the equipment cost and load placed on the video distribution
network to keep pace with asset growth. IneoQuest delivers Playlist Management to
continue scaling the ABR testing methodology that uses IneoQuest’s Active Client to
emulate devices for continuous content availability, transport quality and adaptive protocol
verification.
With Playlist Management, Network Operators and Content owners use Active Client in
conjunction with a playlist of video assets to scan either continuously or over a defined time
period. The scanning function iterates through the playlist based on user defined timing
parameters to test a broad set of content without overburdening the distribution network
with unmanageable loads. A report is automatically generated after each iteration for easy
assessment of service performance and historical trending. See Figure 8-55 for an example
of the Playlist Management page.

Figure 8-55: Playlist Management Page
To configure a list of assets to be scanned based on the defined schedule, you will
(1) Define a single or multiple Groups
(2) Assign the Group(s) and/or configured assets to a Scan List
(3) Set the Schedule for the Scan List operation
Group Configuration
A Group identifies a set of configured assets that will all be streamed simultaneously. If the
configured asset is a top-level HLS manifest or an MPEG-DASH MPD, all the bitrate
variants will be streamed. When configuring a group, be sure to consider the maximum
bandwidth of the IQD ASM Active Client interface as well as the streaming target. To
ensure proper Active Client streaming performance, IneoQuest recommends to not exceed
75% of the 1Gbps appliance interface
Follow these steps to configure a new group of ABR assets in the Group Configuration
section.
Step 1 Click “Add” to name your new group.
Step 2 Select the Group name and add streams to the group by selecting one or more assets in
the Available Assets column and moving them to the Configured Assets.

Step 3 If the group is intended to run independently from the Scan List operation, use the
Repeat Count, Duration, Delay parameters to set value specifically for the group.
Note: If the Group is added to a Scan List, the schedule values for the Scan List will
take precedence but will not overwrite this configuration.
Step 4 Continue adding Groups as required.
Scan List Configuration

A Scan List is simply a method to connect multiple groups to be monitored sequentially.
Step 1 Click “Add” to name a new Scan List.
Step 2 Select the Scan List and one or more Groups by selecting the Group name from
Available Groups and moving them to Scan List Assets. Likewise, independent assets
can be added to the Scan List from the Available Assets list. When an individual asset is
added to the list, it will be treated like a group when monitoring begins. That is, it will be
run independent of any previous or following Group or Asset.
Schedule
Once a Scan List is configured, the timing parameters for scanning the contained Groups
and report generation are configured. The following explains each field in the Schedule
section.
• Duration – The length of time in seconds that each Group in the Scan List will be run for
monitoring. For example, if each Group should run for 5 minutes before proceeding to
the next Group of assets, set a value of 300. The Active Client will monitor all streams in
the Group for 300 seconds before moving on to the next group.
• Group Delay – The time in seconds to pause between monitoring a Group and the next
Group immediately following it in the Scan List.
• Iteration Delay – This parameter pertains only applies if the Scan List monitoring will
repeat after the first iteration. When specified, the Active Client will pause for the
configured number of seconds after the final Group before restarting the Scan List.
• Schedule Repeat – Number of times that the Scan List is executed. A value of 0 will run
continuously.
After each iteration through the Scan List, a report can be generated in either CSV, PDF, or
both formats.
Scan List Operation

To initiate a Scan List, select the appropriate name from the menu and select “Start”.

8.5 Query
The Query tab provides the ability to perform searches in the IQDialogue ASM database for
specific sets of information using simple to use pre-defined search criteria. Once a search is
completed the resulting set can be exported to a CSV file using the Microsoft Excel export
button at the bottom of the tab.
• Alarms: Provides the ability to get detailed information about past alarms and traps
based on time (before and/or after), transaction type and alarm types. See Figure 8-56
for an example.
Figure 8-56: Alarms Tab
• RTSP Information: Provides the ability to get detailed information about RTSP requests
based on time (before and/or after), client IP and server IP. See Figure 8-57 for an
example.

Figure 8-57: RTSP Information Tab
• HTTP Information: Provides detailed activity report based on time (before and/or
after), any HTTP sessions or HTTP errors specifically, source IP (IP address of a
specific client), destination IP (IP address of an HTTP or caching server), and for
specific stream types (HLS, Smooth Streaming, wmv/wma, etc.). The HTTP
Information is divided into two sections, the top part is for a listing of the individual
sessions, and the bottom view is for the details of a specific session (chunks, VeriStream
values, etc.). One important note, when using the “After” filter the query will only return
results of HTTP sessions that got initiated after the selected time, and will not display
sessions that had already been established at that time. See Figure 8-58 for an example.

Figure 8-58: HTTP Information
• Profile Chunk Count: A special query to get a cumulative count of the number of
chunks requested in a period of time against a specific asset in the form of an URI (i.e.
/hls/01.m3u8). See Figure 8-59 for an example.

Figure 8-59: Profile Chunk Count
• RTMP Information: Provides the ability to get detailed information about RTMP
requests based on time (before and/or after), All, Active, or Inactive. See Figure 8-60 for
an example.

Figure 8-60: RTMP Information
8.6 Reporting
The Reporting tab is used to access the manual or automated reporting features provided in
the IQDialogue ASM probe. Please refer to Chapter 9, Reporting Screens for detailed
information on this particular feature.
8.7 Configuration
The Configuration tab is used to configure most operation parameters of the IQDialogue
ASM probe including alarms, probe informational details, KPI customization, etc. The
Configuration tab consists of the following sub-tabs:
• System Configuration
• Publishing Alarm Config
• Alias Configuration
8.7.1 System Configuration

The System Configuration sub-tab is divided into the following functional sections:
• Active Client: Alarm configuration specific to the Active Client functions of IQDialogue
ASM

• Alarm Settings: Alarm configuration for the passive monitoring functions

• FTP Settings: Configuration settings for automatically uploading generated reports via
FTP or SFTP
• Intra-CDN Settings: Configuration settings for Intra-CDN monitoring
• IQD Settings: General configuration parameters of the probe, such as timeout values,
timezone, expected port numbers, etc.
• KPI Settings: Configuration of all available KPIs.
• Log Settings: Logging and debug output levels of the probe. The default values should
not be changed unless you are instructed to do so by IneoQuest support staff.
• Database Settings: This section covers the selection of database table optimization.
• Purge Settings: Automated purge and data retention settings of historical data in the
probe.
• Report Settings: This section covers the configuration of the reporting functionality of
the probe
• SNMP Settings: SNMP trap configuration of the probe. This feature is only available if
the probe is licensed for SNMP.
• Video Uplink Settings: Video Uplink port and destination configuration settings.
• General Settings: This section covers the basic configuration parameters of the probe,
such as location and contact information.
See Figure 8-61 for an example of the System Configuration sub-tab.

Figure 8-61: System Configuration Tab
8.7.1.1 IQD Packet Filter

IQDialogue ASM allows users to filter Data Plane Development Kit and Packet Capture
traffic, allowing only certain elements of network traffic to be processed. This
highly-configurable setting allows users to conduct extremely specific analysis. This
functionality is controlled by editing the iqd.packet.filter field under IQD Settings, seen in
Figure 8-62. Observe that the field accepts strings, and will serve as a Wireshark capture
filter. For this reason, this functionality should be used with caution, as any string entered
here will apply a filter to all traffic. Consequently, the system may appear non-functional if
an invalid or irrelevant string is entered. To minimize the risk of impairments, packet
filtering is off by default.
While extremely robust, it should be used only in one of two scenarios:
• There is considerable irrelevant traffic on the wire.
• There is too much traffic for IQDialogue to handle
You should also note that there is no indication on the configuration tab that the filter has
been enabled. To minimize errors, however, if the filter fails to compile, it will be noted in
the log, and no filter will be applied.
Finally, keep in mind that VLAN tagging of traffic is common (particularly in DPDK
installations). If this is the case, the VLAN qualifier must be added to the filter: e.g. “vlan
and host 123.123.123.123.”

For more details about Wireshark capture filtering, please consult the online user’s guide
available at https://www.wireshark.org/docs/wsug_html_chunked/. Best practices may be
found online at https://wiki.wireshark.org/CaptureFilters.
Figure 8-62: The “iqd.packet.filter” Field
8.7.1.2 IQD Settings “http.uri.edit.list” Parameter

This parameter enables a list of edit strings which can be applied to the URI prior to
processing. This parameter uses regex like replacement strings which can be demarcated by
configurable characters. String substitution may be required if the media URL uses unique
values for each segment. This approach would prevent IQDialogue ASM from associating
the session and result in inaccurate representation of monitored sessions.
Example
Some environments use URIs with embedded session, client, or time specific information
like the URI in the following HTTP GET:
‘GET /x/y/T=20170410161723/z.m3u8’
Left alone, this results in an infinite number of unique Manifest URIs which will impact a
probe’s performance. Using the methods described in this example, you can remove
unnecessary information using:
http.uri.edit.list= s|T=[0-9]*/||

Which changes the example URI into:

/x/y/z.m3u8
This preserves the uniqueness of the URI for associating sessions but eliminates the
problematic section.
• s/a*s/asdasd/; will search and replace any instances of any number of characters
starting with a and ending with s and replace them with “asdasd”. You can specify the
string delimiter by using the first character after the “s” command. This is useful when
the string to be replaced may contain the forward slash character. This also avoids the
need to escape most characters.
• s|x??|y|; will search for any three character string starting with “x” and replace
all of them with “y”. Note the use of the pipe character instead of the forward slash. The
system will recognize the string format and use the pipes instead of forward slashes
automatically.
Multiple strings can be specified using the semicolon ';' to demarcate the end of a string.
Strings are applied in sequential order.
Example
String = s/*{Monday}*/Tuesday/; s/$Tuesday#/Wednesday/;

Behavior = In a string with a substring matching “Monday”, the Monday part would be
replaced with “Tuesday”. And if that string then matched “$Tuesday#” in its entirety,
that string would be replaced with “Wednesday”. So “#Monday#” would become
#Tuesday#, but “$Monday#” would become “Wednesday”.
• s/_q*.mpd/{b64decode}/ will perform a base 64 decode function on any string which

matches the given source string.
• Multiple strings can be entered, each demarcated with the semicolon character.
• Replacement strings are applied in sequential order (first string, second string, etc.) for
recursive purposes.
In addition to regex replacement syntax, there are some special functions which are denoted
by the use of curly braces '{}' . Curly braces are also used to denote substrings which are to
be acted upon using selected special replacement functions.
The following are http.uri.edit.list replacement functions:
• {b64decode} – performs decode on specified string.
Example
String = s/,VXToken={*}/${b64decode}$/;

Behavior = Any substring which contains “,VXToken=” plus any text will be base 64
decoded and then replaced with the result of that decode prepended and postpended by
dollar symbols.
• {info} – places resultant string into httpvod.referer column in iqdialoguecdn database.
Example
String = s/#{*satelite*},/#{info},/;
Behavior = will take any substring preceded by “#” and followed by “,” which contains
the word “satellite” and place it in the referer column of the httpvod table for that
stream.
• {cookie} – places matched string into httpvod.token column in iqdialoguecdn database
Example
String = s/cookie=*,{*}#/{cookie}#/; will place all of the text selected by {*} which is
preceeded by “cookie=*,” and followed by # into the token column of the httpvod table
for that stream, followed by the pound symbol.
NOTE: Using the capital “S” replacement command instead of the lower case “s” causes
the probe to log the before and after log entries into the /var/log/iqdialog file.
See Figure 8-63 for an example of the “http.uri.edit.list” parameter.

Figure 8-63: The “http.uri.edit.list” Field
8.7.1.3 IQD Settings “http.only.save.masters” Parameter

When monitoring large numbers of live streaming traffic with many component streams (>=
2Gbps), processing and saving component manifest files becomes very resource intensive
and limits the number of streams that can effectively be monitored. Enabling
http.only.save.masters allows the probe to discard component stream manifests while saving
all manifests for the master streams. This allows for a much higher load (up to 10Gbps).
8.7.1.4 IQD Settings “census.intracdn.query.max.records” Parameter

When monitoring large quantities of intra-CDN data streams (> 2Gbps or 10s of thousands
of streams),updating the realtime census page can quickly become a load on the system and
cause the Java user interface to respond poorly. By limiting the number of streams displayed
on the Realtime Census page, it allows the page to be useful and not cause undo load on the
user interface. Typically setting this value below 100 is most effective and allows the user to
also use the Realtime Census filters to visually monitor some traffic to ensure the system is
operating as expected.
To display larger numbers of streams in such an environment, it is recommended to use the
query interface page instead of the Realtime Census page. The transient nature of the data
lends itself to analysis through structured queries versus realtime monitoring.

8.7.2 Publishing Alarm Config

The Publishing Alarm Config sub-tab consists of the following sub-tabs:
• Alarms
• Tuples
8.7.2.1 Alarms
The Alarms sub-tab is used to display and configure stateful HTTP based publishing alarms.
The “Alarms” section allows for the configuration of the specific alarms, as well as
application to specific tuples and the historical viewing of past alarms. Figure 8-64 provides
an example.
Figure 8-64: Example Alarms Tab
Stateful publishing alarms can be globally enabled or disabled using the “Enable this alarm”
option in the bottom section, while at the same time assigning a specific severity level to the
alarm and trap.
These alarms can also be targeted at all publishing flows, or specific ones, using the “Alarm
Tuples” definition. In this section you can define specific parameters such as source IP:Port,
Destination IP:Port and URI. There is also a global “Match All” value that will apply the
alarm to all publishing flows indiscriminately.

8.7.2.2 Tuples
In the “Tuples” sub-tab you are presented with any pre-configured or manually configured
tuples. An example is provided in Figure 8-65.
Figure 8-65: Tuple Information
8.7.2.2.1 MPEG-TS Conformance Alarming

During the asset publishing process, the IQDialogue ASM is capable of monitoring HTTP
PUT and WebDAV transmission to the origin server. MPEG-TS conformance alarming
extends the functionality of monitoring to identify the presence and absence of the critical
MPEG video components PAT, PMT, audio PID and video PID. To utilize MPEG-TS
Conformance Alarms, the media asset must be unencrypted and HLS formatted.
Enabling a constant test stream through the encoder, segmenter and publisher allows
continuous validation that MPEG transport packet headers required for media playback
remain intact during the publishing lifecycle.
To activate MPEG-TS Conformance Alarming, select
“alarm.publishing.mp2ts.nonconformance” in the Alarm Settings underneath the System
Configuration tab. Refer to Section 8.7 Configuration.
8.7.3 Alias Configuration

The Alias Configuration sub-tab is divided into the following functional sections:

• Asset Alias
• NIC Alias
• Origin Server Alias
• RTMP Alias
8.7.3.1 Asset Alias

IQDialogue ASM can be configured to display more familiar names when specific
URL/URI are analyzed and displayed in the “KPI” or “Realtime Census” tabs, or when
traffic needs to be reported on a per monitoring interface. Multiple sub-tabs are provided,
each one specific to a certain protocol set. See Figure 8-66 for an example
Figure 8-66: Alias Configuration Asset Alias Sub-tab
Under the Asset Alias sub-tab the format for input in the dialog box is very simple. See
Figure 8-67.

Figure 8-67: Add Alias Dialog Box
Once created the entry is published and saved in the “Asset Alias” tab. When you want to
alias multiple manifests to a single or common alias name the usage of the character “%” is
accepted as a wildcard. The “Top Level Manifest” check box option is used to identify this
URI as a top-level manifest for an HLS flow. Failure to properly configure this option may
lead to false publishing outage alarms, as the top-level manifest will commonly not be
re-published unless it requires a change.
8.7.3.2 NIC Alias

In the NIC Alias section, IQDialogue will pre-populate all known and active interfaces.
Aliases can be defined to each interface as well as the ability to remove an alias, import or
export aliases. See Figure 8-68 for an example of the NIC Alias section.
Figure 8-68: Example NIC Alias Page

8.7.3.3 Origin Server Alias

The “Origin Server Alias” sub-tab is used to create aliases for Origin Server. See
Figure 8-69 for an example of the Origin Server Alias page with the Add Origin Server
Alias dialog box.
Figure 8-69: Origin Server Alias Page with Add

Origin Server Alias Dialog Box
8.7.3.4 Publishing Flows

In support of a defined asset lineup, IQDialogue ASM enhances the configuration of
monitored publishing content. You may choose to pre-define a list of assets for monitoring,
automatically learn publishing flows, or run in both modes. The Publishing Flows sub-tab is
used to add URIs, Source IPs, and Destination IPs for various publishing flows, as seen in
Figure 8-70.

Figure 8-70: Add Publishing Flow Dialog Box
IQDialogue ASM has the ability to monitor this pre-populated list of flows as well as any
flows it automatically discovers from monitoring the wire. To disable the option to
automatically discover flows (and thus use only the pre-populated list from the Publishing
Flows tab), you simply toggle the http.publishing.discover setting, as displayed in
Figure 8-71.

Figure 8-71: Toggle the “http.publishing.discover

setting”
8.7.3.5 RTMP Alias

The “RTP/RTMP” sub-tab is used to create aliases for RTP or RTMP publishing flows
(common for Adobe type content). You can enter the source URL for unique naming in the
“Add RTMP Alias” dialog box. See Figure 8-72 for an example.

Figure 8-72: RTMP Alias Page with Add RTMP Alias

Dialog Box
When configuring an RTP or RTMP Alias, you need to provide the source IP (commonly
the IP address of the encoder), the destination TCP port and an alias name.
8.8 About
The About tab is used to display operational parameters of the probe, such as version
number of the probe and client, time length of NBS login, and overview of SNMP alarm
types generated and muted. See Figure 8-73 for an example.

Figure 8-73: About Tab

Reporting Screens
9 Reporting Screens
This chapter provides information regarding the following:

• Section 9.1 Reporting Tab
• Section 9.2 Automating a Report
• Section 9.3 Report Configuration
• Section 9.4 The Reports
Figure 9-1 identifies the Reporting tab and the reporting sub-tabs that are available on that
screen.
Figure 9-1: Reporting Screens

Reporting Screens
9.1 Reporting Tab
The Reporting tab is where you go to run a report manually and to set up the initial
Automated report functionally, The following reports are available:
• Section 9.4.1 Active Client Report by Token
• Section 9.4.2 Active Client Report by URI
• Section 9.4.3 Client Sessions Report
• Section 9.4.4 User-Agent Report
• Section 9.4.5 Bandwidth Usage
• Section 9.4.6 HTTP Errors by Server
• Section 9.4.7 Alarms & Errors
• Section 9.4.8 HLS Manifest Detail
• Section 9.4.9 Publishing Outage Report
• Section 9.4.10 Client IP/UA Pairings Report
9.1.1 Automated Report Definitions Tab

The Automated Report Definitions tab allows you to manage automated reports. From
here you can add, delete, and modify the reports. You are also able to turn the generation of
the report on or off by selecting the Active check box. See Figure 9-2 for the location of the
Automated Report Definitions tab.

Reporting Screens
Figure 9-2: Automated Report Definitions Tab
The following icons are available at the bottom of the page:
• : Delete an existing report by selecting it and dragging it to the icon.
• : Import a defined report previously saved from IQDialogue ASM, from a

“.csv” file format.
• : Export the selected report to a “.csv” file format.
9.1.2 Generated Reports Tab

The Generated Reports tab allows viewing of automatically generated reports on the
probe. Reports are only available if a connection to the probe is established. See Figure 9-3
for an example of the Generated Reports tab.

Reporting Screens
Figure 9-3: Generated Reports Tab
9.2 Automating a Report
Every report can be automated. After selecting a report from the available list, a report
dialog input box is presented. This dialog box has a check box on it entitled “Automate this
Report” (see Figure 9-4).

Reporting Screens
Figure 9-4: Report Time Range Dialog Box
If “Automate this Report” is selected, a secondary dialog box will be presented with the
parameters needed for automating the report (see Figure 9-5).
The parameters include:
(1) Name – The name to be given to the report
(2) Frequency – Chose either weekly or daily report generation frequency.
(3) Day of Week – Disabled by default for daily reports. If you are selecting a weekly
report from the frequency drop down, this will become enabled. Select the day of the
week for the report to be generated.
Figure 9-5: Report Frequency Dialog Box

Reporting Screens
9.3 Report Configuration
Figure 9-6 shows the available configuration parameters for automated reporting. These
settings are located under the Configuration tab (Section 8.7 Configuration).
Figure 9-6: Configuration Parameters
• report.swap.filesize – default 5
• reports.daily.period – default 24 – number of hours to report on when a daily report is
selected for automation.
• reports.daily.purge – default 02:00 – time of day the purging of the reports that have
been automated from the probe.
• reports.daily.start – default 06:00 – time of day that the automated report generation task
will occur.
• reports.date.format – default MM/dd/yyyy kk:mm – Month in year/Day in month/Year/
Hour in day (1-24):Minute in hour
• reports.nbs.display.max.size – default 1024
• report.purge.age – default 30 – number of days to keep automatically generated reports.
• reports.starttime.offset – default 6 – amount of time you want the report start time to be
offset by in relation to the time the reports are generated. For example, if you want the
reports to be generated at 6:00 AM and run from midnight, then the period would be 24
hours. The start time would be 6:00 AM and the offset would be 6 hours which is the
difference from midnight to the start time.
• reports.virtualizer.method – default swap
• reports.weekly.period – default 168 – number of hours that are reported on for weekly
reports.

Reporting Screens
9.4 The Reports
This section provides examples of the following reports:

• Active Client Report by Token
• Active Client Report by URI
• Client Sessions Report
• User-Agent Report
• Bandwidth Usage
• HTTP Errors by Server
• Alarms & Errors
• HLS Manifest Detail
• Publishing Outage Report
• Client IP/UA Pairings Report
9.4.1 Active Client Report by Token

The Active Client Report by Token provides performance and error rates over a 24-hour
period. This report summarizes bitrate and VeriStream performance as well as HTTP and
manifest errors.
NOTE: This report can take several minutes to create depending on how many active
clients you have running.
9.4.1.1 Report Input

Basic date range input is required in the Report Time Range dialog box along with Token
information (see Figure 9-7).

Reporting Screens
9.4.1.1.1 Sample Report

Figure 9-8 shows an example of an Active Client Report by Token.

Reporting Screens
Figure 9-8: Example Active Client Report by Token
9.4.2 Active Client Report by URI

The Active Client Report by URI provides performance and error rates over a 24-hour
period. This report summarizes bitrate and VeriStream performance as well as HTTP and
manifest errors. A vertical red line represents a manifest error. A red dot on the report
represents a chunk error.
NOTE: This report can take several minutes to create depending on how many active
clients you have running.

Basic date range input is required in the Report Time Range dialog box along with URI
information (see Figure 9-9).

Reporting Screens

Figure 9-10 shows an example of an Active Client Report by URI.

Reporting Screens
Figure 9-10: Example Active Client Report by URI
9.4.3 Client Sessions Report

The Client Sessions Report provides sessions data over the selected time frame. It is
presented in the following three formats:
• Show the number of sessions seen over time.
• Show the top five User-Agents detected based on the number of requests.
• Show the top five manifests requested over time.

Basic date range input is required in the Report Time Range dialog box (see Figure 9-11).

Reporting Screens

Figure 9-12 shows an example of the Client Sessions report.

Reporting Screens
Client Sessions Over Time

Starting: 2015-05-05 14:38
Ending: 2015-05-06 14:38
Probe Location: 170 Forbes Blvd Mansfield MA 02048
Overall Client Sessions
Wednesday 06 May 2015 Page 1 of 3
Figure 9-12: Example Client Sessions Over Time

Report

Reporting Screens
9.4.4 User-Agent Report

The User-Agent Report shows the user agent distribution over the selected time frame.


Figure 9-14 shows an example User-Agent Report.

Reporting Screens
User-Agent Distribution
Starting: 2015-05-04 16:24
Ending: 2015-05-05 16:24
Tuesday 05 May 2015 Page 1 of 2
Figure 9-14: Example User-Agent Report

Reporting Screens
9.4.5 Bandwidth Usage

The Bandwidth Usage Report provides information on the bandwidth usage over time as
seen by IQDialogue.

Basic date range input is required in the Report Time Range dialog box along with the
Network Interface filter. By default, bandwidth will be collected and displayed for all
network interfaces. If the network interface is selected, then only the bandwidth information
for that Network interface will be reported. See Figure 9-15 for an example Report Time
Range dialog box.

Figure 9-16 shows an example Bandwidth Distribution Report.

Reporting Screens
Bandwidth Distribution
Total across all interfaces
Starting: 2015-05-04 16:36
Ending: 2015-05-05 16:36
Overall Bandwidth Usage
Figure 9-16: Example Bandwidth Distribution Report

Reporting Screens
9.4.6 HTTP Errors by Server

The HTTP Error Distribution by Server report provides information on the number of http
errors seen over time. This is reported in five minute intervals and is grouped by the server
on which they were seen. The report also provides a distribution view of the errors grouped
by the HTTP servers.

Basic date input is required in the Report Time Range dialog box along with HTTP error
filter information. By default, all reports are selected in the HTTP Error Code filter. It is also
possible to report on specific HTTP errors codes. See Figure 9-17 for an example Report
Time Range dialog box.

Figure 9-18 shows an example HTTP Error Distribution by Server report.

Reporting Screens
+773(UURU'LVWULEXWLRQE\6HUYHU
6WDUWLQJ
(QGLQJ
3UREH/RFDWLRQ)RUEHV%OYG0DQVILHOG0$
$OO(UURU&RGHVIRU
:HGQHVGD\0D\ 3DJHRI
Figure 9-18: Example HTTP Errors by Server Report

Reporting Screens
9.4.7 Alarms & Errors

The Alarms & Error Distribution report provides information on the number of alarms seen
over time for the selected time frame. The report also shows a distribution of the detected
HTTP Error codes.


Figure 9-20 shows an example Alarms & Error Distribution report.

Reporting Screens
Starting: 2015-05-04 16:24
Ending: 2015-05-05 16:24
Figure 9-20: Example Alarms & Error Distribution

Report

Reporting Screens
9.4.8 HLS Manifest Detail

The HLS Manifest Detail report provides a list of every GET/PUT manifest request for an
HLS flow during the requested time frame. It provides time of request, Source (Origin,
Cache IP) Destination (Active Client, Origin, etc.) and URL/Flow.
NOTE: This report can take several minutes (5 – 30) to generate on large systems.
Automation of this report is recommended.

Basic date range input is required in the Report Time Range dialog box along with URI,
Source, Destination, and Pre/Post Origin information (see Figure 9-21).
When you click OK, a dialog box will appear asking if you want to view the report in
exportable CSV format. If you reply “Yes”, another dialog box will ask if you want to
include column headers. Save this type of report as a CSV file. If you reply “No” to the
question regarding exporting to CSV format, the report will be formatted as it will appear in
PDF format.

Reporting Screens

Figure 9-22 shows an example HLS Manifest Detail in CSV format with column headers.
Figure 9-22: Example HLS Manifest Detail Report in

CSV Format
Figure 9-23 shows an example HLS Manifest Detail report in PDF format.

Reporting Screens
Manifest Details - Publishing & Requests

Starting: 2015-06-16 09:29
Ending: 2015-06-16 11:29
Probe Location: 115 Prince William Street #300 Saint John NB E2L 2B4
Time Source Destination URL

2015-06-16 09:29:00 192.168.150.212 192.168.150.210 /hls/03.m3u8
2015-06-16 09:29:09 192.168.150.212 192.168.150.210 BBC1-256K
2015-06-16 09:29:09 192.168.150.212 192.168.150.210 BBC1-512K
2015-06-16 09:29:10 192.168.150.212 192.168.150.210 /hls/03.m3u8
2015-06-16 09:29:20 192.168.150.212 192.168.150.210 BBC1-512K
2015-06-16 09:29:21 192.168.150.212 192.168.150.210 /hls/03.m3u8
2015-06-16 09:29:21 192.168.150.212 192.168.150.210 BBC1-256K
2015-06-16 09:29:29 192.168.150.212 192.168.150.210 BBC1-256K
2015-06-16 09:29:29 192.168.150.212 192.168.150.210 /hls/03.m3u8
2015-06-16 09:29:30 192.168.150.212 192.168.150.210 BBC1-512K
2015-06-16 09:29:39 192.168.150.212 192.168.150.210 BBC1-256K
2015-06-16 09:29:39 192.168.150.212 192.168.150.210 BBC1-512K
2015-06-16 09:29:39 192.168.150.212 192.168.150.210 /hls/03.m3u8
2015-06-16 09:29:49 192.168.150.212 192.168.150.210 BBC1-256K
2015-06-16 09:29:49 192.168.150.212 192.168.150.210 BBC1-512K
2015-06-16 09:29:49 192.168.150.212 192.168.150.210 /hls/03.m3u8
2015-06-16 09:30:00 192.168.150.212 192.168.150.210 BBC1-256K
2015-06-16 09:30:01 192.168.150.212 192.168.150.210 BBC1-512K
2015-06-16 09:30:01 192.168.150.212 192.168.150.210 /hls/03.m3u8
2015-06-16 09:30:09 192.168.150.212 192.168.150.210 BBC1-512K
2015-06-16 09:30:09 192.168.150.212 192.168.150.210 BBC1-256K
2015-06-16 09:30:09 192.168.150.212 192.168.150.210 /hls/03.m3u8
2015-06-16 09:30:19 192.168.150.212 192.168.150.210 BBC1-512K
2015-06-16 09:30:20 192.168.150.212 192.168.150.210 BBC1-256K
2015-06-16 09:30:20 192.168.150.212 192.168.150.210 /hls/03.m3u8
2015-06-16 09:30:30 192.168.150.212 192.168.150.210 BBC1-512K
2015-06-16 09:30:30 192.168.150.212 192.168.150.210 BBC1-256K
2015-06-16 09:30:30 192.168.150.212 192.168.150.210 /hls/03.m3u8
2015-06-16 09:30:40 192.168.150.212 192.168.150.210 BBC1-512K
2015-06-16 09:30:40 192.168.150.212 192.168.150.210 BBC1-256K
2015-06-16 09:30:40 192.168.150.212 192.168.150.210 /hls/03.m3u8
2015-06-16 09:30:50 192.168.150.212 192.168.150.210 BBC1-256K
2015-06-16 09:30:50 192.168.150.212 192.168.150.210 BBC1-512K
2015-06-16 09:30:51 192.168.150.212 192.168.150.210 /hls/03.m3u8
2015-06-16 09:31:00 192.168.150.212 192.168.150.210 BBC1-256K
2015-06-16 09:31:00 192.168.150.212 192.168.150.210 BBC1-512K
2015-06-16 09:31:01 192.168.150.212 192.168.150.210 /hls/03.m3u8
2015-06-16 09:31:09 192.168.150.212 192.168.150.210 BBC1-256K
2015-06-16 09:31:10 192.168.150.212 192.168.150.210 BBC1-512K
2015-06-16 09:31:10 192.168.150.212 192.168.150.210 /hls/03.m3u8
2015-06-16 09:31:20 192.168.150.212 192.168.150.210 BBC1-256K
2015-06-16 09:31:20 192.168.150.212 192.168.150.210 BBC1-512K
2015-06-16 09:31:20 192.168.150.212 192.168.150.210 /hls/03.m3u8
2015-06-16 09:31:29 192.168.150.212 192.168.150.210 BBC1-256K
2015-06-16 09:31:30 192.168.150.212 192.168.150.210 BBC1-512K
2015-06-16 09:31:30 192.168.150.212 192.168.150.210 /hls/03.m3u8
2015-06-16 09:31:39 192.168.150.212 192.168.150.210 BBC1-256K
2015-06-16 09:31:40 192.168.150.212 192.168.150.210 BBC1-512K
2015-06-16 09:31:40 192.168.150.212 192.168.150.210 /hls/03.m3u8
2015-06-16 09:31:49 192.168.150.212 192.168.150.210 BBC1-512K
2015-06-16 09:31:50 192.168.150.212 192.168.150.210 BBC1-256K
2015-06-16 09:31:50 192.168.150.212 192.168.150.210 /hls/03.m3u8
2015-06-16 09:32:00 192.168.150.212 192.168.150.210 BBC1-256K
2015-06-16 09:32:00 192.168.150.212 192.168.150.210 /hls/03.m3u8
2015-06-16 09:32:01 192.168.150.212 192.168.150.210 BBC1-512K
Tuesday 16 June 2015 Page 1 of 293
Figure 9-23: Example HLS Manifest Detail Report

Reporting Screens
9.4.9 Publishing Outage Report

The Publishing Outage Report provides a list of all publishing outage during the specific
time frame requested by the user. It outlines the start time of an outage, the end time of when
the flow came back into service. As well, it indicates the Source and Destination of the flow.
The URL column represents that of the flow.
Entries that are shown in red with no end time indicate a Publishing Outage that is still
ongoing at the time that the report was created. For data to be available for this report, the
IQDialogue must have publishing alarming enabled.

When you click OK, a dialog box will appear asking if you want to view the report in
exportable CSV format. If you reply “Yes”, another dialog box will ask if you want to
include column headers. Save this type of report as a CSV file. If you reply “No” to the
question regarding exporting to CSV format, the report will be formatted as it will appear in
PDF format.

Figure 9-25 shows an example Publishing Outage Report in CSV format with column
headers.

Reporting Screens
Figure 9-25: Example Publishing Outage Report in

CSV Format
Figure 9-26 shows an example of a Publishing Outage Report in PDF format.
Figure 9-26: Example Publishing Outage Report in

PDF Format
9.4.10 Client IP/UA Pairings Report

The Client IP/UA Pairings Report provides an overview of the user agents coming from
different Source IPs. In the example shown in Figure 9-28, it can be seen that the user agent
of AppleCoreMedia/1.0 originated from two different Source IPs.


Reporting Screens

Figure 9-28 shows an example Client IP/UA Pairings Report.

Reporting Screens
Figure 9-28: Example Client IP/UA Pairings Report

Video Uplink Client Setup
Appendix A Video Uplink Client Setup
This appendix outlines additional details required for IQDialogue Virtual Uplink
configuration to a third party player. The forwarded adaptive video traffic can be delivered
to the end device using any licensed Network Interface Card (NIC) on the IQDialogue as
long as the chosen has an active/routable IP. Contact IneoQuest Support to assist in the
initial setup of the forwarding interface on the IQDialogue ASM server.
A.1 Virtual Uplink Setup
Step 1 Log into the NBS tool and navigate to the Active Client tab.
Step 2 Create a new HLS variant entry or edit an existing URL.
Note: RVL can only use HLS variant streams. Top Level Manifest entries cannot be
used. Only the direct URLs to a variant bitrate can be used.
a. Select the URL to be setup for RVL.
b. Use your mouse to “Right Click” and open the menu.
c. Select Video Uplink then Enable. See Figure A-1 for an example.
Figure A-1: Select “Video Uplink”
d. The VU Properties dialog box will appear. See Figure A-2 for an example.
i. Enter the Destination IP (the IP of the device that will receive the content).
IQDialogue ASM 4.0 User’s Guide — SUG-DIAASM-007 A-1

Video Uplink Client Setup
ii. Enter the Destination Port (Select an available port).
Figure A-2: “Vu Properties” Dialog Box
iii. Click OK.

d. The Active Client can now be enabled by clicking the Start button.
Content is sent out of the IQDialogue NIC to the end device defined by the
destination IP assigned and the port.
A.1.1 End Device Setup (VLC)

This section outlines an example setup using the VLC Media Player as a test application to
receive the UDP traffic from the IQDialogue.
NOTE: The free VLC Media Player software can be downloaded from
http://www.videolan.org/.
Step 1 Open VLC on the device that was defined with the Destination IP in Section A.1 Virtual
Uplink Setup.
Step 2 Under the Media drop-down list select Open Network Stream.
Step 3 Set the URL as udp://@:port (The port is the Destination Port set in Section A.1 Virtual
Uplink Setup).
Step 4 Press Play.
A-2 IQDialogue ASM 4.0 User’s Guide — SUG-DIAASM-007

Active Client and Alarm Configuration Descriptions
Appendix B Active Client and Alarm

Configuration Descriptions
This document describes the IQDialogue ASM Active Client and Alarm Setting
configuration parameters.
The IQDialogue ASM provides a rich set of passive and active monitoring capabilities.
Based on the system configuration, the IQDialogue ASM probe will alarm on various
protocol events and threshold conditions. Alarm configuration descriptions in this document
should be used in conjunction with operational practices for monitoring your specific
network.
Active Client monitoring on the IQDialogue ASM enables users to validate assets
availability and verify the content delivery network by simulating client requests for
configured live or video on demand content. The Active Client configuration determines
how the session will operate and specific error conditions to monitor. Thoughtful
consideration of Active Client configuration will ensure the highest performance of the
IQDialogue ASM’s capabilities and provide the best value for early identification of issues
and troubleshooting.
This information is provided in the following sections:
• Section B.1 IQDialogue ASM Active Client Settings
• Section B.2 IQDialogue ASM Alarm Descriptions and Settings
B.1 IQDialogue ASM Active Client Settings
In the IQDialogue ASM NBS interface, all alarm configurations are found on the
Configuration tab under the Active Client submenu.
B.1.1 active.client.403.session.timeout
When configured, a client that receives a HTTP 403 Forbidden response during a streaming
session will return to the initial URL and re-request the media stream. This functionality
ensures that IQDialogue’s Active Client continues monitoring the configured video assets in
production networks with enhanced security measures.
B.1.2 active.client.allow.circular.redirect
Allows the Active Client to use a redirected URI after receiving a HTTP 307 Temporary
Redirect. The Active Client will repeat the request using the new URI.
IQDialogue ASM 4.0 User’s Guide — SUG-DIAASM-007 B-1

B.1.3 active.client.autojoin.delay
For monitoring publishing flows only - Selecting “Configure Auto Join” on the Active
Client tab will automatically establish a monitoring session of the asset being published.
The autojoin.delay setting specifies the delay period between the time when the publishing
session is recognized until the Active Client session is initiated for monitoring.
Keep in mind that there may be some delay between the manifest file publishing and enough
media files published to properly stream the asset. This configuration option assists with the
timing condition.
B.1.4 active.client.autojoin duration

Duration to play for autojoin new flows – commands to start the newly added flow
B.1.5 active.client.autojoin.new.flows
Enables the Active Client to automatically start a streaming session for newly added flows.
B.1.6 active.client.autojoin.new.flows.autocreate.session
Automatically adds assets recognized during publishing to the Active Client list.
B.1.7 active.client.autojoin.repeatcount
The number of times to repeat the monitoring duration for automatically joined sessions.
B.1.8 active.client.cookie.mode
The cookie mode configuration defines the Active Client operation for HTTP request
messages. Acceptable values are 0 – 2.
• 0 – Disabled – Even if a set-cookie directive is received in the HTTP response, the
Active Client will ignore the cookie
• 1 – Default – On receiving a set-cookie in the HTTP response, the Active Client will
store the cookie for use on all future requests. If a subsequent set-cookie is received the
current cookie is replaced with the new cookie.
• 2 – Append – This setting differs from the default setting if the Active Client receives
additional set-cookie responses. The first set-cookie response is stored and used on all
outgoing requests. If additional set-cookie responses are received the new cookie will be
appended to the old cookie.
B.1.9 active.client.error.chunk.reloadtime
The time to wait in milliseconds before retrying a chunk request (a single time) if there is an
error.
B-2 IQDialogue ASM 4.0 User’s Guide — SUG-DIAASM-007

B.1.10 active.client.error.manifest.reloadtime
The time to wait in milliseconds before attempting to reload the manifest file if an error
occurs on the first attempt.
B.1.11 active.client.error.retry
On receiving any error (manifest, chunk, socket timeout) continue to try and run the Active
Client session.
B.1.12 active.client.hls.download.buffer.size
IQDialogue Active Client buffers the name of each downloaded chunk. Upon receiving a
manifest file, Active Client examines the chunk names to determine if new chunks exist. If
all the chunk URIs are already stored in the buffer, the Active Client will report that there
are no more chunks to download.
The HLS download buffer size configuration provides the control over the number of chunk
URIs to maintain. Essentially, if the chunk name is still buffered, the Active Client will not
operate correctly if the URI is reused. IneoQuest recommends the default value of 15
chunks. Tuning this parameter should be performed only with the assistance of IneoQuest
Support personnel so the Active Client performance can be adjusted and monitored.
B.1.13 active.client.http.connection.timeout
Time to wait before it cleans up a failed start attempt from the ASM census
B.1.14 active.client.http.socket.timeout
Set the parameter in the Active Client for the server connection timeout. This denotes the
time elapsed before the connection established or the server responded to the connection
request.
B.1.15 active.client.logging
Enables logging of Active Client sessions in the AR log. This setting can be used to
troubleshoot Active Client setup but should not be configured permanently because of the
disk space and processing requirements.
B.1.16 active.client.retrieve.encryption.keys
Defines whether or not HLS active clients should retrieve the encryption keys from the
manifest file for the manifest file content (chunks).
If this setting is turned on, the Active Client downloads the encryption keys to be used for
decrypting content found in the manifest file.

NOTE: This setting only applies to Verimatrix decryption if the system is licensed for the
feature.
B.1.17 active.client.smooth.expedus.mode
IQD ASM Active Client for Smooth Streaming assets uses the manifest file to identify the
media fragment duration and time offset of the first fragment. Subsequent request are timed
based on the duration as advertised in the manifest file. A new manifest request is initiated
as the Active Client approaches the end of the fragments in the currently loaded file.
Expedus ASM fragment requests only use the manifest file for the initial fragment. All
following requests use the information in the TfrfBox (contained in the fragment response)
that identifies timestamps and durations of subsequent fragments.
Selecting this configuration forces the IQD ASM Active Client to operate in the same mode
as Expedus ASM. This should only be considered in cases deemed necessary otherwise
MSS manifests will only be validated by the Active Client when initiating the session.
B.1.18 active.client.use.redirect.url
When using redirected URLs, overrides the default Active Client behavior to return to the
original top level manifest for chunk requests. Enabling this mode makes the IQD ASM
Active Client retain the redirected URL for all subsequent requests.
B.1.19 alarm.ac.badvs.chunkcount.error
Per URL an alarm is generated when the number of bad VeriStream (value 1 or 2) chunks
exceeds the configured threshold.
B.1.20 alarm.ac.badvs.chunkcount.error.threshold
Define the number of continuous bad chunks before alarm generation for
alarm.ac.badvs.chunkcount.error configuration.
B.1.21 alarm.ac.badvs.chunkcount.error.severity
Defines severity of the bad VeriStream chunk alarm.
B.1.22 alarm.ac.chunk.load.error
Specifies that an error is desired when a chunk download fails. After two retries if the chunk
request continues to fail, the Active Client continues with the next chunk. This could result
in duplicate alarms depending on other configured settings. For example, the chunk load
error will occur as well as an associated HTTP 404 error.
• alarm.ac.chunk.load.error.severity
• alarm.ac.chunk.load.error.trap

B.1.23 alarm.ac.chunkdelay.error
An alarm is generated if the download time exceeds the chunk duration time. The download
time is measured from the time of the chunk request until the chunk downloaded completes.
Enabling this alarm (along with other response time alarms) can assist in determining the
source of poor VeriStream values.
• Alarm.ac.chunkdelay.error.severity
• Alarm.ac.chunkdelay.error.trap
B.1.24 alarm.ac.connection.error
Not connecting to the target location for either a manifest or chunk
• Alarm.ac.connection.error.severity
• Alarm.ac.connection.error.trap
B.1.25 alarm.ac.manifest.load.error
Specifies that the IQDialogue ASM should alarm for any reason that the Active Client
cannot load a manifest file. This alarm is typically followed by a 4xx or 5xx that specifies
the reason.
• Alarm.ac.manifest.load.error.severity
• Alarm.ac.manifest.load.error.trap
B.1.26 alarm.ac.manifest.nocontent.error
The manifest file is recognized but potentially missing mandatory information, for example,
no chunks.
• Alarm.ac.manifest.nocontent.error. severity
• Alarm.ac.manifest.nocontent.error.trap
B.1.27 alarm.ac.manifest.parse.error
Generally caused by a syntax error that deviates from the protocol specification.
• Alarm.ac.manifest.parse.error.severity
• Alarm.ac.manifest.parse.error.trap
B.1.28 alarm.ac.same.content.error
There are 2 conditions that can cause this alarm to be triggered, signifying a stale manifest:
• If the client requests the manifest file, but the file has not been modified on the server,
the server responds with the 304 status code. The alarm is created every time the “alarm
threshold” is reached. i.e. Every 3 times we get a 304, an alarm is generated (default
threshold is 3).

• If the client requests the manifest file, but the manifest file content is a duplicate of the
last time it was received, create the alarm every time the “alarm threshold” is reached.
i.e. Every 3 times we get the same content, an alarm is generated (default threshold is 3).
– Alarm.ac.same.content.error.trap
– Alarm.ac.same.content.threshold
B.2 IQDialogue ASM Alarm Descriptions and

Settings
In the IQDialogue ASM NBS interface, all alarm configurations are found on the
Configuration tab under the Alarm Settings submenu. In most cases, the IQDialogue ASM
alarm settings follow the same format. Each alarm is typically enabled or disabled with a
check box, configured for severity of the alarm notification, and when applicable provided a
threshold to initiate the alarm by either time interval or number of occurrences.
B.2.1 Per-Session 4xx Error

Description: When enabled, alarms will be generated for HTTP 4xx errors based on the
configured threshold on a per-session basis. Without this check box, Per-Session HTTP 4xx
errors are logged and retrievable through the ASM Query, but an alarm will not be
generated.
Available Settings:
• Enable/Disable: alarm.4xx.session.threshold
• Severity: alarm.4xx.session.threshold.severity
• Threshold Time: alarm.4xx.session.threshold.time – the time interval in which to check
for 4xx error codes.
• Threshold Count: alarm.4xx.session.threshold.count – the number of acceptable 4xx
errors over the defined time interval. A count greater than this threshold within the
configured time period will trigger the alarm.
B.2.2 General 4xx Error

configured threshold. Without this check box, HTTP 4xx errors are logged and retrievable
through the ASM Query but an alarm will not be generated.
Available Settings:
• Enable/Disable: alarm.4xxerror
• Severity: alarm.4xxerror.severity
• Threshold: alarm.4xx.threshold - 4xx threshold alarm applies to all monitored flows. An
alarm will be sent when the number of configured 4xx alarms is reached in a 60 second
window. Disabling the 4xxerror will also disable the threshold alarm.

B.2.3 Per-Session 5xx Error

configured threshold on a per-session basis. Without this check box, Per-Session HTTP 5xx
errors are logged and retrievable through the ASM Query, but an alarm will not be
generated.
Available Settings:
• Enable/Disable: alarm.5xx.session.threshold
• Severity: alarm.5xx.session.threshold.severity
• Threshold Time: alarm.5xx.session.threshold.time – the time interval in which to check
for 5xx error codes.
• Threshold Count: alarm.5xx.session.threshold.count – the number of acceptable 5xx
errors over the defined time interval. A count greater than this threshold within the
configured time period will trigger the alarm.
B.2.4 5xx Error

configured threshold. Without this check box, HTTP 5xx errors are logged and retrievable
through the ASM Query but an alarm will not be generated.
Available Settings:
• Enable/Disable: alarm.5xxerror
• Severity: alarm.5xxerror.severity
• Threshold: alarm.5xx.threshold - 5xx threshold alarm applies to all monitored flows. An
alarm will be sent when the number of configured 5xx alarms is reached in a 60 second
window. Disabling the 5xxerror will also disable the threshold alarm.
B.2.5 Chunk Count

Description: Indicates that the number of chunks specified in the manifest/index file is
lower than the configured threshold. This type of validation is best used during lab test or
product qualification scenarios when adaptive assets are tightly controlled. In this
environment, the active client serves as a validation tool of system performance.
Available Settings:
• Enable/Disable: alarm.chunk.count
• Type: alarm.chunk.count.per.manifest.type – Specifies the type of monitoring (Active,
Passive or Both) to apply the chunk count measurement.
• Severity: alarm.chunk.count.severity
• Threshold: alarm.chunk.count.size – Number of chunks per manifest

B.2.6 Chunk Size

Description: When enabled, IQDialogue ASM will create an alarm when the ‘received’
chunk size is smaller than the ‘expected’ chunk size.
The ‘expected’ chunk size typically comes from the HTTP header “Content-Length” field,
but it can come from the beginning of the data as a hex-encoded length for the chunk. If the
“received” size < “expected” size, then we are missing part of the chunk. This is likely due
to packet loss or when the active client session ends while a chunk was downloading.
Available Settings:
• Enable/Disable: alarm.chunk.size.error
• Severity: alarm.chunk.size.error.severity
B.2.7 Chunk Variation

Description: Indicates that the chunk size for a given session is larger than the configured
variation threshold (default is 20%). The nominal chunk size is the average over the lifetime
of the publishing flow. This alarm is best used in a lab environment where assets are tightly
controlled and session behavior is predictable.
Available Settings:
• Enable/Disable:alarm.chunk.variation
• Severity:
• alarm.chunk.variation.severity
• Threshold:
• alarm.chunk.variation.percentage – Configurable difference between the average chunk
size and the current chunk size defined as a percentage. It is defaulted to 20%.
B.2.8 Duplicate Chunk Request

Description: A cache or mid-cache is requesting duplicate chunks within the configured
threshold time. A properly working cache should not request the same segment twice.
NOTE: This alarm should only be enabled when the IQDialogue is configured in
non-associative mode, and the IQDialogue probe is passively monitoring
intra-CDN traffic.
Available Settings:
• Enable/Disable: alarm.duplicate.chunkrequest
• Severity: alarm.duplicate.chunkrequest.severity
• Thresholds:
– alarm.duplicate.chunkrequest.chunkcount – how many duplicates must be
requested before an alarm is triggered
– alarm.duplicate.chunkrequest.time – time period to verify duplicate chunk
requests

B.2.9 Duplicate Publishing

Description: The same manifest file was published to the origin server within a 1 minute
time period.
Available Settings:
• Enable/Disable: alarm.duplicate.publishing
• Severity: alarm.duplicate.publishing.severity
B.2.10 HTTP GET Transfer Time

Description: The time duration to download the next media chunk/segment. This value is
represented on the ASM Census view in the Time Difference column for chunk specific
information. This alarm applies only when the IQDialogue ASM probe is configured in
non-associative mode for intra-CDN operation.
Available Settings:
• Enable/Disable: httpget.transfer.time
• Severity: httpget.transfer.time.severity
• Threshold: httpget.transfer.time.delay
B.2.11 HTTP PUT Chunk Missing

Description: Alarm is triggered if there are publishing chunks missing. The IQDialogue
ASM compares the names of the chunks expected (based on the manifest file) against the
chunks processed. If any of the expected chunks did not get processed, an alarm is generated
that lists the names of the expected chunks not received.
Available Settings:
• Enable/Disable: alarm.httpput.chunkmissing
• Severity: alarm.httpput.chunkmissing.severity
B.2.12 HTTP PUT Min Chunk

Description: This alarm allows the user to establish a minimum publishing rate for HLS
streams to determine the status of devices involved in content acquisition, transcoding or
segmenting. The publishing rate is set by chunks per minute for each stream.
Use this alarm to monitor publishing of live events and identifying a potential outage.
Available Settings:
• Enable/Disable: alarm.httpput.minchunk.perminute
• Severity: alarm.httpput.minchunk.perminute. severity
• Threshold: alarm.httpput.minchunk.perminute.count

B.2.13 HTTP PUT Transfer Time

Description: The file transfer time for publishing a media chunk to the origin server. Given
a known target chunk size, aggregate publishing traffic rate and the link speed, a target
publishing transfer time can be configured to identify if the publishing process it taking
longer than expected. If content is not available at the origin server upon request, users will
experience performance impact.
Available Settings:
• Enable/Disable: alarm.httpput.transfer.time
• Severity: alarm.httpput.transfer.time.severity
• Threshold: alarm.httpput.transfer.time.delay
B.2.14 Publishing HLS No Key

Description: Specifically for HLS content, no encryption key is available in the index file.
Available Settings:
• Enable/Disable: alarm.publishing.hls.nokey
• Severity: alarm.publishing.hls.nokey.severity
B.2.15 Publishing mp2ts Nonconformance

Description: MPEG-TS conformance identifies the presence and absence of critical MPEG
video components PAT, PMT, audio PID and video PID. To utilize MPEG-TS Conformance
Alarms, the media asset must be unencrypted and HLS formatted.
Enabling a constant test stream through the encoder, segmenter and publisher allows
continuous validation that MPEG transport packet headers required for media playback
remain intact during the publishing life cycle.
Available Settings:
• Enable/Disable: alarm.publishing.mp2ts.nonconformance
• Severity: alarm.publishing.mp2ts.nonconformance.severity
B.2.16 Publishing Outage

Description: All publishing alarms are enabled or disabled with this setting. For publishing
alarms to be generated this option must be selected.
Available Settings:
• Enable/Disable: Publishing. outage

B.2.17 Publishing Outage By IP

Description: By default, publishing alarms are generated based on the control URI and
destination IP address. Enable this configuration to generate publishing outage alarms based
on the publishing server IP address.
Available Settings:
• Enable/Disable: alarm.publishing.outage.by.ip
• Severity: alarm.publishing.outage.severity
B.2.18 Publishing RTMP Outage

Description: After recognizing and RTMP flow, the outage alarm will trigger if the RTMP
flow is no longer present.
Available Settings:
• Enable/Disable: alarm. publishing.rtmp.outage
• Severity: alarm. publishing.rtmp.outage.severity
B.2.19 VeriStream Quality

Description: IneoQuest’s VeriStream quality metric provides an easy to use method of
identifying asset performance. Setting the VeriStream quality alarm provides notification
when a percentage of all chunks have a VeriStream value of 1 to 3, indicating an overall
quality issue of the monitoring point addressed by the IQDialogue ASM probe.
Available Settings:
• Enable/Disable: alarm.veristream.quality
• Severity: alarm.veristream.quality.severity
• Threshold: alarm.veristream.threshold – percentage of chunks that must be VeriStream 1
to 3 for the alarm to trigger


Glossary of Terms
A analysis resources for either more thorough stream

quality analysis or analysis of more streams.
ABR: Adaptive Bit Rate A method by which the Basic/Elite/Extreme Terms used in IneoQuest DVA
delivered bit rate of video varies usually based on the product’s Program Video template Frame Errors metric
dynamically available network bandwidth. “Frame Profile” section to describe escalating
App (Application) For consumer devices, an App is completeness of video analysis options where Basic
software created by the service provider/ broadcaster selects that only I Frames are examined, Elite selects
that enables access to their media content. An App may that only I and P Frames are examined, and Extreme
use the native device Media Player or a third-party selects that I, P, and B Frames are examined. Escalating
Media Player. The App typically includes a user completeness selection enables a user to trade-off
interface to browse available media and control player analysis resources for either more thorough stream
functions that include, start, stop, scrubbing, etc. The quality analysis or analysis of more streams.
App is typically responsible for authentication with the BS.1770 BS.1770 defines the loudness algorithms used
media service to validate the user account, provide to measure the perceived loudness of program material.
billing, etc. Most service provider/broadcaster
Blockiness In IneoQuest’s DVA version 3.02 product,
organizations outsource App development.
this metric indicates the dynamic level of compression
ARP: Address Resolution Protocol The of a video stream as determined by the analysis of a bit
standard method for finding a host's hardware address stream’s video blocks. In later versions of DVA, this
when only its network layer address is known. term is replaced by Compression Level.
ASI or DVB-ASI: Asynchronous Serial Buffer underrun Gear Change Risk (BGCR)
Interface The physical interface that is designed to An event detected by ABR monitoring equipment,
transport video transport streams serially over coax typically by the detection of low values of the
cable at up to 270Mb/s. DVB is a family of European VeriStream metric, where media chunks are not
digital video standards. received from a source as fast as they are consumed by
Asset Used to refer to the content or program regardless an end-user’s media player and a media player would
of the bit rate or resolution in which it is encoded. For typically react by stalling (“re-buffering”) or with a
example, “NBC” or “Star Wars” or “My Funny downshift to a lower bit rate asset variant. The event is
Screaming Cat” is an asset. named a “risk” since, depending on the internal
algorithm design, an end-user player can dynamically
Asset Variant Used to identify an Asset’s bit rate
select it’s response to slowly arriving media chunks
variant. An Asset is usually encoded in sequences of
and can pre-buffer an arbitrary number of media
segment files of different bit rates. An Asset Variant is
chunks making it impossible to precisely report
the set of segments of a common bit rate. An “Asset”
whether the user experiences a “re-buffering”, gear
includes multiple “Asset Variants”.
change, or other player response.
B C
Basic/Adaptive/Strict Terms used in IneoQuest
CA Acronym for Conditional Access
DVA® product’s Program Video template Frame Errors
metric “Error Profile” section to describe escalating CAS Acronym for Conditional Access System
completeness of video analysis options where Basic Client The software program entity described in the
selects that only I Frames are examined, Adaptive HTTP (RFC 7230) Client/Server protocol that
selects that only I and one P and one B Frame are establishes a connection to a Server for the purpose of
examined per GOP, and Strict selects that all I, P, and B sending one or more HTTP requests, typically for
Frames are examined for each GOP. Escalating media information. A Server is a program that accepts
completeness selection enables a user to tradeoff connections in order to service HTTP requests by
sending HTTP responses. A Client protocol entity may
IQDialogue ASM 4.0 User’s Guide — SUG-DIAASM-007 GL-1

initiate a single or multiple simultaneous Sessions. A
Client protocol entity may be virtualized. The “end
E
Client device” is the hardware that enables the Client EBIF Enhanced TV Binary Interchange Format (EBIF)
to initiate and receive streaming ABR content for a is a collection of signaling and messaging
Subscriber. This may or may not be the same device specifications that makes it possible for television
that enables the Subscriber to display the content. An program producers and advertisers to create and serve
IneoQuest product such as Surveyor ABR or Expedus interactive multimedia content through a television's
ASM is both a “Client device” and hosts the Client set-top box.
entity of the client/server protocol but is not an “end
EBP Data structure carried in a video stream used by
Client device”.
stream segmenters and packagers to create required
Closed Caption One of a series of subtitles to a segments or fragments in the preparation of an ABR
television program, accessible through a decoder. media stream.
Compression Level In IneoQuest’s DVA version ECM Acronym for Entitlement Control Message
4.0 product, this metric indicates the dynamic level of
EMM Acronym for Entitlement Management Messages
compression of a video stream as determined by the
analysis of a bit stream’s video blocks. In previous Errored Second An errored second is an interval of a
versions of DVA, the term used for this metric was second during which any error whatsoever has
Blockiness. occurred, regardless of whether that error was a single
bit error, or a complete loss of communication for that
Continuous Monitoring The configuration of a entire second.
monitoring agent such that all packets from the asset
source are inspected for an indefinite period rather than ETV Enhanced Television (ETV) refers to interactive
intermittently sampled or scanned in accordance with a services and applications provided in conjunction with
scheduling algorithm. video programming.
CRC Error Cyclic redundancy check error is the
receipt of data which does not match the cyclic
redundancy check validation process.
F
FEC Forward Error Correction is a communications
technique that is used to correct errored data on the
D receiving end. Before transmission, the outgoing data
is processed through an algorithm that adds extra bits
Data Carousel The content of the transmission stream that are used for error correction. If the transmitted
is provided in a cyclic fashion.
message is received in error, the correction bits are
dBmV Decibels relative to one millivolt used to repair it.
Device Hardware that is used to initiate streaming ABR Flow Term used in IneoQuest products that refers to a
content. This could be subscriber owned (mobile time sequence of IP datagrams with common source
device, smartTV, Roku®) or operator owned (STB) or and/or destination IP address usually carrying one or
proxy device (home gateway) or hardware that hosts a more media programs.
synthetic Client such as IneoQuest’s Expedus ASM or
Flow Alias Term used in IneoQuest products that
Surveyor ABR.
refers to a character string, often selected for human
Dialnorm Meta-data with defined values from 1 to 31 readability, that corresponds to the IP addresses
included in the Dolby Digital AC-3 audio compression identifying a Flow.
system that controls a decoder’s playback loudness.
DPI Acronym for Digital Program Insertion
DTV Acronym for Digital Television
G
DVA Acronym for Digital Video Analyzer Ghost PID A PID that does not appear in the Program
Association Table (PAT) PID structure.
DVB Acronym for Digital Video Broadcasting
GOP A group of pictures, or GOP structure, specifies
the order in which intra- and inter-frames are arranged.
The GOP is a group of successive pictures within a
coded video stream. Each coded video stream consists
GL-2 IQDialogue ASM 4.0 User’s Guide — SUG-DIAASM-007

of successive GOPs. From the pictures contained in it, ISO Acronym for International Organization for
the visible frames are generated. Standardization
I L
IDR Frames An Instantaneous Decoder Refresh (IDR) Levels Certain IneoQuest Monitoring tools can be
frame is a special type of I-frame in H.264. An IDR user-configured to adjust the depth or level of analysis.
frame specifies that no frame after the IDR frame can Level 1 is the simplest monitoring level requiring the
reference any frame before it. This makes seeking the least monitor resources and enabling the highest
H.264 stream easier and more responsive in the player number of monitored assets. Higher levels provide
because the player does not have to retain or process a more thorough monitoring to better detect more types
long history of frames. All subsequent transmitted of impairments and result in faster impairment
frames can be decoded without reference to any frame detection but typically require more monitor
decoded prior to the IDR picture. computing resources resulting in higher costs or lesser
IEC Acronym for International Electrotechnical number of simultaneous monitored assets.
Commission LKFS Loudness, K-weighted, relative to Full Scale
IGMP: Internet Group Management Protocol (LKFS) is a standard loudness metric used to enable
(ver 1,2) (as per RFCs 1112/2236) IGMP is used to normalization of audio levels for delivery of broadcast
dynamically register individual hosts in a multicast TV and other video.
group on a particular LAN. Hosts identify group
memberships by sending IGMP messages to their local
multicast router. Under IGMP, routers listen to IGMP M
messages and periodically send out queries to discover
Master Playlist A file that provides a set of bit rate
which groups are active or inactive on a particular
variants and resolutions which describe different
subnet.
versions of the same content. A playlist is a Master
Instrumented Media Player A player that Playlist if all URI lines in the file identify Media
integrates IneoQuest’s Software Design Kit (SDK) Playlists.
software to enable monitoring and reporting media
Master Program The Master Program Name is used
transport quality performance levels and other
in DVA/Inspector™ to identify a collection of bit rate
statistics.
variants carrying the same program content but
I/P/B Frame I-frame (Intra-coded), P-Frame encoded at different bit rates. Using recommended
(Predicted), B-frame (Bi-predictive) are picture types terminology, a Master Program Name is similar to the
used in video compression algorithms where I-frames Asset name. As used in the DVA/Inspector tool, it
hold fully specified pictures, P-frames include refers to the collection of bit rate variants that are
information about changes in the image from the received by the monitor while the Asset may have been
previous frame, and B-frames include information encoded and resides on a server as a larger collection of
between the current frame and both preceding and Asset Variants.
following frames.
Media Playlist A file that contains a list of Media
IP Multicast: Internet Protocol Multicast IP Segments of the same bit rate. A playlist is a Media
Multicast delivers source traffic to a group of receivers Playlist if all URI lines in the file identify media
without adding any additional burden on the source or segments.
the receivers while using the least network bandwidth
Media Player Refer to Player or Media Player.
of any competing technology. Multicast packets are
replicated in the network resulting in the most efficient MDI-DF: Delay Factor Delay Factor is a metric
delivery of data to multiple receivers possible. All which characterizes IP Packet cumulative jitter and
alternatives require the source to send more than one delay. The DF is the amount of buffer, in milliseconds,
copy of the data. that would be required to subtract IP packet arrival
deviations from the rate determined by the media
IP-SBR: IP Stream Bitrate The IP Stream Bitrate
payload.
is the measured data (payload) per second of a given
media over IP stream. The type of the payload is not MDI-MLR: Media Loss Rate Media Loss Rate is
considered, just the amount of payload in bytes is the number of media packets lost per second.
measured.

MDI-MLT: Media Loss Total Media Loss Total is to the receiving device about the received service or
the total number of media packets lost for a given program.
inspection period. MTSP Acronym for MPEG transport stream packet
MDI-MLT-15: Media Loss Total-15 Media Loss Multicast IP Address (as per RFC3171) IP
Total is the total number of media packets lost for the multicast address are defined as IP addresses within the
15-minute inspection period. This clears at the end of range 224.0.0.0 and 239.255.255.255. IP multicast
the 15 minute interval (i.e., at 00, 15, 30, 45 minutes addresses within 224.0.0.0 and 224.0.0.255 are
after the hour). reserved for network protocols. A multicast HOST will
MDI-MLT-24: Media Loss Total-24 Media Loss generate traffic with an IP destination address within
Total is the total number of media packets lost for the the defined multicast range. Multicast RECEIVERS
24 hour inspection period. It provides a history of the that are interested in receiving data flowing to a
current 96 15-minute inspection periods. This clears at particular group must join the group using the IGMP
midnight and is not a rolling 24 hours. protocol.
MDI-VB: Virtual Buffer Virtual Buffer is the same Multiscreen Multiscreen video describes video
as DF expressed in bytes for a given media stream rate. content transformed into multiple formats, bit rates and
The VB is the amount of buffer, in bytes, that would be resolutions for display on devices such as television,
required to subtract IP packet arrival deviations from mobile phone, tablet computer and computer.
the rate determined by the media payload. Mux Multiplexer
MER Modulation Error Ratio is the ratio, in decibels, of
average symbol power to average error power.
MLS: Media Loss Seconds Media Loss Seconds N
is the total number seconds that saw a loss of media NDA Acronym for Non-Disclosure Agreement
packets from the time the stream was recognized.
Nominal Bitrate The Nominal bitrate is the media
MLS-15: Media Loss Seconds-15 Media Loss bitrate calculated from a stream’s PCR time stamps
Seconds is the total number seconds that saw a loss of when the transport stream is initially detected.
media packets for the 15-minute inspection period.
This clears at the end of the 15 minute interval (i.e., at
00, 15, 30, 45 minutes after the hour). P
MLS-24: Media Loss Seconds-24 Media Loss
Seconds is the total number seconds that saw a loss of PAT: Program Association Table A Program
media packets within the 24 hour inspection period. Association Table is a specific PID that every transport
This clears at midnight and is not a rolling 24 hours. stream is required to contain. It provides the
correspondence the program numbers and the PIDs
MLS-LD Media Loss Seconds is the total number of defined in the PMT. The PAT may be partitioned into
seconds that saw minimum loss distance alarms. 255 sections before it is mapped to a transport stream
MLS-LP Media Loss Seconds is the total number of to minimize loss.
seconds that saw maximum loss period alarms. PCR: Program Clock Reference The program
MOS The Mean Opinion Score (MOS) provides a clock reference (PCR) is transmitted periodically
numerical indication of the perceived quality from the within a video transport stream as a time reference. A
users' perspective of received media after compression sufficiently accurate and correctly received PCR is a
and/or transmission. The MOS is expressed as a precondition for correct data display in the receiver.
number in the range of 1 to 5, where 1 is lowest Performance Metrics Term used in IneoQuest
perceived quality, and 5 is the highest perceived quality products that describes media metrics such as Program
measurement. Availability, Errored Seconds, MOS, etc. as reported
MPEG Acronym for Moving Picture Experts Group over an interval of typically 15 minutes or 24 hours. In
MPEG Tables, SI/PSI/PSIP: Service contrast, Real-Time media metrics are updated as
Information, Program-specific events happen within, typically, 5 to 60 seconds.
Information, Program and System PES: Packetized Elementary Stream
Information Protocol Meta-data defined by Packetized Elementary Stream (PES) is a specification
DVB, ISO/IEC, and ATSC respectively typically defined by the MPEG communication protocol that
carried in a data table format that provides information allows an Elementary stream to be divided into
packets. The elementary stream is packetized by

encapsulating sequential data bytes from the experiences impairments by initiating media sessions
elementary stream inside PES packet headers. using synthetic clients. Media sessions can thus be
PID: Packet Identifier A Packet Identifier is a monitored and repaired before an end user is impacted
unique 13-bit identifier located within the first 4-byte assuring the best user experience.
prefix of a transport stream used to identify Probe Hardware or software used to collect information
components of the transport stream, such as PES, from network program flows.
program tables, PCR for each program, etc. Certain Program Term used in IneoQuest products that
PIDs are predefined, such as: describes the video, audio, and control data that
8191 = stuffing PID together make up a single thread of content such as
8187 = PSIP PID (Program and System Information CNN, NBC, CBS, etc. In the case of a Multi-Program
Protocol) Transport Stream, it describes a single program that
Player or Media Player Software in an Application typically includes a video stream and one or more
that typically performs the following functions: audio streams.
• Establishes a media session using appropriate Program Alias Term used in IneoQuest products that
services available on the device refers to a character string, often selected for human
• Maintains the algorithm of when to request readability, that corresponds to the Program Number in
segments and perform gear changes (i.e. the PAT (Program Association Table).
maintaining the media buffer for intended purpose). Program Availability Quality metric used in
The intended purpose, or optimization, may be for IneoQuest products that is derived from the ratio of
best playback quality, maintain minimum buffer non errored seconds to total measured seconds in a
size, minimize network bandwidth, etc. specified interval expressed as a per cent. IneoQuest
• Interface with DRM services for content decryption products enable the user to select from a number of
• Decompressing the content and forwarding to a metrics and thresholds to determine an errored second
display based on a user’s quality criteria. For Program
Availability comparisons, errored seconds between
In the case of consumer devices, a content provider or measured programs should have the same definitions.
broadcaster can select the media player to be used for
implementation within an Application because the end Program Number A 16 bit value in the PAT
user will download/install a customized application for (Program Association Table) that specifies the
media access from the given provider. This is often the program_map_PID. The Program Map table, in turn,
case on iOS and Android devices. Providers/broadcast- provides the mapping between program numbers and
ers will choose a media player that fits their needs for the program elements that make up a program such as
advanced features. Example media players include – video, audio, etc.
Kaltura, NexStreaming, ExoPlayer, VisualOn, Bitm- PSI Acronym for Program Specific Information
ovin. PSIP: Program and System Information
In the case of an IneoQuest Client device such as an Protocol A protocol defined by the ATSC digital
Expedus ASM or Surveyor ABR that only establishes television standard for carrying data about each
media sessions for monitoring but typically does not channel within the transport stream; such as content
perform gear changes, decompress video, nor forward ratings, program guides, time referenced, station ID
to a display, using the term Player to describe this and conditional access information. PID 8187 is
software functionality is not recommended. reserved for PSIP content.
Playlist A file used by a client that contains information PTS Acronym for Presentation Time-Stamp
about available content that can be played. A Playlist
can be either a Media Playlist or a Master Playlist.
PMT: Program Map Table A specific PID within a Q
transport stream which provides the mapping between QAM Acronym for Quadrature Amplitude Modulation
a program number and the program elements it is
comprised of. It contains a minimum of a program
QoE Acronym for Quality of Experience
number, PCR PID, stream types and program element QoS Acronym for Quality of Service
PIDs.
Proactive Monitoring A monitoring strategy that
can detect media impairments before an end user

R packet loss once it starts. LPE is the total number of
Loss Period errors.
Real Time Metrics Term used in IneoQuest products RTP-SE: Sequence Errors (as per RFC3357)
that describes media metrics such as MDI, bit rate, metric captures the total lost packets given the
packet loss, etc. that are reported as they happen difference in sequence numbers of two successive
within, typically, 5 to 60 seconds. packets of a RTP stream.
Reactive Monitoring A monitoring strategy that RVL: Remote Video Link A 10/100/1000 Ethernet
detects media impairments at the same time the end port on select IneoQuest equipment that allows any
user is experiencing the impairments or later after a video IP stream traffic entering the unit to be
viewer compliant has been registered. Reactive forwarded out this port for other uses. The RVL port
monitoring can utilize a sampling algorithm or can also modify the IP header of the selected IP stream,
continuous monitoring. Reactive monitoring can utilize at line rate, not changing the IP stream behavior.
passive monitoring that analyzes end user sessions or
synthetic clients that are initiated during or after a
reported impairment to acquire diagnostic information. S
This monitoring strategy may detect impairments that
an end user may not notice or may not report and thus Sampling Any non-continuous monitoring algorithm
has a proactive monitoring aspect. such as scanning in which assets are selected for given
intervals for monitoring rather than being continuously
RF Acronym for Radio Frequency
monitored.
RS Reed-Solomon error correction protocol
Scanning A sampling (non-continuous) algorithm in
RS CO Reed-Solomon corrected errors are an early which assets are selected for given intervals for
warning of potential Reed-Solomon uncorrected errors. monitoring rather than continuously. Scanning
RS CO15 Reed-Solomon corrected errors for the typically refers to a periodic selection algorithm such
current 15 minute inspection period that a group of assets are monitored for a period of
time, followed by another group, etc. with the process
RS CO24 Reed-Solomon corrected errors for the
repeating indefinitely. In more complex configurations,
current 24 hour inspection period
one can configure dynamic schedules for scanning that
RS UC Reed-Solomon uncorrected errors alter the dwell and repeat periods. One often chooses
RS UC15 Reed-Solomon uncorrected errors for the scanning selection over continuous asset monitoring to
current 15 minute inspection period cover more assets with less monitoring resources with
RS UC24 Reed-Solomon uncorrected errors for the the tradeoff that problem detection time will be
current 24 hour inspection period extended. Both network bandwidth and monitoring
agent capacity can be minimized through the use of
RTP: Real-Time Protocol The Real-Time transport sequential asset scanning. Scanning is an example of
protocol (RTP) is a Layer 4 protocol defined in RFC Proactive monitoring. Scanning involves a predefined
3550 that provides end-to-end delivery services for time interval (a ‘tick’), of typically 30 seconds duration
data with real-time characteristics, such as interactive enabling a user to configure a monitoring action for
audio and video. Those services include payload type each of the ticks. For example, a user might specify a
identification, sequence numbering, time stamping and monitor’s actions for each of the 120 ticks that occur
delivery monitoring. Applications typically run RTP on per hour; when the hour completes, the actions are
top of UDP to make use of its multiplexing and repeated. Since the ticks are aligned with wall clock
checksum services; both protocols contribute parts of time via NTP, multiple monitors can be synchronized
the transport protocol functionality. such that a given asset can be monitored
RTP-LDE: Loss Distance Errors (as per simultaneously at different locations. The Program
RFC3357) metric captures the spacing between the Lineup Manager (PLM) product is typically used to
loss periods. Loss Distance (LD) is the difference in map out (configure) Scanning over a monitoring period
sequence numbers of two successively lost packets, for a known channel lineup or to arrange monitor
which may or may not be separated by successfully Scheduling for an upcoming media event or multiple
received packets. LDE is the total number of LD media events.
errors. Schedule A specification of a sampling algorithm that
RTP-LPE: Loss Period Errors (as per RFC3357) results in determining the start and end time(s) for
metric captures the frequency and length of RTP monitoring an asset. Specifying a Schedule for

monitoring an asset enables a user to configure a start different networks, etc. to diagnose and isolate the root
time and date and duration; for example, a user may cause of a media impairment. A swarming
choose to Schedule a performance event or Schedule a configuration may change the operation of one or more
selected program offering from a viewing guide for synthetic clients to synchronized operation where the
monitoring. monitoring entities gather data on an asset source
Scrambling Technique used to encrypt video and simultaneously thus operating as a distributed system.
audio to protect content from unauthorized viewing Due to the multiple monitoring entities, a swarming
and copying. configuration is more resistant to failure than a single
monitoring entity. The iVMS™ ASM product can be
SCTE Acronym for Society of Cable used to initiate Swarming by configuring distributed
Telecommunications Engineers monitoring products to selected assets on demand.
SCTE-35 SCTE-35 is a broadcast standard to signal an Swarming may be initiated periodically (Scheduled) or
advertisement in response to an operational event (Ad Hoc).
Segment The Media Playlist lists the media Segments Synthetic Client A Client such as a Surveyor ABR or
that make up the overall content presentation. A Expedus ASM that requests Assets for transport and/or
Segment is the 2 to 10 second (approximately) portion content quality analysis but do not typically forward
of the overall content presentation. the content for human viewing.
Session Used to describe the sequence of media files
sent to a client over a period of time. During a session,
one or more Assets may be requested and received by a T
typical subscriber – that is, a viewer may be watching TAP Test Access Port
WGBH for 10 minutes and then switch to WCVB for
10 minutes. All this activity would be part of the same Thumbnail A small image representation of the video
Session. The start and end of a Session is determined content of a program used to identify as well as verify
simply by periods of continuous activity. If a client the presence and quality of content. The small image is
neither requests nor receives media from a server for a used for both computational and display efficiency.
period, for example, 60 seconds, then the session is Total CC Errors: Total Continuity Count
terminated. When a request is initiated from a client Errors The Total Continuity Count Errors is the
after a period of inactivity, then a session is started. A total number of errors in the MPEG transport stream
Session includes receiving one asset at a time; if two for the given inspection period, based on the 4-bit
assets are received simultaneously, then two sessions continuity counter in the MPEG transport stream.
are active. Note that an IneoQuest synthetic client in Total PID/Mon/Err: Total number of Transport
the Surveyor™ ABR product would typically initiate Stream PIDs/Monitored/Errored Total
multiple simultaneous Sessions requesting multiple number of PIDs within the MPEG transport stream, as
asset variants for the same asset unlike a typical detected in the Program Table/ Total number of PIDs
subscriber client. within the transport stream currently being monitored
SI Acronym for Service Information by system resources/ Total number of PIDs being
monitored that are currently seeing errors.
SNTP Simple Network Time Protocol is a less complex
form of Network Time Protocol that does not require TR 101 290 Refers to the ETSI TR 101 290 Technical
storing information about previous communications. Report titled: “Digital Video Broadcasting (DVB);
Measurement guidelines for DVB systems” that
Stream The received sequence of media files including
describes measurements of DVB digital TV systems.
protocol overhead arriving at a client during a session.
“Stream” is preferred in general over “program” or TS Acronym for Transport Stream
“flow”. TSID: transport_system_id The 16 bit integer in
Subscriber The end user that could be a single viewer the header of a PAT (Program Association Table) that
or group of people. identifies a particular transport stream from any other
within a network.
Swarming Swarming behavior is the collective
configuration of a number of monitoring entities to TS PID: Transport Stream Packet ID A unique
monitor a particular asset or assets in particular 13 bit Packet ID (PID) value used to identify
location. Swarming may be used in a Reactive elementary streams of a program in a single or
monitoring strategy to collect monitoring results from multi-program Transport Stream as described in
different geographic locations, different CDNs, ISO/IEC 13818-1.

V
V-TSB: Video Transport Stream Bitrate The
Video Transport Stream Bitrate is the measured bitrate
of the encapsulated video transport stream within an IP
stream. The arrival data rate of the IP packets is not
considered. This measurement looks at the video
transport stream payload bitrate by inspecting the
PCRs within the transport stream being carried by the
IP packets.
Z
ZAP: ZAP Time Time which it takes for a Multicast
group stream to appear at a destination after an IGMP
join is issued from the destination. For certain Video
over IP applications, that use multicast groups to
transport video, this can be referred to as channel
change time.

Index
A I
Active Alarms 8-8 Intra-CDN 2-1
Active Client 2-2 iVMS ASM Integration 3-3
Group Association on Import 8-42
Recent Alarms 8-38 J
Report by Token 9-7 Java applet 8-1
Report by URI 9-9 Java Requirements 8-1
Session Logging 8-37
Active Requests (AR) Census 8-42 L
Active Requests (AR) Logs 8-42 Logging into the NBS GUI 8-2
Alarm Events 8-3
Alarms & Errors 9-20
P
Apple HLS Traffic 4-4
Publishing 2-1
Authentication 8-34
Publishing Failure Rate 8-8
Automated Report Definitions Tab 9-2
Publishing Outage Report 9-25
Automating a Report 9-4
R
B
Reporting Tab 9-2
Bandwidth Usage 8-10, 9-16
Response Failure Rate 8-8
C
S
Capture File 5-2
Smooth Streaming Traffic 4-7
Client IP/UA Pairings Report 9-26
Client Sessions Report 9-11
Client Type Distribution 8-11 T
Configure Options 8-40 Top 10 Manifest Distribution 8-11
Traceroute 8-39
Transactions 8-2
D
Database Purging 6-1
Database Transactions Logging and Sizing 6-1 U
User-Agent Report 9-14
E
Edge Cache 2-2 V
VeriStream Metric Distribution 8-9
Video Uplink 8-35
F
File Capture 5-1
W
Web based user interface 4-1
G
Web browser requirements 3-1
Generated Reports Tab 9-3
Grouping 8-37
Grouping Management Features 8-40
H
HLS Manifest Detail 9-22
HTTP Errors 4XX 8-6
HTTP Errors 5XX 8-8
HTTP Errors by Server 9-18
HTTP Publishing Sessions 8-5
HTTP Sessions Initiated 8-4
IQDialogue ASM 4.0 User’s Guide — SUG-DIAASM-007 Index-1

Index-2 IQDialogue ASM 4.0 User’s Guide — SUG-DIAASM-007
IneoQuest Technologies, Inc.
170 Forbes Boulevard
Mansfield, MA 02048
URL:
Phone:
1-508-339-2497
Fax:
1-508-339-4727

Iqdialogue Asm 4.0 User's Guide - Sug-Diaasm-007

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Iqdialogue Asm 4.0 User's Guide - Sug-Diaasm-007

Uploaded by

Copyright:

Available Formats

IQDialogue® ASM 4.

Document Number: SUG-DIAASM-007

The information in this guide is subject to change without notice.

Proper Use of IneoQuest Products

1 Technical Support Information

4 Web Interface Session Monitoring

6 Disk and Database Logging

IQDialogue ASM 4.0 User’s Guide — SUG-DIAASM-007 i

8 Northbound Services (NBS) GUI, Dashboards, and Alarming

ii IQDialogue ASM 4.0 User’s Guide — SUG-DIAASM-007

IQDialogue ASM 4.0 User’s Guide — SUG-DIAASM-007 iii

Appendix B Active Client and Alarm Configuration Descriptions

Glossary of Terms .......................................................................................................................... GL-1

iv IQDialogue ASM 4.0 User’s Guide — SUG-DIAASM-007

1 Technical Support Information

1.1 Address and Telephone Numbers

1.2 Internet Addresses

1.3 About this Document

IQDialogue ASM 4.0 User’s Guide — SUG-DIAASM-007 1-1

1.3.1 Documentation Feedback

1-2 IQDialogue ASM 4.0 User’s Guide — SUG-DIAASM-007

2.1 Product Definition

2.2 Product Overview

IQDialogue ASM 4.0 User’s Guide — SUG-DIAASM-007 2-1

2.2.1 Key Features

2-2 IQDialogue ASM 4.0 User’s Guide — SUG-DIAASM-007

2.2.2 Monitoring and Analysis

IQDialogue ASM 4.0 User’s Guide — SUG-DIAASM-007 2-3

– Chunk Per Minute Error

2-4 IQDialogue ASM 4.0 User’s Guide — SUG-DIAASM-007

This chapter provides the following information:

3.1 System Requirements

IQDialogue ASM 4.0 User’s Guide — SUG-DIAASM-007 3-1

3.2 Requirements for Smooth Streaming

3.3 Requirements for Active Client Monitoring

3.4 Client Request or Content Distribution

3-2 IQDialogue ASM 4.0 User’s Guide — SUG-DIAASM-007

3.5 iVMS ASM Integration

IQDialogue ASM 4.0 User’s Guide — SUG-DIAASM-007 3-3

3-4 IQDialogue ASM 4.0 User’s Guide — SUG-DIAASM-007

4 Web Interface Session Monitoring

Figure 4-1: IQDialogue ASM Main Operating Screen

This chapter provides the following information:

IQDialogue ASM 4.0 User’s Guide — SUG-DIAASM-007 4-1

4.1 Menu Layout and Filters

4-2 IQDialogue ASM 4.0 User’s Guide — SUG-DIAASM-007

• Smoothstreaming / Publish: Provides detailed analysis of Microsoft Smooth Streaming

4.2 Interface and Traffic Monitoring Details

IQDialogue ASM 4.0 User’s Guide — SUG-DIAASM-007 4-3

4.3 Streaming Protocols

4.3.1 Apple HLS Traffic

Figure 4-2: Apple HLS Traffic Monitoring

The layout format is:

4-4 IQDialogue ASM 4.0 User’s Guide — SUG-DIAASM-007

IQDialogue ASM 4.0 User’s Guide — SUG-DIAASM-007 4-5

Figure 4-3: Index File Contents

• T1/T2/T3/T4: The time-based calculation markers between chunk requests required to

4-6 IQDialogue ASM 4.0 User’s Guide — SUG-DIAASM-007

4.3.2 Microsoft Smooth Streaming Traffic

Figure 4-4: Microsoft Smooth Streaming Analysis

The layout format is:

IQDialogue ASM 4.0 User’s Guide — SUG-DIAASM-007 4-7

Figure 4-5: Index File Contents