November 2020 - FreeSWITCH-users - FreeSWITCH Mailing Lists

Freeswitch (incorrectly?) reporting packet loss via RTCP
by David Horton 20 Nov '20

20 Nov '20

I have a freeswitch server v1.10.1 running on AWS EC2 which I have noticed is reporting lost packets in the RTCP reports it is sending out. This happens even with a single call. Meanwhile, the network stats on the same instances show no dropped packets and no packet receive errors. Is there anything which could explain this? Have others seen errors in the RTCP stats reported by freeswitch? dave

5 13

'__min': is not a member of 'std' gsmlib
by Gregor Nanger 20 Nov '20

20 Nov '20

I want to build FS in Visual Studio 2019. I retarget projects to new C++ SDK and I get this error: Error C2039 '__min': is not a member of 'std' gsmlib C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.28.29333\include\xlocale 2101 Error C2065 '__min': undeclared identifier gsmlib C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.28.29333\include\xlocale 2101 Error C2039 '__min': is not a member of 'std' gsmlib C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.28.29333\include\xlocale 2303 Error C2065 '__min': undeclared identifier gsmlib C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.28.29333\include\xlocale 2303 It has something with including alogorithm.h, but I have lack of knowledge how to solve this problem. Best regards, Gregor

2 1

api_on_ring
by Joli Martinez 19 Nov '20

19 Nov '20

Hello, I am writing a dialer to test some of our DID's and need to terminate the call on a 180 or 183. I am looking at the "api_on_ring" option, but there is not much documentation on it. Would this function do what I am looking for? and if so could I get an example on how to use it? I am just sending an originate to freeswitch and passing the called number as a variable. api:execute("originate", "{call_timeout=10,origination_caller_id_number=+1"..number.. ",ignore_early_media=true}sofia/gateway/GW/+1" ..called.. " &hangup()") Thanks,

2 1

in-dialog SIP options response with 0 RTP port
by Kashif Abbasi 19 Nov '20

19 Nov '20

Hi, I am having an issue in freeswitch case where during a normal in progress audio call session, A party is sending in-dialog SIP OPTIONS message to freeswitch but somehow freeswitch is responding back with 200OK including the SDP and that SDP somehow contains "0" media/RTP port (m=audio 0 RTP/AVP 0 101). This is causing one way muting during the session. Can someone please help how freeswitch can be configured to stop behaving like this? Thanks >>> In-dialog SIP OPTIONS from source side to Freeswitch OPTIONS sip:110237905476@192.168.148.111:5080 SIP/2.0 Max-Forwards: 68 To: <sip:110237905476@192.168.148.111:5080;user=phone>;tag=H2rHgHZpgepHr From: "+99923468064011" <sip:+99923468064011@192.168.150.117>;tag=3814696699-708259 Call-ID: 215272-3814696699-708253(a)ti-SBC-01.ti.com CSeq: 2 OPTIONS Allow: CANCEL, ACK, INVITE, BYE, OPTIONS, REGISTER, NOTIFY, INFO, REFER, SUBSCRIBE, UPDATE, MESSAGE, PUBLISH Via: SIP/2.0/UDP 192.168.150.117:5060;branch=z9hG4bK0f514d4ecdb762b3b0f17a0d489897fd Contact: <sip:+99923468064011@192.168.150.117:5060> Accept: application/sdp Accept: application/isup Accept: application/xml Content-Length: 0 >>> Reply from Freeswitch with SDP SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.150.117:5060;branch=z9hG4bK0f514d4ecdb762b3b0f17a0d489897fd From: "+99923468064011" <sip:+99923468064011@192.168.150.117>;tag=3814696699-708259 To: <sip:110237905476@192.168.148.111:5080;user=phone>;tag=H2rHgHZpgepHr Call-ID: 215272-3814696699-708253(a)ti-SBC-01.ti.com CSeq: 2 OPTIONS Contact: <sip:110237905476@192.168.148.111:5080;transport=udp> User-Agent: FreeSWITCH-mod_sofia/1.10.4-release-16-133fc2c870~64bit Accept: application/sdp Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY Supported: timer, path, replaces Allow-Events: talk, hold, conference, refer Content-Type: application/sdp Content-Length: 222 v=0 o=FreeSWITCH 1605678925 1605678926 IN IP4 192.168.148.111 s=FreeSWITCH c=IN IP4 192.168.148.111 t=0 0 m=audio 0 RTP/AVP 0 101 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:20 Regards Kash

