Re: [hylafax-users] Eicon Diva Server ignores RingsBeforeAnswer in config file

[Lee Howard <faxguy@xxxxxxxxxxxxxxxx>]

Dan Bonelli wrote:
> When the log says 'RING' twice, I'm assuming that there should be an 
> annoying ringing sound made somewhere, right?

No, not necessarily... and especially not when you've got the T1 plugged 
right into the telco.  The "RING" indications are merely indications 
that a call is waiting to be answered... not that any audible ringing is 
occurring on the channel.  Audible rings and modem RING indications 
cannot be equated at all.

> My (admittedly uninformed) theory is that the lack of an audible ring 
> is what's causing the remote machine to hang up, because the remote 
> machine comes back with a report that says our line is busy, even 
> though I can see them connect in the log files.

It's certainly a possibility... however, there are numerous places that 
you can call and never get an audible ring before the other end 
answers.  So if your theory is correct then these senders are going to 
have problems sending to other places as well.

More likely is that some particular about the CED tone (the answering 
squeal heard when calling a fax machine) made by the Diva Server is 
being misinterpreted as a busy signal.

> The Diva in question is hooked straight into the wall sans PBX, so I'm 
> talking straight to the telco switch.  This would be set up down in 
> the Diva driver settings, and not in Hylafax, right?

Correct.  If it is possible for the Diva Server to produce an audible 
ring sound then this would be configured in the Diva driver settings.

> Pardon the telco ignorance, but what is CED?

CED is the squeal-tone that an answering fax machine makes.

> As to the caller ID issue (which I should have pointed out doesn't 
> always occur in tandem with the handshake dropping problem), I checked 
> out some of the instances where the caller ID's didn't show, and they 
> look like so:
>
> Dec 10 04:56:11 pri-faxserver FaxGetty[31684]: STATE CHANGE: RUNNING 
> -> LISTENING
> Dec 10 04:56:11 pri-faxserver FaxGetty[31684]: --> [4:RING]
> Dec 10 04:56:11 pri-faxserver FaxGetty[31684]: --> [5:CID: 
> ]                        <------ incoming caller ID?
> Dec 10 04:56:11 pri-faxserver FaxGetty[31684]: --> [12:DAD: <snip>]
> Dec 10 04:56:11 pri-faxserver FaxGetty[31684]: --> [4:RING]
> Dec 10 04:56:11 pri-faxserver FaxGetty[31684]: ANSWER: Call ID 1 "<snip>"
> Dec 10 04:56:11 pri-faxserver FaxGetty[31684]: ANSWER: Call ID 2 ""
>
> The log looks the same as all the other inbound faxes, the only 
> difference being that CID has something there.  Aside from the client 
> just not sending the CID info ( e.g. blocked ID), is there any other 
> Hylafax or modem-related reason that would account for it not showing 
> up all the time?

Some callers just simply don't have Caller*ID.

Lee.


____________________ 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*