8450 IP Console User Guide

The 8450 IP Console optimizes user experience and communication effectiveness for announcement broadcasting and emergency alerting. With a customizable GUI and 10.1" LCD touchscreen, the 8450 is used as an input device to activate paging or emergency alerts.

A gooseneck microphone allows for daily announcements, while touchscreen buttons can activate pre-recorded messages or alerts. The tactile, backlit Action Button can also be configured for push-to-talk, screen activation, or screen lock. Ideal for education, health, and other facilities with unique paging needs, the 8450 integrates easily into IP paging ecosystems through SIP, multicast, and REST API. Configurable via web interface and mountable to a desk, wall, or rack in landscape orientation, the 8450 adds flexibility and ease to IP paging environments.

Included

• 8450 IP Console

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

• support@algosolutions.com

Warning

This guide provides important safety information that should be read thoroughly before installing the device. It should be noted that this device:

• Is intended for dry indoor locations only with ambient temperatures of 32 °F - 104 °F (0 °C - 40 °C).

• Uses a CAT5 or CAT6 connection wiring to an IEEE 802.3at- or 802.3af-compliant network PoE switch that must not leave the building perimeter without adequate lightning protection.

• No wiring connected to the 8450 may leave the building perimeter without adequate lightning protection.

Product Overview

Related Links:

• Configuring the Action Button

Installation

The 8450 IP console is intended for desktop use.

Warning

Make sure no network cable from a PoE switch is connected to the console when assembling the stand.

Connecting power during assembly may damage the device.

To install the stand for desktop use:

1. Install the 8450 IP Console in landscape orientation onto the stand. Remove the docking station cover along the long edge of the console by removing the two Philips head screws.

2. Slide the stand tongue into the docking station gently until fully seated. The retaining screw holes should align with the console threaded inserts to re-install the two Philips head screws.

3. Adjust the friction hinge on the stand as needed by applying firm pressure to the console while holding the stand firmly in place.

4. Although the stand is weighted and equipped with high friction feet to minimize movement, two holes are provided in the stand for securing the console stand to a work surface. Use fasteners appropriate to your work surface material (not included).

5. If desired, a goose-neck microphone can be connected to the stand for live voice paging.

6. Connect a network cable from a PoE switch into the RJ45 jack on the rear of the console.

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.

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.

Getting Started

The 8450 is built for flexibility and customization to meet the communication needs of schools, healthcare facilities, and other environments that rely on reliable paging systems.

Popular use cases include:

• School paging for bell schedules, lockdowns, and zone announcements

• Hospital alerting for code blue activation and department paging

• Factory communication for shift alerts and safety notifications

• Office emergency alerting for fire drills, building evacuations, and visitor messaging

• Warehouse paging for zone-based PA and security alerts

With native support for SIP, multicast, and REST API commands, the 8450 integrates seamlessly into virtually any communication system. Even if the phone system goes down, the console’s built-in multicast functionality ensures reliable paging redundancy, as long as the network remains online. Configurable through a web interface and designed to mount to a desk, wall, or rack, the 8450 is built to adapt to any IP paging environment.

Viewing the Device IP or MAC Address

You will need the 8450 IP address to access its web interface.

To view the device IP or MAC address:

1. Connect the 8450 to an IEEE 802.3af PoE network switch.

2. The Algo logo will appear on the screen until bootup is completed (about 30 seconds).

3. Once the bootup is complete,  view the IP or Mac address from Settings .

Accessing the Web Interface

You must log in to view device settings.

The default login password is algo. You can change login password from Advanced Settings → Admin. Changing the default password is highly recommended if the device is directly connected to a public network.

To access the device web interface:

1. Type the device IP address into a web browser.

2. Log in using the default password: algo.

Checking Device Status

The Status section contains information such as your device name, IP address, and multicast mode.

To view device status:

1. Log in to the device web interface.

2. Go to Status.

Device Status Info

The following device information is available in device Status.

The available status information may vary depending on the device configuration.

Controlling Access to the Status Section

By default, the Status section is accessible to both logged-in and anonymous users. For enhanced security, you can restrict access to logged-in users only.

To show the Status page only when users are logged in:

1. Log in to the device web interface.

2. Go to Advanced Settings → Admin → General.

3. Set Show Status Section on Status Page when Logged Out to Off.

4. Select Save.

Screen Overview

This picture provides an overview of a screen layout.

Related Links:

• Displaying Your Company Logo

• Configuring Clock Settings

• Configuring Your Main Button

• Configuring the Navigation Bar

• Configuring Lock & Timeout Settings

Default Screens

The 8450 includes multiple default screens, which you can customize to suit your needs.

• Home screen

  The Home screen is the first screen shown when the device starts.

  Unlike the other default screens, the Home screen is not pre-configured. It starts as a blank screen that you can fully customize.

  You can add up to 16 buttons to the Home screen. Each button can perform an action or link to another screen, making the Home screen an ideal entry point for custom screens.

• Paging screen

  The Paging screen enables you to broadcast live announcements to specific zones, such as classrooms, departments, or building sections.

  You can also use the Delayed Paging feature to record and broadcast a message after recording.

  By default, there are six buttons with their action set to One-way Mic Multicast.

  

• Directory screen

  The Directory screen provides a searchable, scrollable list of zones and SIP extensions, offering an alternative interface for paging or SIP calling.

  You can also create a custom address book and specify which action (paging or placing a SIP call) is associated with each address.

  An address entry associated with one-way paging	An address entry associated with one-way SIP call

• Emergency screen

  The Emergency screen allows you to quickly activate pre-recorded announcements for urgent situations, such as lockdowns or medical alerts. These buttons come pre-configured but can be fully customized to suit the unique needs of each environment.

  By default, there are six buttons, with all buttons having their action set to Start Emergency Alert.

  Default Emergency screen	Default lockdown announcement screen

   

• Emergency Paging screen

  When an emergency announcement is activated from the Emergency screen, you can select Perform Live Page to open the Emergency Paging screen.

  This screen lets you broadcast live audio on top of the pre-recorded emergency announcement.

  The Emergency Paging screen can be button-based or directory-based.

  A button-based Emergency Paging screen	A directory-based Emergency Paging screen

Related Links

• Designing Your Home Screen

• Activating a Button Remotely

• Configuring the Emergency Paging Screen

Custom Screens

You can create up to 20 custom screens. Each screen supports up to 16 buttons, and each button can be assigned one of 8 different actions.

The 8450 can also send REST API requests upon initiating or ending an action. This is particularly useful for triggering tones, strobes, or screens.

Here are some examples of custom screens designed for different use cases.

Example 1 : Hospital scenario

Example 2 : Airport scenario

Example 3 : School scenario

Related Links

• Creating Custom Screens

• Button Actions

Screen Configuration

The 8450 screens are highly customizable. You can adjust visual elements such as themes, backgrounds, button colors, and clock placement to match branding or meet accessibility requirements.

You can modify the settings for both default and custom screens.

You can configure screens in two ways:

• General settings: Apply to all screens. Configure these in Basic Settings → Display (for example, button style, screen theme, and navigation bar).

• Screen-specific settings: Apply to individual screens. Configure these in the Screens tab (for example, button layout, appearance, and actions).

  Note

  When you save screen setting changes in the web interface, the device display refreshes in real time to apply the updates. During this process, you may briefly see the device reboot, flicker, or display a temporary blank screen.

Related Links:

• Configuring General Screen Settings

• Creating Custom Screens

Key Considerations for Configuring the 8450

When configuring an 8450, it is important to consider the following:

1. What general display settings are needed?

2. What screens are needed beyond the defaults?

3. What should the home screen be? The lock screen?

4. What actions need to be available on each screen?

