Hylafax Mailing List Archives
|
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
Re: [hylafax-users] MultiTech ISI5634UPCI/8
There is no equivalent downgrade from 1.32i to 1.25p for the ISI5634UPCI/8. I am also surprised that that downgrade fixed the problem below. The only reason I had seen people
downgrading was because of lockups not connect issues. Also (this question is for Mike) I thought the lockups related to 1.32i had to do with your phone lines getting wet or some such thing (see email as of 4/18/2005). Is that not so?
Steve Tuckner
Multi-Tech Systems
-----Original Message-----
From: hylafax-users-bounce@xxxxxxxxxxx
[mailto:hylafax-users-bounce@xxxxxxxxxxx]On Behalf Of Mike McMullen
Sent: Tuesday, September 13, 2005 1:05 PM
To: Chris Funk; 'Lee Howard'
Cc: hylafax-users@xxxxxxxxxxx
Subject: Re: [hylafax-users] MultiTech ISI5634UPCI/8
>
> Chris Funk wrote:
>
>>Sep 12 09:40:40.81: [24105]: RECV received frame number 46
>>Sep 12 09:40:40.85: [24105]: RECV received frame number 47
>>Sep 12 09:40:40.97: [24105]: FCS error
>>Sep 12 09:41:25.83: [24105]: EOT received (end of transmission)
>>Sep 12 09:41:25.83: [24105]: Received premature V.34 termination.
>>
>>
>
>>Unfortunately, there's nothing that HylaFAX can do here.
>
>>The modem tells us that we got an FCS (frame check) error - and that's
>>not that unusual, but from that moment on we don't get any data at all
>>until the line disconnects 45 seconds later.
>>
>>
>>You could try running Class 1 instead of Class 1.0 and see if the same
>>kinds of "sudden disconnections" occur. If they do, then it's probably
>>not the modem firmware (as V.34 will not be used with Class 1).
>>
>>Lee.
>
>
> Thanks Lee. I'll try the class 1. Here is another error I have been
> getting on that modem.
>
> "Failed to properly detect high-speed data carrier."
>
>
I don't know if this is related. However I recently pretty much eliminated
the above error by downgrading the firmware on another brand of
multitech modem (MT5634ZPX-PCI-V92) from 1.32i to 1.25p.
I would assume there is some common code between the different firmware
and it might be the cause of your problem.
Steve Tuckner at Multitech provided me with 1.25p firmware awhile back.
He might be able to shed some light on the potential problem you have and
the one I had.
Mike
____________________ 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*
____________________ 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*