VAPI•5mo ago

vonage-rejected error by transient agent calling

Used to happen very seldom. Lately depending on the time of day it happens as much as 50% of calls... What am I doing wrong and what does this cryptic error really mean under the covers? sending a call every 7-10 seconds with 4 numbers in rotation is nowehere close to any rate limits is it?

Samples; 9ffa7588-f501-468c-835b-90a315c5bee9, b835c64c-8b5b-49ce-bea7-9db0cdb37d62, 7eec09bf-5bdf-4e52-b95a-084537d7bb93, 1612a088-6dec-4cd3-9a2d-041d17ff5a74, e7bf9eb7-5d8c-474e-b375-918ae3bd8743, 3728c1f2-15b8-44be-9faf-d09445ee87b6

KyleAPP•8/21/25, 10:42 PM

We are seeing these connection status updates in our logs:

🔵 04:38:13:047 Call `b835c64c-8b5b-49ce-bea7-9db0cdb37d62` Waited 300s But Transport Never Connected.

🔵 04:38:13:047 Call `b835c64c-8b5b-49ce-bea7-9db0cdb37d62` Waited 300s But Transport Never Connected.

This basically means it timed out before Vonage could accept the call. If there are any logs on the Vonage side for these calls, it might be worth checking especially if they have PCAP files. That would tell you more about the connection and why it was rejected in the first place. Vonage support may also have some more details about the issue, but right now it could be a myriad of things such as incompatible codecs, caller ID restrictions, account & service related issues such as geographic restrictions and rate limiting too.

Please verify with vonage support and your account details to ensure everything is configured for a successful call and let us know what you find

vonage-rejected error by transient agent calling

Similar Threads

Similar Threads

Similar Threads