5. What additional requirements does the device need? Passcode? Timeout?

Configuring General Screen Settings

You can configure the appearance of all screens, such as the screen theme, screen brightness, and background picture. You can also specify the number of custom screens.

General display settings apply to all screens unless overridden in the settings of a specific screen.

To configure general display settings:

1. Log in to the device web interface.

2. Go to Basic Settings → Display.

3. Configure the settings and select Save.

General Screen Settings

The following table lists general screen settings.

Related Links:

• Specifying the Number of Custom Screens

• Applying a Background Image to All Screens

• Displaying Your Company Logo

Applying a Background Image to All Screens

The 8450 includes a set of default background images that you can apply to your screens.

To apply a background image to all screens:

1. Log in to the device web interface.

2. Go to Basic Settings → Display.

3. Select a picture from the Global Background drop-down list.

4. Select Save.

Using a Custom Background Image

You can also upload your own image and use it as the screen background picture.

The recommended background image size is 1280×800 pixels. Using other dimensions may cause the image to appear cropped, stretched, or blurry.

To add a background image to the screen:

1. Log in to the device web interface.

2. Go to System → File Manager.

3. Select the folder images.

4. Drag and drop your desired image into the images folder.

5. Go to Basic Settings → Display → Global Display Settings.

6. For Global Background, select the image from the drop-down list.

7. Select Save.

Displaying Your Company Logo

You can upload and display your company logo on the screen to give it a more professional look.

The recommended logo file requirements are as follows:

• For logos intended to be placed in the screen header area, the minimum height is 53 pixels. Larger images are automatically scaled down to 53 pixels in height while maintaining their aspect ratio.

• For logos intended to be placed in the center of the screen, the maximum size is 896 × 560 pixels. Larger images are automatically scaled down to fit within this size while preserving their aspect ratio.

To display your company logo on the screen:

1. Log in to the device web interface.

2. Go to System → File Manager.

3. Select the folder logos.

4. Drag and drop your desired logo file into the logos folder.

5. Go to Basic Settings → Display.

6. For Show Logo, select Enabled.

7. For Logo, select the logo file from the drop-down list.

8. Select the Logo Position:

   • Top Left: Show the logo on the left of the screen header.

   • Top Center: Show the logo in the center of the screen header

   • Top Right: Show the logo on the right of the screen header.

   • Center: Show the logo in the center of the screen.

9. Select Save.

Applying a Theme

Themes allow you to change the visual appearance of the device quickly.

Applying a theme overrides your following settings:

• Header effect

• Clock color

• Clock size

• Navigation bar background color

• Navigation icon color

• Button appearance

To apply a theme to your screen:

1. Log in to the device web interface.

2. Go to Basic Settings → Display.

3. Go to Apply Theme and select an option from the drop-down list.

4. Select Load.

5. Select Save.

Configuring the Navigation Bar

The Navigation bar provides quick access to screens.

You can customize the navigation bar’s appearance, including the background color and the visibility of screen icons.

Hiding a screen icon does not affect the screen itself. For example, hiding the Home icon does not hide the Home screen.

To configure the Navigation Bar:

1. Log in to the device web interface.

2. Go to Basic Settings → Display.

3. Go to Nav Bar Settings.

4. Set the settings and then select Save.

Navigation Bar Settings

This table displays navigation bar settings.

Note

You can also show the Lock screen icon in the navigation bar. To display the lock icon in the navigation bar, enable Lock Icon in Nav Bar in Basic Settings → Lock & Timeout.

Configuring Your Main Button

You can use the main button to access custom screens or display the time. By default, it is linked to the Emergency screen. You can relink it to access the Paging screen, to display the time. You can also hide the main button.

Note

To avoid duplication, if the Emergency or Paging screen is assigned to the Main Button, its icon will not appear in the Navigation Bar even if it is enabled there.

To configure the main button:

1. Log in to the device web interface.

2. Go to Basic Settings → Display.

3. Go to Nav Bar Settings.

4. Select an option for Main Button:

   • None: Hide the main button.

   • Emergency: Display the Emergency screen. This is the default setting.

   • Paging: Display the Paging screen.

   • Clock: Display the time information.

5. Select Save.

Configuring Global Button Appearance

You can configure global button settings to ensure a consistent look across all buttons.

These settings are used when a button-based screen is created.

You can also override these button settings for all button-based screens in their specific screen tab.

To configure global button appearance:

1. Log in to the device web interface.

2. Go to Basic Settings → Display.

3. Go to Global Default Button Settings.

4. Set the settings.

5. Select Save.

Related Links:

• Configuring the Action for a Button

Customizing Button Appearance

You can override global button settings to customize the appearance of the button.

To customize button appearance:

1. Under Screens, go to your desired button-based screen.

2. Select Custom for Button Appearance.

3. Set the settings.

4. Select Save.

Button Settings

This table lists global button settings that apply to all screens.

Creating Custom Screens

In addition to the default screens (Home, Directory, Paging, Emergency, and Emergency Paging), you can create up to 20 custom screens.

To access a custom screen from the console display, you must link it to a button on a button-based screen, such as the Home screen. The Home screen is designed to serve as the entry point for your custom screens.

Follow the following steps to create new screens in your display:

1. Define how many custom screens you want

   When you set the number of custom screens, the system creates the same number of configuration pages under the Screens tab in the web interface.

   See Specifying the Number of Custom Screens.

2. Choose the type of each screen

   Specify whether the custom screen is a button-based screen, recording-based screen, or directory-based screen.

   See Choosing a Screen Type.

3. Configure each custom screen

   1. Configure global screen settings.

      Configure settings that apply to all of your screens, such as the screen theme, screen brightness, and background picture.

      See Configuring General Screen Settings.

   2. Configure settings specific to each screen.

      1. For button-based screens, configure the actions for each button.

         See Configuring the Action for a Button.

      2. For recording-based screens, configure settings such as whether users can delete recordings and the target paging zone.

         See Configuring a Recording Screen.

      3. For directory-based screens, configure settings such as the address book, the announcement to play, and choose whether it is a live or delayed page.

         See Configuring a Directory-based Screen.

4. Design the layout of the hosting screen, such as the Home screen

   See Designing Your Home Screen.

5. Link your custom screens to the hosting screen

   See Linking Custom Screens to a Button-Based Screen.

Specifying the Number of Custom Screens

You can add up to 20 custom screens.

Note

When you set the number of custom screens, the system creates the same number of configuration pages under the Screens tab in the web interface. To display these screens on the device, you must link them to buttons on an existing button-based screen.  It is recommended that you link them to buttons on the Home screen.

To specify the number of custom screens:

1. Log in to the device web interface.

2. Go to Basic Settings → Display.

3. In Global Display Settings, enter how many screens you want to add in Number of Custom Screens.

4. Select Save.

   Newly created configuration pages appear in the Screens section. Screens are numbered sequentially, beginning with Screen 1 (For example, Screen 1, Screen 2, Screen 3, and so on).

   

Configuring Screen Settings

The Screens tab allows you to configure each screen, such as the screen type, button layout, appearance, and actions.

Screen Type

Screens define how users interact with the system and other devices.

Depending on your needs, you can choose from different screen types to provide quick access to actions, live announcements, or paging zones.

• Button:  Create a button-based screen. You can customize buttons and link them to specified actions.

• Recording: Provide a screen for recording and paging live audio announcements using a connected gooseneck microphone.

• Directory: Create a directory-based screen. It is an address book that can be associated with paging zones or SIP extensions, allowing you to broadcast pre-recorded announcements easily.

Button-Based Screens

A button-based screen displays customizable buttons that are linked to specified actions.

For reference, see the default Emergency and Paging screens.

