Re: [hylafax-users] CID REJECTED...

[Campbell McKilligan <cowboycam@2die4.com>]

I applied the patch against bug #100 as Lee suggested.  The result was
that CID now half works.  (An improvement I think!?!)  With the
expression ^.*$ in the etc/cid file calls are accepted based on CID.  (I
terminated the call below during the handshake):

Apr 17 00:32:43 chandler FaxGetty[10082]: STATE CHANGE: BASE -> RUNNING
Apr 17 00:32:52 chandler FaxGetty[10082]: STATE CHANGE: RUNNING ->
LISTENING
Apr 17 00:32:52 chandler FaxGetty[10082]: --> [4:RING]
Apr 17 00:32:53 chandler FaxGetty[10082]: --> [11:DATE = 0416]
Apr 17 00:32:53 chandler FaxGetty[10082]: --> [11:TIME = 2231]
Apr 17 00:32:53 chandler FaxGetty[10082]: --> [17:NMBR = 0298723980]
Apr 17 00:32:55 chandler FaxGetty[10082]: --> [4:RING]
Apr 17 00:32:55 chandler FaxGetty[10082]: ANSWER: CID NUMBER
"0298723980" NAME ""
Apr 17 00:33:01 chandler FaxGetty[10082]: --> [4:RING]
Apr 17 00:33:01 chandler FaxGetty[10082]: STATE CHANGE: LISTENING ->
ANSWERING
Apr 17 00:34:17 chandler FaxGetty[10082]: ANSWER: Ring detected without
successful handshake
Apr 17 00:34:17 chandler FaxGetty[10082]: <-- [5:ATH0\r]
Apr 17 00:34:19 chandler FaxGetty[10082]: --> [2:OK]

But if I make the expression more specific (for instance, ^0298723980$)
it still rejects the call - even though it appears to be what hylafax is
reporting as coming from the modem:

Apr 17 00:35:33 chandler FaxGetty[10082]: STATE CHANGE: LOCKWAIT ->
RUNNING
Apr 17 00:35:37 chandler FaxGetty[10082]: STATE CHANGE: RUNNING ->
LISTENING
Apr 17 00:35:37 chandler FaxGetty[10082]: --> [4:RING]
Apr 17 00:35:38 chandler FaxGetty[10082]: --> [11:DATE = 0416]
Apr 17 00:35:38 chandler FaxGetty[10082]: --> [11:TIME = 2234]
Apr 17 00:35:38 chandler FaxGetty[10082]: --> [17:NMBR = 0298723980]
Apr 17 00:35:41 chandler FaxGetty[10082]: --> [4:RING]
Apr 17 00:35:41 chandler FaxGetty[10082]: ANSWER: CID NUMBER
"0298723980" NAME ""
Apr 17 00:35:47 chandler FaxGetty[10082]: --> [4:RING]
Apr 17 00:35:47 chandler FaxGetty[10082]: STATE CHANGE: LISTENING ->
ANSWERING
Apr 17 00:35:47 chandler FaxGetty[10082]: ANSWER: CID REJECTED
Apr 17 00:35:47 chandler FaxGetty[10082]: <-- [5:ATH0\r]
Apr 17 00:35:47 chandler FaxGetty[10082]: --> [2:OK]

Any clues where I could go from now?

Cheers!

Campbell

Lee Howard wrote:
> 
> At 05:47 PM 4/15/01 +1000, Campbell McKilligan wrote:
> >Can someone help with this?  Fax receives fine when qualifyCID is
> >commented out.  With qualifyCID as shown and etc/cid allowing all
> >numbers calls are always rejected...  any clues?
> 
> >[campbell@chandler etc]# cat cid
> >^.*$   # allow all
> 
> >Apr 11 03:57:39 chandler FaxGetty[776]: --> [4:RING]
> >Apr 11 03:57:39 chandler FaxGetty[776]: --> [11:DATE = 0410]
> >Apr 11 03:57:39 chandler FaxGetty[776]: --> [11:TIME = 1818]
> >Apr 11 03:57:39 chandler FaxGetty[776]: --> [17:NMBR = 0298723980]
> >Apr 11 03:57:42 chandler FaxGetty[776]: --> [4:RING]
> >Apr 11 03:57:42 chandler FaxGetty[776]: ANSWER: CID NUMBER "0298723980"
> >NAME ""
> >Apr 11 03:57:48 chandler FaxGetty[776]: --> [4:RING]
> >Apr 11 03:57:48 chandler FaxGetty[776]: STATE CHANGE: LISTENING ->
> >ANSWERING
> >Apr 11 03:57:48 chandler FaxGetty[776]: ANSWER: CID REJECTED
> >Apr 11 03:57:48 chandler FaxGetty[776]: <-- [5:ATH0\r]
> >Apr 11 03:57:48 chandler FaxGetty[776]: -->
> >[2:OK]
> 
> 
> 
> I don't have caller-ID here, so I'm basing everything I say here on my
> knowledge and experience with TSID.  A couple of things...
> 
> First, you ought to try placing "^0298723980$" in the cid file to see what
> happens.  If it rejects that, then there may be something seriously wrong
> with CID handling in HylaFAX.  Is anyone out there using CID rejection out
> there?  Can you comment about its functionality?
> 
> Lastly, I don't think that this is the problem, necessarily, but perhaps
> it's worth mentioning for future things.  TSI handling suffered from a
> problem where null tsi could not be matched, so every call with null tsi
> would be rejected (which is a significant number, unfortunately).  There is
> a patch for this at
> http://bugs.hylafax.org/bugzilla/show_bug.cgi?id=100
> which has been committed to CVS and will be present in the upcoming beta4
> release.  If HylaFAX uses the same function to match CID as it does to
> match TSI, then this may be a future factor... perhaps.  Too bad there's
> not a cidtest utility.
> 
> Lee.
> 
> Here's a demo of null-TSI matching, before and after the patch...
> 
> -- before... --
> [root@providence deanox]# /usr/local/sbin/tsitest ./tsi
> ready>
> input = ""
> [check ^.*$]
> [check ^$]
> reject (no pattern match)
> ready>
> 
> -- after... --
> [root@server deanox]# /usr/sbin/tsitest ./tsi
> ready>
> input = ""
> [check ^.*$]
> accept (matched by ^.*$)
> ready>
> 
> -- after if you want to reject null-tsi --
> [root@server deanox]# /usr/sbin/tsitest ./tsi
> ready>
> input = ""
> [check ^$]
> reject (matched by ^$)
> ready>


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