Overview

TeXML is an XML based data structure used by Telnyx to build quick applications to be associated with your Telnyx phone numbers. When a call comes into one of your Telnyx Numbers, Telnyx makes an HTTP request to the URL endpoint you configured for that number. The endpoint will contain instructions telling Telnyx what to do next with the call.

Responses to the HTTP request are in an XML format that we call TeXML. TeXML allows you to specify instructions in your file using simple commands called verbs. TeXML Translator starts at the top of your TeXML file and executes your TeXML commands sequentially in the order they are arranged in the file.

| Overview | Dial | Conference | Enqueue | Gather | Leave | Hangup | Pause | Play | Record | Redirect |Reject | Say | Stream | Suppression| Transcription |

How TeXML Translator works

Check out our TeXML Setup Guide to get started on a simple TeXML text-to-speech application.

When a call is received by one of your Telnyx phone numbers, Telnyx lookup the URL endpoint you configured for that number and make an HTTP request to it. The URL endpoint then responds to the request with a TeXML file that instructs what to do next in the call. TeXML files have a standard .xml file extension.

Telnyx will read the instructions in the TeXML file, from top to bottom, and execute all the verbs/commands in order.

Outbound calls started via the TeXML Translator work the same way. When you start an outbound call, you also pass a link to a TeXML file. Telnyx will make a request to this file to determine how it should proceed with the call.

While a single TeXML document is executed at a time, many documents can be linked together and generated dynamically to create complex applications to fit any need.

TeXML Syntax

TeXML Translator is XML-based and consists of the following elements:

• <Response> element -- tag defining the body of the TeXML document
• verb -- an XML tag denoting the action that you want Telnyx to take
• noun -- the item for the action specified in the associated verb

Here is a simple TeXML file containing an example of a verb and noun used together:

<?xml version="1.0" encoding="UTF-8"?>

<!-- TeXML files must contain the Response element -->
<Response>
 <!-- Say and Dial are Verbs -->
    <Say>Thank you for calling Telnyx. Please hold.</Say>
    <Dial>
   <!-- Number is a Dial Noun -->
        <Number>+13129457420</Number>
    </Dial>
</Response>

Note: After pasting the above content, Kindly check and remove any new line added

Dynamic Parameters

When creating a TeXML set of instructions you can make use of Mustache Templates to generate instructions dynamically at runtime.

Inserting Dynamic Content

You can make use of Mustache Dynamic templating to insert content into your TeXML instructions through HTTP request parameters in the webhook url we use to fetch your TeXML set of instructions. For example, you could create a TeXML set of instructions that calls a number that is set until the HTTP request is made to fetch your TeXML instructions.

You first create your TeXML instructions using Mustache Templating and set the {{PhoneNumber}} as a variable like this

<?xml version="1.0" encoding="UTF-8"?>
<Response>
  <Dial>
    <Number>{{PhoneNumber}}</Number>
  </Dial>
</Response>

Note: After pasting the above content, Kindly check and remove any new line added

The phone number can now be replaced at runtime by setting your TeXML webhook url to have PhoneNumber as a parameter.

curl -X POST https://api.telnyx.com/v2/texml/calls/{connection_id} \
--data-urlencode "To=+13121230000" \
--data-urlencode "From=+13120001234" \
--data-urlencode "Url=https://www.example.com/texml.xml?PhoneNumber=+18771234567" \
--data-urlencode "StatusCallback=https://www.example.com/statuscallback-listener" \
--header "Authorization: Bearer APIAuthKey_fromPortal"

Note: After pasting the above content, Kindly check and remove any new line added

The request parameters set by Telnyx, i.e. CallSid, From and To are also available for the Mustache Template. The list of the parameters for each of the callback can be found on our developer documentation page.

Iterate Through Lists

You can set arrays as parameters in your TeXML webhook url and let Mustache Template handle them. If for example you want the dial command to have two numbers you could add a Numbers list parameter to your callback Url.

curl -X POST https://api.telnyx.com/v2/texml/calls/{connection_id} \
--data-urlencode "To=+13121230000" \
--data-urlencode "From=+13120001234" \
--data-urlencode "Url=https://www.example.com/texml.xml?PhoneNumbers[]=+18771234567&PhoneNumbers[]=+18771234568" \
--data-urlencode "StatusCallback=https://www.example.com/statuscallback-listener" \
--header "Authorization: Bearer APIAuthKey_fromPortal"

Note: After pasting the above content, Kindly check and remove any new line added

Then you can handle the PhoneNumbers parameter in the TeXML instructions using the following syntax.

