- FreeSWITCH-users - FreeSWITCH Mailing Lists

Generate calls with required CPS.
by Aqs Younas 10 Dec '15

10 Dec '15

Hi, I have a gateway registered with my freeswitch. Currently I generate(originate) calls with python script using ESL to 500 to 2000 numbers to that gateway. Is there anyway to send call to gateway with required CPS. Like my gateway allows calls not greater than 5 CPS. Any suggestion would be much appreciated. Thanks.

4 4

fs_cli problem
by covici＠ccs.covici.com 10 Dec '15

10 Dec '15

Hi. I am noticing that in recent versions of fs -- at least from git of about 1 December of this year, if you are editing a command line and if you use control-d to delete a character where your cursor is, it deletes the prior character instead. Anyone else seeing this? Thanks in advance for any ideas. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici covici(a)ccs.covici.com

5 4

Custom ringback tone
by Michael Nielsen 10 Dec '15

10 Dec '15

Hi, I'm trying to add a custom ringback tone on my FreeSWITCH server. I've created a .mp3 file and added: <action application="set" data="ringback=/home/user/ringback.mp3"/> However, when trying to call, there's just silence... Should the format be different, and if so how do I convert this?

7 18

Import variable from bleg to aleg
by Ximo Peral 10 Dec '15

10 Dec '15

Hello, I need to import a variable from b-leg to a-leg but renaming. I use the parameter <action application = "set" data = "this_is_a_variable_name import =" /> https://wiki.freeswitch.org/wiki/Variable_import The problem is that I can not change the name of the variable. Change the value of the variable in aleg. You know if this is possible?

1 0

originate -ERR NORMAL_TEMPORARY_FAILURE
by Aqs Younas 10 Dec '15

10 Dec '15

