From owner-freebsd-isdn@FreeBSD.ORG Mon May 10 10:56:24 2004 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 D55FA16A4CE for ; Mon, 10 May 2004 10:56:24 -0700 (PDT) Received: from mail3.ewetel.de (mail3-126.ewetel.de [212.6.122.126]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F93043D41 for ; Mon, 10 May 2004 10:56:21 -0700 (PDT) (envelope-from twinterg@gmx.de) Received: from kalak.lemur.nord.de (dialin-80-228-52-242.ewe-ip-backbone.de [80.228.52.242]) by mail3.ewetel.de (8.12.1/8.12.9) with ESMTP id i4AHtrnX028456; Mon, 10 May 2004 19:55:57 +0200 (MEST) Received: from gmx.de (lullog.lemur.nord.de [192.168.2.4]) by kalak.lemur.nord.de (8.12.3/8.12.3) with ESMTP id i47HrSWG042140; Fri, 7 May 2004 19:53:28 +0200 (CEST) (envelope-from twinterg@gmx.de) Message-ID: <409BCD18.1050207@gmx.de> Date: Fri, 07 May 2004 19:53:28 +0200 From: Thomas Wintergerst User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5) Gecko/20031208 X-Accept-Language: de-de, de, en-us, en MIME-Version: 1.0 To: Juha-Matti Liukkonen References: <20040427183104.A72883@saturn.kn-bremen.de> <20040506183919.A39741@saturn.kn-bremen.de> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-CheckCompat: OK cc: freebsd-isdn@freebsd.org cc: Juergen Lock Subject: Re: default MSN X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 May 2004 17:56:24 -0000 Hi Juha-Matti, Juha-Matti Liukkonen wrote: > Hi, > > giving MSN 0 via local-phone-dialout makes at least the AVM CAPI > adapters (B1 BRI, T1 PRI) default properly when CONNECT_REQ is sent > (the callee sees the base number of the interface's number space with > PRI, or the primary number with BRI). > > This behaviour is _not_ defined in the CAPI 2.0 specification, though > (Calling Party Number struct, p.81, and CONNECT_REQ, p.27, in > COMMON-ISDN-API Version 2.0, Part I, 4th Edition), and may thus be > only an AVM feature. Definitely worth a check if/when other > manufacturers' CAPI adapters become supported. Are You sure this is a "feature" of the AVM controllers? I would suspect, the connected PBX (or switch) looks at sender number, decides that it does not fit into the allowed numbers and substitutes it with the base number of the line. Other PBXs may behave differently and reject a call with an invalid sender number. -- Gruss, Thomas Wintergerst