8312 Expanded IP Paging Adapter User Guide

About

Hardware Overview

The 8312 provides interfaces for SIP paging, analog audio, radio integration, relay-controlled automation, and sensor-triggered workflows. This section describes the physical interfaces and LED indicators on the device.

Device Interfaces

This section identifies the physical interfaces on the 8312 and describes their function.

8312 Front View

8312 Back View

LED Indicators

All four blue lights will be on during power up and boot process.

Getting Started

This section describes how to install the 8312, access its web interface, and perform the initial SIP configuration.

Installing the Device

The 8312 is wall-mountable in a horizontal orientation using the supplied bracket. Example installation on ½” drywall:

1. Use appropriate drywall anchors for #8 screws, and predrill per the anchor manufacturer’s instructions. Insert 4 anchors into the wall, and then attach the bracket to the wall anchors using #8 screws.

2. Snap the 8312 into the bracket.

3. Connect the 8312 to a PoE network switch.

4. (Optional) Connect the PAGE AUDIO OUT (terminal block or 3.5 mm jack) to an amplifier. The 8312 provides an isolated (dry) audio output and dry contact closure.

Obtaining the Device IP Address

You will need the device IP address to access its web interface. You can find the device IP address using one of the following methods:

• Use the RESET button to let the device announce its IP address.

• Use Algo Network Device Locator Tool.

• Use other network discovery methods.

To obtain the device IP address using the device RESET button:

1. Connect the device to a PoE network switch.

2. Connect a headset to the AUX OUT port.

   Caution

   The 'Page Audio' Output Level is set to the highest level (+4dBU 10k), by default. This setting may be too loud for headset output. Before putting on the headset, adjust the volume under Basic Settings → Features → Audio → 'Page Audio' Output Level and select a lower value.

3. The blue SIP LED will turn on until boot-up is completed (about 1 minute).  

4. After the SIP LED turns off, locate the sunken RESET button on the front panel. Press the RESET button using a straightened safety pin. Once pressed, you will hear the IP address over the headset.

5. After you have noted down the IP address, press the RESET button again to stop the repetitive announcement.

Alternative Methods to Obtain Device IP

Accessing the Web Interface

You can configure the device through its web interface. The web interface does not require an additional purchase. All settings, integrations, and file uploads can be accessed via the web interface.

To access the device web interface:

1. Enter the device IP address into your web browser.

2. Log in using the default password: algo.

Note

This password can be changed in Advanced Settings → Admin tab after you log in for the first time. It is highly recommended to change the default password if the device is directly connected to a public network.

Logging out of the Device

Use the Logout tab to securely end your current web interface session. Logging out helps prevent unauthorized access to the device, especially when using a shared or public computer.

To log out from the device web interface:

• Select the Logout tab.

Changing the Login Password

You can change the login password in Advanced Settings → Admin tab. It is highly recommended to change the default password if the device is directly connected to a public network.

To change the  login password:

1. Go to Advanced Settings → Admin → Management.

2. Enter the Old Password.

3. Enter your new Password.

4. Repeat the new password in Confirmation.

5. Select Save.

   The device reboots to apply the new setting.

Login Password Requirements

The login password requirements depend on the Force Strong Password setting.

To enable strong password:

1. Go to Advanced Settings → Admin → Management.

2. Set Force Strong Password to Enabled.

3. Select Save.

   Before you can save the changes, your login password must meet the strong password requirements listed above. If it does not, change your login password first.

Making Your First SIP Call

This procedure demonstrates the minimum configuration required to place a SIP paging call.

To make your first SIP call:

1. Go to Basic Settings → SIP.

2. Enter the SIP server IP address or domain name into SIP Domain.

3. Enter the following. This information will be available from your IT Administrator.

   

   • Page Extension

   • Authentication ID

   • Authentication Password

4. Make a call to the 8312 by dialing the SIP extension of the 8312 from a telephone, IP phone, or SIP application.

   After completing the initial SIP configuration, you can configure additional features such as ring extensions, multicast paging, emergency alerts, relay-triggered actions, background music streaming, and scheduled announcements.

Viewing Device Status

The web interface has a Status page which, by default, is available both before and after login.

Depending on your device configuration and firmware version, the Status page may display the following information:

Restricting the Status Page to Logged-In Users

The Status page can be restricted to logged-in users.

To restrict the Status page to logged-in users:

1. Go to  Advanced Settings → Admin → General.

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

3. Select Save.

Customizing Your Status Page

You can customize the content of the Status page.

To customize your status page:

1. Go to Advanced Settings → Admin.

2. Configure the General section:

   • Introduction Section on Status Page: Select whether to show the introduction text on the login screen.

   • Display Switch Port ID on Status Page: Select whether to display the switch port ID on Status page.

3. Select Save.

Register Your Product

Register your product to receive the latest firmware and product updates, important service notifications, and a 3-year extended warranty for IP products.

To register your product:

• Do one of the following:

  • Go to https://www.algosolutions.com/product-registration/.

  • Scan this QR code:

    

Security

Algo devices use TLS for provisioning and SIP signaling to help protect against cyberattacks that attempt 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.

Wiring Connections

This section describes how to connect the 8312 to external devices. It includes wiring examples for connecting the 8312 to a paging amplifier, as well as instructions for connecting relay and sensor input devices to the SMART RELAY and SENSOR INPUTS for event-triggered automation.

Wiring an Amplifier

The wiring diagram below illustrates one of the most common use cases, where the PAGE AUDIO OUT of the 8312 is connected directly to the dry audio input on an amplifier with an input impedance between 600 Ohm and 10k Ohm.

The optional dry contact closure can be used to activate the amplifier(if required).

The output level of the 8312 can be adjusted to match the amplifier’s input specification.

To adjust the audio output level of the 8312:

1. Go to Basic Settings → Features → Audio.

2. Select a 'Page Audio' Output Level.

Wiring an Input Device to the SMART RELAY or SENSOR INPUTS

Note

The 8312 does not support the direct connection of dynamic microphones. Direct connection of a dynamic microphone to the 8312 may result in no audio or improper operation.

To connect a dynamic microphone (e.g., Sennheiser E835), which does not require phantom power, an Algo 1205 Audio Interface is required. The 1205 provides the necessary preamplification, impedance matching, and interface to ensure proper audio input.

You can connect compatible Algo accessories or third-party dry-contact devices to the SMART RELAY or SENSOR INPUTS of the 8312.

You will need the following:

• Pluggable terminal blocks (included in the 8312 package)

• A single twisted-pair (24 AWG)

To wire a relay input device or sensor input device to the 8312:

1. Connect the two pluggable terminal blocks to the CONNECTOR A and CONNECTOR B sections of your 8312 respectively.

   

2. Connect one end of a single twisted-pair (24 AWG) to your input device.

3. Strip approximately 6–8 mm (1/4–5/16 in.) of insulation from the other end of the single twisted-pair.

4. Do one of the following:

   • To connect a sensor input device, choose terminals from SENSOR INPUTS 1 - 12.

   • To connect a relay input device, select the SMART RELAY terminals.

5. Use your finger or a small flat-head screwdriver to press down the corresponding orange release button next to the terminal. Keep the button pressed while inserting one conductor of the wire into the round opening below the button.

   

6. Release the orange button, then gently pull on the wire to verify that it is securely locked in place.

7. Repeat steps 5 and 6 to connect the other conductor of the single twisted-pair to the bottom terminal.

Related Links:

• Configuring an Action for Your SMART RELAY or SENSOR INPUT

Compatible Algo Input Devices

The following Algo devices can be the SMART RELAY-compatible input devices.

1202 Call Button

Connect the center contacts of the modular connector on the back of the 1202 to the SMART RELAY terminal block (not polarity-sensitive) on the 8312.

1203 Call Switch

Connect a single twisted-pair (24 AWG) from the device's terminal block to the SMART RELAY terminal block (not polarity-sensitive) on the 8312.

1204 Volume Control Switch

Connect a single twisted-pair (24 AWG) from the device's terminal block to the SMART RELAY terminal block (not polarity-sensitive) on the 8312.

1205 Audio Interface

Two pairs of wires connect the 1205 Audio Interface to the 8312. One pair carries balanced audio, and the other communicates the rotary switch position.

To connect a 1205 to the 8312:

1. Connect the Relay Input switch terminals (not polarity-sensitive) on the 1205 to the SMART RELAY terminal block on the 8312.

2. Connect the Line In audio terminals (not polarity-sensitive) on the 1205 to the LINE IN terminals on the 8312.

Algo 2507 Ring Detector

Connect a single twisted-pair (24 AWG) from the device's terminal block to the SMART RELAY terminal block (not polarity-sensitive) on the 8312.

Algo 1211 Single Button and Algo 1212 Dual Button

