B2BUA Timeout: Feature Server BYE After 45 Minutes Despite timeLimit: 10800

Self Hosting
1

Hello everyone,

I am facing an issue with outbound VoIP calls dropping after 45 minutes, and I could use some architectural advice on how to resolve it.

Environment:

  • Hosting: Self-Hosted (Kubernetes)
  • Trunk / Carrier: Plivo
  • Call Direction: Outbound (Jambonz → Plivo)

The Issue:
When I initiate a call using the dial verb, the media and signaling work perfectly for over 45 minutes. However, shortly after the 45-minute mark, the call automatically disconnects.

Troubleshooting Performed:

  1. PCAP Analysis: I pulled the PCAP traces and verified that the BYE event is originating directly from the Jambonz Feature Server after 45 minutes, not from Plivo or the end-user.
  2. Application Timers: To rule out standard application limits, I explicitly added "timeLimit": 10800 (3 hours) to my dial verb payload. However, the Feature Server still sends the BYE after 45 minutes, effectively ignoring the 3-hour limit.
  3. Session Timers: This appears to be a strict SIP Session Timer (RFC 4028) enforcement on the FreeSWITCH/Feature Server Leg B side, where it starves after missing a few refresh cycles and eventually tears down the call.

My Question:
How can I properly configure the Feature Server or the SBC to either refresh the session timer internally or bypass this mod_sofia limit so that my calls can respect the timeLimit parameter and last for 1 to 3 hours?

Any guidance on the proper B2BUA configuration for this would be greatly appreciated!

2

What jambonz version are you running?