Hi, I have just installed FreeSWITCH Version 1.7.0+git~20151210T010223Z~85f8bca628~64bit (git 85f8bca 2015-12-10 01:02:23Z 64bit) and registered two default user without changing anything on my local server. freeswitch@internal> sofia status profile internal reg Registrations: ================================================================================================= Call-ID: OfA_p_gR_cgODJYoIsvSNg.. User: 1010(a)192.168.10.41 Contact: "" <sip:1010@182.176.103.109:39618 ;rinstance=c2197b164b54c39f;transport=UDP> Agent: Z 3.7.30891 r30851 Status: Registered(UDP)(unknown) EXP(2015-12-09 22:28:28) EXPSECS(2770) Ping-Status: Reachable Ping-Time: 0.00 Host: debian IP: 192.168.10.37 Port: 39618 Auth-User: 1010 Auth-Realm: 192.168.10.41 MWI-Account: 1010(a)192.168.10.41 Call-ID: II5QsfQj_hgDlJI8jdEmEA.. User: 1015(a)192.168.10.41 Contact: "" <sip:1015@182.176.103.109:39618 ;rinstance=18c203322f8c75d5;transport=TCP> Agent: Z 3.7.30891 r30851 Status: Registered(TCP)(unknown) EXP(2015-12-09 22:30:03) EXPSECS(2865) Ping-Status: Reachable Ping-Time: 0.00 Host: debian IP: 192.168.10.37 Port: 58530 Auth-User: 1015 Auth-Realm: 192.168.10.41 MWI-Account: 1015(a)192.168.10.41 Total items returned: 2 ================================================================================================= But when i try to call user 1015 using originate and connect with extension 8000. freeswitch@internal> originate sofia/internal/1010%192.168.10.41 8000 -ERR NORMAL_TEMPORARY_FAILURE Also freeswitch@internal> originate user/1010 8000 -ERR NORMAL_TEMPORARY_FAILURE 2015-12-09 21:45:04.194431 [DEBUG] switch_ivr_originate.c:2128 Parsing global variables 2015-12-09 21:45:04.194431 [DEBUG] switch_ivr_originate.c:2128 Parsing global variables 2015-12-09 21:45:04.194431 [NOTICE] switch_channel.c:1091 New Channel sofia/internal/1010@182.176.103.109:39618 [196521b6-3287-430e-a560-80cb2799bc48] 2015-12-09 21:45:04.194431 [DEBUG] mod_sofia.c:4775 (sofia/internal/ 1010@182.176.103.109:39618) State Change CS_NEW -> CS_INIT 2015-12-09 21:45:04.194431 [NOTICE] switch_ivr_originate.c:2763 Cannot create outgoing channel of type [error] cause: [USER_NOT_REGISTERED] 2015-12-09 21:45:04.194431 [DEBUG] switch_core_state_machine.c:473 (sofia/internal/1010@182.176.103.109:39618) Running State Change CS_INIT 2015-12-09 21:45:04.194431 [DEBUG] switch_core_state_machine.c:516 (sofia/internal/1010@182.176.103.109:39618) State INIT 2015-12-09 21:45:04.194431 [DEBUG] mod_sofia.c:88 sofia/internal/ 1010@182.176.103.109:39618 SOFIA INIT 2015-12-09 21:45:04.513945 [DEBUG] switch_nat.c:508 mapped public port 17470 protocol UDP to localport 17470 2015-12-09 21:45:04.539548 [DEBUG] sofia_glue.c:1257 sofia/internal/ 1010@182.176.103.109:39618 sending invite version: 1.7.0 git 85f8bca 2015-12-10 01:02:23Z 64bit Local SDP: v=0 o=FreeSWITCH 1449698034 1449698035 IN IP4 182.176.103.109 s=FreeSWITCH c=IN IP4 182.176.103.109 t=0 0 m=audio 17470 RTP/AVP 9 0 8 101 a=rtpmap:9 G722/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:20 a=sendrecv send 1306 bytes to udp/[182.176.103.109]:39618 at 21:45:04.540029: ------------------------------------------------------------------------ INVITE sip:1010@182.176.103.109:39618;rinstance=c2197b164b54c39f;transport=UDP SIP/2.0 Via: SIP/2.0/UDP 182.176.103.109;rport;branch=z9hG4bKcBm8r50ZcZ9ma Max-Forwards: 70 From: "" <sip:0000000000@192.168.10.41>;tag=aaD54F6Xm2Q2K To: <sip:1010@182.176.103.109:39618 ;rinstance=c2197b164b54c39f;transport=UDP> Call-ID: db9b9b73-198a-1234-408f-0800274aea4c CSeq: 84521688 INVITE Contact: <sip:mod_sofia@182.176.103.109:5060> User-Agent: FreeSWITCH-mod_sofia/1.7.0+git~20151210T010223Z~85f8bca628~64bit Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE Supported: timer, path, replaces Allow-Events: talk, hold, conference, presence, as-feature-event, dialog, line-seize, call-info, sla, include-session-description, presence.winfo, message-summary, refer Content-Type: application/sdp Content-Disposition: session Content-Length: 274 X-FS-Support: update_display,send_info Remote-Party-ID: <sip:0000000000@192.168.10.41 >;party=calling;screen=yes;privacy=off v=0 o=FreeSWITCH 1449698034 1449698035 IN IP4 182.176.103.109 s=FreeSWITCH c=IN IP4 182.176.103.109 t=0 0 m=audio 17470 RTP/AVP 9 0 8 101 a=rtpmap:9 G722/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:20 ------------------------------------------------------------------------ 2015-12-09 21:45:04.539548 [DEBUG] switch_core_state_machine.c:40 sofia/internal/1010@182.176.103.109:39618 Standard INIT 2015-12-09 21:45:04.539548 [DEBUG] switch_core_state_machine.c:48 (sofia/internal/1010@182.176.103.109:39618) State Change CS_INIT -> CS_ROUTING 2015-12-09 21:45:04.539548 [DEBUG] switch_core_state_machine.c:516 (sofia/internal/1010@182.176.103.109:39618) State INIT going to sleep 2015-12-09 21:45:04.539548 [DEBUG] switch_core_state_machine.c:473 (sofia/internal/1010@182.176.103.109:39618) Running State Change CS_ROUTING 2015-12-09 21:45:04.539548 [DEBUG] sofia.c:6755 Channel sofia/internal/ 1010@182.176.103.109:39618 entering state [calling][0] 2015-12-09 21:45:04.539548 [DEBUG] sofia.c:6755 Channel sofia/internal/ 1010@182.176.103.109:39618 entering state [terminated][503] 2015-12-09 21:45:04.539548 [NOTICE] sofia.c:7774 Hangup sofia/internal/ 1010@182.176.103.109:39618 [CS_ROUTING] [NORMAL_TEMPORARY_FAILURE] 2015-12-09 21:45:04.539548 [DEBUG] switch_core_state_machine.c:532 (sofia/internal/1010@182.176.103.109:39618) State ROUTING 2015-12-09 21:45:04.539548 [DEBUG] mod_sofia.c:141 sofia/internal/ 1010@182.176.103.109:39618 SOFIA ROUTING 2015-12-09 21:45:04.539548 [DEBUG] switch_core_state_machine.c:532 (sofia/internal/1010@182.176.103.109:39618) State ROUTING going to sleep 2015-12-09 21:45:04.539548 [DEBUG] switch_core_state_machine.c:473 (sofia/internal/1010@182.176.103.109:39618) Running State Change CS_HANGUP 2015-12-09 21:45:04.539548 [DEBUG] switch_core_state_machine.c:739 (sofia/internal/1010@182.176.103.109:39618) Callstate Change DOWN -> HANGUP 2015-12-09 21:45:04.539548 [DEBUG] switch_core_state_machine.c:741 (sofia/internal/1010@182.176.103.109:39618) State HANGUP 2015-12-09 21:45:04.539548 [DEBUG] mod_sofia.c:431 Channel sofia/internal/ 1010@182.176.103.109:39618 hanging up, cause: NORMAL_TEMPORARY_FAILURE 2015-12-09 21:45:04.539548 [DEBUG] switch_core_state_machine.c:60 sofia/internal/1010@182.176.103.109:39618 Standard HANGUP, cause: NORMAL_TEMPORARY_FAILURE 2015-12-09 21:45:04.539548 [DEBUG] switch_core_state_machine.c:741 (sofia/internal/1010@182.176.103.109:39618) State HANGUP going to sleep 2015-12-09 21:45:04.539548 [DEBUG] switch_core_state_machine.c:508 (sofia/internal/1010@182.176.103.109:39618) State Change CS_HANGUP -> CS_REPORTING 2015-12-09 21:45:04.539548 [DEBUG] switch_core_state_machine.c:473 (sofia/internal/1010@182.176.103.109:39618) Running State Change CS_REPORTING 2015-12-09 21:45:04.539548 [DEBUG] switch_core_state_machine.c:827 (sofia/internal/1010@182.176.103.109:39618) State REPORTING 2015-12-09 21:45:04.539548 [DEBUG] switch_core_state_machine.c:104 sofia/internal/1010@182.176.103.109:39618 Standard REPORTING, cause: NORMAL_TEMPORARY_FAILURE 2015-12-09 21:45:04.539548 [DEBUG] switch_core_state_machine.c:827 (sofia/internal/1010@182.176.103.109:39618) State REPORTING going to sleep 2015-12-09 21:45:04.539548 [DEBUG] switch_core_state_machine.c:499 (sofia/internal/1010@182.176.103.109:39618) State Change CS_REPORTING -> CS_DESTROY 2015-12-09 21:45:04.539548 [DEBUG] switch_core_session.c:1646 Session 12 (sofia/internal/1010@182.176.103.109:39618) Locked, Waiting on external entities 2015-12-09 21:45:04.539548 [DEBUG] switch_ivr_originate.c:3751 Originate Resulted in Error Cause: 41 [NORMAL_TEMPORARY_FAILURE] 2015-12-09 21:45:04.539548 [NOTICE] switch_ivr_originate.c:2763 Cannot create outgoing channel of type [user] cause: [NORMAL_TEMPORARY_FAILURE] 2015-12-09 21:45:04.539548 [DEBUG] switch_ivr_originate.c:3751 Originate Resulted in Error Cause: 41 [NORMAL_TEMPORARY_FAILURE] 2015-12-09 21:45:04.539548 [NOTICE] switch_core_session.c:1664 Session 12 (sofia/internal/1010@182.176.103.109:39618) Ended 2015-12-09 21:45:04.539548 [NOTICE] switch_core_session.c:1668 Close Channel sofia/internal/1010@182.176.103.109:39618 [CS_DESTROY] 2015-12-09 21:45:04.539548 [DEBUG] switch_core_state_machine.c:630 (sofia/internal/1010@182.176.103.109:39618) Running State Change CS_DESTROY 2015-12-09 21:45:04.539548 [DEBUG] switch_core_state_machine.c:640 (sofia/internal/1010@182.176.103.109:39618) State DESTROY 2015-12-09 21:45:04.539548 [DEBUG] mod_sofia.c:341 sofia/internal/ 1010@182.176.103.109:39618 SOFIA DESTROY 2015-12-09 21:45:04.894497 [DEBUG] switch_nat.c:568 unmapped public port 17470 protocol UDP to localport 17470 2015-12-09 21:45:05.094227 [DEBUG] switch_core_state_machine.c:111 sofia/internal/1010@182.176.103.109:39618 Standard DESTROY 2015-12-09 21:45:05.094227 [DEBUG] switch_core_state_machine.c:640 (sofia/internal/1010@182.176.103.109:39618) State DESTROY going to sleep Why it is failing or what I am doing wrong. Any pointer would be much appreciated. Thanks.

