This document explains how to configure Algo devices to work with RingCentral Persist using the Algo device’s SIP peer-to-peer feature.
This feature allows Algo devices to maintain communication with other RingCentral endpoints during an Internet outage or loss of connectivity to RingCentral.
When RingCentral connectivity is available, the Algo device registers with RingCentral and receives calls through normal RingCentral routing.
If RingCentral connectivity is unavailable, calls are routed through a Persist device. The Persist device locally forwards SIP calls to the Algo device using its peer-to-peer SIP extension and configured IP address, allowing communication without RingCentral cloud involvement.
Before You Begin
Make sure you have:
Algo devices (firmware v5.7 or later ) registered to RingCentral, with a SIP extension assigned.
You can download the latest firmware from Algo Firmware Downloads.
A Persist device registered to RingCentral.
A Persist device is a RingCentral-supported survivability device that locally routes SIP calls during Internet or cloud outages.
Your Algo devices have been added to the proxy settings on the Persist device.
Configuring Your Algo Device for RingCentral Persist
Follow the instructions below to configure the required SIP Peer-to-Peer, Page Extension, and Advanced SIP settings on the Algo device.
To configure your Algo device for RingCentral Persist:
Log in to the Algo device developer interface using this format: https://<Device_IP>/control/tools.lua.
For example, if your Algo device IP is 10.11.12.123, go to https://10.11.12.123/control/tools.lua.
Configure the following settings:
.png)
SIP Peer-to-Peer: Set to Enabled.
This enables direct SIP communication between devices using IP addresses without requiring SIP server registration or call routing.
Attempt Register: Set to Disabled.
You must disable Attempt Register so that peer-to-peer extensions can still receive calls, but the Algo device does not attempt to register or re-register those extensions with RingCentral. Excessive SIP REGISTER attempts may result in blacklisting by RingCentral.
Select Save.
Go to Additional Features → More Page Extensions.
Enable the desired Page Extension and configure it for Persist peer-to-peer calling:
.png)
Extension: Enter the SIP extension assigned to your device in RingCentral using this format: Extension@<Persist_Device_IP>.
For example, if your Persist device IP is 10.21.22.234 and the SIP extension is 1234, enter 1234@10.21.22.234.
Authentication ID: Enter the extension as the ID.
Authentication Password: Leave it blank.
Select Save.
Go to Advanced Settings → Advanced SIP and configure the following:
.png)
SIP Transportation: Set to UDP.
Outbound Proxy: Enter the hostname (FQDN) and port of your RingCentral SIP outbound proxy server.
Select Save.
Now your Algo device is reachable from other RingCentral-registered devices using either the SIP extension (in this example, 1234) or the RingCentral phone number assigned to it, provided the devices are connected with the Persist device.