# Additional Service Modules

The following section contains details that are optional or inessential to a standard Zoom Node deployment.

### <mark style="color:blue;">Hybrid Live Stream Module</mark>

For Zoom Events customers, as well as developers who would like to unidirectionally broadcast audio and video from a webinar or meeting to a large number of receivers, Zoom offers the Live Stream Service LSS. LSS is an Enterprise Content Delivery Network (eCDN) streaming solution which allows near-real-time streaming for Zoom Events, as well as the ability to be embedded in custom solutions that utilize the Zoom Video SDK.

This feature is typically delivered via the Zoom cloud, allowing for wide distribution of the unidirectional media stream to users located anywhere in the world.

The hybrid version of LSS allows for the media distribution function inside the corporate network, saving significant internet or WAN bandwidth, depending on the deployment location.

#### Solution Details

Zoom Live Stream Service consists of two components, the cloud-based Live Stream Zone Controller (LSZC) and the Live Streaming Gateway (LSGW), which is also deployed in Zoom’s cloud. It can also be deployed to a customer network using Zoom Node.

The LSZC directs user streaming requests to the best LSGW according to the receiver’s network location. As the number of streaming users increases, the LSZC will invoke additional LSGWs as needed. This is all transparent to users, and is handled automatically by the Zoom cloud.

#### Hybrid Deployment

The Hybrid Live Stream Module extends the Live Stream Gateway service for on premises scenarios, allowing for functionality like delivering the media stream directly to internal networks. This reduces latency significantly, as well as lessens internet bandwidth and firewall requirements.

![](/files/63be342f406864fbf84e0783e13148dc89fe0957)

The cloud-based Live Streaming Zone Controller manages all Live Streaming Gateways whether the LSGWs are cloud-native or deployed in the customer datacenter on Zoom Node. User connections to these gateways are managed by the LSGW, which directs clients to the most appropriate resource, depending on their location. If they are inside the network they will connect to a Hybrid LSGW, and if they are outside the network they will connect to a cloud LSGW.

#### Node Requirements

The Hybrid LSS module is deployed as the only module on the Zoom Node, rather than being one of four modules deployed on the Node. The LSS service can be assigned its own IP address, or it can share an IP address with the Node management IP if you want to use a single IP address for the VM and service.

### <mark style="color:blue;">Web Application Gateway</mark>

Zoom offers a web-based Zoom Workplace Application (ZWA) for modern web browsers, which serves as an alternative installation for the standard Zoom Workplace application.

The Hybrid Web Application Gateway (WAG) allows the Zoom web application to join **Private Mode meetings**. These are a unique meeting type that runs locally on your Meetings Hybrid infrastructure. Local hosting keeps any media shared and created by users during the private meeting within your network.

{% hint style="info" %}
**The Hybrid Web Access Gateway is not used for** **hybrid mode meetings**. Users joining a hybrid meeting via web browser will use web gateways through the Zoom cloud.
{% endhint %}

The Hybrid WAG allows 200 concurrent users per service deployed on Zoom Node. It can be run concurrently with other Meetings Hybrid services.