1 0

how to start dtmf timeout countdown after last digit in javascript
by Shabbir abbasi 09 Dec '15

09 Dec '15

i am trying to make an javascripot ivr and collecting user input , but during collection session.collectInput( mycb, dtmf, timeout ); gets timeout and returns function mycb( session, type, obj, arg ) { try { if ( type == "dtmf" ) { console_log( "info", "digit: "+obj.digit+"\n" ); if ( obj.digit == "#" ) { console_log( "info", "detected pound sign.\n" ); exit = true; return( false ); } dtmf.digits += obj.digit; if ( dtmf.digits.length >= digitmaxlength ) { exit = true; return( false ); } } } catch (e) { console_log( "err", e+"\n" ); } return( true ); } //end function collect_user_input i want that timeout gets started countdown after last digit pressed how to solve this ?

3 3

git clone returning 400
by Shabbir abbasi 09 Dec '15

09 Dec '15

i am trying a pull request , i have enabled public access, i have read instructions here https://freeswitch.org/confluence/display/FREESWITCH/Pull+Requests but whe i tried git clone https://shabbirabbasi92@stash.freeswitch.org/scm/shabbirabbasi92/freeswitch… Cloning into 'freeswitch'... fatal: unable to access ' https://shabbirabbasi92@stash.freeswitch.org/scm/shabbirabbasi92/freeswitch…': The requested URL returned error: 400