Connect a single twisted-pair (24 AWG) from the 1211/1212's terminal block to the SMART RELAY terminal block (not polarity-sensitive) on the 8312.

Wiring an Output Device to the Relay Output

The PAGE RELAY terminals provide a dry contact closure when triggered.

You can connect an external device that is activated by opening or closing a circuit, such as a strobe light, door strike, magnetic lock, or other relay-controlled equipment.

To wire an output device to the Relay Output:

1. Disconnect power from the external device, if applicable.

2. Connect the control wires (AWG 24) from the external device to the PAGE RELAY terminals (not polarity-sensitive) on the 8312.

3. Restore power to the external device, if applicable.

Related Links:

• Trigger Actions Using Relay Output

Configuring Additional Ring Extensions

Configure additional ring extensions to support different incoming ring events, such as loud ringing. Using more ring extensions allows different ringtones to be played for each unique extension to identify which extension is ringing.

Up to 10 SIP ring extensions can be registered.

Note

Ring tones associated with Additional Ring Extensions are output only through the PAGE AUDIO OUT interfaces (terminal block and 3.5 mm jack) and AUX OUT.

Note

Ring extensions should not be used for emergency alerts, as emergency notifications are intended to play continuously until manually stopped.

For emergency alerts, see the Emergency Alerts.

To configure additional ring extensions:

1. Go to Additional Features → More Ring Extensions.  

2. Select Enabled beside the extension of interest.

3. Enter the following information. This information will be available from your IT Administrator.

   • Extension

   • Authentication ID

   • Authentication Password

   • Display name (Optional)

4. Select a Ring Tone.

   If you select <Use Default Ring Tone>, the tone specified in Basic Settings → Features → Inbound Ring Settings → Ring/Alert Tone plays.

5. Select Save.

   When the Ring Extension is dialed, the Ring Tone is played on the PAGE AUDIO OUT (terminal block and 3.5 mm jack) and AUX OUT interfaces.

Related Links:

• Using Loud Ringing

Using Rule-Based Ringtones

Set a rule-based ringtone for the device to play a custom ringtone based on the caller's identity. When enabled, the device will play the selected ringtone for callers with a display name or extension that matches the rule.

Note

Rules are tested starting at #1 Custom Tone, so the first rule to match determines the ring tone file that is played. If no rules match, then the default tone in Basic Settings → Ring is played.

To configure rule-based ringtones:

1. Go to Additional Features → More Ring Extensions.

2. Go to the Rule-Based Ringtone section and select Enabled beside a custom tone.

3. Enter the following information:

   1. Use a Regular Expression (regex) to set the Rule.

      • ^ means that the text must be at the beginning of the Caller ID string. So ^Group1 matches all strings that start with the text Group1 (e.g., Group1 555-123-4567 ).

      • $ means that the text must be at the end of the Caller ID string. So $123 matches all strings that end with 123 (e.g., Steve123).

      • For an exact match, use both of the above. Thus, ^Steve$ matches only the string Steve .

      • If none of the special characters above are used, then it will match the text anywhere in the string. So a rule of just Steve will match both 123 Steve and Steve 123.

      • For a default case, use .*  which matches everything (any number of any characters), including blank.

   2. Select a Ring Tone to play for calls from callers matching the specified rule.

4. Select Save.

Using Custom Ringtones

You can enable a custom ring to play a custom ringtone when receiving calls with the Alert-Info SIP header.

To enable custom ringtones:

1. Go to Additional Features → More Ring Extensions.

2. Go to the Custom Ring Tone section and select Enabled.

SIP Paging

The 8312 supports SIP-based voice paging for both single-device and multi-endpoint deployments. When configured with a SIP extension, the 8312 can receive live voice pages from a telephone, SIP client, or other device. For larger deployments, the 8312 can also act as a multicast transmitter, allowing one SIP-registered adapter to stream audio to multiple Algo IP endpoints without requiring each receiver to register individually with the SIP server.

Related Links:

• Multicast Paging

Additional configurations

If VLAN is used, navigate to the Advanced Settings → Network tab to set VLAN options. Once the device is using VLAN you will need to be on the same VLAN to access the web interface.

Additional configurations can be made to meet the needs of the environment. This includes:

• Enabling the G.722 audio code for increased speech intelligibility.

• Enabling ambient noise monitoring for the speaker volume to automatically adjust based on background noise.

• Enabling talkback to allow those near the speaker to communicate with the caller.

SIP Calling to a Single Device

A common application of the 8312 is voice paging via SIP. SIP allows Algo IP products to register with most hosted/cloud or on-premise telephone systems to broadcast voice messages to multiple IP endpoints over a network in real-time.

You can activate the 8312 by dialing its assigned SIP extension from a telephone, device, or client. The device will auto-answer, play the default pre-announce tone, and allow voice paging until disconnected.

To configure your SIP paging settings:

1. Go to Basic Settings → SIP.

2. Enter the SIP server IP address or domain name in SIP Domain (Proxy Server).

3. Enter a Page Extension and its credentials:

   • Authentication ID

   • Authentication Password

     Note that some SIP servers may say Username instead of Authentication ID.

   • Display Name

4. Configure Audio Output:

   • Page Audio Output: Sends audio to the AUX OUT and PAGE AUDIO OUT interfaces.

   • Radio Audio Output: Sends audio to the RADIO and AUX OUT interfaces.

   • Both: Sends audio to the PAGE AUDIO OUT, RADIO, and AUX OUT interfaces.

5. Go to Basic Settings → Features and configure Inbound Page Settings.

6. Go to the Status tab and make sure that the Page registration is successful.

   

7. Dial the assigned extension from a telephone, device, or client.

   The 8312 will auto-answer, play the default pre-announce tone, and allow voice paging until disconnected.

Related Links:

• Inbound Page Settings

Configuring Additional Page Extensions

Using more page extensions is an alternative way to select several different multicast zones to page to when the device is configured as a multicast transmitter.

Additional SIP page extensions can be registered for each multicast zone. This enables you to dial a zone directly without entering DTMF codes; however, this may require additional SIP licenses depending on the SIP provider. Some SIP telephone systems may not support this capability or have a limit on the number of extensions registered on a single device.

Some considerations when choosing to use multiple extensions over DTMF include:

Note

Audio from SIP calls using Additional Page Extensions is output only through the PAGE AUDIO OUT interfaces (terminal block and 3.5 mm jack) and AUX OUT.

To configure additional page extensions:

1. Go to Additional Features → More Page Extensions.

   

2. Select Enabled beside the extension of interest.

3. Enter the following information. This information will be available from your IT Administrator.

   • Extension

   • Authentication ID

   • Authentication Password

   • Display Name (Optional)

4. Select Save.

   The device will auto-answer any inbound calls received on these numbers, establish a voice paging path, and multicast audio to the associated transmit zone if configured. Only a single call can be active at a time.

Related Links:

• SIP Paging

Emergency Alerts

Your device can be used for alerting in the case of emergency (e.g., lockdown, evacuation, reverse evacuation), safety (e.g., medical, workplace accident), and security events (e.g., OSHA or similar workplace regulations).

Emergency alerts allow you to quickly broadcast prerecorded announcements to local outputs and multicast receivers during emergency situations.

Note

Emergency announcements are output through the following local interfaces:

• PAGE AUDIO OUT

• AUX OUT

If the device is configured as a multicast transmitter, the announcements are also transmitted via multicast to the configured receiver devices.

You trigger emergency alerts using one of the following ways:

• Direct Extension: Dial the extension associated with the desired emergency announcement.

• DTMF Selectable: Dial the Extension for DTMF Selection. After the call connects, enter the desired announcement ID using DTMF tones.

Follow these steps to configure and use emergency alerts:

1. Configure how emergency alerts are triggered:

   • Configuring Direct Extensions for Emergency Alerts

   • Configuring DTMF Extensions for Emergency Alerts

2. Configuring Emergency Announcements

3. Triggering Emergency Alerts

Configuring Direct Extensions for Emergency Alerts

You can dial a pre-configured extension number to trigger and play an emergency alert continuously. 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.

To configure direct extensions for emergency alerts:

Related Links:

• Emergency Alerts Settings

Configuring DTMF Extensions for Emergency Alerts

You can dial a single DTMF extension, enter the desired announcement ID using DTMF tones.

To configure a DTMF extension for emergency alerts:

Configuring Emergency Announcements

Configure how the selected emergency announcement is played, including its playback duration, audio source, multicast destination, and optional REST API requests that are sent when the announcement starts or completes.

To configure an Emergency Announcement:

1. Go to Additional Features → Emergency Alerts → Announcements.

2. Set the desired Announcement to Enabled.

