On Thu, Aug 24, 2006 at 01:17:41PM +0200, Arne Metzger wrote: > Lionel Elie Mamane schrieb am 24.08.2006 00:00: >>On Wed, Aug 16, 2006 at 10:29:39AM +0200, Arne Metzger wrote:
>>>just found in /var/spool/hylafax/log/xferfaxlog: >>>08/14/06 15:48 RECV 00000051 faxCAPI "" fax >>>"xxx" "+49 " 267 1 0:24 0:14 "" >>>the call on 08/14/06 15:48 was made using web.de >>>in the original file wordpad show me some special characters in >>>CIDNumber field. >>>i can't even copy that file into this mail (using win xp at work). >>>so i attached the file. >>I see. I've put a new version at >>http://people.debian.org/~lmamane/capi4hylafax/ . Please try it out >>(follow the same procedure as with the version you got from sid: >>unpack, edit debian/control, build .debs, install, test if bug is >>still there). > OK, package has been built and installed. nothing special so far and > working good. > But now the following happens: > Aug 24 12:54:31.48: [11862]: c2faxrecv - INFO: > Aug 24 13:01:33.89: [11865]: c2faxrecv - INFO: SESSION BEGIN 000000061 > +49.461.9093555 > Aug 24 13:01:33.89: [11865]: c2faxrecv - INFO: Incoming analog call on > controller 1 to 9093555. > Aug 24 13:01:43.64: [11865]: c2faxrecv - INFO: Connection established. > Aug 24 13:01:43.64: [11865]: c2faxrecv - INFO: BaudRate = 64000 > Aug 24 13:01:43.64: [11865]: c2faxrecv - INFO: Flags = HighRes, > MMR_compr > Aug 24 13:01:43.67: [11865]: c2faxrecv - INFO: Write fax in path > /var/spool/hylafax to file recvq/fax000000016.tif. > Aug 24 13:01:47.60: [11865]: c2faxrecv - INFO: Page 1 was received. - > Last Page! > Then i have to kill the c2faxrecv-process manually, because it wont > react on incoming calls anymore. > this happens on all incoming calls - with CIDNumber and without. Hmmm... That was a brown paper bag bug. I've put a new version at the same place; this was prepared during the day instead of during the night, so it should be better quality. (It works for me at least, this time I've tested it.) -- Lionel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
