October 2020 - FreeSWITCH-users - FreeSWITCH Mailing Lists

Regarding register issue
by Alaghu Sundram 31 Oct '20

31 Oct '20

Hi, I register vertility through freeswitch I got message as "expire time in 60 by request of proxy sip: sofia_reg. C: 2458 Changing expire time in 60 by request of proxy " I also found error registering other VoIP Registration failed. "Too much hope list" Thanks R.Alaghu Sundram

2 1

Conference with max-members =2 allows a third caller
by Tom Lynn 30 Oct '20

30 Oct '20

I've set a new conference profile, to which I've added max-members and set it equal to 2. I've assigned the new profile to a conference, but the limit does not seem to be enforced. The conference allows a 3rd participant to join. Is there anything more I need to do to limit the number of callers besides setting max-members = X ? Thanks

1 0

Installation Fs 1.10.5 problem
by Andres Gomez 27 Oct '20

27 Oct '20

Hi all. I have a problem after installing standard vanilla. It doesn't start with fs_cli, and when I try to run it manually I see the following: 2020-10-27 10:54:00.042884 [NOTICE] sofia.c:6195 Started Profile external-ipv6 [sofia_reg_external-ipv6] 2020-10-27 10:54:00.043067 [ERR] sofia.c:5083 Invalid ext-rtp-ip 2020-10-27 10:54:00.043074 [ERR] sofia.c:5180 Invalid ext-sip-ip 2020-10-27 10:54:00.043080 [NOTICE] switch_event.c:464 Subclass reservation deleted for mod_sofia.c:sofia::notify_refer 2020-10-27 10:54:00.043084 [NOTICE] switch_event.c:464 Subclass reservation deleted for mod_sofia.c:sofia::notify_watched_header 2020-10-27 10:54:00.043087 [NOTICE] switch_event.c:464 Subclass reservation deleted for mod_sofia.c:sofia::unregister 2020-10-27 10:54:00.043089 [NOTICE] switch_event.c:464 Subclass reservation deleted for mod_sofia.c:sofia::profile_start 2020-10-27 10:54:00.043092 [NOTICE] switch_event.c:464 Subclass reservation deleted for mod_sofia.c:sofia::reinvite 2020-10-27 10:54:00.043095 [NOTICE] switch_event.c:464 Subclass reservation deleted for mod_sofia.c:sofia::replaced 2020-10-27 10:54:00.043098 [NOTICE] switch_event.c:464 Subclass reservation deleted for mod_sofia.c:sofia::transferor 2020-10-27 10:54:00.043100 [NOTICE] switch_event.c:464 Subclass reservation deleted for mod_sofia.c:sofia::transferee 2020-10-27 10:54:00.043103 [NOTICE] switch_event.c:464 Subclass reservation deleted for mod_sofia.c:sofia::error 2020-10-27 10:54:00.043105 [NOTICE] switch_event.c:464 Subclass reservation deleted for mod_sofia.c:sofia::intercepted 2020-10-27 10:54:00.043108 [NOTICE] switch_event.c:464 Subclass reservation deleted for mod_sofia.c:sofia::gateway_state 2020-10-27 10:54:00.043111 [NOTICE] switch_event.c:464 Subclass reservation deleted for mod_sofia.c:sofia::sip_user_state 2020-10-27 10:54:00.043113 [NOTICE] switch_event.c:464 Subclass reservation deleted for mod_sofia.c:sofia::gateway_delete 2020-10-27 10:54:00.043117 [NOTICE] switch_event.c:464 Subclass reservation deleted for mod_sofia.c:sofia::expire 2020-10-27 10:54:00.043120 [NOTICE] switch_event.c:464 Subclass reservation deleted for mod_sofia.c:sofia::register_attempt *2020-10-27 10:54:00.043123 [NOTICE] switch_event.c:464 Subclass reservation deleted for mod_sofia.c:sofia::register_failureSegmentation fault (core dumped)* I´m installing with Debian 10 and :. https://freeswitch.org/confluence/display/FREESWITCH/Debian+10+Buster Regards

3 2

Recording file is bigger than the call duration
by Shahnawaj Khan 27 Oct '20

27 Oct '20

