Hi! I'm experiencing an issue where outbound calls through my provider (Anura Argentina) drop exactly at 5 minutes. My provider confirmed they send a re-INVITE (RFC 4028) every 5 minutes, but Retell's server is responding with 404 Not Here. This seems to be a signaling issue in the SBC/Kamailio layer. Could someone from the engineering team help me check the logs for my account? I've already sent an email with my account details.

Hi @Lovitsy

lucasbozzolo@gmail.com

Ok I send this to team

Hello @Lovitsy , can you share the call ids of these calls, because i can see you have calls that is past 5 mins. https://cdn.discordapp.com/attachments/1470398678073344094/1470420798106898554/image.png?ex=698b3b95&is=6989ea15&hm=6b0b9ffc73eb7a1ec3a601fc867ebc8b9dfeb17e993042b10f8e93935b5f6ab9&

You are correct, it's not happening in 100% of the calls, but it is happening very frequently. Here is a specific Call ID where the call dropped exactly at the 5-minute mark due to the 404 response to the re-INVITE: call_03ef782038d7a1e048fde53fc1e My provider (Anura) confirmed that in this specific call, their system interpreted the 404/486 response as if the session no longer existed on Retell's side. It seems like the dialogue state is being lost or not recognized in some instances.

Can you send me the pcap file .

I checked with my carrier (Anura) and they cannot disable the Session Timers because it's a global configuration for their entire network infrastructure, following the RFC 4028 standard. Since the re-INVITE is a standard SIP practice to keep sessions alive, why is Retell’s SBC responding with a 404 Not Here to an active dialogue? This suggests that the session state is not being maintained correctly in your Kamailio/SBC layer when the re-INVITE arrives. Could the engineering team look into why the active Call-ID is being rejected instead of refreshed? Disabling it on the carrier side is not an option for us.

let me check with our telephony team about this.