May 2011 - FreeSWITCH-users - FreeSWITCH Mailing Lists

many outgoing calls with mod_lcr at the same time possible?
by Anestis Mavro 10 May '11

10 May '11

Hello Freeswitchers, Is it possible to make many outgoing calls with mod_lcr at the same time? An example would be to redirect an incoming call to two mobile phones and ring them simultaneously. With a "normal" bridge we can achieve this, but what about having also LCR (billing and limit included) involved? Regards Anestis

4 5

invalid ELF header error in lua startup script
by Javier Gallart 10 May '11

10 May '11

Hello, we have a lua script that we want to use as startup script in order to start listening for events as soon as FS starts. This is the configuration: <param name="module-directory" value="/usr/lib/lua/5.1/?.so"/> <param name="module-directory" value="/usr/lib/lua/5.1/?.lua"/> <param name="module-directory" value="/usr/lib/lua/5.1/socket/?.lua"/> <param name="module-directory" value="/usr/lib/lua/5.1/socket/?.so"/> <param name="module-directory" value="/usr/local/share/lua/5.1/?.so"/> <param name="module-directory" value="/usr/local/share/lua/5.1/?.lua"/> <param name="module-directory" value="/usr/local/share/lua/5.1/xmlrpc/?.lua"/> <param name="startup-script" value="script.lua"/> The script first line is: require("socket") The file /usr/local/share/lua/5.1/socket.lua exists. Actually when we execute "lua script.lua" it runs properly. But this is the freeswitch log at startup: 2011-05-10 07:00:31.281411 [ERR] mod_lua.cpp:191 error loading module 'socket' from file '/usr/local/share/lua/5.1/socket.lua': /usr/local/share/lua/5.1/socket.lua: invalid ELF header stack traceback: [C]: ? [C]: in function 'require' /usr/local/freeswitch/scripts/script.lua:1: in main chunk Has anyone gone over the same issue? We tried with the latest git. Thanks in advance Javi

2 1

答复: FreeSWITCH-users Digest, Vol 59, Issue 48
by qiqi7036 10 May '11

10 May '11

Hi, I think mod_shout can play remote prompts, please refer this link: http://wiki.freeswitch.org/wiki/Mod_shout dennis.deng -----邮件原件----- 发件人: freeswitch-users-bounces(a)lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] 代表 freeswitch-users-request(a)lists.freeswitch.org 发送时间: 2011年5月10日 4:04 收件人: freeswitch-users(a)lists.freeswitch.org 主题: FreeSWITCH-users Digest, Vol 59, Issue 48 Send FreeSWITCH-users mailing list submissions to freeswitch-users(a)lists.freeswitch.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.freeswitch.org/mailman/listinfo/freeswitch-users or, via email, send a message with subject or body 'help' to freeswitch-users-request(a)lists.freeswitch.org You can reach the person managing the list at freeswitch-users-owner(a)lists.freeswitch.org When replying, please edit your Subject line so it is more specific than "Re: Contents of FreeSWITCH-users digest..."

1 0

How to manipulate destination number before routing to PSTN GW
by fieldpeak 10 May '11

10 May '11

