TechNote – AltitudeCDN™ Multicast+ Integration with

TechNote – AltitudeCDN™ Multicast+
Integration with TalkPoint
Version 1.0
AltitudeCDNTM Multicast+ is a patented (US Pat. 9,516,390) solution that brings multicast support to any live
video deployment that uses HTTP Live Streaming (HLS) or DASH. Multicast+ integrates with the TalkPoint video
event management service, providing TalkPoint customers with a solution that efficiently delivers high-quality
Live (or Video On Demand (VOD) published as “Live”) streaming across the enterprise, without overloading or
degrading network resources.
This guide describes how to provision and deploy a TalkPoint video event that uses AltitudeCDN Multicast+.
Contents
Contents .................................................................................................................................................................1
Introduction ............................................................................................................................................................ 2
Requirements ......................................................................................................................................................... 2
Solution Summary .................................................................................................................................................. 3
TalkPoint Multicast+ Configuration ........................................................................................................................ 4
Diagnostic Usage Statistics ..................................................................................................................................... 4
Addendum – Screen Shots ..................................................................................................................................... 5
1
© 2017 · Ramp Holdings Inc. · All rights reserved.
Introduction
For Live (or Video On Demand (VOD) published as “Live”) events, large numbers of viewers each attempt to
connect separately to external internet content delivery servers, creating a high demand on network resources
that can lead to poor video quality, or even service denial for event viewers and other network clients.
To avoid these issues, Ramp and TalkPoint have jointly developed a solution where TalkPoint customers can
integrate AltitudeCDN Multicast+ into their video content management and delivery environment. By using
Multicast+ Senders and Receivers, a video event is presented as a single multicast stream that is shared
simultaneously by multiple viewers, allowing an event deployment to scale to large audiences, while conserving
network bandwidth.
The TalkPoint event management interface supports parameters to provision Multicast+ events. Typically,
TalkPoint configures these parameters for a customer as a managed service, however, the Multicast+-related
management interface can be exposed for customer access. The on-premise Multicast+ Sender application must
be configured separately to match the corresponding TalkPoint event, and the Multicast+ Receiver application
must be pre-installed for all viewers. The TalkPoint video player and portal page is enabled to detect and receive
Multicast+ streams if present, or fall back to unicast transmission if none is found.
Requirements
To use Multicast+ with TalkPoint, the following requirements exist:
Item
Multicast+ Sender
Multicast+ Receivers
Recommendation
• Multicast+ Sender v1.6.5 or later – The Sender must be installed and running
on an on-premise Windows or CentOS platform, positioned within the
customer network so multicast traffic can reach the audience. For more
information, see the AltitudeCDN Multicast+ Deployment Guide.
• Multicast+ Windows Service Receiver 1.0.47 or later.
OR
• Multicast+ Windows Add-On Receiver 1.1.25 or later.
OR
• Multicast+ Mac Receiver 1.6.5 or later.
• The receivers must be installed on each customer platform prior to the event.
For more information, see the AltitudeCDN Multicast+ Deployment Guide.
2
© 2017 · Ramp Holdings Inc. · All rights reserved.
Solution Summary
Event viewers initiate playing the video event normally by accessing the TalkPoint Player page. The TalkPoint
Player then searches for and detects a local Multicast+ Receiver that can receive the pre-configured multicast
streams. If no Receiver or multicast stream is available, the TalkPoint Player falls back to unicast transmission.
Note: other Multicast+ aware players may also be used
At the Multicast+ Sender, a management URI provided for the TalkPoint event, supplies the Sender agent with
dynamic configuration that determines which multicast addresses and ports to use for each stream. Any stream
switching initiated by the presenter is reflected automatically on the viewer’s player.
Note: For information on the Multicast+ Sender configuration, see the AltitudeCDN Multicast+ Deployment
Guide.
To use Multicast+ with TalkPoint, execute the following workflow:
1. (Typically configured by TalkPoint) Create a matching Multicast+ key pair, then provision:
• The player landing page for the specific customer.
• The corresponding senderKeyStore in the customer’s on-premise senderAgent.properties file.
2. Configure each TalkPoint video event stream (for example, Prelive, Primary, and Backup) with a unique
multicast address and UDP port pair (for example, 239.1.1.1:3500).
Note: Multicast address/port pairs for events require unique multicast addresses to prevent overlap
issues with other events.
3. Configure the URI for the local Multicast+ Receiver (for example http://talkpoint.multicast-receiveraltitudecdn.net:12345, or https://talkpoint.multicast-receiver-altitudecdn.net:123450):
• HTTPS is recommended to match the scheme of the player portal.
• talkpoint.multicast-receiver-altitudecdn.net resolves to 127.0.0.1 in the public DNS.
4. TalkPoint provides a source URI that can be added to the senderAgent.properties file. (for example,
vdmsagent.managementUri=https://event.webcasts.com/viewer/ramppullpaths.jsp?ei=1143852&sh0=d
f909e2f4afd61de52eb8e89f3e886c7249c2294)
• This source URI provides dynamic JSON-based configuration to the Multicast+ Sender agent to
support stream switching.
3
© 2017 · Ramp Holdings Inc. · All rights reserved.
TalkPoint Multicast+ Configuration
This section summarizes the configurations steps for using Multicast+ with TalkPoint (for more information on
the TalkPoint interface, see TalkPoint documentation – relevant screen shots are provided in the Addendum):
1. Create a new Event and set the appropriate values for the Event Name, Event Type, etc.
• Only Live events are supported for Multicast+ integration
2. Within the Player and Branding Options:
• For Media Options, select:
• Stream Type: HTML5
• Multicast Type: RAMP
3. Set the appropriate values for the Slides, Audience Questions, and Audience Phone Bridge settings.
4. Within Event Summary, display the Ramp Setup panel:
• Define the Prelive, Primary, and Backup stream multicast IPv4 and ports used for the event.
These addresses must be coordinated with the customer network IT to ensure that no collision
or overlap occurs with other events or network traffic.
• A default DNS name (talkpoint.multicast-receiver-altitudecdn.net => 127.0.0.1) is used to
identify the local Multicast+ Receiver Host. This can be used for all deployments.
A valid PKI certificate for this hostname is embedded in the Multicast+ Receiver to allow HTTPS
delivery of video content (for example: https://talkpoint.multicast-receiveraltitudecdn.net:12350).
Note: Ensure that the Receiver Host URL port matches the scheme used (for example, HTTP
uses 12345, and HTTPS uses 12350).
•
Copy the Sender Source URL to the Multicast+ Sender configuration. For example:
vdmsagent.managementUri=https://event.webcasts.com/viewer/ramppullpaths.jsp?ei=114385
2&sh0=df909e2f4afd61de52eb8e89fe886c7249c2294
Diagnostic Usage Statistics
As of this writing, Multicast+ Sender diagnostics can be enabled by running an additional sender instance on the
same platform as the Multicast+ senderAgent using the following minimal configuration:
# port both to receive data and serve http
diagnostics.port=18000
diagnostics.regionsFile=regions.json
diagnostics.password=abc123
diagnostics.noAuth
The diagnostic sender may be started as follows:
# nohup ./sender.sh diagnostics.properties > /dev/null 2>&1 &
4
© 2017 · Ramp Holdings Inc. · All rights reserved.
Addendum – Screen Shots
5
© 2017 · Ramp Holdings Inc. · All rights reserved.
6
© 2017 · Ramp Holdings Inc. · All rights reserved.
Download PDF