January 2010 - FreeSWITCH-users - FreeSWITCH Mailing Lists

Issue with openzap and DTMF
by François Legal 14 Jan '10

14 Jan '10

Hello, yesterday, while trying some new extensions with play_and_get_dtmf, I noticed a strange behaviour of freeswitch. The configuration is as follows : An FXS port is bridged to an FXO (say FXO1) port for calling (through my carrier) another FXO (say FXO2) port. The call incoming on FXO2 reaches some extension which does answer then play_and_get_dtmf (or read). So I dial the digits I want, and for each dialed digit, I get it twice in the resultant variable. Now if I reach the extension by calling in from a cell phone, I get exactly the digits I dialed. This seems to me as a problem in openzap. I just wanted to report. François

1 0

Attend CampKDE Jan 15-18 via Voice over Internet (VOIP), BerkeleyTIP
by giovanni_re 14 Jan '10

14 Jan '10

This weekend is CampKDE in San Diego, California, USA. For those who would like to participate, but can't physically attend, the BerkeleyTIP group will (unofficially, as a public service) provide assistance to everyone who would like to communicate via voice about &/or with the conference, & other KDE community members, globally. [VOIP communication is typically free (no money $ cost) to people with internet access.] Join #berkeleytip on irc.freenode.net, & we will do our best (depending on availability of BTIP people) to help people get on VOIP in order to talk about KDE, or whatever. You are also invited to join the BerkeleyTIP mailing list, & ask any help or other questions there. http://groups.google.com/group/BerkTIPGlobal Here's the announcement there: CampKDE Jan 15-18 SanDiego, VOIP & Ride Share; BerkeleyTIP http://groups.google.com/group/BerkTIPGlobal/t/53cbf00b987b66e0 I'll be announcing this on some KDE related mailing lists. When (if) I get time, I'll locate the CampKDE organizers, & email them telling them BTIP is helping KDE community members with this unofficially, & asking them if they'd like to try to do something officially in arranging global VOIP for the KDE community interested in CampKDE. Here is the VOIP HowTo page for BerkeleyTIP: http://sites.google.com/site/berkeleytip/remote-attendance There are 2 ways to join the VOIP conference: 1) Computer VOIP globally using a sw client & headset & mic, & 2) Dial in with land or cell phone to a phone # in Washington state, USA (free, no $ money cost, if you have free long distance phone service). BerkeleyTIP: http://sites.google.com/site/berkeleytip/ ===== So, join on the #berkeleytip freenode irc channel, or the mailing list, & we'll do our best to help you get on the global conference to discuss KDE via voice communication. :)

1 0

Sangoma PRI installation for FreeSWITCH
by Magesh R 14 Jan '10

14 Jan '10

Dear All, I have installed Sangoma PRI card in machine with following steps, * wget ftp://ftp.sangoma.com/linux/custom/3.5/wanpipe-3.5.8.7.tgz * tar -xvfz wanpipe-3.5.8.7.tgz * cd wanpipe-3.5.8.7 * make openzap * make install * make install_pri I have executed "wanrouter hwprobe" command it prints the following details, 1 . AFT-A102-SH : SLOT=4 : BUS=3 : IRQ=11 : CPU=A : PORT=1 : HWEC=0 : V=36 2 . AFT-A102-SH : SLOT=4 : BUS=3 : IRQ=11 : CPU=A : PORT=2 : HWEC=0 : V=36 Card Cnt: A101-2=1 Next I have executed wancfg_fs script to configure the sangoma for freeswitch. It creates the following configuration files * wanpipe1.conf * wanpipe2.conf * smg_prid.conf * openzap.conf * openzap.conf.xml I have attached those files. I have started the wanrouter and printed the wanrouter status, Wanrouter Status: Device name | Protocol | Station | Status | wanpipe1 | AFT TE1 | N/A | Connected | wanpipe2 | AFT TE1 | N/A | Disconnected | Next I have started the smg_ctrl, but it failed to start. It prints the following things, smg_ctrl start Starting processes... Loading SCTP...OK Starting sangoma_prid...OK sangoma_prid failed to start check /var/log/sangoma_mgd.log for errors Stopping running processes... safe_sangoma not running... sangoma_prid is stopped Removing PID files...done I have checked /var/log/sangoma_mgd.log file. But nothing was there. Could any please tell me where I made mistake? Thanks, Mag

4 3

rtp-autoflush
by Mouncif Benniane 14 Jan '10

14 Jan '10

We are running freeswitch with bypass_media=true, if we change the following settings : rtp-autoflush-during-bridge and rtp-autoflush does it affect anything? Thanks

3 7

