May 2015 - FreeSWITCH-users - FreeSWITCH Mailing Lists

T.30 faxing - V.27ter
by Tihomir Culjaga 13 May '15

13 May '15

Hi, i got an issue with faxing between a fax machine and FreeSWITCH T.30 protocol. I'm able to send and get faxes everywhere except to this machine. The fax machine uses V.27ter protocol at 4800 and no ECM. faxing from a different fax machine works perfectly but not when i send it from FS. FS logs are here: https://pastebin.freeswitch.org/24139 I extracted audio and tried to decode it with fax_decode ( from spends/tests ) and it fails to decode as well. Also, i tried to decode the audio between two fax machines when the fax went ok and it fax_decode fails on this one as well. fax_decode logs: https://pastebin.freeswitch.org/24140 so maybe we have an issue with V.27ter perhaps. can anyone look say a bit more on this issue ? P.S.: FreeSWITCH Version 1.4.18+git~20150312T185523Z~4eed221b69~32bit (git 4eed221 2015-03-12 18:55:23Z 32bit) regards, Tihomir.

3 5

multiple registration not working
by Eric Ni 13 May '15

13 May '15

Hi, I have just upgraded form old freeswith 1.2 to the current release version: FreeSWITCH Version 1.4.18+git~20150312T185523Z~4eed221b69~64bit (git 4eed221 2015-03-12 18:55:23Z 64bit) However I can not turn on multiple registration now. After setting <param name="multiple-registrations" value="ture"/> in sip profile. I can still only see one contact in list_users. Can anyone help with this? Thanks.

2 3

[SOS] Help Needed with Strange Behavior
by Mohammad Amin Navid 13 May '15

13 May '15

To all the crazy ones, all the gurus: TLDR: FreeSWITCH Server looses connectivity with main router (gateway), can ping any other server but cannot reach router. We have a cluster of FreeSWITCH servers running behind Kamailio. For 3 years we have been up and running smoothly without any glitches. Last week we upgraded our FreeSWITCH servers, the upgrade included: 1) Upgraded Debian Squeeze to Ubuntu LTS 14.04 2) Upgraded FreeSWITCH from version 1.2 to 1.4.18 (git: 4eed221) Ever since last week, a very strange problem happened 3 times. The FreeSWITCH servers randomly loose connectivity with our main router (gateway). FS servers can be reached and pinged from the rest of servers, they also can ping and reach all other servers but when we ping router from inside FS servers they cannot ping and reach the router. The only way we can get them working again is by: ifconfig eth1 down sleep 3 ifconfig eth1 up route add default gw 208.65.xxx.xxx eth1 The rest of our 20 servers are all running Ubuntu 14.04 and most of them are under heavy load, this only happens with FS servers. Does any one have any clue about this bizarre situation? Any one know under what circumstances a server might loose connectivity and routing to its gateway? Any pointer for debugging or suggestion is highly appreciated. Thank you, Moe

5 4

Improving voice quality
by Adam Ben-Ayoun 13 May '15

13 May '15

Hi guys, We are using Freeswitch as a audio "MCU" for WebRTC using mod_conference, we are currently using mobile clients on both Android and iOS. The voice quality is good but not as good as Hangouts for example, there are small cut-offs every now and then that affects the overall experience. We are trying to understand the reason for that, maybe it's Freeswitch mixing algorithm, our servers infrastructure, or something else. We did tried Janus audio conference demo and it was very good (we used chrome on Android which should use pretty much the same stack). We really need help figuring this out. I want to first make sure it's not our infrastructure (mainly network/CPU). We are using virtualized m3.large on AWS (2 vCPUs and 7.5GB RAM). Maybe there's a certain instance type on a certain provider that is known to give the best quality? Any ideas on how to go about this? Thanks, Adam

5 10

[mod_event_socket][pyswitch][B leg execute before A leg is answered]
by Bilal Abbasi 13 May '15

13 May '15