3. Configure the following:

   • Announcement Duration:

     • Play Once: Plays the selected audio file once.

     • Play Until Cancelled: Plays the announcement continuously until the Call-to-Cancel extension is dialed or the Maximum Announcement Time is reached.

     • Default: Uses the value configured for Default Announcement Duration.

   • Maximum Announcement Time: Select the maximum announcement time.

   • Extension: Specify the announcement extension.

     This option is available only when the Announcement Selection Mode is set to Direct Extensions.

   • Tone/prerecorded Announcement: Select a file or audio input to use as the announcement:

     • <Use Audio Input Port>: Use the audio input specified in Additional Features → Features → Emergency Alerts → Settings → Audio Input Port.

     • <Use Default Ringtone>: Use the ringtone specified in Basic Settings → Features → Ring/Alert Tone.

   • Interval Between Tones (seconds): Specify the interval between tone playbacks, in seconds.

   • Confirmation Tone: Select a file to use as a confirmation tone.

     This option is available when Answer Inbound Call is enabled.

   • Multicast Zone: Set the RTP multicast zone where announcements will be played.

   • Multicast Poly Group: Set the Poly Group where announcements will be played.

     This option is available only when your Multicast Type is set to one of the following:

     • Poly Group Page

     • Poly Push-to-Talk

     • Regular RTP + Poly Group Page

     • Regular RTP + Poly Push-to-Talk

4. To send REST API requests to external devices or systems when the announcement starts, enable and configure Send API Requests.

5. To send REST API requests to external devices or systems when the announcement completes, enable and configure Send API Requests On Completion.

6. Select Save.

Triggering Emergency Alerts

You can trigger an emergency alert using one of the following announcement selection modes:

• Direct Extension: Dial the configured Extension assigned to the desired emergency announcement.

• DTMF Selectable: Dial the Extension configured for DTMF Selection. After the call is connected, enter the desired announcement ID using DTMF tones.

The announcement is selected according to the following mapping:

Note

If Call-to-Cancel Selection Mode is configured to use DTMF 0, Announcement 10 is unavailable because the 0 key is reserved for canceling the announcement.

In this configuration, only Announcements 1–9 are available.

The 8312 can be programmed as a multicast transmitter or receiver and can be grouped into up to 50 multicast zones. Multicast allows a single transmitting device to simultaneously stream audio to multiple receiving devices over the network. To optimize the use of a single SIP extension, the 8312 can be used as a multicast transmitter to stream audio to other Algo receiver devices. Any number and combination of Algo Speakers, Paging Adapters, IP Displays, or Visual Alerters can be set as receiving devices. Receiving devices do not require a unique SIP extension and, therefore, do not need to be registered with the SIP server.

In large environments, it is recommended that the device configured as the multicast sender be stored securely to mitigate the risk of interference or damage. The 8312 is most often used in these scenarios. In a smaller environment or when needed, the 8312 or other devices can also be configured as the multicast sender.

Key Configurations for Multicast Transmitters and Receivers

Ensure the following settings are correctly configured and consistent between the transmitter and receiver devices. These settings depend on your Multicast Mode setup:

• Multicast Mode (under Basic Settings → Multicast)

  • Sender: Set to Transmitter

  • Receiver: Set to Receiver

• Multicast Type (under Basic Settings → Multicast)

  • Both Sender and Receiver should be set to the same Multicast Type. Normally, it’s Regular (RTP) unless Poly devices are involved.

• Zone Number (under Basic Settings → Multicast)

  • Confirm the Transmitter Single Zone selected on the Transmitter is also enabled under the Basic Receiver Zones on the Receiver.

• Zone Definitions (under Advanced Settings → Advanced Multicast)

  • Verify that the IP Address and Port Number for the multicast zone match exactly on both the Transmitter and Receiver devices.

Configuring Your Device as a Multicast Transmitter

The Algo IP endpoint configured as the transmitter will stream audio to all of the receivers simultaneously. Receiver endpoints do not require SIP extensions and do not need to register with the SIP Communication Server.

The page pre-announce tone is generated from the transmitter. The speaker volume can be increased or decreased for each multicast receiver individually.

Note

Always ensure that the multicast settings on all receiver devices match those of the transmitter.

To configure your device as a Multicast Transmitter:

1. Go to the Basic Settings → Multicast.

2. Configure Multicast Mode settings:

   • Multicast Mode: Set to Transmitter (Sender).

   • Multicast Type: Select an option.

     • Regular (RTP): Multicasts only to Algo IP endpoints or multicast-enabled phones.

     • Poly Group Page or Poly Push-to-Talk: Multicasts to Poly phones.

     • Regular RTP + Poly Group Page or Regular RTP + Push-to-Talk: Multicasts to Poly phones, Algo IP endpoints, and multicast-enabled phones.

       Note

       Make sure your multicast receivers be set to the same Multicast Type. Normally, it’s Regular (RTP) unless Poly devices are involved.

   • Number of Zones:

     • Basic Zones Only: Uses nine or fewer multicast zones.

     • Basic and Expanded Zones: Uses 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.

3. Configure Transmitter (Sender) Zone Settings:

   • Zone Selection Mode:

     • Single Zone: Broadcasts on one pre-configured zone. Multiple SIP extensions can be registered on the Transmitter device. Each extension is mapped to a unique zone, allowing zones to be called directly (e.g., from speed-dial keys).

     • DTMF Selectable Zone: Selects the zone by the DTMF key.

   • Transmitter Single Zone: Selects the default zone for the multicast stream to be sent to.

     Note

     • If the DTMF Selectable Zone is chosen, this single zone setting will not apply to Paging since the zone will be dynamically selected per call using DTMF. However, this single zone setting will still apply to the ring extension and relay triggered events.

     • When you configure the multicast receivers, make sure this zone is selected in the Basic Receiver Zones .

   • Speaker Playback Zones: Specifies which basic zones the device can play audio.

   • Expanded Speaker Playback Zones: Specifies which expanded zones the device can play audio.

4. If your Multicast Mode includes Poly Group Page or Poly Push-to-Talk, configure also the following:

   • Poly Zone: Enter the same Multicast IP Address and Port number configured on the Poly phones.

   • Poly Group Selection Mode:

     • Single Group: Broadcasts on one pre-configured group. Multiple SIP extensions can be registered on the Transmitter device. Each extension is mapped to a unique group, allowing groups to be called directly (e.g., from speed-dial keys).

     • DTMF Selectable Group: Selects the group by the DTMF key.

   • Poly Default Channel: Selects the default group for the multicast stream to be sent to.

     The Poly Default Channel is the default channel used for multicast actions unless an option is available for a custom channel with specific parameters.

     Note

     If DTMF Selectable Group is chosen, this single group setting will not apply to paging since the group will be dynamically selected per call using DTMF. The Single Group setting will still apply to the ring extension and relay triggered events.

   • Speaker Playback Groups: Selects Speaker Playback Groups to control which specific groups can play audio from the device.

     This is useful if using the DTMF Selectable Group mode or additional page extensions (Additional Features → More Page Extensions) per group to make the device a member of only certain zones. In this case, the Transmitter does not participate in the Zone but transmits certain traffic.

5. If your Poly Group Selection Mode is set to DTMF Selectable Zone or DTMF Selectable Group, configure how to use the DTMF keys:

   • Zone Selection Tone: Select a tone to be played to prompt a user to select a zone to multicast to.

     This may be used as an interactive voice response (IVR) menu by uploading a custom audio file in the tones folder through System → File Manager. Each zone may use a different tone. This can be configured in Advanced Settings → Advanced Multicast.

   • Two Digit Selection: When enabled, all DTMF Selectable Zones will require two digits. As a result, Basic Zones and Poly group 1-9 must be prefixed with 0, and Expanded Zones or Poly Group 10-25 will no longer need to be prefixed with *.

6. Select Save.

   
   

Configuring Your Device as a Multicast Receiver

Configure your device as a multicast receiver to play multicast audio streams transmitted by another multicast-enabled device. In receiver mode, the device listens for multicast traffic on one or more configured zones and automatically plays paging announcements, emergency alerts, scheduled bells, background music, or other multicast audio without requiring its own SIP registration.

This allows a single transmitter to distribute audio simultaneously to many receivers while minimizing SIP licenses, network bandwidth, and system complexity. Each receiver uses its own local playback volume settings independently of the transmitter.

To configure your device as a Multicast Receiver:

1. Go to the Basic Settings → Multicast.

2. Configure Multicast Mode settings:

   • Multicast Mode: Set to Receiver (Listener).

   • Multicast Type: Select an option.

     Note

     Make sure you select the same Multicast Type as your Multicast Transmitter (Sender).

     • Regular (RTP): All multicast receivers are Algo endpoints. The device will listen to the selected Basic Receiver Zones or Expanded Receiver Zones.

       The zone IP addresses are defined in Advanced Settings →  Advanced Multicast.

     • Poly Group Page or Poly Push-to-Talk: There are Poly phones in the multicast. The device will listen to selected Poly Channels.

       The Poly Group IP address is specified in Poly Zone.

