No response LLM being generated whiles using custo...
# support
a
When using a custom OpenAI API key in the system, the calls stop working after the initial greeting. The LLM is not generating any responses after the greeting message is played. This issue appears to be specific to custom OpenAI API key integration, as the system works correctly when using the default VAPI billing. What is the cause behind that? Steps to Reproduce: 1. Configure system with custom OpenAI API key 2. Initiate a call 3. Observe that only the greeting message is played 4. No further LLM responses are generated Expected Behavior: - System should continue conversation after greeting - LLM should generate responses throughout the entire call Actual Behavior: - System only plays the initial greeting - No LLM responses are generated after greeting - Logs show missing LLM streaming results Two call examples with logs attached: - Working call ID (with VAPI billing): 14731cb2-5546-46d9-a9da-de0354b4b890 - Failed call ID (with custom OpenAI key): ad91ed23-0d0a-44a3-9014-9ba813e854b0 Additional Context: - Problem was resolved when reverting to VAPI's default billing - Custom OpenAI key works properly when tested directly (not through VAPI) https://cdn.discordapp.com/attachments/1339884806229458946/1339884806774849586/Screenshot_2025-02-14_at_10.59.14.png?ex=67b05877&is=67af06f7&hm=50a2ced56ade060a9d2dde2c33da6e2cf5ec0224f11e88d119c7fa29de6ddf46& https://cdn.discordapp.com/attachments/1339884806229458946/1339884807139889162/Screenshot_2025-02-14_at_10.59.50.png?ex=67b05877&is=67af06f7&hm=318afa1ef79a8b42c9c8b08892614812babc50df30ab75b0a120ef8c38834481&
s
Hey @jezreel can you ping me to your #1211483291191083018 ticket and share all details such as call IDs.
a
Hi, sorry for long response, it's seems like I'm unable to provide you with additional details. As I can see that you have similar logs that I've got, so I will investigate why there is an issue with LLM not outputing tokens
c
The issue you encountered was because of the OpenAI change. There was nothing wrong with your end, and the problem has already been resolved.
54 Views