To test the feature I have set my server-url to an incorrect endpoint. When I call my vapi number it instantly goes to "Line busy". In my call logs it shows "Phone call provider closed". I tried testing the message parameter within fallbackDestination, though even with a message set it would not say anything and goes straight to "line-busy" I have used the API to update my vonage phone number. The response I get back is this: (with private info removed) OK 200

{
  "id": "000000000000000000000",
  "orgId": "0000000000000000000000000",
  "number": "+440000000000",
  "createdAt": "2024-05-17T10:57:23.402Z",
  "updatedAt": "2024-07-23T11:20:55.865Z",
  "name": "dev",
  "credentialId": "0000000000000000000000000",
  "fallbackDestination": {
    "type": "number",
    "number": "+440000000000",
    "numberE164CheckEnabled": true
  }
}

CallID's: d6604d17-d264-4ced-9c2e-07bb30d14b1f 1d9c600c-1c82-44f7-a527-a9805b7c5024 Thanks

@Jotham It sounds like you're experiencing issues with the fallback mechanism not triggering the expected message when your server URL is incorrect. To address this, let's ensure that the fallbackDestination is configured correctly to handle such scenarios. The response you've provided indicates that the fallbackDestination is set to a number, which means it should redirect the call to that specified number when the primary action fails. However, if you're expecting a message to be played instead, we might need to adjust the configuration to include a message parameter or use a different fallback mechanism that supports message playback. Could you please confirm if you want the fallback to play a message or redirect the call to another number? If you want to play a message, we'll need to update the fallbackDestination configuration accordingly. If the intention is to redirect the call and it's not working, we may need to investigate further to ensure the number provided is correct and capable of receiving calls. In the meantime, if you have any specific changes you'd like to make to the fallbackDestination or any other settings, please let me know, and I can assist you with that. If you're unsure of the next steps or need further assistance, please ask support for more info on this.

@Jotham The fallback destination for an inbound call will be transferred to if: 1. .

assistantId

is not set 2.

squadId

is not set 3.

assistant-request

message to the

serverUrl

fails If this is not set and above conditions are met, the inbound call is hung up with an error message.

Understood. I believe I am testing 3. assistant-request message to the serverUrl fails. I have also tested with an incorrect model name, which normally would result in an error message being spoken.

For message: This is the message to say before transferring the call to the destination. If this is not provided and transfer tool messages is not provided, default is "Transferring the call now".If set to "", nothing is spoken.

I understand, I tried setting the message to "Error with phone number, transferring the call" It did not speak any message, it just showed "line-busy" on my phone To clarify I think the feature is broken.

allow me some time to get back to you

Okay

It would be handy to have this fallback to dedicated assistant phone number if the account is over capacity, so that there is a simpler method for capacity planning.

hey The fallback destination for an inbound call will be transferred to if: . assistantId is not set squadId is not set assistant-request message to the serverUrl fails