January 2016 - FreeSWITCH-users - FreeSWITCH Mailing Lists

Installation failed Debian : SETSCHEDULER
by pgoergler＠gmail.com 29 Oct '21

29 Oct '21

Hello, I try to install Freeswitch on a proxmox container with debian 8, following https://freeswitch.org/confluence/display/FREESWITCH/FreeSWITCH+1.6+Video But it does not work Here what i did: # cat /etc/debian_version 8.2 # cat /etc/apt/sources.list.d/99FreeSWITCH.test.list deb http://files.freeswitch.org/repo/deb/freeswitch-1.6/ jessie main # apt-get update [...] Hit http://files.freeswitch.org jessie InRelease Hit http://files.freeswitch.org jessie/main amd64 Packages Ign http://files.freeswitch.org jessie/main Translation-en Fetched 367 B in 1s (279 B/s) Reading package lists... Done Now i follow the document and install freeswitch-all # apt-get install freeswitch-all [...] Job for freeswitch.service failed. See 'systemctl status freeswitch.service' and 'journalctl -xn' for details. invoke-rc.d: initscript freeswitch, action "start" failed. dpkg: error processing package freeswitch-all (--configure): subprocess installed post-installation script returned error exit status 1 Setting up libmtp-runtime (1.1.8-1+b1) ... Setting up va-driver-all:amd64 (1.4.1-1) ... Processing triggers for libc-bin (2.19-18+deb8u1) ... Processing triggers for systemd (215-17+deb8u2) ... Processing triggers for python-support (1.0.15) ... Errors were encountered while processing: freeswitch-all E: Sub-process /usr/bin/dpkg returned an error code (1) # tail /var/log/syslog Nov 17 16:50:15 freeswitch systemd[20020]: Failed at step SETSCHEDULER spawning /usr/bin/freeswitch: Operation not permitted Nov 17 16:50:15 freeswitch systemd[1]: freeswitch.service: control process exited, code=exited status=214 Nov 17 16:50:15 freeswitch systemd[1]: Failed to start freeswitch. Nov 17 16:50:15 freeswitch systemd[1]: Unit freeswitch.service entered failed state. Nov 17 16:50:15 freeswitch systemd[1]: freeswitch.service holdoff time over, scheduling restart. Nov 17 16:50:15 freeswitch systemd[1]: Stopping freeswitch... Nov 17 16:50:15 freeswitch systemd[1]: Starting freeswitch... Nov 17 16:50:15 freeswitch systemd[1]: freeswitch.service start request repeated too quickly, refusing to start. Nov 17 16:50:15 freeswitch systemd[1]: Failed to start freeswitch. Nov 17 16:50:15 freeswitch systemd[1]: Unit freeswitch.service entered failed state. Ok the document said it could happen, i have to replace /lib/systemd/system/freeswitch.service I did it # cat /lib/systemd/system/freeswitch.service [Unit] Description=freeswitch After=syslog.target network.target local-fs.target [Service] ; service Type=forking PIDFile=/run/freeswitch/freeswitch.pid PermissionsStartOnly=true ExecStart=/usr/bin/freeswitch -u freeswitch -g freeswitch -ncwait -nonat -rp TimeoutSec=45s Restart=on-failure ; exec WorkingDirectory=/usr/bin User=root Group=daemon LimitCORE=infinity LimitNOFILE=100000 LimitNPROC=60000 ;LimitSTACK=240 LimitRTPRIO=infinity LimitRTTIME=7000000 IOSchedulingClass=realtime IOSchedulingPriority=2 CPUSchedulingPolicy=rr CPUSchedulingPriority=89 UMask=0007 [Install] WantedBy=multi-user.target # systemctl daemon-reload && systemctl start freeswitch Job for freeswitch.service failed. See 'systemctl status freeswitch.service' and 'journalctl -xn' for details. Hum still not working # systemctl status freeswitch.service * freeswitch.service - freeswitch Loaded: loaded (/lib/systemd/system/freeswitch.service; disabled) Active: failed (Result: start-limit) since Tue 2015-11-17 16:52:08 CET; 15s ago Process: 20069 ExecStart=/usr/bin/freeswitch -u freeswitch -g freeswitch -ncwait -nonat -rp (code=exited, status=214/SETSCHEDULER) Nov 17 16:52:07 freeswitch systemd[1]: Failed to start freeswitch. Nov 17 16:52:07 freeswitch systemd[1]: Unit freeswitch.service entered failed state. Nov 17 16:52:08 freeswitch systemd[1]: freeswitch.service holdoff time over, scheduling restart. Nov 17 16:52:08 freeswitch systemd[1]: Stopping freeswitch... Nov 17 16:52:08 freeswitch systemd[1]: Starting freeswitch... Nov 17 16:52:08 freeswitch systemd[1]: freeswitch.service start request repeated too quickly, refusing to start. Nov 17 16:52:08 freeswitch systemd[1]: Failed to start freeswitch. Nov 17 16:52:08 freeswitch systemd[1]: Unit freeswitch.service entered failed state. And with the same error: # tail /var/log/syslog Nov 17 16:52:07 freeswitch systemd[20069]: Failed at step SETSCHEDULER spawning /usr/bin/freeswitch: Operation not permitted Nov 17 16:52:07 freeswitch systemd[1]: freeswitch.service: control process exited, code=exited status=214 Nov 17 16:52:07 freeswitch systemd[1]: Failed to start freeswitch. Nov 17 16:52:07 freeswitch systemd[1]: Unit freeswitch.service entered failed state. Nov 17 16:52:08 freeswitch systemd[1]: freeswitch.service holdoff time over, scheduling restart. Nov 17 16:52:08 freeswitch systemd[1]: Stopping freeswitch... Nov 17 16:52:08 freeswitch systemd[1]: Starting freeswitch... Nov 17 16:52:08 freeswitch systemd[1]: freeswitch.service start request repeated too quickly, refusing to start. Nov 17 16:52:08 freeswitch systemd[1]: Failed to start freeswitch. Nov 17 16:52:08 freeswitch systemd[1]: Unit freeswitch.service entered failed state. What can i do to make it start correctly ? Thanks, --

