November 2015 - FreeSWITCH-users - FreeSWITCH Mailing Lists

Random calls failing with WRONG_CALL_STATe when using TLS
by Emrah 26 Jan '16

26 Jan '16

Hi all, I am facing a very frustrating issue. I often have to dial twice when using my Yealink phone with TLS because the first attempt times out. The logs on the Yealink indicate that the first invite is successfully received, to which my FS sends a 100 trying and 407 proxy auth required. It is subsequently when my phone sends back the invite that the connection crashes with the following error: SSL ERROR SYSCALL Is this something common? Why does the SSL connection crashes when the phone attempts to send the second invite? My phone is behind NAT. It is going to be a crazy expedition to collect the logs and Pastebin them, so I am tempting my luck on the list first to see if you have any pointers. As a last piece, my Bria on my iPHone, among other clients, never had this issue. I did experience it from time to time with Blink on Mac OS X. Any help appreciated. Emrah

5 12

Re: [Freeswitch-users] Event socket and Python
by Johan Brannlund 17 Jan '16

17 Jan '16

Sami Montour wrote: > Sorry I misunderstood your post about testing with a closed port. > Anyway, I ran your script (port 8041) but didn't get a connection to > FS, different from what you received. Hmm, that's interesting. I guess either I happened to check out a buggy version of FS, there's something strange with my configuration or there's some ARM-specific issue (I run FS on a Raspberry Pi). I'll have to do some more troubleshooting. Thank you for checking! - Johan

4 4

Re: [Freeswitch-users] Make of FreeSWITCH 1.6 on CentOS 7 issue(s) - resolved
by Andrew Keil 07 Jan '16

07 Jan '16