See the [IP Address Planning Matrix](/advanced-enterprise-services/zoom-node/zoom-node-deployment-field-guide/zoom-node-infrastructure-prerequisites.md#ip-address-planning-matrix) for prerequisite details.

#### Installing the Web Access Controller Proxy and Web Access Gateway

To install both modules:

1. Log in to the Zoom admin web portal.
2. Browse to the **Zoom Node management** section.
3. Click **Services** and then the **Nodes** tab from the menu in the upper-right corner of the screen.
4. The defined Nodes list appears.
   1. Look for the name of the Zoom Node you either deployed for the Real-Time Web Gateway (RWG), or an existing Node with sufficient capacity, an available slot, and an IP address.

      <figure><img src="/files/3bbc4e7dbe85f0a5dd171629b637940184cff002" alt=""><figcaption></figcaption></figure>
5. Click the **Web Access Zones** tab above the list Nodes.
6. Click the white **+ Add Zone** button below the blue **Add Nodes** button to define a Web Access Zone.
   1. Adding a new Web Access Zone determines the Zoom Data Center that your Hybrid Web Access components will communicate with.
7. Name the new Zone.
8. Click the **Zoom Data Center** drop down and select the Zoom Data Center closest to the location where you are deploying services.
9. Click **Confirm**.

![](/files/e684907af84a286bbdaa5dd7cc4465d19b0a3e9c)

10. Click **back** on the **Services** menu to see a list of installed services.

![](/files/35fb78876133b774c5fc49a58e9b86f9e6e757eb)

Now you must install the **Web Access Controller Proxy** and the **Web Access Gateway**.

The Web Access Controller Proxy provides communication for browsers during the meeting join process, while the Web Access Gateway acts as the media gateway.

#### Installing the Web Access Controller Proxy

To add the Web Access Controller Proxy:

1. Click **Add Services**.
2. Under the **Web Access** heading, click the **Web Access Controller Proxy** box.

   <figure><img src="/files/5948ef239f2342846dcd8b5c3a7df741dd9c8d78" alt="" width="375"><figcaption></figcaption></figure>
3. The following window will open:

![](/files/d25474ad82dbce030db4e685960573dcebf754fc)

4. Under the **Install on a node** option, specify the Node where you will deploy Web Access services.
5. Under the **Web Access Zone** drop down list, click the Web Access Zone you previously defined.
6. Under the **Internal IP** text box, enter the address of an available IP address from the Node.

{% hint style="info" %}
If the Node lacks sufficient assigned IP addresses, add more via the local TUI or GUI. To do this, access the Node's **Local Admin Portal** by clicking the ellipsis next to the listed Node, then authenticate to add more addresses.
{% endhint %}

7. Click **Add** to install the Web Access Controller Proxy.

The installation process will take approximately up to five (5) minutes. The service will change states as it gets ready to boot, from Downloading > Pending > Stopped > Start.

#### Installing the Web Access Gateway

To install the Web Access Gateway:

1. Click **Add Services**.
2. Under the **Web Access** heading, click the **Web Access Gateway** box.

![](/files/f78aa6ab4d6d053c9816c1383714a1ffe67fc43b)

3. The following window will open:

![](/files/254a56d7c4fe931c0c5cf51b8bc30c17d93d56d7)

4. Under the **Install on a node** option, specify the Node where you will deploy Web Access services.
5. Under the **Web Access Zone** drop-down list, click the Web Access Zone you previously defined.
6. Under the **Internal IP** text box, enter the address of an available IP address from the Node.
7. Click **Add**to install the Web Access Controller Proxy.

#### Configuration

Now that the two modules are installed, the rest of the configuration can be performed.

Determine the types of users that you would like to allow joining meetings via the Zoom Web App

This can be done at the entire account level, the group level, or for an individual user. For testing, Zoom suggests first enabling this feature for a test group.

To enable the feature for the entire account, log in to the Zoom admin portal and navigate to **Account Management > Account Settings**.

Select the **Meeting** tab from the top menu. Search "hybrid" in the search dialogue, or scroll down the page and find the **Hybrid services…** section.

![](/files/9f238b920427fa9481da4f627e06230fa55eba49)

Click the check box for **Allow Zoom Web Client to join private meetings**. This will allow users to join Private Mode Zoom Meetings via a web browser.

{% hint style="info" %}
These same instructions apply to enable a group of users or an individual user. Just navigate to either option you'd like to enable and select the same check box for **Allow Zoom Web Client to join private meetings**.
{% endhint %}

#### Testing the Deployment

Now that the components are installed and configured, perform a test for validation.

1. From a host with the feature enabled, schedule a Private Mode meeting.
2. Join the meeting using the Zoom Workplace app client to verify it is a Private Mode meeting. Click the **green meeting shield** to view the Private Mode indicator.
3. Copy the **meeting join URL** from the meeting invite.
4. Paste the copied URL in a new Private or Incognito browser window. Hit **enter**.
5. If the browser prompts you to open the link with the Zoom Workplace app, do not continue. Close the prompt.
6. If the browser prompts you to download the Zoom Workplace app, cancel the download.
7. After a few seconds, two buttons will appear in the browser.
8. Click the **Join from your browser** button.
   1. Do not click the blue button. That will attempt to launch the full Zoom Workplace app.


---

# Agent Instructions: 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:

```
GET https://library.zoom.com/advanced-enterprise-services/zoom-node/zoom-node-deployment-field-guide/additional-service-modules.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
