- FreeSWITCH-users - FreeSWITCH Mailing Lists

pass_rfc2833 in 1.4.15
by Grant Bagdasarian 10 Feb '15

10 Feb '15

Hello, Have there been any know issue with the variable pass_rfc2833? We recently upgraded to 1.4.15 and are facing some DTMF issues. Before on 1.2.13 we also had issues with DTMF, so I added the pass_rfc2833 variable, and the problems went away. Now again with 1.4.15, the variable is still enabled, but the problems happen again. Any ideas? Grant

2 2

Having issues accessing freeswitch.org?
by Brian West 10 Feb '15

10 Feb '15

Make sure your IP isn't on any spammers list. ;) Thanks, -- *Brian West* brian(a)freeswitch.org *Twitter: @FreeSWITCH , @briankwest* http://www.freeswitchbook.com http://www.freeswitchcookbook.com *T:*+19184209001 | *F:*+19184209002 | *M:*+1918424WEST (9378) *iNUM:*+883 5100 1420 9001 | *ISN:*410*543 | *Skype:*briankwest

6 15

Number of SIP concurrent calls based on first draft hardware spec
by Andrew Keil 09 Feb '15

09 Feb '15

To FreeSWITCH users, My client in the UK is asking how many concurrent SIP calls could be handled by the current production release of FreeSWITCH (based on the first draft of the hardware spec attached and the service usage shown below). The services will use the following and be written in Lua running inside FreeSWITCH: - G711 -A-law audio playback/record (since E1) - so no transcoding - DTMF detection - General string and number handling - which lua would do very well - TCP socket communication - No text to speech or speech recognition - Limited conference requirements (ie. Inbound call conferenced with an outbound call on the same server) Initially since they are a "windows-house" they intend to run the Windows 64-bit version of FreeSWITCH on Windows Server 2012 R2 Standard Edition. Eventually I hope to move them to Linux, however one step at a time. If stating how many potential concurrent SIP calls based on my hardware spec attached is too difficult, then the other way of stating your hardware spec (just the basics CPU/RAM/Hard disk subsystem) and how many concurrent SIP calls you can take would also help. I appreciate any assistance that anyone can give. Thanks in advance, Andrew Keil

3 2

FreeSWITCH Week in Review (Master Branch) January 31st-February 6th
by Ken Rice 09 Feb '15

09 Feb '15

New Post on freeswitch.org from kathleen check it out at http://ift.tt/1CMyefz FreeSWITCH Week in Review (Master Branch) January 31st-February 6th Hello, again. This past week in the FreeSWITCH master branch we had 8 commits. It was a quiet week with some small updates: updated freeswitch.spec for flite-2.0.0 and some minor updates to the mod_foo clean targets. New features that were added: FS-7149 Update freeswitch.spec for flite-2.0.0 FS-7245 Don’t rebuild core on mod_foo-clean targets The following bugs were squashed: FS-7235 Fix for call recording deleting recorded files in append mode if appended data is shorter than RECORD_MIN_SEC FS-7236 FS-7236 Added lock to prevent a race condition and segfault in mod_conference FS-7236 Fix code before declaration in mod_conference

1 0

NAT traversal: replacing rttproxy with external RTP IP address in FS
by Ben Hood 09 Feb '15

09 Feb '15

Hi all, TL;DR: Does anybody know of a way to convince FS to insert an external RTP IP into the SDP even if the signalling is coming from a client behind the same NAT? I'm currently using kamailio and rtpproxy behind a NAT in conjunction with FS, but I'd like to eliminate rtpproxy from the equation and get FS to handle all of the RTP NAT. I've set the ext-rtp-ip in the SIP profile and FS seems to have accepted it, but FS still sends out SDPs with the local IP address in them. I'm assuming that this is happening because the client that is forwarding the INVITE is behind the same NAT and therefore FS is not inserting the external IP address into the SDP, but I might be wrong. I'm using version 1.4.15-1. Currently I've got this topology for signalling: CLIENT <-> PUBLIC INTERNET <-> NAT <-> KAMAILIO <-> FS And this topology for media: CLIENT <-> PUBLIC INTERNET <-> NAT <-> RTPPROXY <-> FS whereby rttproxy advertises itself on a public IP and the external firewall has static port forwards set up for ephemeral RTP ports. FS is a B2BUA in this setup. I'd like to replace the media topology with this: CLIENT <-> PUBLIC INTERNET <-> NAT <-> FS and port forward RTP to the FS instance in the firewall. As a proof of concept hack, I was able to get end to end media going between two different clients, by rewriting the local IP of the FS instance in the outgoing SDP on the outbound leg in kamailio. But I'd like to be able to set the correct external IP as part of the normal SDP patching process in FS. Thanks, Ben

