Re: [hylafax-users] Eicon Diva: not receiving faxes

[Lee Howard <faxguy@xxxxxxxxxxxxxxxx>]

Jens Vagelpohl wrote:

> Jan 21 22:24:07 localhost FaxGetty[11220]: MODEM: Model DIVA Unix  
> ISDN Modem
> Jan 21 22:24:07 localhost FaxGetty[11220]: MODEM: Revision Version 1.0
> Jan 21 22:24:07 localhost FaxGetty[11220]: <-- [10:AT+FDCC=?\r]
> Jan 21 22:24:07 localhost FaxGetty[11220]: --> [35:(0,1),(0-D),(0-2), 
> (0-2),0,(0-2),0,0]
> Jan 21 22:24:07 localhost FaxGetty[11220]: --> [2:OK]
> Jan 21 22:24:07 localhost FaxGetty[11220]: Error parsing AT+FDCC=?  
> response: "(0,1),(0-D),(0-2),(0-2),0,(0-2),0,0"
> <continuing communication snipped> 


Eicon "Class 2" is a very curious piece of workmanship.

Per spec Class 2 devices are supposed to use decimal values for most all 
responses, including the +FDCC response.  Class 2.0/2.1 devices are 
supposed to use hexadecimal.  In fact, in days gone by Eicons used to 
say "(0-13)" instead of "(0-D)".

Well, without going into a bunch of other things the bottom-line is that 
the Eicon Class 2 behavior is an amalgam of Class 2 and Class 2.1.  It 
behaves like a Class 2.1 modem, but the AT commands are done with Class 
2.  This curiosity makes creating a stable config file template a bit 
difficult... especially since some of the behaviors have changed over time.

In this particular instance, you should simply add this to your modem 
config file:

 Class2UseHex: yes

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, mail sales@xxxxxxxxx*