VoIP Mailing List Archives
Mailing list archives for the VoIP community |
|
View previous topic :: View next topic |
Author |
Message |
davidswalkabout at gma... Guest
|
Posted: Wed Mar 03, 2021 10:20 pm Post subject: [Freeswitch-users] rtp-timeout-sec VS media_timeout |
|
|
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@lists.freeswitch.org (freeswitch-users-request@lists.freeswitch.org)> wrote:
Quote: |
---------- Forwarded message ----------
From: Allan Kristensen <ak@hejdu.dk (ak@hejdu.dk)>
To: FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org (freeswitch-users@lists.freeswitch.org)>
Cc:
Bcc:
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"/>
Working:
<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?
/Allan
Using:
FreeSWITCH Version 1.10.5-release+git~20200818T185121Z~25569c1631~64bit
|
|
|
Back to top |
|
|
dragos at freeswitch.org Guest
|
Posted: Thu Mar 04, 2021 4:32 am Post subject: [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@gmail.com (davidswalkabout@gmail.com)> wrote:
Quote: | 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@lists.freeswitch.org (freeswitch-users-request@lists.freeswitch.org)> wrote:
Quote: |
---------- Forwarded message ----------
From: Allan Kristensen <ak@hejdu.dk (ak@hejdu.dk)>
To: FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org (freeswitch-users@lists.freeswitch.org)>
Cc:
Bcc:
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"/>
Working:
<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?
/Allan
Using:
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@freeswitch.com (sales@freeswitch.com)
https://freeswitch.com
Official FreeSWITCH Sites
https://freeswitch.com/oss
https://freeswitch.org/confluence
https://cluecon.com
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org (FreeSWITCH-users@lists.freeswitch.org)
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
https://freeswitch.com |
|
|
Back to top |
|
|
botelist at gmail.com Guest
|
Posted: Thu Mar 04, 2021 9:14 am Post subject: [Freeswitch-users] rtp-timeout-sec VS media_timeout |
|
|
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@lists.freeswitch.org> On Behalf Of Dragos Oancea
Sent: Thursday, 4 March, 2021 04:04
To: FreeSWITCH Users Help <freeswitch-users@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@gmail.com (davidswalkabout@gmail.com)> wrote:
Quote: |
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@lists.freeswitch.org (freeswitch-users-request@lists.freeswitch.org)> wrote:
Quote: |
---------- Forwarded message ----------
From: Allan Kristensen <ak@hejdu.dk (ak@hejdu.dk)>
To: FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org (freeswitch-users@lists.freeswitch.org)>
Cc:
Bcc:
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"/>
Working:
<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?
/Allan
Using:
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@freeswitch.com (sales@freeswitch.com)
https://freeswitch.com
Official FreeSWITCH Sites
https://freeswitch.com/oss
https://freeswitch.org/confluence
https://cluecon.com
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org (FreeSWITCH-users@lists.freeswitch.org)
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
https://freeswitch.com |
|
|
Back to top |
|
|
davidswalkabout at gma... Guest
|
Posted: Thu Mar 04, 2021 10:36 pm Post subject: [Freeswitch-users] rtp-timeout-sec VS media_timeout |
|
|
We're using FS 10.5 on Debian Stretch installed via packages.
<param name="rtp-timeout-sec" value="300"/> in our sip_profiles/internal.xml does effect calls. We have no media_timeout* config. |
|
Back to top |
|
|
brian at freeswitch.com Guest
|
|
Back to top |
|
|
davidswalkabout at gma... Guest
|
Posted: Fri Mar 12, 2021 10:38 pm Post subject: [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.
---------- Forwarded message ----------
From: Dragos Oancea <dragos@freeswitch.org (dragos@freeswitch.org)>
To: FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org (freeswitch-users@lists.freeswitch.org)>
Cc:
Bcc:
Date: Thu, 4 Mar 2021 11:04:26 +0200
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"/> |
|
Back to top |
|
|
davidswalkabout at gma... Guest
|
Posted: Mon Mar 15, 2021 5:38 pm Post subject: [Freeswitch-users] rtp-timeout-sec VS media_timeout |
|
|
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 (freeswitch-users-request@lists.freeswitch.org)> wrote:
Quote: |
---------- Forwarded message ----------
From: David P <davidswalkabout@gmail.com (davidswalkabout@gmail.com)>
To: FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org (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.
|
|
|
Back to top |
|
|
brian at freeswitch.com Guest
|
|
Back to top |
|
|
davidswalkabout at gma... Guest
|
Posted: Fri Mar 19, 2021 2:21 am Post subject: [Freeswitch-users] rtp-timeout-sec VS media_timeout |
|
|
Yes, we want to hangup if media_timeout expires on leg b of the conference. This seems to work but seemingly only after reboot, not the 'elegant' restart I tried initially.
Btw, still eager for any news on 'unified-plan' support.
Quote: | ---------- Forwarded message ----------
From: Brian West <brian@freeswitch.com (brian@freeswitch.com)>
To: FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org (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 (davidswalkabout@gmail.com)> wrote:
Quote: | 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 (freeswitch-users-request@lists.freeswitch.org)> wrote:
Quote: |
---------- Forwarded message ----------
From: David P <davidswalkabout@gmail.com (davidswalkabout@gmail.com)>
To: FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org (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.
|
|
|
|
|
Back to top |
|
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|