4 3

Faxing with FreeSWITCH
by bruce＠sqls.net 16 Mar '21

16 Mar '21

Hello! I'm working on setting up a FreeSWITCH/Flowroute fax server. The server is connected without any nat on a 20MB fiber internet connection. I've built some lua scripts that allow me to receive and send faxes and log all the faxes to a sqlite database. I even have a management script that can be called from the fs_cli to add fax2email routes and adjust settings. It's still a pretty rough implementation but overall it's working fairly well but I have two main questions that I hope someone could help me with. 1) I would like to detect "voice calls" or maybe I want to detect fax calls? There's a dialplan function to listen for and detect a fax caller but I'm having trouble implementing it in my lua script. It seems it's a non-blocking function, maybe? Because it just walks right over that line instead of waiting and listening for any fax tones. I thought it would block the script for x seconds and listen for a fax tone and return a result based on what it found. Can someone help me accomplish something similar to that? 2) So far, by far... my most common error is "The call dropped prematurely". I'm not sure how to start debugging the error to figure out what's causing it and how (if I can) solve it. I do have pcap's of the calls from pcapsipdump and I also have the freeswitch log of each call (my lua script pulls and saves that for each fax call). I've opened the pcap files up in wireshark but I don't know what I'm looking for and I think that might be over my head at the moment. Can anyone give me any help on what this error is normally caused by or what I could look for and/or test? Here are a couple of example logs that ended with "The call dropped prematurely". http://bmts.us/faxlogs/FAX-2e913a50-3a4f-4abc-9882-a323a97e5138.log http://bmts.us/faxlogs/FAX-59d02d9d-c4ba-44c2-8edd-a1c9142c7c1c.log

6 11

