![]() |
What would be a sufficient ServerTracing value to use in order to determine the problem more exactly?
I tried 0x00015 (ServerTracing: 21 if my math/understanding is right..)
and got a little more information, which I've attached. Send transcript only, this time. What I ended up with looks pretty similar to what you were describing.
Feb 22 13:16:12.27: [17917]: SEND send PPS (partial page signal) Feb 22 13:16:12.27: [17917]: SEND send MPS (more pages, same document) Feb 22 13:16:12.27: [17917]: <-- [9:AT+FRH=3\r] Feb 22 13:16:14.95: [17917]: --> [7:CONNECT] Feb 22 13:16:16.51: [17917]: --> [5:ERROR] Feb 22 13:16:16.51: [17917]: MODEM Command error Feb 22 13:16:16.51: [17917]: FCS error
I've found that we have two spare internal PCI modems in a recently retired server that I will probably end up replacing these USR modems with.
whenever I use minicom -o to connect to the device (and ^A Q to quit without reset) it doesn't seem like it actually is connecting to the device, as typing does not work.
____________________ 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@xxxxxxxxx*