3. Specify the zone or Poly Group settings:

   Note

   Make sure you select the same zones/channels as your Multicast Transmitter (Sender).

   • Select Zones:

     • Basic Receiver Zones: Select the desired basic zones.

     • Expanded Receiver Zones: Select desired expanded zones, if available.

       Note

       Make sure the Receiver Zones include the Transmitter Single Zone selected on your Transmitter device.

   • Select Poly groups:

     • Poly Zone: Enter the same Multicast IP Address and Port number configured on the Poly phones.

     • Poly Receiver Channels: Select the desired channels.

4. Select Save.

Configuring Multicast Zones

Each 8312 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 zone members. The multicast IP and port number must be the same on all transmitter and receiver units of the same zone. 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, all Algo devices are set to use the multicast IP address 224.0.2.60 and the port numbers 50000-50008.

Note

• Ensure the multicast IP address and port number do not conflict with other services and devices on the same network.

• Make sure that the IP Address and Port Number for the multicast zone match exactly on both the Transmitter and Receiver devices.

Notes

Ensure the IP Address and Port # match on both the Transmitter (Sender) and Receiver (Listener), for the zone being used.

To configure Multicast zones:

1. Log in to the web interface of your multicast transmitter or receiver device.

2. Go to Advanced Settings → Advanced Multicast.

3. View the default zone IP Address and Port. Edit it if necessary.

4. To specify a different tone to play before the multicast starts, select an audio file from the Page Tone drop-down list.

   If you select <Use Default Page Tone>, the audio file specified under Basic Settings → Features → Inbound Page Settings → Page Tone plays.

5. Select Save.

Multicast Page Zones

By default, the 8312 can listen to nine basic multicast zones; however, up to 50 are available (See Additional Features → More Page Extensions for more details). 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

Multicast Page Zone Priority

When set as a multicast receiver, zones have a priority hierarchy where zones higher on the list will be treated with higher priority, with Music being the lowest priority. When set as a multicast transmitter, event priority is based on the event type that initiated the multicast rather than the output multicast channel that will be active.

Multicast Triggers

As a multicast transmitter, the multicast is triggered in the following events, with the audio content broadcast to receivers in the selected multicast zone. The type of content that is broadcast depends on what triggers the multicast.

Triggering a Multicast Using a Page Extension

There are two options for initiating a multicast:

• DTMF Selectable Mode: Has a 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 or Poly group (e.g., 1, 2, etc.) on the keypad.

  Note

  When using the DTMF Selectable Mode, DTMF digits are not passed through to the output channel.

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

• Multiple page extensions: Multiple SIP extensions can be registered on the transmitter. Each extension is mapped to a unique zone or group, allowing zones to be called directly.

  See Additional Features → More Page Extensions tab of the 8312 web interface for more details.

Alternatively, multiple SIP extensions can be registered on the sending device. Each extension is mapped to a unique zone, allowing zones to be called directly (for instance, from speed-dial keys) without the use of DTMF. See Additional Features → More Page Extensions tab.

‘Expanded’ zones can also be enabled, allowing up to 50 zones in total. These have the same behaviors as the basic zones but are hidden by default to simplify the interface.

To multicast using DTMF Selectable Zone:

1. Dial the SIP extension of the Transmitter device.

2. Dial the desired DTMF page group number on the keypad when prompted. Groups 10 and higher start with *.

To multicast using zone extension:

• Dial the SIP extension of the desired zone of the Transmitter device.

Algo Zone/Poly Group and DTMF Extension Mapping (Two-Digit Selection Disabled)

Basic zones or groups use a single digit, while expanded zones (10–50) or groups 10-25 require an asterisk (*) prefix.

Every zone must be entered using exactly two digits.

Triggering Actions Using Relay Input/Output and SENSOR INPUTS

You can use terminal blocks (Relay Input/Output or SENSOR INPUTS) to interface with a wide range of devices for applications such as alerting, access control, SIP calls, and API calls.

This is useful for applications such as emergency buttons, doorbells, and sensor-based notifications.

You can connect normally open or normally closed switches, or compatible Algo input devices (e.g., 1202 Call Button, 1204 Volume Control Switch, 1211 Single Button, 1212 Dual Button).

Configuring an Action for Your SMART RELAY or SENSOR INPUTS

You can configure an action when a SMARY RELAY or SENSOR INPUT is triggered, or when tampering is detected for a supervised relay input device connection.

To configure an action for your SMART RELAY input:

1. Wire a relay input device to the SMART RELAY terminals of your 8312.

2. Log in to your 8312’s web interface.

3. Go to Additional Features → Input/Output.

4. Select a Relay Input Mode that matches the connected device.

   Note

   Always select the matching Relay Input Mode. For example:

   • For Algo 1202, select Algo 1202 Call Button.

   • For a third-party call button, select Relay Normally Open.

5. Configure Action When Input Triggered and the associated settings.

6. For relay input trigger that supports fault detection, configure how the wiring faults should be detected:

   • Detect Open Circuit Fault Only: Triggers action when an open circuit fault is detected.

   • Detect Both Open Circuit & Short Circuit Faults: Triggers action when either open or short circuit faults are detected.

     Note

     Detection thresholds:

     • Open Circuit detection will trigger when the current draw is <4mA.

     • Short Circuit detection will trigger when the current draw is >36mA.

7. Configure Action When Tamper Detected and the associated settings.

8. To send API calls when the action is triggered or completes:

   • Send API Requests: Set to Enabled to configure API calls when the action is triggered.

   • Send API Requests on Completion: Set to Enabled to configure API calls when the action completes.

9. Select Save.

   When the relay input is triggered, the 8312 triggers the configured action.

To configure an action for your Sensor Input:

1. Wire a sensor input device to the SENSOR INPUT terminals of your 8312.

   Note

   Do not connect Algo accessories, such as the 1202, 1203, 1204, 1205, 1211, or 1212, to the SENSOR INPUT. These accessories are designed for use with the SMART RELAY only.

2. Log in to your 8312’s web interface.

3. Go to Additional Features → Input/Output.

4. Go to the Sensors Inputs section and configure the matching sensor input.

   For example, if your sensor input device is wired to the SENSOR INPUT 1, configure Sensor Input 1.

   • Sensors Input: Select Normally Open or Normally Closed as per the connected sensor input device type.

   • Action: Select an action.

5. Configure any additional settings required for the selected action.

6. Select Save.

   When the sensor input is triggered, the 8312 triggers the configured action.

Checking Relay Input and Sensor Input Status

You can find the status of the relay or sensor input device on the Status page.

If the Relay Input device is configured as a Panic Button, you can also view the button information in the Panic Button Status section.

Triggering Actions Using Relay Output

By default, the Relay Output provides a contact closure when triggered.

A device that can be activated by opening or closing a circuit can be connected to the PAGE RELAY interfaces, such as strobe lights, door strikes, or magnetic locks.

Triggering Events

Depending on your relay activation setting, the following events can trigger relay output contact closure:

• Page Calls: When the 8312 receives incoming or outgoing SIP voice calls (initiated by Page extensions).

• Ring Calls: When the 8312 receives incoming or outgoing ring calls (initiated by Ring extensions).

• Emergency Alerts: When the 8312 receives or starts an emergency alert.

• Multicast: When the 8312 receives or starts a multicast.

• Test Audio & Scheduled Events: When the 8312 detects a ring, triggers a scheduled event, or when you test play a tone under Basic Settings → Feature → Ring/Alert Tone.

• Streaming: When 8312 starts or receives Audio Streaming or Internet Radio Streaming.

To configure and use Relay Output:

1. Wire a relay output device to the PAGE RELAY terminals of your 8312.

2. Log in to your 8312’s web interface.

3. Go to Additional Features → Input/Output → Output and set Output Relay to Enabled.

4. Select which of the following events trigger the relay output:

   • Relay Active with All Events: All the events trigger the relay output:

   • Relay Active with Selected Events: Only when the selected events trigger the relay output. If selected, also select the desired events.

5. Select Save.

   When the event is triggered, 8312 triggers a circuit closure of the connected relay output device.

Background Music Streaming

The 8312, set as a Multicast Transmitter (Sender), can stream background music to other Algo receiving devices on the network from one of the following music sources:

• Online radio URL

• Offline audio file

• Music source connected to the 8312’s AUX IN port.

The background music is streamed through the following audio outputs:

• AUX OUT port

• PAGE AUDIO OUT ports, including the terminal block and 3.5 mm jack interfaces.

Streaming Music from the Analog Input Port

Primarily used to play background music, this feature will play sound on the PAGE AUDIO OUT and AUX OUT ports as well as multicast if configured.

Note

The 8312 does not support the direct connection of dynamic microphones. To connect a dynamic microphone (e.g., Sennheiser E835), which does not require phantom power, an Algo 1205 Audio Interface is required. The 1205 provides the necessary preamplification, impedance matching, and interface to ensure proper audio input. Direct connection of a dynamic microphone to the 8312 is not supported and may result in no audio or improper operation.