Cron-like execution in FS
by Matthew Fong 10 Feb '21

10 Feb '21

I'm wondering if there's any features that allow the cron-like execution of code inside of Freeswitch, preferably with lua--or if I am stuck using the api interface and running the cron outside of freeswitch. --matt

5 5

answer command
by Maxim Tsvetov 21 Sep '20

21 Sep '20

Hello, I found in WIKI list of supported commands http://wiki.freeswitch.org/wiki/Mod_commands. I need command "answer" but it doesn't exist (Freeswitch 1.04, Win32) That's what Freeswitch replies for this command: "answer: Command not found!" Сould you please help? Regards, Maxim Tsvetov

11 26

mod_portaudio on Raspberry Pi currently broken?
by Lesley Pervis 27 Jul '20

27 Jul '20

I compiled mod_portaudio for rpi (arm11) in January. No problem. I compiled it again this week. Problem. Logs show it can't find any devices. So I copy the mod_portaudio.so and mod_portaudio_la from January to the newly compiled installation, and voila, devices found. I did a git diff in src/mod/endpoints/mod_portaudio, and there have been a couple of changes in the mod_portaudio.c file, but nothing that would explain this. Mod-portaudio source doesn't seem to have changed, just the way it's build. (Still version 1899, V19-devel.) The newer mod_portaudio.la shows different dependences, and the new mod_portaudio.so is much smaller. I think mod_portaudio is currently broken for raspberry pi and likely other platforms too. Anyone have any insight?

6 18

mod call center tier behaviour
by abubacker 04 May '20

04 May '20

I am working in mod_callcenter Before my call center configuration is like this /referene : callcenter.conf.xml/ /<agents> <agent name="1000@default" type="callback" contact="[call_timeout=10]user/1000" status="Available" max-no-answer="0" wrap-up-time="0" reject-delay-time="1" busy-delay-time="1" /> <agent name="1001@default" type="callback" contact="[call_timeout=10]user/1001" status="Available" max-no-answer="0" wrap-up-time="0" reject-delay-time="1" busy-delay-time="1" /> <agent name="1003@default" type="callback" contact="[call_timeout=10]user/1006" status="Available" max-no-answer="0" wrap-up-time="0" reject-delay-time="1" busy-delay-time="1" /> </agents> <tiers>  <tier agent="1000@default" queue="support@default" level="1" position="1"/> <tier agent="1001@default" queue="support@default" level="1" position="2"/> <tier agent="1003@default" queue="support@default" level="1" position="3"/>  <tier agent="1003@default" queue="secondary" level="1" position="3"/> <tier agent="1001@default" queue="secondary" level="1" position="2"/> <tier agent="1000@default" queue="secondary" level="1" position="1"/> </tiers> </configuration> / Tier list : /freeswitch@FMS-Queue> callcenter_config tier list support@default queue|agent|state|level|position support@default|1000@default|Ready|1|1 support@default|1001@default|Ready|1|2 support@default|1003@default|Ready|1|3 +OK/ When I renamed the 1003@default as 1006@default / <agents> <agent name="1000@default" type="callback" contact="[call_timeout=10]user/1000" status="Available" max-no-answer="0" wrap-up-time="0" reject-delay-time="1" busy-delay-time="1" /> <agent name="1001@default" type="callback" contact="[call_timeout=10]user/1001" status="Available" max-no-answer="0" wrap-up-time="0" reject-delay-time="1" busy-delay-time="1" /> <agent name="1006@default" type="callback" contact="[call_timeout=10]user/1006" status="Available" max-no-answer="0" wrap-up-time="0" reject-delay-time="1" busy-delay-time="1" /> </agents> <tiers>  <tier agent="1000@default" queue="support@default" level="1" position="1"/> <tier agent="1001@default" queue="support@default" level="1" position="2"/> <tier agent="1006@default" queue="support@default" level="1" position="3"/>  <tier agent="1006@default" queue="secondary" level="1" position="3"/> <tier agent="1001@default" queue="secondary" level="1" position="2"/> <tier agent="1000@default" queue="secondary" level="1" position="1"/> </tiers>/ After that I have reload the mod_callcenter http://pastebin.freeswitch.org/14810 The 1003@default is not overwritten , but 1006@default has added newly why 1003@default is still exist /freeswitch@FMS-Queue> callcenter_config tier list support@default queue|agent|state|level|position support@default|1000@default|Ready|1|1 support@default|1001@default|Ready|1|2 support@default|1003@default|Ready|1|3 support@default|1006@default|Ready|1|3 +OK/ Is it a bug or Is it a default behaviour ? -- Best regards, N.Abubacker , Associate system engineer , bk systems pvt ltd , Ph : 9144-43902701 Disclaimer:http://www.bksystems.co.in/email-policy