Hi, I am working on freeswitch 1.10.2 and using record_session to record the media of the calls. I found a case where call recording was greater than the call duration by 4 seconds. I was running freeswitch in debug logs but nothing seems off in the logs. But I found some error logs in xml cdr and unable to find an explanation for those in any of the confluence pages. Please let me know if someone has the idea of following error logs. <error-log> <error-period> <start>1603359922800633</start> <stop>1603359925820633</stop> <flaws>2</flaws> <consecutive-flaws>1</consecutive-flaws> <duration-msec>3020</duration-msec> </error-period> <error-period> <start>1603359908820633</start> <stop>1603359911840633</stop> <flaws>3</flaws> <consecutive-flaws>1</consecutive-flaws> <duration-msec>3020</duration-msec> </error-period> <error-period> <start>1603359757800632</start> <stop>1603359760820633</stop> <flaws>3</flaws> <consecutive-flaws>1</consecutive-flaws> <duration-msec>3020</duration-msec> </error-period> <error-period> <start>1603359751800633</start> <stop>1603359754820633</stop> <flaws>3</flaws> <consecutive-flaws>1</consecutive-flaws> <duration-msec>3020</duration-msec> </error-period> <error-period> <start>1603359742800633</start> <stop>1603359746000634</stop> <flaws>6</flaws> <consecutive-flaws>2</consecutive-flaws> <duration-msec>3200</duration-msec> </error-period> <error-period> <start>1603359601780633</start> <stop>1603359604800633</stop> <flaws>3</flaws> <consecutive-flaws>1</consecutive-flaws> <duration-msec>3020</duration-msec> </error-period> <error-period> <start>1603359566800632</start> <stop>1603359569820633</stop> <flaws>3</flaws> <consecutive-flaws>1</consecutive-flaws> <duration-msec>3020</duration-msec> </error-period> <error-period> <start>1603359497800634</start> <stop>1603359500820633</stop> <flaws>3</flaws> <consecutive-flaws>1</consecutive-flaws> <duration-msec>3019</duration-msec> </error-period> </error-log> Thanks & Regards, Shahnawaz

1 0

sqlite db
by Cris Espinosa 27 Oct '20

27 Oct '20

Hello, https://lists.freeswitch.org/pipermail/freeswitch-users/2018-January/128600…<https://urldefense.com/v3/__https://lists.freeswitch.org/pipermail/freeswit…> I'm following up on a thread from a couple of years ago where Antonio asked Geoff if we were using wss endpoints in our freeswitch setup. The answer to that question is yes. I realize this was a couple of years ago, but we are still having unexplained crashes with our freeswitch instances and switching to mysql did not seem to correct the issue. Is there some concern with wss endpoints and sqlite? The version this issue was occuring on was 1.6.20. As a side note, we are currently working on migrating this setup to 1.10.5 and possibly moving back to sqlite Cris Espinosa COMMUNICATE COLLABORATE CONNECT SoftWare Engineer [http://go.ringcentral.com/rs/ringcentral/images/newlogoforsig.png]

1 0

How to bridge to external using URL, which is correct?
by mario_fs 26 Oct '20

26 Oct '20

I am trying to bridge an incoming call to an external number(s). I currently have this working for years to normal cell phones. I want to change it to call my ITSP instead of a mobile number but having problems. I have ready the wiki and many posts but they have many variations. Have tried with registered and unregistered. I am missing something. The question is what is the correct/best format, I can register the outbound # since it’s my account, the inbound is already registered. Thanks very much! Mario G I tried #1 below and it does not work. 1. sofia/gateway/${dial_gateway}/sip:number@itsp.com <sip:number@itsp.com>. <- NOGO 2. WIki has these but I am really puzzled but the use of “internal": data="sofia/internal/9998881111(a)sip.yourprovider.xn--com-9o0a OR data="{sip_auth_username=foo,sip_auth_password=bar}sofia/internal/9998881111(a)sip.yourprovider.xn--com/-ib7a> Wiki also shows this example which I use to call cell #, but does not work for directions ITSP call: sofia/gateway/asterlink/18005551212 And found this: action application="bridge" data="sofia/gateway/providerA/$1

2 4

Lost ACKs and BYE (ack timeout)
by Martyn Davies 24 Oct '20

24 Oct '20

I have Freeswitch running in an Alpine VM with a Sangoma gateway downstream. Until recently I was using Freeswitch 16 and it was working fine, but due to an OS upgrade, it seemed reasonable to upgrade to Freeswitch 18 (the version that comes with that Alpine release). However, now upstream calls from the Sangoma fail. Specifically, when FS sends the 200 OK (for the Invite), the Sangoma now does not reply with ACK, and so FS tears down the call after 30 sec. I tried the 'connectile dysfunction' parameter, but this did not seem to have any positive effect. In fact, it was perhaps worse because the Register (from Sangoma to FS) seems to get stuck in a loop, with Sangoma sending the request over and over back to back. I would be interested to hear if this rings a bell with anyone? Are there any crucial differences in base config between 16 and 18 that would change the behaviour? Regards, Martyn

2 1

Gateway Configuration on Virtual Machine
by Harshita Pandey 22 Oct '20

22 Oct '20

