VoIP.info Device reference

Algo 8138 IP Color Visual Alerter

Evaluate the 8138 as a four-color SIP, multicast, API and contact-triggered PoE alerter whose pattern policy, wet-location installation and photosensitivity boundary require local acceptance.

Reviewed 2026-09-27Exact-model manufacturer product page, product sheet and user guide updated July 27, 2026 reviewed September 27, 2026; no alerter, LED output, mount, gasket, PoE switch, PBX, SIP account, multicast network, API, contact circuit, certificate, supervision platform, accessibility or emergency workflow testedAdvancedDocumentation based · not lab tested

Documented specifications

Open IP Phone Compare →

Algo · Manufacturer product, user-guide and firmware resources were current at review; exact regional inventory, purchased hardware revision, approved firmware, licences and remaining support period were not established.

8138: manufacturer-sourced facts
SpecificationDocumented value
Light and patterns64 LEDs: 16 each in amber, blue, green and red; 15 patterns and 3 intensity levels, with 180 manufacturer-listed combinations including steady on Source ↗
Published optical output370–690 lumens and 102–190 peak candela depending on color; these are manufacturer figures, not installed visibility results Source ↗
Activation pathsSIP ring or paging, subscribed in-use events, RTP multicast send and receive, REST API and normally open or normally closed contact input are documented Source ↗
PowerIEEE 802.3af Class 0 PoE input; product sheet lists 4 W maximum at the device and 2 W idle Source ↗
Mounting and environmentWall or ceiling mounting with included plate; product sheet lists IP66 when correctly installed and the guide requires the specified orientation, drainage, gaskets or approved sealant for wet locations Source ↗
SIP and multicast scaleProduct sheet lists 50 page, 10 emergency-alert and 10 ring extensions plus 50 RTP multicast zones; a single active call and platform licensing remain separate constraints Source ↗
Security controlsTLS, SRTP, mutual authentication, HTTPS provisioning and IEEE 802.1X are documented; configuration and certificate trust were not verified Source ↗
Supervision optionsADMP, Algo 8300 controller, SNMP and RTCP are documented; ADMP and the 8300 controller cannot be used simultaneously Source ↗

Unlisted fields remain unverified. Platform compatibility and remaining support life require confirmation for the exact ordered model.

Choose 8138 for distinct color policy, not a generic strobe claim

The 8138 provides amber, blue, green and red LEDs, unlike the white-light 8128. Treat every color, pattern and intensity as a local policy item: document its event, audience, required response, trigger and clear condition. Do not assume that a color has a universal emergency meaning or that every viewer can distinguish it.

The product sheet's lumen, candela and angular-visibility figures are manufacturer specifications. Confirm actual sight lines, ambient light, reflections and interpretation at each installed position; do not convert the headline output into a promised coverage area or accessibility result.

Preserve the photosensitivity and signaling boundary

Algo documents steady-state and lower-intensity choices and classifies different optical risks in the product sheet. The user guide still warns against close direct viewing and says flashing or flickering may trigger seizures for photosensitive people. Select the least provocative pattern that meets the operational need and include affected occupants and qualified safety staff in acceptance.

The guide states that the 8138 is for informative signaling and not a replacement for fire-alarm signaling. Keep a UC-triggered alert separate from any required listed alarm appliance, regulated notification system, approved emergency content or life-safety inspection.

Bind each SIP, multicast, API or contact trigger to one result

The 8138 can detect ring events without answering, auto-answer page extensions, monitor subscribed states, send or receive multicast, accept an API request or react to a contact input. Capture the exact input, authenticated identity, extension or zone, priority, pattern and clear condition. One successful registered extension does not validate the other trigger paths.

For emergency-alert extensions, the guide requires an explicit cancel path and documents both direct-extension and DTMF selection. Test the start, cancel, overlap and reboot cases with controlled content. Additional extensions may require platform licences, and the guide documents only one active call at a time.

Install wet-location protection as a complete assembly

The guide permits indoor or outdoor installation only with its conditions. For wet locations, preserve the mounting orientation, downward cable and drain path, supplied gaskets or approved sealing method, smooth mating surface and protected wiring cavity. The product sheet's IP66 statement is conditional on correct installation and does not certify the wall, electrical box, conduit or field workmanship.

Use the documented PoE input and keep the switch's per-port and total budget visible. Validate the input supervision and relay load against the exact terminal limits before connecting a button, sensor or other circuit. A dry contact label alone does not establish electrical or operational compatibility.

Harden management and verify end-to-end supervision

The guide exposes an initial administrative password and can show status without login unless the option is restricted. Replace defaults, restrict management reachability, protect credentials and API access, and validate certificate trust, TLS, SRTP, provisioning and 802.1X independently where they are required. Document whether ADMP, the on-premise 8300 controller or another monitor owns supervision.

Commission the purchased hardware and approved firmware with the intended switch, VLAN, PBX or UC service, multicast design, contact circuit and viewing area. Test authorized and rejected triggers, exact colors and patterns, clear behavior, offline alarms, restart, network and power loss, and restoration. No device, optical output, weather seal, platform integration, accessibility result, emergency function, availability or price was validated for this guide.

Sources & applicability

Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.

Examples require adaptation to your topology. No live PBX or hardware testing is claimed.