2 1

dynamic music on hold for mod_conference
by Lappe, Adam 19 Mar '20

19 Mar '20

Hi all, i am trying to dynamically set the mod-sound variable in mod_conference, so I can play different music on hold to my conference rooms without having to create multiple profiles. Is there a way to set my moh-sound path while I create the conference? Or can I change the moh-sound file via the event socket in a existing conference? I think this would also lead to success. Thanks in advance, Adam

5 6

New Debian FS vanilla install fails
by Sean Devoy 04 Mar '20

04 Mar '20

HI all, I have a new Debian 8.1 (32 bit) server for testing. I first did an apt-get install curl then per the instructions here: https://freeswitch.org/confluence/display/FREESWITCH/Debian+7 I did this: echo "deb http://files.freeswitch.org/repo/deb/debian/ `lsb_release -sc` main" >> /etc/apt/sources.list.d/freeswitch.list curl http://files.freeswitch.org/repo/deb/debian/freeswitch_archive_g0.pub | apt-key add - apt-get update apt-get install freeswitch-meta-vanilla It runs for less than a minute and dies at: Setting up freeswitch-sysvinit (1.4.19~10~1-1~jessie+1) ... Job for freeswitch.service failed. See 'systemctl status freeswitch.service' and 'journalctl -xn' for details. invoke-rc.d: initscript freeswitch, action "start" failed. dpkg: error processing package freeswitch-sysvinit (--configure): subprocess installed post-installation script returned error exit status 1 Setting up freeswitch-systemd (1.4.19~10~1-1~jessie+1) ... dpkg: dependency problems prevent configuration of freeswitch-init: freeswitch-init depends on freeswitch-sysvinit (= 1.4.19~10~1-1~jessie+1); however: Package freeswitch-sysvinit is not configured yet. dpkg: error processing package freeswitch-init (--configure): dependency problems - leaving unconfigured and ends shortly with: Errors were encountered while processing: freeswitch-sysvinit freeswitch-init E: Sub-process /usr/bin/dpkg returned an error code (1) I ran the cmds it says: systemctl status -l freeswitch.service * freeswitch.service - freeswitch Loaded: loaded (/lib/systemd/system/freeswitch.service; disabled) Active: failed (Result: start-limit) since Wed 2015-06-17 17:11:15 EDT; 18min ago Jun 17 17:11:15 fstest.devoy.us systemd[1]: freeswitch.service: control process exited, code=exited status=1 Jun 17 17:11:15 fstest.devoy.us systemd[1]: Failed to start freeswitch. Jun 17 17:11:15 fstest.devoy.us systemd[1]: Unit freeswitch.service entered failed state. Jun 17 17:11:15 fstest.devoy.us systemd[1]: freeswitch.service start request repeated too quickly, refusing to start. Jun 17 17:11:15 fstest.devoy.us systemd[1]: Failed to start freeswitch. Jun 17 17:11:15 fstest.devoy.us systemd[1]: Unit freeswitch.service entered failed state. journalctl -xn -- Logs begin at Wed 2015-06-17 16:59:45 EDT, end at Wed 2015-06-17 17:17:01 EDT. -- Jun 17 17:11:15 fstest.devoy.us systemd[1]: freeswitch.service: control process exited, code=exited status=1 Jun 17 17:11:15 fstest.devoy.us systemd[1]: Failed to start freeswitch. -- Subject: Unit freeswitch.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit freeswitch.service has failed. -- -- The result is failed. Jun 17 17:11:15 fstest.devoy.us systemd[1]: Unit freeswitch.service entered failed state. Jun 17 17:11:15 fstest.devoy.us systemd[1]: freeswitch.service start request repeated too quickly, refusing to start. Jun 17 17:11:15 fstest.devoy.us systemd[1]: Failed to start freeswitch. -- Subject: Unit freeswitch.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit freeswitch.service has failed. -- -- The result is failed. Jun 17 17:11:15 fstest.devoy.us systemd[1]: Unit freeswitch.service entered failed state. Jun 17 17:11:54 fstest.devoy.us kernel: perf interrupt took too long (10077 > 10000), lowering kernel.perf_event_max_sample_rate to 12500 Jun 17 17:17:01 fstest.devoy.us CRON[12430]: pam_unix(cron:session): session opened for user root by (uid=0) Jun 17 17:17:01 fstest.devoy.us CRON[12431]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Jun 17 17:17:01 fstest.devoy.us CRON[12430]: pam_unix(cron:session): session closed for user root Did I misunderstand that Debian 8 was OK, in fact required at 1.6.n? What am I missing? Sean

