April 2021 - FreeSWITCH-users - FreeSWITCH Mailing Lists

RE - Internal Interface suddenly freezes
by Kakiman Expert 11 Apr '22

11 Apr '22

hello Did you find any solution to this issue ? I am in production with 1.10.5 version and since a week, I have the same issue. The internal profile is out of service and registration is impossible. and we don't have any answer to "sofia status profile internal" , the prompt in fs_cli keeps waiting. the only way to solve is to restart freeswitch thanks regards

11 18

Issue with Enterprise originate and 487 "ORIGINATOR_CANCEL".
by Jai Rangi 14 Jan '22

14 Jan '22

All, Running into a small issue with group calling, when the original caller hang up, phones dont show that call as missed call, cause of wrong reason code from freeswitch. Scenario: - Caller -> FS (Groupcall) to 101 and 102 - Phones ring - Caller hangup - Phones should see missed calls, - But free-switch send cancel with Reason: SIP;cause=200;text="Call completed elsewhere", where is should send Reason: SIP;cause=487;text="ORIGINATOR_CANCEL". Here is what my bridge data. bridge(<all_threads=true,absolute_codec_string=PCMU,PCMA,G729,group_confirm_file=playback /usr/local/freeswitch/sound/ivr/1443458342.wav,group_confirm_key=exec>{sip_cid_type=rpid,ignore_early_media=true,originate_timeout=30}[leg_timeout=20 ]user/101@192.168.5.50:_:[ignore_early_media=true,leg_timeout=20 ]user/ 102(a)192.168.5.50) If I send bridge(<all_threads=true,absolute_codec_string=PCMU,PCMA,G729,group_confirm_file=playback /usr/local/freeswitch/sound/ivr/1443458342.wav,group_confirm_key=exec>{sip_cid_type=rpid,ignore_early_media=true,originate_timeout=30}[leg_timeout=20 ]user/101(a)192.168.5.50 Everything works fine. I see some old posts but no resolution. Freeswitch version on Debian 8.9 FreeSWITCH (Version 1.6.16 git 3da6bd0 2017-04-07 16:49:13Z 64bit) Any idea or suggestion for workaround? Jai

8 12

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

Internal Interface suddenly freezes
by Stefan Kainz 22 Oct '21

22 Oct '21

Hi everbody, I have a little bit of a problem. Im using Version 1.10.3. ( but this problem also occurs on version 1.4.18 ) Sometimes the internal Sofia interface just stops responding to SIP Requests. It sometimes happens once every day, and sometimes once a week. It happens at completely random times, like one day in the morning, and the next day in the middle of the night. The freeswitch.log gives me nothing, its like the Sofia interface was stopped. When I try to restart the interface with "sofia profile internal restart” nothing happens. The fs_cli just remains stuck with that command. The solution is to restart the freeswitch service. Sometimes when I recognise it too late, for example in the middle of the night, it seems like the problem solves itself after about 2 hours. The profile just starts working again, without somebody doing anything. I have checked a variety of things, including the firewall & fail2ban, network connection, made sure watchdog is disabled, and also tested it on different Debian-versions and freeswitch versions. It seems this problem occurs on every freeswitch version i have tested. The external-profile on the other hand, keeps working like nothing happened. Both Interfaces listen on the same network-device with a public ip. The only difference is, the internal profile uses a Lua file to handle registrations. Has anybody come across anything similar? Any help is much appreciated! Regards,

7 21

Re: [Freeswitch-users] rtp-timeout-sec VS media_timeout
by David P 25 Jun '21

25 Jun '21

Hi Allan, I don't know if the media_timeout=300 behavior you saw is a bug or not, but I wanted to add my own observation of weirdness about hangup cause MEDIA_TIMEOUT... I just noticed a conference end abruptly after one leg spoke for 5 minutes. The logs aren't clear why this happened, but it seems that <param name="rtp-timeout-sec" value="300"/> in our sip_profiles/internal.xml is the reason -- it seems that because the *other* leg of the conference remained silent, the RTP timeout was reached. I couldn't find any confluence pages about MEDIA_TIMEOUT by googling. On Fri, Jan 8, 2021 at 1:08 AM < freeswitch-users-request(a)lists.freeswitch.org> wrote: > > ---------- Forwarded message ---------- > From: Allan Kristensen <ak(a)hejdu.dk> > To: FreeSWITCH Users Help <freeswitch-users(a)lists.freeswitch.org> > Cc: > Bcc: > Date: Wed, 6 Jan 2021 19:37:33 +0100 > Subject: [Freeswitch-users] rtp-timeout-sec VS media_timeout > We had some problems with "hanging channels" for our webrtc clients (via > kamailio). > To solve the problem I tried to use "media_timeout" setting but it didn't > really work. So I tried the deprecated "rtp-timeout-sec" and this actually > works fine? > > Not working: > <param name="media_timeout" value="300"/> > > Working: > <param name="rtp-timeout-sec" value="300"/> > > How to reproduce: Make a call using webrtc and just close browser window, > after some time freeswitch should close the channel because of missing rtp. > Instead it just keeps writing: "switch_rtp.c:853 No audio stun for a long > time!" forever... > > Anyway, it works now....just curious why...a typo or bug? > > /Allan > > Using: > FreeSWITCH Version 1.10.5-release+git~20200818T185121Z~25569c1631~64bit >

3 3

Unregister all devices
by jean rouquet 29 May '21

29 May '21

Hello, If bob is registered from two devices, is it possible from one device to cancel both registrations? regards, Jean

3 4

Re: [Freeswitch-users] rtp-timeout-sec VS media_timeout
by David P 28 May '21

28 May '21

We're using FS 10.5 on Debian Stretch installed via packages. <param name="rtp-timeout-sec" value="300"/> in our sip_profiles/internal.xml does effect calls. We have no media_timeout* config.

4 4

Configuring mod_portaudio for Debian built-in (JACK?) audio
by Steven Schoch 21 May '21

21 May '21

I have an HP Prodesk tower with Debian and FreeSWITCH installed. It has an audio jack that is plugged into a speaker. I configured the system so that the devices in /dev/snd are group "freeswitch". Now I want to transfer a call to the speaker with <action application="bridge" data="portaudio/auto_answer"/>. However, I am getting errors when I load mod_portaudio that look like this: 2021-03-27 21:15:30.747447 [ERR] mod_portaudio.c:1617 Invalid outstream specified for endpoint 'default' It looks like a config file issue, but I have no clue where to start because I couldn't find a good example. Any suggestions? -- Steve

2 3

JSON channel variable from Dialplan
by Guillermo Ruiz Camauer 05 May '21

05 May '21

Hi all, Is it possible to set the value of a channel variable to a JSON formatted string? I need to do something like this: <action application="set" data="MY_VAR=[\"Ford\", \"Chevy\"]"/> The problem seems to be that FS is not accepting the escape sequence and MY_VAR gets set to [\ How do I go about escaping double quotes in the dialplan? -- Guillermo Ruiz Camauer

4 6

Horizontally scaling mod_callcenter
by Nathan Stratton 02 May '21

02 May '21

We are currently using FreeSWITCH mod_callcenter for live video agents. It's working well, but recently we have been asked to greatly scale the number of queues and agents to the point where we will need many FreeSWITCH boxes to support them. Based on the documentation and posts I have read mdo_callcenter does NOT support multiple instances with a shared database. So what is the best practice to scale? ><> nathan stratton

2 2