July 2021 - FreeSWITCH-users - FreeSWITCH Mailing Lists

Need help to setup stir shaken in Freeswitch
by Pete Kay 04 Aug '22

04 Aug '22

Hi Does anyone know how to configure Freeswitch for stir shaken? Could you give me some info or doc how to do it? Thanks, Pete

3 3

uuid_broadcast hang and start after the call hangup
by Dmitry Mordovin 06 May '22

06 May '22

Hello I have LUA script which start a call (new session generated) Code here new_session = freeswitch.Session(destination); if (new_session:ready()) then new_session_disp = new_session:getVariable("endpoint_disposition"); while(new_session:ready() and new_session_disp ~= "ANSWER") do <------>new_session_disp = new_session:getVariable("endpoint_disposition"); end api = freeswitch.API(); api:executeString("bgapi uuid_park " .. tostring(new_session.uuid)); end On answer event I park the call and script finished. I see single active call. Listing below. freeswitch@freeswitch43> show calls uuid,direction,created,created_epoch,name,state,cid_name,cid_num,ip_addr,dest,presence_id,presence_data,accountcode,callstate,callee_name,callee_num,callee_direction,call_uuid,hostname,sent_callee_name,sent_callee_num,b_uuid,b_direction,b_created,b_created_epoch,b_name,b_state,b_cid_name,b_cid_num,b_ip_addr,b_dest,b_presence_id,b_presence_data,b_accountcode,b_callstate,b_callee_name,b_callee_num,b_callee_direction,b_sent_callee_name,b_sent_callee_num,call_created_epoch 3aa3a274-c23d-11eb-9150-e74dc4cdb20a,outbound,2021-05-31 18:22:59,1622485379,sofia/external/1000,CS_PARK,,0000000000,,1000,,,,ACTIVE,Outbound Call,1000,,3aa3a274-c23d-11eb-9150-e74dc4cdb20a,freeswitch43,,,,,,,,,,,,,,,,,,,,,, 1 total. After all I execute command from cli: Command looks like: uuid_broadcast 3aa3a274-c23d-11eb-9a50-e74dc4cdb20a lua::’next-script.lua' both In logs I see, command was sent to FS success, but not executed! Moveover, after call hangup, FS start execution of command but can’t coz call in terminate state. 2021-05-31 18:23:30.312133 [NOTICE] sofia.c:1079 Hangup sofia/external/1000 [CS_PARK] [NORMAL_CLEARING] 2021-05-31 18:23:30.312133 [DEBUG] switch_ivr.c:625 sofia/external/1000 Command Execute lua(next-script.lua) 2021-05-31 18:23:30.312133 [DEBUG] switch_core_session.c:2668 sofia/external/1000 ZOMBIE EXEC lua(next-script.lua) EXECUTE sofia/external/1000 lua(next-script.lua) What/why is ZOMBIE EXEC ? Could someone help me to find reason of strange behavior FS? Looks like the uuid_broadcast command stay in queueu and wait something… and start after call has hangup.

3 2

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

Can calls be rejected if they are missing EITHER audio or video USABLE ice candidates?
by David P 09 Aug '21

09 Aug '21

We're evaluating a paid TURN service, and we've found that sometimes it provides only a STUN candidate for audio and neither STUN nor TURN for video. The user's host candidates are all private IPv4. FS 10.5 allows such a call, but we'd like to reject any call *lacking* usable ICE candidates for *either* audio or video. I see at https://freeswitch.org/confluence/display/FREESWITCH/Channel+Variables that there is channel var "variable_remote_media_ip", so if this is empty for both audio and video, we could set our dialplan to reject the call. But is this var set independently for audio and video so we can check that both are present? Or is there a better way?

2 1

Handling temporary WS breakages more gracefully
by David P 26 Jul '21

26 Jul '21

When there is a temporary break in verto's WSS login, it does verto.purge() and that seems to force a new createOffer/createAnswer negotiation and re-execution of the dialplan if the connection is re-established. Is there a reason why renegotiation of the media connections is necessary? In our case we've tried to minimize disruptions to the callers by using verto's support for reattaching/recovering sessions, but that seems to complicate things when the dialplan is re-executed...it seems to result in simultaneous verto calls with the same users. And some of these sessions seem to trigger media_timeout despite there being media (resulting in sudden loss of media in recordings). Does it seem that I'm interpreting things consistently with the design of verto and FS? If so, then it seems that we should disable the verto.purge() so the current ICE connections are kept and the dialplan is not re-executed, and rely on media_timeout to detect abandoned sessions.

1 0

Verto WebRTC
by Praveenkumar T 23 Jul '21

23 Jul '21

Dear All, I am using Verto (WebRTC) as well as other standard sip phone which can establish normal extension calls b/w each other, however I notice in the fs_cli <show registrations> it's not listing the extension ID for the one which are logged/registered via Verto, where as I can see the extension registrations listed in case of other sip phone. Please confirm if any configuration to be done in order to list in show registrations (to list the extensions which are registered via Verto). Waiting for your kind response. Thanks & Regards Praveen

2 1

Re-Invite not passed to other leg
by Jason Grant 20 Jul '21

20 Jul '21

I was hoping someone could help clarify on whether re-invites are supposed to pass between both legs of a call when a call is placed on hold? As far as I can see, the re-invite when a caller is placed on hold is passed to FreeSWITCH but it is not passed on to the other leg. The issue I’m having is the SDP body changes of a=sendonly or a=sendrecieve never reach the other leg. Is this intended behaviour? Is there a way to change this? Kind regards Jason Grant

4 3