To stream music from the analog input port:

1. Go to Additional Features → Input/Output → Audio Streaming.

2. Set Stream Audio from Analog Input Port to Always Active.

3. Set the VOX Mode:

   • Enabled: Automatically starts streaming when sound is detected (based on the VOX Sensitivity setting) and stops after the VOX Timeout period when no sound is detected.

   • Disabled: Always activates audio streaming, regardless of whether sound is detected.

4. Go to Additional Features → Input/Output → Audio Input Settings and configure the following:

   • Audio Input Port: Select an option:

     • Line In (radio in & back terminal block): Use the input from the LINE IN terminals on the back panel of the device.

     • Aux In (front blue 3.5mm headset): Use the input from the AUX IN port.

     • Aux Out (front green 3.5mm headset with mic): Use the input from the AUX OUT port.

       Note

       You can connect a 3.5 mm wired earbuds with a microphone to the AUX OUT port and use it as an audio input.

   • Audio Input Volume: Specifies how to change the volume level of the input audio source.

5. Connect a music input device to the selected analog input port of your device.

   When music stream starts, the sound is played on the PAGE AUDIO OUT and AUX OUT ports as well as multicast if configured.

Note

Always Active cannot be used when the Relay Input Mode is set to 1205 Audio Interface Switch or when the relay trigger action Stream Mic Audio. To enable Always Active, set Relay Input Mode to Disabled, or set Action When Input Triggered to Play Tone, Make SIP Voice Call, or Make SIP Call with Tone.

You can stream and multicast online radio or loop a preconfigured audio file to multiple devices simultaneously.

This allows centralized audio distribution without requiring individual playback control on each device.

You can stream Internet radio in one of the following ways:

• Use the Scheduler to stream radio at a specific time, with or without recurrence.

  For more information, see Using 8312 Scheduler.

• Enable continuous streaming under Advanced Settings → Advanced Audio → Internet Radio Streaming.

Note

Make sure Additional Features → Input/Output → Always Active is set as Disabled before using Internet Radio Streaming.

Otherwise, you cannot enable Internet Radio Streaming.

Supported Radio or Audio Format

Make sure your audio meets the following requirements:

• Radio streams: The stream must be an HTTP or HTTPS audio stream encoded in MP3, AAC, AAC+, Ogg Vorbis, Opus, or FLAC. HLS (.m3u8) audio streams are also supported.

• Offline audio files: Each file must be in MP3 format, smaller than 200 MB or shorter than 3 hours at 128 kbps.

  Otherwise, the file is not available in the Offline Music File drop-down list for Internet Radio Streaming.

Uploading Offline Audio Files

To play offline audio files, you must upload them to the radio folder of the File Manager before you can use them in Internet Radio Streaming.

Note

The file must be in MP3 format, smaller than 200 MB or shorter than 3 hours at 128 kbps.

Otherwise, the file is not available in the Offline Music File drop-down list for Internet Radio Streaming.

To upload offline audio files:

1. Go to System → File Manager.

2. Select the radio folder.

3. Do one of the following:

   • Drag and drop audio files from your local computer into this folder.

   • Select Upload and follow the on-screen instructions to upload files from your computer or mobile device.

4. When prompted, select Reboot.

   After the reboot completes, the uploaded audio files are available in the Offline Music File drop-down list for Internet Radio Streaming.

Configuring Internet Radio Streaming

You can stream either online radio or a local audio file. If your device is a Multicast Transmitter, you can also configure the target multicast zone to stream the audio to multiple devices simultaneously.

Once configured, the device continuously streams the radio station or local audio file until you disable the feature.

Note

When multicasting music, ensure that Automatic Gain Control (AGC) is Disabled in Basic Settings → Features tab on all the receiving devices. Meanwhile, on the Multicast sending device, select G.722 or Opus for the Sender Output Codec setting in Advanced Settings → Advanced Multicast tab.

Note

When both the Offline Music File and Radio URL are specified, the Radio URL takes precedence if an Internet connection is available.

To configure Internet Radio Streaming:

1. Go to Advanced Settings → Advanced Audio.

2. Go to the Internet Radio Streaming section and configure the following:

   • Internet Radio Streaming: Set as Enabled.

   • Radio Volume: Set the audio output volume for the device’s AUX OUT port.

     This volume doesn’t impact the multicast volume of the receiving devices.

   • Radio URL: Enter the stream URL.

   • Offline Music File: Select an audio file to stream.

     Make sure you have uploaded at least one offline music file to the System → File Manager → Radio folder.

   • Multicast Zone: Select a zone to multicast the audio to.

     Your device must be configured as a multicast transmitter first. The multicast output is RTP-only, using the L16 codec with a fixed packet size.

3. Select Save.

   The Internet radio stream starts.

Stopping Internet Radio Streaming

You can disable Internet Radio Streaming to stop an ongoing stream.

This doesn’t change your Internet Radio Streaming settings.

To stop Internet Radio Streaming:

1. Go to Advanced Settings → Advanced Audio.

2. Go to the Internet Radio Streaming section and set Radio Streaming as Disabled.

3. Select Save.

Internet Radio Streaming FAQs

Scheduler

Your device includes calendaring functionality synchronized with Network Time Protocol (NTP). You can schedule events on the local device or other IP endpoints, including:

• Play a pre-configured tone or alert to a multicast zone

  Ideal for education or manufacturing environments where certain areas require regular bell schedules or announcements, while others do not.

• Start a SIP call to trigger a pre-configured tone or alert on specific devices

  Useful when triggering tones or announcements through the PBX for selected endpoints, such as targeted alerts, shift bells, or department-specific notifications.

• Stream live audio to a multicast zone

  Suitable for facility-wide announcements, background music, or emergency notifications that need to play simultaneously across all subscribed devices.

• Schedule API calls from the device web interface to trigger actions on other devices

  For example:

  • Activating a strobe light

  • Displaying a slide or slideshow on an IP display

  • Triggering an emergency alert

  • Triggering an InformaCast scenario

  You can include up to 5 API calls in an API Call event.

  For a complete list of API commands, see RESTful API Guide.

You can organize related events into a group so they can be scheduled and managed together.

You can create standalone and recurrent events, skip event or group instances in recurrent schedules, or restore skipped instances.

Note

If your device is configured as a Multicast Transmitter (Sender), the audio in the scheduled events (if available) will be multicast to receivers.

Scheduler Overview

The Scheduler interface is organized into several tabs that provide tools for managing scheduled announcements and events. The following table describes the purpose of each tab and the tasks that can be performed from it.

Using the Scheduler

You can create and manage schedules using one of the following methods:

• Using the product's web interface: Refer to Using 8312 Scheduler.

• Using the Remote Device UI from ADMP: Refer to the Algo Device Management Platform (ADMP) User Guide.

• Using the RESTful API: Refer to the RESTful API Guide.

Creating a Dedicated Scheduler User Account

The Scheduler User Login feature creates a separate user account with limited access to the device web interface. This account allows users to manage the Scheduler without providing access to administrative settings.

When a Scheduler user logs in, only the Status and Scheduler menus are available. The user can create and modify scheduled events, calendars, groups, and scheduler data, but cannot view or change any device configuration settings.

This feature is useful when non-administrative personnel, such as office staff, school administrators, or facility managers, need to maintain scheduled announcements or events without requiring full administrator access.

To configure a Scheduler user account:

1. Go to Advanced Settings → User Management.

2. Under Scheduler, select Enabled.

3. Enter a Username.

4. Enter a Password.

5. Click Save.

   The Scheduler user account is now available from the login page.

To log in as the Scheduler user:

1. Open the device web interface.

2. From the User list, select the Scheduler user account.

3. Enter the Scheduler user's password.

4. Select Login.

   The web interface displays only the Status and Scheduler menus. Administrative configuration pages are not available.

TLS for SIP Signaling and Provisioning

Algo devices support Transport Layer Security (TLS). This feature adds security by ensuring that Algo products can trust the hosted SIP server. This is useful for when third-party devices or attackers may try to intercept, replicate, or alter Algo products and try to connect to the server. The TLS protocol will ensure that third parties cannot read/modify any actual data. Previously, security was less of a concern because phone systems were on isolated networks, but hosted services are becoming increasingly more common. Using a hosted SIP service requires traffic to be sent over the public internet and is therefore much more susceptible to attacks. Signed certificates are important pieces in the operation of Algo devices to ensure the security, integrity, and privacy of device communication. Algo components that use TLS are Provisioning and SIP Signaling.

Algo devices come pre-loaded with certificates from a list of trusted certificate authorities (CA), which are installed in the hardware at the time of manufacture.

Note