2 4

mod_vlc taking more time in playing a stream than mod_shout
by Aqs Younas 09 Feb '15

09 Feb '15

Hi, Users. I am facing an issue when trying to play a stream with mod_vlc i hear voice after 8 to 10 seconds after getting answer. But when i play same stream with mod_shout i get voice instantly. Why mod_vlc is taking much time in playing the stream? Is there any way to reduce this time? All thoughts are welcome. Thanks.

2 3

Freeswitch behind a WS Proxy
by Christian Hoene 09 Feb '15

09 Feb '15

Hello, we have placed Freeswitch behind a Apache ws tunnel proxy. Now, Freeswitch give me an error message because the sip_via is not correct. nta.c:3146 agent_check_request_via() nta: Via check: invalid transport "SIP/2.0/WSS" from 127.0.0.1:39964 nta.c:2990 agent_recv_request() nta: REGISTER (1) has invalid Via How do I modify the sip via entry that Freeswitch is expecting? Where to set the sip_via_address/protocol/port variables? Thanks CH

2 2

SWITCH_EVENT_NOTIFY will not send 'body' or 'content-length'
by Vik Killa 09 Feb '15

09 Feb '15

When firing a NOTIFY event using sendevent, mod_sofia does not accept 'body' or 'content-length' from the event; My goal is to be able to send custom 'dialog' events to send NOTIFYs to UAs I noticed FS will send the dialog event if I don't include the 'content-length' header and body. Here is an example event that works. mod_sofia will parse the event and fire the NOTIFY sendevent NOTIFY profile: internal event-string: dialog content-type: application/dialog-info+xml user: 1002 host: 3.local to-uri: 1002(a)3.local from-uri: 1002(a)3.local contact-uri: sip:1002@192.168.0.109:10536;fs_path=sip:192.168.207.156:5060 if I add content-length and a body, mod_sofia does not fire the NOTIFY: content-length: 493 <?xml version="1.0"?><dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="3" state="full" entity="sip:orbit+lot@3.local"><dialog id="lot" direction="initiator"><state>early</state><local><identity display="TEST">sip:lot@3.local;proto=orbit</identity><target uri="sip:lot@3.local;proto=orbit"><param pname="+sip.rendering" pvalue="no"/></target></local><remote><identity display="park">sip:lot</identity><target uri="sip:park+lot"/></remote></dialog></dialog-info> I noticed in mod_sofia.c, where it listens for SWITCH_EVENT_NOTIFY it does not parse the 'content-length' header but it does look for the body and even tries to send it in nua_notify() Is this the desired behavior? If SWITCH_EVENT_NOTIFY is trying to send the body of the event, shouldn't it look for a content-length header or try to create one based on the body? If it is not the desired behavior, could this be a bug? Thank you in advance.

2 2

Can't build VS2013 Windows
by Malay Thakershi 09 Feb '15

09 Feb '15

Hello, I tried to build for Win32 target but I get these errors. Error 84 error C2220: warning treated as error - no 'object' file generated C:\FS_GIT\libs\sofia-sip\libsofia-sip-ua\tport\ws.c 314 1 libsofia_sip_ua_static Error 88 error C2220: warning treated as error - no 'object' file generated C:\FS_GIT\libs\sofia-sip\libsofia-sip-ua\stun\stun_common.c 784 1 libsofia_sip_ua_static Error 91 error C2220: warning treated as error - no 'object' file generated C:\FS_GIT\libs\sofia-sip\libsofia-sip-ua\stun\stun.c 2192 1 libsofia_sip_ua_static Error 170 error LNK1181: cannot open input file 'C:\FS_GIT\libs\win32\sofia\Win32\Debug\libsofia_sip_ua_static.lib' C:\FS_GIT\src\mod\asr_tts\mod_unimrcp\LINK mod_unimrcp Error 187 error LNK1181: cannot open input file 'C:\FS_GIT\libs\win32\sofia\Win32\Debug\libsofia_sip_ua_static.lib' C:\FS_GIT\src\mod\endpoints\mod_sofia\LINK mod_sofia Machine where I am building are 64-bit but my server where FS needs to be deployed is 32-bit. I tried building on two different machines with latest clones. x64 builds fine. Any suggestions. Thanks.

