TransferCall issue between Vonage imported numbers...
# support
j
The following occurs : 1. I successfully call a Vonage imported phone number, connecting me to the right assistant. 2. This assistant tries to transfer the call to another phone number from Vonage, as instructed. This other phone number is also an imported Vonage number linked to another assistant from the same org. 3. However, the call ends abruptly before I was connected to this other assistant. Example call : CallId : 6c9fd65e-a6f4-4ac7-8ae2-71e74300c853 OrgId : 456ce6b0-9137-48db-a1a6-ad2771a175d4 Expected to get : successful transfer to +32460225067 What I get : call ends abruptly. I already deleted then re-added my Vonage credentials. Then I deleted and re-added all the Vonage phone numbers. Didn't solve the problem. From the VAPI logs, it seems the call transfer was requested: Model called tool: transferCall({"destination":"+32460225067"}) But from the Vonage logs, there doesn't seem to even be a request for this number 🤔
What worked : removing phone numbers first, then Vonage api keys, in that order. Then re-added API keys then phone numbers. Could someone explain why it works now ? Would like to avoid this issue in the future.
c
Your solution of removing phone numbers first, then Vonage API keys, and then re-adding them in reverse order fixed the issue because it properly realigned the associations between your phone numbers and Vonage application. \## Technical Explanation 1\. Application and Webhook Configuration When you add Vonage credentials to VAPI, the system: - Creates a Vonage application in your Vonage account - Sets up webhook endpoints for inbound calls and events - Stores the
vonageApplicationId
and
vonageApplicationPrivateKey
2\. Phone Number Association When you add a Vonage phone number, VAPI: - Associates that number with the application using
vonageApplicationId
- Configures the number to route calls through VAPI's webhook endpoints \## Why Your Order of Operations Matters By removing phone numbers first, you ensured they weren't still pointing to an application that would be deleted. When you re-added the API keys, VAPI created a fresh application with proper webhook configurations. Then adding the phone numbers back properly linked them to this new application. If done in the wrong order, you could end up with phone numbers pointing to non-existent applications or credentials that don't match what's in your Vonage account. By maintaining this order of operations when making changes to your Vonage configuration, you should avoid encountering this issue again.
j
Hello @Shubham Bajaj, this is very clear, thanks 🙏
Happy to mark this as solved ✅
5 Views