2 3

The FreeSWITCH project and Static Analysis
by Ken Rice 09 Dec '15

09 Dec '15

New Post on freeswitch.org from Kathleen King check it out at http://ift.tt/1R7Yh7U The FreeSWITCH project and Static Analysis The FreeSWITCH project is nearly ten years old, and the FreeSWITCH git repo has commits from about 214 different authors and over 3.2 million lines of code with 875k of those lines under the src directory. Some of the maintenance challenges associated with such a large software project include: detecting and resolving human errors such as typos, logic inversions, and dangerous formatting. Implementing code review is a must, and there are different techniques common to the industry used to reduce the defect density and standardize the code format: autobuilding against multiple compilers, routine testing, and static code analysis. The core development team at FreeSWITCH uses all three techniques. Both autobuilding and routine testing can be applied with in-house system workflows. Routinely building the packages against different compilers allows for consistent tracking to make sure additional commits won’t break existing code in any of the prepackaged builds. This also allows for consistent handling of packages for multiple operating systems. By autobuilding against different compilers, we can make sure that a commit for one set of packages doesn’t break the builds for the others. Routine testing is another viable option for code review, and routinely testing and implementing a bug tracking system allows the community members to report bugs found in unique environmental circumstances. Open-source software relies on many different eyes to keep bugs shallow, and this practice opens up different configurations and applications of the software for a more thorough testing. Each year hundreds of tickets are opened on the FreeSWITCH project JIRA, and the developers work tirelessly to address all of them. Static analyzers can scan thousands to millions of lines of code without getting tired and usually don’t require many manual steps to run. The relationship between a project’s developers and the creators of a static code analyzer can be a symbiotic one. The analyzer works by using a database of multiple tiers of positive and negative heuristics. First, it runs the low cost patterns against the entire code base to generate a large list of possible issues, then runs more accurate and higher cost patterns against the bug candidates to reduce the number of false positives, and finally evaluates the severity and more accurately classifies the issues. Once the analyzer has completed its run, it requires an experienced software developer familiar with the code base to review each issue reported. Most static analyzers are built to report possible candidates in the first pass, and thus immature analyzers are perceived to red flag everything. They tend to create a lot of noise by reporting a large number of false positives and misclassifying the severity of issues. After the developers for the software being analyzed have reviewed the results of the analysis, they can give specific examples of why they determined it to be a false positive which can be used to improve the static analyzer’s heuristics. As the database matures, the quality of the negative heuristics improves and reduces the volume of false positives. The advantage here is that each report triaged leads to a commit resolving a bug or an improvement to the analyzer. The team over at Program Verification Systems have built a static analyzer for C/C++ code that integrates into Microsoft Visual Studio. According to their website, the program allows the user to scan of lines of code to locate various typos and other errors. Their analyzer supports C/C++, C++/CLI, and C++/CX with support for C# language coming soon. The PVS-Studio is also available as a standalone utility through the distribution packages which allows for viewing the analysis logs on a machine without Visual Studio. It can also be used to track multiple sub-builds and analyze non-standard build systems. The reports for the open-source projects that have been analyzed with this software can be found on their website in the Checked Projects section. The FreeSWITCH team ran the open-source FreeSWITCH project through the PVS analyzer. A decent majority of the issues reviewed were determined to be minor Windows-specific bugs not previously flagged by compilers currently implemented by the team. The team is continuing to review and resolve the alerts from the analysis and have integrated this analyzer into the code review workflow. They look forward to continuing this symbiotic relationship with the goal of improving the quality of software. If you would like to replicate the results you can use the following steps. Set up an instance of Microsoft Windows 10, install Microsoft Visual Studio 2015, and install the analyzer from the http://ift.tt/1R7WpMh website. Create a new FreeSWITCH project. Clone the FreeSWITCH repo into your project. Open the FreeSWITCH project. Set the debug to ‘x64’ if not already set. Click the PVS studio drop down box and select “check solution” to run the analyzer. Settle in and wait for the results.

