The Telnyx Mission Control SIP Connections allow users to define multiple retries in case a call fails to connect. The policy for fail-over and retries is designed to make sure that calls always connect regardless of issues on Telnyx or the user side.

This policy depends on the type of Connection and other settings, and to explain how it works we need to define the following concepts:

Fail-over and Retry Concepts

  1. IP1: Primary Signaling IP address of the SIP Region (e.g. for US SIP Region it's 192.76.120.10)
  2. IP2: Secondary Signaling IP address of the SIP Region (e.g. for US SIP Region it's 64.16.250.10)
  3. Routes: Each Connection can have multiple routes, for IP Auth connections each IP address is a route, for FQDN connections each FQDN is a route.
  4. Route preferences: If a Connection routing method is Sequential then each route can be set as either Primary, Secondary, or Tertiary. Please note that this is also set at the Number level, and the Number settings override the Connection settings. If a Connection routing method is Round Robin then each route is attempted in random order.
  5. Call Connected: A call attempt is considered "connected" (not to be confused with "answered") if it gets one of the following results:
  • 486 Busy
  • 404 Not Found
  • 603 Declined
  • Call rings (180/183) but it's not answered
  • Call is answered (200 OK)

Inbound Call to Connection with only one route

  1. Telnyx sends an attempt from IP1 to the single route of the Connection.
  2. If the call attempt doesn't connect then Telnyx retries from IP2.

Inbound Call to Connection with multiple routes

  1. Telnyx sends a call attempt from IP1 to the first route of the Connection.
  2. If the call attempt doesn't connect then Telnyx sends an attempt from IP1 to the second route of the Connection.
  3. If the call attempt doesn't connect then Telnyx sends an attempt from IP1 to the third route of the Connection.
  4. If the call attempt doesn't connect then Telnyx sends an attempt from IP2 to the first route of the Connection.
  5. If the call attempt doesn't connect then Telnyx sends an attempt from IP2 to the second route of the Connection.
  6. If the call attempt doesn't connect then Telnyx sends an attempt from IP2 to the third route of the Connection.

Inbound Call to Cred Auth Connection

Please note that Telnyx will send call attempts to Cred Auth Connections only from the IP that the SIP device registered to, which can be either IP1 or IP2, and that SIP device can be configured to register against:

  1. An IP address (either IP1 or IP2)
  2. An FQDN that points only to IP1 (for US SIP region sip-anycast1.telnyx.com)
  3. An FQDN that points only to IP2 (for US SIP region sip-anycast2.telnyx.com)
  4. An FQDN with SRV records that point to IP1 as primary and IP2 as secondary (sip.telnyx.com) -> In this case the SIP device might end up registering to either IP1 or IP2 depending on its internal tests.

Also call attempts to Cred Auth connections go through a KSS (SIP registrar) for which there are 3 instances on each US region.

  1. Telnyx sends a call attempt from primary KSS and then through IP1/2 to the Cred Auth Connection.
  2. If the call attempt doesn't connect then Telnyx sends a call attempt from secondary KSS and then through IP1/2 to the Cred Auth Connection.
  3. If the call attempt doesn't connect then Telnyx sends a call attempt from tertiary KSS and then through IP1/2 to the Cred Auth Connection.

Inbound Call to Connection and Number with Call Forward On Failure

Please note that Telnyx will send call attempts to Cred Auth Connections only from the IP that the SIP device registered to, which can be either IP1 or IP2, and that SIP device can be configured to register against:

  1. Telnyx sends a call attempt from IP1 to the first route of the Connection.
  2. If the call attempt doesn't connect then Telnyx sends an attempt from IP1 to the second route of the Connection.
  3. If the call attempt doesn't connect then Telnyx sends an attempt from IP1 to the third route of the Connection.
  4. If the call attempt doesn't connect then Telnyx sends an attempt to the Call Forward PSTN Number through the first Termination Carrier in route.
  5. If the call attempt doesn't connect then Telnyx sends an attempt to the Call Forward PSTN Number through the second Termination Carrier in route.
  6. If the call attempt doesn't connect then Telnyx sends an attempt to the Call Forward PSTN Number through the "n" Termination Carrier in route (max 10 termination carriers).

Inbound Call to Number with Call Forward Always

  1. Telnyx sends a call attempt to the PSTN Number through the first Termination Carrier in route.
  2. If the call attempt doesn't connect then Telnyx sends an attempt to the PSTN Number through the second Termination Carrier in route.
  3. If the call attempt doesn't connect then Telnyx sends an attempt to the PSTN Number through the "n" Termination Carrier in route (max 10 termination carriers).

Inbound Call to Connection with SRV records

To be confirmed.

Outbound Call to PSTN Number

  1. Telnyx sends a call attempt to the PSTN Number through the first Termination Carrier in route.
  2. If the call attempt doesn't connect then Telnyx sends an attempt to the PSTN Number through the second Termination Carrier in route.
  3. If the call attempt doesn't connect then Telnyx sends an attempt to the PSTN Number through the "n" Termination Carrier in route (max 10 termination carriers).

Can't find what you're looking for? Click the chat bubble at your lower right-hand corner and talk to the support team!

Did this answer your question?