To all, Found what I was missing (and causing all my build issues): rpm -Uvh http://files.freeswitch.org/freeswitch-release-1-6.noarch.rpm Now when I perform the yum install commands and it pulls down the right version and everything works as expected. Here is my procedure (for those who wish to use the manual configure/make approach): Install FreeSWITCH 1.6.0 on CentOS 7 (fresh installation): Note: Everything below is run inside CentOS 7 terminal as "root" user (via "su -" command) 1) Make sure yum update is run and CentOS is up-to-date 2) {optional} inside Terminal window select Edit Profile Preferences and select "Use custom default terminal size" and make it 160 x 60. Close terminal and re-open for the change to take affect. 3) yum -y install git 4) yum -y install epel-release 5) rpm -Uvh http://files.freeswitch.org/freeswitch-release-1-6.noarch.rpm 6) yum -y install git gcc-c++ autoconf automake libtool wget python ncurses-devel zlib-devel libjpeg-devel openssl-devel e2fsprogs-devel sqlite-devel libcurl-devel pcre-devel speex-devel ldns-devel libedit-devel libxml2-devel 7) yum -y install libyuv-devel opus-devel libvpx-devel libvpx2* libdb4* libidn-devel unbound-devel libuuid-devel lua-devel libsndfile-devel 8) cd /usr/local/src 9) git clone -b v1.6 https://freeswitch.org/stash/scm/fs/freeswitch.git 10) cd /usr/local/src/freeswitch 11) ./bootstrap.sh 12) ./configure 13) make 14) make install 15) make cd-sounds-install 16) make cd-moh-install 17) cd /usr/local/freeswitch/conf 18) vi vars.xml Change: <X-PRE-PROCESS cmd="set" data="default_password=1234"/> {!!set it to something different!!} Save and close (<Esc> :wq!) 19) cd /usr/local/freeswitch/conf/sip_profiles 20) mv internal-ipv6.xml internal-ipv6.xml.removed {disables ipv6 support} 21) mv external-ipv6.xml external-ipv6.xml.removed {disables ipv6 support} 22) cd /usr/local/freeswitch/bin 23) ./freeswitch -nonat -nonatmap 24) ... to exit from FreeSWITCH console FreeSWITCH Version: 1.6.0+git~20150903T203652Z~6762f14140~64bit (git 6762f14 2015-09-03 20:36:52Z 64bit) From: freeswitch-users-bounces(a)lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Andrew Keil Sent: Saturday, 19 September 2015 12:06 PM To: FreeSWITCH Users Help <freeswitch-users(a)lists.freeswitch.org> Subject: Re: [Freeswitch-users] Make of FreeSWITCH 1.6 on CentOS 7 issue(s) This worked! However mod_opus fails now. Since I cannot perform a yum install libopus-devel do I need to follow this link: http://files.freeswitch.org/downloads/libs/opus-1.1.tar.gz Getting there! Andrew From: freeswitch-users-bounces(a)lists.freeswitch.org<mailto:freeswitch-users-bounces@lists.freeswitch.org> [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Andrew Keil Sent: Saturday, 19 September 2015 8:46 AM To: FreeSWITCH Users Help <freeswitch-users(a)lists.freeswitch.org<mailto:freeswitch-users@lists.freeswitch.org>> Subject: Re: [Freeswitch-users] Make of FreeSWITCH 1.6 on CentOS 7 issue(s) Thanks I will give this a try. On 19 Sep 2015, at 12:07 AM, Christopher Rienzo <cmrienzo(a)gmail.com<mailto:cmrienzo@gmail.com>> wrote: sudo yum install lua-devel On Fri, Sep 18, 2015 at 1:39 AM, Andrew Keil <andrew.keil(a)visytel.com<mailto:andrew.keil@visytel.com>> wrote: To FreeSWITCH users, I am attempting to make the latest FreeSWITCH release on CentOS 7 (I am trying to avoid the RPM approach since I am also working with Sangoma to assist with their updated merge of freetdm into FreeSWITCH). CentOS 7: CentOS-7-x86_64-DVD-1503-01.iso (with yum update done successfully). As root user: yum install git gcc-c++ autoconf automake libtool wget python ncurses-devel zlib-devel libjpeg-devel openssl-devel e2fsprogs-devel sqlite-devel libcurl-devel pcre-devel speex-devel ldns-devel libedit-devel libxml2-devel {also did the following to see if these will help} yum install libyuv-devel yum install libvpx-devel yum install libidn-devel yum install unbound-devel yum install libdb4* yum install libuuid-devel cd /usr/local/src git clone -b v1.6 https://freeswitch.org/stash/scm/fs/freeswitch.git cd freeswitch ./bootstrap.sh vi modules.conf {comment out mod_fsv (due to libyuv-devel error)} ./configure ./make making all mod_lua make[4]: Entering directory `/usr/local/src/freeswitch/src/mod/languages/mod_lua' CXX mod_lua_la-mod_lua.lo mod_lua.cpp:37:17: fatal error: lua.h: No such file or directory #include "lua.h" The mod_fsv issue I do not care so much about however Lua I need. FYI: I did try the rpm approach on a separate CentOS 7 VM and noticed the Lua dependant package is version 5.1.4 not 5.2. I hope someone has an idea of what to try next. Regards, Andrew Keil _________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting(a)freeswitch.org<mailto:consulting@freeswitch.org> http://www.freeswitchsolutions.com Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com FreeSWITCH-users mailing list FreeSWITCH-users(a)lists.freeswitch.org<mailto: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 _________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting(a)freeswitch.org<mailto:consulting@freeswitch.org> http://www.freeswitchsolutions.com Official FreeSWITCH Sites http://www.freeswitch.org http://confluence.freeswitch.org http://www.cluecon.com FreeSWITCH-users mailing list FreeSWITCH-users(a)lists.freeswitch.org<mailto:FreeSWITCH-users@lists.freeswitch.org> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users<http://lists.freeswitch.org/mailman/options/freeswitch-users> http://www.freeswitch.org

4 10

outbound proxy and port
by Chris B. Ware 05 Jan '16

05 Jan '16

Hi, I need to send registrations and calls from external profile to a si provider, passing through an outbound proxy, port 5080. I I set on sofia: <param name="outbound-proxy" value="10.24.4.151"/> Registrations pass through the OB Proxy, but using, of course, standard 5060 port. I I set on sofia: <param name="outbound-proxy" value="10.24.4.151:5080"/> Param seems to be not understood and registrations go directly to the sip provider. How can I set outbound proxy port? Thanks

7 7

sip simple delivery
by Juan Pablo L. 04 Jan '16

04 Jan '16

