- FreeSWITCH-users - FreeSWITCH Mailing Lists

Freeswitch Professional support
by Yigal Rachilevsky 17 Mar '14

17 Mar '14

Hello We are looking for Consultant / Professional support in Israel If anyone is interested, please reply me Thanks

1 0

Modifying SDPs for SIPREC
by Siri MM 17 Mar '14

17 Mar '14

Hi, I am trying to come up with a simplified SIPREC compliant client, which would playback an existing recorded file to a third party server. It is a requirement of SIP RFC that the INVITE message from the SIPREC client has SDP attributes such as a=sendonly, a=label and so on. Further Contact URI in the SIP header needs to be updated to include '+sip.src' feature tag, "siprec" option tag in the Require header etc. I was wondering if this is achievable in freeswitch in it's current state? Or am I required to come up with my own mod, such as mod_oreka, to send the INVITE with the required headers?

3 3

How to set callback for subclass CUSTOM event in perl with module ESL::Dispatch?
by "Гришин В.С." 16 Mar '14

16 Mar '14

I have FreeSWITCH Version 1.2.22~32bit ( 32bit) on Centos 5.9 In directory /usr/src/freeswitch-1.2.22/libs/esl/perl is script dispatch.pl I changed it to see CUSTOM events and spandsp::rxfaxpageresult subclass events, but heither CUSTOM events hor spandsp::rxfaxpageresult subclass not captured. #!/usr/bin/perl use ESL::Dispatch; use Data::Dumper; my $daemon = init ESL::Dispatch({}); $| = 1; sub worker { my $self = shift; print "I'm a worker\n"; } sub heartbeat { my $self = shift; my $event = shift; print Dumper $event; } sub channel_hangup { my $self = shift; my $event = shift; print Dumper $event; print "DO SQL GOODIES HERE!\n"; } sub custom { my $self = shift; my $event = shift; print Dumper $event; print "DO SQL GOODIES HERE!\n"; } $0 = "ESL::Dispatch rocks!"; $daemon->set_worker(\&worker, 2000); $daemon->set_callback("heartbeat", \&heartbeat); $daemon->set_callback("channel_hangup", \&channel_hangup); $daemon->set_callback("custom", \&custom); $daemon->set_callback('spandsp::rxfaxpageresult', \&custom); $daemon->run; I need catch the evnet only subclass spandsp:: (https://wiki.freeswitch.org/wiki/Mod_spandsp#Events) into CUSTOM event. Vladislav Grishin

2 2

DTMF
by Brian Chamberlain 16 Mar '14

16 Mar '14

Hi All, Is there a way to detect the dtmf mode on a leg of a call? At the moment we have a carrier who sometimes sends inband and sometimes sends 2833, sometimes proposes 2833 but only sends inband, etc... I've set dtmf-type on the profile in use with this carrier as none so whenever we send 183 or 200 freeswitch doesn't have any telephone-event in the SDP and the carrier sends inband. Its the only way I could guarantee consistent DTMF mode with this carrier. I have most cases worked out but I have an edge case where a customer is using a REALLY old PBX and needs inband and not 2833 When we send a call to this customer we offer 2833 in the proposal and the PBX sends back that it doesn't want any DTMF signalling which is correct. Unfortunately because I'm calling spandsp_start_dtmf even though there is no proposal from PBX freeswitch sends DTMF from carrier INBAND but also generates SIP info messages. This gives the dreaded double digit issue. If I comment spandsp_start_dtmf everything works great but I need spandsp_start_dtmf . Is there someway to detect that the dtmf-type is none on a channel and in that case don't call spandsp_start_dtmf or detect 2833 and do call it? I've been looking for variables I could check but can't find one.. I could drop these messages on our proxy but would prefer if there was a more elegant solution. Many Thanks for any assistance. Regards Brian

1 0

ZRTP SAS to non ZRTP call leg UA?
by Bill Ross 16 Mar '14

