A comment on the asterisk packaging and a question

Kilian Krause kk@verfaction.de
Mon, 21 Mar 2005 13:28:15 +0100


--=-M7n/M0j9g/QflYNWnD0o
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Hi again Ralph,

a very important bit i forgot to mention in my previous email is that
you must have ztcfg run only ONCE.

I.e. if you encounter a broken zaphfc configuration like you cannot
receive or place any call, then it's most likely that one.=20
There's an automagic postinst from within the zaptel pacakge, so you
might encounter a problem here under certain conditions. I haven't yet
fully narrowed down when ztcfg is run once too many and when too few to
work ok, but if after modprobe zaphfc the asterisk won't start, try
running ztcfg once and try again.

If you can start asterisk right away and cannot receive/place calls,
then remove the ztcfg post-install lines from /etc/modutils/zaptel
and /etc/modprobe.d/zaptel. Run update-modules and try again. You should
now see asterisk not starting right after modprobe, but launching ok
with ztcfg.

I know this bug is annoying, but so far i haven't seen a fix in zaptel
upstream. If you feel like it, put it into BTS, but it'll be tracked
down long term, as it's highly annoying with zaphfc and qozap cards.

--=20
Best regards,
 Kilian

--=-M7n/M0j9g/QflYNWnD0o
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: Dies ist ein digital signierter Nachrichtenteil

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQBCPr3fvdkzt4X+wX8RAh/yAJ97xEB4J58yq4/JhhZiq8/071PCPwCeIOv4
hvOvVT8GmDFvGGHp2v9F6pw=
=oQJw
-----END PGP SIGNATURE-----

--=-M7n/M0j9g/QflYNWnD0o--