Hi, i would like to find out how can i stop a sip simple from being delivered once it has been dealt with, i have a module that receives the event and decides whether to deliver it or not based on some criteria ($$), but it does not matter what the module does, after it has finished precessing the message, freeswitch still delivers it. i understand it does this by default, any advise would be appreciated. thanks!

5 8

Playback is not working
by Vikas Kumar 22 Dec '15

22 Dec '15

Hi All, I am getting this log, but I am not able to hear any sound or audio files are not being played. But logs says : 2015-09-23 10:46:51.722460 [DEBUG] switch_ivr_play_say.c:1305 Codec Activated L16@8000hz 1 channels 20ms 2015-09-23 10:46:55.782300 [DEBUG] switch_ivr_play_say.c:1708 done playing file /usr/local/freeswitch/sounds/en/us/callie/voicemail/vm-too-small.wav 2015-09-23 10:46:55.782300 [DEBUG] switch_ivr.c:191 Codec Activated L16@8000hz 1 channels 20ms 2015-09-23 10:46:55.882377 [DEBUG] switch_ivr_play_say.c:70 No language specified - Using [en] 2015-09-23 10:46:55.882377 [DEBUG] switch_ivr_play_say.c:250 Handle play-file:[voicemail/vm-record_message.wav] (en:en) 2015-09-23 10:46:55.882377 [DEBUG] switch_ivr_play_say.c:1305 Codec Activated L16@8000hz 1 channels 20ms 2015-09-23 10:47:00.482235 [DEBUG] switch_ivr_play_say.c:1708 done playing file /usr/local/freeswitch/sounds/en/us/callie/voicemail/vm-record_message.wav 2015-09-23 10:47:00.482235 [DEBUG] switch_ivr.c:191 Codec Activated L16@8000hz 1 channels 20ms 2015-09-23 10:47:01.602224 [DEBUG] switch_ivr_play_say.c:585 Raw Codec Activated 2015-09-23 10:47:01.602224 [DEBUG] switch_core_codec.c:219 sofia/internal/1012(a)119.9.73.183 Push codec L16:70 2015-09-23 10:47:03.602229 [DEBUG] switch_core_codec.c:244 sofia/internal/1012(a)119.9.73.183 Restore previous codec GSM:3. 2015-09-23 10:47:03.602229 [DEBUG] mod_voicemail.c:1244 Message is less than minimum record length: 3, discarding it. 2015-09-23 10:47:03.602229 [DEBUG] switch_ivr_play_say.c:70 No language specified - Using [en] 2015-09-23 10:47:03.602229 [DEBUG] switch_ivr_play_say.c:250 Handle play-file:[voicemail/vm-too-small.wav] (en:en) 2015-09-23 10:47:03.602229 [DEBUG] switch_ivr_play_say.c:1305 Codec Activated L16@8000hz 1 channels 20ms Did anybody faced this issue??. Please let me know..Its urgent.!!! Thanks vikas Disclaimer :- The information in this e-mail and any attachments is confidential and may be legally privileged. It is intended solely for the addressee or addressees. If you are not an intended recipient, please delete the message and any attachments and notify the sender of misdelivery. Any use or disclosure of the contents of either is unauthorised and may be unlawful. All liability for viruses is excluded to the fullest extent permitted by law. Any views expressed in this message are those of the individual sender, except where the sender states them, with requisite authority, to be those of the specific TIMES GROUP company.

4 6

Debian packages for ARM/MIPS/POWERPC
by Stanislav Sinyagin 17 Dec '15

17 Dec '15

hi, I put together the build scenario that I tested for ARM (armhf at scaleway.com) and it should also work for other architectures: https://freeswitch.org/confluence/display/FREESWITCH/Building+debs+for+othe… It will be great if someone tests them on other architectures too. cheers, stanislav

5 21

mod_gsmopen - deadlock tty
by Luiz Fernando Softov 16 Dec '15

16 Dec '15