5 7

Stumped by mod_portaudio permissions issue
by Mark Haun 02 Feb '20

02 Feb '20

I built freeswitch version 1.7.0+git~20150730T192909Z~ab7f83c654~32bit for my ARM-based home server (an NVIDIA Jetson board), with the intention of using mod_portaudio with a wireless USB headset for my main home phone. It works well when running freeswitch directly as root, but when I configured freeswitch to run at system startup, mod_portaudio could no longer find any audio devices. No problem, I thought, it's a simple permissions issue. I am using the example debian init script from the wiki (this is a Jessie install with SysV init rather than systemd). It runs freeswitch as user freeswitch, group daemon using the -u and -g command-line options. So I added "freeswitch" to the audio group, then used sudo to verify that I could play sound files with "aplay" as the freeswitch user. That worked, but it did not solve the mod_portaudio failure. Thinking there must be an issue with portaudio separate from ALSA, I fetched and built the "pa_devs" utility which enumerates and prints the available audio devices. (This is basically what mod_portaudio is doing on startup.) Running as the freeswitch user, that worked too. Hmmmm. I tried running freeswitch from the command line using sudo rather than the -u and -g options, i.e. $ sudo freeswitch /usr/local/freeswitch/bin/freeswitch -nc and that worked as well! Then I started experimenting with -u and -g and discovered that $ /usr/local/freeswitch/bin/freeswitch -nc -u freeswitch allows mod_portaudio to load correctly, whereas $ /usr/local/freeswitch/bin/freeswitch -nc -u freeswitch -g daemon causes mod_portaudio to fail. Can anyone explain what's happening here? In both cases the process UID, GID, EUID, EGID, FUID, and FGID are the same (freeswitch:daemon) as displayed with "ps xao pid,uid,gid,euid,egid,fuid,fgid". Could this be a bug in freeswitch? There are a couple of threads from 2-3 years ago in the archives, where mod_portaudio permissions issues were never resolved and the solution remained a mystery. For the time being I guess this (not using -g) is a workaround, but I'd sure like to understand what is going on. Mark

5 7

Change SIP Contact header on b-leg
by Кирилл Преслер 22 Feb '19

22 Feb '19

Provider not accepting calls because of "bad" Contact header sip:gw+ss@10.50.244.15:5060;transport=udp;gw=ss ITSP needs sip:username@10.50.244.15:5060, where username should be passed from dialplan for every call and there is no params. I've tried following variables with set and export, but nothing seems to work. sip_contact_user sip_outgoing_contact_uri sip_invite_contact_params

3 2