> For the complete documentation index, see [llms.txt](https://docs.3q.video/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.3q.video/user-guide-new-ui/projects/livestreaming/e-cdn-for-livestreaming.md).
# E-CDN for Livestreaming
The **E-CDN for Livestreaming** feature allows livestreams to be distributed more efficiently within corporate networks. An eCDN, or Enterprise Content Delivery Network, helps reduce network load by distributing livestream data inside the company network instead of having every viewer request the full stream directly from the external CDN. This is especially useful for livestreams with many viewers in the same organization, such as townhalls, internal conferences, trainings, or corporate events.
3Q supports eCDN integrations for Livestreaming, including provider-based enterprise delivery solutions such as Hive or Kollective, depending on the account configuration.
From the livestream project settings, users can:
* Select an eCDN provider for a livestream project
* Enable optimized delivery for corporate networks
* Reduce bandwidth usage during large internal livestreams
* Improve livestream stability for high viewer numbers
* Use eCDN delivery together with the 3Q Player
***
### Connecting E-CDN Provider
To configure an E-CDN Provider:
1. Open **Accounts** in the main navigation.
2. Navigate to [Partner & Services](/user-guide-new-ui/account/partners-and-services.md).
3. Open Connect Partners.
4. Select E-CDN Provider and insert the credentials.
***
### Configuring eCDN for a Livestream Project
{% hint style="info" %}
To use a E-CDN with a livestream project, you need to connect the Provider of your choice with our platform. You can find more information [here](/user-guide-new-ui/account/partners-and-services.md).
{% endhint %}
The eCDN provider is configured in the livestream project settings.
To configure eCDN:
1. Open **Projects** in the main navigation.
2. Select the livestream project you want to configure.
3. Open the project **Settings**.
4. In the **General** tab, scroll to the **eCDN Provider** setting.
5. Select the configured eCDN provider.
6. Save the project settings.
After saving, the livestream project uses the selected eCDN provider for supported playback workflows.
***
### When to use a E-CDN
eCDN is recommended when many viewers access the same livestream from the same company network.
Without eCDN, each viewer may request the livestream individually from the CDN. In large organizations, this can create high bandwidth usage at internet gateways, firewalls, proxies, or corporate network connections.
With eCDN, livestream traffic can be distributed more efficiently inside the corporate network. This helps improve scalability and can reduce the load on the external network connection.
Typical use cases include:
* Company townhalls
* Internal executive broadcasts
* Employee livestreams
* Training sessions
* Corporate webinars
* Internal product launches
* Events with many viewers in offices or shared networks
***
### E-CDN Provider
The **E-CDN Provider** setting defines which enterprise delivery provider should be used for the livestream project.
The available providers depend on the account configuration and booked services.
Example providers may include:
* Hive eCDN
* Kollective eCDN
* Other configured enterprise CDN providers
If no eCDN provider is available in the project settings, the feature may not be enabled for the account or may require additional configuration.
***
### Preparing an eCDN Livestream
Before using eCDN for a production livestream, the configuration should be tested with the intended network environment.
A recommended preparation workflow is:
1. Configure the eCDN provider in the livestream project settings.
2. Embed or open the livestream with the intended player configuration.
3. Start a test livestream signal.
4. Test playback from the corporate network.
5. Confirm that the selected eCDN provider is active.
6. Test with multiple viewers or test clients if possible.
7. Review playback quality and network behavior.
8. Coordinate with the customer’s IT or network team if required.
Testing is especially important for large events because corporate firewalls, proxies, VPNs, and network segmentation can affect eCDN behavior.
***
### Working with Corporate IT
For enterprise livestreams, the customer’s IT or network team may need to be involved.
Depending on the selected eCDN provider and company environment, IT teams may need to review:
* Firewall rules
* Proxy behavior
* Browser support
* WebRTC availability
* Internal network routing
* VPN behavior
* Security policies
* eCDN provider requirements
The exact requirements depend on the selected eCDN provider.
***
### Difference between CDN and eCDN
A regular CDN distributes content through external delivery infrastructure. Viewers request the livestream from CDN servers that are optimized for scalable internet delivery.
An eCDN focuses on enterprise environments. It helps distribute the livestream inside the corporate network and reduces the amount of traffic that must pass through the company’s internet connection.
In many livestream workflows, CDN and eCDN work together:
* The CDN delivers the stream to the organization.
* The eCDN optimizes distribution inside the organization’s network.
* The 3Q player handles playback for the viewer.
***
### Notes
eCDN availability depends on the account configuration, booked modules, selected provider, and user permissions.
The eCDN provider must be configured before it can be selected in a livestream project.
For production events with many viewers, always test the eCDN setup in advance with the target network environment.
If playback issues occur in a corporate network, involve the customer’s IT or network team and verify the eCDN provider requirements.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.3q.video/user-guide-new-ui/projects/livestreaming/e-cdn-for-livestreaming.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