2 1

PRI channels get stuck in HANGUP state.
by Thomas Johnson 09 Feb '15

09 Feb '15

I am trying to track down an issue where FreeTDM seems to get confused about the state of channels on my PRI. The state seems to occur on origination; FreeTDM opens a channel, and immediately closes it, logging REQUESTED_CHAN_UNAVAIL. The channel then sits in the HANGUP state, preventing inbound calls and logging the following error. 2015-02-03 08:25:04.774438 [ERR] ftmod_libpri.c:1883 [s1c1][1:1] -- Selected channel is already in use I can resolve this by restarting Freeswitch, but it is obviously less-than-ideal. A bit of relevant logging is at the end of this message. It seems to occur immediately after a hangup on the same channel; could I be triggering a race condition? https://freeswitch.org/jira/browse/OPENZAP-220 seems to have similar symptoms, but manifests as a different error number. I upgraded Freeswitch last week (1.5.15b git 608d3e2 2015-01-22 09:09:59Z 64bit) to ensure that I had the patch referenced by the ticket. Is it possible that this could be a cabling issue? We're running Freeswitch on FreeBSD 10.0 amd64. I'm happy to provide any other information that would be useful. I'm [relatively] new to Freeswitch, so please be gentle ;-). Thank you, Tom 2015-02-03 14:34:23.437947 [DEBUG] ftmod_libpri.c:1451 -- Hangup ACK on channel 1:1 2015-02-03 14:34:23.437947 [DEBUG] ftmod_libpri.c:1460 [s1c1][1:1] Changed state from HANGUP to HANGUP_COMPLETE 2015-02-03 14:34:23.437947 [DEBUG] ftdm_state.c:541 [s1c1][1:1] Executing state processor for HANGUP_COMPLETE 2015-02-03 14:34:23.437947 [DEBUG] ftmod_libpri.c:942 -- 1:1 STATE [HANGUP_COMPLETE] 2015-02-03 14:34:23.437947 [DEBUG] ftmod_libpri.c:950 [s1c1][1:1] Completed state change from HANGUP to HANGUP_COMPLETE in 0 ms 2015-02-03 14:34:23.437947 [DEBUG] ftmod_libpri.c:1268 [s1c1][1:1] Changed state from HANGUP_COMPLETE to DOWN 2015-02-03 14:34:23.437947 [DEBUG] ftdm_state.c:541 [s1c1][1:1] Executing state processor for DOWN 2015-02-03 14:34:23.437947 [DEBUG] ftmod_libpri.c:942 -- 1:1 STATE [DOWN] 2015-02-03 14:34:23.437947 [DEBUG] ftmod_libpri.c:950 [s1c1][1:1] Completed state change from HANGUP_COMPLETE to DOWN in 0 ms 2015-02-03 14:34:23.437947 [DEBUG] ftdm_io.c:3194 [s1c1][1:1] DTMF debug is already disabled 2015-02-03 14:34:23.437947 [DEBUG] ftdm_io.c:3226 [s1c1][1:1] No need to disable input dump 2015-02-03 14:34:23.437947 [DEBUG] ftdm_io.c:3257 [s1c1][1:1] No need to disable output dump 2015-02-03 14:34:23.437947 [DEBUG] mod_freetdm.c:2707 got clear channel sig [RELEASED] 2015-02-03 14:34:23.437947 [DEBUG] ftdm_io.c:6873 Cleared call with id 37 2015-02-03 14:34:23.437947 [DEBUG] ftdm_io.c:2999 [s1c1][1:1] channel done 2015-02-03 14:34:23.437947 [DEBUG] ftmod_libpri.c:978 -- Closed channel 1:1 2015-02-03 14:34:23.679236 [DEBUG] switch_ivr_originate.c:2099 Parsing global variables 2015-02-03 14:34:23.679236 [DEBUG] switch_event.c:1688 Parsing variable [ignore_early_media]=[true] 2015-02-03 14:34:23.679236 [DEBUG] switch_event.c:1688 Parsing variable [file]=[46475.tif] 2015-02-03 14:34:23.679236 [DEBUG] switch_event.c:1688 Parsing variable [jobid]=[293102] 2015-02-03 14:34:23.679236 [INFO] ftmod_zt.c:671 Setting echo cancel to 64 taps for 1:1 2015-02-03 14:34:23.679236 [DEBUG] mod_freetdm.c:403 Set codec PCMU 20ms 8d09030a-e4ab-e411-905b-0026b95c8602 2015-02-03 14:34:23.679236 [DEBUG] mod_freetdm.c:1251 Connect outbound channel FreeTDM/1:1/18019941076 8d09030a-e4ab-e411-905b-0026b95c8602 2015-02-03 14:34:23.679236 [NOTICE] switch_channel.c:1055 New Channel FreeTDM/1:1/18019941076 [8d09030a-e4ab-e411-905b-0026b95c8602] 8d09030a-e4ab-e411-905b-0026b95c8602 2015-02-03 14:34:23.679236 [DEBUG] mod_freetdm.c:1260 (FreeTDM/1:1/18019941076) State Change CS_NEW -> CS_INIT 8d09030a-e4ab-e411-905b-0026b95c8602 2015-02-03 14:34:23.679236 [DEBUG] switch_core_session.c:1388 Send signal FreeTDM/1:1/18019941076 [BREAK] 8d09030a-e4ab-e411-905b-0026b95c8602 2015-02-03 14:34:23.679236 [DEBUG] mod_freetdm.c:1279 Attached session 8d09030a-e4ab-e411-905b-0026b95c8602 to channel 1:1 2015-02-03 14:34:23.679236 [DEBUG] mod_freetdm.c:1767 [s1c1][1:1] Changed state from DOWN to DIALING 2015-02-03 14:34:23.778359 [DEBUG] ftdm_state.c:541 [s1c1][1:1] Executing state processor for DIALING 2015-02-03 14:34:23.778359 [DEBUG] ftmod_libpri.c:942 -- 1:1 STATE [DIALING] 2015-02-03 14:34:23.778359 [DEBUG] mod_freetdm.c:2707 got clear channel sig [DIALING] 2015-02-03 14:34:23.778359 [DEBUG] ftmod_libpri.c:950 [s1c1][1:1] Completed state change from DOWN to DIALING in 95 ms 8d09030a-e4ab-e411-905b-0026b95c8602 2015-02-03 14:34:23.778359 [DEBUG] switch_core_state_machine.c:472 (FreeTDM/1:1/18019941076) Running State Change CS_INIT 8d09030a-e4ab-e411-905b-0026b95c8602 2015-02-03 14:34:23.778359 [DEBUG] switch_core_state_machine.c:512 (FreeTDM/1:1/18019941076) State INIT 8d09030a-e4ab-e411-905b-0026b95c8602 2015-02-03 14:34:23.778359 [DEBUG] mod_freetdm.c:430 (FreeTDM/1:1/18019941076) State Change CS_INIT -> CS_ROUTING 8d09030a-e4ab-e411-905b-0026b95c8602 2015-02-03 14:34:23.778359 [DEBUG] switch_core_session.c:1388 Send signal FreeTDM/1:1/18019941076 [BREAK] 8d09030a-e4ab-e411-905b-0026b95c8602 2015-02-03 14:34:23.778359 [DEBUG] switch_core_state_machine.c:512 (FreeTDM/1:1/18019941076) State INIT going to sleep 8d09030a-e4ab-e411-905b-0026b95c8602 2015-02-03 14:34:23.778359 [DEBUG] switch_core_state_machine.c:472 (FreeTDM/1:1/18019941076) Running State Change CS_ROUTING 8d09030a-e4ab-e411-905b-0026b95c8602 2015-02-03 14:34:23.778359 [DEBUG] switch_core_state_machine.c:528 (FreeTDM/1:1/18019941076) State ROUTING 2015-02-03 14:34:23.778359 [DEBUG] mod_freetdm.c:453 FreeTDM/1:1/18019941076 CHANNEL ROUTING 8d09030a-e4ab-e411-905b-0026b95c8602 2015-02-03 14:34:23.778359 [DEBUG] switch_ivr_originate.c:67 (FreeTDM/1:1/18019941076) State Change CS_ROUTING -> CS_CONSUME_MEDIA 8d09030a-e4ab-e411-905b-0026b95c8602 2015-02-03 14:34:23.778359 [DEBUG] switch_core_session.c:1388 Send signal FreeTDM/1:1/18019941076 [BREAK] 8d09030a-e4ab-e411-905b-0026b95c8602 2015-02-03 14:34:23.778359 [DEBUG] switch_core_state_machine.c:528 (FreeTDM/1:1/18019941076) State ROUTING going to sleep 8d09030a-e4ab-e411-905b-0026b95c8602 2015-02-03 14:34:23.778359 [DEBUG] switch_core_state_machine.c:472 (FreeTDM/1:1/18019941076) Running State Change CS_CONSUME_MEDIA 8d09030a-e4ab-e411-905b-0026b95c8602 2015-02-03 14:34:23.778359 [DEBUG] switch_core_state_machine.c:547 (FreeTDM/1:1/18019941076) State CONSUME_MEDIA 8d09030a-e4ab-e411-905b-0026b95c8602 2015-02-03 14:34:23.778359 [DEBUG] switch_core_state_machine.c:547 (FreeTDM/1:1/18019941076) State CONSUME_MEDIA going to sleep 2015-02-03 14:34:23.799281 [DEBUG] ftmod_libpri.c:1466 -- Hangup on channel 1:1 2015-02-03 14:34:23.799281 [DEBUG] ftmod_libpri.c:1479 [s1c1][1:1] Changed state from DIALING to TERMINATING 2015-02-03 14:34:23.799281 [DEBUG] ftdm_state.c:541 [s1c1][1:1] Executing state processor for TERMINATING 2015-02-03 14:34:23.799281 [DEBUG] ftmod_libpri.c:942 -- 1:1 STATE [TERMINATING] 2015-02-03 14:34:23.799281 [DEBUG] ftmod_libpri.c:950 [s1c1][1:1] Completed state change from DIALING to TERMINATING in 0 ms 2015-02-03 14:34:23.799281 [DEBUG] ftdm_io.c:6216 [s1c1][1:1] Scheduling safety hangup timer 2015-02-03 14:34:23.799281 [DEBUG] mod_freetdm.c:2707 got clear channel sig [STOP] 8d09030a-e4ab-e411-905b-0026b95c8602 2015-02-03 14:34:23.799281 [NOTICE] mod_freetdm.c:2731 Hangup FreeTDM/1:1/18019941076 [CS_CONSUME_MEDIA] [REQUESTED_CHAN_UNAVAIL] 8d09030a-e4ab-e411-905b-0026b95c8602 2015-02-03 14:34:23.799281 [DEBUG] switch_channel.c:3222 Send signal FreeTDM/1:1/18019941076 [KILL] 8d09030a-e4ab-e411-905b-0026b95c8602 2015-02-03 14:34:23.799281 [DEBUG] switch_core_session.c:1388 Send signal FreeTDM/1:1/18019941076 [BREAK] 8d09030a-e4ab-e411-905b-0026b95c8602 2015-02-03 14:34:23.799281 [DEBUG] switch_core_state_machine.c:472 (FreeTDM/1:1/18019941076) Running State Change CS_HANGUP 8d09030a-e4ab-e411-905b-0026b95c8602 2015-02-03 14:34:23.799281 [DEBUG] switch_core_state_machine.c:735 (FreeTDM/1:1/18019941076) Callstate Change DOWN -> HANGUP 8d09030a-e4ab-e411-905b-0026b95c8602 2015-02-03 14:34:23.799281 [DEBUG] switch_core_state_machine.c:737 (FreeTDM/1:1/18019941076) State HANGUP 2015-02-03 14:34:23.799281 [DEBUG] mod_freetdm.c:544 [1:1] FreeTDM/1:1/18019941076 CHANNEL HANGUP ENTER 2015-02-03 14:34:23.799281 [DEBUG] mod_freetdm.c:623 [s1c1][1:1] Changed state from TERMINATING to HANGUP 2015-02-03 14:34:23.819045 [DEBUG] switch_ivr_originate.c:3719 Originate Resulted in Error Cause: 44 [REQUESTED_CHAN_UNAVAIL] 2015-02-03 14:34:23.918415 [DEBUG] ftdm_state.c:541 [s1c1][1:1] Executing state processor for HANGUP 2015-02-03 14:34:23.918415 [DEBUG] ftmod_libpri.c:942 -- 1:1 STATE [HANGUP] 2015-02-03 14:34:23.918415 [DEBUG] ftmod_libpri.c:950 [s1c1][1:1] Completed state change from TERMINATING to HANGUP in 109 ms 2015-02-03 14:34:23.918415 [DEBUG] mod_freetdm.c:643 [1:1] FreeTDM/1:1/18019941076 CHANNEL HANGUP EXIT

2 2