Phone Target Capabilities

GET 
/v0/voice/phone_target_capabilities

What a Phone target may be configured to do, for THIS caller's org.

Two different facts, and the form needs both. They do NOT coincide, which is the whole reason this returns two fields:

rfc2833_dtmf -- is out-of-band a real choice here. Yes, for every organization: only Telnyx serves out-of-band, and resolve_pstn_provider routes an rfc2833 target to Telnyx whatever its org's carrier is. So this is false only while the master kill switch is off, and then for everyone.

default_dtmf_mechanism -- what a target that states no preference does. rfc2833 on a Telnyx org, inband for an org kept on Twilio by TWILIO_DEFAULT_ORG_IDS. The form must render this as its default rather than assuming in-band, or it will show "In-band" for a target that in fact dials out-of-band.

This is the field that varies per org, and it is advisory for display only. It must not be used to decide whether to OFFER out-of-band: an org whose default is in-band may still select rfc2833 per target, and a form that hid the control would make such a target uneditable without silently rewriting it.

Keep this route even if the switches are eventually retired. The app gates the control on rfc2833_dtmf === true and fails closed, so a 404 here hides the control from everybody -- the opposite of enabling it.

Advisory only. The server validates the value again at run submit (validate_dtmf_mechanism); a hidden control is not enforcement.

Request

Responses

200

Successful Response

422

Validation Error