Kaltura eCDN
- Kaltura eCDN Information Guide
- Enterprise Content Delivery Network eCDN Overview
- Configure network and firewall requirements for Kaltura Edge Server
- Chrome / Edge Local Network Access (LNA) and Kaltura eCDN
- The Kaltura eCDN Monitoring Portal
- eCDN Stress Test Application
- Kaltura Supported CDN (Content Delivery Networks) and Streaming Servers
- Kaltura eCDN Release Notes
- When is eCDN used?
- What is Kaltura Edge Server (KES)?
- What are the standard KES system requirements?
- How does pre-positioning work?
- How does end-user detection work?
- What URLs does an end-user access when playing back?
- What URLs does the KES access?
- What player uiconf modifications are required to playback from KES?
- When and where are SSL certificates required?
- How does KES failover?
- How does the Kaltura Edge Server scale?
- Is there a limit to the number of rules per KES, or in total?
- Can the KES operate without an Internet connection?
- Can the KES do tokenization or AES-128 encryption?
- Can the KES serve from remote storage?
- How do I view the status or health of the KES node?
- How do I add/modify/delete IP addresses for the end-user mapping function?
- Who is responsible for updating the operating system on the KES node?
- How will KES upgrades or patches be performed?
- How can I tell if eCDN is working?
- How does eCDN work with WAN optimizers like Bluecoat and Riverbed?
- What end-user information is passed to Kaltura when using eCDN?