These pre-installed trusted certificates are not visible to users and are separate from the certs folder.

The TLS handshake happens to make sure that the client and server can trust each other, and once that trust is established, the two parties can freely send encrypted data and decrypt any data that they receive. After the TLS handshake process is complete, a TLS session is established, and the server and client can then exchange messages that are symmetrically encrypted with a shared (pre-sender) secret key.

For further details, see Algo TLS guide for SIP Signalling and HTTPS Provisioning.

Uploading Public CA Certificates to Algo SIP Endpoints

If the particular CA Certificate is not installed by factory, you can easily upload your own.

To install the public CA certificate on the Algo 8312:

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

2. In the web interface of the Algo device, navigate to the System → File Manager tab.

3. Upload the certificate files into the certs/trusted directory.

4. Click the Upload button in the top left corner of the file manager and browse to the certificate.

Reach out to support@algosolutions.com to get the complete list of trusted certificate authorities loaded from factory.

For SIP TLS, if the Validate Server Certificate option is enabled in Advanced Settings → Advanced SIP tab, then the device will validate the SIP server against common certificate authorities.

For Provisioning, if HTTPS is selected and the Validate Server Certificate option is enabled in the Advanced Settings  → Provisioning tab, then the device will validate the server against common certificate authorities.

To validate against additional certificates:

1. Go to System → File Manager.

2. Upload a Base64 encoded X.509 certificate file in .pem, .cer, or .crt format to the certs folder.

Provisioning can be secured by setting the Download Method to HTTPS (under the Advanced Settings → Provisioning tab). This prevents configuration files from being read by an unwanted third-party. This resolves the potential risk of having sensitive data stolen, such as admin passwords and SIP credentials.

Note

To verify the server, enable the Validate Server Certificate option. This then checks if the certificate that is provided by the server is signed by any of the CAs included in the list of trusted CAs (used by the Debian infrastructure and Mozilla browsers). If we receive a certificate signed by any of these CAs, then that server will be trusted.

The ‘Validate Server Certificate’ parameter can also be enabled through provisioning:

Prov.download.cert = 1

Using Configuration Files

When deploying the 8312, configuration files are used to provision the devices automatically. These configuration files define network settings, SIP credentials, and operational preferences, reducing the need for manual setup. There are two types of provisioning files available: generic and specific.

• Generic configuration file: The configuration file is not tied to a specific device. It does not include the MAC address in its filename, and any Algo 8312 device connected to the network can automatically download and use this file from the provisioning server. However, you must enter SIP extensions and credentials manually.

• Specific configuration file: The configuration file is intended for a single device and includes the device's MAC address in the filename. Only the Algo 8312 unit with the matching MAC address can download and use this file.

For more information, see the Algo’s SIP endpoint provisioning guide at www.algosolutions.com/provision.

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 create an .md5 checksum file:

1. Download an MD5 tool. For example, http://www.fourmilab.ch/md5.

2. Extract the tool and open a command prompt in the same directory.

3. Run the md5 command with the target filename to generate the .md5 file.

4. To output the hash in lowercase, add the -l parameter:

   Custom

   md5 -l yourfilename.ext

   Plain text

   The resulting .md5 file will be saved in the same directory.

Securing SIP Signaling (and RTP Audio)

SIP signaling is secured by setting SIP Transportation to TLS (under the Advanced Settings → Advanced SIP tab). SIP transportation refers to the underlying protocol used for transmitting SIP messages between different entities in a network. Setting it to TLS ensures that the SIP traffic will be encrypted. SIP signaling is responsible for establishing the call (the control signals to start and end the call with the other party), but it does not contain the audio.

For the audio (voice) path, use the setting SDP SRTP Offer. Setting this to Optional means the SIP call’s RTP audio data will be encrypted (using SRTP) if the other party also supports audio encryption. If the other party does not support SRTP, then the call will still proceed, but with unencrypted audio. To make audio encryption mandatory for all calls, set SDP SRTP Offer to Standard. In this case, if the other party does not support audio encryption, then the call attempt will be rejected.

The 8312 supports a wide range of third-party integrations, including radio systems, Microsoft Teams, InformaCast, and OAuth-enabled services.

These integrations allow the 8312 to extend paging, alerting, and notification workflows across public address systems, radio users, SIP platforms, cloud services, and third-party notification systems.

For a full list of compatible platforms and the configuration guides, see Compatible Platforms.

Motorola Curve Radio Integration

The 8312 can be used to distribute audio from UC platforms to overhead paging systems, compatible Motorola Curve radio users, or both simultaneously. This helps extend critical messages across public address systems, radio systems, and wider operational environments.

Note

Only audio from calls received on the main Ring Extension or Page Extension (configured under Basic Settings → SIP) can be routed to the RADIO output.  

Configuring a Motorola Curve Donor Radio for Continuous Operation

The 8312 Expanded IP Paging Adapter requires a dedicated Motorola Curve donor radio that remains powered on continuously. By default, Motorola Curve radios enable the Auto Power Off (APO) feature, which automatically turns the radio off approximately 180 seconds after it is placed in a powered charger. This behavior prevents the 8312 from maintaining a permanent radio connection.

To use a Motorola Curve radio as a donor radio, disable the Auto Power Off feature using Motorola Customer Programming Software (CPS).

Note

• A Motorola CPS Programming Cable (PMKN4154A) is required to configure the radio.

To disable Auto Power Off:

1. Download and install CPS R12 from Motorola Business Radio Customer Programming Software (CPS).  

   

2. Verify that the switch in the Programming Cable is in Digital position.

3. Connect the Motorola charging cradle and your computer using the programming cable.

4. Place the Motorola Curve donor radio into the charging cradle.

5. Turn on the radio.

6. Open the Motorola CPS application.

7. Select the RADIO tab.

8. Select the Radio Type to CURVE.

9. Select Read Radio to read the current radio configuration. The radio uploads its configuration into CPS.  

   

10. Locate the Auto Power Off (Sec.) and change the value to OFF.

    

11. Select Write to radio to save the updated configuration to the radio.  

12. After the programming completes, select Close.

    The Motorola Curve donor radio no longer powers off automatically while it is in the charging cradle. It can remain continuously powered on, allowing the 8312 to maintain a permanent connection to the radio for Radio-to-PA and UC-to-Radio communication.

Integrating with a Motorola Curve System

The 8312 can integrate with a Motorola Curve system by connecting a Motorola Curve donor radio to the RADIO port. When configured, audio from calls received on the main Ring Extension or Page Extension can be transmitted to Motorola Curve radios. If the 8312 is also configured as a multicast transmitter, the same audio can be multicast to configured receiver zones.

Note

Only audio from calls received on the main Ring Extension or Page Extension (configured under Basic Settings → SIP) can be routed to the RADIO output.

To integrate the Motorola Curve System:

1. Connect a Motorola Curve donor radio to the RADIO port of the 8312 using a customized Radio Connector Cable.

   You can purchase this cable from Algo (part number: 79-00062).

2. Go to Basic Settings → SIP and do the following:

   1. Configure the SIP Domain (Proxy Server).

   2. Configure the Ring Extension (also called main Ring Extension), or Page Extension (also called main Page Extension).

   3. Set Audio Output to one of the following:

      • Radio Audio Output: Sends the audio to RADIO and AUX OUT interfaces.

      • Both: Sends the audio to PAGE AUDIO OUT, RADIO, and AUX OUT interfaces.

3. (Optional) To adjust audio output volume, go to Basic Settings → Feature → Audio and configure the desired settings.

4. Select Save.

   When your 8312 receives calls on the main Ring Extension or main Page Extension, the audio in the call is transmitted to Motorola Curve radios.

Integration with Teams

Algo IP endpoints (including 8312) 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.

You can configure Teams integration using one of the following ways:

• Microsoft Teams Configuration with Algo IP Devices Using ADMP

• Microsoft Teams Configuration with Algo IP Devices Using the Device Web Interface

Integration with InformaCast

Algo devices (including 8312) can do the following when integrated with InformaCast:

• Receiving notifications from InformaCast

• Triggering InformaCast Scenario

For more information, see Singlewire InformaCast Integration Guide.

Using OAuth for Authentication

OAuth (Open Authorization) is an industry-standard protocol that enables secure, delegated access to resources without requiring users to share credentials such as usernames and passwords.

Instead of storing static credentials on a device or application, OAuth allows a trusted third-party service (such as Google, Microsoft, or Slack) to issue time-limited access tokens. These tokens allow an Algo device to interact with the service on behalf of a user or system, without exposing sensitive login information.

For more information, see Using OAuth for Authentication.

You can back up the current configuration, restore previously saved settings, reset the device to its factory defaults, and perform maintenance tasks to support troubleshooting, recovery, and device redeployment.

Backing Up System Configuration

