May 2009 - freeswitch-dev@lists.freeswitch.org

[Freeswitch-dev] fifo in occasionally drops call
by Scott Shen 06 May '09

06 May '09

Using FS r13231, when testing fifo in, experienced occasionally call drops with no obvious reason, is it something to do with early media? See the debug log below Dialplan: sofia/internal/sip:1007@192.168.0.31:5342 Regex (PASS) [TEST_Q] destination_number(40001) =~ /^40001$/ break=on-false Dialplan: sofia/internal/sip:1007@192.168.0.31:5342 Action fifo(test_q in) 2009-05-06 15:18:46 [DEBUG] switch_core_state_machine.c:114 switch_core_standard_on_routing() (sofia/internal/sip:1007@192.168.0.31:5342) State Change CS_ROUTING -> CS_EXECUTE 2009-05-06 15:18:46 [DEBUG] switch_core_session.c:933 switch_core_session_signal_state_change() Send signal sofia/internal/sip:1007@192.168.0.31:5342 [BREAK] 2009-05-06 15:18:46 [DEBUG] switch_core_state_machine.c:483 switch_core_session_run() (sofia/internal/sip:1007@192.168.0.31:5342) State ROUTING going to sleep 2009-05-06 15:18:46 [DEBUG] switch_core_state_machine.c:397 switch_core_session_run() (sofia/internal/sip:1007@192.168.0.31:5342) Running State Change CS_EXECUTE 2009-05-06 15:18:46 [DEBUG] switch_core_state_machine.c:490 switch_core_session_run() (sofia/internal/sip:1007@192.168.0.31:5342) State EXECUTE 2009-05-06 15:18:46 [DEBUG] mod_sofia.c:173 sofia_on_execute() sofia/internal/sip:1007@192.168.0.31:5342 SOFIA EXECUTE 2009-05-06 15:18:46 [DEBUG] switch_core_state_machine.c:151 switch_core_standard_on_execute() sofia/internal/sip:1007@192.168.0.31:5342 Standard EXECUTE EXECUTE sofia/internal/sip:1007@192.168.0.31:5342 set(outside_call=true) 2009-05-06 15:18:46 [DEBUG] mod_dptools.c:748 set_function() sofia/internal/sip:1007@192.168.0.31:5342 SET [outside_call]=[true] EXECUTE sofia/internal/sip:1007@192.168.0.31:5342 fifo(test_q in) 2009-05-06 15:18:46 [DEBUG] switch_ivr.c:1342 switch_ivr_session_transfer() (sofia/internal/sip:1007@192.168.0.31:5342) State Change CS_EXECUTE -> CS_ROUTING 2009-05-06 15:18:46 [DEBUG] switch_core_session.c:933 switch_core_session_signal_state_change() Send signal sofia/internal/sip:1007@192.168.0.31:5342 [BREAK] 2009-05-06 15:18:46 [NOTICE] switch_core_state_machine.c:179 switch_core_standard_on_execute() Hangup sofia/internal/sip:1007@192.168.0.31:5342 [CS_EXECUTE] [NORMAL_CLEARING] 2009-05-06 15:18:46 [DEBUG] switch_channel.c:1641 switch_channel_perform_hangup() Send signal sofia/internal/sip:1007@192.168.0.31:5342 [KILL] 2009-05-06 15:18:46 [DEBUG] switch_core_session.c:933 switch_core_session_signal_state_change() Send signal sofia/internal/sip:1007@192.168.0.31:5342 [BREAK] 2009-05-06 15:18:46 [DEBUG] switch_core_state_machine.c:490 switch_core_session_run() (sofia/internal/sip:1007@192.168.0.31:5342) State EXECUTE going to sleep 2009-05-06 15:18:46 [DEBUG] switch_core_state_machine.c:397 switch_core_session_run() (sofia/internal/sip:1007@192.168.0.31:5342) Running State Change CS_HANGUP 2009-05-06 15:18:46 [DEBUG] switch_core_state_machine.c:433 switch_core_session_run() (sofia/internal/sip:1007@192.168.0.31:5342) State HANGUP 2009-05-06 15:18:46 [DEBUG] mod_sofia.c:323 sofia_on_hangup() Channel sofia/internal/sip:1007@192.168.0.31:5342 hanging up, cause: NORMAL_CLEARING 2009-05-06 15:18:46 [DEBUG] mod_sofia.c:378 sofia_on_hangup() Sending BYE to sofia/internal/sip:1007@192.168.0.31:5342 Regards Scott

1 0

[Freeswitch-dev] originate creates a channel that can not be killed
by Scott Shen 06 May '09

06 May '09

I am using FS r13096, found following problem 1. originate {originate_timeout=6,originate_retries=3,originate_retry_sleep_ms=60000}user/1002 &bridge(user/1007) 2. when 1002 side ringing, quickly pickup and hangup 3. show channels gives something like 31b614d0-999d-406e-bdba-b18ead0d26d8,outbound,2009-05-04 13:42:56,1241408576,sofia/internal/sip:1002@192.168.10.100:5060;line=xStcbdok,CS_EXECUTE,FreeSWITCH,0000000000,,sip:1002@192.168.10.100:5060;line=xStcbdok,bridge,user/1007,,default,PCMA,8000,PCMA,8000 1. when use uuid_kill of above uuid, FS reports "No Such Channel" 2. then at 60000ms interval, FS will give messages like 'Originate attempt x/3 in 60000ms' 3. when x reaches 1, the channel will be cleaned. On step 3 and 4, if there's "No Such Channel", isn't that the channel should not be displayed? On step 5, although the "originate" is attempted ( which shouldn't, because the call is already hangup on step 2 ), but neither caller nor the callee is ringed. Also, is there a way to cancel "originate" ? eg send a cancel after invite. Regards Scott

3 6

[Freeswitch-dev] ClueCon 2009 Blog, Moises Silva Speaking
by Michael Collins 06 May '09

06 May '09

FYI, I just wanted to let the community know that we maintain a blog<http://cluecon.com/blog/1>on the ClueCon website <http://www.cluecon.com>. Please check it out. The latest entry mentions Moises Silva's recent blog entry about his speaking at ClueCon this year. Please check the ClueCon blog periodically as we will be adding new information about speakers, sponsors, and other good stuff. -Michael S Collins http://www.cluecon.com

1 0

[Freeswitch-dev] ANNOUNCEMENT: FreeSWITCH mod_opal Now Officially In Beta
by Michael Collins 04 May '09

04 May '09

The FreeSWITCH team would like everyone to know that the mod_opal module is now officially in beta. Please read this article for more information: http://www.freeswitch.org/node/179 Many thanks to Robert Jongbloed and Craig Southeren of the OPAL project for their many years of support for open source VoIP. -Michael S Collins http://www.cluecon.com

1 0