16 Mar '14

Hi; When a call is between a ZRTP UA and non ZRTP UA, with FS MITM, I want to give the user the SAS that the ZRTP call leg is using. I note there is a script: scriptd/lua/zrtp_sas_proxy.lua that is supposed to hook into the call flow by: <action application="export" data="nolocal:api_on_answer=luarun zrtp_sas_proxy.lua ${uuid}"/> This appears to display the SAS, and, I will add TTS for POTS phones. Q1: Where do I make the script install call above? Q2: Is there a better way, code? Thanks; Bill Ross

1 0

Re: [Freeswitch-users] Mistified by a registration issue
by Brian West 16 Mar '14

16 Mar '14

Firewall uname -a what CPU? What nat settings have you tried? Because you’ll notice on both the remote is receiving you from 5061 not 5060 as it should if your firewall is correctly configured. -- Brian West brian(a)freeswitch.org FreeSWITCH Solutions, LLC PO BOX 2531 Brookfield, WI 53008-2531 Twitter: @FreeSWITCH , @briankwest http://www.freeswitchbook.com http://www.freeswitchcookbook.com T: +1.918.420.9001 | F: +1.918.420.9002 | M: +1.918.424.WEST iNUM: +883 5100 1420 9001 ISN: 410*543 Skype:briankwest PGP Key: http://www.bkw.org/key.txt (AB93356707C76CED) On Mar 15, 2014, at 4:21 PM, Clive Lansink <clive(a)lansink.co.nz> wrote: > Hello listers. > > I have had Freeswitch running for quite some time now with few issues. But recently I installed a new router and came across this problem while configuring it. I have my Sofia external profile set to use port 5060 and my internal profile uses another port. So I followed my previous practice and set the router to forward UDP port 5060 to Freeswitch and that works properly. > I decided on this occasion that itmight be a good idea to also open up ports 16384-32768 so these are also forwarded to Freeswitch, as these are the RTP ports Freeswitch is set to use. I quickly found to my surprise that Freeswitch would fail to register with the external provider once I did this, but as soon as I stopped forwarding ports 16384-32768, Freeswitch would again register as it should. > > This seems really weird since I don't see how ports 16384-32768 can have any impact on the registration process on port 5060, and in any case whatever might be happening on these ports only involves Freeswitch so how can setting up such a port forwarding impact on registration. > > I would be pleased if anyone out there can answer this. > > I have included two SIP traces from the log. The first, trace1.txt, is the registration sequence when the ports are not forwarded. You can see Freeswitch sends a register, and the provider responds with an unauthorised which I think is the usual way it works. Freeswitch then responds with a register again and the provider responds with an ok. There are also some options packets in the sequence. So this is the regular pattern I see when Freeswitch is registered and remains registered. > > The second, trace2.txt, shows what happens when the ports 16384-32768 are set in the router to be forwarded to Freeswitch. Here we see Freeswitch sends a register packet, though it doesn't have the authentication information. I presume this is because at this point the gateway knows that it is not registered so this is like the first step in registering from scratch. Then we see the provider respond with an unauthorised message including (as before) the instruction for how to authenticate. But then Freeswitch doesn't respond with a follow-up attempt to register and eventually we see that it just reports that it timed out trying to register. > > I'm not a SIP expert but I don't see anything in the second dialog to explain why Freeswitch doesn't follow up to complete the registration even though it clearly does receive the unauthorised message with the authentication information. > > It would be great if someone could suggest what might be going on here. > > Thank you. > > > Clive Lansink > Email: Clive(a)Lansink.Co.NZ > Phone: +64 9 520-4242 > Mobile: +64 21 663-999 > Fax: +64 21 789-150 > <trace1.txt><trace2.txt>_________________________________________________________________________ > Professional FreeSWITCH Consulting Services: > consulting(a)freeswitch.org > http://www.freeswitchsolutions.com > > FreeSWITCH-powered IP PBX: The CudaTel Communication Server > http://www.cudatel.com > > Official FreeSWITCH Sites > http://www.freeswitch.org > http://wiki.freeswitch.org > http://www.cluecon.com > > FreeSWITCH-users mailing list > FreeSWITCH-users(a)lists.freeswitch.org > http://lists.freeswitch.org/mailman/listinfo/freeswitch-users > UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users > http://www.freeswitch.org

