- FreeSWITCH-dev - FreeSWITCH Mailing Lists

Slashdot: How-to-Help-With-a-University-ICT-Strategy
by Giovanni Maruzzelli 27 Jul '09

27 Jul '09

http://ask.slashdot.org/story/09/07/27/1652247/How-to-Help-With-a-Universit… " An anonymous reader writes "I have been asked to contribute to my university's revised ICT (Information and Communication Technology) strategy and I am curious what fellow Slashdot members consider to be the main advice in this context. What are the major mistakes that organizations like universities make? Given the complexity of the different participants in a university, how does one have a coherent strategy that fulfills the needs of such a wide audience? How does one promote open source in a managerial culture? How does one deal with the curse of the virtual learning environment?"" http://ask.slashdot.org/comments.pl?sid=1316571&cid=28842157

1 0

ClueCon 2009 - Last Chance For Early Bird Special!
by Michael Collins 27 Jul '09

27 Jul '09

ClueCon is next week! We're all gearing up for a great event. Here is some important information for those who've not already paid: Today is the last day to receive the $499 early bird special. After today, the price will go up to $699. If you have registered at the ClueCon website but you have not yet paid then please call 877.742.CLUE immediately! We want to make sure that you get the early bird rate. All registrations after today (Monday July 27) will be $699. Thank you for your support of ClueCon 2009! We are looking forward to seeing everyone in person in Chicago. -Michael Collins http://www.cluecon.com 877.742.CLUE

1 0

Skypiax, Skype endpoint and trunk, revamped
by Giovanni Maruzzelli 27 Jul '09

27 Jul '09

Ciao FreeSWITCHers, please have a look at the much changed wiki page: http://wiki.freeswitch.org/wiki/Skypiax_Skype_Endpoint_and_Trunk and checkout and test the code in svn. Much has happened, various bug fixes and features added. Most notable: - multiple instances of the same Skype username on Linux (eg: running 20 concurrent channels as "Bob" Skype user) - adding and removing interfaces on the fly (patch sent by Muhammad Shahzad) - easier creation of Skype clients configuration directory - reduced latency - better robustness - running as Windows Service - customized ALSA driver for more devices with less IRQs and context switches - custom kernel tickless and 100HZ (eg. solves high load problems in CentOS and in virtualization) - interactive command line client for prototyping Also, please note that ALSA drivers version 1.0.20 seems to be much more stable in our kind of usage (snd-dummy). Various other enhancements will come, but in the mean time please give feedback on the current svn code (we want to be robust for the 1.0.4 Release :-) ) See you all at www.cluecon.com, talk on Skypiax August 4th at 4.30 pm ! -giovanni Sincerely, Giovanni Maruzzelli ========================================= www.celliax.org via Pierlombardo 9, 20135 Milano Italy gmaruzz at celliax dot org Cell : +39-347-2665618 Fax : +39-02-87390039

1 0

support currency and number pronounced in spanish (suggestion)
by Diego Toro 26 Jul '09

26 Jul '09

Hi all, This code support currency and number pronounced in spanish, there are new files so that to pronounce numbers in spanish is different to english, for example, number 100 in english is one-hundred and 500 is five-hundred but in spanish that is not right way. Audio files neccesaries (included in phrase_es.xml): veinti.wav 100.wav 500.wav 700.wav 900.wav I changed code on mod_say_es.c and switch_status_t play_group method to improve support for pronouncing currency and number, this is new code: static switch_status_t play_group(switch_say_method_t method, int a, int b, int c, char *what, switch_core_session_t *session,switch_input_args_t *args) { if (a) { switch(a) { case 1: if (b || c) { say_file("digits/hundred.wav"); } else { say_file("digits/100.wav"); } break; case 5: say_file("digits/500.wav"); break; case 7: say_file("digits/700.wav"); break; case 9: say_file("digits/900.wav"); break; default: say_file("digits/%d.wav", a); say_file("digits/hundred.wav"); break; } } if (b) { if (b > 1) { switch (b) { case 2: if (c) { say_file("digits/veinti.wav"); } else { say_file("digits/20.wav"); } break; default: say_file("digits/%d0.wav", b); if (c) { say_file("currency/and.wav"); } break; } } else { say_file("digits/%d%d.wav", b, c); c = 0; } } if (c) { if (method == SSM_COUNTED) { say_file("digits/h-%d.wav", c); } else { say_file("digits/%d.wav", c); } } if (what && (a || b || c)) { say_file(what); } return SWITCH_STATUS_SUCCESS; } any suggestion is welcome Diego Toro

2 1

A possible bug in FS causing Linux Kernel crash
by Muhammad Shahzad 26 Jul '09

26 Jul '09

