14233: Dial->Conference: Invalid Timeout

This error occurs when you send a Conference instruction for a TaskRouter reservation and the Timeout value is not a valid integer. For a Conference instruction, Timeout controls how long Twilio rings the phone associated with the Worker's contact_uri before assuming there is no answer. The default is 60 seconds and the maximum is 999 seconds.

• Your application sent Timeout as a non-integer value, such as text, a decimal, or an empty value, instead of an integer number of seconds.
• Your application sent a Timeout value greater than 999 seconds for the Conference instruction.
• If you use the TaskRouter JavaScript SDK, your reservation.conference() call passed a timeout value that does not represent integer seconds.

• Send Timeout as an integer number of seconds, for example 30.
• Keep Timeout at 999 seconds or less. If you do not need a custom value, omit Timeout and use the default of 60 seconds.
• Validate and sanitize the Timeout value in your application before you send the Conference instruction or call reservation.conference(). Reject blank, non-numeric, and decimal values before making the request. This follows from the requirement that Timeout be an integer.

• Task Reservation Resource
• TaskRouter JavaScript SDK: reservation.conference
• TwiML Voice: <Conference>