Re: [hylafax-users] Failed to properly detect high-speed data carrier

[Lee Howard <faxguy@xxxxxxxxxxxxxxxx>]

Many different modems?

Which modems?

The failure is exactly the same with all of these different modems?  (an 
OK response to AT+FRM=146)

Lee.


EISELE Pascal wrote:

> First of all, thanks for the answer ;)
> Is the problem comming from the sender or the receiver ? I've tryed 
> many different modem on the receiver without succes. I'm using Class 1 
> mode, so it should be a software problem, isn't it ?
>
>
> Lee Howard a écrit :
>
> > EISELE Pascal wrote:
> >
> > > Hello,
> > >
> > > I'm currently testing HylaFax 4.2.1 under Solaris 9 (self-compiled) 
> > > and Debian GNU/Linux 3.1 with two identical modem : Kortex Novafax 
> > > 56000 Vocal  + V90.
> > > They are configured in Class 1 mode on both machine.
> > > When I send a fax from Linux to Solaris, it's working fine.
> > > When I send a fax from Solaris to Linux, it failed with error 
> > > "Failed to properly detect high-speed data carrier".
> > > When I send a fax from Solaris to anywhere it's working great. When 
> > > a I send a fax from Linux to anywhere it's working great too !
> > > I think my problem is comming from receving fax under Linux.
> >
> >
> >
> > > Mar 02 16:44:08.15: [ 1041]: --> [7:CONNECT]
> > > Mar 02 16:44:09.47: [ 1041]: --> [2:OK]
> > > Mar 02 16:44:09.47: [ 1041]: <-- [11:AT+FRM=146\r]
> > > Mar 02 16:44:16.58: [ 1041]: --> [2:OK]
> > > Mar 02 16:44:16.58: [ 1041]: <-- [9:AT+FRS=7\r]
> > > Mar 02 16:44:16.71: [ 1041]: --> [2:OK]
> > > Mar 02 16:44:16.72: [ 1041]: RECV FAX: Failed to properly detect 
> > > high-speed data carrier.
> > >  
> > Yeah,  the problem is that AT+FRM=146 should *not* result in OK.  The 
> > OK result indicates a return to command-mode.  AT+FRM=146 should 
> > result in CONNECT and then later NO CARRIER, or +FCERROR... or even 
> > possibly ERROR.  OK doesn't mean anything, really, except that it 
> > "failed to properly detect the high-speed data carrier".
> >
> > Get with your modem manufacturer and find out what the modem is doing 
> > at that point.  If they can tell you a workaround, then let us know, 
> > and we can do something.  Otherwise, they'll need to fix the firmware.
> >
> > Lee.
> >
> >
> > ____________________ 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, don't mail 
> > sales@xxxxxxxxx*
>
>
> --
> EISELE Pascal <mailto:peisele@xxxxxxxxxxx> 	Direct : +33 (0)3 88 65 76 78
> Administrateur systèmes & réseaux 	Tél : +33 (0)3 88 65 04 04
> 13b rue du Maréchal Lefebvre 	Fax : +33 (0)3 88 65 76 76
> 67100 Strasbourg 	http://www.appligos.fr <http://www.appligos.fr/>


____________________ 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*