Hi, I am having random Linux Kernel crash problems while running FreeSWITCH as Skype to/from SIP gateway on one of our production servers. This machine is running CentOS 5.2, Kernel version 2.6.18-92.1.22.el5.centos.plusPAE with FS svn revision number 13754. At time of Kernel crash i could find following crash messages which point to some source code file in FS source tree. --------------------- Kernel Begin ------------------------ 3 Time(s): ======================= 3 Time(s): [<c0404eff>] syscall_call+0x7/0xb 3 Time(s): [<c043ed22>] sys_delete_module+0x192/0x1b8 3 Time(s): [<c0449011>] audit_syscall_entry+0x14b/0x17d 3 Time(s): [<c049f4fe>] remove_proc_entry+0x139/0x18c 3 Time(s): [<f8d96281>] alsa_sound_exit+0xa/0x30 [snd] 3 Time(s): [<f8d96304>] snd_info_done+0x46/0x49 [snd] 3 Time(s): BUG: warning at fs/proc/generic.c:732/remove_proc_entry() (Not tainted) 1 Time(s): snd-malloc: Memory leak? pages not freed = 1 ---------------------- Kernel End ------------------------- While the problem seems to arise from ALSA kernel module but it blames FS file fs/proc/generic.c:732 for this. The only FS module that is using ALSA is mod_skypiax but as far as i remember that module is using FS internal routines to allocate and de-allocate sound driver services for Skype client. Please suggest a solution. Thank you. -- Muhammad Shahzad ----------------------------------- CISCO Rich Media Communication Specialist (CRMCS) CISCO Certified Network Associate (CCNA) Cell: +92 334 422 40 88 MSN: shari_786pk(a)hotmail.com Email: shaheryarkh(a)googlemail.com

1 0

random fs crashing
by Juan Backson 25 Jul '09

25 Jul '09

Hi, I am having some strange randomly crashing of fs in production. They all point to something wrong in the main(). Although I have my own module running, but I don't think it should have any impact to the main() process. Could someone please point me to some solution that may resolve or debug this problem? [New process 15596] [New process 15595] #0 0x00002b5b831bc215 in raise () from /lib64/libc.so.6 Thread 1198 (process 15595): #0 0x00002b5b832584c2 in select () from /lib64/libc.so.6 No symbol table info available. #1 0x00002b5b823fc9c5 in apr_sleep (t=<value optimized out>) at time/unix/time.c:246 tv = {tv_sec = 0, tv_usec = 351000} #2 0x00002b5b823a418a in switch_core_runtime_loop (bg=<value optimized out>) at src/switch_core.c:672 No locals. #3 0x0000000000402607 in main (argc=2, argv=0x7fff5b793498) at src/switch.c:706 pid_path = "/usr/local/freeswitch/log/freeswitch.pid", '\0' <repeats 215 times> pid_buffer = "15595", '\0' <repeats 26 times> old_pid_buffer = "5951", '\0' <repeats 27 times> pid_len = 5 old_pid_len = 4 err = 0x0 nf = 0 runas_user = 0x0 runas_group = 0x0 nc = 1 pid = <value optimized out> x = <value optimized out> alt_dirs = 0 known_opt = 1 high_prio = 0 flags = 1 ret = <value optimized out> destroy_status = <value optimized out> fd = (switch_file_t *) 0x12bc7b00 pool = (switch_memory_pool_t *) 0x12bc79c8 rlp = {rlim_cur = 245760, rlim_max = 245760} waste = 0 __PRETTY_FUNCTION__ = "main" Thanks, JB

2 1

Re: [Freeswitch-dev] D-READ FAIL! [] while using openzap with libpri
by Alex Green 24 Jul '09

24 Jul '09

