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