----------------------------- **While I generate an answer, here are some sources that might be helpful**: * [List Calls]() * [Call Ended Reason]() * [Create Phone Call]() * [Get Call]() -----------------------------

### Answer The error you are encountering,

pipeline-error-azure-openai-llm-failed

, indicates a failure within the Azure OpenAI LLM pipeline. This is a known issue that has been discussed in community forums and may be related to specific function call configurations [(1)]() . Here are a few steps you can take: 1. **Check Your Function Configuration**: Ensure that the function schema is correctly defined. A common issue is having an invalid schema for a function, which can lead to this error. For example:

json
   {
       "name": "sendEmail",
       "description": "Used to send an email to a client.",
       "parameters": {
           "type": "object",
           "properties": {
               "emailAddress": { "type": "string" }
           },
           "required": ["emailAddress"]
       }
   }

2. **Test OpenAI Endpoint Directly**: You can try sending a direct request to the OpenAI endpoint to ensure that your function configuration and the OpenAI integration are working correctly. This can help isolate whether the issue is within Vapi or the OpenAI integration. 3. **Monitor Server Logs**: Ensure that your server is set up to handle POST requests appropriately. The OPTIONS call is a preflight request used in Cross-Origin Resource Sharing (CORS) to check permissions before making the actual POST request. If these are not handled correctly, the function call may fail. 4. **Check Vapi Status**: Occasionally, the problem may be on Vapi's end due to integration issues or service outages. Monitoring Vapi's status page or reaching out on their forums might provide insights. If these steps do not resolve the issue, it may be best to keep an eye on community forums for updates or potential bug fixes related to this error, [(2)]() , [(3)]() .

and then see if it is fault from vapi or your side

shouldn't it be sending a POST now that the headers are assigned? It keeps sending OPTIONS, seems odd

not sure why this was prematurely marked solved but I've figured it out, for those checking back here you need to add "x-vapi-secret" to the "Access-Control-Allow-Headers" header where handling CORS pre-flight.