Hi Tzafrir! Thank you for your answer, and my apologies for my delayed response. I regret to say that the patch test's results were not succesful. I shall describe the whole procedure in detail for you to establish whether I did something wrong.
The fact is that I am as much a Linux beginner as I am an Asterisk one, and so I had first to learn how to stick the patch. Since I found no instructions to apply it, perhaps this was not the right procedure... After initially attempting with 3M self-adhessive tape with little success..., I finally did the following: 1) I copied the autoztcgf.diff to the /usr/src/zaptel-1.4.5.1 directory 2) I run patch -b < autoztcfg.diff 3) Since a file named zaptel.c did not exist, patch offered me to enter the filename. I entered zaptel-base.c which I thought was the most probable file to be patched. 4) I obtained 6 out of 6 success messages indicating however very variable offsets, ranging between 13 and 224 lines, which called my attention. May be this was normal, however. Then I performed the following actions: 1) I sent the zaptel file in /etc/modprobe.d/ to trash (remember this file had been artificially grafted by me by means of zaptel 1.4.4). By the way I want to make clear that zaptel files in /etc/init.d and in /etc/rc.d/init.d were created by version 1.4.5.1, and that zaptel modules were loaded during bootup (they just were not configured). 2) I stopped Asterisk and unloaded zttranscode, wctdm24xxp and zaptel by means of rmmod. (My card is a TDM800P) 3) I then installed the patched zaptel-1.4.5.1 starting with a make clear command. Everything went OK. A new zaptel.conf replaced the previous one. I properly configured it by hand. I restarted the machine. Results: 1) Zaptel was not automatically configured. I ran zttool: 'unconfigured' statement 2) I ran /sbin/ztcfg -vv. The result was a wonderful computer crash. I had to restart it from the CPU button :-( Finally I returned to my original installation and re-sent the zaptel script to the /etc/modprobe.d directory. Everything began to work properly again. In my humble and newbie's opinion, a patch to simply install this script would have to solve the problem. Considering that previous versions did it, I cannot understand well why this action has been eliminated in version 1.4.5.1. Greetings, Aldo ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- On Wed Oct 17 16:57:31 CDT 2007 Tzafrir Cohen wrote: >On Wed, Oct 17, 2007 at 06:37:21PM -0300, Aldo D. Sudak wrote: >> Greetings to all list members! >> >> My name is Aldo Sudak and I am an Asterisk newbie. I am writing now because >> I have not >> been able to find any mention to the issues described below, neither in this >> list nor in the wiki. >> >> I am performing preliminary tests with Asterisk 1.4.11 and Zaptel 1.4.5.1 on >> Fedora Core 6. >> Installation of all of the Asterisk packages was straightforward and I >> always obtained success >> messages. Following Asterisk and Zaptel installation I ran the corresponding >> make config >> commands in order to have both Asterisk and Zaptel running at startup. With >> Zaptel, however, >> two issues arose: >> >> 1) zaptel.conf in the /etc/ directory had not been created. The GUI loaded >> itself a very rudimentary >> zaptel.conf file which lacked loadzone and defaultzone definitions, so I >> prefered to manually copy >> and paste zaptel.conf.sample from the sources and rename it. > >use zapconf or genzaptelconf to generate one that actually works. >Both are included with Zaptel and installed by default (genzaptelconf is >being phased out). > >> >> 2) Zaptel modules loaded during bootup but were not automatically >> configured, and so I had to >> manually run ztcfg and afterwards restart Asterisk each time I started the >> computer. I discovered >> that there did not exist a 'zaptel' file in the /etc/modprobe.c/ directory, >> so I made an experiment >> by installing Zaptel 1.4.4, which generated the file, and then re-installing >> Zaptel 1.4.5.1. The >> experience was successful and now Zaptel 1.4.5.1 is loaded and configured >> during bootup. > > /etc/init.d/zaptel start > >is required to properly start zaptel. It will also run ztcfg. Otherwise >users run into issues where misconfigured zaptel.conf fails loading of a >module. That is a buggy behaviour. > >If your card is an analog one, take a look at http://bugs.digium.com/7613 >and tell me what you think. > >Something similar for digital spans would require more information in >sysfs. > >-- > Tzafrir Cohen >icq#16849755 jabber:tzafrir.cohen at xorcom.com >+972-50-7952406 mailto:tzafrir.cohen at xorcom.com >http://www.xorcom.com iax:guest at local.xorcom.com/tzafrir
_______________________________________________ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
