[Freeswitch-users] MEDIA_TIMEOUT after long duration call

Wed Apr 14 01:00:33 PDT 2010

Ok, I see http://svn.freeswitch.org/svn/freeswitch/tags/1.0.rc6
I thought it is a release candidate, isn't it? Is it safe to use it in production?

BTW MEDIA_TIMEOUT didn't occur since 16 hours, so I think the failure was a defective contact..

Date: Tue, 13 Apr 2010 12:19:10 -0500
From: anthony.minessale at gmail.com
To: freeswitch-users at lists.freeswitch.org
Subject: Re: [Freeswitch-users] MEDIA_TIMEOUT after long duration call

The last stable release is actually 1.0.6

On Tue, Apr 13, 2010 at 12:03 PM, Francisco Scaramanga <scaram at hotmail.de> wrote:

I am running the last stable release 1.0.4 and could reproduce the failure. Sometimes it happens in a call of 4 minutes duration.

I don't have a rtp packet trace but there is one more reason for MEDIA_TIMEOUT. I had a look at the sourcecode and followed the calls down to the winsock function recvfrom. It also could be a socket error.  If the recvfrom function returns -2 a MEDIA_TIMEOUT will happen. Maybe something was wrong with the network hardware cables, switch ..

I changed my hardware. Test is running...

How can I enable a rtp packet trace? It think I should check this too.

> Date: Tue, 13 Apr 2010 16:23:44 +0100
> From: steveayre at gmail.com

> To: freeswitch-users at lists.freeswitch.org
> Subject: Re: [Freeswitch-users] MEDIA_TIMEOUT after long duration call

> 
> Which version of FS are you running? From the line numbers it isn't
> the latest, so you might try updating and see if you can still
> reproduce.
> 
> Given that the hangup appears to happen on mod_sofia.c:744, there is a

> MEDIA_TIMEOUT near that line which is triggered if FS times out trying
> to read a video frame from RTP. That will occur when the RTP stack
> thinks it has missed too many RTP packets.
> 
> Do you have an RTP packet trace for the call?

> 
> -Steve
> 
> 
> 
> On 13 April 2010 14:53, Francisco Scaramanga <scaram at hotmail.de> wrote:
> > hi , I have a problem with long duration calls. After 11 hours and 35

> > minutes the call ends because of MEDIA_TIMEOUT. It seems to be
> > reproduceable.
> > Any idea? I use SIP phone SIEMENS Gigaset S685.
> >
> > 2010-04-12 19:00:51.421875 [DEBUG] sofia.c:3289 Channel

> > sofia/internal/1010 at 192.168.1.234 entering state [completed][200]
> > 2010-04-12 19:00:51.421875 [DEBUG] switch_core_session.c:630 Send signal

> > sofia/internal/1010 at 192.168.1.234 [BREAK]
> > 2010-04-12 19:00:51.421875 [NOTICE] mod_dptools.c:649 Channel
> > [sofia/internal/1010 at 192.168.1.234] has been answered

> > 2010-04-12 19:00:51.421875 [DEBUG] switch_channel.c:182
> > sofia/internal/1010 at 192.168.1.234 receive message [AUDIO_SYNC]
> > EXECUTE sofia/internal/1010 at 192.168.1.234 MyModul

> > 2010-04-12 19:00:51.640625 [DEBUG] sofia.c:3289 Channel
> > sofia/internal/1010 at 192.168.1.234 entering state [ready][200]
> > 2010-04-13 06:35:53.406250 [NOTICE] mod_sofia.c:744 Hangup

> > sofia/internal/1010 at 192.168.1.234 [CS_EXECUTE] [MEDIA_TIMEOUT]
> > 2010-04-13 06:35:53.406250 [DEBUG] switch_channel.c:1683 Send signal
> > sofia/internal/1010 at 192.168.1.234 [KILL]

> > 2010-04-13 06:35:53.406250 [DEBUG] switch_core_session.c:932 Send signal
> > sofia/internal/1010 at 192.168.1.234 [BREAK]
> > 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:491

> > (sofia/internal/1010 at 192.168.1.234) State EXECUTE going to sleep
> > 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:398
> > (sofia/internal/1010 at 192.168.1.234) Running State Change CS_HANGUP

