Algo’s 8507 IP Horn Array Speaker is a highly durable speaker with wideband audio designed to deliver clear, intelligible audio communication, such as voice paging and emergency notifications in reverberant, loud environments.
The 8507 is IPX9-rated for harsh outdoor environments, including areas with frequent exposure to water, dust, or debris. It can withstand temperatures from -40°C to +50°C. Each Horn Array Speaker is approximately 41 lbs or 46 lbs with the mounting bracket. The outer dimensions are 45.3” x 11” and 10.8” deep without the mounting bracket. With a mounting bracket, the 8507 is 14” deep to a wall when wall-mounted or 16.25” to a pole center when pole-mounted. The 8507 can be used stand-alone or in a cluster configuration, depending on your needs.
.png "image(101).png")
Included
8507 IP Horn Array Speaker
Array mounting bracket and hardware kit
Weather resistant ethernet connector
Wiring shroud
Purchased Separately (Optional)
Pole mount hardware kit
Wall mount hardware kit
Disclaimer
The information contained in this document is believed to be accurate in all respects but is not warranted by Algo. The information is subject to change without notice and should not be construed in any way as a commitment by Algo or any of its affiliates or subsidiaries. Algo and its affiliates and subsidiaries assume no responsibility for any errors or omissions in this document. Revisions of this document or new editions of it may be issued to incorporate such changes. Algo assumes no liability for damages or claims resulting from any use of this manual or such products, software, firmware, and/or hardware.
No part of this document can be reproduced or transmitted in any form or by any means – electronic or mechanical – for any purpose without written permission from Algo.
For additional information or technical assistance in North America, please contact Algo’s support team:
1-604-454-3792
Important
This guide contains safety information which should be read thoroughly before permanently installing the product.
Important Notice
The 8507 Horn Array Speaker is AC mains powered. If the power plug is removed for direct connection to a mains supply, the connections should be performed by a qualified electrician according to local building codes.
The 8507 Horn Array Speaker must be mounted securely to a structure capable of supporting its weight. Note that this device is capable of output sound pressure levels in excess of 137 dB at 3 feet (1m). Ensure that the Horn Array is mounted in a location such that nobody is directly in front of or beside the Horn Array including during installation and testing of this device.
If used for emergency communications, the 8507 IP Horn Array Speaker should be routinely tested. SNMP or Algo ADMP supervision is recommended for continuous assurance of proper operation.
The 8507 IP Horn Array Speaker may be used in wet or outdoor environments contingent on electrical and network connections being suitable for wet or outdoor locations. It is strongly recommended that an outdoor-rated network cable be used for network connection.
CAT5 or CAT6 connection wiring to an IEEE 802.3 compliant network PoE/PoE+ switch must not leave the building perimeter without adequate lightning protection consistent with local electrical codes.
Getting Started
The 8507 Horn Speaker requires AC Mains power and PoE for full operating power. For configuration and quick testing, the Horn Array Speaker can operate without AC power but will limit its audio output to a single horn driver.
Connect the 8507 to a PoE network switch and AC Mains power (optional). The blue LED in the bottom plastic cap will turn on with PoE power until the device boot up is completed. This typically takes about 1 minute.
Once the blue LED turns off, press the reset switch (RST) to hear the IP address over the speaker. The IP address for your device may also be found via the Algo locator tool: www.algosolutions.com/locator. The tool is only available for Windows computers.
Type the device IP address into a web browser to access the web interface and configure your device for testing. The 8507 Horn Array may also be configured using centralized provisioning or the Algo Device Management Platform (ADMP).
Initial Configuration
Enter the 8507 IP address into a web browser to access the web interface.
Log in using the default password: algo.
Navigate to Basic Settings → SIP and enter the IP address or the domain name for the SIP server (provided by your IT team or hosted provider) into SIP Domain (Proxy Server).
Enter the Page and/or Ring credentials Extension, Authentication ID, and Authentication Password (provided by your IT team or hosted provider). If you are not using an extension, leave the fields blank. Note that some SIP servers may say Username instead of Authentication ID.
Verify the extension is properly registered with the SIP server in the Status tab. Ensure the SIP registration says Successful.
Test the adapter by dialing the registered SIP extension from a telephone. The speaker should auto-answer, play the default pre-announce audio, and open a speech path.
Mounting
The 8507 is typically installed vertically to create a dispersion pattern with narrow vertical and wide horizontal coverage. It may be tilted downward from 5 to 35 degrees in 5-degree increments.
When surface mounted, an optional bracket component allows up to 90-degree left to right rotation. For pole mount applications, any interfering structures or surfaces will determine the degree of rotation. A pole-mounted 8507 can rotate 90-degrees left to right if the pole center is at least 6 inches from a wall.
To prevent personal harm, it is essential that:
Due to its weight and size, two people handle, install, and mount the 8507 Horn Array Speaker.
The mounting surface or material is sufficient to carry the device's weight. The device can be mounted to a solid surface or 2" NPS (2.375" 63.3mm OD) pole.
Appropriate fasteners are used to prevent the device from falling.
Contact of dissimilar metals is avoided, especially in outdoor or wet applications, to avoid galvanic corrosion. Note that the mounting brackets and hardware supplied with the Horn Array Speaker are designed to prevent aluminum and stainless-steel components from contacting each other.
Isolation components are used to ensure long-term performance of the metal bracket components.
[main large image]
Install the Array Bracket
If no tilt is required, the array bracket may be installed in any position on the array as long as both mounting clips are used. If tilt is required, mount the adapter plate on the bottom of the array as shown below to allow downward tilt from a solid wall by up to 35 degrees.
If 30 or 35 degree tilt is required, the array must be mounted onto the adapter plate, as shown in Figure 2. The edge of the array bracket must be distanced at least 1.5 inches from the adapter plate edge to ensure the shroud does not impede and prevent tilting at 30 or 35 degrees.
Install the mounting adapter plate (D) to the Horn Array Speaker using the 2 mounting clips (E) and the 12 socket head bolt (F). Torque to 6.5 ft-lbs.
Pre-install the 6 hex head bolts (H) loosely with lock washers (I) and nuts (J) into the array bracket (C) to simplify installation. Slide the universal array bracket onto the adapter plate and tighten the bolts into the adapter plate channel to 9.75 ft-lbs.
[array bracket image]
[adapter plate and clip]
Assemble Linkage Arm
For tilt angles of 0, 5, 10, and 15 degrees, the linkage arm is not required. For tilt angles of 20, 25, 30, and 35 degrees, the linkage arm is required and must be pre-installed according to the figure below.
Slide the linkage spacer (L) between the large hole of the array bracket (C).
Slide the two linkage arm plates (K) over the protruding plastic on the array bracket (C), with the linkage bushing (M) wedged in between the plates.
Tighten the 5/16”-18 x 2” hex head bolt (Q) through the linkage spacer (L) with the flat washer (P), sleeve washer (O) and 5/16”-18 locknut (N). Torque to 9.75 ft-lbs.
[linkage arm plate]
Install the Mounting Bracket
Pole Mount (2 3/8” OD Pole)
Note that for a full 90-degree rotation, the pole center should be at least 6 inches from any adjacent wall.
[diagram - pending changes from Jeff re: Ubolt discussion]
Pole Installation Instructions
To pole mount the universal mounting bracket, first slide both U-clamps (PC) over the pole, spacing them 8 inches apart.
Align the sleeve washers (SW) and flat washers (FW) over the mounting plate and onto the threads of the U-Clamps. The isolating plastic sleeve washers must be used to prevent galvanic corrosion.
Tighten the locknuts (LN) to 17.5 ft-lbs. Tightening the locknuts will secure the mounting bracket (B) to the U-clamps and the U-clamps to the pole.
Wall Mount
Note the example kit is meant to mount the 8507 to wood, brick, block, or concrete. If the mounting surface is metal other than aluminum and in a wet location, an isolation barrier may be required between the aluminum wall bracket and wall surface to prevent galvanic corrosion.
[diagram]
Wood Installation Instructions
Pre-drill 4 x 9/32” holes into the masonry at least 3” deep. Vacuum any dust or debris from the hole.
Attach the mounting bracket using the 4 x 3/8” Tapcon screws (TB) and isolating flat washers (FW) and sleeve washers (SW).
Concrete, Block, or Brick Installation Instructions
Pre-drill 4 x 5/16” holes into the masonry at least 3” deep. Vacuum any dust or debris from the hole.
Attach the mounting bracket using the 4 x 3/8” Tapcon screws (TB) and isolating flat washers (FW) and sleeve washers (SW).
Install the Horn Array Speaker to the Mounting Bracket
[mounting and fastening the array diagram]
[zoom in circles diagram]
Use the following instructions to install the array to the mounting bracket:
With two people, position the Horn Array Speaker so the black axle of the array bracket slides into the slots of the mounting bracket.
Install the hex head bolt (Q) through the corresponding holes in the array and mounting.
Install the flat washer (P), sleeve washer (O) and locknut (N) to the angle adjustment bolt and tighten to 9.75 ft-lbs.
Install Wiring Shroud
The wiring shroud is required if the 8507 is installed outdoors or in a wet environment to meet IPX9 ingress protection. To do this:
Slide the plug support over the ethernet cable. Slide on the plug gasket next and plug nut after.
Push the ethernet plug into the bayonet plug housing. The end of the jack should stick out of the other side.
Fit the plug support into the plug housing and behind the ethernet jack.
Squeeze the plug gasket into the spokes of the plug housing. The face of the gasket should sit flush to the ends of the spokes.
Tighten the plug nut tightly over the plug housing. The bayonet plug should now be fully sealed
Connect the ethernet plug on the exposed end of the bayonet to the jack on the 8507. Twist the end of the bayonet to secure the jack.
Squeeze the drain tube over the drain fitting.
Attach the shroud parts with the power and ethernet cables fitting through the openings and the drain tube nested inside.
Any moisture that accumulates inside the 8507 can now exit through the flexible vent hose. This hose must be clear to drain inside the shroud.
[bottom diagram]
Wiring
Ethernet Wiring
If the 8507 is installed outdoors or in a wet environment, an outdoor-rated network cable with an LLDPE jacket or equivalent for water and UV protection must be used. To do this:
Install the supplied weatherproof sealing nut over the pre-terminated network cable.
Plug the network cable into the RJ45 jack.
Hand-tighten the sealing nut firmly onto the horn array weather-resistant jack.
AC Electrical Wiring
For quick testing and configuration, the 8507 can operate from PoE power.
For full capability, both AC Mains power 100 V – 240 VAC 50/60Hz and PoE is required. The maximum input current is 4A at 115VAC or 2A at 230VAC. The AC Mains supply must be current limited at 15A by a suitable circuit breaker or fuse.
The 8507 has an outdoor-rated electrical cable terminated with a North America NEMA 5-15P plug. For outdoor or wet environments, the AC plug may be removed and the electrical cable can be wired into a waterproof junction box using a cable gland. If you cut the cable you will find the following three color-coded wires:
Black wire – HOT
White wire – NEUTRAL
Yellow or green wire – GROUND
Accessing the Web Interface
To configure your device, you must enter the IP address for your device into your browser (see below).
You must log in to view device settings. The default password is algo. This password can be changed under Advanced Settings → Admin after logging in. Changing the default password is highly recommended if the device is directly connected to a public network.
Important
The Save button must be clicked to apply any changes made in the web interface.
Web Interface Setup
Connect the device to an IEEE 802.3af PoE network switch. The Algo logo will appear on the screen until boot-up is completed (about 1 minute).
Once complete, the IP address of your device should appear on the display. You can also find your device IP address by downloading the Algo locator tool: www.algosolutions.com/locator. The tool is only available for Windows computers.
Type the device IP address into a web browser to access the web interface and configure your device for testing. Note that these devices may be configured using centralized provisioning or the Algo Device Management Platform (ADMP).
Check Device Status
By default, the Status page is available with and without a login. The Status page can be made exclusive to logged-in users via Advanced Settings → Admin → General → Show Status Section on Status Page when Logged Out.
The Status page contains information such as:
|
|
Register Your Product
You may register your product at https://www.algosolutions.com/product-registration/ to ensure access to the latest upgrades for your device and to receive important service notices.
Reset
Security
Algo devices use TLS for provisioning and SIP signaling to mitigate cyberattacks by those trying to intercept, replicate, or alter Algo products. Algo devices also come pre-loaded with certificates from a list of trusted certificate authorities (CA) to ensure secure communication with reputable sources. Pre-installed trusted certificates are not visible to users and are separate from those in the ‘certs’ folder.
For further details, see Securing Algo Endpoints: TLS and Mutual Authentication.
SIP Configuration
Basic Settings
SIP signaling is the underlying protocol for transmitting SIP messages between different entities in a network. SIP signaling establishes the call but does not contain the audio.
A SIP endpoint license associated with a UCaaS platform may be required to register the 8450. One license will be required per extension registered. If one device has multiple extensions registered, each registered extension will require a license. On a hosted or cloud platform, the required endpoint extension or seat may be treated the same as any other extension on the system and incur a monthly cost or similar fee.
.png "image(86).png")
SIP | |
|---|---|
SIP Domain (Proxy Server) | The SIP Server's IP address (e.g., 192.168.1.111) or domain name (e.g., myserver.com). |
Page Extension | Page extensions auto-answer and open a voice path, enabling live announcements. Enter the SIP page extension so the device will auto-answer any inbound call received on this extension and provide a voice paging path (and multicast if configured). |
Authentication ID | The Authentication ID is a name that represents the page extension. It is also referred to as ‘Username’ for some SIP servers. This may be the same as the Ring or Page extension in some cases. |
Authentication Password | This is the SIP password for the registered SIP account. Up to eight (63) characters can be used. The password can be used to authenticate SIP users. Contact your System Administrator for the password to obtain access. |
Display Name (Optional) | Enter the name you want displayed when an SIP call is made. For the display name to be shown, the PBX and phone(s) must be configured to display this message as the Caller ID. |
Advanced SIP
.png "image(87).png")
General | |
|---|---|
SIP Transportation | Select a transport layer protocol to use for SIP messages from the dropdown. These options include:
|
SIPS Scheme | Only visible when SIP Transportation is set to TLS. Enable to require the SIP connection from endpoint to endpoint to be secure. |
Validate Server Certificate | Enable to validate the SIP server against common certificate authorities. To validate additional certificates, navigate to System → File Manager to upload a Base64 encoded X.509 certificate file in .pem, .cer, or .crt format to the certs folder. |
SIP Outbound Support (RFC 5626) | Enable this option to support best networking practices according to RFC 5626. This option should be enabled if the device is registered with a hosted server or TLS is used for SIP Transportation. Only enable this option if the SIP server supports RFC 5626. |
Outbound Proxy | Enter the IP address for an outbound proxy. |
Register Period (seconds) | Enter the maximum requested period where the device will re-register with the SIP server. The default setting is 3600 seconds (1 hour). Note that if an Expires header is provided by the SIP response 200 (OK), this time will take precedence over the Register Period defined time here. Only change if instructed to do so. |
Rate Limit SIP Registration | This option should be used in cases where many SIP extensions are registered (ex. one for each zone). Select a rate limit to stagger registration requests and prevent overloading the server by sending them all at the same time. |
Wait for Successful Unregister | Enable to wait for the device to successfully unregister from the server. Enabling may cause a slight delay during configuration changes and reboots |
SRTP | |
|---|---|
SDP SRTP Offer | Select an option from the dropdown menu:
|
NAT | |
|---|---|
Media NAT | IP address for STUN server if present or IP address/credentials for a TURN server. |
ICE – TURN Server | Enter the IP address or domain of the ICE server. |
ICE – TURN User | Enter the username. |
ICE – TURN Password | Enter the password. |
STUN - Server | Enter the IP address or domain of the STUN server. |
Server Redundancy | |
|---|---|
Server Redundancy Feature | Enable to configure up to two secondary backup servers. When enabled, the device will attempt to register with the primary server but switch to a secondary server when necessary. The configuration allows re-registration to the primary server upon availability or to stay with a server until unresponsive. |
Backup Server #1, #2 | Provided by your SIP provider or IT team. |
Polling Intervals (seconds) | Select the time interval for sending monitoring packets to each server from the dropdown menu. Inactive servers are always polled and the active server may optionally be polled. |
Poll Active Server | Enable to explicitly poll the current server to monitor availability. Other regular events may also handle this automatically and can be disabled to reduce network traffic. |
Automatic Fallback | Enable to allow the device to reconnect with a higher priority server once available, even if the backup connection is still working. |
Polling Method | Select a polling method based on what your SIP provider supports. |
Zoom Phone Local Survivability | |
|---|---|
Local Survivability | Enable to re-register with local ZPLS Node if connection to Zoom fails. This allows sites to maintain a subset of Zoom Phone features even if connectivity to the Zoom Phone cloud is lost. |
Survivability Proxy | The IP address or domain name of the local ZPLS node. |
Interoperability | |
|---|---|
Keep-Alive Method | Select a keep-alive method:
|
Keep-Alive Interval | Set the interval in seconds that the CRLF message should be sent. 30 seconds is recommended. |
Use Outgoing TLS port in SIP Headers | Enable to use the ephemeral port number from an outgoing SIP TLS connection instead of the listening port number in SIP Contact and Via headers. This is useful for connecting the device to some local SIP servers, like Asterisk or FreeSWITCH. |
Do Not Reuse Authorization Headers | Enable so all SIP authorization information from the last successful request will not be reused in the next request. |
Allow Missing Subscription-State Headers | Enable to allow SIP NOTIFY messages that do not contain a Subscription-State header. |
Interoperability | |
|---|---|
Keep-Alive Method | Select a keep-alive method:
|
Keep-Alive Interval | Set the interval in seconds that the CRLF message should be sent. 30 seconds is recommended. |
Use Outgoing TLS port in SIP Headers | Enable to use the ephemeral port number from an outgoing SIP TLS connection instead of the listening port number in SIP Contact and Via headers. This is useful for connecting the device to some local SIP servers, like Asterisk or FreeSWITCH. |
Do Not Reuse Authorization Headers | Enable so all SIP authorization information from the last successful request will not be reused in the next request. |
Allow Missing Subscription-State Headers | Enable to allow SIP NOTIFY messages that do not contain a Subscription-State header. |
Multicast Configuration
The 8450 IP Console can only be programmed as a multicast transmitter to broadcast voice paging or alerts and trigger other devices. IP endpoints on the same local network as the 8450 can be grouped into up to 50 multicast zones and paged via multiple SIP extensions.
Multicast IP Addresses
Each device has a unique IP address and shares a common multicast IP and port number (multicast zone) for multicast packets. The Transmitter units send to a configurable multicast zone, and the Receiver units listen to assigned multicast zones.
The network switches and router see the packet and deliver it to all the group members. The multicast IP and port number must be the same on each group's Transmitter and Receiver units. The user may define multiple zones by picking different multicast IP addresses and/or port numbers.
Multicast IP addresses range: 224.0.0.0/4 (from 224.0.0.0 to 239.255.255.255)
Port numbers range: 1 to 65535
By default, the device is set to use the multicast IP address 224.0.2.60 and the port numbers 50000-50008
Ensure the multicast IP address and port number do not conflict with other services and devices on the same network.
Basic Multicast Settings
Always ensure that the multicast settings on all Receiver devices match those of the Transmitter.
.png "image(88).png")
Multicast Mode | |
|---|---|
Multicast Type | The device may broadcast multicast paging compatible with Poly “on-premise group paging” protocol and most multicast-enabled phones that use RTP audio packets. Select Regular (RTP) if you are only multicasting to Algo IP endpoints or multicast-enabled phones. To multicast page announcements to Poly phones, select Poly Group Page or Poly Push-to-Talk. Select Regular RTP + Poly Group Page or Regular RTP + Push-to-Talk to multicast page audio to Poly phones, Algo IP endpoints, and multicast-enabled phones. |
Number of Zones | Select Basic Zones Only if configuring nine or fewer multicast zones. Select Basic and Expanded Zones to configure up to 50 zones. The expanded zones have the same behavior as the basic Receiver zones but are hidden by default to simplify the interface. |
Poly Group Paging/Push-to-Talk (This section is used if the Multicast Type includes Poly Group Page or Poly Push-to-Talk.) | |
|---|---|
Poly Zone | Enter the same Multicast IP Address and Port number configured on the Poly phones. |
Using Multicast Page Zones
The 8450 IP Console can broadcast to up to 50 paging. The multicast IP addresses define these zones.
By default, these zones have the names below but can be used however you prefer.
Priority
All Call
Zone 1
Zone 2
Zone 3
Zone 4
Zone 5
Zone 6
Music
As a multicast transmitter, event priority for the 8450 is based on the event type that initiated the multicast rather than the output multicast channel that will be active.
Zone paging can be set using DTMF. DTMF uses dynamic page zone selection and requires only the transmitting device to have a registered SIP extension. To page, dial the SIP extension of the transmitter and dial the desired DTMF page zone (e.g., 1, 2, etc.) on the keypad. DTMF digits and their corresponding zone numbers can be found in the Advanced Settings → Advanced Multicast tab of the web interface.
Advanced Multicast Settings
.png "image(83).png")
Transmitter Settings | |
|---|---|
Transmitter Output Codec | Select an audio encoding format for the Transmitter device to use when sending output to the Receivers. Supported formats include:
|
Poly Output Codec | Select an audio encoding format when using Poly Group Page or Poly Push-to-Talk. Supported formats are G.711 ulaw and G.722 only. |
Output Packetization Time (milliseconds) | Select the size of the audio packets the Transmitter sends to the Receivers from the dropdown menu. The default of 20 milliseconds is recommended unless a different value is specifically required for compatibility with other devices. |
Multicast TTL | Only change the multicast time to live (TTL) setting if custom routing is configured on the network that specifically routes multicast packets between subnets and a longer TTL count is required. This ensures packets are not bounced back and forth in a network identity. When the TTL is reached, the router drops the packet. |
RTP Control Protocol (RTCP) | |
|---|---|
RTCP Port Selection | Select how a port will be chosen to send or receive RTCP packets. Note: If Next Higher Port is selected, ensure that the default multicast zone definitions are modified so that zones are only assigned to even-numbered ports, leaving the next higher odd-numbered ports free for RTCP packets. |
Audio Configuration
Basic Settings
Basic Settings
.png "image(74).png")
Inbound Page Settings | |
|---|---|
Page Timeout | Set the maximum duration for a page. The page will end when the timeout limit has been reached. This is useful to ensure the paging system is not stuck in an active state in cases where someone accidentally forgets to hang up. |
G.722 Support | Enable or disable the G.722 codec. G.722 enables wideband audio for optimum speech intelligibility. |
DTMF Detection Type | Select the preferred dual-tone multi-frequency (DTMF) detection method. DTMF is a technology used with touch tone phones (the sound made when pressing a number key). The device uses this for multi-zone selection, passcode, etc. |
Audio Processing | |
|---|---|
Automatic Gain Control (AGC) | Enable or disable AGC to normalize the audio level. Enabling ensures the speaker is always played at a consistent volume. |
Emergency Alerts
The 8450 can be used for emergency (e.g., lockdown, evacuation, reverse evacuation), safety (e.g., medical, workplace accident), and security events (e.g., OSHA or similar workplace regulations) alerting.
Emergency alerts notify others of an emergency quickly and efficiently. Users can dial a pre-configured extension number to trigger and latch an emergency alert or announcement. The announcement will continue to play on a loop until a different “Call-to-Cancel” extension is called to clear the announcement or a pre-defined timeout is reached.
Up to 10 extensions can be registered allowing up to 10 different announcements. A single “Call-to-Cancel” extension also needs to be registered. Calling this number will cancel an active announcement.
Note: Some SIP telephone systems may not support this feature if they limit the number of extensions that can be registered on a single device.
.png "image(85).png")
Settings | |
|---|---|
Default Announcement Duration | An announcement can be played once or continuously until canceled. Select Play Once to play a single cycle of the chosen tone file. If Play Until Cancelled is selected, the announcement will continue to play until the "Call-to-Cancel" extension is called to clear the announcement or a defined timeout is reached. |
Default Maximum Announcement Time | Select the maximum time an announcement can be played. |
Default Announcement Tone | This tone is used if any of the announcements have the Tone/Pre-recorded Announcement set to Use Default Ring Tone. |
Announcement Selection Mode | Select Direct Extensions to register a separate extension for each announcement. Select DTMF Selectable to register a single extension that accepts DTMF input to select which announcement to play. |
Answer Inbound Call | Enable to answer inbound calls with the option to play a confirmation tone before starting an alert. If disabled, the inbound ring signal will be detected, but the device will not answer the call. |
Passcode Protected Announcement Extensions | Select Enabled to require the caller to enter a passcode after dialing an announcement or “Call-to-Cancel” extension. Setting a passcode helps prevent unintentional announcements. |
Announcement Passcode | Enter a passcode that a caller must enter to play or cancel an announcement. When prompted, the caller must enter the passcode followed by the # sign before the announcement will be played or canceled. The passcode prompt will be played before any other action. If the passcode is not correctly entered within 15 seconds, the call will end. |
Passcode Prompt Tone | Select a tone to play when the passcode is ready to be entered. |
DTMF Selection | |
|---|---|
Extension | Enter the SIP extension for the DTMF Selection parameter. |
Authentication ID | Enter the Authentication ID. It may also be called Username for some SIP servers or may be the same as the extension. |
Authentication Password | Enter the SIP password provided by the system administrator for the SIP account. |
Display Name (Optional) | Enter a ‘Display Name’ that will be sent when the SIP call is made. The PBX and phone(s) must be configured to display this message as the Caller ID. |
Prompt Tone | Select a tone to play when the passcode is ready to be entered. |
Call-to-Cancel | |
|---|---|
Call-to-Cancel Selection Mode | If using “DTMF 0”, the user should dial the main DTMF Selection extension and select ‘0’ to cancel the announcement. |
Extension | Enter the SIP extension for the Call-to-Cancel Selection parameter. |
Authentication ID | Enter the Authentication ID provided by the System Administrator. It may also be called Username for some SIP servers or may be the same as the extension. |
Display Name (Optional) | Enter a ‘Display Name’ that will be sent when the SIP call is made. The PBX and phone(s) must be configured to display this message as the Caller ID. |
Confirmation Tone | Select a tone to play to confirm that an alert has been canceled. |
Announcements | |
|---|---|
Announcement # | To configure an Emergency Alert extension, select Enabled for an announcement number. Up to 10 extensions can be registered allowing up to 10 different announcements. Audio files can be easily uploaded to create custom announcements. Only one Call-to-Cancel extension is needed. Some SIP telephone systems may not support multiple announcements if they limit the number of extensions that can be registered on a single device. |
Announcement Duration | Choose the duration of an announcement. The Default option follows the behavior configured in Default Announcement Duration. |
Maximum Announcement Time | Select the maximum announcement time. |
Tone/Pre-recorded Announcement | Select a file to use as a ringtone or announcement. |
Confirmation Tone | Select a file to use as a confirmation tone. |
Multicast Zone | Set the RTP multicast zone where announcements will be played. |
Multicast Poly Group | Set the Poly Group where announcements will be played. |
Tones
The 8450 includes several pre-loaded audio files that can be selected to play for various events. The web interface allows you to select a file and play it immediately over the speaker for testing, available in Basic Settings → Features. Files may also be added, deleted, or renamed. For more information see File Manager.
.png "image(80).png")
Files | |
|---|---|
Download and Install Ring Tones from the Algo Server | Tone files can be downloaded manually from the Algo website. |
Cache | |
|---|---|
Rebuild Tone Cache Files | Only needed when the tone cache is out of sync. The operation might take a long time depending on the types and sizes of the tone files. |
Test Tones | Listen to uploaded audio files before selecting them for your system. |
Advanced Audio
.png "image(78).png")
Functions | |
|---|---|
Jitter Buffer Range (milliseconds, 10 ~ 500) | Enter a value between 10-500 to add more buffering if necessary to correct for inconsistent delays on the network. It is recommended to use the lowest value. |
Always Send RTP Media | Enable to send audio packets at all times. This option is needed when the server expects to always see audio packets. |
Integration
API
Algo RESTful API can be used to access, manipulate, and trigger Algo endpoints on your network through HTTP/HTTPS requests.
Requesting systems can interact with Algo devices through a uniform and predefined set of stateless operations. See the Algo RESTful API Guide for more details.
To configure API settings, use the web interface and navigate to Advanced Settings → Admin → API Support.
.png "image(90).png")
API Support | |
|---|---|
RESTful API | Disabled by default. Enable a secure API for remote access and device control via HTTP. For more information, see the Algo RESTful API Guide. |
Authentication Method | Speak to your IT Administrator for more information. |
RESTful API Password | Speak to your IT Administrator for more information. |
SCI Support | |
|---|---|
SCI | Disabled by default. Simple Control Interface (SCI) is a separate control interface for certain applications. Its primary purpose is to support phones that may have programmable keys that can only send out HTTP GET requests. |
SCI Password | Enter your SCI password. |
InformaCast
As a Singlewire Solutions Partner, Algo products have been certified for compatibility and interoperability.
To set up your device with InformaCast, use the web interface and navigate to Advanced Settings → Admin → InformaCast.
.png "image(89).png")
InformaCast IP Speaker | |
|---|---|
InformaCast IP Speaker Support | This feature requires a valid InformaCast license to be activated. Please contact sales@algosolutions.com for assistance. |
InformaCast Scenarios API | |
|---|---|
InformaCast Scenario API Support | When enabled, a button can be configured to Start InformaCast Scenario. Input the Security Token and specify a location if applicable. |
Microsoft Teams
Algo devices are certified by and compatible with Microsoft Teams. When registered in the Microsoft Teams SIP Gateway, the 8450 can be configured to deliver Teams-based communication throughout facilities. For more details, see the Microsoft Teams Testing & Configuration Guide.
.png "image(92).png")
Microsoft | |
|---|---|
Microsoft Teams Support | Enable to provision the device via Microsoft’s servers. The device reboot will take up to 5 minutes to complete, as the device will communicate several times with the Microsoft server. This feature requires a compatible release from Microsoft. |
Device Management
ADMP
The Algo Device Management Platform (ADMP) is a cloud-based device management solution to manage, monitor, and configure Algo IP endpoints from any location. Devices can be easily grouped via a tagging functionality, allowing devices to be coded by district, department, or function to easily oversee many devices. Devices can be supervised for connectivity and email-based notifications can be sent should devices go offline, allowing for a real-time overview of device status.
To connect your device to your ADMP account, use the web interface and navigate to Advanced Settings → Admin → ADMP Cloud Monitoring.
Note that if you choose to use ADMP to manage your devices, the Algo 8300 IP Controller cannot be used at the same time.
To learn more about ADMP and how to purchase a license, visit the website.
.png "image(93).png")
ADMP Cloud Monitoring | |
|---|---|
Enable ADMP Cloud Monitoring | The Algo Device Management Platform (ADMP) simplifies the process of managing, monitoring, and maintaining Algo devices from any location. This feature requires a valid Account ID. To learn more about ADMP and how to purchase a license, visit the website. |
Account ID | Enter the account ID listed on the Settings page of your ADMP account. |
Allow Configuration File Sync | Enable ADMP to query and display settings stored on the device. |
Heartbeat Interval | Select how often ADMP should check the status of your device. |
Algo 8300 Controller
The Algo 8300 IP Controller is designed for centralized on-premise or local network Algo endpoint monitoring and supervision. Any Algo SIP endpoint device, can be monitored on the network via the 8300 dashboard.
Note that if you choose to use the Algo 8300 IP Controller to manage your devices, ADMP cannot be used at the same time.
Learn more about the Algo 8300 IP Controller.
SNMP
Simple Network Management Protocol (SNMP) can be used to monitor and manage your device.
To configure your SNMP settings, use the web interface and navigate to Advanced Settings → Admin → Simple Network Management Protocol.
.png "image(94).png")
SNMP | |
|---|---|
SNMP Support | Disabled by default. The existing setting will respond to a simple status query for automated supervision. |
SNMP Community String | Speak to your IT Administrator for more information. |
SNMPv3 Security | Speak to your IT Administrator for more information. |
RTCP
Real-Time Transport Control Protocol (RTCP) can be used to monitor data delivery.
To configure your RTCP settings, use the web interface and navigate to Advanced Settings → Advanced Multicast → RTP Control Protocol (RTCP).
.png "image(95).png")
RTP Control Protocol (RTCP) | |
|---|---|
RTCP Port Selection | Select how a port will be chosen to send or receive RTCP packets. Note: If Next Higher Port is selected, ensure that the default multicast zone definitions are modified so that zones are only assigned to even-numbered ports, leaving the next higher odd-numbered ports free for RTCP packets. |
System Configuration
Input
.png "image(82).png")
Action When Button Pressed | |
|---|---|
Action | Play Tone When a button is pressed, a tone or a pre-recorded audio file will be broadcast. This function can be used to request support or assistance in service or retail environments, notify about an emergency at a specific location in medical or educational facilities, or sound an alarm during an intrusion. Make Two-Way SIP Voice Call When a button is pressed, a voice path will open for an intercom-like call via an external microphone connected to a pre-configured telephone extension. This option can be used when a call needs to be made from a public place where a telephone would not be practical to use. Make SIP Call with Tone When a button is pressed, a private call can be made to a pre-configured telephone extension with a pre-recorded message. For instance, a call to a supervisor’s telephone notifying about an emergency or intrusion at some location. Stream Mic Audio When a button is pressed, audio from the attached microphone will be broadcast over multicast to the selected zone or group. |
Tone/Pre-recorded Announcement | Available when Action is set to Play Tone or Make SIP Call with Tone. Select a recording or tone to use. Custom audio files may be used and uploaded through System → File Manager. |
Tone Duration | Available when Action is set to Play Tone. |
Multicast Zone | Available when Action is set to Play Tone or Stream Mic Audio. The RTP multicast zone where tones and microphone audio will be broadcast to. |
Multicast Poly Group | Available when Action is set to Play Tone or Stream Mic Audio. The Poly Group where tones and microphone audio will be broadcast to. |
Extension to Dial | Available when Action is set to Make Two-Way SIP Voice Call or Make SIP Call with Tone. A SIP account is required in Page Extension fields to make a call. |
Allow 2nd Button Press | Available when Action is set to Make Two-Way SIP Voice Call or Make SIP Call with Tone. If enabled, the 2nd button press will End Call or End and Restart Call. Therefore, if an input is triggered a second time, the SIP call will be terminated and, in some cases, immediately called again. |
Outbound Ring Limit | Available when Action is set to Make Two-Way SIP Voice Call or Make SIP Call with Tone. If enabled, the 2nd button press will End Call or End and Restart Call. Therefore, if an input is triggered a second time, the SIP call will be terminated and, in some cases, immediately called again. |
Ringback Tone | Available when Action is set to Make Two-Way SIP Voice Call or Make SIP Call with Tone. The tone played during an outbound call while waiting for the call receiver to answer. |
Maximum Call Duration | Available when Action is set to Make Two-Way SIP Voice Call. The maximum length a call can be. |
Interval Between Tones (seconds) | Available when Action is set to Make SIP Call with Tone. Specify the time delay (seconds) between tones. |
Maximum Tone Duration | Available when Action is set to Make SIP Call with Tone. Select the maximum tone duration. The tone will be terminated once the maximum time is reached. |
Network Settings
.png "image(81).png")
Common | |
|---|---|
Internet Protocol | Use the dropdown to select IPv4 Only or IPv4 and IPv6. If IPv6 is also configured, it will have to be set up via DHCP or statically, similarly to the IPv4. |
Supersede DNS provided by DHCP | This setting will not appear if the selected Internet Protocol is set to Static. |
IPv4 | |
|---|---|
IPv4 Method | The device can be set to a static or DHCP IP address. DHCP is an IP standard designed to simplify the administration of IP addresses. When selected, DHCP will automatically configure IP addresses for each device on the network. DHCP is selected by default. When Static is selected, the device will use the IP address entered in the fields below. |
IPv4 Address/Netmask | Enter the static IP address and netmask (CIDR format) for the device (e.g., 192.168.1.23/24). |
IPv4 Gateway | Enter the gateway address. |
IPv6 | |
|---|---|
IPv6 Method | The device can be set to a static or DHCP IP address. DHCP is an IP standard designed to simplify the administration of IP addresses. When selected, DHCP will automatically configure IP addresses for each device on the network. When Static is selected, the device will use the IP address entered in the fields below. |
IPv6 Address/Netmask | Enter the static IP address and netmask (CIDR format) for the device (e.g., 2001:123::abcd:1234/64). |
IPv6 Gateway | Enter the gateway address. |
ICMPv6 Options | |
|---|---|
Destination Unreachable Messages | Enable to restrict traffic by filtering ICMPv6 packets. |
Neighbor Discovery Redirect Messages | Enable to restrict traffic by filtering ICMPv6 packets. |
Anycast Echo Replies | Enable to restrict traffic by filtering ICMPv6 packets. |
Enable Rate Limiting Outbound Messages | Enable to limit the device to respond to other network devices at the specified rate below and prevent it from receiving multiple requests at the same time. |
Rate Limit (packets per second) | Specify the packets per second allowed for Rate Limiting Outbound Messages. |
802.1Q Virtual LAN (If the device is using VLAN, you will need to be on the same VLAN to access the web interface.) | |
|---|---|
VLAN Mode | VLAN tagging is the networking standard that supports Virtual LANs (VLANs) on an Ethernet network. The standard defines a system of VLAN tagging for Ethernet frames and the accompanying procedures to be used by bridges and switches in handling such frames. The standard also provides provisions for a quality-of-service prioritization scheme known as IEEE 802.1p and defines the Generic Attribute Registration Protocol. |
VLAN ID | Specify the VLAN that the Ethernet frame belongs to. The hexadecimal values 0x000 and 0xFFF are reserved. All other values may be used as VLAN identifiers, allowing up to 4094 VLANs. The reserved value 0x000 indicates that the frame does not belong to any VLAN. In this case, the 802.1Q tag specifies only a priority and is referred to as a priority tag. |
VLAN Priority | Set the frame priority level. Otherwise known as Priority Code Point (PCP), VLAN Priority is a 3-bit field that refers to the IEEE 802.1p priority or frame priority level. Values are from 0 (lowest) to 7 (highest). |
802.1X Port-based Network Access Control | |
|---|---|
802.1x Authentication | Enable to add credentials to access LAN or WLAN that have 802.1X network access control (NAC). You can ask your IT Administrator for this information |
Authentication Mode | Select the desired authentication mode. |
Anonymous ID | If configured, the device will send the anonymous ID to the authenticator instead of the 802.1X client username. |
ID | The ID should contain a string identifying the IEEE 802.1X authenticator originating the request. Ask your IT administrator for details. |
Password | Ask your IT administrator for details. |
Validate Server Certificate | Enable to validate the authentication server against common authorities. To validate additional certificates, go to the System → File Manager to upload a Base64 encoded X.509 certificate file in .pem, .cer, or .crt format to the certs folder. |
Differentiated Services | |
|---|---|
SIP (6-bit DSCP value) | Enter the DSCP value for SIP packets. |
RTP (6-bit DSCP value) | Enter the DSCP value for RTP packets. |
RTCP (6-bit DSCP value) | Enter the DSCP value for RTCP packets. |
DNS | |
|---|---|
DNS Caching Mode | There are three mode options:
|
TLS | |
|---|---|
Allow Weak TLS Ciphers | Enables compatibility with legacy systems that may not support the most current encryptions standards |
Admin
.png "image(96).png")
Admin Password | |
|---|---|
Old Password | Enter the old admin password. The default password when you first get the device is algo. |
Password | Enter a new admin password to log into the device web interface. Make sure the new password is stored safely. If the password is forgotten, you must reset the device entirely with the Reset Button to restore the default password. All other settings will be reset to the original default settings as well. For additional password security, see the setting: Force Strong Password. |
Confirmation | Re-enter your new admin password. |
General | |
|---|---|
Device Name (Hostname) | Add a name to identify the device in the Algo Network Device Locator Tool. |
Introduction Section on Status Page | Turn On to show the introduction text on the login screen. |
Show Status Section on Status Page when Logged Out | Turn On to allow others to view the status page without logging in. If turned Off, the settings and configurations on the status page will be hidden entirely unless a user is logged in to ensure only trusted users can view device information. |
Display Switch Port ID on Status Page | Turn On to display the Switch Port ID on the Status Page. This option is only possible if the device is connected to a switch that supports LLDP or CDP. |
Web Interface Session Timeout | Set the maximum duration of inactivity to log a user out of the web interface automatically. |
Play Tone at Startup | The device can play a beep tone at startup. The device does not have a full speaker to play a custom audio file. |
Log Settings | |
|---|---|
Log Level | This setting should only be used after consulting with the Algo support team. |
Log Method | Select a Log Method:
|
Log Server | Enter the Syslog server address provided by your IT administrator. |
Management | |
|---|---|
Web Interface Protocol | HTTPS is always enabled on the device. HTTP is enabled by default but may be disabled. To do so, select HTTPS Only mode so requests are automatically redirected to HTTPS. Note that no security certificate exists since the device can have any address on the local network. Therefore, most browsers will provide a warning when using HTTPS. |
Force Strong Password | When Enabled, you can enforce a secure password for the device web interface for additional protection. The password requirements for a strong password are:
|
Allow Secure SIP Passwords | When Enabled, SIP passwords are stored in the configuration file in an encrypted format to prevent viewing and recovery. If enabled, navigate to Basic Settings → SIP and fill out the field Realm. To obtain your SIP Realm information, contact your SIP Server administrator or check the SIP log file for a registration attempt. The Realms may be the same or different for all the extensions used. All the configured Authentication Password(s) must be re-entered here as well as any other locations where SIP extensions have been configured to save the encrypted password(s). If the Realm is changed later, all passwords must be re-entered to save the passwords with the new encryption. |
Simple Network Management Protocol | |
|---|---|
SNMP Support | Disabled by default. The existing setting will respond to a simple status query for automated supervision. |
SNMP Community String | Speak to your IT Administrator for more information. |
SNMPv3 Security | Speak to your IT Administrator for more information. |
API Support | |
|---|---|
RESTful API | Disabled by default. Enable a secure API for remote access and device control via HTTP. For more information, see the Algo RESTful API Guide. |
Authentication Method | Speak to your IT Administrator for more information. |
RESTful API Password | Speak to your IT Administrator for more information. |
SCI Support | |
|---|---|
SCI | Disabled by default. Simple Control Interface (SCI) is a separate control interface for certain applications. Its primary purpose is to support phones that may have programmable keys that can only send out HTTP GET requests. |
SCI Password | Enter your SCI password. |
System Integrity | |
|---|---|
System Integrity Checking | Enable this feature to verify that installed system packages have not been tampered with by running a check. Enabling this feature may cause reboots and upgrades to take 30 seconds longer. Verification results can be found on the Status tab. |
InformaCast IP Speaker | |
|---|---|
InformaCast IP Speaker Support | This feature requires a valid InformaCast license to be activated. Please contact sales@algosolutions.com for assistance. |
InformaCast Scenarios API | |
|---|---|
InformaCast Scenario API Support | When enabled, a button can be configured to Start InformaCast Scenario. Input the Security Token and specify a location if applicable. |
Microsoft | |
|---|---|
Microsoft Teams Support | Enable to provision the device via Microsoft’s servers. The device reboot will take up to 5 minutes to complete, as the device will communicate several times with the Microsoft server. This feature requires a compatible release from Microsoft. |
ADMP Cloud Monitoring | |
|---|---|
Enable ADMP Cloud Monitoring | The Algo Device Management Platform (ADMP) simplifies the process of managing, monitoring, and maintaining Algo devices from any location. This feature requires a valid Account ID. To learn more about ADMP and how to purchase a license, visit the website. |
Account ID | Enter the account ID listed on the Settings page of your ADMP account. |
Allow Configuration File Sync | Enable ADMP to query and display settings stored on the device. |
Heartbeat Interval | Select how often ADMP should check the status of your device. |
Time
.png "image(76).png")
Time Settings | |
|---|---|
Time Zone | Use the dropdown to select the time zone required for your clock. |
NTP Time Server | The interface will attempt to use Timer Server 1 and work down the list if one or more of the time servers become unresponsive. These settings are pre-populated with public NTP servers hosted on the internet. To use these, the device requires internet connection. Alternatively, this can be customized to point the device to any other NTP server hosted or premise-based. |
Supersede NTP provided by DHCP | By default, if an NTP Server address is provided via DHCP Option 42, it will be used instead of the NTP servers listed above. Enable this option to ignore DHCP Option 42. |
Device Date/Time | This field shows the current time and date set on the device. If you are testing the device on a lab network that does not have access to an external NTP server, click Sync with browser to temporarily set the time on the device. This time value will be lost at power down or overwritten if connection to the NTP server is available. Time and date are used for logging purposes and the scheduler feature. |
Manually Override Time | Manual time and date are intended for testing purposes only. Time will be lost upon power down if the NTP server is reachable. |
Provisioning
Algo devices can be provisioned through a provisioning server or zero-touch provisioning (ZTP).
System administrators can provision multiple Algo devices together, eliminating the need to log into each endpoint web interface. After configuration or firmware files are placed on a provisioning server, Algo devices can be instructed to fetch these files and apply the settings.
Algo also offers a ZTP service that is meant to be used as a redirection service to your provisioning server or to configure your device with an Algo Device Management Platform (ADMP) account. ZTP is enabled by default and occurs before any other provisioning step. It will be disabled automatically after any other provisioning settings are changed on the device for the first time.
.png "image(75).png")
Mode | |
|---|---|
Provisioning Mode | Enabling provisioning allows installers to pre-configure the device on a network before installation. This is typically done for large deployments to save time and ensure consistent setups. It is recommended that Provisioning Mode be set to Disabled if this feature is not in use. This will prevent unauthorized re-configuration of the device if DHCP is used. Visit the Algo Provisioning Guide for more information. |
Settings | |
|---|---|
Server Method | Set to Auto by default. Select a Server Method.
For provisioning to work with a DHCP option, DHCP must be enabled under Advanced Settings → Network → IPv4. |
Static Server | Enter the server address or domain. |
Download Method | Select your preferred method for downloading provisioning files. The options are:
The device configuration files can be automatically downloaded from a provisioning server using DHCP Option 66. This option code (when set) supplies a TFTP boot server address to the DHCP client to boot from. A file listed below can be uploaded on the provisioning server (for access via TFTP, FTP, HTTP, or HTTPS):
Both protocol and path are supported for Option 66, allowing for http://myserver.com/config-path to be used. |
Config Download Path | Enter the path where the configuration file is located in the provisioning server (e.g., algo/config/8450). |
Firmware Download Path | Enter the path where the configuration file is located in the provisioning server (e.g., algo/config/8450). |
Partial Provisioning | Enable to allow support for “-i” incremental provisioning files. Disable for enhanced security if this is not required. |
Check-sync Behavior | Select Always Reboot to set the device to always reboot despite other settings. Select Conditional Reboot to set the device and check the provisioning server. Only reboot if a new config is found (unless “reboot=true” is provided as a parameter in the check-sync event). |
Sync Start Time | Set a time (HH:mm:ss) for the device to perform a sync according to the Check-sync Behavior setting. Leave this blank if not needed. |
Sync End Time | If set, the device will sync randomly in the window between Sync Start Time and Sync End Time. Setting an End Time earlier than the Start Time indicates an overnight period. Leave blank to lank to sync exactly at the set start time. |
Sync Frequency | Select the sync frequency. Frequency can be set to Daily or Selected Days Only. |
Sync Days | Select the days of the week for syncs to occur. |
Zero Touch Provisioning | ZTP is enabled by default but is disabled when any changes are made to the device configuration. This button can also be used to disable ZTP if no changes have yet been made to the device configuration. |
MD5 Checksum
If using TFTP as a download mode, a .md5 checksum file must be uploaded to the provisioning server In addition to the .conf file. This checksum file is used to verify that the .conf file is transferred correctly without error.
To generate a .md5 file, you can use tools such as http://www.fourmilab.ch/md5. To use this tool, simply download and unzip the .md5 program in a command prompt. The correct .md5 file will be generated in the same directory. To generate lowercase letters, use the “-l” parameter.
Generating a generic configuration file
This configuration file is device-generic in terms of MAC address and will be used by all connected 8450 devices.
If using a generic configuration file, extensions and credentials must be entered manually once the 8450 has automatically downloaded the configuration file.
To see Algo’s SIP endpoint provisioning guide, visit www.algosolutions.com/provision
Generating a specific configuration file
The specific configuration file will only be downloaded by the 8450 with the MAC address specified in the configuration file name.
Since all necessary settings can be included in this file, the 8450 will be ready to work immediately after downloading the configuration file. The MAC address of each 8450 can be found on the back label of the unit.
To see Algo’s SIP endpoint provisioning guide, visit www.algosolutions.com/provision
System Maintenance
.png "image(97).png")
Backup/Restore Configuration | |
|---|---|
Download Configuration File | Save configuration settings to a text file for backup or to set up a provisioning configuration file. |
Restore Configuration File | Restore settings by uploading a backup file. |
Restore Configuration to Defaults | This action will reset all device settings to factory defaults unless the device is registered with ZTP. If registered with ZTP, the device will reset to the defaults set by the conf ZTP file. |
Backup/Restore All User Files | |
|---|---|
Download Backup Zip File | Download the device configuration settings and the files in File Manager (ex., certificates, licenses, and tones) to a backup ZIP file. |
Restore from Backup Zip File | Restore the device configuration settings and files in File Manager (ex., certificates, licenses, and tones) by uploading a backup zip file. |
Restore All Settings and Files to Defaults | Reset the device configuration settings. All preloaded and uploaded files, including tone files, will be deleted. |
Reboot | |
|---|---|
Reboot the Device | Reboots the device. |
Firmware
.png "image(98).png")
Installed Firmware | |
|---|---|
Product Firmware | Displays the current firmware on the device. |
Online Upgrade | |
|---|---|
Check for Firmware Updates | Click Check to check for the latest firmware. If the firmware is up to date, Latest Firmware will state Firmware up to date. If your firmware is outdated, the new firmware availability will be listed. Internet connection is required. |
Custom Upgrade | |
|---|---|
Method | Select a method for firmware upgrades to occur. This can be done From Local Files or From URL. |
Signed Firmware File | Use to upgrade firmware from a local file. To do this, download the firmware file from https://www.algosolutions.com/firmware-downloads/ then upload the file by clicking on Choose File and selecting the firmware file. Click Upgrade at the bottom of the interface. Once the upgrade is complete, you can confirm the firmware version is changed by looking at the top right of the web interface. |
Upgrade URL | Instead of downloading the firmware file https://www.algosolutions.com/firmware-downloads/, you may add the download link here instead. Click Upgrade at the bottom of the interface. Once the upgrade is complete, you can confirm the firmware version is changed by looking at the top right of the web interface. |
Allow Downgrade | Enable to allow product or base firmware to be downgraded to an older patch version. Enabling this option could cause future upgrade issues. If you require downgrading, please contact support@algosolutions.com for assistance. |
File Manager
The 8450 has 818MB of storage space for additional files.
.png "image(99).png")
certs Folder
If you have enabled Validate Server Certificate under Advanced Settings →Advanced SIP or Advanced Settings → Provisioning and want to validate against additional certificates, you can upload them here.
To install a public CA certificate on the Algo device, follow the steps below:
Obtain a public certificate from your Certificate Authority (Base64 encoded X.509 .pem, .cer, or .crt).
Open the certs folder in the web interface by going to System → File Manager.
Upload the certificate files into the certs folder by clicking Upload in the top left corner of the file manager and select the certificate.
Reach out to support@algosolutions.com to get the complete list of pre-loaded trusted certificates.
debug Folder
If you have any challenges with the device and work with the Algo support team to overcome or fix them, the debug folder will be used. The device will generate files containing information about the device and put them in the debug folder. You do not need to use this folder unless directed to by the Algo support team.
images Folder
Upload images to use as backgrounds for configured pages.
license Folder
If you would like to use Informacast on a device that hasn't been bundled with an Informacast license, you will need to purchase a license and put it into the license folder in the file manager.
tones Folder
Custom audio files may be uploaded to play notifications. Audio files should be stored in the tones directory.
Existing files may be modified by downloading the original file, making the desired changes, then uploading the updated file with a different name. To download, right-click the tone and click Download.
Audio files must be in the following format:
WAV or MP3 format
Smaller than 200 MB
File names must be limited to 32 characters, with no spaces.
For further instructions, reference the Custom Tone Conversion and Upload Guide.
System Log
System log files are automatically created and can assist with troubleshooting if the device does not behave as expected.
.png "image(100).png")
Log Out
Log out of the web interface.
FCC Compliance Statement
This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy, and if it is not installed and used in accordance with the instruction manual, it may cause harmful interference to radio communications. Operations of this equipment in a residential area is likely to cause harmful interference, in which case the user will be required to correct the interference at their own expense.