Re: [hylafax-users] several ISDN questions

[Bodo Meissner <bodo@xxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Toni Mueller wrote, on 18.08.2008 10:15:

| Did you get near an analysis about what exactly failed?

Hello Toni,

I only know that the c2faxsend program reports successful transmission
while on the receiving side the second and following pages are only a
few millimeters long and contain the header line only.
I did not find a way to get more debug output from c2faxsend and did not
~  have access to any debug output from the receiving side.

|  * Installing Asterisk (but not configuring it, yet) was a no-brainer
|    in a Lenny (beta) machine.

I think learning how to configure Asterisk is the hardest part. IMHO it
would be too much work if I need this only to get HylaFAX workin with my
ISDN card and do not want to use Asterisk as a PBX.

|> I replaced my AVM B1 card with an Eicon (now Dialogic) Diva Server card
|> using it's TTY interface configured as a Group 1.0 modem.
|
| So, Group2 faxing is impossible under ISDN? Should I rather get a
| multiport serial card and attach two modems to it?

Sorry, this was a mistake from my side. It is not group but class 1.0.
Dialogic (Eicon) Diva Server cards can work in class 1.0 and 2 (or
2.0?). I chose class 1 because I wanted the high level protocol stuff to
be done by HylaFAY instead of the Dialogic (Eicon) driver.

|> You need the Diva Server drivers for Linux from Dialogic for the TTY
|> interface. Version 8.5-108-80 [...] is
|> compatible with Linux kernels up to 2.6.24 and version 8.5-108-106
|> [...] with kernels up to 2.6.25.
|> Kernel version 2.6.26 is not supported because of major changes in the
|> modules handling.
|
| Regardless of whatever else I'm going to do, I'm not taking a binary
| driver, no matter what. [...]
| So, the Diva cards are out of bounds for me if I understood you
| correctly.

I did not make this clear. The driver from Dialogic is not a binary only
driver. You have to compile the drivers for your kernel and need the
kernel sources for this. It is normal that the driver sources are not
necessarily compatible with newer kernels.

In version 8.5-108-80 the sources of the TTY driver (the most
interesting part) are hidden in an encrypted binary file "tty_compiler".
Although it will be compiled on your system, you would need some hacks
to see the sources. In version 8.5-108-106 the TTY driver is open source
and the Dialogic (Eicon) support was very helpful.

At least parts of the open sources are not free, so Linux distributions
can not provide pre-compiled drivers from Dialogic's current sources.
That's why the Eicon drivers in the Linux kernels are based on an older
version with less features.

If you use CAPI and capi4hylafax you cannot use all features of HylaFAX.
That's why I would recommend to use a card with a TTY interface or use
IAXmodem with Asterisk.


Bodo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkit2BgACgkQnMz9fgzDSqewIwCfcgEVDuG4gJZwKLl7TeXzRXFH
RhAAnAzdub332MKKvk9yI9+Szj2WGRBa
=agzU
-----END PGP SIGNATURE-----


____________________ HylaFAX(tm) Users Mailing List _______________________
 To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
 *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*