> > 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:434
> > (sofia/internal/1010 at 192.168.1.234) State HANGUP
> > 2010-04-13 06:35:53.406250 [DEBUG] mod_sofia.c:338 Channel

> > sofia/internal/1010 at 192.168.1.234 hanging up, cause: MEDIA_TIMEOUT
> > 2010-04-13 06:35:53.406250 [DEBUG] mod_sofia.c:396 Sending BYE to
> > sofia/internal/1010 at 192.168.1.234

> > 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:46
> > sofia/internal/1010 at 192.168.1.234 Standard HANGUP, cause: MEDIA_TIMEOUT
> > 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:434

> > (sofia/internal/1010 at 192.168.1.234) State HANGUP going to sleep
> > 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:476
> > (sofia/internal/1010 at 192.168.1.234) State Change CS_HANGUP -> CS_REPORTING

> > 2010-04-13 06:35:53.406250 [DEBUG] switch_core_session.c:932 Send signal
> > sofia/internal/1010 at 192.168.1.234 [BREAK]
> > 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:398

> > (sofia/internal/1010 at 192.168.1.234) Running State Change CS_REPORTING
> > 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:612
> > (sofia/internal/1010 at 192.168.1.234) State REPORTING

> > 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:53
> > sofia/internal/1010 at 192.168.1.234 Standard REPORTING, cause: MEDIA_TIMEOUT

> > 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:612
> > (sofia/internal/1010 at 192.168.1.234) State REPORTING going to sleep
> > 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:411

> > (sofia/internal/1010 at 192.168.1.234) State Change CS_REPORTING -> CS_DESTROY
> > 2010-04-13 06:35:53.406250 [DEBUG] switch_core_session.c:1068 Session 3

> > (sofia/internal/1010 at 192.168.1.234) Locked, Waiting on external entities
> > 2010-04-13 06:35:53.406250 [NOTICE] switch_core_session.c:1086 Session 3

> > (sofia/internal/1010 at 192.168.1.234) Ended
> > 2010-04-13 06:35:53.406250 [NOTICE] switch_core_session.c:1088 Close Channel
> > sofia/internal/1010 at 192.168.1.234 [CS_DESTROY]

> > 2010-04-13 06:35:53.406250 [DEBUG] switch_core_codec.c:122 Restore original
> > codec.
> > 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:564
> > (sofia/internal/1010 at 192.168.1.234) State DESTROY

> > 2010-04-13 06:35:53.406250 [DEBUG] mod_sofia.c:255
> > sofia/internal/1010 at 192.168.1.234 SOFIA DESTROY
> > 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:60

> > sofia/internal/1010 at 192.168.1.234 Standard DESTROY
> > 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:564
> > (sofia/internal/1010 at 192.168.1.234) State DESTROY going to sleep

> >
> > ________________________________
> > Ihre Daten brauchen Platz? SkyDrive gibt Ihnen 25 GB - gratis!
> > _______________________________________________
> > FreeSWITCH-users mailing list

> > FreeSWITCH-users at lists.freeswitch.org
> > http://lists.freeswitch.org/mailman/listinfo/freeswitch-users

> > UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> > http://www.freeswitch.org

> >
> >
> 
> _______________________________________________
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org

> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users

> http://www.freeswitch.org

Ihre Daten brauchen Platz?  SkyDrive gibt Ihnen 25 GB - gratis!

_______________________________________________

FreeSWITCH-users mailing list

FreeSWITCH-users at lists.freeswitch.org

http://lists.freeswitch.org/mailman/listinfo/freeswitch-users

UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users

http://www.freeswitch.org

-- 
Anthony Minessale II

FreeSWITCH http://www.freeswitch.org/
ClueCon http://www.cluecon.com/

Twitter: http://twitter.com/FreeSWITCH_wire

AIM: anthm
MSN:anthony_minessale at hotmail.com
GTALK/JABBER/PAYPAL:anthony.minessale at gmail.com

IRC: irc.freenode.net #freeswitch

FreeSWITCH Developer Conference
sip:888 at conference.freeswitch.org
googletalk:conf+888 at conference.freeswitch.org

pstn:+19193869900

_________________________________________________________________
http://redirect.gimas.net/?n=M1004xNoSpam2
Angst vor Spam? Hotmail schützt Sie mit modernster Technologie!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20100414/4e656f3e/attachment-0001.html 