Use this screen type when you want quick access to frequently used commands or functions, such as initiating a live paging, triggering an announcement, or activating REST API requests.

Recording-Based Screen

A recording-based screen allows you to create audio announcements using a connected gooseneck microphone.

Use this screen type to record announcements and page it to selected zones.

Directory-Based Screens

A directory-based screen provides a searchable, scrollable list of zones and SIP extensions, offering an alternative interface for paging or SIP calling.

You can also create a custom address book and specify which action (paging or placing a SIP call) is associated with each address.

For reference, see the default Directory screen.

Use this screen type to quickly page a specific zone, or call a SIP extension.  

Choosing a Screen Type

When creating a new screen, the first step is to select a screen type.

To choose your screen type:

1. Log in to the device web interface.

2. Go to Screens. Then select your desired screen.

3. Go to the General section.

4. Select a Screen Type.

5. Select Save.

Related Links:

• Applying a Background Image to All Screens

Applying a Preset Screen for Button-Based Screens

Your device includes preset layouts for button-based screens. These presets let you quickly configure the screen’s layout and core functions.

Note

To apply a preset screen, you must select it and then load it. Otherwise, the preset screen will not be applied.

To apply a preset screen:

1. Log in to the device web interface.

2. Go to Screens. Then select your desired button-based screen.

3. Go to the Apply Preset Screen section and select an option.

   • Emergency: Create a button-based screen with a 3-Column-By-2-Rows layout. Each button with the action set as Start Emergency Alert by default.

   • Paging: Create a button-based screen with a 3-Column-By-2-Rows layout. Each button with the action set as One-way Mic Multicast by default.

4. Select Load.

   Loading a preset screen overwrites all settings on the screen, including button layout, button actions, and other configurations.

5. Change other screen settings if desired.

6. Select Save.

Configuring the Layout for a Button-Based Screen

When your screen type is Button, you can configure the layout and appearance of your buttons.

To configure the layout for a button-based screen:

1. Log in to the device web interface.

2. Go to Screens. Then select your desired button-based screen.

3. Go to the Button Screen Setting section.

4. Select a Button Layout. This defines the number of buttons on your screen and their layout.

   The corresponding sections are added to this page for button configuration.

5. Configure your Button Appearance:

   • Global: Use the button appearance settings defined in Basic Settings → Display → Global Default Button Settings.

   • Custom: Customize the button appearance.

6. Select Save.

Related Links:

• Button Configuring Global Button Appearance

Button Layout

This table lists available button layouts.

Configuring the Action for a Button

For a button-based custom screen, you must specify the action when a button is selected.

You can enable REST API support to control this button using API commands.

Button Actions

This table lists available actions for a button.

Related Links:

• Configuring REST API Requests for a Button

• Configuring the Action Button

To configure button actions:

1. Log in to the device web interface.

2. Go to Screens. Then select your desired button-based screen.

3. Go to the desired Button section.

4. Configure the button settings:

   • Button Status: To show this button on the device display, select Enabled. Otherwise, select Disabled.

   • Text: (Optional) Enter the text to display on the button.

   • Icon: (Optional) Select an icon to display on the button.

     You can upload icons to Systems > File Manager → icons and choose one from the drop-down list.

   • Action: Select an action to trigger when you select the button.

   • Identifier: (Optional) Enter a unique identifier for this button. This is required if you need to activate this button using REST API  commands remotely.

5. To enable Button Protection, select whether users must enter a passcode or confirm the action before going to the target screen.

6. Select Save.

Note

When using API requests to activate an 8450 button, button protection settings are ignored. This is because REST API access security is controlled separately through the REST API password.

Tips

You can set a button’s status to Disabled to customize the screen layout.

For example, in a 3-column × 3-row layout, disabling buttons 2, 5, and 8 creates two columns of buttons with a wide gap between them.

Configuring a Button to Place SIP Call Using Dial Pad

You can configure a button to call an SIP endpoint by entering its SIP extension.

To configure a button to place SIP call using dial pad:

1. Log in to the device web interface.

2. While configuring a button in Screens, select SIP Call with Dialpad for Action.

3. To allow remote activation of this button by other devices using REST API commands, or SIP extension, enter a unique Identifier for this button.

4. To send REST API requests along with the action, specify the following:

   • Send API Requests: Send one or more REST API requests to external devices or systems to trigger specific functions or behaviors..

   • Send API Requests on Completion: When the button action ends, send one or more REST API requests to external devices or systems to trigger specific functions or behaviors.

5. To enable Button Protection, select whether users must enter a passcode or confirm the action before going to the target screen.

6. Select Save.

Related Links:

• Configuring REST API Requests for a Button

Configuring a Button to Call a Specified SIP Extension

You can configure a button to call a specified SIP endpoint by entering its SIP extension.

To configure a button to call a specified SIP extension:

1. Log in to the device web interface.

2. While configuring a button in Screens, select SIP Call Pre-Configured Extension for Action.

3. To allow remote activation of this button by other devices using REST API commands, or SIP extension, enter a unique Identifier for this button.

4. Enter the SIP extension you want to call in Call Destination.

5. To send REST API requests along with the action, specify the following:

   • Send API Requests: Send one or more REST API requests to external devices or systems to trigger specific functions or behaviors..

   • Send API Requests on Completion: When the button action ends, send one or more REST API requests to external devices or systems to trigger specific functions or behaviors.

6. To enable Button Protection, select whether users must enter a passcode or confirm the action before going to the target screen.

7. Select Save.

Related Links:

• Configuring API Requests for a Button

Configuring a Button to Play a Pre-Recorded Audio to a SIP Endpoint

You can configure a button to play a pre-recorded audio to a SIP endpoint.

To configure a button to play a pre-recorded audio to a SIP endpoint using dial pad:

1. Log in to the device web interface.

2. While configuring a button in Screens, select Make SIP Call with Tone for Action.

3. To allow remote activation of this button by other devices using REST API commands, or SIP extension, enter a unique Identifier for this button.

4. Specify also the following:

   • Call Destination:  Specify the SIP endpoint extension.

   • Tone/Pre-recorded Announcement: Select the audio file to play.

   • Interval Between Tones (seconds): Specify the pause time before the message repeats.

   • Maximum Tone Duration: Specify how long the announcement will play.

5. To send REST API requests along with the action, specify the following:

   • Send API Requests: Send one or more REST API requests to external devices or systems to trigger specific functions or behaviors..

   • Send API Requests on Completion: When the button action ends, send one or more REST API requests to external devices or systems to trigger specific functions or behaviors.

6. To enable Button Protection, select whether users must enter a passcode or confirm the action before going to the target screen.

7. Select Save.

Related Links:

• Configuring API Requests for a Button

Configuring a Button to Page Pre-defined Audio to Zones

You can configure a button to broadcast a pre-defined audio message to selected zones.

To configure a button to page pre-defined audio to zones:

1. Log in to the device web interface.

2. While configuring a button in Screens, select Multicast with Tone for Action.

3. To allow remote activation of this button by other devices using REST API commands or SIP extension, enter a unique Identifier for this button.

4. Specify also the following:

   • Alert Name: Enter a name for the alert.

     This name appears on the display during the paging.

   • Tone/Pre-recorded Announcement: Select the audio file to play.

   • Multicast Zone: Set the target multicast zone.

   • Alert Duration: Specify how long the multicast will play.

5. To send a command to InformaCast to activate a specific predefined scenario, enable Start InformaCast Scenario. Then enter the target Scenario ID.

6. To send REST API requests along with the action, specify the following:

   • Send API Requests: Send one or more REST API requests to external devices or systems to trigger specific functions or behaviors..

   • Send API Requests on Completion: When the button action ends, send one or more REST API requests to external devices or systems to trigger specific functions or behaviors.