2 1

FreeSWITCH Week in Review (Master Branch) November 28th – December 5th
by Ken Rice 08 Dec '15

08 Dec '15

New Post on freeswitch.org from Kathleen King check it out at http://ift.tt/1IS2zbI FreeSWITCH Week in Review (Master Branch) November 28th – December 5th Our features this week include: improvements to the auto bitrate features in mod_conference, the addition of the Debian install script for the verto communicator, and separate controls for gain and volume for verto. Join us Wednesdays at 12:00 CT for some more FreeSWITCH fun! This week we have Tsahi Levent-Levi talking about WebRTC! And head over to freeswitch.com to learn more about FreeSWITCH support. New features that were added: FS-8595 [mod_conference] Improve auto bitrate in personal canvas mode and do not let auto bitrate exceed native picture size Improvements in build system, cross platform support, and packaging: FS-8614 [verto_communicator] Add Debian developers install script and update README.md to reference it The following bugs were squashed: FS-8585 [mod_commands] Expanded {} and <> to [] for each dial string in group_call to allow for multiple device registrations for the same user FS-8589 [mod_conference] Fixed using conference playback with full-screen=true not working correctly FS-8354 [mod_conference] Fixed G722 audio issues with mod_conference caused by previous commit fab43547 FS-8602 [mod_conference] Fixed conference not auto-generating layouts properly when callers with no camera are present FS-8615 [mod_conference] Fixed a crash when quickly changing layouts and setting reservation ids FS-8588 [mod_httapi] Fixed a crash found while fixing unreliable digit collection FS-8599 [verto] Removed a workaround for Mozilla that is no longer needed for video size FS-8590 [verto_communicator] Fixed sending malformed vid-res-id command when changing layouts by treating no res-id the same as clear FS-8612 [core] Fixed a rare IVR originated calls crash due to read codec leak FS-8619 [mod_rayo] Reply with conflict stanza error if bind is attempted with duplicate JID. Improve error handling when ‘ready’ callback fails. The FreeSWITCH 1.4 branch had a couple of bug fixes back ported. And again, keep in mind that 1.4 is quickly moving toward end of life and won’t be supported any longer except for high level security issues. The following bugs were squashed: FS-8582 [mod_httapi] Fixed a crashed caused by null URL being passed

1 0

Connect the FXS gateway and Freeswitch in local network
by Ismir Saljic 07 Dec '15

07 Dec '15

Hi all, I am new to Freeswitch and I am trying to connect FXS gateway with Freeswitch. As both devices are on the same LAN I assume that I need to use internal profile. For now I need only to make outbound calls to the gateway. I've tried to send calls to the IP address of the gateway without registration but it's not working. This is my config from dialplan/default/00_name file: <include> <extension name="To PSTN"> <condition field="destination_number" expression="^0111(\d+)$"> <action application="bridge" data="sofia/internal/$1@X.X.X.X:5060" /> </condition> </extension> </include> Is it necessary to register gateway on freeswitch in order to make it working or it is also possible to send calls to IP address of the gateway? Gateway has static IP address. Any help would be appreciated! Thank you Salja

3 5