• Home
  • Hosted Voice
  • SIP Trunking

Bring Your Own Telco (BYOT) Considerations

Written by Marissa Orsini

Updated at December 18th, 2024

Contact Us

  • The Essentials
    FAQs Forms
  • Announcements
    Carrier Events mFax Events Platform Events Release Notes
  • Billing Administration
    Datagate OneBill
  • Faxing
    mFax - Analog mFax - Digital Native Fax
  • Hardware & Software
    Manual Configuration Provisioning NDP Axis Cisco Fanvil Grandstream Polycom Snom Yealink Mobile Applications Desktop Applications Mobile-X SNAPbuilder TeamMate Connector UC Integrator
  • Hosted Voice
    Auto Attendants Branding Call Queues Call Routing CDRs Conferencing E-911 Features Fraud Integrations Inventory / Phone Numbers Local & Toll Free Porting Onboarding Recommendations SNAP.HD SIP Trunking SMS / MMS Users Voicemail Caller ID
  • Troubleshooting
    VoIPmonitor Firewalls PBX
  • Ray's Stuff
+ More

Table of Contents

Purpose Voice Traffic SIP Signalling SMS/MMS Faxing E-911 CNAM Fraud and Spam Detection STIR/Shaken Supported Carriers Pricing

Scope: The following information will give you the considerations when planning for BYOT implementations.

 

 

Purpose

BYOT is designed for WLP partners who want to use their own carriers. 


Voice Traffic

We will make a single connection between our SBCs and the SBC or carrier of your choice over port 5060 (UDP or TCP). If the partner uses multiple carriers they will need to establish their own SBC to connect with us. Our preferred SBC is FreeSBC from https://www.telcobridges.com/, but any can be used.

If the BYOT connection is Telnyx, you will need to setup authentication based on a technical prefix. Full steps to setup can be found in here Once that is setup, you will need to inform support, so we can add this to your BYOT connection. 


SIP Signalling

Carrier connections should use port 5060 for UDP and TCP traffic and port 5061 for TLS traffic. We do not support BYOT connections that use SIP signaling on any other ports.
 

If the BYOT carrier can not accommodate this, then utilizing an SBC such as our preferred SBC of FreeSBC https://www.telcobridges.com/<https://www.telcobridges.com/,> (but any can be used) to handle the conversion of the carriers port to our servers.


SMS/MMS

Message delivery to our PBX platform must be done from our carriers. We support off-net messaging which means that the WLPs DIDs will not need to be ported to us.


Faxing

mFax requires the use of our own carriers. DIDs used for faxing would need to be ported to us.

Native Fax can utilize your own carriers. We cannot guarantee any results for fax performance.


E-911

It is up to the WLP if they want to use their own e911 provider, or ours. If they choose to use theirs, then the e911 portal integration would not be available for them or their customers.


CNAM

Caller ID Name must be delivered in your initial invite. We will not perform CNAM lookups on calls passed from your SBC or carrier.


Fraud and Spam Detection

Fraud and Spam detection are provided by a third-party service and only available on telco services provided by us. We can introduce you to a vendor that will offer this service if needed.


STIR/Shaken

We cannot offer attestation and certification on BYOT trunks. Each WLP will need to address this with their carriers.


Supported Carriers

Our team provides best-effort support for any carrier that meets SIP compliance standards. Additionally, we have thoroughly tested interoperability with the following carriers:

  • Bandwidth
  • Inteliquent/Sinch
  • NUSO/Brightlink
  • Telnyx
  • Commio

For these carriers, we have verified seamless integration and performance, ensuring enhanced compatibility for your deployment.


Pricing

BYOT is billed per minute for traffic passed into, or out of our switches. 

With the exception of faxing, there are no costs for:

  • Porting
  • CNAM
  • DIDs

Note: Please note that a setup fee is required.

bring own telco byot

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Yeastar S: Connect a SIP Trunk
  • Configure Failover for a SIP Trunk
  • Obihai 200/300: SIP Trunk Configuration
  • Allworx: Connect a SIP IP Based Trunk

Knowledge Base Software powered by Helpjuice

Expand