![]() |
> -----Original Message----- > From: hylafax-users-bounce@xxxxxxxxxxx [mailto:hylafax-users- > bounce@xxxxxxxxxxx] On Behalf Of Andrew Rinaldi > Sent: Saturday, April 14, 2007 01:37 > To: hylafax-users@xxxxxxxxxxx > Subject: Re: [hylafax-users] Problems trying to fax from Eicon PRI to > Eicon PRI > > Hi Ulf, > > We know that the Eicon Analog firmware is broken in a number of areas. If > the PRI firmware is based on the same code then I think your best hope is > to > work with iFAX to see if they can help debug the issues. Unfortunately, > with the Eicon software layer doing most of the work, HylaFAX has a > reduced > ability to overcome problems. As far I understand the driver, it loads the firmware during start of the driver, which would mean both sites would be loading the same code. > > Regards > > ANDREW RINALDI > Mainpine Limited - Support > USA +1 503 822 9944 | Asia/Europe +44 1225 869439 > andrew.rinaldi@xxxxxxxxxxxx | www.mainpine.com > > -----Original Message----- > From: hylafax-users-bounce@xxxxxxxxxxx > [mailto:hylafax-users-bounce@xxxxxxxxxxx] > Sent: 14 April 2007 09:21 > To: hylafax-users@xxxxxxxxxxx > Subject: Re: [hylafax-users] Problems trying to fax from Eicon PRI to > Eicon > PRI > > > -----Original Message----- > > From: Ulf Zimmermann > > Sent: Saturday, April 14, 2007 00:59 > > To: Ulf Zimmermann; hylafax-users@xxxxxxxxxxx > > Subject: RE: [hylafax-users] Problems trying to fax from Eicon PRI to > > Eicon PRI > > > > > -----Original Message----- > > > > > > I currently have 3 servers. Two in Fremont, CA and one in Phoenix, > AZ. > > > In Fremont one server has a Patton 2977 card with an older Hylafax > > > install and another server with an Eicon PRI card with Hylafax > > > Enterprise 2.4.7. > > > > > > In Phoenix I had a Patton 2977 card and just swapped it with an > Eicon > > > PRI and then upgraded the OS (RedHat EL4) and installed Hylafax > 4.3.3. > > > > > > When I try to fax from Eicon server in Fremont to the Eicon server > in > > > Phoenix, I get on the Phoenix side just: > > > > > > On the Fremont side I get the job rejected with "High resolution > > > document is not supported by client" and the log looks like: > > > > > > > Ok, it seems to be a Hylafax Enterprise issue. Phoenix to Phoenix > works. > > Fremont-Eicon to Fremont-Eicon doesn't. Even after getting both sides > to > > the same Eicon software. Upgraded Hylafax Enterprise to 2.4.9. Time to > try > > Hylafax 4.3.3 on the Fremont side to see what it does. > > > > Ulf. > > > > Or not. Hylafax 4.3.3 on that machine instead of Enterprise 2.4.9, same > problem. It got the same Divas config, with exception of serial number. > Same modem config file, again only difference is the area code and local > number. No idea left here. > > > ____________________ 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* ____________________ 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*