Interconnection

Interconnecting with BWT

BWT maintains interconnection with other carriers for the exchange of voice traffic. If you’re a carrier or service provider interested in establishing interconnection, this page covers the basics.

Peering Options

SIP Interconnection

Our standard interconnection method. We exchange traffic over SIP, typically over the public internet with IP whitelisting, or via private interconnection at mutually agreeable facilities.

  • Public internet peering: IP-authenticated SIP trunks over the public internet. We whitelist your source IPs; you whitelist ours. Simple, fast to provision, works for most use cases.
  • Private interconnection: Direct cross-connects or private network segments at colocation facilities. Appropriate for higher-volume interconnections or where public internet transit isn’t acceptable.

Requirements

  • SIP (RFC 3261) compliant endpoint
  • G.711 codec support (PCMU and/or PCMA)
  • RFC 2833 DTMF
  • Static IP addressing
  • STIR/SHAKEN signing capability for originating traffic (required for US carriers per FCC mandate)

Interconnection Agreements

We execute standard interconnection agreements for carrier-to-carrier traffic exchange. The type of agreement depends on the nature of the interconnection:

  • Wholesale customer agreements for customers purchasing origination or termination services
  • Bilateral interconnection agreements for mutual traffic exchange between carriers
  • Tandem transit agreements for carriers routing traffic through our tandem

We try to keep our agreements straightforward. If you’ve dealt with ILEC ICAs that run 200 pages, you’ll find ours refreshing.

LERG and Routing

BWT is listed in the Local Exchange Routing Guide (LERG) under OCN 8697. Our switches are registered with standard CLLIs and are routable via industry-standard routing databases.

If you’re setting up routing to our network, you can find our information in the LERG, or contact us directly for current routing details and IP addressing.

Getting Started

If you’re interested in establishing interconnection with BWT:

  1. Email sales@bwt.io with a brief description of what you’re looking to do
  2. We’ll schedule a technical call to discuss requirements and architecture
  3. We’ll execute an appropriate agreement
  4. We’ll exchange technical details (IPs, codecs, capacity) and do test calls
  5. You’re live

The whole process typically takes one to two weeks for a standard SIP interconnection. Complex arrangements take longer, but we don’t drag our feet.