Re: [hylafax-users] MODEM Command Error

["George H" <george.dma@xxxxxxxxx>]

I wrote a small linux shell script to demonstrate what I said as well.
It is .. kinda hacky, if there is a linux guru out there who can spice
this up.. Please do and share it with us all :)

Put these two files in /var/spool/fax   (or wherever is the hylafax spool dir)
Also read in the logger.sh file to tweak vars.

On 5/10/07, George H <george.dma@xxxxxxxxx> wrote:
> On 5/10/07, Lee Howard <faxguy@xxxxxxxxxxxxxxxx> wrote:
> > George H wrote:
> >
> > > faxserver etc # grep -i "009617223632" xferfaxlog
> > > faxserver etc # cd ../log/
> > > faxserver log # grep -i "REMOTE TSI \"009617722801\"" c0000*
> > > c000000266:May 07 09:18:33.60: [31707]: REMOTE TSI "009617223632"
> > > c000000267:May 07 09:21:46.10: [31707]: REMOTE TSI "009617223632"
> > > c000000268:May 07 09:23:29.75: [31707]: REMOTE TSI "009617223632"
> > > c000000269:May 07 09:25:15.90: [31707]: REMOTE TSI "009617223632"
> > > c000000310:May 07 12:23:38.06: [31707]: REMOTE TSI "009617223632"
> > > c000000346:May 07 14:30:11.23: [31707]: REMOTE TSI "009617223632"
> > > c000000449:May 08 12:09:30.70: [20268]: REMOTE TSI "009617223632"
> > > c000000461:May 08 12:34:18.90: [25687]: REMOTE TSI "009617223632"
> > > c000000462:May 08 12:35:57.72: [25687]: REMOTE TSI "009617223632"
> > > c000000463:May 08 12:37:53.34: [25687]: REMOTE TSI "009617223632"
> > > c000000487:May 08 14:03:56.83: [27238]: REMOTE TSI "009617223632"
> > > faxserver log #
> > >
> > > As you can see there is a serious problem with this TSI, it is not
> > > logged in xferfaxlog but has 11 log files in the /var/spool/fax/log
> > > directory.
> >
> >
> > On an incoming fax call you should typically see two xferfaxlog entries:
> > a CALL record and a RECV record.  Did you not get CALL records in
> > xferfaxlog that correspond (in time, not necessarily in TSI) with the
> > session log?
> >
>
> Yeah it seems you are correct. xferfaxlog does log the failed entries
> as CALL records, unfortunately they don't have the TSI number listed.
> When doing a search to look for a match I have to grep it by the date
> and time (though I don't know if down to the minute is enough, by the
> second would be more accurate.) I ran the command below to find the
> first failure from the list above. Lucky for us it lists the log file
> number too so I am sure this is for that entry (cos the TSI is not
> shown).
>
> faxserver etc # grep -i "05/07/07 09:18" xferfaxlog
> 05/07/07 09:18  CALL    000000266       ttyS5           ""      fax
>  "737556"        ""      0       0       0:36    0:36"RSPREC error/got
> EOT"  ""      ""      ""      ""      ""
>
> This is the stuff I need to know about, how many times I get failed
> CALL records and to which TSI (I assume because the TSI is in the
> c000* log file that it could also be in the xferfaxlog ?) and through
> that I can see the numbers on how many times it failed, succeeded
> ..etc.
>
> --
> "Nothing is impossible for the person that doesn't have to do it"
> "The probability of anything happening is in inverse ratio to its desirability"
> "If I were a roman statue, I'd be made alabastard"
> --
> George H
> george.dma@xxxxxxxxx


--
"Nothing is impossible for the person that doesn't have to do it"
"The probability of anything happening is in inverse ratio to its desirability"
"If I were a roman statue, I'd be made alabastard"
--
George H
george.dma@xxxxxxxxx

Attachment: logger.sh
Description: Bourne shell script

Ring detected without successful handshake
No local dialtone
COMREC invalid response received
No answer (T.30 T1 timeout)
T.30 T2 timeout, expected page not received
RSPREC error/got DCN
COMREC received DCN
Unspecified Receive Phase B error
RSPREC error/got EOT
RSPREC invalid response received
Failure to train modems
Failed to properly detect high-speed data carrier.