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

["Sedat " <sedat@xxxxxxxxxx>]

> -----Original Message-----
> From: Lee Howard [mailto:faxguy@xxxxxxxxxxxxxxxx]
> Sent: Wednesday, December 31, 2003 9:08 AM
> To: Sedat
> Cc: hylafax-users@xxxxxxxxxxx
> Subject: Re: [hylafax-users] QualifyCID. CID Rejected but Fax still
> Received.
> 
> On 2003.12.30 22:53 Sedat  wrote:
> >
> >
> >  What about
> >    a-) waiting until line stops ringing (no RING from modem for nn
> > secs.)
> 
> This runs the possibility that the RING from one call stops and the
> RING from another starts in less than nn secs.
> 
[Sedat ] Yes I know, that is why I have the plan b-) . If your telco
supports CID, then if you receive a new call within nn secs, your telco will
send a new CID which will activate plan b-)

 Only problem which remains is that, if the call originates from a switch
that does not support CID than that call will not be answered ( but for sure
he will try again some time later)

> > then reinitialize the modem or
> >    b-) a new CID info is received (a new call is on the line) then
> > start CID
> > check again
> 
> This can, in effect, be accomplished already with CIDNumberAnswerLength
> and setting RingsBeforeAnswer to zero.
> 
> >  Not very polite but one can answer and then drop the line as well :-(
> 
> Like maybe with a "RejectCIDCmd: ATH1\nATH0" option?
[Sedat ]  Yeah that would be my last take
> 
> Some people use QualifyCID to cause faxgetty to only answer calls from
> known-fax-senders so that they can use the line for voice purposes when
> it rings 3 or more times.  So the historical default behavior can't be
> changed.  A theoretical RejectCIDCmd could allow some versatility here,
> though.
> 
> Lee.

[Sedat ] 


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