November 2019 - FreeSWITCH-users - FreeSWITCH Mailing Lists

segfault because of require("ESL") in lua
by Yuriy Nasida 29 Nov '19

29 Nov '19

Hi guys, FS runs my lua script during the call. At the same time this script should run some fs_cli commands at different fs node. I want to invoke ESL from lua to do this. Please advice is it good idea ? Currently FS got segfault because of require("ESL") in lua.

1 0

Local stream
by Abdou khadre NDOYE 28 Nov '19

28 Nov '19

Hi, I have some trouble using mod_local_stream, When I place a file in the right path configured in local_stream.conf.xml file doesn’t played. Sometime I have this error when I use rate 8000 : 2019-11-07 10:53:14.620285 [DEBUG] switch_core_media.c:8494 Audio params are unchanged for sofia/internal/338600485(a)172.16.10.5. 2019-11-07 10:53:14.660286 [DEBUG] switch_ivr.c:625 sofia/internal/315@172.16.10.50:5060 Command Execute playback(local_stream://moh) EXECUTE sofia/internal/315@172.16.10.50:5060 playback(local_stream://moh) 2019-11-07 10:53:14.660286 [DEBUG] switch_core_file.c:389 File moh sample rate 8000 doesn't match requested rate 16000 2019-11-07 10:53:14.660286 [DEBUG] switch_ivr_play_say.c:1497 Codec Activated L16@16000hz 1 channels 20ms 2019-11-07 10:53:14.680286 [NOTICE] switch_core_media.c:15605 Deactivating write resampler My config ; <directory name="moh" path="$${sounds_dir}/music/16000"> <param name="rate" value="16000"/> <param name="shuffle" value="true"/> <param name="channels" value="1"/> <param name="interval" value="20"/> <param name="timer-name" value="soft"/> </directory> I need help. Thank

2 1

Freeswitch 1.8 mod_callcenter get CALL_REJECTED Originate Error
by Chhorm Chhatra 28 Nov '19

28 Nov '19

Hi, Currently, our Freeswitch 1.8 production server, frequently encounters CALL_REJECTED when mod_callcenter tries to originate the call to the agent. *Is there any clue you can suggest to debug this issue?* I am sure that the callee does not reject this call because mod_callcenter > can't even make the call to the agent (Callee). The call would traverse like this: *DID Call via GSM Gateway > Freeswitch > (IVR Call > Callcenter-Queue > Agent)* Any help would be really appreciated. Best regards, Chhorm Chhatra

1 0

Delay in Options Packets
by Jai Rangi 26 Nov '19

26 Nov '19

Hello, Every now and then we see long delay in response for options. Example in the trace below free-switch took 44 seconds before it send 200 OK. What will be best way to troubleshoot this? U 2019/11/25 10:49:27.185325 192.168.1.1:49020 -> 192.168.1.5:5060 OPTIONS sip:100000@192.168.1.5 SIP/2.0. Via: SIP/2.0/UDP 192.168.2.1:49020;branch=z9hG4bKhjhs8ass877. Max-Forwards: 70. To: sip:100000@192.168.1.5. From: sip:1000@192.168.2.1:49020;tag=cbzxq0. Call-ID: hcrtfi(a)192.168.2.1. CSeq: 1 OPTIONS. Accept: application/sdp. Content-Length: 0. . U 2019/11/25 10:49:51.819959 192.168.1.5:5060 -> 192.168.1.1:49020 SIP/2.0 200 OK. Via: SIP/2.0/UDP 192.168.2.1:49020 ;branch=z9hG4bKhjhs8ass877;received=192.168.1.1. From: <sip:1000@192.168.2.1:49020>;tag=cbzxq0. To: <sip:100000@192.168.1.5>;tag=aUUQj55rcetma. Call-ID: hcrtfi(a)192.168.2.1. CSeq: 1 OPTIONS. Contact: <sip:192.168.1.5:5660>. User-Agent: Monitor. Accept: application/sdp. Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE. Supported: 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-Length: 0.

3 3

Re: [Freeswitch-users] call drop because of no write codec, incompatible_destination
by Mike Jerris 26 Nov '19

26 Nov '19

Take a look at log with sip trace enabled but this usually happens when we can’t negotiate codecs. > On Oct 24, 2019, at 10:19 AM, António Silva via FreeSWITCH-users <freeswitch-users(a)lists.freeswitch.org> wrote: > > > From: António Silva <asilva(a)wirelessmundi.com> > Subject: call drop because of no write codec, incompatible_destination > Date: October 24, 2019 at 9:40:00 AM MDT > To: FreeSWITCH Users Help <freeswitch-users(a)lists.freeswitch.org> > > > Hi, > > I'm seeing multiple calls drop with incompatible_destination, i try to call again the same destination and it works fine. it gets me crazy... > > In logs i see the error, "has no write codec", in the capture i see the negotiation both sides have codecs, they are correctly configure in directory. > > what could be causing this? i'm using version 1.8.6 > > > Part of the LOG where the error happens: > > f39e569f-5184-481a-9f67-6185367e2829 2019-10-21 11:50:37.694352 [ALERT] switch_core_state_machine.c:701 sofia/1-perfil-fija/sip:11@131.179.185.131:5112 session thread sleep state: CS_CONSUME_MEDIA! > f39e569f-5184-481a-9f67-6185367e2829 2019-10-21 11:50:41.794408 [ALERT] switch_core_session.c:1130 Send signal sofia/1-perfil-fija/sip:11@131.179.185.131:5112 [BREAK] > f39e569f-5184-481a-9f67-6185367e2829 2019-10-21 11:50:41.794408 [ALERT] switch_core_session.c:1130 Send signal sofia/1-perfil-fija/sip:11@131.179.185.131:5112 [BREAK] > f39e569f-5184-481a-9f67-6185367e2829 2019-10-21 11:50:41.794408 [ALERT] switch_core_state_machine.c:705 sofia/1-perfil-fija/sip:11@131.179.185.131:5112 session thread wake state: CS_CONSUME_MEDIA! > f39e569f-5184-481a-9f67-6185367e2829 2019-10-21 11:50:41.814367 [ALERT] switch_core_media.c:486 Looking for zrtp-hash > f39e569f-5184-481a-9f67-6185367e2829 2019-10-21 11:50:41.814367 [ALERT] switch_core_media.c:439 Deciding whether to pass zrtp-hash between legs > f39e569f-5184-481a-9f67-6185367e2829 2019-10-21 11:50:41.814367 [ALERT] switch_core_media.c:441 CF_ZRTP_PASSTHRU_REQ not set, so not propagating zrtp-hash > f39e569f-5184-481a-9f67-6185367e2829 2019-10-21 11:50:41.834519 [DEBUG] sofia.c:7325 Channel sofia/1-perfil-fija/sip:11@131.179.185.131:5112 entering state [completing][200] > f39e569f-5184-481a-9f67-6185367e2829 2019-10-21 11:50:41.834519 [DEBUG] sofia.c:7335 Remote SDP: > f39e569f-5184-481a-9f67-6185367e2829 v=0 > f39e569f-5184-481a-9f67-6185367e2829 o=11 5008 38 IN IP4 192.168.100.11 > f39e569f-5184-481a-9f67-6185367e2829 s=Mapping > f39e569f-5184-481a-9f67-6185367e2829 c=IN IP4 192.168.100.11 > f39e569f-5184-481a-9f67-6185367e2829 t=0 0 > f39e569f-5184-481a-9f67-6185367e2829 m=audio 5008 RTP/AVP 0 101 > f39e569f-5184-481a-9f67-6185367e2829 a=rtpmap:0 PCMU/8000 > f39e569f-5184-481a-9f67-6185367e2829 a=rtpmap:101 telephone-event/8000 > f39e569f-5184-481a-9f67-6185367e2829 a=fmtp:101 0-16 > f39e569f-5184-481a-9f67-6185367e2829 a=ptime:20 > f39e569f-5184-481a-9f67-6185367e2829 > f39e569f-5184-481a-9f67-6185367e2829 2019-10-21 11:50:41.834519 [NOTICE] sofia.c:7338 Pre-Answer sofia/1-perfil-fija/sip:11@131.179.185.131:5112! > f39e569f-5184-481a-9f67-6185367e2829 2019-10-21 11:50:41.934371 [ALERT] switch_core_session.c:2662 sofia/1-perfil-fija/sip:11@131.179.185.131:5112 Send KeyFrame > f39e569f-5184-481a-9f67-6185367e2829 2019-10-21 11:50:41.934371 [DEBUG] switch_core_session.c:2825 EXECUTE [depth=1] sofia/1-perfil-fija/sip:11@131.179.185.131:5112 lua(execute_on_ring_b.lua) > f39e569f-5184-481a-9f67-6185367e2829 2019-10-21 11:50:41.934371 [ALERT] switch_core_session.c:2889 sofia/1-perfil-fija/sip:11@131.179.185.131:5112 receive message [APPLICATION_EXEC] > f39e569f-5184-481a-9f67-6185367e2829 2019-10-21 11:50:41.934371 [ALERT] switch_core_session.c:1047 Send signal sofia/1-perfil-fija/sip:11@131.179.185.131:5112 [BREAK] > f39e569f-5184-481a-9f67-6185367e2829 2019-10-21 11:50:41.954358 [ALERT] switch_core_session.c:1047 Send signal sofia/1-perfil-fija/sip:11@131.179.185.131:5112 [BREAK] > f39e569f-5184-481a-9f67-6185367e2829 2019-10-21 11:50:41.954358 [ALERT] switch_ivr_originate.c:4136 sofia/1-perfil-fija/sip:11@131.179.185.131:5112 receive message [AUDIO_SYNC] > f39e569f-5184-481a-9f67-6185367e2829 2019-10-21 11:50:42.034370 [DEBUG] switch_cpp.cpp:1187 sofia/1-perfil-fija/sip:11@131.179.185.131:5112 destroy/unlink session from object > f39e569f-5184-481a-9f67-6185367e2829 2019-10-21 11:50:42.034370 [ALERT] switch_core_session.c:2905 sofia/1-perfil-fija/sip:11@131.179.185.131:5112 receive message [APPLICATION_EXEC_COMPLETE] > f39e569f-5184-481a-9f67-6185367e2829 2019-10-21 11:50:42.034370 [DEBUG] switch_channel.c:3537 (sofia/1-perfil-fija/sip:11@131.179.185.131:5112) Callstate Change RINGING -> EARLY > f39e569f-5184-481a-9f67-6185367e2829 2019-10-21 11:50:42.094512 [ALERT] sofia.c:7338 sofia/1-perfil-fija/sip:11@131.179.185.131:5112 receive message [PROGRESS_EVENT] > f39e569f-5184-481a-9f67-6185367e2829 2019-10-21 11:50:42.094512 [ALERT] switch_core_media.c:486 Looking for zrtp-hash > f39e569f-5184-481a-9f67-6185367e2829 2019-10-21 11:50:42.094512 [ALERT] switch_core_media.c:439 Deciding whether to pass zrtp-hash between legs > f39e569f-5184-481a-9f67-6185367e2829 2019-10-21 11:50:42.094512 [ALERT] switch_core_media.c:441 CF_ZRTP_PASSTHRU_REQ not set, so not propagating zrtp-hash > f39e569f-5184-481a-9f67-6185367e2829 2019-10-21 11:50:42.094512 [ALERT] switch_ivr_bridge.c:1650 sofia/1-perfil-fija/sip:11@131.179.185.131:5112 receive message [AUDIO_SYNC] > f39e569f-5184-481a-9f67-6185367e2829 2019-10-21 11:50:42.094512 [ALERT] switch_core_state_machine.c:701 sofia/1-perfil-fija/sip:11@131.179.185.131:5112 session thread sleep state: CS_CONSUME_MEDIA! > f39e569f-5184-481a-9f67-6185367e2829 2019-10-21 11:50:42.094512 [ALERT] switch_ivr_bridge.c:1751 sofia/1-perfil-fija/sip:11@131.179.185.131:5112 receive message [BRIDGE] > f39e569f-5184-481a-9f67-6185367e2829 2019-10-21 11:50:42.094512 [ALERT] switch_core_session.c:981 Send signal sofia/1-perfil-fija/sip:11@131.179.185.131:5112 [BREAK] > f39e569f-5184-481a-9f67-6185367e2829 2019-10-21 11:50:42.094512 [DEBUG] switch_ivr_bridge.c:1795 (sofia/1-perfil-fija/sip:11@131.179.185.131:5112) State Change CS_CONSUME_MEDIA -> CS_EXCHANGE_MEDIA > f39e569f-5184-481a-9f67-6185367e2829 2019-10-21 11:50:42.094512 [ALERT] switch_core_session.c:1480 Send signal sofia/1-perfil-fija/sip:11@131.179.185.131:5112 [BREAK] > f39e569f-5184-481a-9f67-6185367e2829 2019-10-21 11:50:42.114382 [ALERT] switch_core_state_machine.c:705 sofia/1-perfil-fija/sip:11@131.179.185.131:5112 session thread wake state: CS_CONSUME_MEDIA! > f39e569f-5184-481a-9f67-6185367e2829 2019-10-21 11:50:42.114382 [DEBUG] switch_core_state_machine.c:584 (sofia/1-perfil-fija/sip:11@131.179.185.131:5112) Running State Change CS_EXCHANGE_MEDIA (Cur 242 Tot 835614) > f39e569f-5184-481a-9f67-6185367e2829 2019-10-21 11:50:42.114382 [DEBUG] switch_core_state_machine.c:653 (sofia/1-perfil-fija/sip:11@131.179.185.131:5112) State EXCHANGE_MEDIA > f39e569f-5184-481a-9f67-6185367e2829 2019-10-21 11:50:42.114382 [ALERT] switch_core_state_machine.c:653 sofia/1-perfil-fija/sip:11@131.179.185.131:5112 Send KeyFrame > f39e569f-5184-481a-9f67-6185367e2829 2019-10-21 11:50:42.114382 [DEBUG] mod_sofia.c:657 SOFIA EXCHANGE_MEDIA > f39e569f-5184-481a-9f67-6185367e2829 2019-10-21 11:50:42.134357 [ERR] switch_core_media.c:15507 sofia/1-perfil-fija/sip:11@131.179.185.131:5112 has no write codec. > f39e569f-5184-481a-9f67-6185367e2829 2019-10-21 11:50:42.134357 [NOTICE] switch_core_media.c:15508 Hangup sofia/1-perfil-fija/sip:11@131.179.185.131:5112 [CS_EXCHANGE_MEDIA] [INCOMPATIBLE_DESTINATION] > f39e569f-5184-481a-9f67-6185367e2829 2019-10-21 11:50:42.134357 [ALERT] switch_channel.c:3346 Send signal sofia/1-perfil-fija/sip:11@131.179.185.131:5112 [KILL] > f39e569f-5184-481a-9f67-6185367e2829 2019-10-21 11:50:42.134357 [DEBUG] mod_hash.c:297 Usage for total_account:11@clinicalluch.daratel.com is now 0 > f39e569f-5184-481a-9f67-6185367e2829 2019-10-21 11:50:42.134357 [ALERT] switch_core_session.c:1480 Send signal sofia/1-perfil-fija/sip:11@131.179.185.131:5112 [BREAK] > > > > -- > Saludos / Regards / Cumprimentos > António Silva > > > > > _________________________________________________________________________ > > The FreeSWITCH project is sponsored by SignalWire https://signalwire.com > Enhance your FreeSWITCH install with disruptive priced SMS and PSTN services. > Build your next product on our scalable cloud platform. > > Join our online community to chat in real time https://signalwire.community > > Professional FreeSWITCH Services > sales(a)freeswitch.com > https://freeswitch.com > > Official FreeSWITCH Sites > https://freeswitch.com/oss > https://freeswitch.org/confluence > https://cluecon.com > > FreeSWITCH-users mailing list > FreeSWITCH-users(a)lists.freeswitch.org > http://lists.freeswitch.org/mailman/listinfo/freeswitch-users > UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users > https://freeswitch.com

2 2

core.db and postgresql
by David Villasmil 26 Nov '19

26 Nov '19

Hello all, I configured postgres in the core, tables were created, all good. But i just noticed that the sqlite3 files in /var/lib/freeswitch/db/ are still being updated: -rw-r----- 1 freeswitch freeswitch 14336 Jun 3 18:14 /var/lib/freeswitch/db/call_limit.db -rw-r--r-- 1 freeswitch freeswitch 242688 Nov 26 12:13 /var/lib/freeswitch/db/core.db -rw-r--r-- 1 freeswitch freeswitch 4054016 Nov 26 11:10 /var/lib/freeswitch/db/sofia_reg_external.db -rw-rw---- 1 freeswitch freeswitch 33 Nov 26 12:11 /var/lib/freeswitch/db/zrtp.dat Is this right? Isn't the point of using db in the core _not_ to use sqlite? Thanks for your help! David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

2 1

bgsystem call
by Ruslan Shevchenko 26 Nov '19

26 Nov '19

Hi, I try to use 'bgsystem' call from mod_dptools API. With the next two entries in dialplan, I guess, the session should wait until calling party stop call: <action application=“bgsystem” data=” …. “> <action aapplication=“playback” data=“silence_stream://-1 > But looks, like the session, endsed immediately after the process, spawned by bgsystem, finished (and before we receive result). Also, looks like the help page on the wiki (about the possibility to return data from bgsystem: https://freeswitch.org/confluence/display/FREESWITCH/mod_dptools%3A+bgsystem) is incorrect, it is impossible to receive output in channel variable, as I can understand. Is handling session is expected behavior ? Maybe exists some way to handle events from bgprocess ? Thanks,

2 1

FreeSwitch database need help
by Ayoub Ichchou 25 Nov '19

25 Nov '19

Good afternoon, I have been using FreeSwitch for a long time and so far it works like silk. The thing is that now I have engaged in a new adventure with FS, i want to use FS as SBC. For this I want to mount FS with a MySQL database and then form a cluster. I found the problem when I try to mount the database with FS. I am sure that there is a way for FS to generate the database, the necessary tables and fill them with the necessary data to manage FS as SBC, but I cannot find documentation about it. I have the FS books and I have read the confluence wiki. I want FS to generate the necessary database and tables because I don't know how to create the database data for FS to use to make all the SBC functionality. Where can I find the documentation for it? what are the steps to create the database to use FS as SBC? Regards.

2 1

CentOS 7 systemctl start freeswitch
by Abdirahman A. Osman 25 Nov '19

25 Nov '19

Hi, I am using CentOS 7 and tried to start the freeswitch with systemctl start freeswitch. It is working with freeswitch -nc but the systemctl start freeswitch is using the freeswitch:daemon user, a shown below root@localhost bin]# systemctl status freeswitch.service ● freeswitch.service - freeswitch Loaded: loaded (/usr/lib/systemd/system/freeswitch.service; enabled; vendor preset: disabled) Active: failed (Result: start-limit) since Thu 2019-11-21 09:05:16 EST; 8s ago Process: 4251 ExecStart=/usr/bin/freeswitch -u freeswitch -g daemon -ncwait $DAEMON_OPTS (code=exited, status=1/FAILURE) Process: 4249 ExecStartPre=/bin/chown -R freeswitch:daemon /var/run/freeswitch/ (code=exited, status=0/SUCCESS) Process: 4248 ExecStartPre=/bin/mkdir -p /var/run/freeswitch/ (code=exited, status=0/SUCCESS) Nov 21 09:05:16 localhost.localdomain systemd[1]: freeswitch.service: control process exited, code=exited status=1 Nov 21 09:05:16 localhost.localdomain systemd[1]: Failed to start freeswitch. Nov 21 09:05:16 localhost.localdomain systemd[1]: Unit freeswitch.service entered failed state. Nov 21 09:05:16 localhost.localdomain systemd[1]: freeswitch.service failed. Nov 21 09:05:16 localhost.localdomain systemd[1]: freeswitch.service holdoff time over, scheduling restart. Nov 21 09:05:16 localhost.localdomain systemd[1]: Stopped freeswitch. Nov 21 09:05:16 localhost.localdomain systemd[1]: start request repeated too quickly for freeswitch.service Nov 21 09:05:16 localhost.localdomain systemd[1]: Failed to start freeswitch. Nov 21 09:05:16 localhost.localdomain systemd[1]: Unit freeswitch.service entered failed state. Nov 21 09:05:16 localhost.localdomain systemd[1]: freeswitch.service failed. Although permissions of the folders the below folders are set for the user freeswitch drwxr-xr-x 13 freeswitch daemon 4096 Nov 17 15:36 /etc/freeswitch/ drwxr-x--- 2 freeswitch daemon 40 Nov 21 09:05 /var/run/freeswitch/ drwxr-xr-x 13 freeswitch daemon 4096 Nov 17 15:36 /etc/freeswitch/ -rwxr-xr-x. 1 freeswitch daemon 28336 Aug 20 15:08 /usr/bin/freeswitch

3 2

FS firing Curl request for extension transfer
by Shahnawaj Khan 25 Nov '19

25 Nov '19

Hi, I am using mod_xml_curl to fetch dialplan dynamically. On the Basis of condition I need to jump from one extension to another within the same context. my dialplan is similar to the below example. <context name="some_context"> <extension name="some_extention"> <condition field="destination_number" expression="^1010$"> <action application="set" data="auto_hunt=true"/> <action application="answer"/> <action application="transfer" data="Dnis_1"/> </condition> </extension> <extension name="Dnis_1"> <condition field="destination_number" expression="Dnis_1"> <action application="bridge" data="user/1010"/> </condition> </extension> </context> In above case FS is firing curl request for every extension jump within context. Is there any way to jump from one extension to another within same context without firing new request. I don't want to use execute_extension as it return right back to where it was called from. Thanks & Regards, Shahnawaz

2 1