1 0

Re: [Freeswitch-users] Mistified by a registration issue
by Sean Devoy 15 Mar '14

15 Mar '14

Clive, Are you sure that is all that you are changing? Clearly the one that authorizes successfully has Authorization: Digest username="095290110", realm="voip", nonce="60f381b0", algorithm=MD5, uri="sip:sip.kiwilink.co.nz;transport=udp", response="a00513b45bea998c2f5dcdc89e9d8194" in the first sip packet. The one that fails does not include the "Authorization" information in the initial packet. Without knowing anything else, I would have guessed that the one that fails has the gateway configured with <param name="register" value="false"/> I realized you have basically indicated that is not changing, but if there is ANY chance you are using separate configurations, I would check your sipinterfaces.xml Hth, Sean -----Original Message----- From: freeswitch-users-bounces(a)lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Clive Lansink Sent: Saturday, March 15, 2014 5:21 PM To: Freeswitch users list Subject: [Freeswitch-users] Mistified by a registration issue Hello listers. I have had Freeswitch running for quite some time now with few issues. But recently I installed a new router and came across this problem while configuring it. I have my Sofia external profile set to use port 5060 and my internal profile uses another port. So I followed my previous practice and set the router to forward UDP port 5060 to Freeswitch and that works properly. I decided on this occasion that itmight be a good idea to also open up ports 16384-32768 so these are also forwarded to Freeswitch, as these are the RTP ports Freeswitch is set to use. I quickly found to my surprise that Freeswitch would fail to register with the external provider once I did this, but as soon as I stopped forwarding ports 16384-32768, Freeswitch would again register as it should. This seems really weird since I don't see how ports 16384-32768 can have any impact on the registration process on port 5060, and in any case whatever might be happening on these ports only involves Freeswitch so how can setting up such a port forwarding impact on registration. I would be pleased if anyone out there can answer this. I have included two SIP traces from the log. The first, trace1.txt, is the registration sequence when the ports are not forwarded. You can see Freeswitch sends a register, and the provider responds with an unauthorised which I think is the usual way it works. Freeswitch then responds with a register again and the provider responds with an ok. There are also some options packets in the sequence. So this is the regular pattern I see when Freeswitch is registered and remains registered. The second, trace2.txt, shows what happens when the ports 16384-32768 are set in the router to be forwarded to Freeswitch. Here we see Freeswitch sends a register packet, though it doesn't have the authentication information. I presume this is because at this point the gateway knows that it is not registered so this is like the first step in registering from scratch. Then we see the provider respond with an unauthorised message including (as before) the instruction for how to authenticate. But then Freeswitch doesn't respond with a follow-up attempt to register and eventually we see that it just reports that it timed out trying to register. I'm not a SIP expert but I don't see anything in the second dialog to explain why Freeswitch doesn't follow up to complete the registration even though it clearly does receive the unauthorised message with the authentication information. It would be great if someone could suggest what might be going on here. Thank you. Clive Lansink Email: Clive(a)Lansink.Co.NZ Phone: +64 9 520-4242 Mobile: +64 21 663-999 Fax: +64 21 789-150

1 0

Freeswitch and Apple Facetime?
by William King 15 Mar '14

15 Mar '14

