---------- Forwarded message ----------

From: Brian West <brian@freeswitch.com>
To: FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org>
Cc: 
Bcc: 
Date: Wed, 17 Mar 2021 22:46:54 -0500
Subject: Re: [Freeswitch-users] rtp-timeout-sec VS media_timeout

Are you trying to hang the call up?

On Mon, Mar 15, 2021 at 5:45 PM David P <davidswalkabout@gmail.com> wrote:

Although I didn't see that adding...

  media_timeout=300000  

...to our conference settings have any effect after restarting FS10.5 this way...

  fs_cli -x 'fsctl shutdown elegant restart'  

...I do see it having an effect now. I suspect there's been a reboot since then. FYI

On Sun, Mar 14, 2021 at 1:00 AM <freeswitch-users-request@lists.freeswitch.org> wrote:

---------- Forwarded message ----------
From: David P <davidswalkabout@gmail.com>
To: FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org>
Cc: 
Bcc: 
Date: Sat, 13 Mar 2021 16:15:55 +1300
Subject: Re: [Freeswitch-users] rtp-timeout-sec VS media_timeout

Using FS10.5 installed from packages on Debian Stretch...

I wanted to replicate the behavior we had with <param name="rtp-timeout-sec" value="300"/> so that we'll hangup calls in which leg B of a conference has sent no media for 5 mins.

I edited our dialplan like this...

<action application="conference_set_auto_outcall"
 data="['conference_member_flags=endconf,jitterbuffer_msec=5p:100p,media_timeout=300000']sofia/gateway/...deleted..."/>

and restarted like this...

fs_cli -x 'fsctl shutdown elegant restart'

But after 8 mins in such a call there was no hangup.