Hi all, I have installed freeswitch on Virtual Machine. However, when I try to do the gateway configuration, it gives an error.* Are some additional changes required to be made in the Virtual machine *while installing freeswitch as compared to installing freeswitch on the local machine? I get the following error message 2020-10-19 07:18:34.576508 [DEBUG] sofia.c:4597 sip-ip [192.168.2.215] 2020-10-19 07:18:34.576508 [DEBUG] sofia.c:4597 ext-rtp-ip [103.25.231.107] 2020-10-19 07:18:34.576508 [DEBUG] sofia.c:4597 ext-sip-ip [103.25.231.107] 2020-10-19 07:18:34.576508 [DEBUG] sofia.c:4597 rtp-timeout-sec [300] 2020-10-19 07:18:34.576508 [WARNING] sofia.c:5192 rtp-timeout-sec deprecated use media_timeout variable. 2020-10-19 07:18:34.576508 [DEBUG] sofia.c:4597 rtp-hold-timeout-sec [1800] 2020-10-19 07:18:34.576508 [WARNING] sofia.c:5199 rtp-hold-timeout-sec deprecated use media_hold_timeout variable. 2020-10-19 07:18:34.576508 [DEBUG] sofia.c:4597 tls [false] 2020-10-19 07:18:34.576508 [DEBUG] sofia.c:4597 tls-only [false] 2020-10-19 07:18:34.576508 [DEBUG] sofia.c:4597 tls-bind-params [transport=tls] 2020-10-19 07:18:34.576508 [DEBUG] sofia.c:4597 tls-sip-port [5081] 2020-10-19 07:18:34.576508 [DEBUG] sofia.c:4597 tls-passphrase [] 2020-10-19 07:18:34.576508 [DEBUG] sofia.c:4597 tls-verify-date [true] 2020-10-19 07:18:34.576508 [DEBUG] sofia.c:4597 tls-verify-policy [none] 2020-10-19 07:18:34.576508 [DEBUG] sofia.c:4597 tls-verify-depth [2] 2020-10-19 07:18:34.576508 [DEBUG] sofia.c:4597 tls-verify-in-subjects [] 2020-10-19 07:18:34.576508 [DEBUG] sofia.c:4597 tls-version [tlsv1,tlsv1.1,tlsv1.2] 2020-10-19 07:18:34.576508 [INFO] sofia.c:5993 Setting MAX Auth Validity to 0 Attempts 2020-10-19 07:18:34.576508 [NOTICE] sofia.c:6160 Started Profile external [sofia_reg_external] 2020-10-19 07:18:34.576508 [DEBUG] sofia.c:3134 Creating agent for external 2020-10-19 07:18:34.576508 [DEBUG] sofia.c:3253 Created agent for external 2020-10-19 07:18:34.576508 [DEBUG] sofia.c:3302 Set params for external 2020-10-19 07:18:34.576508 [DEBUG] sofia.c:3349 Activated db for external 2020-10-19 07:18:34.576508 [INFO] switch_core_sqldb.c:1870 sofia:external Starting SQL thread. 2020-10-19 07:18:34.576508 [DEBUG] sofia.c:3387 Starting thread for external 2020-10-19 07:18:34.576508 [DEBUG] sofia.c:3034 Launching worker thread for external 2020-10-19 07:18:34.576508 [NOTICE] sofia_reg.c:3426 Added gateway 'MySIP' to profile 'external' 2020-10-19 07:18:34.576508 [NOTICE] sofia_reg.c:3426 Added gateway 'MySIP1' to profile 'external' 2020-10-19 07:18:34.576508 [NOTICE] sofia_reg.c:3426 Added gateway ' example.com' to profile 'external' 2020-10-19 07:18:35.576510 [NOTICE] sofia_reg.c:453 Registering MySIP1 2020-10-19 07:18:35.576510 [NOTICE] sofia_reg.c:453 Registering MySIP 2020-10-19 07:18:35.756510 [ERR] sofia_reg.c:2469 MySIP1 Failed Registration with status Service Unavailable [503]. failure #1 2020-10-19 07:18:35.756510 [ERR] sofia_reg.c:2469 MySIP Failed Registration with status Service Unavailable [503]. failure #1 2020-10-19 07:18:36.576508 [WARNING] sofia_reg.c:510 MySIP1 Failed Registration [503], setting retry to 5 seconds. 2020-10-19 07:18:36.576508 [WARNING] sofia_reg.c:510 MySIP Failed Registration [503], setting retry to 30 seconds. 2020-10-19 07:18:42.596508 [NOTICE] sofia_reg.c:453 Registering MySIP1 2020-10-19 07:18:42.956509 [ERR] sofia_reg.c:2469 MySIP1 Failed Registration with status Service Unavailable [503]. failure #2 2020-10-19 07:18:43.596508 [WARNING] sofia_reg.c:510 MySIP1 Failed Registration [503], setting retry to 5 seconds. 2020-10-19 07:18:49.596509 [NOTICE] sofia_reg.c:453 Registering MySIP1 2020-10-19 07:18:49.956507 [ERR] sofia_reg.c:2469 MySIP1 Failed Registration with status Service Unavailable [503]. failure #3 2020-10-19 07:18:50.596510 [WARNING] sofia_reg.c:510 MySIP1 Failed Registration [503], setting retry to 5 seconds. Thanks in advance. Regards