7. To enable Button Protection, select whether users must enter a passcode or confirm the action before going to the target screen.

8. Select Save.

Related Links:

• Configuring REST API Requests for a Button

Configuring a Button to Trigger an Emergency Alert Announcement

You can configure a button to trigger an emergency alert for the specified zones.

To configure a button to trigger an emergency alert announcement:

1. Log in to the device web interface.

2. While configuring a button in Screens, select Start Emergency Alert for Action.

3. To allow remote activation of this button by other devices using REST API commands, or SIP extension, enter a unique Identifier for this button.

4. Specify the following settings:

   • Alert Name: Enter a name for the alert. This name appears on the display during the paging.

   • Secondary Text : Enter a description for the alert. This text appears on top of the display during the paging.

   • Tone/Pre-recorded Announcement: Select the audio file to play.

   • Multicast Zone: Set the target multicast zone.

   • Tone/Pre-recorded Announcement Duration: Select to play the announcement once, or play until stopped.

   • Interval Between Tones (seconds): Specify the pause time before the message repeats.

   • Background Color: Specify the background color of the emergency alert screen.

   • Text Color: Specify the text color for the Alert Name and Secondary Text.

   • Clock: Display time and date information on the alert page.

   • Elapsed Time: Enable this option to display how long the emergency alert has been active.

   • Paging During Emergency: Enable emergency paging at the same time. Configure the paging settings in Advanced Settings > Emergency Paging.

   • Action Button During Emergency: Select Enabled to use the Action Button during an emergency alert. You need to configure the Action Button actions.

   • Play Tone/Pre-recorded Announcement on Cancel: Play another message when you cancel the emergency alert.

   • Passcode Required to Cancel: Enter a passcode before you can cancel the emergency alert. This is the passcode you set in Basic Settings → Lock & Timeout → Valid Passcodes.

5. To send a command to InformaCast to activate a specific predefined scenario, enable Start InformaCast Scenario. Then enter the target Scenario ID.

6. To send REST API requests along with the action, specify the following:

   • Send API Requests: Send one or more REST API requests to external devices or systems to trigger specific functions or behaviors..

   • Send API Requests on Completion: When the button action ends, send one or more REST API requests to external devices or systems to trigger specific functions or behaviors.

7. To enable Button Protection, select whether users must enter a passcode or confirm the action before going to the target screen.

8. Select Save.

Related Links:

• Configuring API Requests for a Button

• Configuring the Action Button

Paging During an Emergency Alert Announcement

While a pre-recorded emergency announcement is playing, you can select Perform Live Page to broadcast a live message.

If the live page interrupts the announcement, the pre-recorded audio will restart from the beginning once the live page ends. This ensures the announcement is not cut off prematurely.

To page during Emergency alert announcement:

1. From your console display, select an emergency screen. For example, the Emergency screen.

2. Select an emergency alert button.

3. When asked Are you sure?, select Proceed.

4. Select Perform Live Page to open the Emergency Paging screen.

5. Select the desired paging action.

6. Speak into the gooseneck microphone.

7. To stop paging, select Exit Live Page.

Related Links

• Configuring the Emergency Paging Screen

Configuring a Button to Multicast to Zones

You can configure a button to multicast live or with a delay to selected zones using the gooseneck microphone.

To configure a button to multicast to zones:

1. Log in to the device web interface.

2. While configuring a button in Screens, select One-way Mic Multicast for Action.

3. To allow remote activation of this button by other devices using REST API commands, or SIP extension, enter a unique Identifier for this button.

4. Specify also the following:

   • Tone/Pre-recorded Announcement: Select the audio file to play.

   • Multicast Zone: Set the target multicast zone.

5. Select a Page Mode:

   • Live: Select to page live.

   • Delayed: Select to record your audio, and then you can choose to Send or Cancel it.

     This gives you greater control over the message before it is sent.

6. To send REST API requests along with the action, specify the following:

   • Send API Requests: Send one or more REST API requests to external devices or systems to trigger specific functions or behaviors..

   • Send API Requests on Completion: When the button action ends, send one or more REST API requests to external devices or systems to trigger specific functions or behaviors.

7. To enable Button Protection, select whether users must enter a passcode or confirm the action before going to the target screen.

8. Select Save.

Related Links:

• Configuring API Requests for a Button

Configuring a Button to Start InformaCast Scenario

You can configure a button to send a call to InformaCast to initiate a Scenario.

To configure a button to start an InformaCast scenario:

1. Log in to the device web interface.

2. While configuring a button in Screens, select Start InformaCast Scenario for Action.

3. To allow remote activation of this button by other devices using API commands, or SIP extension, enter a unique Identifier for this button.

4. Specify the target Scenario ID.

5. To send REST API requests along with the action, specify the following:

   • Send API Requests: Send one or more REST API requests to external devices or systems to trigger specific functions or behaviors..

   • Send API Requests on Completion: When the button action ends, send one or more REST API requests to external devices or systems to trigger specific functions or behaviors.

6. To enable Button Protection, select whether users must enter a passcode or confirm the action before going to the target screen.

7. Select Save.

Related Links:

• Configuring REST API Requests for a Button

• Microsoft Teams Configuration with Algo IP Devices

Configuring a Button to Go to a Screen

You can configure a button to go to another screen.

To configure a button to go to another screen:

1. Log in to the device web interface.

2. While configuring a button in Screens, select Go to Screen for Action.

3. To allow remote activation of this button by other devices using API commands, or SIP extension, enter a unique Identifier for this button.

4. Specify the Target Screen.

5. To send REST API requests along with the action, specify the following:

   • Send API Requests: Send one or more REST API requests to external devices or systems to trigger specific functions or behaviors..

   • Send API Requests on Completion: When the button action ends, send one or more REST API requests to external devices or systems to trigger specific functions or behaviors.

6. To enable Button Protection, select whether users must enter a passcode or confirm the action before going to the target screen.

7. Select Save.

Related Links:

• Configuring REST API Requests for a Button

Configuring REST API Requests for a Button

You can configure up to five REST API requests to an Algo 8450 button. When you select this button, or activate it remotely, the associated REST API requests are triggered, allowing you to control the device even you are not beside it.

There are two ways to associate REST API requests with a button:

• Set Send API Request as the button Action.

• Combine REST API requests with button action.

  For example, start a SIP call and send REST API requests simultaneously.

Example Use Case: Using Multiple API Requests in an Emergency Lockdown Scenario

When a button is pressed or activated remotely, trigger the following events:

• Activate Algo ceiling speakers inside the building at a moderate volume to announce the lockdown message.

• Activate Algo horn speakers outside the building at a higher volume to alert people nearby.

• Display an emergency slide on Algo IP displays instructing occupants to follow staff directions.

• Trigger a strobe light in high-noise areas where audio announcements are not heard.

• Unlock a secured exit door via  REST API commands to allow safe evacuation.

  This coordinated action ensures that occupants, staff, and emergency responders are all notified immediately through multiple channels — audio, visual, and access control — improving both safety and response times.

To configure API Requests for a button:

1. Log in to the device web interface.

2. While configuring a button in Screens, do one of the following:

   1. Select Send API Request for Action.

   2. Set Enabled for Send API Request.

3. To allow remote activation of this button by other devices using REST API commands, or SIP extension, enter a unique Identifier for this button.

4. Select Number of API Requests.

5. Select a REST API command from Command drop-down list.

6. Enter the general command parameters:

   • Data Payload: Data to be sent in the request body.

   • Target: One or more destination devices (comma-delimited).

