Skip to content
  • There are no suggestions because the search field is empty.

TLS 1.0 Retirement

TLS 1.0 is being retired on our SIP proxy

What's happening

TLS 1.0 is an old encryption standard. It has been retired industry-wide because it no longer meets modern security requirements. As part of our migration to the Lyra platform, we are removing support for TLS 1.0 on the SIP proxy.

This change only affects you once your account has been migrated to Lyra. If a phone number or device on your account connects using TLS 1.0, that connection will stop working from the point your account moves across, not before.

Some accounts have more than one affected number or device. Check all of them, not just the first one you find.

Key dates

Migrations to Lyra are taking place in stages from Monday 12/10/26 to Tuesday 10/11/26 

TLS 1.0 will stop being supported on your account from the date it migrates, which could be any time within this window. To avoid disruption, please complete the steps below before Monday 12/10/26

How do I know if this affects me?

You may have received an email or other notification from us naming one or more devices, numbers, or IP addresses on your account using TLS 1.0. If so, work through each one listed. Accounts with several phone lines or devices can have more than one affected connection at the same time.

If you have not received a specific notification but want to check your own setup, look at the SIP transport type configured on each of your devices. If any device is set to TLS, check the TLS version it is using. Anything below TLS 1.2 will be affected.

What do I need to do?

First, locate each affected device. This is usually a desk phone, ATA, or PBX endpoint. You can normally find its IP address through your router's connected devices list, or from the notification we sent you.

If you have multiple affected devices, you will need to repeat the fix for each one. They do not need to use the same option. For example, you might replace one old handset while just switching another to UDP.

Once you have located a device, there are three ways to resolve the issue.

Option 1: Change the SIP transport type (turn off TLS)

If the device does not need to stay on TLS, the simplest fix is to switch it to UDP.

  1. Find the device's IP address.
  2. Enter that IP address into a web browser to open the device's configuration page.
  3. Log in with the device's admin credentials.
  4. Go to the SIP account settings.
  5. Change the transport type from TLS to UDP.
  6. Change the SIP port to 50600.
  7. Save the settings and restart the device if prompted.

Option 2: Upgrade the device firmware

Some devices support TLS 1.2 or higher through a firmware update. If yours does, this lets you keep using TLS.

  1. Check your device model against our [compatibility list] to confirm a supported firmware version exists.
  2. Download the latest firmware from the manufacturer's website.
  3. Log in to the device's web interface.
  4. Upload and install the new firmware.
  5. Confirm the device reconnects and registers correctly after the update.

Option 3: Replace the device

If the device cannot be switched to UDP and cannot be upgraded to support TLS 1.2 or higher, it will need to be replaced. Contact our support team if you would like advice on a compatible replacement.