Thanks Anthony, The box with the TE210p has: ---------------------------- Zaptel 1.4.12 Libpri 1.4.10 Openzap via Freeswitch 1.0.3 I initially had the two ports of the TE210p connected together for testing. I had D-Channel issues fairly often. Here is the interesting bit: I noticed that the code around line 117 in lpwrap_pri.c had changed over the last 4 months (since version 693). I updated openzap to the head, recompiled and my little test app making calls from one PRI to the other on the TE210p worked fine (or so I thought, see below). Vanilla Freeswitch box with TE110p: ----------------------------------- Zaptel rev 4630 (from http://wiki.freeswitch.org/wiki/Zaptel_Tutorial) Libpri 1.4.10.1 Freeswitch 1.0.3 Connect the two together and D-channel errors, which was no surprise on my previous experience, so I updated Freeswitch to the trunk. At this point I still got D-channel errors as reported in the last email. Thanks again, -alex Anthony Minessale wrote: > Which revision of FS/OpenZAP/Zaptel are you using respectively? > > All the errors after your shutdown are not really clues they are just > typical > things that happen when you close the socket but the endless D-READ FAIL > sounds strange. How often does this happen? > > We mostly have sangoma users so we have less info on Digium cards > but I can try to investigate your problem for you if you answer my first > round of questions. > > > > On Wed, Jul 22, 2009 at 10:16 PM, Alex Green <alexg(a)etherstack.com > <mailto:alexg@etherstack.com>> wrote: > > On a number of occasions using openzap with libpri the D channel seems > to some how lose synchronisation resulting in 'D-READ FAIL! []'. > > Background: > ----------- > On one side is a very standard Linux box with Freeswitch and a TE110p > card. The signalling is set up to be a Network E1. On the other side of > the PRI coax cable is a box I am experimenting with has openzap > interacting with a small application of my own. This side is set up to > be a CPE E1 (using a TE210p). This problem has happened to me previously > using freeswtich/openzap but scouring the internet has found nought. I > am concerned that I have done something silly, but I have double checked > everything. The error is printed from lpwrap_pri.c line 117. > > Symptoms: > --------- > On freeswitch "D-READ FAIL! []" is just printed to screen over and over > again. After issuing a shutdown the following clue is given after > stopping mod_openzap: > 2009-07-22 17:11:07 [INFO] zap_io.c:257 zap_channel_destroy() Closing > channel zt:1:30 fd:67 > 2009-07-22 17:11:07 [INFO] zap_io.c:257 zap_channel_destroy() Closing > channel zt:1:31 fd:68 > D-READ FAIL! [] > Error = -1 > Lpwrap Run Pri: : Bad file descriptor > > On Openzap (without freeswitch) the following happens: > [CRIT] src/ozmod/ozmod_libpri/lpwrap_pri.c:122 __pri_lpwrap_read() span > 5 D-READ FAIL! [] > [ERROR] src/ozmod/ozmod_libpri/ozmod_libpri.c:88 s_pri_error() !! > Received short I-frame (expected 4, got -3) > [DEBUG] src/ozmod/ozmod_libpri/ozmod_libpri.c:812 process_event() EVENT > [ALARM_TRAP][7][5:1] STATE [PROGRESS_MEDIA] > [DEBUG] src/ozmod/ozmod_libpri/ozmod_libpri.c:821 process_event() > Changing state on 5:1 from PROGRESS_MEDIA to RESTART > [WARNING] src/ozmod/ozmod_libpri/ozmod_libpri.c:831 process_event() > channel 5:1 (1:1) has alarms! [YELLOW/LOOP] > [DEBUG] src/ozmod/ozmod_libpri/ozmod_libpri.c:812 process_event() EVENT > [ALARM_TRAP][7][5:2] STATE [DOWN] > ...The last two are printed repeatedly. > > > For some extra information I have summarised my setup below. Any help on > this (surly I am not the first person to experience this!) is greatly > appreciated. Many thanks, -alex > > > > Setup: > ------ > *Zaptel.conf* > Box1 (Freeswitch Network E1) has 'span=1,1,0,ccs,hdb3' > Box2 (Openzap CPE E1) has 'span=1,0,0,ccs,hdb3' > I have experimented with crc4 on/off and timing of 1/2. > > *openzap.conf* similar on both sides. > [span zt] > number => 1 > trunk_type => e1 > b-channel => 1-15,17-31 > d-channel=> 16 > > *openzap.conf.xml* > Box1 (Freeswitch Network E1). > <libpri_spans> > <span id="1"> > <param name="node" value="network"/> > <param name="switch" value="euroisdn"/> > <param name="dialplan" value="XML"/> > <param name="context" value="default"/> > </span> > </libpri_spans> > > Box2 (Openzap CPE) passes the following to libpri (via > zap_configure_span); > "node", "cpe", > "switch", "euroisdn", > "dp", "unknown", > "l1", "alaw", > > _______________________________________________ > FreeSWITCH-dev mailing list > FreeSWITCH-dev(a)lists.freeswitch.org > <mailto:FreeSWITCH-dev@lists.freeswitch.org> > http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev > UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev > http://www.freeswitch.org > > > > > -- > Anthony Minessale II > > FreeSWITCH http://www.freeswitch.org/ > ClueCon http://www.cluecon.com/ > Twitter: http://twitter.com/FreeSWITCH_wire > > AIM: anthm > MSN:anthony_minessale@hotmail.com > <mailto:MSN%3Aanthony_minessale@hotmail.com> > GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com > <mailto:PAYPAL%3Aanthony.minessale@gmail.com> > IRC: irc.freenode.net <http://irc.freenode.net> #freeswitch > > FreeSWITCH Developer Conference > sip:888@conference.freeswitch.org > <mailto:sip%3A888@conference.freeswitch.org> > iax:guest@conference.freeswitch.org/888 > <http://iax:guest@conference.freeswitch.org/888> > googletalk:conf+888@conference.freeswitch.org > <mailto:googletalk%3Aconf%2B888@conference.freeswitch.org> > pstn:213-799-1400 > > > ------------------------------------------------------------------------ > > _______________________________________________ > FreeSWITCH-dev mailing list > FreeSWITCH-dev(a)lists.freeswitch.org > http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev > UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev > http://www.freeswitch.org

2 1

ASR, dictation ;-)
by Giovanni Maruzzelli 24 Jul '09

