Re: [hylafax-users] zyxel u-1496e config

[Lee Howard <faxguy@deanox.com>]

At 03:13 PM 8/30/01 -0500, Dan wrote:

>>Here.  Try this (attached).  Send me the session logs from two consecutive
>>attempts.
>
>Lee thanks for the rpm.  I installed rpm and sent some test faxes looks
>great
>sent about 6 faxes to different numbers all went, tried to fax you but it
>gave me a  No carrier detected error.
>
>Here are the logs you asked for.
>
>thanks for the help :-)
....
>Aug 30 10:01:37.46: [ 1084]: DELAY 75 ms
>Aug 30 10:01:37.54: [ 1084]: <-- [11:AT+FTM=145\r]
>Aug 30 10:01:37.56: [ 1084]: --> [7:CONNECT]
....
>Aug 30 10:01:41.92: [ 1084]: DELAY 75 ms
>Aug 30 10:01:42.00: [ 1084]: <-- [11:AT+FTM=146\r]
>Aug 30 10:01:42.02: [ 1084]: --> [7:CONNECT]
....
>Aug 30 10:03:30.12: [ 1141]: DELAY 75 ms
>Aug 30 10:03:30.20: [ 1141]: <-- [11:AT+FTM=145\r]
>Aug 30 10:03:30.22: [ 1141]: --> [7:CONNECT]
....
>Aug 30 10:03:35.20: [ 1141]: DELAY 75 ms
>Aug 30 10:03:35.28: [ 1141]: <-- [11:AT+FTM=146\r]
>Aug 30 10:03:35.30: [ 1141]: --> [7:CONNECT]

Well, I can tell you that my patch did not fix the problem, and I don't
think that any of the updates towards 4.1.1 did it, either.  Notice here
that your modem is now responding CONNECT rather than NO CARRIER, just as
it should be.  So, I don't know what the problem was, but I'm certain that
my patch was not the solution, because as people on the -devel list have
mentioned, NO CARRIER after +FTM means literally that the remote has hung
up, so aborting the fax is completely proper.

Continuing to use the binary RPM that I sent you will be fine.  My patch
essentially accomplished nothing, since in the real world anything other
than CONNECT is not likely to happen... but *if* a NO CARRIER happened the
only difference would be a 7-second +FTM-looping delay before it hangs up
(looking quite silly to any protocol gurus), anything else other than
CONNECT and NO CARRIER at this point will cause an immediate abortion.

So, my guess is that your original RPM installation was corrupted or the
binary was corrupt, or something like that.

As for not being able to connect with my system - well, it's not important
anymore and not worth the long distance charges, but we could probably try
to resolve that if you encounter that "no carrier detected" scenario at
other places.

Lee.



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