MEDIA_TIMEOUT after long duration call
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@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@192.168.1.234 [BREAK] 2010-04-12 19:00:51.421875 [NOTICE] mod_dptools.c:649 Channel [sofia/internal/1010@192.168.1.234] has been answered 2010-04-12 19:00:51.421875 [DEBUG] switch_channel.c:182 sofia/internal/1010@192.168.1.234 receive message [AUDIO_SYNC] EXECUTE sofia/internal/1010@192.168.1.234 MyModul 2010-04-12 19:00:51.640625 [DEBUG] sofia.c:3289 Channel sofia/internal/1010@192.168.1.234 entering state [ready][200] 2010-04-13 06:35:53.406250 [NOTICE] mod_sofia.c:744 Hangup sofia/internal/1010@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@192.168.1.234 [KILL] 2010-04-13 06:35:53.406250 [DEBUG] switch_core_session.c:932 Send signal sofia/internal/1010@192.168.1.234 [BREAK] 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:491 (sofia/internal/1010@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@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@192.168.1.234) State HANGUP 2010-04-13 06:35:53.406250 [DEBUG] mod_sofia.c:338 Channel sofia/internal/1010@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@192.168.1.234 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:46 sofia/internal/1010@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@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@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@192.168.1.234 [BREAK] 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:398 (sofia/internal/1010@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@192.168.1.234) State REPORTING 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:53 sofia/internal/1010@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@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@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@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@192.168.1.234) Ended 2010-04-13 06:35:53.406250 [NOTICE] switch_core_session.c:1088 Close Channel sofia/internal/1010@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@192.168.1.234) State DESTROY 2010-04-13 06:35:53.406250 [DEBUG] mod_sofia.c:255 sofia/internal/1010@192.168.1.234 SOFIA DESTROY 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:60 sofia/internal/1010@192.168.1.234 Standard DESTROY 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:564 (sofia/internal/1010@192.168.1.234) State DESTROY going to sleep _________________________________________________________________ http://redirect.gimas.net/?n=M1004xSkyDrive2 Ihre Daten brauchen Platz? SkyDrive gibt Ihnen 25 GB - gratis!
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@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@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@192.168.1.234 [BREAK] 2010-04-12 19:00:51.421875 [NOTICE] mod_dptools.c:649 Channel [sofia/internal/1010@192.168.1.234] has been answered 2010-04-12 19:00:51.421875 [DEBUG] switch_channel.c:182 sofia/internal/1010@192.168.1.234 receive message [AUDIO_SYNC] EXECUTE sofia/internal/1010@192.168.1.234 MyModul 2010-04-12 19:00:51.640625 [DEBUG] sofia.c:3289 Channel sofia/internal/1010@192.168.1.234 entering state [ready][200] 2010-04-13 06:35:53.406250 [NOTICE] mod_sofia.c:744 Hangup sofia/internal/1010@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@192.168.1.234 [KILL] 2010-04-13 06:35:53.406250 [DEBUG] switch_core_session.c:932 Send signal sofia/internal/1010@192.168.1.234 [BREAK] 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:491 (sofia/internal/1010@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@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@192.168.1.234) State HANGUP 2010-04-13 06:35:53.406250 [DEBUG] mod_sofia.c:338 Channel sofia/internal/1010@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@192.168.1.234 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:46 sofia/internal/1010@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@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@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@192.168.1.234 [BREAK] 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:398 (sofia/internal/1010@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@192.168.1.234) State REPORTING 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:53 sofia/internal/1010@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@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@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@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@192.168.1.234) Ended 2010-04-13 06:35:53.406250 [NOTICE] switch_core_session.c:1088 Close Channel sofia/internal/1010@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@192.168.1.234) State DESTROY 2010-04-13 06:35:53.406250 [DEBUG] mod_sofia.c:255 sofia/internal/1010@192.168.1.234 SOFIA DESTROY 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:60 sofia/internal/1010@192.168.1.234 Standard DESTROY 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:564 (sofia/internal/1010@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@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
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@gmail.com To: freeswitch-users@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@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@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@192.168.1.234 [BREAK] 2010-04-12 19:00:51.421875 [NOTICE] mod_dptools.c:649 Channel [sofia/internal/1010@192.168.1.234] has been answered 2010-04-12 19:00:51.421875 [DEBUG] switch_channel.c:182 sofia/internal/1010@192.168.1.234 receive message [AUDIO_SYNC] EXECUTE sofia/internal/1010@192.168.1.234 MyModul 2010-04-12 19:00:51.640625 [DEBUG] sofia.c:3289 Channel sofia/internal/1010@192.168.1.234 entering state [ready][200] 2010-04-13 06:35:53.406250 [NOTICE] mod_sofia.c:744 Hangup sofia/internal/1010@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@192.168.1.234 [KILL] 2010-04-13 06:35:53.406250 [DEBUG] switch_core_session.c:932 Send signal sofia/internal/1010@192.168.1.234 [BREAK] 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:491 (sofia/internal/1010@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@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@192.168.1.234) State HANGUP 2010-04-13 06:35:53.406250 [DEBUG] mod_sofia.c:338 Channel sofia/internal/1010@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@192.168.1.234 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:46 sofia/internal/1010@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@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@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@192.168.1.234 [BREAK] 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:398 (sofia/internal/1010@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@192.168.1.234) State REPORTING 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:53 sofia/internal/1010@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@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@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@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@192.168.1.234) Ended 2010-04-13 06:35:53.406250 [NOTICE] switch_core_session.c:1088 Close Channel sofia/internal/1010@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@192.168.1.234) State DESTROY 2010-04-13 06:35:53.406250 [DEBUG] mod_sofia.c:255 sofia/internal/1010@192.168.1.234 SOFIA DESTROY 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:60 sofia/internal/1010@192.168.1.234 Standard DESTROY 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:564 (sofia/internal/1010@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@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@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_________________________________________________________________ http://redirect.gimas.net/?n=M1004xSkyDrive2 Ihre Daten brauchen Platz? SkyDrive gibt Ihnen 25 GB - gratis!
The last stable release is actually 1.0.6 On Tue, Apr 13, 2010 at 12:03 PM, Francisco Scaramanga <scaram@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@gmail.com To: freeswitch-users@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@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@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@192.168.1.234 [BREAK] 2010-04-12 19:00:51.421875 [NOTICE] mod_dptools.c:649 Channel [sofia/internal/1010@192.168.1.234] has been answered 2010-04-12 19:00:51.421875 [DEBUG] switch_channel.c:182 sofia/internal/1010@192.168.1.234 receive message [AUDIO_SYNC] EXECUTE sofia/internal/1010@192.168.1.234 MyModul 2010-04-12 19:00:51.640625 [DEBUG] sofia.c:3289 Channel sofia/internal/1010@192.168.1.234 entering state [ready][200] 2010-04-13 06:35:53.406250 [NOTICE] mod_sofia.c:744 Hangup sofia/internal/1010@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@192.168.1.234 [KILL] 2010-04-13 06:35:53.406250 [DEBUG] switch_core_session.c:932 Send signal sofia/internal/1010@192.168.1.234 [BREAK] 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:491 (sofia/internal/1010@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@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@192.168.1.234) State HANGUP 2010-04-13 06:35:53.406250 [DEBUG] mod_sofia.c:338 Channel sofia/internal/1010@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@192.168.1.234 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:46 sofia/internal/1010@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@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@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@192.168.1.234 [BREAK] 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:398 (sofia/internal/1010@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@192.168.1.234) State REPORTING 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:53 sofia/internal/1010@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@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@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@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@192.168.1.234) Ended 2010-04-13 06:35:53.406250 [NOTICE] switch_core_session.c:1088 Close Channel sofia/internal/1010@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@192.168.1.234) State DESTROY 2010-04-13 06:35:53.406250 [DEBUG] mod_sofia.c:255 sofia/internal/1010@192.168.1.234 SOFIA DESTROY 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:60 sofia/internal/1010@192.168.1.234 Standard DESTROY 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:564 (sofia/internal/1010@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@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@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!<http://redirect.gimas.net/?n=M1004SkyDrive>
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@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@hotmail.com <MSN%3Aanthony_minessale@hotmail.com> GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com<PAYPAL%3Aanthony.minessale@gmail.com> IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org <sip%3A888@conference.freeswitch.org> googletalk:conf+888@conference.freeswitch.org<googletalk%3Aconf%2B888@conference.freeswitch.org> pstn:+19193869900
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@gmail.com To: freeswitch-users@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@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@gmail.com
To: freeswitch-users@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@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@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@192.168.1.234 [BREAK] 2010-04-12 19:00:51.421875 [NOTICE] mod_dptools.c:649 Channel [sofia/internal/1010@192.168.1.234] has been answered
2010-04-12 19:00:51.421875 [DEBUG] switch_channel.c:182 sofia/internal/1010@192.168.1.234 receive message [AUDIO_SYNC] EXECUTE sofia/internal/1010@192.168.1.234 MyModul
2010-04-12 19:00:51.640625 [DEBUG] sofia.c:3289 Channel sofia/internal/1010@192.168.1.234 entering state [ready][200] 2010-04-13 06:35:53.406250 [NOTICE] mod_sofia.c:744 Hangup
sofia/internal/1010@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@192.168.1.234 [KILL]
2010-04-13 06:35:53.406250 [DEBUG] switch_core_session.c:932 Send signal sofia/internal/1010@192.168.1.234 [BREAK] 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:491
(sofia/internal/1010@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@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@192.168.1.234) State HANGUP 2010-04-13 06:35:53.406250 [DEBUG] mod_sofia.c:338 Channel
sofia/internal/1010@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@192.168.1.234
2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:46 sofia/internal/1010@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@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@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@192.168.1.234 [BREAK] 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:398
(sofia/internal/1010@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@192.168.1.234) State REPORTING
2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:53 sofia/internal/1010@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@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@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@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@192.168.1.234) Ended 2010-04-13 06:35:53.406250 [NOTICE] switch_core_session.c:1088 Close Channel sofia/internal/1010@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@192.168.1.234) State DESTROY
2010-04-13 06:35:53.406250 [DEBUG] mod_sofia.c:255 sofia/internal/1010@192.168.1.234 SOFIA DESTROY 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:60
sofia/internal/1010@192.168.1.234 Standard DESTROY 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:564 (sofia/internal/1010@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@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@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
Ihre Daten brauchen Platz? SkyDrive gibt Ihnen 25 GB - gratis! _______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@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@hotmail.com GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org googletalk:conf+888@conference.freeswitch.org pstn:+19193869900 _________________________________________________________________ http://redirect.gimas.net/?n=M1004xNoSpam2 Angst vor Spam? Hotmail schützt Sie mit modernster Technologie!
We are no longer on SVN, we have now moved to GIT for the 1.0.6 release. http://wiki.freeswitch.org/wiki/Download_FreeSWITCH Note that the latest most stable version is always likely to be latest GIT version not the latest tagged released, as there will often be bugs present in the releases that are fixed in the latest GIT version. Tagged releases have more to do with the introduction of new features (such as G729 support in 1.0.6) than any guarantee of stability. -Steve On 14 April 2010 09:00, Francisco Scaramanga <scaram@hotmail.de> wrote:
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@gmail.com To: freeswitch-users@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@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@gmail.com To: freeswitch-users@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@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@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@192.168.1.234 [BREAK] 2010-04-12 19:00:51.421875 [NOTICE] mod_dptools.c:649 Channel [sofia/internal/1010@192.168.1.234] has been answered 2010-04-12 19:00:51.421875 [DEBUG] switch_channel.c:182 sofia/internal/1010@192.168.1.234 receive message [AUDIO_SYNC] EXECUTE sofia/internal/1010@192.168.1.234 MyModul 2010-04-12 19:00:51.640625 [DEBUG] sofia.c:3289 Channel sofia/internal/1010@192.168.1.234 entering state [ready][200] 2010-04-13 06:35:53.406250 [NOTICE] mod_sofia.c:744 Hangup sofia/internal/1010@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@192.168.1.234 [KILL] 2010-04-13 06:35:53.406250 [DEBUG] switch_core_session.c:932 Send signal sofia/internal/1010@192.168.1.234 [BREAK] 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:491 (sofia/internal/1010@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@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@192.168.1.234) State HANGUP 2010-04-13 06:35:53.406250 [DEBUG] mod_sofia.c:338 Channel sofia/internal/1010@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@192.168.1.234 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:46 sofia/internal/1010@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@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@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@192.168.1.234 [BREAK] 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:398 (sofia/internal/1010@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@192.168.1.234) State REPORTING 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:53 sofia/internal/1010@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@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@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@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@192.168.1.234) Ended 2010-04-13 06:35:53.406250 [NOTICE] switch_core_session.c:1088 Close Channel sofia/internal/1010@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@192.168.1.234) State DESTROY 2010-04-13 06:35:53.406250 [DEBUG] mod_sofia.c:255 sofia/internal/1010@192.168.1.234 SOFIA DESTROY 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:60 sofia/internal/1010@192.168.1.234 Standard DESTROY 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:564 (sofia/internal/1010@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@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@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@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@hotmail.com GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com IRC: irc.freenode.net #freeswitch
FreeSWITCH Developer Conference sip:888@conference.freeswitch.org googletalk:conf+888@conference.freeswitch.org pstn:+19193869900
________________________________ Angst vor Spam? Hotmail schützt Sie mit modernster Technologie! _______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
That being said, for a change things have been somewhat quiet after the 1.0.6 release. There have been some bug fixes that went in after, but not the usual frenzy of reports right after a release. Mike On Apr 14, 2010, at 7:23 AM, Steven Ayre wrote:
We are no longer on SVN, we have now moved to GIT for the 1.0.6 release.
http://wiki.freeswitch.org/wiki/Download_FreeSWITCH
Note that the latest most stable version is always likely to be latest GIT version not the latest tagged released, as there will often be bugs present in the releases that are fixed in the latest GIT version. Tagged releases have more to do with the introduction of new features (such as G729 support in 1.0.6) than any guarantee of stability.
-Steve
On 14 April 2010 09:00, Francisco Scaramanga <scaram@hotmail.de> wrote:
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?
Now I am using stable release 1.0.6 and have a MEDIA_TIMEOUT again, because function rtp_common_read counts missed packets. During a long session of several hours the amount of missed packets exceeds the limit. Now I changed my .\conf\sip_profiles\internal.xml and set the rtp timeout to 0, which means no timeout. set <param name="rtp-timeout-sec" value="0"/> My usecase is to have long duration calls. Can I do this without cross-effects, or is not wise to set rtp timout to 0?
From: mike@jerris.com Date: Wed, 14 Apr 2010 09:08:32 -0400 To: freeswitch-users@lists.freeswitch.org Subject: Re: [Freeswitch-users] MEDIA_TIMEOUT after long duration call
That being said, for a change things have been somewhat quiet after the 1.0.6 release. There have been some bug fixes that went in after, but not the usual frenzy of reports right after a release.
Mike
On Apr 14, 2010, at 7:23 AM, Steven Ayre wrote:
We are no longer on SVN, we have now moved to GIT for the 1.0.6 release.
http://wiki.freeswitch.org/wiki/Download_FreeSWITCH
Note that the latest most stable version is always likely to be latest GIT version not the latest tagged released, as there will often be bugs present in the releases that are fixed in the latest GIT version. Tagged releases have more to do with the introduction of new features (such as G729 support in 1.0.6) than any guarantee of stability.
-Steve
On 14 April 2010 09:00, Francisco Scaramanga <scaram@hotmail.de> wrote:
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?
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_________________________________________________________________ http://redirect.gimas.net/?n=M1004xjajah2 Über Messenger günstiger telefonieren? Sagen Sie "Ja" zu JAJAH!
The threshold for rtp timeout is supposed to be consecutive packets lost, not over the duration of the call. Please double check that there is not some long run of silence or something causing an actual rtp timeout, and if you can confirm that, please open a bug on jira for this issue. Mike On Apr 15, 2010, at 8:08 AM, Francisco Scaramanga wrote:
Now I am using stable release 1.0.6 and have a MEDIA_TIMEOUT again, because function rtp_common_read counts missed packets. During a long session of several hours the amount of missed packets exceeds the limit.
Now I changed my .\conf\sip_profiles\internal.xml and set the rtp timeout to 0, which means no timeout.
set <param name="rtp-timeout-sec" value="0"/>
My usecase is to have long duration calls. Can I do this without cross-effects, or is not wise to set rtp timout to 0?
From: mike@jerris.com Date: Wed, 14 Apr 2010 09:08:32 -0400 To: freeswitch-users@lists.freeswitch.org Subject: Re: [Freeswitch-users] MEDIA_TIMEOUT after long duration call
That being said, for a change things have been somewhat quiet after the 1.0.6 release. There have been some bug fixes that went in after, but not the usual frenzy of reports right after a release.
Mike
On Apr 14, 2010, at 7:23 AM, Steven Ayre wrote:
We are no longer on SVN, we have now moved to GIT for the 1.0.6 release.
http://wiki.freeswitch.org/wiki/Download_FreeSWITCH
Note that the latest most stable version is always likely to be latest GIT version not the latest tagged released, as there will often be bugs present in the releases that are fixed in the latest GIT version. Tagged releases have more to do with the introduction of new features (such as G729 support in 1.0.6) than any guarantee of stability.
-Steve
On 14 April 2010 09:00, Francisco Scaramanga <scaram@hotmail.de> wrote:
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?
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Über Messenger günstiger telefonieren? Sagen Sie "Ja" zu JAJAH! _______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
turning off media timeout is perfectly ok, its not even valid to use media timeouts, we have it as a courtesy. sip session timers is the valid method. On Thu, Apr 15, 2010 at 8:46 AM, Michael Jerris <mike@jerris.com> wrote:
The threshold for rtp timeout is supposed to be consecutive packets lost, not over the duration of the call. Please double check that there is not some long run of silence or something causing an actual rtp timeout, and if you can confirm that, please open a bug on jira for this issue.
Mike
On Apr 15, 2010, at 8:08 AM, Francisco Scaramanga wrote:
Now I am using stable release 1.0.6 and have a MEDIA_TIMEOUT again, because function rtp_common_read counts missed packets. During a long session of several hours the amount of missed packets exceeds the limit.
Now I changed my .\conf\sip_profiles\internal.xml and set the rtp timeout to 0, which means no timeout.
set <param name="rtp-timeout-sec" value="0"/>
My usecase is to have long duration calls. Can I do this without cross-effects, or is not wise to set rtp timout to 0?
From: mike@jerris.com Date: Wed, 14 Apr 2010 09:08:32 -0400 To: freeswitch-users@lists.freeswitch.org Subject: Re: [Freeswitch-users] MEDIA_TIMEOUT after long duration call
That being said, for a change things have been somewhat quiet after the 1.0.6 release. There have been some bug fixes that went in after, but not the usual frenzy of reports right after a release.
Mike
On Apr 14, 2010, at 7:23 AM, Steven Ayre wrote:
We are no longer on SVN, we have now moved to GIT for the 1.0.6 release.
http://wiki.freeswitch.org/wiki/Download_FreeSWITCH
Note that the latest most stable version is always likely to be latest GIT version not the latest tagged released, as there will often be bugs present in the releases that are fixed in the latest GIT version. Tagged releases have more to do with the introduction of new features (such as G729 support in 1.0.6) than any guarantee of stability.
-Steve
On 14 April 2010 09:00, Francisco Scaramanga <scaram@hotmail.de> wrote:
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?
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
------------------------------ Über Messenger günstiger telefonieren? Sagen Sie "Ja" zu JAJAH!<http://redirect.gimas.net/?n=M1004jajah> _______________________________________________
FreeSWITCH-users mailing list FreeSWITCH-users@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@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@hotmail.com <MSN%3Aanthony_minessale@hotmail.com> GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com<PAYPAL%3Aanthony.minessale@gmail.com> IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org <sip%3A888@conference.freeswitch.org> googletalk:conf+888@conference.freeswitch.org<googletalk%3Aconf%2B888@conference.freeswitch.org> pstn:+19193869900
that's not 1.0.6 http://wiki.freeswitch.org/wiki/Installation_Guide On Apr 14, 2010, at 4:00 AM, Francisco Scaramanga <scaram@hotmail.de> wrote:
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@gmail.com To: freeswitch-users@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@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@gmail.com To: freeswitch-users@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@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@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@192.168.1.234 [BREAK] 2010-04-12 19:00:51.421875 [NOTICE] mod_dptools.c:649 Channel [sofia/internal/1010@192.168.1.234] has been answered 2010-04-12 19:00:51.421875 [DEBUG] switch_channel.c:182 sofia/internal/1010@192.168.1.234 receive message [AUDIO_SYNC] EXECUTE sofia/internal/1010@192.168.1.234 MyModul 2010-04-12 19:00:51.640625 [DEBUG] sofia.c:3289 Channel sofia/internal/1010@192.168.1.234 entering state [ready][200] 2010-04-13 06:35:53.406250 [NOTICE] mod_sofia.c:744 Hangup sofia/internal/1010@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@192.168.1.234 [KILL] 2010-04-13 06:35:53.406250 [DEBUG] switch_core_session.c:932 Send signal sofia/internal/1010@192.168.1.234 [BREAK] 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:491 (sofia/internal/1010@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@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@192.168.1.234) State HANGUP 2010-04-13 06:35:53.406250 [DEBUG] mod_sofia.c:338 Channel sofia/internal/1010@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@192.168.1.234 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:46 sofia/internal/1010@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@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@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@192.168.1.234 [BREAK] 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:398 (sofia/internal/1010@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@192.168.1.234) State REPORTING 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:53 sofia/internal/1010@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@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@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@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@192.168.1.234) Ended 2010-04-13 06:35:53.406250 [NOTICE] switch_core_session.c:1088 Close Channel sofia/internal/1010@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@192.168.1.234) State DESTROY 2010-04-13 06:35:53.406250 [DEBUG] mod_sofia.c:255 sofia/internal/1010@192.168.1.234 SOFIA DESTROY 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:60 sofia/internal/1010@192.168.1.234 Standard DESTROY 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:564 (sofia/internal/1010@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@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@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@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@hotmail.com GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com IRC: irc.freenode.net #freeswitch
FreeSWITCH Developer Conference sip:888@conference.freeswitch.org googletalk:conf+888@conference.freeswitch.org pstn:+19193869900
Angst vor Spam? Hotmail schützt Sie mit modernster Technologie! _______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch- users http://www.freeswitch.org
"How can I enable a rtp packet trace? It think I should check this too." http://www.wireshark.org/ On 13 April 2010 18:03, Francisco Scaramanga <scaram@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@gmail.com To: freeswitch-users@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@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@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@192.168.1.234 [BREAK] 2010-04-12 19:00:51.421875 [NOTICE] mod_dptools.c:649 Channel [sofia/internal/1010@192.168.1.234] has been answered 2010-04-12 19:00:51.421875 [DEBUG] switch_channel.c:182 sofia/internal/1010@192.168.1.234 receive message [AUDIO_SYNC] EXECUTE sofia/internal/1010@192.168.1.234 MyModul 2010-04-12 19:00:51.640625 [DEBUG] sofia.c:3289 Channel sofia/internal/1010@192.168.1.234 entering state [ready][200] 2010-04-13 06:35:53.406250 [NOTICE] mod_sofia.c:744 Hangup sofia/internal/1010@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@192.168.1.234 [KILL] 2010-04-13 06:35:53.406250 [DEBUG] switch_core_session.c:932 Send signal sofia/internal/1010@192.168.1.234 [BREAK] 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:491 (sofia/internal/1010@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@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@192.168.1.234) State HANGUP 2010-04-13 06:35:53.406250 [DEBUG] mod_sofia.c:338 Channel sofia/internal/1010@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@192.168.1.234 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:46 sofia/internal/1010@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@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@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@192.168.1.234 [BREAK] 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:398 (sofia/internal/1010@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@192.168.1.234) State REPORTING 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:53 sofia/internal/1010@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@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@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@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@192.168.1.234) Ended 2010-04-13 06:35:53.406250 [NOTICE] switch_core_session.c:1088 Close Channel sofia/internal/1010@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@192.168.1.234) State DESTROY 2010-04-13 06:35:53.406250 [DEBUG] mod_sofia.c:255 sofia/internal/1010@192.168.1.234 SOFIA DESTROY 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:60 sofia/internal/1010@192.168.1.234 Standard DESTROY 2010-04-13 06:35:53.406250 [DEBUG] switch_core_state_machine.c:564 (sofia/internal/1010@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@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@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@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
participants (4)
-
Anthony Minessale
-
Francisco Scaramanga
-
Michael Jerris
-
Steven Ayre