7. If you selected Other command type, also specify the following:

   • Method: Choose the HTTP method (POST or PUT).

   • Custom Path: Enter the custom API endpoint path. For example, /api/custom/alert.

   • Header: Provide required headers. For example, Content-Type: application/jsonor authentication tokens.

8. To enable Button Protection, select whether users must enter a passcode or confirm the action before going to the target screen.

9. Select Save.

REST API Commands for a Button

The 8450 comes with pre-configured REST API commands to allow you to perform actions such as playing a tone, or starting a strobe light.

You can also create custom REST API commands to send API requests to any third-party devices and services that accept API requests.

Examples of REST API Configurations for a Button

Here are some examples of REST API configuration for a button.

Example 1: Start a strobe light

In this configuration, when Button 2 is pressed or activated remotely,  it will send a REST API command to device 10.12.123.12 to start the strobe light, flashing in red and yellow using pattern 1 at brightness 100.

Example 2: Start a screen

In this configuration, when Button 3 is pressed or activated remotely, it triggers a REST API request to 10.12.123.12 and 10.12.123.14 to display an emergency screen. The screen shows an emergency alert image with large, white scrolling text at the bottom instructing people to follow facility staff directions.

Example 3: Trigger a third-party application workflow

In this configuration, when Button 9 is pressed or activated remotely,  it sends a POST request with JSON data to a Microsoft Azure Logic App endpoint. This will trigger a workflow (such as notifying a Microsoft Teams channel) that an Emergency Lockdown event has been activated on the Algo 8450 in the Main Office.

Configuring a Recording Screen

When creating a Recordings screen, you can configure whether users can delete recordings and specify the zone where the recording will be played.

To configure a recording-based screen:

1. Log in to the device web interface.

2. Go to Screens. Then select your desired recording screen.

3. Go to the Recording Screen Setting section and specify the following:

   • Allow Creating and Deleting Recordings: Specify whether users can delete recordings.

   • Multicast Zone: Specify a target paging zone.

   • Multicast Poly Group: Specify a Poly group to multicast to. This option is available only if you enabled one of the following in Basic Settings → Multicast → Multicast Type:

     • Poly Group Page

     • Poly Push-to-Talk

     • Regular RTP + Poly Group Page

     • Regular RTP + Poly Push-to-Talk

4. Select Save.

Configuring a Directory-Based Screen

When creating a Directory screen, you can specify the address book, pre-configure the announcement to play, and choose whether it is a live or delayed page.

When you select delayed paging, your audio is recorded, and you can choose to send or cancel it. This gives you greater control over the message before it is sent.

To configure a Directory screen:

1. Log in to the device web interface.

2. Go to Screens. Then select your desired Directory screen.

3. To apply a Preset Screen, select an option from the drop-down list:

   • Directory (Paging) - 6 Zones: Display the basic zones.

   • Directory (Paging) - 50 Zones: Display the basic and expanded zones.

4. Select Load.

5. To customize the number of zones, select your address book from the Address Book File.

   You can upload your address book to Systems > File Manager → addressbook and choose it from the drop-down list.

6. Go to the Directory Screen Setting section and specify the following:

   • Tone/Pre-recorded Announcement: Select an audio file to play before the paging begins.

   • Page Mode:

     • Live: Select to page live.

     • Delayed: Select to record your audio, and then you can choose to send or cancel it.

       This gives you greater control over the message before it is sent.

7. Select Save.

Creating a Custom Address Book

You can upload a custom address book for your directory screen.

An address book is a plain text file that defines the address, action, and SIP extension or paging zones associated with the address.

Two types of actions are available:

• Call: Initiate an outgoing SIP call.

• Page: Page to a zone.

Here are examples of entries for paging and SIP call on a directory screen.

Format of the Address Book

Each entry in the address book contains three fields, separated by tabs:

<Address_Name>    <Action>    <Target>

Where:

• <Address_Name> is the display name of the entry.

• <Action> is either Call or Page.

• <Target> specifies the destination (SIP extension, zone, or group).

Here are some address entry examples:

• To call a SIP extension:  Classroom 102    Call    1001

• To page a zone:  Main Building    Page    Zone1

• To call Poly Group phones: Main Building    Call    Poly1

• To page Poly Group zones: Main Building    Call    Zone1

• To page Regular RTP + Poly Group Page or Regular RTP + Poly Push-to-Talk:  Main Building    Page Zone4, Poly1

Note

Invalid entries in the address book are ignored by the device.

In the following example, Room 2 configuration is ignored as the delimiter for Room2 and Page is three-space, instead of a tab.

Room 1	Call	1001
Room 2 Page    1002

To create a custom address book:

1. Go to Systems > File Manager → addressbook.

2. Select Download. Use the downloaded .txt file as the template.

3. Rename it.

4. Open it using a text editing tool, such as Notebook.

5. Enter following information for each address entry:

   • Address name: Enter a descriptive name for this address.

   • Action: The action associated with the address entry:

     • Call: To initiate a SIP call to specified SIP extension.

     • Page: To start a paging to specified zones.

   • SIP extension or paging zones:

     • Enter the target SIP extension if the action is Call.

     • Enter paging zone if the action is Page.

6. Save your .txt file.

7. Log in to the device web interface.

8. Go to Systems > File Manager → addressbook.

9. Drag and drop your file into the addressbook folder.

10. Select Save.

Now, this address book appears in your Address Book File drop-down list when you configure a directory screen.

Designing Your Home Screen

Home screen is a button-based screen. Each button can perform an action or link to another screen, making the Home screen an ideal entry point for your custom screens.

When designing the Home page, consider the following:

• Button layout: Decide how many custom screens to link. For example, to link four custom screens, choose at least a Two Columns by Two Rows layout.

• Preset Screen: If the screen is used for emergency announcements or live paging, you can apply a preset screen to quickly set up the basic layout and functions.

• Action: Set the action for each button. To link a custom page, use the Go to Screen action.

• Button protection: If you need to restrict access, enable a passcode or confirmation dialog for the button.

Related Links:

• Configuring the Layout for a Button-Based Screen

• Configuring the Action for a Button

Linking Custom Screens to a Button-Based Screen

After you configure a custom screen, it will not immediately appear on the device display.

To make it accessible, you must link it to a button on an existing button-based screen, such as:

• Home screen

• Emergency screen

• Paging screen

Note

Although you can link a custom screen to any button-based screen, it is recommended to link it to the Home screen for new users. The Home screen is a blank screen and is intended for customization. Linking a custom screen to other default screens, such as the Emergency or Paging screen, may risk overriding their default designs.

To link a custom screen to an existing button-based screen:

1. Log in to the device web interface.

2. Go to Screens and select a button-based screen. For example, the Home screen.

   The screen must have a Button Layout other than None.

3. Select the desired button and set its Action as Go to Screen.

4. Select your custom screen for the Target Screen.

5. To enable Button Protection, select whether users must enter a passcode or confirm the action before going to the target screen.

6. Select Save.

   Now you can access the custom screen from the display by selecting the target screen and then selecting the specified button.

Configuring the Emergency Paging Screen

When an emergency alert is activated, you have the option to perform a live page on top of the alert through the Emergency Paging screen.

This screen allows you to broadcast live while a pre-recorded emergency announcement is playing.

This screen can only be accessed via the default Emergency screen by selecting Perform Live Page.

The Emergency Paging screen can be button-based or directory-based.

To configure the Emergency Paging Screen:

1. Log in to the device web interface.

2. Go to Advanced Settings → Emergency Paging.

3. Select the screen type:

   • Button: Display a button-based screen.

   • Directory: Display a directory-based screen.

4. Configure the screen settings.

5. Select Save.

Related Links:

• Configuring Layout for a Button-Based Screen