10 seconds delay on fallback
by Sergey Okhapkin 14 Jan '10

14 Jan '10

To implement fallback to backup PSTN routes and do LCR my dialplan executes the following commands: set execute_on_answer=set hangup_after_bridge=true set some custom channel variables bridge sofia/gateway1/number set some custom channel variables bridge sofia/gateway2/number .... This generally works fine if gateway1 returns SIP error, dialplan sets channel variables to another values and calls gateway2 immediately. But if GW1 responds with 183 early media and SIP error after that, bad thing happens - dialplan continues immediately, sets channel variables, executes bridge application, but INVITE to GW2 is sent after 10 seconds delay. Caller gets 10 extra seconds of post dial delay. I suspect the delay happens because of attempt to read audio frame, switch_ivr_originate() has the following lines: if (switch_channel_media_ready(caller_channel)) { tstatus = switch_core_session_read_frame() ... Any advice how to avoid extra delay in this situation?

3 4

Re: [Freeswitch-users] Cisco media gateway and DTMF
by Dan 13 Jan '10

13 Jan '10

Thanks for your reply, Wireshark shows all of the digits coming through cleanly, in the case below (also on pastebin) its 0951*72789, freeswitch does not seem to be processing one or more of the rtp events. Is there some specific debugging I should turn on that might give me some more info on why freeswitch is not processing some of these events? http://pastebin.freeswitch.org/11780 449 12.280148 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Zero 0 450 12.285108 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Zero 0 451 12.290082 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Zero 0 452 12.335129 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Zero 0 (end) 453 12.340124 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Zero 0 (end) 454 12.345124 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Zero 0 (end) 455 12.365162 192.168.3.21 192.168.6.130 RTP PT=ITU-T G.711 PCMU, SSRC=0x1D050315, Seq=21862, Time=359229277, Mark 456 12.380167 192.168.3.21 192.168.6.130 RTP PT=ITU-T G.711 PCMU, SSRC=0x1D050315, Seq=21863, Time=359229605 461 12.385248 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Nine 9 462 12.385253 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Nine 9 465 12.390163 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Nine 9 466 12.435211 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Nine 9 (end) 467 12.440201 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Nine 9 (end) 468 12.445205 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Nine 9 (end) 469 12.480251 192.168.3.21 192.168.6.130 RTP PT=ITU-T G.711 PCMU, SSRC=0x1D050315, Seq=21870, Time=359230405 470 12.485275 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Five 5 471 12.485284 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Five 5 472 12.490251 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Five 5 475 12.535277 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Five 5 (end) 476 12.540287 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Five 5 (end) 477 12.545287 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Five 5 (end) 478 12.580337 192.168.3.21 192.168.6.130 RTP PT=ITU-T G.711 PCMU, SSRC=0x1D050315, Seq=21877, Time=359231197 484 12.585337 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF One 1 485 12.585343 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF One 1 486 12.590362 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF One 1 492 12.635393 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF One 1 (end) 493 12.640368 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF One 1 (end) 494 12.645369 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF One 1 (end) 495 12.665406 192.168.3.21 192.168.6.130 RTP PT=ITU-T G.711 PCMU, SSRC=0x1D050315, Seq=21884, Time=359231677, Mark 496 12.680431 192.168.3.21 192.168.6.130 RTP PT=ITU-T G.711 PCMU, SSRC=0x1D050315, Seq=21885, Time=359232005 497 12.680438 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Star * 502 12.685408 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Star * 506 12.690412 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Star * 507 12.735450 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Star * (end) 508 12.740453 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Star * (end) 509 12.745469 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Star * (end) 511 12.780526 192.168.3.21 192.168.6.130 RTP PT=ITU-T G.711 PCMU, SSRC=0x1D050315, Seq=21892, Time=359232805 512 12.780534 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Seven 7 513 12.785502 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Seven 7 514 12.790492 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Seven 7 515 12.835544 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Seven 7 (end) 516 12.840537 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Seven 7 (end) 517 12.845537 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Seven 7 (end) 523 12.880582 192.168.3.21 192.168.6.130 RTP PT=ITU-T G.711 PCMU, SSRC=0x1D050315, Seq=21899, Time=359233605 524 12.885593 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Two 2 525 12.885599 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Two 2 526 12.890580 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Two 2 528 12.935618 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Two 2 (end) 529 12.940618 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Two 2 (end) 530 12.945618 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Two 2 (end) 531 12.965656 192.168.3.21 192.168.6.130 RTP PT=ITU-T G.711 PCMU, SSRC=0x1D050315, Seq=21906, Time=359234077, Mark 532 12.980659 192.168.3.21 192.168.6.130 RTP PT=ITU-T G.711 PCMU, SSRC=0x1D050315, Seq=21907, Time=359234413 538 12.985690 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Seven 7 539 12.985695 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Seven 7 540 12.990657 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Seven 7 541 13.035703 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Seven 7 (end) 542 13.040701 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Seven 7 (end) 543 13.045700 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Seven 7 (end) 544 13.080762 192.168.3.21 192.168.6.130 RTP PT=ITU-T G.711 PCMU, SSRC=0x1D050315, Seq=21914, Time=359235205 545 13.080768 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Eight 8 546 13.085736 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Eight 8 547 13.090798 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Eight 8 549 13.135809 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Eight 8 (end) 550 13.140780 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Eight 8 (end) 551 13.145793 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Eight 8 (end) 554 13.180827 192.168.3.21 192.168.6.130 RTP PT=ITU-T G.711 PCMU, SSRC=0x1D050315, Seq=21921, Time=359236005 558 13.185847 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Nine 9 559 13.185854 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Nine 9 560 13.190821 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Nine 9 566 13.235872 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Nine 9 (end) 567 13.240864 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Nine 9 (end) 568 13.245872 192.168.3.21 192.168.6.130 RTP EVENT Payload type=RTP Event, DTMF Nine 9 (end) ----- Original Message ----- From: "Brian West" <brian(a)freeswitch.org> To: freeswitch-users(a)lists.freeswitch.org Sent: Wednesday, January 13, 2010 12:39:52 PM Subject: Re: [Freeswitch-users] Cisco media gateway and DTMF Cisco gateways can detect DTMF at random if you have kids screaming or loud noises in the background... very unreliable. /b On Jan 13, 2010, at 1:36 PM, Dan wrote: Sorry, I should have made that more clear, this is using 2833. As I mentioned tcpdump shows all the digits coming through as DTMF events on the RTP stream (and all the correct DTMF digits are coming through). _______________________________________________ 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 3

Cisco media gateway and DTMF
by Dan 13 Jan '10

13 Jan '10

Hi guys, I'm having an issue with DTMF detection from our cisco 5300 gateways. DTMF detection has been working great when someone was manually inputing the digits (ie there are small pauses between the DTMF digits), but when the other end is sending those digits from say a speed dial or programmed dial string and can send the DTMF digits one right after the other we start to drop one or more digits about 75% of the time. I upgraded to trunk this morning and have tried everything that was listed on http://wiki.freeswitch.org/wiki/RTP_Issues . I have a pcap output of the SIP and RTP data, it looks fine to me, I can see the DTMF payloads coming as they should be. Any ideas? I would be fine sending or posting the pcap file to someone privately. Thanks Dan-

3 3

Svar: Re: Multi-Homed setup, starting over - still not working
by mailinglist 13 Jan '10

13 Jan '10

Hi Joseph Oh yes I have :-) But are you sayng that "eval ${domain}" will do more than is done when I restart the fs? I don't see that anywhere in the guide :-D I'll try it out asap! Thanks Fribse >>> "Joseph L. Casale" 12-01-10 18:41 >>> >Hi Guys > >I really would like to have this up and running, but I'm constantly running into things that doesn't work, and I have no idea where the problem is... > >I've started from scratch with pfSense and Freeswitch. >I've followed the Multi Home tutorial here: http://wiki.freeswitch.org/wiki/Multi_home_tutorial > >I've deleted the 'lan' profile, and altered the 'internal' profile as recommended, and I've gotten to the paragraph: > >APPLYING YOUR CHANGES AND CHECKING YOUR WORK > >When I start up my x-lite program I get this error: >2010-01-12 16:38:54.172731 [WARNING] sofia_reg.c:1755 Can't find user [1000(a)83.89.x.x] >You must define a domain called '83.89.x.xin your directory and add a user with the id="1000" attribute >and you must configure your device to use the proper domain in it's authentication credentials. >and you must configure your device to use the proper domain in it's authentication credentials. > >83.89.x.x is my external IP, and not my internal IP??? > >Any help on this? This is because you haven't set your domain in vars.xml. The behavior is that $${local_ip_v4} evals to your wan ip. This is the first step in that tutorial:) http://wiki.freeswitch.org/wiki/Multi_home_tutorial#INTERNAL_LAN Open vars.xml, make the line: Match your lan ip: restart fs, then goto the fs_cli and type `eval ${domain}` it should come back with "your" lan ip. _______________________________________________ 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 4