1 0

Why immediate hangup? Sample count too low?
by David P 18 Nov '20

18 Nov '20

Months ago on earlier versions of FS, I added a Restart button to our verto app which hangs-up the call and initiates a new one with a new ID. On FS 1.10.5, I notice that these 2nd calls usually immediately fail. For example, here's one that looks fine until NORMAL_CLEARING appears. The only thing unusual to me is the switching of the relay candidate's address to its raddr: 2020-11-18 21:31:35.444366 [NOTICE] avformat.c:785 video thread start b690a9b6-309f-7caf-df90-299302820fb9 2020-11-18 21:31:35.504354 [NOTICE] switch_rtp.c:1301 *Auto Changing audio stun/rtp/dtls port from (private relay raddr):12419 to (same private relay's candidate in SDP)*:14494 idx:4 80b39dc6-544c-49bf-a9f1-7e946a7eb1c2 2020-11-18 21:31:35.564421 [DEBUG] switch_rtp.c:7759 Correct audio ip/port confirmed. 80b39dc6-544c-49bf-a9f1-7e946a7eb1c2 2020-11-18 21:31:35.664366 [DEBUG] conference_member.c:1764 Raw Codec Activation Success L16@8000hz 1 channel 20ms 80b39dc6-544c-49bf-a9f1-7e946a7eb1c2 2020-11-18 21:31:35.664366 [DEBUG] conference_member.c:1811 Raw Codec Activation Success L16@48000hz 2 channel 20ms 80b39dc6-544c-49bf-a9f1-7e946a7eb1c2 2020-11-18 21:31:35.664366 [DEBUG] conference_loop.c:1338 Setup timer soft success interval: 20 samples: 160 from codec PCMU 80b39dc6-544c-49bf-a9f1-7e946a7eb1c2 2020-11-18 21:31:37.464367 [NOTICE] sofia.c:1089 Hangup sofia/internal/9900_3e1f002c-b97f-4565-85f8-2c886e71c96d_v-1*k-1 [CS_EXECUTE] [NORMAL_CLEARING] Does anyone spot a reason for the hangup? Maybe the sample count is too low?

1 0

Regarding freeswitch termination
by alaghu.sundram 17 Nov '20

17 Nov '20

I got wss destroy message regularly freeswitch(a)fsm.intelliverse.com> sofia loglevel all 9 Sofia log level for component [all] has been set to [9] tport.c:2795 tport_wakeup() tport_wakeup(0x7f89500c2d20): events IN tport.c:2893 tport_recv_event() tport_recv_event(0x7f89500c2d20) tport.c:2165 tport_shutdown0() tport_shutdown0(0x7f89500c2d20, 2) tport.c:2098 tport_close() tport_close(0x7f89500c2d20): wss/208.205.78.126:9519/sips tport.c:2273 tport_set_secondary_timer() tport(0x7f89500c2d20): set timer at 0 ms because zap tport.c:2803 tport_wakeup() tport_wakeup(0x7f89500c2d20): tport is closed! Setting secondary timer! tport.c:2273 tport_set_secondary_timer() tport(0x7f89500c2d20): set timer at 0 ms because zap tport_type_ws.c:531 tport_ws_deinit_secondary() 0x7f89500c2d20 destroy wss transport 0x7f89500c2f10. tport.c:2770 tport_wakeup_pri() tport_wakeup_pri(0x7f8950005a80): events IN tport.c:862 tport_alloc_secondary() tport_alloc_secondary(0x7f8950005a80): new secondary tport 0x7f89500c2d20 tport.c:2307 tport_set_secondary_timer() tport(0x7f89500c2d20): set timer at 4998 ms because keepalive tport.c:2657 tport_accept() tport_accept(0x7f89500c2d20): new connection from wss/208.205.78.126:26392/sips tport.c:2795 tport_wakeup() tport_wakeup(0x7f89500c2d20): events IN tport.c:2893 tport_recv_event() tport_recv_event(0x7f89500c2d20) tport.c:2311 tport_set_secondary_timer() tport(0x7f89500c2d20): reset timer tport.c:2795 tport_wakeup() tport_wakeup(0x7f89500c2d20): events IN tport.c:2893 tport_recv_event() tport_recv_event(0x7f89500c2d20) tport.c:3234 tport_recv_iovec() tport_recv_iovec(0x7f89500c2d20) msg 0x7f89500fb760 from (wss/208.205.78.126:26392) has 100 bytes, veclen = 1 tport.c:3052 tport_deliver() tport_deliver(0x7f89500c2d20): bad msg 0x7f89500fb760 (0 bytes) from wss/208.205.78.126:26392/sips next=(nil) tport.c:2311 tport_set_secondary_timer() tport(0x7f89500c2d20): reset timer tport.c:2311 tport_set_secondary_timer() tport(0x7f89500c2d20): reset timer tport.c:2795 tport_wakeup() tport_wakeup(0x7f89500c2d20): events IN tport.c:2893 tport_recv_event() tport_recv_event(0x7f89500c2d20) tport.c:3234 tport_recv_iovec() tport_recv_iovec(0x7f89500c2d20) msg 0x7f89500fc050 from (wss/208.205.78.126:26392) has 100 bytes, veclen = 1 tport.c:3052 tport_deliver() tport_deliver(0x7f89500c2d20): bad msg 0x7f89500fc050 (0 bytes) from wss/208.205.78.126:26392/sips next=(nil) tport.c:2311 tport_set_secondary_timer() tport(0x7f89500c2d20): reset timer tport.c:2311 tport_set_secondary_timer() tport(0x7f89500c2d20): reset timer tport.c:2795 tport_wakeup() tport_wakeup(0x7f89500c2d20): events IN tport.c:2893 tport_recv_event() tport_recv_event(0x7f89500c2d20) tport.c:2165 tport_shutdown0() tport_shutdown0(0x7f89500c2d20, 2) tport.c:2098 tport_close() tport_close(0x7f89500c2d20): wss/208.205.78.126:26392/sips tport.c:2273 tport_set_secondary_timer() tport(0x7f89500c2d20): set timer at 0 ms because zap tport.c:2803 tport_wakeup() tport_wakeup(0x7f89500c2d20): tport is closed! Setting secondary timer! tport.c:2273 tport_set_secondary_timer() tport(0x7f89500c2d20): set timer at 0 ms because zap tport_type_ws.c:531 tport_ws_deinit_secondary() 0x7f89500c2d20 destroy wss transport 0x7f89500c2f10. tport.c:2770 tport_wakeup_pri() tport_wakeup_pri(0x7f8950005a80): events IN tport.c:862 tport_alloc_secondary() tport_alloc_secondary(0x7f8950005a80): new secondary tport 0x7f89500c2d20 tport.c:2307 tport_set_secondary_timer() tport(0x7f89500c2d20): set timer at 4998 ms because keepalive tport.c:2657 tport_accept() tport_accept(0x7f89500c2d20): new connection from wss/208.205.78.126:28372/sips tport.c:2795 tport_wakeup() tport_wakeup(0x7f89500c2d20): events IN tport.c:2893 tport_recv_event() tport_recv_event(0x7f89500c2d20) tport.c:2311 tport_set_secondary_timer() tport(0x7f89500c2d20): reset timer tport.c:2795 tport_wakeup() tport_wakeup(0x7f89500c2d20): events IN tport.c:2893 tport_recv_event() tport_recv_event(0x7f89500c2d20) tport.c:3234 tport_recv_iovec() tport_recv_iovec(0x7f89500c2d20) msg 0x7f89500fb210 from (wss/208.205.78.126:28372) has 100 bytes, veclen = 1 tport.c:3052 tport_deliver() tport_deliver(0x7f89500c2d20): bad msg 0x7f89500fb210 (0 bytes) from wss/208.205.78.126:28372/sips next=(nil) tport.c:2311 tport_set_secondary_timer() tport(0x7f89500c2d20): reset timer tport.c:2311 tport_set_secondary_timer() tport(0x7f89500c2d20): reset timer tport.c:2795 tport_wakeup() tport_wakeup(0x7f89500c2d20): events IN tport.c:2893 tport_recv_event() tport_recv_event(0x7f89500c2d20) tport.c:3234 tport_recv_iovec() tport_recv_iovec(0x7f89500c2d20) msg 0x7f89500fb210 from (wss/208.205.78.126:28372) has 100 bytes, veclen = 1 tport.c:3052 tport_deliver() tport_deliver(0x7f89500c2d20): bad msg 0x7f89500fb210 (0 bytes) from wss/208.205.78.126:28372/sips next=(nil) tport.c:2311 tport_set_secondary_timer() tport(0x7f89500c2d20): reset timer tport.c:2311 tport_set_secondary_timer() tport(0x7f89500c2d20): reset timer -- Sent from: http://freeswitch-users.2379917.n2.nabble.com/

1 0

Regarding freeswitch termination
by alaghu.sundram 17 Nov '20

17 Nov '20

After registiration we got destroy wss transport Sofia log level for component [all] has been set to [9] tport.c:2770 tport_wakeup_pri() tport_wakeup_pri(0x7fdcc8005840): events IN tport.c:862 tport_alloc_secondary() tport_alloc_secondary(0x7fdcc8005840): new secondary tport 0x7fdcc8070480 tport.c:2307 tport_set_secondary_timer() tport(0x7fdcc8070480): set timer at 4998 ms because keepalive tport.c:2657 tport_accept() tport_accept(0x7fdcc8070480): new connection from wss/208.205.78.126:58435/sips tport.c:2795 tport_wakeup() tport_wakeup(0x7fdcc8070480): events IN tport.c:2893 tport_recv_event() tport_recv_event(0x7fdcc8070480) tport.c:2311 tport_set_secondary_timer() tport(0x7fdcc8070480): reset timer tport.c:2795 tport_wakeup() tport_wakeup(0x7fdcc8070480): events IN tport.c:2893 tport_recv_event() tport_recv_event(0x7fdcc8070480) tport.c:3234 tport_recv_iovec() tport_recv_iovec(0x7fdcc8070480) msg 0x7fdcc8041220 from (wss/208.205.78.126:58435) has 100 bytes, veclen = 1 tport.c:3052 tport_deliver() tport_deliver(0x7fdcc8070480): bad msg 0x7fdcc8041220 (0 bytes) from wss/208.205.78.126:58435/sips next=(nil) tport.c:2311 tport_set_secondary_timer() tport(0x7fdcc8070480): reset timer tport.c:2311 tport_set_secondary_timer() tport(0x7fdcc8070480): reset timer tport.c:2795 tport_wakeup() tport_wakeup(0x7fdcc8070480): events IN tport.c:2893 tport_recv_event() tport_recv_event(0x7fdcc8070480) tport.c:3234 tport_recv_iovec() tport_recv_iovec(0x7fdcc8070480) msg 0x7fdcc8041220 from (wss/208.205.78.126:58435) has 100 bytes, veclen = 1 tport.c:3052 tport_deliver() tport_deliver(0x7fdcc8070480): bad msg 0x7fdcc8041220 (0 bytes) from wss/208.205.78.126:58435/sips next=(nil) tport.c:2311 tport_set_secondary_timer() tport(0x7fdcc8070480): reset timer tport.c:2311 tport_set_secondary_timer() tport(0x7fdcc8070480): reset timer tport.c:2795 tport_wakeup() tport_wakeup(0x7fdcc8070480): events IN tport.c:2893 tport_recv_event() tport_recv_event(0x7fdcc8070480) tport.c:2165 tport_shutdown0() tport_shutdown0(0x7fdcc8070480, 2) tport.c:2098 tport_close() tport_close(0x7fdcc8070480): wss/208.205.78.126:58435/sips tport.c:2273 tport_set_secondary_timer() tport(0x7fdcc8070480): set timer at 0 ms because zap tport.c:2803 tport_wakeup() tport_wakeup(0x7fdcc8070480): tport is closed! Setting secondary timer! tport.c:2273 tport_set_secondary_timer() tport(0x7fdcc8070480): set timer at 0 ms because zap tport_type_ws.c:531 tport_ws_deinit_secondary() 0x7fdcc8070480 destroy wss transport 0x7fdcc8070670. tport.c:2770 tport_wakeup_pri() tport_wakeup_pri(0x7fdcc8005840): events IN tport.c:862 tport_alloc_secondary() tport_alloc_secondary(0x7fdcc8005840): new secondary tport 0x7fdcc8070480 tport.c:2307 tport_set_secondary_timer() tport(0x7fdcc8070480): set timer at 4998 ms because keepalive tport.c:2657 tport_accept() tport_accept(0x7fdcc8070480): new connection from wss/208.205.78.126:31157/sips tport.c:2795 tport_wakeup() tport_wakeup(0x7fdcc8070480): events IN tport.c:2893 tport_recv_event() tport_recv_event(0x7fdcc8070480) tport.c:2311 tport_set_secondary_timer() tport(0x7fdcc8070480): reset timer tport.c:2795 tport_wakeup() tport_wakeup(0x7fdcc8070480): events IN tport.c:2893 tport_recv_event() tport_recv_event(0x7fdcc8070480) tport.c:3234 tport_recv_iovec() tport_recv_iovec(0x7fdcc8070480) msg 0x7fdcc80d5660 from (wss/208.205.78.126:31157) has 100 bytes, veclen = 1 tport.c:3052 tport_deliver() tport_deliver(0x7fdcc8070480): bad msg 0x7fdcc80d5660 (0 bytes) from wss/208.205.78.126:31157/sips next=(nil) tport.c:2311 tport_set_secondary_timer() tport(0x7fdcc8070480): reset timer tport.c:2311 tport_set_secondary_timer() tport(0x7fdcc8070480): reset timer tport.c:2795 tport_wakeup() tport_wakeup(0x7fdcc8070480): events IN tport.c:2893 tport_recv_event() tport_recv_event(0x7fdcc8070480) tport.c:3234 tport_recv_iovec() tport_recv_iovec(0x7fdcc8070480) msg 0x7fdcc80d5a50 from (wss/208.205.78.126:31157) has 100 bytes, veclen = 1 tport.c:3052 tport_deliver() tport_deliver(0x7fdcc8070480): bad msg 0x7fdcc80d5a50 (0 bytes) from wss/208.205.78.126:31157/sips next=(nil) tport.c:2311 tport_set_secondary_timer() tport(0x7fdcc8070480): reset timer tport.c:2311 tport_set_secondary_timer() tport(0x7fdcc8070480): reset timer -- Sent from: http://freeswitch-users.2379917.n2.nabble.com/

1 0

Create webrtc call with custom signaling
by אריה קלטר 13 Nov '20

13 Nov '20

Hello It there a way to create a webrtc call with custom signaling? I want that when freeswitch receive a sip call, send it to the browser without registration or authentication Freeswitch receive incoming call: Create second leg for webrtc Get sdp of the second leg I will send it to the browser using custom signaling, Get answer sdp from the browser, Send the answer sdp to freeswitch Bridge both legs I saw media_webrtc=true, but i did not understand how to receive the offer sdp and how to send the answer back to freeswitch using the api. Can i do it using esl? Any idea how to implement it? Is it possible?

2 1

Setting up a call center on FreeSWITCH
by Sam van Herwaarden 12 Nov '20

12 Nov '20

Hi all, Does anyone here have experience setting up call centers on FreeSWITCH? Is there any open source software that makes this easy? Our organization (https://precisionag.org) is likely to have some needs in this area soon, though I'm still identifying the exact requirements. We are looking to have inbound traffic on our system processed by a call center, while also running an automated outbound system on the same number. I think I have a decent sense of how the dialplan would look, but I have no experience with things like queueing and don't know what kind of software is available for managing a call center like this. If you do consulting on this, or if you know someone good, it would be great if you can get in touch. Kind regards, Sam

2 3

WebRTC and UnifiedPlan
by David Villasmil 10 Nov '20

10 Nov '20

Hello all, Are there plans to support Unified-Plan or PlanB in the future? Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

1 1