[Freeswitch-users] rtp-timeout-sec VS media_timeout

Bote Man botelist at gmail.com
Thu Mar 4 13:41:31 UTC 2021

I recall that the rtp_* variable names were changed to media_* some time ago. I updated the wiki to reflect this.


Now the question is: what version of code exhibited this behavior? 


If it was built before the change, then naturally the rtp_* series will be what it uses.




John Boteler 

BnC Group U.S.A. 




From: FreeSWITCH-users <freeswitch-users-bounces at lists.freeswitch.org> On Behalf Of Dragos Oancea
Sent: Thursday, 4 March, 2021 04:04
To: FreeSWITCH Users Help <freeswitch-users at lists.freeswitch.org>
Subject: Re: [Freeswitch-users] rtp-timeout-sec VS media_timeout


For media timeout there are the following chan vars:

media_timeout, media_hold_timeout, media_timeout, media_hold_timeout_video, media_hold_timeout_audio, media_timeout_audio .


They are in milliseconds, not seconds like rtp-timeout-sec . 


<param name="media_timeout" value="300000"/>


On Thu, Mar 4, 2021 at 4:47 AM David P <davidswalkabout at gmail.com <mailto:davidswalkabout at gmail.com> > wrote:

Hi Allan,


I don't know if the media_timeout=300 behavior you saw is a bug or not, but I wanted to add my own observation of weirdness about hangup cause MEDIA_TIMEOUT...


I just noticed a conference end abruptly after one leg spoke for 5 minutes. The logs aren't clear why this happened, but it seems that <param name="rtp-timeout-sec" value="300"/> in our sip_profiles/internal.xml is the reason -- it seems that because the *other* leg of the conference remained silent, the RTP timeout was reached.


I couldn't find any confluence pages about MEDIA_TIMEOUT by googling.


On Fri, Jan 8, 2021 at 1:08 AM <freeswitch-users-request at lists.freeswitch.org <mailto:freeswitch-users-request at lists.freeswitch.org> > wrote:

---------- Forwarded message ----------
From: Allan Kristensen <ak at hejdu.dk <mailto:ak at hejdu.dk> >
To: FreeSWITCH Users Help <freeswitch-users at lists.freeswitch.org <mailto:freeswitch-users at lists.freeswitch.org> >
Date: Wed, 6 Jan 2021 19:37:33 +0100
Subject: [Freeswitch-users] rtp-timeout-sec VS media_timeout

We had some problems with "hanging channels" for our webrtc clients (via kamailio).

To solve the problem I tried to use "media_timeout" setting but it didn't really work. So I tried the deprecated "rtp-timeout-sec" and this actually works fine?


Not working:

<param name="media_timeout" value="300"/>



<param name="rtp-timeout-sec" value="300"/>


How to reproduce: Make a call using webrtc and just close browser window, after some time freeswitch should close the channel because of missing rtp.

Instead it just keeps writing: "switch_rtp.c:853 No audio stun for a long time!" forever...


Anyway, it works now....just curious why...a typo or bug?





FreeSWITCH Version 1.10.5-release+git~20200818T185121Z~25569c1631~64bit


The FreeSWITCH project is sponsored by SignalWire https://signalwire.com
Enhance your FreeSWITCH install with disruptive priced SMS and PSTN services.
Build your next product on our scalable cloud platform.

Join our online community to chat in real time https://signalwire.community

Professional FreeSWITCH Services
sales at freeswitch.com <mailto:sales at freeswitch.com> 

Official FreeSWITCH Sites

FreeSWITCH-users mailing list
FreeSWITCH-users at lists.freeswitch.org <mailto:FreeSWITCH-users at lists.freeswitch.org> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20210304/fe8281ac/attachment.html>

More information about the FreeSWITCH-users mailing list