> ## Documentation Index
> Fetch the complete documentation index at: https://docs.voxo.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Paging adapters

> Which paging adapters VOXO supports, and how to check an adapter when paging returns "service unavailable".

A paging adapter connects an overhead paging or intercom system to your VOXO phone service, so a call or page from a phone plays through speakers.

## Recommended adapter

* **Algo 8301** — the supported and recommended paging adapter. VOXO can order one for you, and it integrates with your VOXO service.

If you need a paging adapter or a replacement, the Algo 8301 is the supported choice. You can buy one and have it configured for your account.

## Adapters VOXO does not supply

VOXO does not stock or supply every paging adapter on the market. The **Snom PA1**, for example, is not provided by VOXO. If you already own a third-party adapter, it may still work, but support for it is limited and VOXO cannot order replacements for it.

<Tip>
  To check whether an adapter is one VOXO supplied, see whether it appears in your account's device list. An adapter that is not listed there is likely customer-owned third-party hardware.
</Tip>

## When paging shows "service unavailable"

A **"service unavailable"** message when you press the intercom or paging button often comes from the paging adapter rather than the phone. Check whether the adapter is online before troubleshooting the phone itself.

To set up or review where pages are sent, see [Paging Groups](/omnia/admin/paging-groups).

**Contact support** if a VOXO-supplied Algo 8301 shows offline or returns "service unavailable" after you confirm it has power and a network connection.

## Provision an overhead horn (Algo paging endpoint)

An overhead horn — such as an Algo paging speaker — is added to VOXO like any other device: create an extension, add the horn as a device, point it at VOXO's provisioning URL, then add it to a paging group. Because a horn has no screen, the provisioning step happens on the device itself, which is where most setups get stuck.

<Steps>
  <Step title="Create the extension and add the device">
    Create a new extension for the horn and add the horn as a device on it (model and MAC address), the same way you would any phone. See [Extensions](/omnia/admin/extensions) for the create-extension and add-a-device steps. A **Paging** extension type works well for a horn.
  </Step>

  <Step title="Point the horn at the VOXO provisioning URL">
    The horn pulls its configuration from VOXO's provisioning URL:

    ```text Provisioning URL theme={null}
    https://api.voxo.co/p
    ```

    Set this in the horn's own **Advanced → Auto Provisioning** menu, on the device itself. It is not in the horn's web interface, and it cannot be set from another phone.
  </Step>

  <Step title="Reach the menu on a screenless horn">
    Because the horn has no display, you reach its setup through its physical reset procedure. If the horn won't come online and you can't reach its menu:

    * Power-cycle the horn and watch its status LED.
    * On Algo units, briefly bridging the two reset terminals while the LED is double-flashing triggers a reset, returning the device to its default credentials (default password `algo`).
    * Confirm the horn has power and a working network connection — the correct VLAN or subnet, not a static IP on the wrong subnet — before provisioning.
  </Step>

  <Step title="Add the horn to a paging group">
    Once the horn is online, add it to the relevant [paging group](/omnia/admin/paging-groups) so it broadcasts when that group is paged.
  </Step>
</Steps>

<Note>
  If you can't physically reach the horn, or it isn't appearing on your network at all, that's a wiring or network step — contact support and we'll work through it with you.
</Note>