Saves the device settings (configuration) and all files stored in File Manager, including certificates, licenses, and tones, to a backup ZIP file. Back up the configuration before making major changes or upgrading the firmware so it can be restored if needed.

To download system configuration:

1. Go to System → Maintenance → Backup / Restore Configuration.

2. Select Download next to Download Configuration File.

   

   The configuration file is downloaded to your default downloads folder using the following file name format:

   settings-<product_model>-<product_MAC_ADDRESS>.txt

Restoring the Device Configuration

You can restore the device configurations from a backup configuration file, or restore to its factory default settings using either the RESET button or the web interface.

You can also choose to restore the factory default settings and delete all preloaded and uploaded files.

Restoring Settings Using a Backup Configuration File

You can restore the device settings from a backup configuration file.

To restore settings using a backup configuration file:

1. Go to System → Maintenance → Backup / Restore Configuration.

2. Select Choose File next to the Restore Configuration File option.

   

3. Select the configuration file, then select Restore.

   The system reboots to restore the settings.

Restoring Factory Default Settings Only

Restore the factory default settings while keeping all preloaded and uploaded files. You can perform this operation using either the RESET button or the device's web interface.

To restore the factory default settings using the RESET button:

1. Reboot or power cycle the device.

2. Wait until the SIP LED begins flashing.

3. Press and hold the RESET button until the SIP LED begins a double-flash pattern.

   Note

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

4. Release the RESET button.

5. Wait for the device to complete the boot process.

6. After the device has finished booting, press the Reset button once.

   The device restores the factory default settings. When you press the RESET button after the boot process is complete, the device announces its IP address through the analog output ports.

To restore the factory default settings from your web interface:

1. Go to System → Maintenance → Backup / Restore Configuration.

2. Select Restore Defaults.

   

3. When asked to confirm this action, select OK.

   The system reboots to restore the default settings.

Restoring Factory Default Settings and Deleting Files

You can restore the device to its factory settings and delete all preloaded and uploaded files.

This is useful when redeploying the device or performing a complete factory reset.

To reset the device factory default settings and delete files:

1. Go to System → Maintenance → Backup / Restore Configuration → Restore Defaults and Delete Files.

   

2. When asked to confirm this action, select OK.

   The system reboots to restore the default settings. All preloaded and upload files are also deleted.

Managing Firmware

The Online Upgrade feature checks whether a newer firmware version is available from the Algo firmware server (firmware2.algosolutions.com). The device must have an active internet connection to perform this check.

Note

During the firmware update process, Algo devices communicate with two different hosts:

• firmware2.algosolutions.com: Checks whether a newer firmware version is available.

• algofw.sfo3.cdn.digitaloceanspaces.com: Downloads the firmware image when an update is available.

If your network uses outbound firewall rules, web filtering, or proxy allowlists, ensure that HTTPS (TCP port 443) access to both hosts is permitted. Blocking either host may prevent firmware updates from completing successfully.

To check for firmware updates:

1. Go to System → Firmware.

2. Under Online Upgrade, click Check.

3. Wait while the device checks for the latest firmware.

   If the device is running the latest firmware, Latest Firmware displays Firmware up to date.

   If a newer firmware version is available, the available firmware version is displayed.

Upgrading or Downgrading Firmware

The Custom Upgrade section allows you to manually install firmware when internet access is unavailable or when instructed by Algo Technical Support.

You can install firmware from a signed firmware file stored on your computer or from a firmware download URL.

To install firmware from a local file:

1. Download the signed firmware file from the Algo firmware downloads page.

2. Go to System → Firmware.

3. Under Method, select From Local Files.

4. Click Choose File.

5. Browse to and select the signed firmware file.

6. Select Upgrade.

7. After the device restarts, verify that the firmware version has been updated.

To install firmware from a URL:

1. Copy the firmware download URL from the Algo firmware downloads page.

2. Go to Firmware.

3. Under Method, select From URL.

4. Enter the firmware download URL in Upgrade URL.

5. Start the firmware upgrade.

6. After the device restarts, verify that the firmware version has been updated.

Allowing Firmware Downgrade

The Allow Downgrade option controls whether the device can install an earlier firmware version.

Note

Downgrading firmware may affect future firmware upgrades. If you need to downgrade the firmware, contact Algo Technical Support for assistance.

To allow firmware downgrades:

• Enable Allow Downgrade only if instructed by Algo Technical Support.

Managing System Log

The System Log provides a record of device events and operational messages that can help monitor system activity and troubleshoot issues. You can view the log to verify device operation, identify errors or warnings, and gather diagnostic information when investigating configuration or network problems.

Configuring Log Settings

The Log Settings page allows you to configure how the device records and manages system log messages. You can adjust the logging level, enable or disable remote logging, and specify a remote syslog server to collect log information for centralized monitoring, diagnostics, and troubleshooting.

To configure the log settings:

1. Go to Advanced Settings → Admin → Log Settings.

2. Configure the following:

   • Log Level: Select the appropriate level for the information you want to capture.

     Note

     Change the Log Level only under the guidance of Algo Technical Support. Higher log levels generate additional diagnostic information, which may clutter the logs and make routine monitoring and troubleshooting more difficult.

   • Log Method:

     • Local: The log file is saved in RAM on the device.

     • Network: Send the log file to an external SysLog server so settings are not lost if the device is rebooted, or for ease of central access.

     • Both: Use both methods.

   • Network Log Protocol: Select the transport protocol used to send Syslog messages to the configured log server.

     Note

     The default port when using UDP/TCP is 514. The default port when using TLS is 6514. To specify a different port, enter ADDRESS:PORT. When using TLS, use the System → File Manager tab to upload the CA certificate renamed to ca.pem to the certs/syslog folder. If the server is using peer certificate authentication, also upload the certificate/key pair renamed to cert.pem and key.pem.

   • Log Server: Enter the Syslog server address provided by your IT Administrator.

   • Log Additional Events: To be used by support@algosolutions.com if necessary.

   • Select Additional Log Events: To be used by support@algosolutions.com if necessary.

     Note

     Configure additional log events only when requested by Algo Technical Support. These options are intended for advanced troubleshooting.

3. Select Save.

Downloading System Logs

The System Log contains diagnostic information that can help identify and troubleshoot device issues.

To retrieve system logs:

1. Go to System → System Log.

2. Do one of the following:

   • Download: Save the log file to your local disk.

   • View: View the log information on-screen.

   Provide the file to Algo Technical Support if requested.

Managing Files Using File Manager

Use File Manager to manage the files stored on the device. You can upload, download, replace, and delete supported files, including audio files, certificates, and license files.

File Formats

The File Formats section lists the supported file types and requirements for files that can be uploaded to the device.

Certs Folder

The certs folder stores trusted Certificate Authority (CA) certificates used when validating server certificates.

Upload additional certificates only if Validate Server Certificate is enabled under Advanced Settings → Advanced SIP.

To install a public CA certificate:

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

2. Go to System → File Manager.

3. Open the certs folder.

4. Click Upload.

5. Select the certificate file.

The certificate is added to the trusted certificate store.

For a list of pre-installed trusted certificates, contact support@algosolutions.com.

Debug Folder

The debug folder stores diagnostic files generated by the device.

Diagnostic files are used by Algo Technical Support to troubleshoot device issues.

To retrieve diagnostic files:

1. Go to System → File Manager.

2. Open the debug folder.

3. Download the requested diagnostic files.

4. Provide the files to Algo Technical Support.

License Folder

The license folder stores license files required to enable licensed features.

To install a license:

1. Obtain the license file from Algo.

2. Go to System → File Manager.

3. Open the license folder.

4. Click Upload.

5. Select the license (.lic) file.

   The license is installed and becomes available after the upload completes.

Tones Folder

The tones folder stores custom audio files used for paging and notification applications.

To upload a custom audio file:

1. Go to System → File Manager.

2. Open the tones folder.

3. Click Upload.

4. Select the audio file from your computer.

5. Wait for the upload to complete.

   The uploaded audio file is available for notification applications.

To replace an existing audio file:

1. Download the existing audio file.

2. Modify the file as required.

3. Save the modified file using a different file name.

4. Upload the new file to the tones folder.

Note

Audio files must meet the supported format and file requirements listed in File Formats.

Radio Folder

The radio folder stores custom audio files used for offline Internet Radio Streaming.

To upload a custom audio file:

1. Go to System → File Manager.

2. Open the radio folder.

3. Click Upload.

4. Select the music file from your computer.

   Make sure the file be in MP3 format, smaller than 200 MB or shorter than 3 hours at 128 kbps.

5. Wait for the upload to complete.

   The uploaded audio file is available in the Offline Music File drop-down list under Advanced Settings → Advanced Audio → Internet Radio Streaming.

Managing Tones

Tone files are used for ringing, alerts, and other audio notifications on the device. You can download the default Algo tone files, rebuild tone cache files if tones do not play correctly, and test tone files directly from the device interface.

