@Andres Cardozo I understand that you're experiencing issues with the assistant's messages during calls, leading to either broken blocks or users hanging up due to the assistant not speaking. To address this, we need to review the clientMessages configuration for the assistant and ensure that the messages are set up correctly to engage the users without causing interruptions or silence that could lead to hang-ups. Could you please provide more details on how you would like the assistant to behave during the calls? Specifically, what messages should be sent and at what points during the interaction? This information will help us to adjust the settings accordingly and resolve the issue you're facing.

You can continue this conversation by mentioning me in the message.

This is happening with normal assistants

@Andres Cardozo For your reference, I am sharing the PCAP file and metadata about the call as well. The PCAP file is empty which clearly states something went wrong so yeah another recent call id will help. https://cdn.discordapp.com/attachments/1316852392209154048/1326905272429449247/Screenshot_2025-01-09_at_18.53.55.png?ex=67812055&is=677fced5&hm=6f38dff38f1fd58bb4a662ef57b0dbee6a8ffaa12070a6100f85446e6356f2a1& https://cdn.discordapp.com/attachments/1316852392209154048/1326905272807198752/Jambonz_Call_Data.pcap?ex=67812055&is=677fced5&hm=30fe273944046fb1f0ba1c72f0b1aad5b114191ae81274ca492585c9f19a3512&

@Andres Cardozo Looking at the previous thread PCAP data, we noticed there was a significant delay (about 27 seconds) from your end in responding to our INVITE request. While the PCAP shows timestamps going up to 42 seconds, you'll only hear 15 seconds of audio in the call recording (42 minus 27). This is because the call audio didn't actually connect until that 27-second mark. So any conversation that happened before the connection was established won't be captured in the recording.