Yoann C.
03/03/2025, 6:47 PMVapi Support Bot
03/03/2025, 6:48 PMvoice
property. Here’s how you can set it up:
json
{
"voice": {
"provider": "azure",
"voiceId": "your-custom-voice-id"
}
}
Make sure to replace "your-custom-voice-id"
with the actual ID of your custom voice from Azure.
3. **Check Voice ID**: Double-check that the voice ID you are using matches the one in Azure. Sometimes, mismatched IDs can lead to errors.
4. **API Key and Permissions**: Ensure that your Azure API key has the necessary permissions to access the custom voice. If there are any restrictions, it might cause issues during the setup.
5. **Testing**: After configuring the voice, test the setup to ensure everything is working correctly. You can do this by checking voice samples to confirm clarity and performance.
### Common Errors to Watch For:
- **Voice Manifest File Not Found**: Ensure that the manifest file is correctly located and accessible.
- **API Key Issues**: Make sure you are using the correct and updated API key.
- **Compatibility**: Verify that the voice you are trying to use is compatible with the language and settings you need.
If you follow these steps and still encounter issues, feel free to share the specific error message you’re getting, and I can help troubleshoot further! 😊
Sources:
- [Importing Custom Azure Voices into VAPI](https://docs.vapi.ai/customization/custom-voices/custom-voice)
- [Common Errors Encountered When Configuring Azure Custom Voices in VAPI](https://discord.com/channels/1211482211119796234/1211483291191083018/1335770702074347520)Kyle Brunker
03/05/2025, 3:09 PMconst azureCredential = {
provider: 'azure',
service: 'speech',
region: 'your-azure-region',
apiKey: 'your-azure-api-key'
};
b) Voice Configuration:
const voiceConfig = {
provider: 'azure',
voiceId: 'your-custom-voice-id', // Format: 'custom-deployment-name'
speed?: number // Optional: 0.5 to 2.0
};
After that, The system will validate your voice.
Common Issues and Solutions:
\- Make sure your voiceId matches exactly what's shown in Azure Speech Studio
\- Verify your Azure credentials have access to the custom voice
\- Ensure the region matches where your custom voice is deployed