# (Optional) BYOC Number Management

This section provides step-by-step instructions to upload, associate, and assign BYOC numbers to your Zoom account and users. This section also includes instructions for configuring call forwarding logic, assigning an ELIN to a site, configuring routing rules, and how to enable call forwarding during a survivability event. These processes are not required for customers that do not plan to integrate their ZPLS module with an SBC. However, customers that *do* plan on integrating are encouraged to complete this process as soon as possible, prior to any outage occurring.

### Upload BYOC Number List to the Cloud

Customers planning to use call forwarding or an emergency location identification number (ELIN) must upload a list of BYOC numbers to the web portal. The number of BYOC numbers to add should be equal to the maximum number of users and ELINs that will be supported during a survivability event.

For example, if a site has 100 users, 100 BYOC extensions may be required. Further, if the site utilizes ELIN, an additional BYOC number may be required, totaling 101 numbers. However, fewer numbers may suffice if all users will not be assigned a BYOC number. To add BYOC numbers to the web portal, perform the following steps:

1. Sign into the Zoom web portal.
2. Under the **Phone System Management** sub-menu, select **Phone Numbers**.
3. Select the **BYOC** tab.

   <div data-with-frame="true"><figure><img src="/files/497f8406a35d5e459659758955830cbddb2ab55c" alt=""><figcaption></figcaption></figure></div>
4. Add BYOC numbers manually with the **Add** button, or via CSV upload through the **Import** button (CSV template provided).

{% hint style="info" %}
When adding BYOC numbers, be sure to add the numbers to the specific site they will be assigned to for use.
{% endhint %}

### Associate BYOC Numbers with Users

After your company’s BYOC numbers are uploaded, they must be assigned to specific users for use during routine operation. This defines the logic to route calls made to a BYOC number to a Zoom user before or after a survivability event. To assign BYOC numbers to a user, perform the following steps:

1. Sign into the Zoom web portal.
2. Under the **Phone System Management** sub-menu, select **Phone Numbers**.
3. Select the **Unassigned** tab.
4. Filter the phone numbers by selecting the **Site** they are assigned to.
5. Locate the number to assign, and click **Assign to** and a pop-up will appear.

   <div data-with-frame="true"><figure><img src="/files/76876c2bc399e488e813ddd96a2afeb79ff3a859" alt=""><figcaption></figcaption></figure></div>
6. Within the pop-up, assign the BYOC number to a user and click **OK**.
7. Repeat as necessary.

### Configure Survivability Call Forwarding Logic

{% hint style="info" %}
Unlike the previous section, which associates a BYOC number with a Zoom user, this section specifically defines call forwarding logic *during a survivability event*. Call forwarding logic applied here does not affect routine operations or behavior.
{% endhint %}

After BYOC numbers have been configured to users and the account, survivability call forwarding logic should be defined prior to any potential survivability event. To configure survivability call forwarding logic, perform the following steps:

1. Sign into the Zoom web portal.
2. Under the **Phone System Management** sub-menu, select **Company Info**.
3. **Select the site name** from the list (or click **Account Settings** if a single-site configuration).
4. Select the site’s **Settings** tab.
5. On the following screen, locate the **Zoom Node** subsection, and the setting for **Call Forwarding Local Survivability**. Click **Manage** to load a new page.

   <div data-with-frame="true"><figure><img src="/files/f9fd997b3def1abd2f8691a95d8c3a1e83b828a4" alt=""><figcaption></figcaption></figure></div>
6. On the following page, click the blue **Add** button to begin defining call forwarding rules.
7. **Source Numbers** are the numbers being forwarded, like a user’s Zoom Phone-registered number. These numbers must be assigned prior to configuring call forwarding.
8. **Destination Numbers** are the BYOC numbers source numbers are forwarded to.
9. [Remember](#_uqxkanvtah5p) that multiple source numbers can direct to the same destination number, but one source number cannot direct to multiple destination numbers.

<div data-with-frame="true"><img src="/files/b70e729ba2051ad8cd21af65c303b9ae81100761" alt="" width="563"></div>

10. Click **Save** when complete and repeat as necessary for each user or phone number.

{% hint style="info" %}
Call Forwarding logic is **disabled** by default, and must be manually enabled from the web portal during a survivability event. For more information, refer to the section on [enabling call forwarding](#_wobxo9fvuzgk).
{% endhint %}

### Configure ELIN

Each site supports a single [emergency location identification number](#_wep0hh3heran) (ELIN) to provide location information to emergency responders during a survivability event. To configure an ELIN for a site, perform the following steps:

1. Sign into the Zoom web portal.
2. Under the **Phone System Management** sub-menu, select **Company Info**.
3. **Select the site name** from the list (or click **Account Settings** if a single-site configuration).
4. Select the site’s **Settings** tab.
5. On the following screen, locate the **Zoom Node** subsection, and the setting for **Emergency Location Identification Number (ELIN)**. Click **Add Number** to populate the number selection field.

<div data-with-frame="true"><img src="/files/a79999a4f5abb146d1665a5ade0d9305e4c8bde2" alt="" width="563"></div>

6. Within the pulldown menu, select the BYOC number that will be used as the outgoing calling number to emergency services during a survivability event. If the number is not currently listed on the account, upload it through the [BYOC number upload process](#_aezu04x8z043).
7. An administrator can verify the ELIN assignment to the survivability module through the **Phone Numbers** page listed under the **Phone System Management** sub-menu. ELIN numbers will display as assigned to **Local Survivability**.

   <div data-with-frame="true"><figure><img src="/files/c7ae39e1ba720079f944152f10057bf542c1d740" alt=""><figcaption></figcaption></figure></div>

### Routing Rules (Optional)

Customers that require routing rules (e.g., dialing 9 to enable outbound dialing) can preserve these during a survivability event for a consistent end-user experience; however, when routing rules are enabled, the default routing path (SIP group) is ignored, and number translations are preserved. To enable ro uting rules during a survivability event, perform the following steps:

{% hint style="info" %}
Routing Rules defined at the Site level can be preserved by ZPLS. Rules defined at the account level will not be preserved.
{% endhint %}

1. Sign into the Zoom web portal.
2. Under the **Phone System Management** sub-menu, select **Company Info**.
3. **Select the site name** from the list (or click **Account Settings** if a single-site configuration).
4. Select the site’s **Settings** tab.

   <div data-with-frame="true"><figure><img src="/files/7cb443862331740d905307921847e3d942ff7f3d" alt="" width="563"><figcaption></figcaption></figure></div>
5. Locate the **Zoom Node** subsection, and the setting for **Local Survivability**. Mark the checkbox to **Enable Routing Rules**.

   <div data-with-frame="true"><figure><img src="/files/fa3a7d4e8ad6cd09ad58369de5be656e3a8eac18" alt=""><figcaption></figcaption></figure></div>
6. Click **Save** when complete.

{% hint style="danger" %}
The ZPLS module must be restarted for this change to take immediate effect.
{% endhint %}


---

# 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/zoom-workplace/zoom-phone/zoom-phone-local-survivability-field-guide/optional-tasks/optional-byoc-number-management.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.