• Configuring a Directory-Based Screen

Configuring Clock Settings

You can configure the time and date settings, including their content, format, and style.

A clock can be shown on any configured screen or on the left side of the navigation bar (as the Main Button). You can also choose to hide the time and date from a screen.

To configure time and date settings:

1. Log in to the device web interface.

2. Go to Basic Settings → Clock.

3. Set the settings and select Save.

Related Links:

• Configuring Your Main Button

Clock Settings

This tables lists the clock settings.

Configuring Lock & Timeout Settings

For security and energy savings, the 8450 can perform a specified action after a set period of inactivity, such as displaying a wallpaper, turning off the screen, or locking the device.

You can also lock the device using the Action Button.

Related Links:

• Configuring the Action Button

Configuring Screen Timeout Settings

For security and energy savings, the 8450 can perform a specified action after a set period of inactivity, such as displaying a wallpaper, turning off the screen, or locking the device.

To configure timeout settings:

1. Log in to the device web interface.

2. Go to Basic Settings → Lock & Timeout.

3. Set the screen timeout settings:

   • User Interface Timeout: Specify the inactivity period after which the device performs a designated action.

     If you select None, no screen timeout is applied.

   • Timeout Action: Specify the action to apply when the screen inactivity time has exceeded the timeout:

     • None: No action. That is, no screen timeout action is applied.

     • Go to Home Screen: Go to the Home screen.

     • Show Image: Select an image to display.

     • Turn Off Screen: Display a blank screen.

     • Lock Screen: Lock the screen. You must enter the passcode to unlock it.

   • Timeout Image: If the device timeout action is set to Show Image, set an image to display.

   • LCD Brightness after Timeout: If the device timeout action is set to Go to Homepage or Show Image, or None use this parameter to dim the display if desired.

4. Select Save.

Configuring Screen Lock Settings

To restrict access, you can lock the screen either automatically after device bootup or manually using the Action Button.

To unlock the screen, a valid passcode must be entered. The passcode is set in Basic Settings → Passcodes.

To configure the screen lock settings:

1. Log in to the device web interface.

2. Go to Basic Settings → Lock & Timeout.

3. Set the screen lock settings:

   • Lock Icon in Nav Bar: Control whether a lock icon will appear in the navigation bar. If enabled, the device can be locked by tapping this icon.

   • Lock on Startup: If enabled, the device will enter the locked state upon starting.

   • Lock Action: Specify the action to apply when you lock the screen:

     • None: No action.

     • Go to Homepage:  Go to the Home screen.

     • Show Image: elect an image to display.

     • Turn Off Screen: Display a blank screen. Tap the display to wake it up.

   • Lock Image: If the device timeout action is set to Show Image, set an image to display.

   • LCD Brightness after Lock: If the device timeout action is set to Go to Homepage, Show Image, or None use this parameter to dim the display if desired.

   • Valid Passcodes: Select which passcode levels can unlock the device when locked. Passcodes are configured in Basic Settings → Passcodes.

4. Select Save.

Passcode Protection

Up to five distinct passcodes can be configured to limit device users to specific functions or controls.

After passcode levels are set, they can be enabled to access the device in general and activate a button action.

Share the passcodes with others who should have access at the configured level.

To configure passcodes:

1. Log in to the device web interface.

2. Go to Basic Settings → Passcodes.

3. For each passcode, do the following:

   1. Enter a descriptive name for the passcode in the left text field.

   2. Enter the passcode in the right text field.

      Note

      • The passcode can only contain numbers and can not exceed 15 digits.

      • Leaving the passcode field blank disables passcode protection (no passcode set).

4. Select Save.

Using Additional Features

You can configure the Action Button behavior, assign SIP extensions to up to 10 buttons, and customize or translate the text displayed on the 8450 device.

Configuring the Action Button

You can use the Action Button on the device to perform specific tasks. This button provides quick access to critical functions in case of an emergency.

You can also enable REST API control for this button.

To configure the Action Button:

1. Log in to the device web interface.

2. Go to Additional Features → Input.

3. Configure an action to trigger when you press, or press and hold the button:

   1. Select an action for Action When Pressed.

   2. Configure other relevant settings.

4. Configure an action for a double press (the Action Button is pressed twice in rapid succession):

   1. Select an action for Action When Double Pressed.

   2. Configure other relevant settings.

5. Select Save.

Related Links:

• Button Actions

Using the Action Button for Push-to-Talk (PTT) Paging

You can configure the Action Button to function in a Push-to-Talk mode during paging.

• To start paging, press and hold the Action Button, then speak into the microphone.

• To stop paging, release the Action Button.

Push-to-Talk mode is useful for quick or short announcements, or for intercom-style communication where the user controls when to speak.

To configure the Action Button for Push-to-Talk:

1. Log in to the device web interface.

2. Go to Additional Features → Input.

3. Select One-way Mic Multicast for Action When Pressed.

4. To allow remote activation of this button by other devices using REST API commands, or SIP extension, enter a unique Identifier for this button.

5. Select the zone to multicast to in Multicast Zone.

6. To play an audio file before the paging begins, select a file from Tone/Pre-recorded Announcement.

7. Select a Page Mode:

   • Live: Select to page live.

   • Delayed: Select to record your audio, and then you can choose to Send or Cancel it.

     This gives you greater control over the message before it is sent.

8. Select Push & Hold for Activation.

9. To send REST API requests along with the action, specify the following:

   • Send API Requests: Send one or more REST API requests to external devices or systems to trigger specific functions or behaviors..

   • Send API Requests on Completion: When the button action ends, send one or more REST API requests to external devices or systems to trigger specific functions or behaviors.

10. Select Save.

Using the Action Button During an Emergency Alert

You can use the Action Button to quickly activate paging during an emergency alert.

Before you can do this, enable Action Button During Emergency for the button that triggers the emergency alert.

Related Links:

• Configuring a Button to Trigger an Emergency Alert Announcement

Configuring Inbound SIP Extensions

You can assign an SIP extension to a button. Once configured, if you call the SIP extension, the button will be activated remotely and the associated action will be triggered.

This feature allows you to trigger specific actions even when you are away from the device, such as sending announcements, placing calls, or interacting with third-party systems.

You can assign up to 10 SIP extensions, each mapped to a different button.

Example Use Cases:

• A school staff member can call the SIP extension to make a live announcement during an emergency or important event.

• A security guard can call the SIP extension from a mobile phone to open a gate or trigger an alert.

• A facility manager can call the SIP extension to initiate pre-recorded safety or informational messages remotely.

To configure inbound SIP extensions:

1. Log in to the device web interface.

2. Go to Additional Features → Inbound SIP Extensions.

3. To require access control, select Enabled for Passcode Protection. Then set the following:

   • Passcode: enter a passcode.

     The passcode can only contain numbers and can not exceed 15 digits.

   • Passcode Prompt Tone: select a tone to indicate the user that a passcode is required.

4. In Call Timeout, select the maximum time allowed for a connection attempt.

5. Configure the SIP Extension:

   • SIP Extension #: Enable or disable the SIP extension.

   • Identifier: Enter the target button identifier, ensuring it matches the one configured for the button on its configuration screen.

   • Extension: Enter the SIP extension.

   • Authentication ID: Enter a name that represents the SIP extension. It is also referred to as ‘Username’ for some SIP servers.

   • Authentication Password: Enter 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.

   • 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.

   • Allow Interruption: Enable this option so you can interrupt the ongoing action on that button unless it is an emergency paging.

     Note

     You can’t interrupt an ongoing emergency paging.

   • Confirmation Tone: Enable this option to play a tone when the device answers the call.

6. Select Save.

Related Links:

• Activating a Button Remotely Using Its SIP Extension