<?xml version="1.0" encoding="UTF-8"?>
<Response>
  <Dial>
  {{#PhoneNumbers}}
    <Number>{{.}}</Number>
  {{/PhoneNumbers}}
  </Dial>
</Response>

Note: After pasting the above content, Kindly check and remove any new line added

This will end up being parsed as

<?xml version="1.0" encoding="UTF-8"?>
<Response>
  <Dial>
    <Number>+18771234567</Number>
    <Number>+18771234568</Number>
  </Dial>
</Response>

Note: After pasting the above content, Kindly check and remove any new line added

Render Conditional Content

Conditional content is supported by using if/else statements in the TeXML instructions. You could define a set of instructions to dial an specific number depending on From parameter present in the HTTP request.

<?xml version="1.0" encoding="UTF-8"?>
<Response>
{{#if From == +18771234567}}
  <Dial>
    <Number>+18771234568</Number>
  </Dial>
{{#elseif From == +18771234568}}
  <Dial>
    <Number>+18771234567</Number>
  </Dial>
{{#else}}
  <Say>No valid number is present</Say>
{{/if}}
</Response>

Note: After pasting the above content, Kindly check and remove any new line added

Supported operators are ==, != and no operator for checking if the parameter value is not null.

Response

The baseline of TeXML files is the <Response> tag.

All verbs in a TeXML file must be placed within a single parent <Response> element, and each file can only have a single one.

Verbs

A verb identifies the action to take.

When using Verbs one instruction must completed before the next one is executed. Verbs may have optional TeXML attributes that override the flow of execution, allowing you customize the verb behavior.

All verbs are case sensitive, so <Dial> and <dial> are not interchangeable.

Voice Verbs

The following verbs cause the specified action to take place during the call:

Nouns

A noun is what the verb uses to complete an action and is placed inside a verb element. A noun can be the text that is read in a call or other TeXML elements that represent the action, such as Number to dial or a SIP URI to transfer the call to.

<?xml version="1.0" encoding="UTF-8"?>
<Response>
 <Dial>
      <Sip>sip:[email protected]</Sip>
 </Dial>
</Response>

Note: After pasting the above content, Kindly check and remove any new line added

Each verb has its own set of nouns. See the documentation for a specific verb for more details.

Additional Request Parameters

Each time Telnyx makes a request to your application to fetch new TeXML, additional parameters with information about the call will be sent with the request to your URL.

PARAMETER	DESCRIPTION
CallSid	A unique identifier for this call, generated by Telnyx.
From	The phone number of the party that initiated the call. Phone numbers are formatted with a '+' and country code, e.g. +16175551212 E.164 format.
To	The phone number of the called party. Phone numbers are formatted with a '+' and country code, e.g. +16175551212 E.164 format.

Data Formats

Dates and Times

All dates and times in requests to and from TeXML files follow Telnyx API conventions: UTC, and presented in RFC 2822 format.

Phone Numbers

All numbers in requests to or from TeXML files follow Telnyx API conventions: E.164 format. Numbers in this format start with a plus sign ("+") and the country code.

SIP URIs follow Telnyx SIP Trunking and SIP Credentials conventions: sip:[email protected]

Dial

The <Dial> verb transfers an existing call to another destination. <Dial> will end this new call if: the called party does not answer, the number does not exist, or Telnyx receives a busy signal.

Verb Attributes

ATTRIBUTE	DESCRIPTION	OPTIONS	DEFAULT
action	Optional URL where TeXML will make a request to when the <Dial> call ends to retrieve a new set of TeXML instructions to continue the call flow.
method	HTTP request type used to retrieve the next set of instructions.	GET, POST	POST
callerId	Caller ID that must be a valid E.164 format number.
fromDisplayName	The fromDisplayName string to be used as the caller id name (SIP From Display Name) presented to the destination. The string should have a maximum of 128 characters, containing only letters, numbers, spaces, and -_~!.+ special characters. If ommited, the display name will be the same as the number in the callerId field.
hangupOnStar	The hangupOnStar attribute lets the initial caller hang up on the called party by pressing the '`*`' key on their phone. Does not apply for the Conference noun.	true, false	false
record	The record attribute lets you record both legs of a call within the associated <Dial> verb. It works with the <Number> and <Sip> nouns only. If you want to record the conference, please use record attribute on <Conference> noun. Recordings are available in two options: mono-channel or dual-channel.	do-not-record, record-from-answer, record-from-ringing, record-from-answer-dual, record-from-ringing-dual	do-not-record
recordMaxLength	Defines the maximum length for the recording in seconds.	0-14400, 0 for infinite	0
recordingStatusCallback	Optional URL that tells Telnyx where to make its GET or POST request when the recording is available.
recordingStatusCallbackMethod	HTTP request type used for recordingStatusCallback.	GET, POST	POST
recordingStatusCallbackEvent	The recording events for which Telnyx should a webhook on. Multiple events are separated by a space.	in-progress, completed, absent	completed
timeLimit	Sets the maximum duration in seconds of the call created by <Dial>.	60 - 14,400	14,400 (4 hours)
timeout	Sets the maximum time in seconds that Telnyx will wait for the dialed party to answer.	5 - 120	30
ringTone	The ringback tone played back to the caller.	at,au,bg,br,be,ch,cl,cn,cz,de,dk,ee,es,fi,fr,gr,hu,il,in,it,lt,jp,mx,my,nl,no,nz,ph,pl,pt,ru,se,sg,th,uk,us,us-old,tw,ve,za	us

Nouns

NOUN	DESCRIPTION	OPTIONAL ATTRIBUTES
<Number>	E.164 phone number.	method, sendDigits, statusCallback, statusCallbackEvent, statusCallbackMethod
<Sip>	SIP URI.	method, password, statusCallback, statusCallbackEvent, statusCallbackMethod, url, username
<Queue>	queue name	method, url

Send custom headers by appending them to the SIP URI -- just as you'd pass headers in a URI over HTTP. For example:

<?xml version="1.0" encoding="UTF-8"?>
<Response>
    <Dial>
        <Sip>
            sip:[email protected]?x-mycustomheader=foo&amp;x-myotherheader=bar
        </Sip>
    </Dial>
</Response>

Note: After pasting the above content, Kindly check and remove any new line added

Noun Attributes

<Number> and <Sip> Attributes

ATTRIBUTE	DESCRIPTION	OPTIONS	DEFAULT
statusCallback	A URL for Telnyx to send webhook requests to on each event specified in the statusCallbackEvent attribute for outbound calls only. Inbound Status Callback events can be configured for TeXML the connection settings in the Mission Control Portal.
statusCallbackEvent	The call events for which Telnyx should send a webhook. Multiple events are separated by a space.	initiated, ringing, answered, amd, dtmf, completed	completed
statusCallbackMethod	HTTP request type Telnyx should use when requesting the statusCallback URL.	GET, POST	POST
url	Optional URL to another TeXML document that can contain <Gather> and <Hangup> verbs so that the called party can chose to take an action on the incoming call before the two parties are connected. The callee will continue to hear ringback while the url document is executed.
method	HTTP request type used for url.	GET, POST	POST
machineDetection	Enables Answering Machine Detection. Note: add amd event type to statusCallbackEvent list to receive the detection result webhook.	Enable, Disable, DetectMessageEnd	Disable
detectionMode	Sets the Answering Detection mode.	Regular, Premium	Regular
machineDetectionTimeout	Maximum timeout threshold for overall detection, in miliseconds.	500 - 60000

<Number> Only Attributes

<Sip> Only Attributes

<Queue> Attributes

Simultaneous Dialing

You can use multiple <Number> and <Sip>nouns within a <Dial> verb to dial multiple phone numbers and SIP addresses at the same time. The first person to answer the call will be connected to the caller, while the rest of the call attempts are hung up:

<?xml version="1.0" encoding="UTF-8"?>
<Response>
  <Dial>
    <Number>+18775551212</Number>
    <Sip>sip:[email protected]</Sip>
    <Number>+18771234567</Number>
  </Dial>
</Response>

Note: After pasting the above content, Kindly check and remove any new line added

Examples

<?xml version="1.0" encoding="UTF-8"?>
<Response>
    <Dial action="/nextinstructions.php" callerId="+13120001234">+19999999999</Dial>
</Response>

Note: After pasting the above content, Kindly check and remove any new line added

<?xml version="1.0" encoding="UTF-8"?>
<Response>
    <Dial action="/nextinstructions.php" callerId="+13120001234">
      <Number statusCallback="https://foo.com/my_call_stats" statusCallbackEvent="initiated ringing answered completed">+19999999999</Number>
    </Dial>
</Response>

Note: After pasting the above content, Kindly check and remove any new line added

<?xml version="1.0" encoding="UTF-8"?>
<Response>
    <Dial action="/nextinstructions.php" callerId="+13120001234" hangupOnStar="true">
      <Sip statusCallback="https://foo.com/my_sip_call_stats" statusCallbackEvent="initiated">sip:[email protected]</Sip>
    </Dial>
</Response>

<?xml version="1.0" encoding="UTF-8"?>
<Response>
    <Dial action="/nextinstructions.php" callerId="+13120001234">
      <Number statusCallback="https://foo.com/my_call_stats" statusCallbackEvent="initiated ringing answered completed amd" machineDetection="Enable" detectionMode="Regular">+19999999999</Number>
    </Dial>
</Response>

Note: After pasting the above content, Kindly check and remove any new line added

<?xml version="1.0" encoding="UTF-8"?>
<Response>
    <Dial>
      <Queue url="/before_bridge_action">TestQueue</Queue>
    </Dial>
</Response>

Note: After pasting the above content, Kindly check and remove any new line added

Expected Callbacks

If action is set the following callback can be expected. when the call is completed. The new set of instructions can be sent as a response to it.

{
  "AccountSid" : "19a75cea-02c6-4b9a-84fa-c9bc8341feb8",
  "AnsweredTime" : "2023-09-06T09:05:14.860713Z",
  "CallLegId" : "7d87c352-4c94-11ee-99f7-02420a0daa69",
  "CallSessionId" : "7bf6178c-4c94-11ee-b679-02420aef02a0",
  "CallSid" : "v3:viLNGyAMjOw6H0AAmA3_CL4rbzYWgahKGqeoZ0Eu_TUYPeWs5w3z6w",
  "CallSidLegacy" : "v3:viLNGyAMjOw6H0AAmA3_CL4rbzYWgahKGqeoZ0Eu_TUYPeWs5w3z6w",
  "ConnectionId" : "2034058542482196149",
  "DataLocality" : "USA",
  "DialCallDuration" : "11",
  "DialCallSid" : "v3:t7KEildpy-HskSZeY78-WjFFcJMAaopsPfnkaH2J3NcByeTzgfVS1A",
  "DialCallSidLegacy" : "v3:t7KEildpy-HskSZeY78-WjFFcJMAaopsPfnkaH2J3NcByeTzgfVS1A",
  "DialCallStatus" : "completed | busy | no-answer | failed",
  "EndTime" : "2023-09-06T09:05:26.720715Z",
  "From" : "+13122010094",
  "OccurredAt" : "2023-09-06T09:05:26.720715Z",
  "OrganizationId" : "19a75cea-02c6-4b9a-84fa-c9bc8341feb8",
  "StartTime" : "2023-09-06T09:05:14.080710Z",
  "To" : "+12029925624",
  "UserId" : "19a75cea-02c6-4b9a-84fa-c9bc8341feb8",
}

If statusCallbackEvent are set you can expect the following webhooks.

initiated

{
   "AccountSid": "cb6cfbbc-eb00-41af-a3f3-0d7b32009e4b",
   "CallSid": "v2:7V3r4VFCGLTzKLOveE0-7vM9dX17-NRQgU1byo-uuOIX9JcDadLLKw",
   "CallSidLegacy": "v2:7V3r4VFCGLTzKLOveE0-7vM9dX17-NRQgU1byo-uuOIX9JcDadLLKw",
   "CallStatus": "initiated",
   "CallbackSource": "call-progress-events",
   "From": "+18445931290",
   "ParentCallSid": "v2:qiaymU9Ij90xJRRkYGWHOIx_41EVJPrzlny2zC67hwL1wVIUnnMrqQ",
   "ParentCallSidLegacy": "v2:qiaymU9Ij90xJRRkYGWHOIx_41EVJPrzlny2zC67hwL1wVIUnnMrqQ",
   "SequenceNumber": "0",
   "Timestamp": "2021-04-28 21:51:13.591099Z",
   "To": "+13122010055"
}

Note: After pasting the above content, Kindly check and remove any new line added

ringing

{
   "AccountSid": "cb6cfbbc-eb00-41af-a3f3-0d7b32009e4b",
   "CallSid": "v2:7V3r4VFCGLTzKLOveE0-7vM9dX17-NRQgU1byo-uuOIX9JcDadLLKw",
   "CallSidLegacy": "v2:7V3r4VFCGLTzKLOveE0-7vM9dX17-NRQgU1byo-uuOIX9JcDadLLKw",
   "CallStatus": "ringing",
   "CallbackSource": "call-progress-events",
   "From": "+18445931290",
   "ParentCallSid": "v2:qiaymU9Ij90xJRRkYGWHOIx_41EVJPrzlny2zC67hwL1wVIUnnMrqQ",
   "ParentCallSidLegacy": "v2:qiaymU9Ij90xJRRkYGWHOIx_41EVJPrzlny2zC67hwL1wVIUnnMrqQ",
   "SequenceNumber": "1",
   "Timestamp": "2021-04-28 21:51:13.591107Z",
   "To": "+13122010055"
}

Note: After pasting the above content, Kindly check and remove any new line added

in-progress

{
   "AccountSid": "cb6cfbbc-eb00-41af-a3f3-0d7b32009e4b",
   "CallSid": "v2:7V3r4VFCGLTzKLOveE0-7vM9dX17-NRQgU1byo-uuOIX9JcDadLLKw",
   "CallSidLegacy": "v2:7V3r4VFCGLTzKLOveE0-7vM9dX17-NRQgU1byo-uuOIX9JcDadLLKw",
   "CallStatus": "in-progress",
   "CallbackSource": "call-progress-events",
   "From": "+18445931290",
   "ParentCallSid": "v2:qiaymU9Ij90xJRRkYGWHOIx_41EVJPrzlny2zC67hwL1wVIUnnMrqQ",
   "ParentCallSidLegacy": "v2:qiaymU9Ij90xJRRkYGWHOIx_41EVJPrzlny2zC67hwL1wVIUnnMrqQ",
   "SequenceNumber": "2",
   "Timestamp": "2021-04-28 21:51:15.532975Z",
   "To": "+13122010055"
}

Note: After pasting the above content, Kindly check and remove any new line added

completed

{
   "AccountSid": "cb6cfbbc-eb00-41af-a3f3-0d7b32009e4b",
   "CallDuration": "2",
   "CallSid": "v2:7V3r4VFCGLTzKLOveE0-7vM9dX17-NRQgU1byo-uuOIX9JcDadLLKw",
   "CallSidLegacy": "v2:7V3r4VFCGLTzKLOveE0-7vM9dX17-NRQgU1byo-uuOIX9JcDadLLKw",
   "CallStatus": "completed",
   "CallbackSource": "call-progress-events",
   "From": "+18445931290",
   "HangupSource": "",
   "ParentCallSid": "v2:qiaymU9Ij90xJRRkYGWHOIx_41EVJPrzlny2zC67hwL1wVIUnnMrqQ",
   "ParentCallSidLegacy": "v2:qiaymU9Ij90xJRRkYGWHOIx_41EVJPrzlny2zC67hwL1wVIUnnMrqQ",
   "RecordingDuration": "5",
   "RecordingUrl": "https://recording.com/your-recording-url",
   "SequenceNumber": "3",
   "Timestamp": "2021-04-28 21:51:18.731479Z",
   "To": "+13122010055"
}

Note: After pasting the above content, Kindly check and remove any new line added

amd

{
   "AccountSid": "cb6cfbbc-eb00-41af-a3f3-0d7b32009e4b",
   "AnsweredBy": "machine_start|human|fax|machine_end_beep|machine_end_other|unknown",
   "CallSid": "v2:7V3r4VFCGLTzKLOveE0-7vM9dX17-NRQgU1byo-uuOIX9JcDadLLKw",
   "CallSidLegacy": "v2:7V3r4VFCGLTzKLOveE0-7vM9dX17-NRQgU1byo-uuOIX9JcDadLLKw",
   "MachineDetectionDuration": "23357"
}

Note: After pasting the above content, Kindly check and remove any new line added

If recordingStatusCallbackEvent are set you can expect the following webhooks.

in-progress

{
   "AccountSid": "cb6cfbbc-eb00-41af-a3f3-0d7b32009e4b",
   "CallSid": "v2:qiaymU9Ij90xJRRkYGWHOIx_41EVJPrzlny2zC67hwL1wVIUnnMrqQ",
   "CallSidLegacy": "v2:qiaymU9Ij90xJRRkYGWHOIx_41EVJPrzlny2zC67hwL1wVIUnnMrqQ",
   "From": "[email protected]",
   "RecordingChannels": "1",
   "RecordingSource": "DialVerb",
   "RecordingStatus": "in-progress",
   "To": "+12132045020"
}

Note: After pasting the above content, Kindly check and remove any new line added

completed

{
   "AccountSid": "cb6cfbbc-eb00-41af-a3f3-0d7b32009e4b",
   "CallSid": "v2:qiaymU9Ij90xJRRkYGWHOIx_41EVJPrzlny2zC67hwL1wVIUnnMrqQ",
   "CallSidLegacy": "v2:qiaymU9Ij90xJRRkYGWHOIx_41EVJPrzlny2zC67hwL1wVIUnnMrqQ",
   "From": "[email protected]",
   "RecordingChannels": "1",
   "RecordingDuration": "5",
   "RecordingSid": "35094891-3290-4142-b2c2-b2eda57534cf",
   "RecordingSource": "DialVerb",
   "RecordingStatus": "completed",
   "RecordingUrl": "https://recording.com/your-recording-url",
   "To": "+12132045020"
}

Note: After pasting the above content, Kindly check and remove any new line added

Status Callback HTTP Attributes

The attributes contained in the statusCallback request to your URL.

ATTRIBUTE	DESCRIPTION
AccountSid	A unique identifier for the account generating this call.
CallSid	A unique identifier for this call, generated by Telnyx.
ParentCallSid	A unique identifier for the parent call.
CallStatus	A descriptive status for the call. The value is one of initiated, ringing, in-progress, completed, busy or canceled.
Timestamp	The timestamp when the event was fired, given as UTC in RFC 2822 format.
CallbackSource	A string that describes the source of the webhook. This is provided to help disambiguate why the webhook was made. On Status Callbacks, this value is always call-progress-events.
From	The outbound caller number.
To	The inbound callee number.
RecordingDuration	Recording duration in seconds.
RecordingUrl	Url where the recording can be downloaded from.
RecordingSid	A unique identifier for the recording, generated by Telnyx.
RecordingChannels	1 for mono-channel, 2 for dual-channel
RecordingStatus	The staus for the recording. The value is one of in-progress, completed or absent.
SequenceNumber	A sequence number ordering the multiple callbacks received. First callback has the lowest, last callback the highest.

Conference

The <Dial> verb's <Conference> noun allows you to connect to a conference room. Much like how the <Number> noun allows you to connect to another phone number, the <Conference> noun allows you to connect to a named conference room and talk with the other callers who have also connected to that room. Conference is commonly used as a container for calls when implementing hold, transfer, and barge. If the specified conference name does not exist, a new conference will be created. More <Conference> attributes are coming soon.

Verb Attributes

Example

<?xml version="1.0" encoding="UTF-8"?>
<Response>
  <Dial>
    <Conference>Room 1234</Conference>
  </Dial>
</Response>

Note: After pasting the above content, Kindly check and remove any new line added

Expected Callbacks

If statusCallbackEvent are set you can expect the following webhooks.

join

{
   "AccountSid": "cb6cfbbc-eb00-41af-a3f3-0d7b32009e4b",
   "CallSid": "v2:r3Cj9j-Hx7NAZETtYpdgktVUYKhsc8D1mSmzY8_6r4HHZYViWIs6Fw",
   "CallSidLegacy": "v2:r3Cj9j-Hx7NAZETtYpdgktVUYKhsc8D1mSmzY8_6r4HHZYViWIs6Fw",
   "ConferenceSid": "58b4eda9-03de-4bee-9178-d0e10d83e519",
   "FriendlyName": "Room 1234",
   "From": "[email protected]",
   "SequenceNumber": "1",
   "StatusCallbackEvent": "participant-join",
   "Timestamp": "2021-04-28 22:51:29.993535Z",
   "To": "+12132045020"
}

Note: After pasting the above content, Kindly check and remove any new line added

leave

{
   "AccountSid": "cb6cfbbc-eb00-41af-a3f3-0d7b32009e4b",
   "CallSid": "v2:r3Cj9j-Hx7NAZETtYpdgktVUYKhsc8D1mSmzY8_6r4HHZYViWIs6Fw",
   "CallSidLegacy": "v2:r3Cj9j-Hx7NAZETtYpdgktVUYKhsc8D1mSmzY8_6r4HHZYViWIs6Fw",
   "ConferenceSid": "58b4eda9-03de-4bee-9178-d0e10d83e519",
   "FriendlyName": "Room 1234",
   "From": "[email protected]",
   "SequenceNumber": "3",
   "StatusCallbackEvent": "participant-leave",
   "Timestamp": "2021-04-28 22:51:47.114479Z",
   "To": "+12132045020"
}

Note: After pasting the above content, Kindly check and remove any new line added

end

{
   "AccountSid": "cb6cfbbc-eb00-41af-a3f3-0d7b32009e4b",
   "CallSid": "v2:0YXD2QVLtba0UDTe3k6H9gEsAEs4qRLsuy6u_zoS364PKR6DApuKuw",
   "CallSidLegacy": "v2:0YXD2QVLtba0UDTe3k6H9gEsAEs4qRLsuy6u_zoS364PKR6DApuKuw",
   "ConferenceSid": "58b4eda9-03de-4bee-9178-d0e10d83e519",
   "FriendlyName": "Room 1235",
   "From": "[email protected]",
   "SequenceNumber": "4",
   "StatusCallbackEvent": "conference-end",
   "Timestamp": "2021-04-28 22:51:51.480853Z",
   "To": "+12132045020"
}

Note: After pasting the above content, Kindly check and remove any new line added

speaker

{
   "AccountSid": "cb6cfbbc-eb00-41af-a3f3-0d7b32009e4b",
   "CallSid": "v2:0YXD2QVLtba0UDTe3k6H9gEsAEs4qRLsuy6u_zoS364PKR6DApuKuw",
   "CallSidLegacy": "v2:0YXD2QVLtba0UDTe3k6H9gEsAEs4qRLsuy6u_zoS364PKR6DApuKuw",
   "ConferenceSid": "58b4eda9-03de-4bee-9178-d0e10d83e519",
   "FriendlyName": "Room 1235",
   "From": "[email protected]",
   "SequenceNumber": "5",
   "StatusCallbackEvent": "participant-speech-start",
   "Timestamp": "2021-04-28 22:51:51.480853Z",
   "To": "+12132045020"
}

Note: After pasting the above content, Kindly check and remove any new line added

Status Callback HTTP Attributes

The attributes contained in the statusCallback request to your URL.

ATTRIBUTE	DESCRIPTION
AccountSid	A unique identifier for the account generating this call.
CallSid	A unique identifier for this call, generated by Telnyx.
ConferenceSid	A unique identifier for this conference, generated by Telnyx.
FriendlyName	Name given to the conference.
From	The outbound caller number.
Timestamp	The timestamp when the event was fired, given as UTC in RFC 2822 format.
To	The inbound callee number.
SequenceNumber	A sequence number ordering the multiple callbacks received. First callback has the lowest, last callback the highest.
StatusCallbackEvent	Event generating the callback.

Enqueue

The <Enqueue> verb enqueues current call in a call queue.

Verb Attributes

Examples

<?xml version="1.0" encoding="UTF-8"?>
<Response>
    <Enqueue waitUrl="/wait_in_queue">TestQueue</Enqueue>
</Response>

Note: After pasting the above content, Kindly check and remove any new line added

<?xml version="1.0" encoding="UTF-8"?>
<Response>
    <Enqueue maxWaitTimeSecs="60" action="/dequeue_action">TestQueue</Enqueue>
</Response>

Note: After pasting the above content, Kindly check and remove any new line added

Gather

The <Gather> verb collects DTMF tones during a call. <Say> can be nested within <Gather> to create an interactive IVR with text-to-speech.

Verb Attributes

Nouns

Example

<?xml version="1.0" encoding="UTF-8"?>
<Response>
    <Gather action="/processdtmf.php" finishOnKey="*" timeout="20">
        <Say>Please press 1 for sales, or 2 for support. Press * to exit the menu.</Say>
    </Gather>
   <Say>We did not receive any input. Goodbye!</Say>
</Response>

Note: After pasting the above content, Kindly check and remove any new line added

Expected Callbacks

action

{
    "AccountSid":"cb6cfbbc-eb00-41af-a3f3-0d7b32009e4b",
    "CallSid":"v2:DPNqxVjTNtQYaKdcKbU0QgRFrQ3YzuAQrVYC4Ggcuq7zTpDkUB7A4w",
    "CallSidLegacy":"v2:DPNqxVjTNtQYaKdcKbU0QgRFrQ3YzuAQrVYC4Ggcuq7zTpDkUB7A4w",
    "Digits":"1",
    "From":"[email protected]",
    "To":"+12132045020"
}

Note: After pasting the above content, Kindly check and remove any new line added

Leave

The <Leave> verb removes a call from queue and continues with the next verb after the original <Enqueue>.

Verb Attributes

The <Leave> verb doesn't support any attributes.

Example

<?xml version="1.0" encoding="UTF-8"?>
<Response>
    <Leave />
</Response>

Note: After pasting the above content, Kindly check and remove any new line added

Hangup

The <Hangup> verb ends the current call. There are no attributes associated with <Hangup> and no nouns can be nested within it.

Example

<?xml version="1.0" encoding="UTF-8"?>
<Response>
    <Say>Support line is closed. Please try again tomorrow.</Say>
    <Hangup />
</Response>

Note: After pasting the above content, Kindly check and remove any new line added

Expected Callbacks

completed

{
   "AccountSid": "cb6cfbbc-eb00-41af-a3f3-0d7b32009e4b",
   "CallDuration": "2",
   "CallSid": "v2:7V3r4VFCGLTzKLOveE0-7vM9dX17-NRQgU1byo-uuOIX9JcDadLLKw",
   "CallSidLegacy": "v2:7V3r4VFCGLTzKLOveE0-7vM9dX17-NRQgU1byo-uuOIX9JcDadLLKw",
   "CallStatus": "completed",
   "CallbackSource": "call-progress-events",
   "From": "+18445931290",
   "HangupSource": "callee",
   "SequenceNumber": "0",
   "Timestamp": "2021-04-28 21:51:18.731479Z",
   "To": "+13122010055"
}

Note: After pasting the above content, Kindly check and remove any new line added

Status Callback HTTP Attributes

The attributes contained in the statusCallback request to your URL.

ATTRIBUTE	DESCRIPTION
AccountSid	A unique identifier for the account generating this call.
CallSid	A unique identifier for this call, generated by Telnyx.
CallStatus	A descriptive status for the call. The value is one of completed, busy or canceled.
Timestamp	The timestamp when the event was fired, given as UTC in RFC 2822 format.
CallbackSource	A string that describes the source of the webhook. This is provided to help disambiguate why the webhook was made. On Status Callbacks, this value is always call-progress-events.
From	The outbound caller number.
To	The inbound callee number.
SequenceNumber	A sequence number ordering the multiple callbacks received. First callback has the lowest, last callback the highest.
HangupSource	Source of the hangup. The value can be callee or caller

HttpRequest

The <HttpRequest> verb sends a request to the external servers. It consists of 2 child nodes <Request> and <Response>

Request

The <Request> node defines all the attributes of the request. It can have 2 child nodes <Headers> and <Body>

Request Attributes

Example

<Response>
    <HttpRequest>
        <Request url="https://example.com" method="POST" async=”true”>
        <Headers>
            <Header>
                <Key>Authorization</Key>
                <Value>Bearer API_key</Value>
            </Header>
            <Header>
                <Key>Content-Type</Key>
                <Value>application/json</Value>
            </Header>
        </Headers>
        <Body>
        <![CDATA[
                {
                    "from":{{From}}
                }
                ]]>
        </Body>
        </Request>
    </HttpRequest>
</Response>

Response

The <Response> node allows assigning required parts of the response to the variables that will be passed to the action url. It will be triggered only if the async is set to false.

Example

<Response>
    <HttpRequest>
        <Request url="https://example.com" method="POST" async=”false”>
        ...
        </Request>
        <Response>
            <Type>JSON</Type>
            <StatusCode>200</StatusCode>
            <Content>
                <Field>
                    <Name>contact.name.first</Name>
                    <Value>first_name</Value>
                </Field>
                <Field>
                    <Name>contact.name.last</Name>
                    <Value>last_name</Value>
                </Field>
            </Content>
        </Response>
    </HttpRequest>
</Response>

Pause

The <Pause> verb waits silently for a specified number of seconds or one second by default. No nouns can be nested within <Pause> and a self-closing tag must be used.

Verb Attributes

Example

<?xml version="1.0" encoding="UTF-8"?>
<Response>
    <Pause length="5"/>
</Response>

Note: After pasting the above content, Kindly check and remove any new line added

Play

The <Play> verb plays an MP3 or WAV audio file, that Telnyx fetches from the URL you configure, back to the caller.

<Play> can be used independently as a verb or nested within <Gather> as a noun to play an audio file while waiting for DTMF tones.

Verb Attributes

Example

<?xml version="1.0" encoding="UTF-8"?>
<Response>
  <Gather action="/processdtmf.php">
    <Play loop="10">http://www.example.com/sounds/greeting.wav</Play>
  </Gather>
</Response>

Note: After pasting the above content, Kindly check and remove any new line added

Record

The <Record> verb creates an audio file with the call audio. If a recordingStatusCallback, Telnyx will deliver the URL for the recording to that address once the call has ended. Recording URLs are valid for 10 minutes after the call has ended. All recordings are also available via the Telnyx Mission Control Portal .

Verb Attributes

Additional Action Parameters

recordingStatusCallback will be used to deliver the final URL and information on the call recording. If available TeXML will also send recording information along with the request to the action URL with the following parameters:

Example

<?xml version="1.0" encoding="UTF-8"?>
<Response>
    <Record action="/recordingfinish.php" recordingStatusCallback="https://wwww.foo.com/recording-storage/" playBeep="true" finishOnKey="*9"/>
    <Say>
        You reached Telnyx Sales voicemail.
        Please leave a message after the beep.
        Press the pound key when finished.
    </Say>
</Response>

Note: After pasting the above content, Kindly check and remove any new line added

Redirect

The <Redirect> verb transfers control of the current call to another TeXML application. This is useful to create a tree structure of TeXML files for different applications. No nouns can be nested within <Redirect>.

Verb Attributes

Example

<?xml version="1.0" encoding="UTF-8"?>
<Response>
    <Redirect>http://www.example.com/TeXML/redirect.xml</Redirect>
</Response>

Note: After pasting the above content, Kindly check and remove any new line added

Refer

The <Refer> verb in Telnyx allows you to transfer a phone call to another SIP infrastructure during a TeXML call. You can initiate it at any point during the call. When you use the <Refer> verb, Telnyx will replace the original call with a new call to the external system you specify, effectively transferring the call to that system.

Verb Attributes

Example

<?xml version="1.0" encoding="UTF-8"?>
<Response>
    <Refer>
        <Sip>sip:[email protected]</Sip>
    </Refer>
</Response>

Note: After pasting the above content, Kindly check and remove any new line added

Expected Callbacks

If action is set you can expect the following webhook when the <Refer> verb finishes. New set of TeXML instructions should be returned in response.

{
  "AccountSid": "6d547b4f-993a-4e87-b95c-2d9460b3824b",
  "CallSid": "v3:wf0h6MLq0PIHItrkFyEPM0WLPAarG_fUA2MLQqkLYRhRRrCqnT6TPg",
  "CallSidLegacy": "v3:wf0h6MLq0PIHItrkFyEPM0WLPAarG_fUA2MLQqkLYRhRRrCqnT6TPg",
  "ReferCallStatus": "in-progress",
  "ReferSipResponseCode": "202",
  "NotifySipResponseCode": "200",
  "Timestamp": "2021-04-28 21:51:13.591099Z"
}

Note: After pasting the above content, Kindly check and remove any new line added

Action Callback HTTP Attributes

The attributes contained in the action request to your URL.

ATTRIBUTE	DESCRIPTION
AccountSid	A unique identifier for the account generating this call.
CallSid	A unique identifier for this call, generated by Telnyx.
ReferCallStatus	Provides new call status based on SIP NOTIFY messages. May be omitted if REFER fails or no NOTIFY requests are received. Possible values: in-progress, busy, canceled, failed
ReferSipResponseCode	This indicates the SIP response code that Telnyx receives from the SIP endpoint in response to the REFER request.
NotifySipResponseCode	Reflects final SIP response code on referred leg, based on NOTIFY messages. May be omitted if REFER fails or no NOTIFY requests are received.
Timestamp	The timestamp when the event was fired, given as UTC in RFC 2822 format.

Reject

The <Reject> verb rejects a call to your Telnyx number. It is effectively an exit statement from the current document, as there is no way to return to any instructions listed after the <Reject> verb. If placed as the very first verb in an incoming call, <Reject> will prevent the call from being answered and will incur no cost. If placed elsewhere in the call, the call will hang up but will be charged up to that point.

You can't nest any verbs within <Reject> and you can't nest <Reject> in any other verbs.

Verb Attributes

Example

<?xml version="1.0" encoding="UTF-8"?>
<Response>
    <Reject />
</Response>

Note: After pasting the above content, Kindly check and remove any new line added

Say

The <Say> verb speaks the text specified back to the caller enabling text to speech for any application.

Verb Attributes

Example

<?xml version="1.0" encoding="UTF-8"?>
<Response>
    <Say voice="alice">This is a premium Amazon Polly text-to-speech message!</Say>
</Response>

Note: After pasting the above content, Kindly check and remove any new line added

Stream

The <Stream> instruction starts streaming the media from a call to a specific WebSocket address in near-realtime. Audio will be delivered as base64-encoded RTP packets, wrapped in JSON payloads. When used with <Start> verb it starts asynchronous stream to your websocket destination url. For synchronous bi-directional stream please use <Connect> verb.

<Stream> Attributes

Examples

<?xml version="1.0" encoding="UTF-8"?>
<Response>
  <Start>
    <Stream url="wss://yourdomain.com/stream" track=”both_tracks” />
  </Start>
</Response>

Note: After pasting the above content, Kindly check and remove any new line added

Suppression

The <Suppression> instruction starts noise suppression on the call to improve audio quality.

<Suppression> Attributes

Examples

<?xml version="1.0" encoding="UTF-8"?>
<Response>
  <Start>
    <Suppression direction="both" />
  </Start>
</Response>

Note: After pasting the above content, Kindly check and remove any new line added

Transcription

The <Transcription> instruction starts real-time transcription on the call.

<Transcription> Attributes

Examples

<?xml version="1.0" encoding="UTF-8"?>
<Response>
  <Start>
    <Transcription language="en" interimResults="true" transcriptionCallback="/transcription" />
  </Start>
</Response>

Note: After pasting the above content, Kindly check and remove any new line added

Stop

The <Stop> verb stops specified by noun instruction on a call.

Nouns

Examples

<?xml version="1.0" encoding="UTF-8"?>
<Response>
  <Stop>
    <Stream />
  </Stop>
</Response>

Note: After pasting the above content, Kindly check and remove any new line added