it's not 100% accurate in the media timeout.<div>It would be too expensive to use actual timers, it uses the number of samples you should be getting from rtp</div><div>and a number of loops where no media was received.</div>
<div><br></div><div>Migrating from svn 13000 range to GIT is a big step and you may have to adjust to some new behaviors.</div><div>media_timeout may not even have existed that long ago I don't recall.</div><div><br></div>
<div>If you don't need media timeouts turn off the param or turn it up to longer.</div><div><br></div><div><br><div class="gmail_quote">On Tue, Jun 29, 2010 at 1:09 PM, Michael Collins <span dir="ltr"><<a href="mailto:msc@freeswitch.org">msc@freeswitch.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Pastebin your dialplan and the lua script for starters. Also, is it the 5300 that is responding with the media timeout?<br>
-MC<br><br><div class="gmail_quote"><div><div></div><div class="h5">On Tue, Jun 29, 2010 at 10:15 AM, Dan <span dir="ltr"><<a href="mailto:freeswitch-users@digitaldan.com" target="_blank">freeswitch-users@digitaldan.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex"><div><div></div><div class="h5"><div><div style="font-family:Times New Roman;font-size:12pt;color:rgb(0, 0, 0)">
Hi guys, I have been running two freeswitch boxes (13754M) that answer calls from a cisco 5300 (both on the same network) and records them to disk with a small lua application. This has been working well for the past few months. I decided to upgrade one of them to trunk ( git-3fbd9e2 2010-06-11 11-08-51 -0500 ) and have run into a problem. Some calls will fail with a MEDIA_TIMEOUT after a few minutes, the time it takes to fail ranges from 4 minutes to 10 minutes, I don't have a full sip trace or pcap dump yet, I reverted back to the old freeswitch version (on the same hardware) and have not been able to reproduce it in a test environment yet ( I continue to try). Below are the relevant lines from the log files for one of the calls:<br>
<br>2010-06-23 07:42:19.033466 [DEBUG] switch_channel.c:2257 (sofia/external/<a href="mailto:nobody@192.168.21.4" target="_blank">nobody@192.168.21.4</a>) Callstate Change ACTIVE -> HANGUP<br>2010-06-23 07:42:19.033466 [NOTICE] mod_sofia.c:884 Hangup sofia/external/<a href="mailto:nobody@192.168.21.4" target="_blank">nobody@192.168.21.4</a> [CS_EXECUTE] [MEDIA_TIMEOUT]<br>
2010-06-23 07:42:19.033466 [DEBUG] switch_channel.c:2273 Send signal sofia/external/<a href="mailto:nobody@192.168.21.4" target="_blank">nobody@192.168.21.4</a> [KILL]<br>2010-06-23 07:42:19.033466 [DEBUG] switch_core_session.c:1023 Send signal sofia/external/<a href="mailto:nobody@192.168.21.4" target="_blank">nobody@192.168.21.4</a> [BREAK]<br>
2010-06-23 07:42:19.033466 [DEBUG] switch_core_codec.c:146 sofia/external/<a href="mailto:nobody@192.168.21.4" target="_blank">nobody@192.168.21.4</a> Restore previous codec PCMU:0.<br><br>My configuration is bone stock, so the rtp timeout value is at 300, but I have some calls that have lasted only 4 minutes. One other piece of information is that on one of the recordings that was hung up after 4 minutes and 17 seconds the recorded file was only 24 seconds long (it stopped recording after the first 24 seconds) , so I'm assuming freeswitch did not think there were any rtp packets to record. <br>
<br>Any ideas on where to start debugging this? I have setup a new freeswitch box connected to the same 5300 to reproduce, but have not been able to generate the call volume ( there where around 30 calls being recorded) yet, but I'm working on it.<br>
<br>Thanks!<br></div></div><br></div></div>_______________________________________________<br>
FreeSWITCH-users mailing list<br>
<a href="mailto:FreeSWITCH-users@lists.freeswitch.org" target="_blank">FreeSWITCH-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
<br></blockquote></div><br>
<br>_______________________________________________<br>
FreeSWITCH-users mailing list<br>
<a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Anthony Minessale II<br><br>FreeSWITCH <a href="http://www.freeswitch.org/">http://www.freeswitch.org/</a><br>ClueCon <a href="http://www.cluecon.com/">http://www.cluecon.com/</a><br>
Twitter: <a href="http://twitter.com/FreeSWITCH_wire">http://twitter.com/FreeSWITCH_wire</a><br><br>AIM: anthm<br><a href="mailto:MSN%3Aanthony_minessale@hotmail.com">MSN:anthony_minessale@hotmail.com</a><br>GTALK/JABBER/<a href="mailto:PAYPAL%3Aanthony.minessale@gmail.com">PAYPAL:anthony.minessale@gmail.com</a><br>
IRC: <a href="http://irc.freenode.net">irc.freenode.net</a> #freeswitch<br><br>FreeSWITCH Developer Conference<br><a href="mailto:sip%3A888@conference.freeswitch.org">sip:888@conference.freeswitch.org</a><br><a href="mailto:googletalk%3Aconf%2B888@conference.freeswitch.org">googletalk:conf+888@conference.freeswitch.org</a><br>
pstn:+19193869900<br>
</div>