Translating 8450 Device User Interface

Starting with the 5.6 firmware release, the Algo 8450 IP Console supports language translation packs to make the user-facing experience accessible in different languages. These packs replace all text that appears to end users in the console (menus, prompts, labels) with a translated version, making it easier to deploy the console in international and non-English speaking environments.

You can translate the 8450 console user interface either manually, or by uploading a language pack.

Note

Translating the console user interface does not change the administrative web user interface (Web UI) used for system setup and configuration.

Translating the Console Language Manually

You can manually edit each user interface text field and replace it with another language of your choice.

To translate the console user interface manually:

1. Log in to the device web interface.

2. Go to Additional Features → Translation.

3. Go to each user interface string section and change the translation:

   • General

   • Lock Screen

   • Emergency

   • Directory

   • Recordings

   • SIP Call

   • Paging

   • Remote Alert

   • API / InformaCast Success / Failure Messages

   • Days

   • Months

   • Time

   • Setting Bar

   • Errors

4. Select Save.

   This changes all user interface strings to your translations in the 8450 console.

Translating the Console Language Using a Language Pack

Translation packs allow you to replace user interface strings on the 8450 display with localized versions, making the device easier to use in different languages.

These packs do not affect the web interface used for administration or configuration.

Currently, a French language pack is available.

To install a language pack:

1. Download the French language config file from Algo 8450 French Language Pack.

2. Unzip the downloaded ZIP file and locate the .conf file.

3. Log in to the device web interface.

4. Go to Systems → File Manager.

5. Go to the translations folder.

6. Drag and drop your .conf file into the translations folder.

7. Go to Additional Features → Translation.

8. For the option Apply Translation Pack, select the .conf file from the drop-down list. Then, select Load.

   The translated strings will appear on the screen for preview. You can adjust individual words or phrases to match local terminology or preferences.

9. Select Save.

   This changes all user interface strings to French in the 8450 console.

Restoring the Console Language to English

You can revert the console language back to English.

To restore the console language to English:

1. Log in to the device web interface.

2. Go to Additional Features → Translation.

3. In the Translations section, select Clear.

4. Select Save.

   This changes all user interface strings back to English in the 8450 console.

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.

Advanced SIP

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 8450 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.

1. Multicast IP addresses range: 224.0.0.0/4 (from 224.0.0.0 to 239.255.255.255)

2. Port numbers range: 1 to 65535

3. 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.

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 Priority Order (Highest to Lowest)

The 8450 uses zones to organize where announcements, alerts, or music are played. Zones can be renamed or repurposed as needed, but they always follow a priority order.

This ensures that critical messages override less important audio so the most urgent information is always heard.

1. Priority zone: Reserved for critical or emergency messages. It always overrides all other paging.

2. All Call: For system-wide announcements. It plays across all zones unless interrupted by the Priority zone paging.

3. Zone 1–6: For targeted announcements to specific areas. It can be overridden by Priority or All Call paging.

4. Music zone: For background music or non-urgent audio. It has the lowest priority.

Paging a Zone Using the DTMF

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 a zone using a DTMF tone:

1. Log in to the device web interface.

2. From a SIP phone, dial the SIP extension of your 8450 device.

3. After the call connects, press the DTMF digit for the desired zone on your phone’s keypad.

4. After the call connects, speak clearly into your phone’s microphone.

   Your audio will be broadcast to the selected zone only.

5. Hang up to end the multicast.

DTMF Tones Mapping with Zones

The table lists the DTMF tones mapping with zones.

DTMF digits and their corresponding zone numbers can be found in the Advanced Settings → Advanced Multicast tab of the web interface

Advanced Multicast Settings

Audio Configuration

Basic Settings

Configuring a Console Group

You can configure multiple 8450 devices as a console group. All devices in the group must be on the same network.

When a Multicast with Tone or Start Emergency Alert action starts on one console, it will be shown on all consoles in the group.

This allows you to have synchronized notifications and alerts across all operator positions, ensuring consistent visibility and response regardless of which console initiates the action.

To configure a console group:

1. Log in to the device web interface.

2. Go to Basic Settings → Features.

3. Select Enabled for Remote Mode.

4. Enter desired 8450 devices in Console Group. Separate the IP addresses using comma.

5. To allow the device to stop the current Multicast with Tone event and start the new one, enable Allow Multicast with Tone Override.\\\

   If enabled, the device will stop the current 'Multicast with Tone' event and start the new one.

   If disabled, the device will instead say Cannot override current alert.

6. To allow the device to stop an ongoing Multicast with Tone event  within the console group, enable Allow Remote Multicast with Tone Cancel.

   If enabled, the top banner will contain the Stop Alert button.

7. Select Save.

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.

Recording Your Own Tones

You can record your own tone using a Recordings screen. The recording is saved in the recordings folder in File Manager. To use it as a tone, move it to the tones folder so it appears in the tone drop-down list.

To record your own tone:

1. From your device display, select a recording screen.

2. Select Start Recording.

3. Speak into the gooseneck microphone.

4. Select End and enter a name for the recording. Then select Save.

   The file names must be limited to 32 characters, with no spaces.

5. Log in to the device web interface.

6. Go to System → File Manager.

7. Do one of the following:

   • Drag and drop your recording into the tones folder.

   • Select Upload and choose your recording.

8. Select Save.

   Your recording will now be available in the drop-down list when you select a tone, such as for Tone/Pre-recorded Announcement or Passcode Prompt Tone.

Related Links:

• File Manager

Advanced Audio

Integration

Your device can integrate with Microsoft Teams and InformaCast.

Microsoft Teams

Algo IP endpoints are certified for native compatibility with the Microsoft Teams SIP Gateway. Applications such as IP paging, emergency alerting, and hands-free visitor communication can be implemented using both Microsoft Teams and Algo IP endpoints.

For more information on how to integrate Algo IP endpoints with Microsoft Teams, see Microsoft Teams Configuration with Algo IP Devices.

InformaCast

Algo 8450 is certified for compatibility and interoperability with Singlewire InformaCast, accommodating solutions for your voice paging, emergency notification, and alerting requirements.

For more information on how to integrate Algo IP endpoints with Microsoft Teams, see Singlewire InformaCast Guide – Testing & Configuration.

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.

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.

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.

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).

System Configuration

Network Settings

Weak TLS Ciphers

Admin

Time

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.

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

Firmware

File Manager

The 8450 has 800MB of storage space for additional files.

Addressbooks Folder

This folder contains address book files used by the Directory feature.

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:

1. Obtain a public certificate from your Certificate Authority (Base64 encoded X.509 .pem, .cer, or .crt).

2. Open the certs folder in the web interface by going to System → File Manager.

3. 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.

Icons Folder

The icons folder is used for storing icons that appear within configurable screen buttons.

Note

When icon size is set to Full Size, the icon scales to fill the entire button.

For Small, Medium, or Large icon sizes, the icon scales to fit within the button.

In all cases, the icon’s original aspect ratio is preserved.

The icons preloaded on the 8450 device are from Google Fonts Icons. You can generate your own icons from this library.

To add more icons from Google Font Icons Library:

1. Go to Google Fonts Icons.

2. Select the icon you want to use and set the following:

   • Size: Set as 200.

   • Color: Set as #373737 .

     This is the color of 8450 preloaded icons. You can also choose a different color if desired.

     

3. Select Export PNG to download the icon.

4. Log in to the device web interface.

5. Go to System → File Manager.

6. Select the recording in Files → icons folder.

7. Do one of the following:

   • Drag and drop your exported icons into the icons folder.

   • Select Upload and choose your icons.

8. Select Save.

   Your icons will now be available in the drop-down list when you select an icon for a button.