3 3

Not able to connect to a Softphone
by Harshita Pandey 22 Oct '20

22 Oct '20

Hi, I am not even able to connect to a softphone. When I had installed the freeswitch on a local Machine I was able to connect it to a softphone, but now I have installed freeswitch on a Virtual Machine and that too on a server. I have used the following credentials: Username: 1001 Domain: The IP Address I get on executing eval${local_ip_v4} on the freeswitch command line Password: 1234 (the default password). Where am I doing wrong, or is it that I need to add something else as well, while installing freeswitch on server or VM while connecting to a softphone. I have been using a Linphone as a softphone. Thanks in advance for your help

1 0

Fwd: v1.10 - Able to answer call but no Audio
by Sark Mobiles 22 Oct '20

22 Oct '20

Hello, We installed and configured Freeswitch on CentOS as per the steps provided in below link, https://freeswitch.org/confluence/display/FREESWITCH/CentOS+7+and+RHEL+7#Ce… This is the status - * Users are getting registered * When User A calls User B, B gets a ringtone and is able to answer the call * A sees that the call is connected but there is no audio for either A or B. netstat output --------------------- tcp 0 0 <SVR_IP>:5060 0.0.0.0:* LISTEN 10503/freeswitch tcp 0 0 <SVR_IP>:8081 0.0.0.0:* LISTEN 10503/freeswitch tcp 0 0 <SVR_IP>:8082 0.0.0.0:* LISTEN 10503/freeswitch tcp 0 0 0.0.0.0:8021 0.0.0.0:* LISTEN 10503/freeswitch tcp 0 0 <SVR_IP>:5080 0.0.0.0:* LISTEN 10503/freeswitch Log output --------------- 2020-10-21 08:32:12.323087 [NOTICE] switch_ivr_originate.c:3794 Channel [sofia/internal/1001@<SVR_IP>] has been answered 2020-10-21 08:32:12.323087 [DEBUG] switch_channel.c:3865 (sofia/internal/1001@<SVR_IP>) Callstate Change EARLY -> ACTIVE 2020-10-21 08:32:12.323087 [DEBUG] sofia.c:7326 Channel sofia/internal/1001@<SVR_IP> entering state [completed][200] 2020-10-21 08:32:12.323087 [DEBUG] switch_ivr_originate.c:3852 Originate Resulted in Success: [sofia/internal/1000@192.168.43.32:18486] 2020-10-21 08:32:12.323087 [DEBUG] switch_ivr_originate.c:3852 Originate Resulted in Success: [sofia/internal/1000@192.168.43.32:18486] 2020-10-21 08:32:12.323087 [DEBUG] switch_ivr_bridge.c:1793 (sofia/internal/1000@192.168.43.32:18486) State Change CS_CONSUME_MEDIA -> CS_EXCHANGE_MEDIA 2020-10-21 08:32:12.323087 [DEBUG] switch_core_state_machine.c:585 (sofia/internal/1000@192.168.43.32:18486) Running State Change CS_EXCHANGE_MEDIA (Cur 2 Tot 6) 2020-10-21 08:32:12.323087 [DEBUG] switch_core_state_machine.c:654 (sofia/internal/1000@192.168.43.32:18486) State EXCHANGE_MEDIA 2020-10-21 08:32:12.323087 [DEBUG] mod_sofia.c:656 SOFIA EXCHANGE_MEDIA 2020-10-21 08:32:12.723235 [DEBUG] sofia.c:7326 Channel sofia/internal/1001@<SVR_IP> entering state [ready][200] 2020-10-21 08:32:16.123236 [DEBUG] switch_rtp.c:2448 RTCP packet not written 2020-10-21 08:32:20.143147 [DEBUG] switch_rtp.c:2448 RTCP packet not written 2020-10-21 08:32:24.163187 [DEBUG] switch_rtp.c:2448 RTCP packet not written This keeps repeating - "RTCP packet not written" Please let us know what we might be doing wrong. Appreciate your help. Regards, Krishnan

1 0