[hylafax-devel] Patch Hylafax to work with Elsa TLV.34/ISDN ?

[Norbert Peyer-Unger <peyer-unger@debitel.net>]

Hi,

after 3 days of viewing log files and changing configuration files I'm
stucked

Here's my configuration:
- Redhat 6.0
- Hylafax 4.0pl2  (also tried 4.1beta2)
- Elsa TLV.34/ISDN on a PBX

Here's my problem:
Faxgetty didn't answers incoming calls.
Outbound Fax works very well.
In details, during an incoming call I see this message in /var/log/messages

   [6:RING;9015200;211]
                       |            |_____ dialed PBX Number
                       |___________  Dialer Number   (in this case another
num. of our PBX)

this is OK because the Elsa TLV.34/ISDN shows Dialer Number (if transmitted
by TelCo) and the dialed PBX Number. Faxgetty didn't answers to the call,
output from faxstat reads
'Listening to the rings of MODEM', I tried   'faxanswer ttyS1',  faxgetty
answers to the call and
the inbound fax was processed correctly.  After reading the man pages I
configured the system
with Distinctive Ring Support, put
  RingFax:    RING;9015200;211
in my config.ttyS1. The next attempt for inbound fax was successful,
faxgetty answered the call.

As far as I can see faxgetty only recognizes a sinlge RING for inbound
calls, a string like
RING;nnnnn;nnn as transmitted by the Elsa TLV34 won't work.
Is my analysis correct? If so, is there a workaround for this problem?
If not, what are the names of the files / procedures to modify, so faxgetty
only looks for the first
4 characters (RING). I think I have to modify faxgetty, but there's no
faxgetty.c++ file.
Hope I'm not OT in this list.

Thanks in advance
  Norbert

--
Norbert Peyer-Unger
peyer-unger@debitel.net


____________________ HylaFAX(tm) Developers Mailing List ____________________
 To unsub: mail -s unsubscribe hylafax-devel-request@hylafax.org < /dev/null