Gurus, i met an issue for dial plan, it sounds easy but puzzled me a few days not fix it yet...i belive gurus here could help me... i want to remove the + of destination number before routing to PSTN GW, e.g. when i dial +9123, i would like FS remove +, and then route to the PSTN GW, below is the dial plan and log, See the log, FS did remove '+' of '+9123', but then when it checks the rule ‘9_to_GW’, it still checks '+9123' (I expect it is '9123'), and then failed. Thanks. *Dial plan:* <extension name="remove_plus_of_dst_num" continue="true"> <condition field="destination_number" expression="^\+(\d+)$"> <action application="set" data="effective_destination_number=$1"/> </condition> </extension> …... <extension name="9_to_GW" > <condition field="destination_number" expression="^(9\d+)$"> <action application="bridge" data="sofia/internal/$1(a)192.168.200.101 "/> </condition> </extension> *Log:* freeswitch@mypc> 2011-05-07 22:48:05.717537 [DEBUG] sofia.c:6488 IP 192.168.200.201 Approved by acl "192.168.0.0/16[]". Access Granted. 2011-05-07 22:48:05.717537 [NOTICE] switch_channel.c:812 New Channel sofia/inter nal/+4001(a)192.168.200.100 [92568c57-ff7b-4dbc-b322-a9babf893e62] 2011-05-07 22:48:05.719537 [DEBUG] sofia.c:4760 Channel sofia/internal/+4001@192 .168.200.100 entering state [received][100] 2011-05-07 22:48:05.719537 [DEBUG] sofia.c:4771 Remote SDP: v=0 o=AudiocodesGW 1062502113 1062501981 IN IP4 192.168.200.201 s=Phone-Call c=IN IP4 192.168.200.201 t=0 0 m=audio 6060 RTP/AVP 8 0 96 a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:96 telephone-event/8000 a=fmtp:96 0-15 a=ptime:20 2011-05-07 22:48:05.719537 [DEBUG] sofia.c:4908 (sofia/internal/+4001(a)192.168.20 0.100) State Change CS_NEW -> CS_INIT 2011-05-07 22:48:05.719537 [DEBUG] switch_core_session.c:1116 Send signal sofia/ internal/+4001(a)192.168.200.100 [BREAK] 2011-05-07 22:48:05.722537 [DEBUG] switch_core_state_machine.c:325 (sofia/intern al/+4001(a)192.168.200.100) Running State Change CS_INIT 2011-05-07 22:48:05.722537 [DEBUG] switch_core_state_machine.c:361 (sofia/intern al/+4001(a)192.168.200.100) State INIT 2011-05-07 22:48:05.722537 [DEBUG] mod_sofia.c:84 sofia/internal/+4001(a)192.168.2 00.100 SOFIA INIT 2011-05-07 22:48:05.722537 [DEBUG] mod_sofia.c:124 (sofia/internal/+4001(a)192.168 .200.100) State Change CS_INIT -> CS_ROUTING 2011-05-07 22:48:05.722537 [DEBUG] switch_core_session.c:1116 Send signal sofia/ internal/+4001(a)192.168.200.100 [BREAK] 2011-05-07 22:48:05.722537 [DEBUG] switch_core_state_machine.c:361 (sofia/intern al/+4001(a)192.168.200.100) State INIT going to sleep 2011-05-07 22:48:05.722537 [DEBUG] switch_core_state_machine.c:325 (sofia/intern al/+4001(a)192.168.200.100) Running State Change CS_ROUTING 2011-05-07 22:48:05.722537 [DEBUG] switch_channel.c:1668 (sofia/internal/+4001@1 92.168.200.100) Callstate Change DOWN -> RINGING 2011-05-07 22:48:05.722537 [DEBUG] switch_core_state_machine.c:364 (sofia/intern al/+4001(a)192.168.200.100) State ROUTING 2011-05-07 22:48:05.722537 [DEBUG] mod_sofia.c:147 sofia/internal/+4001(a)192.168. 200.100 SOFIA ROUTING 2011-05-07 22:48:05.722537 [DEBUG] switch_core_state_machine.c:77 sofia/internal /+4001(a)192.168.200.100 Standard ROUTING 2011-05-07 22:48:05.722537 [INFO] mod_dialplan_xml.c:331 Processing +4001 <+4001 >->+9123 in context default Dialplan: sofia/internal/+4001(a)192.168.200.100 parsing [default->unloop] continu e=false Dialplan: sofia/internal/+4001(a)192.168.200.100 Regex (PASS) [unloop] ${unroll_lo ops}(true) =~ /^true$/ break=on-false Dialplan: sofia/internal/+4001(a)192.168.200.100 Regex (FAIL) [unloop] ${sip_loope d_call}() =~ /^true$/ break=on-false Dialplan: sofia/internal/+4001(a)192.168.200.100 parsing [default->remove_plus_of_ dst_num] continue=true Dialplan: sofia/internal/+4001(a)192.168.200.100 Regex (PASS) [remove_plus_of_dst_ num] destination_number(+9123) =~ /^\+(\d+)$/ break=on-false Dialplan: sofia/internal/+4001(a)192.168.200.100 Action set(destination_number=912 3) Dialplan: sofia/internal/+4001(a)192.168.200.100 parsing [default->remove_plus_of_ src_num] continue=true Dialplan: sofia/internal/+4001(a)192.168.200.100 Regex (PASS) [remove_plus_of_src_ num] caller_id_number(+4001) =~ /^\+(\d+)$/ break=on-false Dialplan: sofia/internal/+4001(a)192.168.200.100 Action set(effective_caller_id_na me=4001) Dialplan: sofia/internal/+4001(a)192.168.200.100 Action set(effective_caller_id_nu mber=4001) Dialplan: sofia/internal/+4001(a)192.168.200.100 parsing [default->7_8_to_Lync] co ntinue=false Dialplan: sofia/internal/+4001(a)192.168.200.100 Regex (FAIL) [7_8_to_Lync] destin ation_number(+9123) =~ /^([78]\d{3})$/ break=on-false Dialplan: sofia/internal/+4001(a)192.168.200.100 parsing [default->9_to_GW] contin ue=false Dialplan: sofia/internal/+4001(a)192.168.200.100 Regex (FAIL) [9_to_GW] destinatio n_number(+9123) =~ /^(9\d+)$/ break=on-false Dialplan: sofia/internal/+4001(a)192.168.200.100 parsing [default->1_to_IPP] conti nue=false Dialplan: sofia/internal/+4001(a)192.168.200.100 Regex (FAIL) [1_to_IPP] destinati on_number(+9123) =~ /^(1\d{3})$/ break=on-false Dialplan: sofia/internal/+4001(a)192.168.200.100 parsing [default->DISA] continue= false Dialplan: sofia/internal/+4001(a)192.168.200.100 Regex (FAIL) [DISA] destination_n umber(+9123) =~ /^\*(3472)$/ break=on-false Dialplan: sofia/internal/+4001(a)192.168.200.100 parsing [default->Recordings] con tinue=false Dialplan: sofia/internal/+4001(a)192.168.200.100 Regex (FAIL) [Recordings] destina tion_number(+9123) =~ /^\*(732673)$/ break=on-false 2011-05-07 22:48:05.727537 [DEBUG] switch_core_state_machine.c:119 (sofia/intern al/+4001(a)192.168.200.100) State Change CS_ROUTING -> CS_EXECUTE 2011-05-07 22:48:05.727537 [DEBUG] switch_core_session.c:1116 Send signal sofia/ internal/+4001(a)192.168.200.100 [BREAK] 2011-05-07 22:48:05.727537 [DEBUG] switch_core_state_machine.c:364 (sofia/intern al/+4001(a)192.168.200.100) State ROUTING going to sleep 2011-05-07 22:48:05.727537 [DEBUG] switch_core_state_machine.c:325 (sofia/intern al/+4001(a)192.168.200.100) Running State Change CS_EXECUTE 2011-05-07 22:48:05.727537 [DEBUG] switch_core_state_machine.c:371 (sofia/intern al/+4001(a)192.168.200.100) State EXECUTE 2011-05-07 22:48:05.727537 [DEBUG] mod_sofia.c:240 sofia/internal/+4001(a)192.168. 200.100 SOFIA EXECUTE 2011-05-07 22:48:05.727537 [DEBUG] switch_core_state_machine.c:157 sofia/interna l/+4001(a)192.168.200.100 Standard EXECUTE EXECUTE sofia/internal/+4001(a)192.168.200.100 set(destination_number=9123) 2011-05-07 22:48:05.728537 [DEBUG] mod_dptools.c:1060 sofia/internal/+4001(a)192.1 68.200.100 SET [destination_number]=[9123] EXECUTE sofia/internal/+4001(a)192.168.200.100set(effective_caller_id_name=4001) 2011-05-07 22:48:05.728537 [DEBUG] mod_dptools.c:1060 sofia/internal/+4001(a)192.1 68.200.100 SET [effective_caller_id_name]=[4001] EXECUTE sofia/internal/+4001(a)192.168.200.100set(effective_caller_id_number=4001 ) 2011-05-07 22:48:05.729537 [DEBUG] mod_dptools.c:1060 sofia/internal/+4001(a)192.1 68.200.100 SET [effective_caller_id_number]=[4001] 2011-05-07 22:48:05.729537 [NOTICE] switch_core_state_machine.c:189 sofia/intern al/+4001(a)192.168.200.100 has executed the last dialplan instruction, hanging up. 2011-05-07 22:48:05.729537 [DEBUG] switch_channel.c:2563 (sofia/internal/+4001@1 92.168.200.100) Callstate Change RINGING -> HANGUP 2011-05-07 22:48:05.729537 [NOTICE] switch_core_state_machine.c:191 Hangup sofia /internal/+4001(a)192.168.200.100 [CS_EXECUTE] [NORMAL_CLEARING] 2011-05-07 22:48:05.730538 [DEBUG] switch_channel.c:2579 Send signal sofia/inter nal/+4001(a)192.168.200.100 [KILL] 2011-05-07 22:48:05.730538 [DEBUG] switch_core_session.c:1116 Send signal sofia/ internal/+4001(a)192.168.200.100 [BREAK] 2011-05-07 22:48:05.730538 [DEBUG] switch_core_state_machine.c:371 (sofia/intern al/+4001(a)192.168.200.100) State EXECUTE going to sleep 2011-05-07 22:48:05.730538 [DEBUG] switch_core_state_machine.c:325 (sofia/intern al/+4001(a)192.168.200.100) Running State Change CS_HANGUP 2011-05-07 22:48:05.731538 [DEBUG] switch_core_state_machine.c:565 (sofia/intern al/+4001(a)192.168.200.100) State HANGUP 2011-05-07 22:48:05.732538 [DEBUG] mod_sofia.c:457 Channel sofia/internal/+4001@ 192.168.200.100 hanging up, cause: NORMAL_CLEARING 2011-05-07 22:48:05.732538 [DEBUG] mod_sofia.c:519 Responding to INVITE with: 48 0 2011-05-07 22:48:05.732538 [DEBUG] switch_core_state_machine.c:46 sofia/internal /+4001(a)192.168.200.100 Standard HANGUP, cause: NORMAL_CLEARING 2011-05-07 22:48:05.732538 [DEBUG] switch_core_state_machine.c:565 (sofia/intern al/+4001(a)192.168.200.100) State HANGUP going to sleep 2011-05-07 22:48:05.732538 [DEBUG] switch_core_state_machine.c:356 (sofia/intern al/+4001(a)192.168.200.100) State Change CS_HANGUP -> CS_REPORTING 2011-05-07 22:48:05.732538 [DEBUG] switch_core_session.c:1116 Send signal sofia/ internal/+4001(a)192.168.200.100 [BREAK] 2011-05-07 22:48:05.732538 [DEBUG] switch_core_state_machine.c:325 (sofia/intern al/+4001(a)192.168.200.100) Running State Change CS_REPORTING 2011-05-07 22:48:05.732538 [DEBUG] switch_core_state_machine.c:625 (sofia/intern al/+4001(a)192.168.200.100) State REPORTING 2011-05-07 22:48:06.017554 [DEBUG] switch_core_state_machine.c:53 sofia/internal /+4001(a)192.168.200.100 Standard REPORTING, cause: NORMAL_CLEARING 2011-05-07 22:48:06.017554 [DEBUG] switch_core_state_machine.c:625 (sofia/intern al/+4001(a)192.168.200.100) State REPORTING going to sleep 2011-05-07 22:48:06.017554 [DEBUG] switch_core_state_machine.c:350 (sofia/intern al/+4001(a)192.168.200.100) State Change CS_REPORTING -> CS_DESTROY 2011-05-07 22:48:06.017554 [DEBUG] switch_core_session.c:1116 Send signal sofia/ internal/+4001(a)192.168.200.100 [BREAK] 2011-05-07 22:48:06.017554 [DEBUG] switch_core_session.c:1288 Session 2 (sofia/i nternal/+4001(a)192.168.200.100) Locked, Waiting on external entities 2011-05-07 22:48:06.017554 [NOTICE] switch_core_session.c:1306 Session 2 (sofia/ internal/+4001(a)192.168.200.100) Ended 2011-05-07 22:48:06.017554 [NOTICE] switch_core_session.c:1308 Close Channel sof ia/internal/+4001(a)192.168.200.100 [CS_DESTROY] 2011-05-07 22:48:06.018554 [DEBUG] switch_core_state_machine.c:454 (sofia/intern al/+4001(a)192.168.200.100) Callstate Change HANGUP -> DOWN 2011-05-07 22:48:06.018554 [DEBUG] switch_core_state_machine.c:457 (sofia/intern al/+4001(a)192.168.200.100) Running State Change CS_DESTROY 2011-05-07 22:48:06.018554 [DEBUG] switch_core_state_machine.c:467 (sofia/intern al/+4001(a)192.168.200.100) State DESTROY 2011-05-07 22:48:06.018554 [DEBUG] mod_sofia.c:362 sofia/internal/+4001(a)192.168. 200.100 SOFIA DESTROY 2011-05-07 22:48:06.018554 [DEBUG] switch_core_state_machine.c:60 sofia/internal /+4001(a)192.168.200.100 Standard DESTROY 2011-05-07 22:48:06.018554 [DEBUG] switch_core_state_machine.c:467 (sofia/intern al/+4001(a)192.168.200.100) State DESTROY going to sleep