FSComm Windows build
by Carlos Talbot 13 Jan '10

13 Jan '10

FYI, there's a Windows pre-compiled binary of FSComm now available for those who want to check it. http://files.freeswitch.org/windows_installer/FSComm.exe regards, Carlos

4 8

Fw: SIP client authorization issues (Globarange phone)
by VG Oget 13 Jan '10

13 Jan '10

Hi, I am trying to register a GlobaRange SIP phone to FreeSwitch (was able to do it with Asterisk some time ago). It is a locked VOIP phone to Joip.com. On Ubuntu with latest version as of a few days ago… I redirected the traffic to Freeswitch (basically proxy.joip.com points and to the Freeswitch host) and also changed the SIP port to 23768 (what the phone wants). Very close to this: http://darkskiez.co.uk/index.php?page=Use_The_Panasonic_Globarange_With_Ast… I have Xlite successfully registering (SIP port 23768 and using proxy.joip.com not the IP address) so I’m confident the freeswitch config is close to being okay… Now I have intercepted the traffic during registration. The issue (I think) is that the SIP authentication phases use a different username and I don’t know how to configure it. I looked into this page extensively: http://wiki.freeswitch.org/wiki/XML_User_Directory_Guide And also tried to understand sip_suth_username but I cannot find the solution. If someone can point me in the right direction, that would be perfect. Thank you, G. -------------- Phone: 192.168.1.11 Freeswitch: 192.168.1.5 (=proxy.joip.com on local dns) SIP port: 5060 Extension(changed): 1234567890 (joip username) Authentication username (changed): 98765432 ------------ REGISTER sip:proxy.joip.com:23768 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.11:6060;branch=z9hG4bK991d765d Max-Forwards: 70 To: sip:1234567890@proxy.joip.com From: sip:1234567890@proxy.joip.com;tag=3957008896 Call-ID: yyyy-xxxxxxxxxxxx(a)192.168.1.11 CSeq: 1 REGISTER Contact: sip:1234567890@192.168.1.11:6060;nat=3;deviceid=2 Expires: 304 Allow: INVITE,ACK,CANCEL,BYE,NOTIFY User-Agent: Panasonic GT1500/a13.32/xxxxxxxxxxxx Content-Length: 0 SIP/2.0 401 Unauthorized Via: SIP/2.0/UDP 192.168.1.11:6060;branch=z9hG4bK991d765d From: <sip:1234567890@proxy.joip.com>;tag=3957008896 To: <sip:1234567890@proxy.joip.com>;tag=96BeFKm5U4jFH Call-ID: yyyy-xxxxxxxxxxxx(a)192.168.1.11 CSeq: 1 REGISTER User-Agent: FreeSWITCH-mod_sofia/1.0.5-20100106-0400-hacked Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, UPDATE, INFO, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE Supported: timer, precondition, path, replaces WWW-Authenticate: Digest realm="proxy.joip.com", nonce="67132386-fe25-11de-97c3-c7963d15da66", algorithm=MD5, qop="auth" Content-Length: 0 REGISTER sip:proxy.joip.com:23768 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.11:6060;branch=z9hG4bKe585be9f Max-Forwards: 70 To: sip:1234567890@proxy.joip.com From: sip:1234567890@proxy.joip.com;tag=3957008896 Call-ID: yyyy-xxxxxxxxxxxx(a)192.168.1.11 CSeq: 2 REGISTER Contact: sip:1234567890@192.168.1.11:6060;nat=3;deviceid=2 Expires: 304 Authorization: Digest realm="proxy.joip.com", nonce="67132386-fe25-11de-97c3-c7963d15da66", algorithm=MD5, qop=auth, cnonce="7FDF680B", nc=00000001, uri="sip:proxy.joip.com:23768", username="98765432", response="7bd8c1898e9c01ee1817146ddc86c8b4" Allow: INVITE,ACK,CANCEL,BYE,NOTIFY User-Agent: Panasonic GT1500/a13.32/xxxxxxxxxxxx Content-Length: 0 SIP/2.0 403 Forbidden Via: SIP/2.0/UDP 192.168.1.11:6060;branch=z9hG4bKe585be9f From: <sip:1234567890@proxy.joip.com>;tag=3957008896 To: <sip:1234567890@proxy.joip.com>;tag=ag56ge58rD91c Call-ID: yyyy-xxxxxxxxxxxx(a)192.168.1.11 CSeq: 2 REGISTER User-Agent: FreeSWITCH-mod_sofia/1.0.5-20100106-0400-hacked Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, UPDATE, INFO, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE Supported: timer, precondition, path, replaces Content-Length: 0 ---- Get your preferred Email name! Now you can @ymail.com and @rocketmail.com. http://mail.promotions.yahoo.com/newdomains/aa/

2 1