SIP Trunking Setup Guide

27 Aug 2024

Step by step instructions on how to setup and configure SIP Trunks on the LoopUp Cloud Telephony platform.

In this article

Introduction and Pre-requisites

This article will step through each of the tasks required to configure a SIP Trunk on the LoopUp Cloud Telephony Platform

Supported Scenarios and Devices

LoopUp SIP Trunking is designed to support the following scenarios:

  • IP to IP SIP Trunking (i.e., SIP Registration is not supported)
  • Dedicated endpoints and customer owned devices that are reachable via a unique domain name or IP Address and port (i.e., multi-tenant shared endpoints are not supported)
  • The region of the SIP Trunk must match the region the numbers belong to (i.e., it's not possible to route a German (EMEA) number to a SIP Trunk in the AMER region)

The following devices have been tested by LoopUp and the necessary configuration for interop:

Other devices may work, but have not been tested by LoopUp.

Viewing SIP Trunks

Once SIP Trunking services have been enabled on your account, you will see a new menu item on the left navigation:

All SIP Trunks are listed in the order they are created, with newer ones appearing at the top.

To find a specific SIP Trunk in the list, the search box will filter based on the Trunk Name, Description, as well as endpoint details.

Create a SIP Trunk

Click the 'Create New SIP Trunk' button at the top right of the SIP Trunking page

And the following form appears in the card below it.

  • Name - Required
  • Description - Optional
  • Region - Required
    • This cannot be changed later, and refers to the specific region LoopUp will accept SIP Trunk connections to/from. More information on this will be covered later in this article.
  • Distribution - Required
    • Round Robin - This sets all endpoints to have the same weighting, and will distribute calls in a 'round robin' fashion. This is classed as 'dumb load balancing' or 'load distribution'. Each new call will be sent to the next available endpoint based on which one was tried previously.
    • Failover - This specifies that the endpoints will be tried in the order listed for each new inbound call. Each call will try the first endpoint, followed by the next, and so on.
  • Channel Limit - Required
    • For self-service SIP Trunk management please specify the number of channels required, this is between 1 and 100. If you need more channels contact support to process the request.
  • Protocol - Required
    • UDP - use the UDP protocol for all signalling messages - this is the most common option. When this is selected media will not be encrypted.
    • TCP - use the TCP protocol for all signalling messages - when this is selected media will not be encrypted.
    • TLS - use the TLS protocol over TCP for all signalling messages - this is used to ensure all signalling is encrypted. When this is selected media will be also be encrypted.
  • Primary Endpoint - Required
    • The IP Address or FQDN of the customer's endpoint followed by a colon and the listening port on their endpoint. When TLS is selected you must enter a FQDN.
  • Additional Endpoints - Optional
    • A comma separated list of additional endpoints.

Here is an example of a populated form:

When entering a FQDN for an endpoint, the system will perform a DNS Query when the create button is clicked. If no DNS Records are returned, then the SIP Trunk will not be created.
NOTE: As stated in the supported scenarios, all endpoints referenced in the SIP Trunk must be globally unique combination of IP Address and Port or FQDN and Port. It is not supported to create more than one trunk to the same endpoint within the same region. If this particular shared endpoint scenario is required, then the endpoint should have an additional interface configured to listen on a different port for each trunk.

Configuration Information

The following information will be displayed once the SIP Trunk has been created.

(example above has been cut off for illustrative purposes, but will contain more information)

To can also be viewed later by clicking on the 'configuration information' icon on the specific SIP Trunk (spanner and screwdriver icon).

LoopUp Platform Endpoints

These are the unique based on the region that was selected when creating the SIP Trunk

AMER Region LoopUp Endpoints
  • usdc1-edgesbc.loopup.com - 176.74.7.53
  • usdc2-edgesbc.loopup.com - 176.74.3.253
EMEA Region LoopUp Endpoints
  • ukdc1-edgesbc.loopup.com - 176.74.5.5
  • ukdc2-edgesbc.loopup.com - 185.66.35.35
APAC Region LoopUp Endpoints
  • hkdc1-edgesbc.loopup.com - 185.66.34.4
  • ausdc1-edgesbc.loopup.com - 176.74.1.4

Protocols and Ports

The selected protocol dictates the listening port on our LoopUp platform endpoints.

  • UDP & TCP - 5060
  • TLS - 5061

TLS Specific Information

LoopUp's Root Certificate

For more information and to download these certificates please read the LoopUp SIP Trunking Public Certificate Chain knowledge article.

Root Certificate Authority

Subject Name: DigiCert Global Root CA
Issuer: DigiCert Global Root CA
Thumbprint: A8:98:5D:3A:65:E5:E5:C4:B2:D7:D6:6D:40:C6:DD:2F:B1:9C:54:36
Serial Number: 08:3B:E0:56:90:42:46:B1:A1:75:6A:C9:59:91:C7:4A
Valid To: 10/November/2031

Intermediate Certificate Authority

Subject Name: DigiCert TLS RSA SHA256 2020 CA1
Issuer: DigiCert Global Root CA
Thumbprint: 1C:58:A3:A8:51:8E:87:59:BF:07:5B:76:B7:50:D4:F2:DF:26:4F:CD
Serial Number: 06:D8:D9:04:D5:58:43:46:F6:8A:2F:A7:54:22:7E:C4
Valid To: 13/April/2031

Supported Ciphers

The following ciphers are supported for signalling

  • ECDHE-RSA-AES265-GCM-SHA384
  • ECDHE-RSA-AES128-GCM-SHA256
  • ECDHE-RSA-AES256-SHA384
  • ECDHE-RSA-AES128-SHA256

The following ciphers are supported for media

  • AES-CM-128-HMAC-SHA1-80
  • AES-CM-128-HMAC-SHA1-32

Media Codecs

  • G.711 a-law / PCMA
  • G.711 μ-law / PCMU
  • T.38

Media Ports

  • UDP:7000-65535

Supported Root Certificates for TLS SIP Trunks

LoopUp take security very seriously and will only accept TLS SIP Trunks using certificates issued by Root Certificate Authorities that LoopUp have approved. This list may change from time to time, if your preferred Root Certificate Authority is not on the list, you will need to purchase a certificate from one that is.

Assign Numbers to a SIP Trunk

On each SIP Trunk, there is a section on the card labelled 'Numbers Assigned', underneath shows the amount of numbers that are currently assigned to that trunk. (Assigned means the number is configured to route to that SIP Trunk).

When hovering over the number, a link will appear that either says 'Assign Numbers' or 'View Numbers' depending on if there are numbers already assigned.

On this page you can update one number at a time by double clicking the row or click the edit icon (pencil). Then drop down the Destination box and select the SIP Trunk the number should be routed to.

Alternatively you can perform bulk actions by clicking the checkboxes on the left, and then click 'Bulk Edit' button. Once the destination is selected - click on the green tick to the right of the bulk edit section.

To remove a number from a SIP Trunk select the destination as None, or any other service you would like the number to route to.

Once done the portal will show a confirmation notification at the top right of the page.

Delete a SIP Trunk

From the list of SIP Trunks, hover over the SIP Trunk you want to delete and the action icon appears, click the bin/trash icon and click Confirm.

NOTE: It is not possible to delete a trunk that has numbers routing to it. Move the numbers to another destination or None and then delete the SIP Trunk.

You should then see the confirmation notification temporarily at the top right of the page

Edit a SIP Trunk

It is not possible to change the Region that a SIP Trunk is associated with. To amend any other item click the Edit button on the SIP Trunk.

Amend the information as required, and click Save Changes.

  • SIP Trunking
  • Setup Guide