8 11

Moving on from CentOS
by Max Clark 10 May '11

10 May '11

Hello all, Recent developments (or absolute lack of) within the CentOS project and its perceived long term viability has forced an internal discussion to select a successor distribution. The most likely candidates at this point are Ubuntu and its LTS releases for servers, and Scientific Linux with the new 6.x releases. The pro/con lists for each are growing and the issue is complicated. With CentOS 5.x being the reference distro for FreeSWITCH development I'm curious if this conversation has started among the FreeSWITCH developers, and if it has, what is the project leaning to for a successor distribution? Thanks, Max

18 25

Rates Normalizer / Importer tool
by A E [Gmail] 09 May '11

09 May '11

Hi All, Wondering if anyone has / knows of, a good rate importer tool that can be used to standardize and normalize the rates obtained from various carriers so they can be analysed and imported into a DB or be saved as a CSV or something? Should I have posted this in the Freeswitch-Biz list? Thanks so much in advance aeg

3 4

SkypeKit for mo_skyopen?
by mazilo 09 May '11

09 May '11

I wondered if this http://developer.skype.com/public/skypekit SkypeKit will help making mod_skypopen more useable. Has any FS developers here gotten a chance to take a look at http://developer.skype.com/public/skypekit SkypeKit and tries to incorporate into FS for mod_skypopen to replace the need for a Skype client? ----- FreeSWITCH hosted on a Seagate DockStar with OpenWRT. -- View this message in context: http://freeswitch-users.2379917.n2.nabble.com/SkypeKit-for-mo-skyopen-tp634… Sent from the freeswitch-users mailing list archive at Nabble.com.

