![]() |
I have QualifyCID set to etc/cid. I am using it for DID number rejection. Tsitest shows the numbers being accepted and rejected as I want. All calls that I do want to receive are accepted and received just fine with the correct/complete CID/DID information. When the call comes in for a number to be rejected, the faxgetty log shows it being rejected as follows. --------- Dec 29 16:34:16.43: [13644]: SESSION BEGIN 000003471 15138423721 Dec 29 16:34:16.43: [13644]: HylaFAX (tm) Version 4.1.8 Dec 29 16:34:16.43: [13644]: ANSWER: CID REJECTED Dec 29 16:34:16.43: [13644]: SESSION END --------- BUUUUTTT, then a new log file is created an instant later by the same faxgetty and the fax is received. Here are the first few log lines. --------- Dec 29 16:34:52.69: [13644]: SESSION BEGIN 000003472 15555551212 Dec 29 16:34:52.69: [13644]: HylaFAX (tm) Version 4.1.8 Dec 29 16:34:52.69: [13644]: <-- [4:ATA\r] Dec 29 16:34:58.57: [13644]: --> [74:+FHT: FF 03 40 20 20 20 20 20 20 20 20 20 2 0 20 20 20 20 54 43 41 50 4D 49] Dec 29 16:34:58.85: [13644]: --> [26:+FHT: FF 13 80 00 EE FA 46] Dec 29 16:34:59.76: [13644]: --> [4:+FCO] Dec 29 16:34:59.76: [13644]: ANSWER: FAX CONNECTION DEVICE '/dev/ttyG000' Dec 29 16:34:59.76: [13644]: STATE CHANGE: ANSWERING -> RECEIVING ---------- At this point the CID information is lost by faxgetty and when faxrcvd is called, it is given an empty CIDNumber on the command line. Watching faxstat, it appears that the faxgetty never really does any kind of disconnect or hangup to the original call. Ideas? ____________________ 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*