Fallback Destination Failed #outbound
# support
t
What does Property FallbackDestination should not existProperly number E164CheckEnabled should not exist ? What does this error mean https://cdn.discordapp.com/attachments/1272486046290022400/1272486046474436638/image.png?ex=66bb267b&is=66b9d4fb&hm=4cc55393eda72a4af909021df41e9a5227985f5fe4afb417ce1a016cd85b795d&
can you please help me with this
v
@Thrinadh Reddy The error message you're encountering suggests that there are properties in a configuration or a request that are not recognized or are not supposed to be present. Specifically: -
FallbackDestination should not exist
indicates that there is a property named
FallbackDestination
that is not expected or is not valid in the current context. -
Properly number E164CheckEnabled should not exist
seems to be a typo or a misinterpretation. It likely should read
Property E164CheckEnabled should not exist
, which would mean that the property
E164CheckEnabled
(which seems to refer to a setting for checking if phone numbers are in the E164 format) is also not expected or valid in the current context. This could be due to a number of reasons such as a recent API update where these properties have been deprecated, a mistake in the configuration file, or an incorrect API call. It's important to check the current API documentation or configuration schema to ensure that you are using the correct properties. If you need further assistance with this, please let me know more details or ask support for more info on this.
You can continue this conversation by mentioning me in the message.
t
I am using the UI Platform and why is this happening
how to remove that FallbackDestination
@Vapi
v
@Thrinadh Reddy To remove the
FallbackDestination
property from your configuration on the UI Platform, you would typically follow these steps: 1. **Access the Configuration Section**: Log in to the UI Platform and navigate to the section where you manage your configurations. This could be under settings, API configurations, or a similar section depending on the platform. 2. **Locate the Property**: Find the
FallbackDestination
property within your configuration. It might be part of a JSON object, XML configuration, or set through a visual interface. 3. **Remove or Edit**: If you're editing a JSON or XML file, you can simply delete the line containing the
FallbackDestination
property. If you're using a visual interface, there might be a delete or remove option next to the property. 4. **Save Changes**: After removing the property, save your changes. There might be a save button or similar action required to commit your changes. 5. **Test**: It's always a good idea to test your configuration after making changes to ensure that everything is working as expected. If you're unsure about any of these steps or if the platform has specific instructions, it would be best to consult the platform's documentation or reach out to their support team for guidance. If you need further assistance with this, please provide more details about the UI Platform you are using, and I'll do my best to help you out.
t
@User
s
share the assistant id.
t
3094861c-902a-4940-b505-0d8d264ea75e
@Shubham Bajaj please check the assistant id
s
@Thrinadh Reddy your using country code with number, if yes do it w/o country code. Also let me know how it goes.
t
Looks you unrolled some update and was able to make calls now. Thanks