Hi, I'm using freeswitch 1.15 in Freebsd 10.1, with mod_gsmopen FreeSWITCH Version 1.5.15b+git~20150407T231134Z~d55c4a053b~64bit (git d55c4a0 2015-04-07 23:11:34Z 64bit), whats happen, its the same with another versions like, 1.6, 1.4.19, etc After sometime running freeswitch, i have this TTYs. crw------- 1 root wheel 0x8e Sep 24 15:30 ttyU1.3 crw------- 1 root wheel 0x8f Sep 24 15:30 ttyU1.3.init crw------- 1 root wheel 0x90 Sep 24 15:30 ttyU1.3.lock crw------- 1 root wheel 0x8e Sep 24 15:30 ttyU2.3 crw------- 1 root wheel 0x8f Sep 24 15:30 ttyU2.3.init crw------- 1 root wheel 0x90 Sep 24 15:30 ttyU2.3.lock crw------- 1 root wheel 0x8e Sep 24 15:30 ttyU3.3 crw------- 1 root wheel 0x8f Sep 24 15:30 ttyU3.3.init crw------- 1 root wheel 0x90 Sep 24 15:30 ttyU3.3.lock crw------- 1 root wheel 0x76 Sep 25 00:46 ttyU4.0 crw------- 1 root wheel 0x77 Sep 24 22:28 ttyU4.0.init crw------- 1 root wheel 0x78 Sep 24 22:28 ttyU4.0.lock crw------- 1 root wheel 0x7c Sep 24 22:28 ttyU4.1 crw------- 1 root wheel 0x7d Sep 24 22:28 ttyU4.1.init crw------- 1 root wheel 0x7e Sep 24 22:28 ttyU4.1.lock crw------- 1 root wheel 0x82 Sep 24 22:28 ttyU4.2 crw------- 1 root wheel 0x83 Sep 24 22:28 ttyU4.2.init crw------- 1 root wheel 0x84 Sep 24 22:28 ttyU4.2.lock crw------- 1 root wheel 0x8e Sep 24 22:28 ttyU4.3 crw------- 1 root wheel 0x8f Sep 24 22:28 ttyU4.3.init crw------- 1 root wheel 0x90 Sep 24 22:28 ttyU4.3.lock crw------- 1 root wheel 0xa8 Sep 25 00:46 ttyU5.0 crw------- 1 root wheel 0xa9 Sep 24 22:28 ttyU5.0.init crw------- 1 root wheel 0xaa Sep 24 22:28 ttyU5.0.lock crw------- 1 root wheel 0xae Sep 24 22:28 ttyU5.1 crw------- 1 root wheel 0xaf Sep 24 22:28 ttyU5.1.init crw------- 1 root wheel 0xb6 Sep 24 22:28 ttyU5.1.lock crw------- 1 root wheel 0xba Sep 24 22:28 ttyU5.2 crw------- 1 root wheel 0xbb Sep 24 22:28 ttyU5.2.init crw------- 1 root wheel 0xbc Sep 24 22:28 ttyU5.2.lock crw------- 1 root wheel 0xc0 Sep 24 22:28 ttyU5.3 crw------- 1 root wheel 0xc1 Sep 24 22:28 ttyU5.3.init crw------- 1 root wheel 0xc2 Sep 24 22:28 ttyU5.3.lock As you can see, ttyU1.3, ttyU2.3, ttyU3.3 are USB deadlocks I try to unload mod_gsmopen, but i receive a message that is in use so i kill freeswitch, then ttyU1.3, ttyU2.3, ttyU3.3, are free and disappear (as well .init and .lock) I try to figure out whats happening, with logs, alarms, but i can't. Someone have the same problem, or know the solution? ps. Reading the list, i realize that few members use the module, or don't have problems. If i am correct, is there any other way to use GSM modems or GSM, which is low cost? Is there anyone who can guide me in some things about the code or tips? ps 2. sorry about my english -- Luiz Fernando Softov http://www.softov.com.br fernando(a)softov.com.br

3 19

Re- FreeSWITCH call billing timers vs. BT SIP billing
by Andrew Keil 15 Dec '15

15 Dec '15