Hi users, Currently i am using pyswitch to connect to freeswitch mod_event_socket. I am originating a call and mapping its B-Leg to an IVR. So that is A-party picks up the call,he/she will listen some IVR. issue is before actually answering the call on A-leg IVR starts on B-leg. My originate command: self.eventsocket.apiOriginate("sofia/gateway/aptcl/"+NUM+"",application="bridge",appargs= "[DTMF="+DTMF+"]loopback/9665/default/XML", cidname="godson", cidnum="123" ,channelvars={"origination_uuid":uid,"DTMF":DTMF}) I am bridging the B-Leg with local extension 9665 where the IVR is mapped. can some one help me to sort-out the issue. Your help is highly appropriated. Freeswitch version: FreeSWITCH Version 1.4.18+git~20150312T185523Z~4eed221b69~64bit (git 4eed221 2015-03-12 18:55:23Z 64bit) Regards Bilal Abbasi

1 0

Video record problem
by Denis Jakovlev 13 May '15

13 May '15

Hi all, I'm trying to make a video recording of the conference calls (sound works without problems) Easy extension <extension name="conference_set_auto_outcall"> <condition field="destination_number" expression="^(12345)$"> <action application="answer"/> <action application="execute_extension" data="RECORD"/> <action application="set" data="conference_auto_outcall_timeout=3"/> <action application="set" data="conference_auto_outcall_flags=none"/> <action application="set" data="conference_auto_outcall_caller_id_name=$${effective_caller_id_name}"/> <action application="set" data="conference_auto_outcall_caller_id_number=$${effective_caller_id_number}"/> <action application="set" data="conference_auto_outcall_profile=default"/> <action application="conference_set_auto_outcall" data="{ignore_early_media=true}user/1005@$${domain}"/> <action application="conference" data="$1@simple"/> </condition> </extension> Plus extension for recording <extension name="video record that call"> <condition field="destination_number" expression="^RECORD$" break="on-true"> <action application="set" data="res=${bgapi uuid_setvar ${uuid} enable_file_write_buffering false}"/> <action application="set" data="res=${bgapi uuid_record ${uuid} start /usr/local/freeswitch/recordings/Video_${uuid}.fsv}"/> </condition> </extension> But I always have an error in the log. 2015-05-06 13:35:37.601687 [ERR] mod_fsv.c:702 You are asking to write 1024 bytes of data which is not supported. Please set enable_file_write_buffering=false to use .fsv format fe2f13e2-f3e3-11e4-91db-33c69ed9247a 2015-05-06 13:35:37.601687 [ERR] switch_ivr_async.c:1155 Error writing /usr/local/freeswitch/recordings/Video_fe2f13e2-f3e3-11e4-91db-33c69ed9247a.fsv 2015-05-06 13:35:37.721700 [ERR] mod_fsv.c:702 You are asking to write 1024 bytes of data which is not supported. Please set enable_file_write_buffering=false to use .fsv format fe2f13e2-f3e3-11e4-91db-33c69ed9247a 2015-05-06 13:35:37.721700 [ERR] switch_ivr_async.c:1155 Error writing /usr/local/freeswitch/recordings/Video_fe2f13e2-f3e3-11e4-91db-33c69ed9247a.fsv 2015-05-06 13:35:37.861731 [ERR] mod_fsv.c:702 You are asking to write 1024 bytes of data which is not supported. Please set enable_file_write_buffering=false to use .fsv format fe2f13e2-f3e3-11e4-91db-33c69ed9247a 2015-05-06 13:35:37.861731 [ERR] switch_ivr_async.c:1155 Error writing /usr/local/freeswitch/recordings/Video_fe2f13e2-f3e3-11e4-91db-33c69ed9247a.fsv 2015-05-06 13:35:37.981710 [ERR] mod_fsv.c:702 You are asking to write 1024 bytes of data which is not supported. Please set enable_file_write_buffering=false to use .fsv format fe2f13e2-f3e3-11e4-91db-33c69ed9247a 2015-05-06 13:35:37.981710 [ERR] switch_ivr_async.c:1155 Error writing /usr/local/freeswitch/recordings/Video_fe2f13e2-f3e3-11e4-91db-33c69ed9247a.fsv 2015-05-06 13:35:38.101712 [ERR] mod_fsv.c:702 You are asking to write 1024 bytes of data which is not supported. Please set enable_file_write_buffering=false to use .fsv format Although this option, I of course turn. Hence the question. Is there a possibility to include this option globally? Or how it can be solved differently? What am I doing wrong? -- S pozdravem, Ing.Denis Jakovlev mob.tel. 775-415-382

2 1

freeswitch systemd unit file for debian?
by Joseph Dickson 12 May '15

