I can not import my Telnyx phone number into the vapi. It's giving me the same error over and over again https://cdn.discordapp.com/attachments/1350395359666507838/1350395359871893507/image.png?ex=67d6952e&is=67d543ae&hm=cea2434fabd6855d081f1e8f38fe4a5ead42d20d9cca616039cf120074dec452&

Hi there! I see you're having trouble importing your Telnyx phone number into Vapi with a "The provided credentials are not valid" error. Let me help you troubleshoot this! 🔍 Here are some common causes and solutions for this error: 1. **API Key Issues**: - Make sure you're using the correct API key (private vs public) - Verify the key format in your request header is

Authorization: Bearer YOUR_API_KEY

- Allow time for newly generated keys to propagate [source](https://discord.com/channels/1211482211119796234/1211483291191083018/1336399188665040968) 2. **SIP Configuration**: - Check that your SIP trunk credentials are correctly configured - Verify the gateway IP (typically

sip.telnyx.com

for Telnyx) - Ensure your SIP URI is properly formatted [source](https://docs.vapi.ai/advanced/sip/telnyx) 3. **Required Credentials Check**: - Confirm you have all necessary credentials: - Vapi API key and secret - SIP domain, username, and password - Carrier details - Properly configured SIP URI [source](https://docs.vapi.ai/advanced/sip/telnyx) 4. **Endpoint Verification**: - Make sure you're using the correct API endpoint - Incorrect endpoints can result in authentication failures [source](https://discord.com/channels/1211482211119796234/1211483291191083018/1328923059905630238) Could you share which steps you've already tried? That would help me provide more specific guidance for your situation. Sources: - [Discord Thread on API Key Issues](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336399188665040968) - [Vapi Documentation on Telnyx Integration](https://docs.vapi.ai/advanced/sip/telnyx) - [Discord Thread on Endpoint Issues](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1328923059905630238)

@jamiroCJ could you share your orgId so I can take a look?

d32a865a-5166-4bab-85dd-e5bdbcc367cd

@jamiroCJ can you try now? The issue has been resolved on our end. It should work for you now.