6 9

SpanDSP: nocng for rxfax?
by Kristian Kielhofner 09 May '11

09 May '11

Hello all, I'm using tone_detect (1100Hz) to detect incoming faxes. It's working pretty well but I'm noticing that there seem to be some timing issues when using rxfax as rxfax seems to do its own tone detection. Is it possible to use "nocng" or something similar to tell rxfax to skip tone detection (as I'm doing it with tone_detect first anyway)? Is this a terrible idea? Thanks! -- Kristian Kielhofner

3 3

Unable to install Centos on AMD Motherboard (SB850)
by Charles Bujold 09 May '11

09 May '11

Upgrading our Freeswitch server to a newer PC which has an AMD SB850 chipset motherboard and Centos is unable to install since it does not have the SATA drivers support. First tried finding a driver with no success. Then tried seeing when Centos 6 was going to be released but it looks like nobody really knows. So now I'm looking at Ubuntu 11.4 as a possible OS. I like Centos but if it can't keep up and can only support older equipment I'm wondering if it is the right platform for us. Is anybody using Ubuntu 11.4 and how does Freeswitch work on it? Thanks cjb

5 6

Pass UUI through SIP
by Yungwei Chen 09 May '11

09 May '11

Hi, I want to check if Freeswitch supports passing UUI from a sip client to an IVR via SIP messages in the following scenario. My google search found a few UUI related threads, which are not helpful. A custom application tells Freeswitch to make an outbound call to someone using call management commands. When the call is answered, Freeswitch connects the person to an IVR. (So now the person is talking to the IVR.) In order to be able to find corresponding calls initiated from the application on the IVR side, the application attches a UUID to each outbound call and the UUID is expected to pass to the IVR via SIP messages. Thanks.

2 1