24 Jul '09

http://yro.slashdot.org/story/09/07/23/228208/SpinVox-Recognition-Is-Often-…

1 0

D-READ FAIL! [] while using openzap with libpri
by Alex Green 23 Jul '09

23 Jul '09

On a number of occasions using openzap with libpri the D channel seems to some how lose synchronisation resulting in 'D-READ FAIL! []'. Background: ----------- On one side is a very standard Linux box with Freeswitch and a TE110p card. The signalling is set up to be a Network E1. On the other side of the PRI coax cable is a box I am experimenting with has openzap interacting with a small application of my own. This side is set up to be a CPE E1 (using a TE210p). This problem has happened to me previously using freeswtich/openzap but scouring the internet has found nought. I am concerned that I have done something silly, but I have double checked everything. The error is printed from lpwrap_pri.c line 117. Symptoms: --------- On freeswitch "D-READ FAIL! []" is just printed to screen over and over again. After issuing a shutdown the following clue is given after stopping mod_openzap: 2009-07-22 17:11:07 [INFO] zap_io.c:257 zap_channel_destroy() Closing channel zt:1:30 fd:67 2009-07-22 17:11:07 [INFO] zap_io.c:257 zap_channel_destroy() Closing channel zt:1:31 fd:68 D-READ FAIL! [] Error = -1 Lpwrap Run Pri: : Bad file descriptor On Openzap (without freeswitch) the following happens: [CRIT] src/ozmod/ozmod_libpri/lpwrap_pri.c:122 __pri_lpwrap_read() span 5 D-READ FAIL! [] [ERROR] src/ozmod/ozmod_libpri/ozmod_libpri.c:88 s_pri_error() !! Received short I-frame (expected 4, got -3) [DEBUG] src/ozmod/ozmod_libpri/ozmod_libpri.c:812 process_event() EVENT [ALARM_TRAP][7][5:1] STATE [PROGRESS_MEDIA] [DEBUG] src/ozmod/ozmod_libpri/ozmod_libpri.c:821 process_event() Changing state on 5:1 from PROGRESS_MEDIA to RESTART [WARNING] src/ozmod/ozmod_libpri/ozmod_libpri.c:831 process_event() channel 5:1 (1:1) has alarms! [YELLOW/LOOP] [DEBUG] src/ozmod/ozmod_libpri/ozmod_libpri.c:812 process_event() EVENT [ALARM_TRAP][7][5:2] STATE [DOWN] ...The last two are printed repeatedly. For some extra information I have summarised my setup below. Any help on this (surly I am not the first person to experience this!) is greatly appreciated. Many thanks, -alex Setup: ------ *Zaptel.conf* Box1 (Freeswitch Network E1) has 'span=1,1,0,ccs,hdb3' Box2 (Openzap CPE E1) has 'span=1,0,0,ccs,hdb3' I have experimented with crc4 on/off and timing of 1/2. *openzap.conf* similar on both sides. [span zt] number => 1 trunk_type => e1 b-channel => 1-15,17-31 d-channel=> 16 *openzap.conf.xml* Box1 (Freeswitch Network E1). <libpri_spans> <span id="1"> <param name="node" value="network"/> <param name="switch" value="euroisdn"/> <param name="dialplan" value="XML"/> <param name="context" value="default"/> </span> </libpri_spans> Box2 (Openzap CPE) passes the following to libpri (via zap_configure_span); "node", "cpe", "switch", "euroisdn", "dp", "unknown", "l1", "alaw",

2 1

Good Information On How To Submit Bug Reports
by Michael Collins 22 Jul '09

22 Jul '09

FYI, Brian West called to my attention that one of our community members, John Wehle, has been very good at submitting useful bug reports, in many cases with patches. His style of reporting is worthy of imitation, so I've added a few links to the JIRA section of the Reporting Bugs wiki page: http://wiki.freeswitch.org/wiki/Reporting_Bugs#Examples_Of_Well-Written_JIR… Please feel free to check it out. If you have any questions on what a bug report should look like then definitely read some of John's submissions and emulate his style. By submitting useful bug reports you will save the FreeSWITCH developers countless hours and headaches, not to mention the warm fuzzies you'll feel inside. :) -Michael

1 0