Downloading Tone Files

Your device includes a set of default ring tones, stored in System → File Manager → Tones. If you delete any of these files, you can download them again to restore the original ring tones.

To download Algo default tone files:

1. Go to System → Tones.

2. Do one of the following:

   • To download the tone files and install them into your File Manager → Tones folder, select  Download and Install.

     

   • To download them to your local disk, select the Algo website link.

     

Rebuilding Tone Cache Files

Rebuild Tone Cache Files recreates the cached versions of all tone files on the device. Use this option only if the tone cache is out of sync with the tone files, such as when uploaded or modified tones do not play correctly. The operation does not change or delete the original tone files and may take several minutes depending on the number and size of the files.

To rebuild tone cache files:

1. Go to System → Tones → Cache.

2. Select Rebuild All.

Testing Tone Files

You can play uploaded audio files directly through the device to verify that they sound as expected.

To test tone files:

1. Go to System → Tones.

2. In the Cache section, select Test Tones.

3. In the Test Tones section, select an audio file and select Play or Loop.

4. To stop the playback, select Stop.

Appendix: Web Interface Reference

This section provides an overview of the pages and settings available in the 8312 web interface. It describes the purpose of each configuration page to help you locate and configure the settings required for your deployment.

SIP Settings

The SIP tab under Basic Settings allows for the SIP server information and account credentials to be entered. This information can be obtained from your telephone system administrator or hosted account provider. After entering the information and saving the settings, go to the Status tab to confirm the registration was successful.

Features Settings

Features configure the device's operational functions and optional capabilities, such as audio behavior, paging, alerts, multicast, and other feature-specific settings.

Multicast: Transmitter (Sender) Settings

When you set the Multicast Mode to Transmitter (Sender), you can configure your device to transmit multicast audio to compatible Algo IP endpoints, multicast-enabled IP phones, and supported Poly devices. You can configure multicast modes, zones, Poly group paging settings, and DTMF-based zone selection to control how and where paging audio is distributed across the network.

For more information, see Configuring Your Device as a Multicast Transmitter.

Note

Always ensure that the multicast settings (such as zone numbers, the multicast IP address, and port definitions) on all receiver devices match those of the transmitter device.

Multicast: Receiver (Listener) Settings

When you set the Multicast Mode to Receiver(Listener), you can configure the device to receive multicast audio from compatible Algo IP endpoints, multicast-enabled IP phones, and supported Poly devices. You can configure the multicast mode, receiver zones, and Poly group paging settings to control which multicast streams the device monitors and plays.

For more information, see Configuring Your Device as a Multicast Receiver.

Input/Output Settings

The Input tab allows external accessories to be connected to the 8312. This is a dry contact input which can be configured as normally open or normally closed mode. Algo offers accessories, such as the 1202, 1203, 1204, and 2507. Third-party accessories/systems may also be used provided they have a dry contact output.

Configuration Fields Common to All Actions

The following configuration fields are common to all actions.

Note

The Panic Button option is available when:

• ADMP Cloud Monitoring and Panic Button Monitoring are both set to Enabled

• Relay Input Mode is set to one of the following:

  • Relay Normally Open with Supervision (e.g. Algo 1203 Call Switch)

  • Relay Normally Closed with Supervision

  • Algo 1202 Call Button

  • Algo 1211 Single Button

  • Algo 1212 Dual Button

Configuration Fields for Buttons

If your input device has buttons, you can configure actions for the second button press, or action override.

The following configuration fields may be available.

"Play Tone" Configuration Fields

"Make SIP Voice Call" Configuration Fields

Note

To make a SIP voice call, you must have configured the following in Basic Settings → SIP:

• SIP Domain (Proxy Server)

• Page Extension

"Make SIP Call with Tone" Configuration Fields

Note

To make a SIP voice call, you must have configured the following in Basic Settings → SIP:

• SIP Domain (Proxy Server)

• Page Extension

"Stream Mic Audio" Configuration Fields

Note

Before configuring this action, ensure your device (the host IP Endpoint) is configured as a Transmitter (Sender) under Basic Settings → Multicast → Multicast Mode.

"Send API Request" Configuration Fields

Related Links:

• RESTful API Guide

"Send SNMP Trap" Configuration Fields

Note

• Send SNMP Trap on Release is available only when the relay input mode is configured as:

  • Normally Open

  • Normally Closed

  • Normally Open with Supervision

  • Normally Closed with Supervision

• You must enable and configure Simple Network Management Protocol in Advanced Settings → Admin before using this action.

"Start InformaCast Scenario" Configuration Fields

Note

• The Start InformaCast Scenario action is available only when InformaCast Scenarios API is enabled under Advanced Settings → Admin → InformaCast Scenarios API.

• Before configuring this action, ensure you have configured an InformaCast Scenario and obtained its ID.

Related Links

• Singlewire InformaCast Integration Guide

Emergency Alerts Settings

The Emergency Alerts page allows you to configure SIP-triggered emergency announcements and alert behavior. You can define how announcements are activated and cancelled, configure authentication and passcode protection, select announcement audio sources, and specify multicast destinations and API requests to support emergency notification workflows.

For more information, see Configuring Emergency Announcements.

General Settings

General Settings controls how the announcement plays and how to trigger it.

DTMF Selection

DTMF extension will be used to activate and optionally cancel emergency alerts when Announcement Selection Mode is set to DTMF Selectable. Use the configurations below to register a single extension that will accept DTMF input to play selected announcements.

Call-to-Cancel

When your Algo device uses SIP for emergency alerts, both a start trigger (Announcement) and stop trigger (Call-to-Cancel) must be configured.

Up to 10 extensions can be registered, allowing up to 10 different announcements. Audio files can also be easily uploaded to create custom announcements. Only one Call-to-Cancel extension is needed, despite the number of the alert extensions.

Note

Some SIP phone systems may not support this feature if they limit the number of extensions that can be registered on a single device.

Related Links:

• RESTful API Guide

Network Settings

Network Settings configure how the device connects to your IP network, including IP addressing (DHCP or static), DNS, and IPv4/IPv6 settings. These settings ensure the device can communicate with SIP servers, cloud services, and other network resources.

Note

Available settings may vary depending on your product model and firmware version.

Admin Settings

Admin settings allow you to configure device access, security, management, monitoring, and integration features.

From this page, you can change administrator credentials, manage logging and network management settings, enable APIs and external services, and configure device maintenance options.

Note

The Power over Ethernet configuration section is available only on devices that require a PoE+ power source.

Note

Disabling Link Layer Discovery Protocol (LLDP) prevents your device from exchanging network configuration information with the connected network switch. If you are using a VLAN, make sure Link Layer Discovery Protocol (LLDP) is enabled, or that the VLAN Mode (under Advanced Settings → Network Settings) is set to Manual so you can configuration VLAN settings manually.

Note

The Intrado OneAlert feature is available only to Algo IP Speakers, IP Paging Adapters, IP Displays, and IP Visual Alerters.

Note

• This feature requires a valid license to be activated. Please contact sales@algosolutions.com for assistance.

• The InformaCast IP Speaker feature is available only to Algo IP Speakers, IP Visual Alerters, IP Paging Adapters, IP Displays, and IP Consoles.

• For more information, see Singlewire InformaCast Integration Guide.

Provisioning Settings

Provisioning configures automatic device provisioning, allowing the device to retrieve configuration files and updates from a remote provisioning server.

Fore more information, see Central Provisioning of Algo IP Endpoints.

Note

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.

Advanced Audio Settings

Advanced Audio configures advanced audio processing and media settings to optimize audio quality, reliability, and compatibility.

Advanced SIP Settings

Advanced SIP configures advanced SIP communication settings, such as registration, session timers, transport, codecs, and other protocol options to optimize interoperability and call performance.

Advanced Multicast Settings

These settings are only visible when in Transmitter or Receiver multicast mode. This can be set in Basic Settings → Multicast. The default pre-populated multicast zone IP addresses and ports will work in most cases and should only be altered for rare cases.

Appendix: Compliance and Safety

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.

Product Warnings

Important Notice

This product is powered by a certified limited power source (LPS), Power over Ethernet (PoE); through CAT5 or CAT6 connection wiring to an IEEE 802.3at- or 802.3af-compliant network PoE switch. The product is intended for installation indoors. If the product is installed beyond the building perimeter or used in an inter-building application, the wiring connections must be protected against overvoltage/transient. Algo recommends that this product is installed by a qualified electrician.

If you are unable to understand the English language safety information then please contact Algo by email for assistance before attempting an installation support@algosolutions.com.

Emergency Communication

If used in an emergency communication application, the 8312 should be routinely tested. SNMP or ADMP supervision is recommended for assurance of proper operation. Contact Algo for other methods of operational assurance including the use of the integrated microphone for automated “sound to air” acoustic testing.