0

Conference disconnecting at 32 seconds

I am using a GET request to trigger my Tropo webapi app - it then calls a number and asks for a digit to be pressed, upon which it conferences the answering user to a conference ID.

This works fine **until **32 seconds after the user initially picked up, upon which they are disconnected. This is precisely 32 seconds *and 0ms* each time, according to the logs.

Is this a feature of development rather than production environment, or am I missing something?

Grateful for any thoughts, thanks :)

1 comment

Please sign in to leave a comment.