Configuration of Call Control/TeXML Voice Apps

The Call Control / TeXML applications section is located on the left hand side of the portal under Voice > Programmable Voice.

Click on this button below and it will directly get you to the Voice Applications page.

Click on " Create your first application" and assign a name to this application to better manage the application.

You will need to input a URL where all the webhook events will be sent. Also, you can setup a fail-over URL. If two consecutive delivery attempts to the primary URL fail, Telnyx will attempt delivery to this URL. NOTE: Must include a scheme such as 'https'.

Determines which webhook format will be used based on the API version V1 or V2.

We recommend using API V2, as it contains a richer feature set versus the initial version which will be deprecated in the future.

When enabled, you will specify the number of seconds Telnyx will wait for commands from your application before hanging up.

In this field, you will need to specify a delay in seconds for Telnyx to wait before retrying an unsuccessful webhook delivery attempt. If not set, Telnyx will retry immediately.

"Latency" directs Telnyx to route media through the site with the lowest round-trip time to the user's connection. Telnyx calculates this time using ICMP ping messages. This can be disabled by specifying a site to handle all media.

There are three types in this field: RFC 2833, Inband and SIP INFO.

Enable capture of RTCP reports to build QoS Reports (found under Debugging > SIP Call Flow Tool). By default it's not enabled, clicked the "yes" radio button to enable it.

Specify if the call cost webhook should be sent. By default it's not enabled, clicked the "yes" radio button to enable it.
​

You can configure your global application settings for inbound calls over here.

Specify a subdomain that can be used to receive calls to a Connection, in the same way a phone number is used, from a SIP endpoint.

You can limit the total number of inbound calls to phone numbers associated with this connection.

By default, the radio button for no is checked. Select yes and save your settings if you want receive attestation information in the webhooks for incoming calls.

Select the codes using the check mark boxes that you would like Telnyx to offer on your calls. You can force specific codecs by only checking one of the boxes.

You can configure your global application settings for outbound calls over here.

Assign your application to an outbound voice profile in order to make outbound calls.

You can limit the total number of outbound calls to phone numbers associated with this connection.

Once you've successfully created your Call Control application, it is given an application id that can be seen within the application settings as seen in the below picture.

The application id is used to reference or trigger your API calls programmatically. Don't forget to reference our developer documentation to see how you can control your calls with the different API commands available.

Click on " Create your first application" and assign a name to this application to better manage the application.
​

In this field, HTTP request method Telnyx will use to interact with your XML Translator webhooks. Either "GET" or "POST".

You will need to mention a URL where all the XML translator webhook events will be sent. Also, you can setup a fail-over URL. This URL to which Telnyx will deliver your XML Translator webhooks if we get an error response from your "Voice URL"

You will need to mention the HTTP request method Telnyx should use when requesting the "Status Callback" URL.

Specify the URL for Telnyx to send requests to containing information about call progress events.

When enabled, you will specify the numbers of seconds to wait for actual application before hanging up.

"Latency" directs Telnyx to route media through the site with the lowest round-trip time to the user's connection. Telnyx calculates this time using ICMP ping messages. This can be disabled by specifying a site to handle all media.

DTMF Type

There are three types in this field: RFC 2833, Inband and SIP INFO.

Enable capture of RTCP reports to build QoS Reports (found under Debugging > SIP Call Flow Tool). By default it's not enabled, clicked the "yes" radio button to enable it.

Specify if the call cost webhook should be sent. By default it's not enabled, clicked the "yes" radio button to enable it.
​

You can configure your global application settings for inbound calls over here.

Specify a subdomain that can be used to receive calls to a Connection, in the same way a phone number is used, from a SIP endpoint.

You can limit the total number of inbound calls to phone numbers associated with this connection.

By default, the radio button for no is checked. Select yes and save your settings if you want receive attestation information in the webhooks for incoming calls.

Select the codes using the check mark boxes that you would like Telnyx to offer on your calls. You can force specific codecs by only checking one of the boxes.

You can configure your global application settings for outbound calls over here.

Assign your application to an outbound voice profile in order to make outbound calls.

You can limit the total number of outbound calls to phone numbers associated with this connection.

Once you've successfully created your TeXML application, it is given an application id that can be seen within the application settings as seen in the below picture.

The application id is used to reference or trigger your API calls programmatically. Don't forget to reference our developer documentation to see how you can setup your XML instructions.