HylaFAX The world's most advanced open source fax server

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [hylafax-users] QualifyCID -and- (HylaFAX Version 4.1)



First test your etc/cid file with tsitest:

[campbell@viper etc]# which tsitest
/usr/sbin/tsitest

[campbell@viper etc]# tsitest /var/spool/fax/etc/cid
ready> 911
[check ^0299290282$]
[check ^0398702955$]
[check ^.*$]
accept (matched by ^.*$)
ready>

AS CID, TSI and tsitest use the same regex code this will make sure that the
regex code is not broken in your version and that your etc/cid file is correct.

There is a patch you can apply to util/RegEx which stops Hylafax from
incorrectly rejecting CID or TSIs (depending on which one you are checking)
when the received string is empty.

There is a second patch which ensures that CID passed on for checking properly
once it is received.  Just because CID numbers appear in the logs, it doesn't
guarantee that it got sent of for checking properly.

alt wrote:

> The bottom line is:
> inserting             !^<pattern>$ <-- as the first line in
> /var/spool/hylafax/etc/cid -- eg. ^8005551212$
> also inserting      ^.*$  <-- as the last line in
> /var/spool/hylafax/etc/cid
>
> The <pattern> shown in the first line is being accepted by
> hylafax1 when it should be 'CID REJECTED.'
>
> Looking at this from another angle, should I only place the
> following:
> ^<pattern>$ <-- as the first line in
> /var/spool/hylafax/etc/cid -- eg. ^8005551212$
> The above line will *not be accepted/answered by hylafax.
>
> Lastly when I try inserting (as an only line in the etc/cid)-->
> ^$ <-- all incoming calls are accepted.  It seems to me
> QualifyCID is not working properly.  Its my understanding that ^$
> means a null or empty string.  The CID info is in-fact available
> (showing in my server log)  What I think may be happening is; the
> patterns placed in etc/cid (in this instance) are being matched
> against the TSI info  --and not--  CID info
>
> With my per-modem config files set to ...
> ServerTracing:          1
> SessionTracing:         15
> serverlogs do in fact show CID name and number However; my
> session logs will not show CID name and number information with
> the setting shown above.  The session logs do show 'cid rejected'
> when QualifyCID is defined but etc/cid is empty.
>
> I don't need or use TSI screening.  I need and want to screen via
> CID, providing we can figure what's going incorrectly here.
>
> Thanks for your thoughts.
>
> ____________________ 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@hylafax.org < /dev/null
>   *To learn about commercial HylaFAX(tm) support, mail sales@hylafax.org.*


____________________ 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@hylafax.org < /dev/null
  *To learn about commercial HylaFAX(tm) support, mail sales@hylafax.org.*




Project hosted by iFAX Solutions