Paging is one of the last analog holdouts in modern voice deployments. Schools, warehouses, manufacturing floors, retail locations, and healthcare facilities still rely on overhead speakers fed by 70-volt amplifiers that were installed long before anyone heard the term VoIP. When an MSP takes over a customer's phone system, the question almost always comes up: can we keep the paging system?
The answer is yes. The path runs through a SIP paging adapter. The two dominant products in the market are the Algo 8301 and the Bogen UTI1, and wiring either of them correctly is the difference between a clean five-minute cutover and a four-hour callback for hum, dropped audio, or DTMF that won't pass through to the zone controller. This guide covers the actual wiring, the configuration, and the failure modes, with the assumption that you're deploying behind a modern hosted PBX rather than a legacy on-prem switch.
Quick Answer
Why SIP Paging Integration Still Matters in 2026
Despite the broad shift to cloud voice, analog paging infrastructure is far from dead. The U.S. has approximately 99,200 public K-12 schools, and a substantial portion of those buildings still rely on 70V/25V distributed audio systems for bells, intercom, and emergency announcements. The installed base in warehousing, healthcare, manufacturing, and retail is similarly massive. Replacing every speaker and amplifier in a 50,000 square foot facility is not a realistic project scope for most customers -- and it should not need to be.
The FCC is actively pushing the industry toward all-IP networks. Its technology transitions guidance requires that public safety and life-safety communications -- which include premise paging in many deployments -- continue to function across the TDM-to-IP migration. That regulatory reality, combined with the scale of installed analog infrastructure, means SIP paging adapter work is a recurring service opportunity that sits directly alongside every hosted voice migration MSPs already close.
Replacing the PBX is the easy part. Migrating the paging system without touching the speakers or the amp is the value-add that keeps customers from balking at the cutover. Understanding how to do it cleanly separates MSPs who can scope the full project from those who have to subcontract it out. For a broader look at the hardware landscape, the VoIP paging system equipment guide covers Algo, Valcom, CyberData, Viking, and Grandstream in more depth.
Every hosted VoIP migration that touches a customer with overhead speakers is a paging adapter opportunity. The hardware cost is low, the labor is billable, and keeping the existing amp and speakers reduces the customer's total project cost -- which makes the PBX cutover an easier sell.
How SIP Paging Adapters Actually Work
A SIP paging adapter is a network appliance that registers to a VoIP PBX as a SIP endpoint and converts the incoming RTP audio stream into either a balanced analog line output (Algo 8301) or a relay closure plus line-level audio (Bogen UTI1 in conjunction with an ATA, or devices like the Algo 8373). When a user dials the paging extension, the adapter auto-answers the SIP INVITE, decodes the RTP stream, and pushes audio to the connected amplifier.
Before you start pulling cable, there are four technical parameters that determine whether the installation works cleanly or becomes a callback:
- Line output impedance: Most legacy paging amplifiers expect a high-impedance dry audio input between 600 ohm and 10 kOhm. The Algo 8301 is configurable across this range from the web UI.
- Output level: Standard reference is 0 dBm at 600 ohm (0.775 Vrms). Going hotter than this overdrives the amplifier and produces distortion or compression.
- Activation signaling: Some amps need a dry contact closure to wake up or trigger a relay before they pass audio. Both the 8301 and UTI1 provide this.
- DTMF passthrough: If the customer has a multi-zone controller behind the amp -- common in schools -- DTMF tones from the caller's keypad must reach it in-band, not just as RFC 2833 packets.
One distinction worth clarifying before any customer scoping call: a SIP paging adapter converts SIP audio for an external analog amplifier and the existing speakers wired to it. A SIP speaker is an all-in-one IP endpoint with the amplifier and driver built in. Adapters preserve legacy infrastructure. SIP speakers are the path when starting from scratch.
Algo 8301 vs Bogen UTI1: What Each One Does
These two devices solve adjacent problems and are sometimes confused on initial scoping calls. The simplest way to think about them: the Algo 8301 speaks SIP natively and outputs analog. The Bogen UTI1 speaks analog telephone signaling and needs an ATA in front of it to participate in a SIP environment.
The Algo 8301 is a fully compliant third-party SIP endpoint that registers to any hosted or premise-based PBX. Per the 8301 User Guide, it outputs a balanced, isolated line-level audio signal designed to drive a single amplifier with an input impedance between 600 ohm and 10 kOhm. It also includes an NTP-synchronized scheduler for bells and tones, 1 GB of internal audio storage, and PoE 802.3af power -- no wall wart, no separate power run.
The Bogen UTI1 is a universal telephone interface that speaks loop-start, ground-start, station access, and page-port contact closure activation. Per the Bogen UTI1 manual, it does not speak SIP. To use a UTI1 in a SIP environment, you need an ATA or FXS port in front of it. This is not a limitation -- it is often the correct deployment choice when a customer already has ATA infrastructure in place or has a complex multi-input scenario where the UTI1's interface flexibility is genuinely useful.
| Feature | Algo 8301 | Bogen UTI1 |
|---|---|---|
| Native SIP | Yes | No -- requires ATA or FXS port |
| Power | PoE 802.3af | External 24V DC (built-in supply) |
| Multicast | Yes (send and receive) | No |
| Built-in scheduler | Yes (NTP-synchronized) | No |
| Internal audio storage | 1 GB | None |
| Background music input | Yes | Yes (with variable muting) |
| Contact closure output | Yes (dry) | Yes (AUX relay, programmable) |
| Wideband audio (G.722) | Yes | Limited by ATA codec |
| Typical use case | New SIP cutover with existing amp | Legacy analog environment with existing ATA pool |
Scroll to see full table on mobile
Use the Algo 8301 for any greenfield SIP cutover where you want a clean native IP endpoint and the customer wants scheduled bells or tones. Use the Bogen UTI1 when you already have an ATA pool deployed, the customer has a complex multi-input scenario, or the budget for a new endpoint is genuinely not there. Both paths work -- the choice is about what is already in the rack.
Wiring an Algo 8301 to a Bogen Amplifier
This is the most common modern install. The 8301 connects to a Bogen TPU, C-series, or GS-series amplifier via a four-wire line-out connection using either the mini-XLR connector or the pluggable terminal block. Most installers use the terminal block for permanent installs. The wiring values below come from Algo's Paging Adapter Amplifier Integration Guide.
Physical Wiring Steps
- Mount the 8301 within cable distance of the amplifier. PoE feeds power and data over a single Cat5e/Cat6 run back to the switch -- no wall wart, no conduit run for power.
- Connect the line output from the 8301's terminal block to the amplifier's telephone or auxiliary input. The balanced output uses a wire pair and is polarity-independent.
- For Bogen TPU-35/60/100/250: wire the 8301 line-out to the amp's TEL input terminals. No additional switch positions required.
- For Bogen GS35/GS60/GS100/GS150/GS250: set the amplifier's input switch to the TEL position before connecting. The GS-series expects a high-impedance balanced input on the telephone terminals.
- For Bogen C35/C60/C100: connect to the telephone input terminals. The C-series is unbalanced on the AUX input, so use the telephone pair instead to avoid a ground loop.
- If a zone controller is present (Bogen PCM2000, Bogen Multicom 2000, or a third-party zone controller): wire the 8301 line-out to the UTI1's page port terminals. Set the UTI1 horizontal slide switch to CONT and the vertical slide switch to Page Port to pass audio plus contact closure activation.
- If contact closure is required to wake the amplifier: run a separate wire pair from the 8301's relay output to the amp's contact closure trigger input. The 8301 closes the relay automatically on every active SIP call.
Algo 8301 Web Configuration
After mounting and wiring, access the 8301's IP address in a browser. The default password is algo. Configure the following settings before testing:
- Basic Settings > Features > Line Out Analog Output Level: Set to
0dBm 600 ohm (0.775 Vrms)for all Bogen C-series, GS-series, TPU, and PCM2000 amplifiers. This is the correct starting point for almost every Bogen amp -- do not rely on the default. - Basic Settings > Features > Generate In-Band DTMF Tones: Enable this if the amplifier has a zone controller that listens for DTMF. Leaving it off is one of the most common reasons zone selection stops working after a SIP cutover.
- Basic Settings > SIP: Enter the SIP server domain, the paging extension number, the Authentication ID, and the SIP password from your hosted PBX platform.
- Advanced Settings > Advanced Audio: Verify the preferred codec list starts with G.711 mu-law (PCMU), with G.722 as a secondary option only.
- Save and reboot the 8301 so the SIP registration takes effect.
Wiring a Bogen UTI1 to a SIP ATA
If the customer already has a Grandstream HT-series ATA, a Cisco SPA112, or an AudioCodes MP-1xx in place, keeping the UTI1 and feeding it from the ATA's FXS port is often the right call. The UTI1 stays in place, the amplifier and speakers stay in place, and the total parts cost for the ATA side is well under $150. This is the scenario covered in detail in the Bogen UTI1 installation manual.
Physical Wiring Steps
- Set the UTI1's interface type slide switches. For station-access mode -- the most common config behind an ATA -- set the horizontal switch to STA and the vertical switch to PBX (per manual page 9). This makes the UTI1 behave like a telephone station that auto-answers when the FXS port rings it.
- Connect the ATA's FXS port to the UTI1's Trunk/Page Port RJ11 jack with a standard 4P4C or 6P4C modular cable.
- Wire the UTI1's Page and Music terminal block to the amplifier's telephone input. Polarity does not matter on the balanced output.
- Adjust the Page Level control on the UTI1 to roughly the 12 o'clock position as a starting point. Tune it during a live test page -- do not trust the factory default level.
- Enable the trunk disconnect feature in the UTI1 if you want it to auto-release after a VOX timeout (factory default: 6 seconds of silence). This prevents stuck pages when a phone hangs up improperly.
ATA Configuration
On the ATA's FXS line profile, four settings determine whether the paging path works reliably:
- Disable echo cancellation. It causes audible artifacts on one-way paging audio -- the kind that sounds like underwater garbling on the speakers.
- Set the codec preference to G.711 mu-law only. Paging does not benefit from compressed codecs, and they break in-band DTMF delivery.
- Set DTMF mode to In-Band (Audio), not RFC 2833. Many zone controllers will not accept out-of-band DTMF regardless of what the SIP RFC says.
- Leave hook-flash timing at default. Paging will never use it, but a non-default value can cause unexpected behavior on the UTI1's relay logic.
SIP Registration and PBX Configuration
On the PBX side, treat the adapter exactly like a generic SIP extension with auto-answer behavior. The minimum requirements are the same regardless of whether you're registering an Algo 8301 directly or an ATA fronting a Bogen UTI1 to the hosted PBX platform.
- Provision a dedicated extension for paging. Do not share an extension with a desk phone. Both Algo and Bogen documentation assume the adapter owns the extension number outright.
- Configure SIP credentials in the adapter: SIP domain, extension number, authentication ID, and password.
- Mark the extension as auto-answer or paging endpoint in the platform portal. On Viirtue and most hosted PBX platforms, this is a straightforward setting that controls how Call Forward, Do Not Disturb, and voicemail behave for the endpoint.
- Set up a paging feature code or hunt group if you want multiple users to reach the paging system without memorizing an extension. A typical mapping is *99 for All Call or a custom code configured at the tenant level.
- For multi-zone paging, use multicast: configure the 8301 to receive a specific multicast address, and configure the PBX to send page audio to that multicast group. This lets you drive multiple Algo endpoints from a single SIP call without putting per-endpoint RTP load on the PBX.
One thing worth understanding about multicast delivery: it is handled entirely at the network layer, which means IGMP snooping on the switch matters. If a second Algo endpoint is not receiving the page audio even though it is registered, check the VLAN configuration before touching anything on the PBX side. The most common culprit is IGMP snooping blocking multicast traffic without an IGMP querier configured on the segment.
Paging extension configuration is a five-minute task on a well-designed hosted platform. The network layer -- PoE, VLAN, IGMP -- is where most installs actually get stuck. Scope the network requirements during discovery, not during the cutover call.
Troubleshooting Matrix
The symptoms below cover the majority of field failures reported across Algo 8301 and Bogen UTI1 installs. Work through this in order rather than jumping to factory resets.
| Symptom | Likely Cause | Diagnostic / Fix |
|---|---|---|
| Page connects but no audio at speakers | Amp waiting for contact closure to activate | Enable relay on the 8301 web UI; wire contact closure pair to amp trigger input |
| Loud hum or buzz on speakers | Ground loop between adapter and amp | Use balanced output only; verify isolated line-out is enabled; check for shared chassis ground between devices |
| Audio is distorted or clipping | Line output level too hot | Set 8301 output to 0dBm 600 ohm; reduce UTI1 Page Level control counterclockwise |
| Audio is faint even at max amp volume | Output impedance mismatch | Match 8301 line-out impedance setting to amp input spec (600 ohm vs 10 kOhm) |
| Zone controller does not respond to DTMF | RFC 2833 only; in-band DTMF not enabled | Enable "Generate In-Band DTMF Tones" under Advanced Audio on the 8301 web UI |
| SIP registration fails | NAT, credential mismatch, or SBC misroute | Check Status tab on 8301 for registration state; verify auth ID matches PBX exactly; check NAT traversal settings |
| Page rings but does not auto-answer | Extension not configured for auto-answer | On the hosted PBX, mark the extension as a paging endpoint or set auto-answer to immediate in the portal |
| Multicast not reaching second adapter | IGMP snooping blocking traffic on switch | Enable IGMP querier on the VLAN or configure a static multicast address allowed by the switch ACL |
| Audio cuts off after 6 seconds (UTI1) | UTI1 VOX timer expired | Increase VOX timeout via Feature Code 51 on the UTI1, or disable trunk disconnect entirely |
| Choppy or robotic audio over speakers | Codec transcoding mid-path | Force G.711 mu-law on the paging extension and ATA FXS profile; remove G.722 from the priority list |
Scroll to see full table on mobile
Deployment Scenarios
The wiring steps above cover the technical execution. These three scenarios show how those steps translate into real project scopes -- with the variables that actually matter for quoting and scheduling.
Scenario 1: K-12 Elementary School, 35 Classrooms
A school with an existing Bogen TPU-250 amplifier driving 70V ceiling speakers across 35 rooms, plus a daily bell schedule. Deploy a single Algo 8301 wired to the TPU TEL input. Use the 8301's built-in NTP scheduler to handle school bell tones -- no longer dependent on a mechanical bell clock or a separate scheduling system. Register the 8301 to the hosted PBX as a dedicated extension, and provide front-office staff with a feature code for All Call. Single-zone configuration; one active page at a time. Typical install time: under two hours including network drop and SIP provisioning.
Scenario 2: 80,000 sq ft Distribution Warehouse
A distribution center with two amplifier rooms feeding three zones: receiving, picking, and shipping. Deploy three Algo 8373 IP Zone Paging Adapters, one per amp, plus one Algo 8301 registered as the primary SIP endpoint. The 8301 multicasts to the three 8373 receivers, which switch the amplifier output by zone. Users dial the 8301's extension and enter a DTMF zone code for targeted announcements or all-zones broadcast. Requires in-band DTMF passthrough enabled on the 8301 and IGMP querier configured on the warehouse VLAN. Concurrency is handled through multicast rather than individual SIP calls, which keeps RTP load on the hosted PBX near zero regardless of how many zone adapters are listening.
Scenario 3: Medical Clinic, 12 Exam Rooms, Legacy Bogen UTI1 Already Installed
A clinic that recently replaced its NEC SV9100 with a hosted PBX. The UTI1 is already wired to the Bogen amplifier and the customer does not want a rip-and-replace. Deploy a Grandstream HT801 ATA with one FXS port. Connect the FXS port to the UTI1's Trunk/Page Port jack via RJ11. Set the UTI1 to STA/PBX mode. Register the HT801 to the hosted PBX as a dedicated extension with auto-answer enabled, G.711 mu-law only, and in-band DTMF. Total hardware cost under $150 for the ATA. The existing UTI1, amplifier, and 47 ceiling speakers stay in place. This is the cleanest argument for keeping the UTI1: when the analog infrastructure is fully functional and the only thing changing is the PBX, the most profitable install is the one that touches the least hardware.
Why Viirtue Handles Paging Better Than Generic SIP Providers
Most hosted PBX platforms treat paging as a checkbox feature. They'll let you register a SIP endpoint and call it done. That works for a simple single-zone overhead page, but it falls apart quickly when MSPs are managing multiple customers with multiple paging zones, scheduled announcements, and multicast groups to keep organized.
The Viirtue hosted VoIP platform treats paging as a managed feature inside a white-label VoIP platform built specifically for MSP resellers. The operational differences matter at scale:
- Auto-answer extension types are exposed directly in the partner portal, not buried in dial plan XML or requiring a support ticket. Configuring an Algo 8301 takes under five minutes per device.
- Multicast groups are managed at the tenant level, so a single MSP can run 20 different customer paging environments without IP address collisions or cross-tenant VLAN tickets.
- Integrated billing through ViiBE bills paging extensions, ATA ports, and scheduled announcement services automatically. There is no parallel spreadsheet of "paging endpoints we forgot to invoice for."
- Compliance handling at the platform level means STIR/SHAKEN, FCC Form 477, and 911 dispatchable location are covered. Paging extensions with associated DIDs do not create compliance gaps that fall back on the MSP.
Generic SIP providers force MSPs to stitch together a PBX, an FXS gateway, a scheduler, a multicast manager, and a billing system. UCaaS platforms like RingCentral, 8x8, and Zoom Phone support paging endpoints but treat resellers as a channel afterthought and do not expose multicast group management or scheduler integration to partners. The VoIP paging system equipment guide goes deeper on the hardware side of that decision for MSPs evaluating the full scope of a paging migration project.
SIP Paging Adapter Wiring and the MSP Opportunity Behind It
Getting SIP paging adapter wiring right comes down to three things: the physical line-level connection to the amplifier, the line output level set correctly for the amp model (0 dBm 600 ohm for nearly every Bogen amplifier in the field), and the SIP registration configured with the right codec and DTMF settings. Once those are in place, the customer's legacy overhead system becomes a fully integrated SIP endpoint that participates cleanly in the modern voice environment -- without touching a single speaker or ceiling tile.
For MSPs running paging projects across multiple customer sites, the bigger question is which platform sits behind those adapters. A hosted PBX built for the reseller channel handles the paging-adjacent work -- multicast management, scheduling, auto-answer extension types, ViiBE billing integration, and compliance -- without the manual stitching that SIP-only providers push down to the integrator. That operational efficiency is what makes paging a repeatable, profitable line item instead of a one-off install with a long tail of callbacks.
If you are evaluating where to land your paging customers, Viirtue's partner program is built for MSPs and IT providers who want margin ownership and a platform that handles the operational layer -- not just dial tone.
Sources and Further Reading
- Algo Solutions. 8301 IP Paging Adapter and Scheduler Product Page.
- Algo Solutions. Paging Adapter Amplifier Integration Guide.
- Algo Solutions. 8301 Paging Adapter and Scheduler User Guide.
- Bogen Communications. UTI1 Universal Telephone Interface Installation and Use Manual.
- Bogen Communications. UTI1 Single-Zone Universal Telephone Interface Product Page.
- National Center for Education Statistics. Characteristics of Elementary and Secondary Schools, Condition of Education 2024.
- Allied Market Research. Public Address and Voice Alarm Systems Market Forecast 2025-2034.
- Federal Communications Commission. Notice of Proposed Rulemaking on Intercarrier Compensation and IP Transition (February 2026).
- Federal Communications Commission. Technology Transitions Overview.
FAQ: SIP paging adapter wiring
Can I use any SIP paging adapter with my hosted PBX?
Almost always, yes. The Algo 8301, Algo 8373, CyberData paging adapters, and any ATA fronting a Bogen UTI1 are standard third-party SIP endpoints. Verify with your hosted PBX provider that they allow third-party device registration and support G.711 µ-law as a codec option, which is the case for any reputable platform.
Do I need PoE to install an Algo 8301?
Yes, the 8301 is powered exclusively by PoE 802.3af. If the install location does not have a PoE-capable switch port, install a single-port PoE injector. The 8301 does not have a barrel jack or alternative power input.
What is the difference between the Algo 8301 and the Algo 8373?
The 8301 outputs balanced line-level audio to a single amplifier. The 8373 is a zone paging adapter with three high-powered relays that switch a single amplifier’s output across up to three speaker zones. Use the 8301 for single-zone or multicast-to-multiple-amps setups, and the 8373 to replace a legacy zone controller behind one amplifier.
Can I keep my existing Bogen amplifier and just replace the PBX?
Yes, and that is the most common scenario MSPs encounter. Install an Algo 8301 wired to the Bogen amplifier’s telephone input, register the 8301 to the new SIP PBX, and the existing amplifier and ceiling speakers continue to work without modification.
Will the paging system work during a hosted PBX outage?
Local paging through an Algo 8301 requires the PBX to route the call, so during a PBX outage the SIP path is unavailable. However, the 8301’s scheduler runs locally, so scheduled bells and tones continue. For mission-critical paging in life-safety contexts, deploy a local backup paging input directly to the amplifier as a failover.
How do I add zone paging to a single-amplifier site?
Either replace the existing zone controller with an Algo 8373 (one device, three relay-switched zones), or keep the legacy zone controller and pass DTMF through the 8301 with In-Band DTMF Tones enabled. The 8373 is cleaner for new installs. The DTMF passthrough approach is cheaper if the existing zone controller is fully functional.
What codec should the SIP trunk use for paging?
Use G.711 µ-law on the trunk path that touches the paging adapter. Even if the rest of your trunk supports G.722 or Opus, force G.711 µ-law on the paging extension to guarantee in-band DTMF passthrough and to avoid transcoding artifacts that show up as choppy or robotic audio over the speakers.
