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

**URL:** <https://community.jambonz.org/t/b2bua-timeout-feature-server-bye-after-45-minutes-despite-timelimit-10800/30>\
**Category:** Self Hosting\
**Tags:** k8s\
**Created:** [June 4, 2026, 9:02am UTC](https://community.jambonz.org/t/b2bua-timeout-feature-server-bye-after-45-minutes-despite-timelimit-10800/30 "2026-06-04T09:02:06Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![bhavik](https://avatars.discourse-cdn.com/v4/letter/b/ecc23a/32.png) [@bhavik](https://community.jambonz.org/u/bhavik)\
**Post date:** [June 4, 2026, 9:02am UTC](https://community.jambonz.org/t/b2bua-timeout-feature-server-bye-after-45-minutes-despite-timelimit-10800/30/1 "2026-06-04T09:02:06Z")

</div>

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!

---

<div class="post-metadata">

**Author:** ![daveh](https://avatars.discourse-cdn.com/v4/letter/d/85e7bf/32.png) [@daveh](https://community.jambonz.org/u/daveh)\
**Post date:** [June 9, 2026, 8:37pm UTC](https://community.jambonz.org/t/b2bua-timeout-feature-server-bye-after-45-minutes-despite-timelimit-10800/30/2 "2026-06-09T20:37:50Z")

</div>

What jambonz version are you running?