Help Center

Integrations

Point your switch, softswitch or SMSC at TelecomsXchange.

SIP platforms09

  1. Connect a SIP platform to TelecomsXchangeEvery value to connect a softswitch, SIP proxy, PBX or CPaaS to TelecomsXchange: host, port, tech prefix, IP or digest auth, and inbound whitelisting.
  2. Connect Asterisk to TelecomsXchangeConfigure an Asterisk PJSIP trunk to send calls to TelecomsXchange with a tech prefix, by IP or digest authentication, and to accept calls from 174.136.44.213.
  3. Connect FreeSWITCH to TelecomsXchangeConfigure a FreeSWITCH Sofia gateway without registration to send calls to TelecomsXchange with a tech prefix, and an ACL to accept calls from 174.136.44.213.
  4. Connect Kamailio to TelecomsXchangeRoute calls from Kamailio to TelecomsXchange with dispatcher and a tech prefix, answer digest challenges with uac, and accept 174.136.44.213 with permissions.
  5. Connect OpenSIPS to TelecomsXchangeRoute OpenSIPS calls to TelecomsXchange with drouting and a tech prefix, answer digest challenges with uac_auth, and accept 174.136.44.213 with permissions.
  6. Connect Sippy Softswitch to TelecomsXchangeSet up TelecomsXchange in Sippy Softswitch as a vendor connection with a tech-prefix translation rule, and as a customer account authenticated by IP.
  7. Connect PortaSwitch to TelecomsXchangeSet up TelecomsXchange in PortaBilling and PortaSIP: a To vendor connection with the tech prefix, and a customer account authenticated by IP.
  8. Connect Twilio to TelecomsXchangeSend Twilio Programmable Voice calls to TelecomsXchange routes with Dial and Sip plus digest auth, and deliver TelecomsXchange numbers to a Twilio SIP domain.
  9. Connect Telnyx to TelecomsXchangeSend Telnyx TeXML or Call Control calls to TelecomsXchange routes with digest credentials, and deliver TelecomsXchange numbers to a Telnyx SIP connection.

PBXs05

  1. Connect 3CX to TelecomsXchangeSet up a 3CX V20 generic SIP trunk with IP authentication to send calls to TelecomsXchange with a tech prefix, and receive calls from 174.136.44.213.
  2. Connect FreePBX to TelecomsXchangeSet up a FreePBX 17 PJSIP trunk with no registration to send calls to TelecomsXchange with a tech prefix, and accept inbound calls from 174.136.44.213.
  3. Connect Yeastar P-Series to TelecomsXchangeSet up a Yeastar P-Series peer trunk to send calls to TelecomsXchange with a tech prefix by IP authentication, and route inbound calls from 174.136.44.213.
  4. Connect Grandstream UCM to TelecomsXchangeSet up a Grandstream UCM6300 or UCM63xx peer SIP trunk to send calls to TelecomsXchange with a tech prefix, and route inbound calls from 174.136.44.213.
  5. Connect Cisco CUBE to TelecomsXchangeConfigure Cisco CUBE on IOS XE to send CUCM calls to TelecomsXchange with a tech prefix, by IP or digest authentication, and accept calls from 174.136.44.213.

Contact centres and UCaaS05

  1. Connect VICIdial to TelecomsXchangeAdd TelecomsXchange as a VICIdial carrier with no registration, prepend the tech prefix in the dialplan entry, and keep outbound dialing within 10 CPS per IP.
  2. Connect Genesys Cloud to TelecomsXchangeCreate a Genesys Cloud BYOC Cloud external trunk over UDP to TelecomsXchange, with digest authentication, a tech-prefix transformation and an outbound route.
  3. Use TelecomsXchange with Amazon ConnectAmazon Connect has no bring-your-own-carrier SIP trunk. What works with TelecomsXchange: a SIP server you run in front of Connect, over UDP.
  4. Connect Microsoft Teams Direct Routing to TelecomsXchangeUse Teams Direct Routing with TelecomsXchange through a certified SBC: TLS and SRTP to Teams, plain SIP over UDP with a tech prefix to sip01.
  5. Connect Zoom Phone BYOC to TelecomsXchangeUse Zoom Phone Bring Your Own Carrier (Premise Peering) with TelecomsXchange through a supported SBC: TLS to Zoom, SIP over UDP with a tech prefix to sip01.

Softswitches and SBCs05

  1. Connect VOS3000 to TelecomsXchangeSet up TelecomsXchange in VOS3000 as a static routing gateway with a callee rewrite rule for the tech prefix, and as a static mapping gateway when you sell.
  2. Connect VoipSwitch to TelecomsXchangeAdd TelecomsXchange to VoipSwitch as a gateway with the tech prefix as its dialed number prefix, and as a wholesale client authenticated by IP 174.136.44.213.
  3. Connect MOR (Kolmisoft) to TelecomsXchangeAdd TelecomsXchange to Kolmisoft MOR as a SIP provider authenticated by IP with a provider rule for the tech prefix, and accept it as an IP-authenticated device.
  4. Connect an AudioCodes Mediant SBC to TelecomsXchangeConfigure an AudioCodes Mediant SBC for TelecomsXchange: a UDP proxy set to sip01, an IP Group, a manipulation that adds the tech prefix, and classification for 174.136.44.213.
  5. Connect a Ribbon SBC to TelecomsXchangeConfigure a Ribbon SBC Edge or SWe Lite for TelecomsXchange: a UDP SIP server table to sip01, a signaling group, a transformation that adds the tech prefix, and call routes.

SMPP platforms04

  1. Connect an SMPP platform to TelecomsXchangeEvery value an SMS engineer needs to connect an SMPP gateway or SMSC to TelecomsXchange, to buy SMS routes, sell them or carry SMS for phone numbers.
  2. Connect Kannel to TelecomsXchangeConfigure a Kannel smsc group to bind to TelecomsXchange over SMPP, add the route's tech prefix with unified-prefix, get receipts, and sell SMS with opensmppbox.
  3. Connect Jasmin SMS Gateway to TelecomsXchangeAdd a Jasmin SMPP client connector for TelecomsXchange with jCli, prepend the route's tech prefix with an MT interceptor, get receipts, and accept TelecomsXchange's bind to sell SMS.
  4. Connect Restcomm SMSC to TelecomsXchangeCreate a Restcomm (Telestax) SMSC Gateway client ESME that binds to TelecomsXchange, add the tech prefix with an mproc rule, route receipts, and accept TelecomsXchange's bind as a server ESME.