Re: [hylafax-users] QualifyCID. CID Rejected but Fax still Received. - Solution

["Frank Brock" <FrankBrock@xxxxxxxxxxxx>]

Lee,

Removing RingsBeforeAnswer and keeping CIDnumberAnswerLength causes the
correct behavior (I think). 

Now, the cid rejected number just rings, rings, rings.  Log shows it as
a rejected number and the modem just RING, RING, RING after reject.

A good cid is picked up right away as expected.

Down side is that if a call comes in and there is an error on the Telco
or in the Modem DID reporting (I have seen this sometimes in the Digi
DataFire) and no DID info is reported, then the call will also go
unanswered since we never see enough CID digits and there is no
RingsBeforeAnswer as a backup to catch the call.  Oh well. But when the
sender auto recalls, hopefully the same error will not occur to them and
the call gets picked up then.

Do you still think this is a bug and should be reported?  It looks like
it is working properly to me.  Just the combination of the two features
cause the problem (RingsBeforeAnswer and CIDnumberAnswerLenght)

BTW (off this topic), do you know how best to tune all the various modem
DELAYS that are used during modem initializations ?  I think I probably
see about 10 seconds total per fax just in modem re-inititializations.

-----Original Message-----
From: Lee Howard [mailto:faxguy@xxxxxxxxxxxxxxxx] 
Sent: Wednesday, December 31, 2003 2:01 AM
To: Frank Brock
Subject: Re: [hylafax-users] QualifyCID. CID Rejected but Fax still
Received.

On 2003.12.30 19:15 Frank Brock wrote:
> Yes. I will write it up later this week into the bug trakcer.
> Btw, I use cidnumberanswerelenght.  Works great.
> cid comes between 1 and 2.
> I set ringsbeforeanswer to 2 but then the answerlenght actually picks
> it
> up just a split second after first ring when it sees all the digits.
> Just like it is supposed to.

Then if you set RingsBeforeAnswer to 0 you shouldn't have this problem 
any more... I don't think... since it will only answer upon seeing CID 
and not on RINGs.

> The modem reinit was something I think I saw once while watching
> faxstat.  Msut be that the reinit of the digi modems is not making the
> call "go away".

It's not supposed to make the call go away.  It's just supposed to not 
answer.

>  Almost need to go off and then right back on hook to
> kill the call.  ??

Well, answering and then hanging up isn't really what QualifyCID was 
intended to do.  Some people use it, for example, to allow them to use 
the line as fax and voice... only answering when a known 
fax-sender-line-number called.

> Not really sure how the modem can make the call go away if it never
> picks up...?

I don't think that was the intention.  If *this* is what you want, then 
you really want QualifyTSI... but perhaps with the CID information.  It 
should be fairly easy to hack faxgetty to get QualifyTSI to use the CID 
information.

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@xxxxxxxxxxxx*