To FreeSWITCH users, I have a question in regard to correct billing of a SIP call within FreeSWITCH (to align with Telco billing), since I have asked this question below of BT (direct to their SIP compliance testing team) and received their response today. Based on the diagram below of a simple SIP call: BT FreeSWITCH | --- INVITE ------> | | <-- 100 Trying --- | | <-- 200 OK ------- | | --- ACK ---------> | | <-- RTP ---------> | | --- BYE ---------> | | <-- 200 OK ------- | In order to best match the BT billing records for call duration (that will be sent to my client for their SIP service) I want to make sure that our timers are correct. In the above diagram shows an inbound call from BT to FreeSWITCH. Which of the below statements are correct (2 out of the 4 should be correct): 1) The answer (or connect) timer should start from when FreeSWITCH sends the "200 OK" to indicate that the call is connected? 2) The answer (or connect) timer should start from when FreeSWITCH receives the ACK message back from BT (after sending the "200 OK" to indicate that the call was connected)? 3) The timer for call duration should end when FreeSWITCH receives the "BYE" message from BT? 4) The timer for call duration should end when FreeSWITCH sends the "200 OK" to BT (after it received the "BYE" message from BT)? If the call was reversed ie. an outbound call made from FreeSWITCH to BT (simply swap BT and FreeSWITCH in the above diagram) Which of the below statements are correct (2 out of the 4 should be correct): 1) The answer (or connect) timer should start from when FreeSWITCH receives the "200 OK" to indicate that the call is connected? 2) The answer (or connect) timer should start from when FreeSWITCH sends the ACK message back to BT (after receiving the "200 OK" to indicate that the call was connected)? 3) The timer for call duration should end when FreeSWITCH sends the "BYE" message to BT? 4) The timer for call duration should end when FreeSWITCH receives the "200 OK" from BT (after it sent the "BYE" message to BT)? BT's response: ... Out of the first 4 statements, numbers 2 and 3 are closest. After BT sends the ACK the call timer will start, it will then stop again when BT sends the BYE. Out of the second 4 statements, numbers 2 and 3 are closest. After BT receives the ACK the call timer will start, it will then stop again after BT receives the BYE. ... Therefore, when looking at FreeSWITCH this becomes more interesting, if I base BT's response to be true and correct. Since currently the events generated at the end of a call CHANNEL_HANGUP and CHANNEL_HANGUP_COMPLETE, which align as follows: CHANNEL_HANGUP when BYE received or sent CHANNEL_HANGUP_COMPLETE when 200 OK sent or received Which brings me to my actual question: Since billing timing is done from the point of call connect (or when the ACK is received or sent after the 200 OK) to the point of receiving the BYE message (or sending it, depending on the direction of the call) then why does FreeSWITCH return all the billing variables inside the CHANNEL_HANGUP_COMPLETE based on call timer ending when CHANNEL_HANGUP_COMPLETE is generated and not based on when CHANNEL_HANGUP is generated? Here is a snipet of the CHANNEL_HANGUP_COMPLETE variables: variable_duration:14 variable_billsec:14 ... variable_billmsec:14041 ... variable_billusec:14041103 ... variable_answerusec:58543 In order to test this, I delayed a Lua script after HUNGUP (or CHANNEL_HANGUP event) was detected (for about 10 seconds) prior to ending the Lua script. I know this is not recommended, however it is just to explain this case. As you can see the call duration and all the billing variables show the time up to CHANNEL_HANGUP_COMPLETE not CHANNEL_HANGUP. However, the interesting variable is: variable_answerusec, which seems correct up to CHANNEL_HANGUP. I would appreciate any comments regarding this since obviously I would like the call durations on FreeSWITCH to match BT. If BT are not correct with their timer points, then I am happy to go back to them with some evidence to dispute their claims. Regards, Andrew Keil

3 4

High syscall percentage on Centos 7
by Denys D 11 Dec '15

11 Dec '15

Hi! Has anybody faced with high system calls on Centos 7 while running FreeSwitch? We have migrated from FS 1.2.23 on Centos 5.11 to FS 1.6.2 on Centos 7 and faced with very high syscall (up to 60% CPU time) rate under moderate load (300 CPS, 1500 simultaneous calls). We also faced the same issue on Centos 6.7 and Debian 8.2 with FS 1.6.2 on the same hardware. On Centos 5.11 with the same load and h/w we had no more than 10% syscalls CPU time. We have already tried nohz=off kernel option and it didn't solve the problem. What should we change in our environment to achieve the same performance level as it was on Centos 5.11?

7 8