Images Folder

Upload images to use as backgrounds for configured pages.

The recommended background image size is 1280×800 pixels. Using other dimensions may cause the image to appear cropped, stretched, or blurry.

Related Links:

• Applying a Background Image to All Screens

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.

Logos Folder

Used by the logos feature to store logos that can be configured via Basic Settings → Display → Show Logo.

The recommended logo file requirements are as follows:

• For logos intended to be placed in the screen header area, the minimum height is 53 pixels. Larger images are automatically scaled down to 53 pixels in height while maintaining their aspect ratio.

• For logos intended to be placed in the center of the screen, the maximum size is 896 × 560 pixels. Larger images are automatically scaled down to fit within this size while preserving their aspect ratio.

Related Links:

• Displaying Your Company Logo

Tones Folder

You can upload custom audio files 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 meet the following requirements:

• WAV or MP3 format

• Smaller than 200 MB

• File names must be limited to 32 characters, with no spaces.

Related Links:

• Recording Your Own Tones

Translations Folder

You can upload custom language packs to change the 8450 device user interface language.

These packs replace all text that appears to end users in the console (menus, prompts, labels) with a translated version, making it easier to deploy the console in international and non-English speaking environments.

Related Links:

• Translating 8450 Device User Interface

System Log

System log files are automatically created and can assist with troubleshooting if the device does not behave as expected.

Log Out

Log out of the web interface.

Resetting the Device

A reset will set all configuration options to their factory default settings, including the login password.

You can reset the device using one of the following methods:

• From System → Maintenance → Restore Configuration to Defaults.

• Use the reset button (RST).

  Use this option if you have no access to the device web interface.

Reset Button

The 8450 has a small, round button located next to the Ethernet jack at the back of the device. You can use this Reset button to restore the device to its factory settings.

To return all the settings in the 8450 to the factory default, reboot or power cycle the 8450. To do this, wait until the blue LED on the back of the device flashes (visible in the product label), then press and hold the reset button until the LED begins a double flash pattern. Release the reset button and allow the unit to complete its boot process.

Reset the Device to Factory Default Settings Using the Reset Button

You can only reset the device to its factory settings during its bootup.

To reset the device to the factory default settings using the Reset Button:

1. Power cycle the device.

2. Wait until the blue LED flashes, then press and hold the Reset button until the blue LED starts to double-flash.

   The blue LED is located on the back of the device, and is visible on the product label.

3. Release the Reset button and allow the unit to complete its boot process.

Important

Do not press the reset button until the LED begins flashing.

A reset will set all configuration options to factory default, including the login password.

Once booting is complete, the IP address should appear on the screen if the device is in the factory reset state.

Using REST API Commands to Control Devices

Algo REST 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.

Before You Start

Enabling REST API

To allow REST API control on an Algo device, you must first enable RESTful API access on that device.

About RESTful API Passwords

When sending a REST API request, both the sender and receiver may require a password to ensure authorized access.

If the far end enables the REST API password, you must include this password in all API commands sent to that device.

Similarly, if you enable the REST API password on the 8450, any device sending API commands must also include this password in their API requests.

You can specify a far-end REST API password in one of the following ways:

• To send API requests as an 8450 button action, specify the far-end API password in  Remote Device RESTful API Password.

• Add the far-end API password in the API command

To enable RESTful API:

1. Enable RESTful API under the Advanced Settings → Admin tab.

2. Select an Authentication Method. There are three types of authentications:

   Authentication Method	Description
   Standard (recommended)	Uses a Hash-based Message Authentication Code (HMAC) with an SHA-256 encoded digest.
   Basic	Uses Base64 encoding and should only be used over HTTPS.
   None (not recommended)	Should only be used with extreme care as it provides no authentication.

3. Enter a RESTful API Password. The default password is algo.

   Once set, any device or system sending API commands to this device must include the password in the request.

4. Select Save.

Enabling SCI Support

You can enable SCI (Simple Control Interface) to support phones that may have programmable keys to send out HTTP GET requests to 8450.

To enable SCI support:

1. Log in to the device web interface.

2. Go to Advanced Settings → Admin.

3. Select Enabled for SCI.

4. Ener your SCI access password.

5. Select Save.

Activating a Button Remotely

You can activate an Algo 8450 button remotely using one of the following methods:

• Calling the SIP extension of that button.

• Sending a REST API command to control that button.

• Press a relay input trigger with REST API commands associated with that button.

  

Activating a Button Remotely Using Its SIP Extension

You can activate an Algo 8450 button remotely by calling its SIP extension.
This lets you do emergency paging, announcements, or tone playing without being near the device.

You can assign up to 10 SIP extensions, each mapped to a different button.

Note

You can not cancel the action by hanging up. However, you can configure a button to stop active actions on 8450.

See Stopping Active Actions on 8450.

Follow these steps to activate an Algo 8450 button remotely using a REST API command:

1. Configure the button with an identifier and action.

2. Configure an inbound SIP extension for the button.

3. Call the button’s inbound SIP extension.

4. If a passcode is required for the inbound SIP extension, enter the passcode followed by # after the call connects.

   For example, if the passcode is 1234, enter 1234#.

   The button will activate and trigger its assigned action.

Related Links:

• Configuring API Requests for a Button

• Configuring Inbound SIP Extensions

• Stopping Active Actions on 8450.

Activating a Button Remotely Using REST API Commands

You can activate an Algo 8450 button remotely by sending a REST API command.

This allows you to trigger actions such as emergency paging, announcements, or tone playback from another device or application.

Follow these steps to activate an Algo 8450 button remotely using a REST API command.

1. Enable RESTful API access on the 8450.

2. Configure the button with an identifier and associated action.

3. From an external device or application, send a REST API command to the 8450 target button.

   The button will activate and trigger its assigned action.

Related Links:

• Enabling RESTful API

• Configuring API Requests for a Button

• Stopping Active Actions on 8450.

Activating a Button Remotely Using a Relay Input Trigger

You can activate an Algo 8450 button remotely by configuring a relay input on another device to send a REST API request or SIP call to the 8450.

This allows you to trigger actions such as emergency paging, announcements, or tone playback from a relay input.

Follow these steps to activate an Algo 8450 button remotely using a relay input trigger.

1. On the 8450:

   • Enable RESTful API access.

   • Configure the target button with its identifier and associated action.

   • (Optional) Assign an inbound SIP extension to the button if you want to activate it by SIP call.

2. On the relay input device:

   • Set the relay input action to one of the following:

     • Send API Request: Enter the 8450 IP address, target button identifier, and action in the payload.

     • Make SIP Voice Call or Make SIP Call with Tone:  Enter the 8450 button’s SIP extension.

   When the relay input is triggered, the 8450 button is activated and its associated action is executed.

Related Links:

• Enabling RESTful API

• Configuring API Requests for a Button

• Configuring Inbound SIP Extensions

• Stopping Active Actions on 8450.

Stopping Active Actions on 8450

You can remotely stop active actions on the 8450, such as paging, SIP calls, or emergency paging.

Use one of the following methods:

• Send the API command from an API application to stop active actions on the 8450.

• Call the inbound SIP extension of a button configured an API request to stop active 8450 actions. You must enable Allow Interruption for this SIP extension.

• Remotely activate a button configured with an API request to stop active actions on the 8450.

• Trigger a relay input configured with an API request to stop active actions on the 8450.

Example 1:  API configuration for a button to stop active actions on 8450

In this configuration, when Button 8 is pressed or activated remotely,  it will send a REST API command to a 8450 device to stop all its active actions.

Example 2: Inbound SIP extension configuration to stop active actions on 8450

Related Links:

• RESTful API Guide

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.