12 May '15

Happy Friday! I'm having trouble using latest release systemd unit file on Debian Jessie.. It looks like the unit file is the same in master, so I imagine the issue exists there too.. On my system (fresh Debian 8 install), I get the following failure when trying to start using the included unit file: May 01 12:48:22 XXX systemd[9119]: Failed at step CHDIR spawning /bin/mkdir: No such file or directory I'm new to systemd, but it looks like the problem is that the WorkingDirectory is set to /run/freeswitch. Trouble is that /run/freeswitch is created in an ExecStartPre statement. That's the best explanation I have for the CHDIR failure that systemd is complaining about. It looks like the only way to get /run/freeswitch created soon enough to be used as a WorkingDirectory is the tmpfiles.d mechanism that systemd has. Am I on the right track, or am I missing an obvious solution? Thanks! Joseph Dickson jdickson(a)evolvetsi.com

5 10

503 internal error for gateway calls....
by Dmitry Saratsky 12 May '15

12 May '15

Hi All! I have very strange problem on one of my switches... when I calling through 1 specific gateway (gateway's config well be shown later) - I get internal error with code 503 and freeswitch even do not try to send invite to the remote gateway... This gateway have very special configured as shown below (after debug output) and digest registration. Digest registration is passed fine for me! part of relevant console debug: ------------------------------------------------------------------ 2015-05-12 21:15:36.462865 [DEBUG] switch_core_state_machine.c:40 sofia/ext-ipv4/12121231122 Standard INIT 2015-05-12 21:15:36.462865 [DEBUG] switch_core_state_machine.c:48 (sofia/ext-ipv4/12121231122) State Change CS_INIT -> CS_ROUTING 2015-05-12 21:15:36.462865 [DEBUG] switch_core_session.c:1396 Send signal sofia/ext-ipv4/12121231122 [BREAK] 2015-05-12 21:15:36.462865 [DEBUG] switch_core_state_machine.c:512 (sofia/ext-ipv4/12121231122) State INIT going to sleep 2015-05-12 21:15:36.462865 [DEBUG] switch_core_state_machine.c:472 (sofia/ext-ipv4/12121231122) Running State Change CS_ROUTING 2015-05-12 21:15:36.462865 [DEBUG] switch_core_state_machine.c:528 (sofia/ext-ipv4/12121231122) State ROUTING 2015-05-12 21:15:36.462865 [DEBUG] mod_sofia.c:123 sofia/ext-ipv4/12121231122 SOFIA ROUTING 2015-05-12 21:15:36.462865 [DEBUG] switch_ivr_originate.c:67 (sofia/ext-ipv4/12121231122) State Change CS_ROUTING -> CS_CONSUME_MEDIA 2015-05-12 21:15:36.462865 [DEBUG] switch_core_session.c:1396 Send signal sofia/ext-ipv4/12121231122 [BREAK] 2015-05-12 21:15:36.462865 [DEBUG] switch_core_state_machine.c:528 (sofia/ext-ipv4/12121231122) State ROUTING going to sleep 2015-05-12 21:15:36.462865 [DEBUG] switch_core_state_machine.c:472 (sofia/ext-ipv4/12121231122) Running State Change CS_CONSUME_MEDIA 2015-05-12 21:15:36.462865 [DEBUG] switch_core_state_machine.c:547 (sofia/ext-ipv4/12121231122) State CONSUME_MEDIA 2015-05-12 21:15:36.462865 [DEBUG] switch_core_state_machine.c:547 (sofia/ext-ipv4/12121231122) State CONSUME_MEDIA going to sleep 2015-05-12 21:15:36.462865 [DEBUG] switch_core_session.c:1061 Send signal sofia/ext-ipv4/12121231122 [BREAK] 2015-05-12 21:15:36.462865 [DEBUG] switch_core_session.c:1061 Send signal sofia/ext-ipv4/12121231122 [BREAK] 2015-05-12 21:15:36.462865 [DEBUG] switch_core_session.c:1061 Send signal sofia/ext-ipv4/12121231122 [BREAK] 2015-05-12 21:15:36.462865 [DEBUG] switch_core_session.c:1061 Send signal sofia/ext-ipv4/12121231122 [BREAK] 2015-05-12 21:15:36.462865 [DEBUG] sofia.c:6623 Channel sofia/ext-ipv4/12121231122 entering state [calling][0] 2015-05-12 21:15:36.462865 [DEBUG] sofia.c:6623 Channel sofia/ext-ipv4/12121231122 entering state [terminated][503] 2015-05-12 21:15:36.462865 [NOTICE] sofia.c:7539 Hangup sofia/ext-ipv4/12121231122 [CS_CONSUME_MEDIA] [NORMAL_TEMPORARY_FAILURE] 2015-05-12 21:15:36.462865 [DEBUG] switch_channel.c:3222 Send signal sofia/ext-ipv4/12121231122 [KILL] 2015-05-12 21:15:36.462865 [DEBUG] switch_core_session.c:1396 Send signal sofia/ext-ipv4/12121231122 [BREAK] 2015-05-12 21:15:36.462865 [DEBUG] switch_core_state_machine.c:472 (sofia/ext-ipv4/12121231122) Running State Change CS_HANGUP 2015-05-12 21:15:36.462865 [DEBUG] switch_core_state_machine.c:735 (sofia/ext-ipv4/12121231122) Callstate Change DOWN -> HANGUP 2015-05-12 21:15:36.462865 [DEBUG] switch_core_state_machine.c:737 (sofia/ext-ipv4/12121231122) State HANGUP 2015-05-12 21:15:36.462865 [DEBUG] mod_sofia.c:413 Channel sofia/ext-ipv4/12121231122 hanging up, cause: NORMAL_TEMPORARY_FAILURE 2015-05-12 21:15:36.462865 [DEBUG] switch_core_state_machine.c:60 sofia/ext-ipv4/12121231122 Standard HANGUP, cause: NORMAL_TEMPORARY_FAILURE 2015-05-12 21:15:36.462865 [DEBUG] switch_core_state_machine.c:737 (sofia/ext-ipv4/12121231122) State HANGUP going to sleep 2015-05-12 21:15:36.462865 [DEBUG] switch_core_state_machine.c:504 (sofia/ext-ipv4/12121231122) State Change CS_HANGUP -> CS_REPORTING 2015-05-12 21:15:36.462865 [DEBUG] switch_core_session.c:1396 Send signal sofia/ext-ipv4/12121231122 [BREAK] 2015-05-12 21:15:36.462865 [DEBUG] switch_core_state_machine.c:472 (sofia/ext-ipv4/12121231122) Running State Change CS_REPORTING 2015-05-12 21:15:36.462865 [DEBUG] switch_core_state_machine.c:823 (sofia/ext-ipv4/12121231122) State REPORTING 2015-05-12 21:15:36.462865 [DEBUG] switch_core_state_machine.c:104 sofia/ext-ipv4/12121231122 Standard REPORTING, cause: NORMAL_TEMPORARY_FAILURE 2015-05-12 21:15:36.462865 [DEBUG] switch_core_state_machine.c:823 (sofia/ext-ipv4/12121231122) State REPORTING going to sleep 2015-05-12 21:15:36.462865 [DEBUG] switch_core_state_machine.c:498 (sofia/ext-ipv4/12121231122) State Change CS_REPORTING -> CS_DESTROY 2015-05-12 21:15:36.462865 [DEBUG] switch_core_session.c:1396 Send signal sofia/ext-ipv4/12121231122 [BREAK] 2015-05-12 21:15:36.462865 [DEBUG] switch_core_session.c:1623 Session 4 (sofia/ext-ipv4/12121231122) Locked, Waiting on external entities 2015-05-12 21:15:36.462865 [DEBUG] switch_ivr_originate.c:3720 Originate Resulted in Error Cause: 41 [NORMAL_TEMPORARY_FAILURE] 2015-05-12 21:15:36.462865 [INFO] mod_dptools.c:3244 Originate Failed. Cause: NORMAL_TEMPORARY_FAILURE ------------------------------------------------------------------ no packet was sent to remote gateway (checked with tcpdump), so it is internal error... relevant gateway is registered well: ------------------------------------------------------------------ ================================================================================================= Name gateway.name Profile ext-ipv4 Scheme Digest Realm realm.gateway.name Username +12223334455 Password yes >From <sip:+12223334455@realm.gateway.name> Contact <sip:+12223334455@1.1.1.1:5060 ;expires=3600;+g.oma.sip-im;+g.oma.sip-im.large-message;transport=udp;gw= gateway.name> Exten +12223334455 To sip:+12223334455@realm.gateway.name Proxy sip:realm.gateway.name Context ext Expires 3600 Freq 3600 Ping 0 PingFreq 0 PingTime 0.00 PingState 0/0/0 State REGED Status UP Uptime 554s CallsIN 0 CallsOUT 2 FailedCallsIN 0 FailedCallsOUT 2 ================================================================================================= ------------------------------------------------------------------ gateway config: ------------------------------------------------------------------ <include> <gateway name="gateway.name"> <param name="proxy" value="realm.gateway.name"/> <param name="register-proxy" value="10.10.10.10"/> <param name="contact-params" value="expires=3600;+g.oma.sip-im;+g.oma.sip-im.large-message"/> <param name="username" value="+12223334455"/> <param name="auth-username" value="+12223334455(a)realm.gateway.name"/> <param name="from-user" value="+12223334455"/> <param name="from-domain" value="realm.gateway.name"/> <param name="password" value="password"/> <param name="expire-seconds" value="3600"/> <param name="register" value="true"/> <param name="register-transport" value="udp"/> <param name="caller-id-in-from" value="false"/> <param name="extension-in-contact" value="+12223334455"/> <param name="retry-seconds" value="180"/> </gateway> </include> ------------------------------------------------------------------ what is special in this gateway configuration, is that gateway name is differers from proxy and both differs from register-proxy. this is required for my for successfully registration (bcz realm.gateway.name is not resolvable with DNS). In addition username is differs from auth-username - for some reason it is required by vendor... PS: FreeSWITCH (Version 1.5.15b git a41505f 2015-02-23 22:38:20Z 64bit) is ready Any ideas? Thanks, Dmitry.

2 2

Re-write of mod_vlc
by Aqs Younas 12 May '15

12 May '15

Hi, We are using mod_vlc for quite a long time for playing streams(urls) for our radio application, which have more than 250 concurrent listeners. Currently we are facing multiple issues while playing non mp3 streams (aac, flv). i) Freeswitch starts pooling ram untill our server is crashed due to ram starving or we manually restart our freeswitch to release ram.So, most of the time we manually restart freeswitch instances. If we play only mp3 streams with mod_shout. Freeswitch ram pooling problem is resolved. But we want to play streams other than mp3, that's why we are using mod_vlc. ii) AGC (Auto gain controller) some streams are higher in volume than others.There are more than 1000 stream, daily new streams are being added and old one deleted. So, we can't manually adjust their volumes by setting channel variables. iii) Couldn't play anything while mod_vlc is trying to buffer the stream. (Please wait while we are trying to connect your requested radio) So, I am here to ask is there any chance of re writing this module. Or any modification in up coming freeswitch releases. We are using FreeSWITCH Version 1.4.18~64bit ( 64bit) on Linux 66-226-75-55 3.2.0-4-amd64 #1 SMP Debian 3.2.63-2+deb7u2 x86_64 GNU/Linux Your replies would be much appreciated. Thanks.

2 2

ClueCon Weekly - May 13, 2015 - Nenad Corbic and Last mile troubleshooting with Sangoma Enterprise SBC¹s
by Ken Rice 12 May '15

12 May '15

Hey FreeSWITCHers, We would like to invite you all to join us tomorrow May 13th for ClueCon Weekly! This week Nenad Corbic of Sangoma will be joining us with the topic of ³Last mile troubleshooting with Sangoma Enterprise SBC¹s². This week, we will discuss how Carriers use CPE equipment to improve their last mile debugging. We will provide a quick overview of Sangoma SBC product line and outline features and scenarios that can help providers and enterprise keep their VoIP networks running effectively and sustain high quality of service. Join us at https://conference.freeswitch.org/verto/ and call 888 to join in live. Or watch on YouTube @ https://youtu.be/LTxnUPLxaRE Call starts at 1PM Eastern (1700 GMT) Wed May 13th! And If you have not registered for ClueCon, Visit ClueCon.com and register today! K -- Ken http://www.FreeSWITCH.org http://www.ClueCon.com http://www.OSTAG.org irc.freenode.net #freeswitch Twitter: @FreeSWITCH

1 0