From owner-freebsd-isdn@FreeBSD.ORG Sun Jan 23 18:23:33 2005 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D60B016A4D3 for ; Sun, 23 Jan 2005 18:23:33 +0000 (GMT) Received: from mail2.ewetel.de (mail2.ewetel.de [212.6.122.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E6D743D58 for ; Sun, 23 Jan 2005 18:23:32 +0000 (GMT) (envelope-from Thomas.Wintergerst@nord-com.net) Received: from kalak.lemur.nord.de (dialin-80-228-53-199.ewe-ip-backbone.de [80.228.53.199]) by mail2.ewetel.de (8.12.1/8.12.9) with ESMTP id j0NINSFS009298; Sun, 23 Jan 2005 19:23:29 +0100 (MET) Received: from [192.168.2.131] (crest-w2k.lemur.nord.de [192.168.2.131]) by kalak.lemur.nord.de (8.12.3/8.12.3) with ESMTP id j0NHtQl8045915; Sun, 23 Jan 2005 18:55:30 +0100 (CET) (envelope-from Thomas.Wintergerst@nord-com.net) Message-ID: <41F3E50D.8090407@nord-com.net> Date: Sun, 23 Jan 2005 18:55:25 +0100 From: Thomas Wintergerst User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: =?ISO-8859-15?Q?Joachim_B=F6ddeker?= References: <005c01c4fef3$cba9afe0$0b01a8c0@aruba> In-Reply-To: <005c01c4fef3$cba9afe0$0b01a8c0@aruba> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 8bit X-CheckCompat: OK cc: freebsd-isdn@freebsd.org cc: Jan Stocker Subject: Re: Freebsd 5.3 / c4b / capi4hylafax / hylafax MSN problem X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: twinterg@gmx.de List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jan 2005 18:23:34 -0000 Hi Joachim, Joachim Böddeker wrote: > Hi. > > I hav some trouble to get the combination of > Freebsd 5.3, c4b, capi4hylafax and hylafax to work together correctly. (all current versions) > > This runs with an AVM-B1-PCI. > > Basically it works, but I have some trouble regarding the MSNs. > > 1. Incoming MSN is not working. > "c2faxrecv -v" prints out the correct called number, but regardless of it, the B1 accepts the call (even if it is not in > IncomingMSNs). > > If I use AcceptGlobalCalls=0, then I receive > > Workaround is: > AcceptSpeech=0 > AcceptGlobalCalls=1 > > It would be nice to get the following working: > IncomingMSNs=xxx,yyy,zzz > AcceptSpeech=(0|1) > AcceptGlobalCalls=0 AFAIK this is a known problem of the capi4hylafax part. Jan Stocker (one of the Cc:s of this mail) is working on it (or wants to as soon if he has time for ist). > > 2. Outgoing MSN is not working > Regardless of what is entered as OutgoingMSN, the fax is always send with the standard MSN (which should is unknown on the FreeBsd > Server). The reason could be that an empty caller id is sent? > > No Workaround yet. As You wrote in Your following mail this now seems to work. If it does not work, there are some cases that may lead to signaling the "base" MSN of Your line. - If You do not specify any sender number, the switch You are attached to will report Your "base" MSN to the called party. The same is true for sender numbers that do not belong to Your line of have an invalid format. - For a local PBX You normally have to use internal MSNs. The external MSNs have to be linked to the internal ones through the PBX configuration. Maybe a CAPI trace (application level) could shed some light on what capi4hylafax is really sending to the line with the Connect-Request message. [...] -- Thomas Wintergerst From owner-freebsd-isdn@FreeBSD.ORG Sun Jan 23 18:23:34 2005 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 37AAF16A4D0 for ; Sun, 23 Jan 2005 18:23:34 +0000 (GMT) Received: from mail2.ewetel.de (mail2.ewetel.de [212.6.122.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6CB2143D45 for ; Sun, 23 Jan 2005 18:23:33 +0000 (GMT) (envelope-from Thomas.Wintergerst@nord-com.net) Received: from kalak.lemur.nord.de (dialin-80-228-53-199.ewe-ip-backbone.de [80.228.53.199]) by mail2.ewetel.de (8.12.1/8.12.9) with ESMTP id j0NINSFU009298; Sun, 23 Jan 2005 19:23:31 +0100 (MET) Received: from [192.168.2.131] (crest-w2k.lemur.nord.de [192.168.2.131]) by kalak.lemur.nord.de (8.12.3/8.12.3) with ESMTP id j0NHtWl8045920; Sun, 23 Jan 2005 18:55:32 +0100 (CET) (envelope-from Thomas.Wintergerst@nord-com.net) Message-ID: <41F3E514.8070103@nord-com.net> Date: Sun, 23 Jan 2005 18:55:32 +0100 From: Thomas Wintergerst User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: =?ISO-8859-15?Q?Joachim_B=F6ddeker?= References: <02cd01c4ff0f$cbfa7e40$0b01a8c0@aruba> In-Reply-To: <02cd01c4ff0f$cbfa7e40$0b01a8c0@aruba> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 8bit X-CheckCompat: OK cc: freebsd-isdn@freebsd.org cc: Jan Stocker Subject: Re: C4B: capidev : Error sending message 0x8005 0x2007 / capi4hylafax X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: twinterg@gmx.de List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jan 2005 18:23:34 -0000 Hi Joachim, Joachim Böddeker wrote: > Hi. > > I have another problem, seems to be within capidev. Every fax I send is automatically resend due to an error. The problem seems to > be with capidev, because of matching error messages in the logfile. > > "kernel: capidev: E capidev_write: Appl. id 4: Error sending message 0x8005: 0x2007" > > It's always "...: Error sending message 0x8005: 0x2007". > > Looking into the source code i found that this error is used for a returncode differing from CAPI_OK received from the > kcapi_put_message(). > > The result of 0x2007 translates into CCE_ILLEGAL_MSG_PARAMETER. > > The message of 0x8005 translates into C_SUPPL_NOTIFIC_DIVERSION_ACTIVATED. > > Does anybody know, what is happening here? This is a problem of the capi4hylafax part, too. "Message 0x8005" is a CAPI Listen-Request message. But because capi4hylafax sends a message with application id 0 in the message itself, the message is invalid. Jan Stocker knows of this bug and will solve it as soon he has the time for it. -- Thomas Wintergerst