After reading this blog post: http://blog.krisk.org/2013/09/learning-stupid-nat-tricks-from-apple.html and http://blog.krisk.org/2013/09/learning-stupid-nat-tricks-from-apple.html and the last couple weeks worth of Week in Reviews(the SDP compression support). I started wondering what is left to be able to have FS support Apple Facetime. Anyone have devices and interest to test? -- William King Senior Engineer Quentus Technologies, INC 1037 NE 65th St Suite 273 Seattle, WA 98115 Main: (877) 211-9337 Office: (206) 388-4772 Cell: (253) 686-5518 william.king(a)quentustech.com

5 5

Mistified by a registration issue
by Clive Lansink 15 Mar '14

15 Mar '14

Hello listers. I have had Freeswitch running for quite some time now with few issues. But recently I installed a new router and came across this problem while configuring it. I have my Sofia external profile set to use port 5060 and my internal profile uses another port. So I followed my previous practice and set the router to forward UDP port 5060 to Freeswitch and that works properly. I decided on this occasion that itmight be a good idea to also open up ports 16384-32768 so these are also forwarded to Freeswitch, as these are the RTP ports Freeswitch is set to use. I quickly found to my surprise that Freeswitch would fail to register with the external provider once I did this, but as soon as I stopped forwarding ports 16384-32768, Freeswitch would again register as it should. This seems really weird since I don't see how ports 16384-32768 can have any impact on the registration process on port 5060, and in any case whatever might be happening on these ports only involves Freeswitch so how can setting up such a port forwarding impact on registration. I would be pleased if anyone out there can answer this. I have included two SIP traces from the log. The first, trace1.txt, is the registration sequence when the ports are not forwarded. You can see Freeswitch sends a register, and the provider responds with an unauthorised which I think is the usual way it works. Freeswitch then responds with a register again and the provider responds with an ok. There are also some options packets in the sequence. So this is the regular pattern I see when Freeswitch is registered and remains registered. The second, trace2.txt, shows what happens when the ports 16384-32768 are set in the router to be forwarded to Freeswitch. Here we see Freeswitch sends a register packet, though it doesn't have the authentication information. I presume this is because at this point the gateway knows that it is not registered so this is like the first step in registering from scratch. Then we see the provider respond with an unauthorised message including (as before) the instruction for how to authenticate. But then Freeswitch doesn't respond with a follow-up attempt to register and eventually we see that it just reports that it timed out trying to register. I'm not a SIP expert but I don't see anything in the second dialog to explain why Freeswitch doesn't follow up to complete the registration even though it clearly does receive the unauthorised message with the authentication information. It would be great if someone could suggest what might be going on here. Thank you. Clive Lansink Email: Clive(a)Lansink.Co.NZ Phone: +64 9 520-4242 Mobile: +64 21 663-999 Fax: +64 21 789-150

1 0

Re: [Freeswitch-users] (no subject)
by Andre Demattia 15 Mar '14

15 Mar '14

What needs to be done for better performance on Windows? What modules ect need to be optimized? -----Original Message----- From: "Ryan Gholam" <ryangholam(a)gmail.com> Sent: ‎3/‎15/‎2014 5:35 AM To: "FreeSWITCH Users Help" <freeswitch-users(a)lists.freeswitch.org> Subject: Re: [Freeswitch-users] (no subject) Thank you mike for your reply is it better for me if i compile freeswitch on windows or is it the same when i install using exe . On Mar 14, 2014 7:05 PM, "Michael Jerris" <mike(a)jerris.com> wrote: We have done quite a lot of optimization work on linux, someone will need to do similar for windows and submit patches. On Mar 14, 2014, at 4:51 AM, Ryan Gholam <ryangholam(a)gmail.com> wrote: > Hi guys , I install freeswitch.exe from the original website i find a big difference from windows and ubuntu , Freeswitch is much more powerful on linux than on windows , how can i set maximum performance for freeswitch in windows it is reaching 150,000 Channels and throwing errors how can i use the ulimit -c and ulimit -d in windows . > _________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting(a)freeswitch.org http://www.freeswitchsolutions.com FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com FreeSWITCH-users mailing list FreeSWITCH-users(a)lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org

2 1