Hello, I'm having an issue as i'm not receiving the end-of-call-report only in case the called customer rejects the call (customer-busy). I'm getting it from everything else except for this.

@Madame Hello! I'm here to help you with your issue. It sounds like you're expecting to receive an end-of-call report when a call is rejected by the customer, but it's not happening. To assist you better, could you please confirm if you have a specific Server URL set up to receive these reports, and if so, whether it's correctly configured to handle the "customer-busy" event? Additionally, it would be helpful to know if you've received end-of-call reports for other call termination reasons without any issues.

Yes, I received th report for other call termiantion issues.

@Madame Great, it's helpful to know that you're receiving reports for other call termination issues. It seems like there might be a specific problem with the handling of the "customer-busy" event. To troubleshoot this further, I would recommend checking the following: 1. Verify that the "customer-busy" event is indeed configured to trigger an end-of-call report in your system. 2. Check any logs or error messages that might indicate why the report isn't being generated or sent for this particular event. 3. Ensure that there are no filters or conditions in your report generation logic that might be excluding the "customer-busy" event. If everything seems to be configured correctly and you're still not receiving the report, it might be necessary to look into the service provider's documentation or contact their support to ensure that the "customer-busy" event is supposed to generate a report and that there are no known issues with it. If you need further assistance with this or if you'd like me to perform any specific checks or actions, please let me know!

The event is correctly setup on our side.

customer-busy and all the things are sent via status-update server url

Hi, I'm a dev in the same team. Just to add more details to this: Our assistant is configured to only send end-of-call-report events to the server url. Nonetheless it will send a status-update event in case of customer-busy which looks like a bug to me. Also shouldn't there be a end-of-call-report event for every call? For calls that were ended with reason "customer-did-not-answer" there will be an end-of-call-report event for instance. So that seems a bit inconsistent.

end-of-call-report contains data related to call like transcript, recordingURL and other necessary things but these things didn't happen because customer-did-not-answer. So, it is kinda logical not to send any end-of-call-report.

So you are telling me it's logical to send a status-update event to the server url when the assistant is explicitly configured to only send end-of-call-report events? And it's logical to send an end-of-call-report for customer-did-not-answer but not for customer-busy? In my opinion end-of-call-report should be sent for every call no matter if the customer picked up or not to allow consistent processing of calls.

Well, I will talk to my dev team about it but for now. All, I can tell you to use status-update server message