June 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

Call drop with 406 after being answered
by Igor Potjevlesh 07 Jul '21

07 Jul '21

Hello! I'm facing a problem with a call scenario with an in-dialog INVITE just after the call has been picked up. Freeswitch receive on his leg B this in-dialog INVITE. Not forwarded to leg A. In a SIP trace, I can see 406 Not Acceptable on leg B whereas there is no difference in the Media except "Bandwidth Information" which is "AS:80" versus "AS:82" in the RE-INVITE. I turn on the logs on debug, but nothing specific appears. The first thing: 3f6d8dd1-5415-4a58-a948-551d841cf5dd 2021-06-11 10:34:12.873542 [NOTICE] sofia.c:1012 Hangup sofia/internal/ABC [CS_EXCHANGE_MEDIA] [NORMAL_CLEARING] 3f6d8dd1-5415-4a58-a948-551d841cf5dd 2021-06-11 10:34:12.873542 [DEBUG] switch_ivr_bridge.c:787 BRIDGE THREAD DONE [sofia/internal/ABC] 3f6d8dd1-5415-4a58-a948-551d841cf5dd 2021-06-11 10:34:12.873542 [DEBUG] switch_core_state_machine.c:653 (sofia/internal/ ABC) State EXCHANGE_MEDIA going to sleep [.] 5f1866f7-f6c6-43c9-83bb-07cbb51cc3a5 2021-06-11 10:34:12.893545 [DEBUG] switch_core_session.c:2815 sofia/lega/+FROM(a)W.X.Y.Z. skip receive message [APPLICATION_EXEC_COMPLETE] (channel is hungup already) Is there any reason for this? SDP is not duplicated, but there is no specific reason for replying with 406. Regards, Igor. -- L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast. https://www.avast.com/antivirus

3 7

Issue with BLF and shared line Indications
by Kunal Mittal 06 Jul '21

06 Jul '21

Looking for some help with BLF in Freeswitch. Randomly for few users BLF indicator for parking and shared lines stops working. Rebooting the phone fixes the problems for some time and then again it stops working. We have FS 1.10.6 Approx. 500 Users Registered (most of them registered remotely from different networks) 1000 Contacts (Multiple registrations) Using Call Parking and Shared lines, most phones subscribe for BLF to monitor the calls on shared line or parked calls. System Details: VM with 12 GB Ram and 8 Core CPU. Using Postgres for Core Data and profiles. Max 40-50 calls. Sometimes I notice high CPU on this server, while on other servers with no shared lines and no BLF, Virtual machines handles 100+ calls and 700 users. Anyone could provide any suggestions/hints to help troubleshoot this. Is this too much for one server to handle? Is BLF too complicated?

2 1

Setting Contact Header in Register
by Peter Steinbach 06 Jul '21

06 Jul '21

Hello, for a german SIP provider, I need to send the contact header in the Register request the following way: Contact: <sip:012345678@xx.yy.zz.aa:5080> with 012345678 as the registered SIP trunk number Today we send: Contact: <sip:gw+dtst@xx.yy.zz.aa:5080;transport=udp;gw=dtst> which is not accepted by them. The reason is: They filter SIP packets by their phone numbers in the contact header for security reasons. So my question is: Is there a way to set the desired behaviour in the Register request: Contact: <sip:012345678@xx.yy.zz.aa:5080> -- With kind regards Peter Steinbach Telefaks Services GmbH mailto:lists (att) telefaks.de Internet: www.telefaks.de

2 2

Amazon EC2 Instances - Freeswitch
by HS 03 Jul '21

03 Jul '21

Dear all, I have been testing an Opensips + Freeswitch setup on the same instance on EC2. I did follow the guide here for IP setup: https://freeswitch.org/confluence/display/FREESWITCH/Amazon+EC2 However, for production, it seems better to have separate instances for Opensips and Freeswitch. (Or wrong?). What would be the following variables: bind_server_ip external_rtp_ip external_sip_ip Shall I use the Opensips external IP or Freeswitch (although Freeswitch will have no external access). Thanks for the help.

5 17