We’ve encountered an issue where a client reported that some of our calls did not transfer, even though the end reason indicates they were successfully forwarded. This problem has been observed in the following calls: - 6df29494-7903-49f4-8ca1-8089e240d567 - babb5e01-4b8a-453a-b3b8-df549c4b9a4b - 7c15037b-8e6a-4c2b-bce5-3b5c82847362 - c81d79bc-20f8-4ee1-a76f-316eb6b44355 Could you please investigate this issue and provide any insights or resolutions?

@Vramir Certainly! I will start by checking the logs for the calls you've mentioned to see if there are any error messages or issues that could explain why the calls were not transferred successfully. I'll also verify if your Vici system is configured to handle SIP REFER messages, as this could be relevant for call transfers. While I do this, could you please confirm if there have been any recent changes to your system or network that might affect call transfers? Additionally, if you could check if the

forwardingPhoneNumber

attribute in your API calls was set correctly or if you've tried omitting it or setting it to null or an empty string, that would be helpful information. I'll proceed with the log investigation now and get back to you with my findings as soon as possible.

We have calls that have succesfully forwarded, so this is an issue that occurs sometimes

Got it. Tagging @User for additional help.