Algo is a telecommunications manufacturer of SIP endpoints, as well as various other technologies including IP speakers, paging adapters, specialty handsets (PTT, PTM) and even strobe lights, clocks, push buttons, doorphones / intercoms, and specialty handsets (PTT, PTM).
This document supports configuration of the Algo 8xxx series.
Instructions for configuring Algo SIP endpoints with Telnyx
In this activity you will:
OPTIONAL: Enable the SIP-TLS SRTP encryption
OPTIONAL: Enable support for G-722 codec
If you experience any issues, visit our Troubleshooting section.
At least one Telnyx SIP account/sub-account with the following features:
A valid caller ID must be indicated (if you want Algo to make outgoing call to a specific destination - Anonymous outgoing calls aren't possible)
IF you want SIP traffic to be encrypted (and it's your choice), you will need to enable SIP-TLS for SRTP encryption.
Ensure you are on the most current Algo device firmware
Setting up your Telnyx SIP portal account so you can make and receive calls:
Note: Video walkthrough for Algo/Telnyx configuration coming soon. Check back as we update our docs.
1. Associate the SIP credentials to your endpoint
In this step, you will associate the credentials for your Telnyx SIP account/sub-account (see pre-requisites) to your Algo SIP endpoint.
Your Algo device should have an IP address assigned to it. To register your Algo SIP endpoint, open a web browser and enter this IP address.
Select the Basic Settings tab and then the SIP sub-tab and enter the following information:
SIP Domain (Proxy Server): sip.telnyx.com
Base/Page Extension: Your account/sub-account username
Authentication ID: Your account/sub-account username
Authentication Password: Your account/sub-account password
Display Name: Your outbound caller ID. (Devices set to make outgoing calls require a caller ID to be configured on your Telnyx SIP account, as mentioned in the pre-requisites.)
Note that if you want to register additional extensions for ringing, paging and emergency alerting, you will need to use unique credential for the respective extension in the same way. You can use any combination of page, ring, and/or emergency alerts is fine, so long as their credentials are unique!
2. OPTIONAL: Enable the SIP-TLS/SRTP encryption
In this step, you will enable and activate TLS for SIP transportation and SRTP encryption if you want to encrypt SIP traffic.
Select the Advanced Settings tab, followed by the Advanced SIP tab and enter the following information:
SIP Transportation: TLS
SDP SRTP Offer: Standard which ensures mandatory audio encryption for all calls.
Note that if the other party does not support audio encryption, any call attempt to that party will be rejected. If you don't want this to happen, set SDP SRTP Offer to Optional. All calls will be encrypted unless the other party does not support encryption. In that case, the call will not be encrypted.
IMPORTANT 8301 Users: In order for a SIP server to validate the Algo device, an additional certificate has to be manually installed on the 8301. To add this user certificate file use a ‘.pem’ filetype extension and have the file named ‘sipclient’. This is done by manually adding a file named ‘sipclient.pem’, which contains a device certificate and private key, to the ‘certs’ folder (under the Advanced Settings tab File Manager). In future releases, ‘.crt’, ‘.cer’, and ‘.der’ certificate extensions are also be supported and you will not be restricted to naming the file ‘sipclient.pem’.
3. Confirm registration success
Now select the Status tab. You will be on the Device Status tab.
Find the Status section and ensure that the each extension's SIP registration shows as Successful.
That's it! Your Algo is now set up and ready to go with Telnyx!
4. OPTIONAL: Enable support for G-722 codec
In this step, you will enable the Telnyx-supported G-722 codec if you want to use it. This applies to the codec used during SIP negotiation only. Multicast codecs are configured separately.
Select the Basic Settings tab and then the Features sub-tab.
Find the G-722 Support field in the Inbound Page Settings section and use the radio buttons to enable this feature.
Note: Algo supports the following audio codecs: G.711 u-law, G.711 A-law, G.722 Wideband.
There are some common issues that you may run into. The following sections will provide the most likely reasons, and potential solutions.
1. SIP Registration status = "Rejected by Server"
If you see this error, it means that the Telnyx server got the connection request from your endpoint, but it didn't authorize the connection.
In a case like this, the first thing to always check, and the most common issue, are incorrectly entered credentials.
Double-check your SIP account credentials (extension, authentication ID, and password) and make sure they're correct (including case)
If your credentials are correct, select the Basic Settings tab and then the SIP sub-tab.
If the password doesn't appear correct, it's possible that your browser is auto-filling the password field. Make sure no auto-fill is occurring because of your browser settings.
If you're authenticating correctly, it could be possible that you didn't configure the SIP transportation correctly (i.e.: You enabled encryption on the Algo side, but not the Telnyx side, or vice versa)
Select the Advanced Settings tab and then the Advanced SIP tab and ensure that your transportation you set here matches the configuration in your Telnyx Mission Control Portal.
It is possible that you entered the incorrect address or port for the SIP server. In this case, the server doesn't know it should reject the request and will simply deny the connection. You will find this in the system log. To view the system log:
Select the System tab and then the System Log sub-tab.
If you see a 500 Internal Server error, double-check that you provided the correct address/port for the SIP server.
2. SIP Registration Status = "No reply from server"
If you see this error, it means that the Algo device isn't able to communicate with the phone server.
This is a really common issue. Make sure your internet connection is up and stable and try again.
SIP Domain (Proxy Server)
Ensure that the server is entered correctly.
Select the Basic Settings tab and then the SIP tab.
Double-check that the SIP Domain (Proxy Server) field is entered correctly.
Firewall being extra careful
If you have a firewall present, it could be blocking incoming packets from the server.
Review our getting started with guide to make sure your Telnyx Mission Control Portal account is setup correctly!
Additionally, check out:
Can't find what you're looking for? Click the chat bubble at your lower right hand corner and start a chat!
*Note that you must be logged into your Telnyx Mission Control Portal in order to interact with the chat bubble.