Voice Model Mismatch: Assistant Setup vs. Logged Voice Provider
While reviewing the logs for recent calls, I noticed that the voice model referenced in the logs doesn’t match the one specified when triggering the call through the VAPI API.
Even though the API request explicitly sets a VAPI voice, the logs show a different provider (for example, 11Labs).
Could you please check whether this discrepancy is expected behavior or if there might be an issue with how the voice provider is being recorded or routed?
Call ID:
Even though the API request explicitly sets a VAPI voice, the logs show a different provider (for example, 11Labs).
Could you please check whether this discrepancy is expected behavior or if there might be an issue with how the voice provider is being recorded or routed?
Call ID:
019a2bb6-a9eb-744a-96df-13fc7a6e0acb
