From owner-freebsd-isdn@FreeBSD.ORG Mon Sep 10 18:37:58 2012 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2165A1065673 for ; Mon, 10 Sep 2012 18:37:58 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe02.c2i.net [212.247.154.34]) by mx1.freebsd.org (Postfix) with ESMTP id 8D1178FC14 for ; Mon, 10 Sep 2012 18:37:57 +0000 (UTC) X-T2-Spam-Status: No, hits=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 Received: from [176.74.212.201] (account mc467741@c2i.net HELO laptop015.hselasky.homeunix.org) by mailfe02.swip.net (CommuniGate Pro SMTP 5.4.4) with ESMTPA id 318579007; Mon, 10 Sep 2012 20:32:49 +0200 From: Hans Petter Selasky To: freebsd-isdn@freebsd.org Date: Mon, 10 Sep 2012 20:33:54 +0200 User-Agent: KMail/1.13.7 (FreeBSD/9.1-PRERELEASE; KDE/4.8.4; amd64; ; ) References: <504E1B19.3020901@incore.de> In-Reply-To: <504E1B19.3020901@incore.de> X-Face: 'mmZ:T{)),Oru^0c+/}w'`gU1$ubmG?lp!=R4Wy\ELYo2)@'UZ24N@ =?iso-8859-1?q?d2+AyewRX=7DmAm=3BYp=0A=09=7CU=5B?=@, _z/([?1bCfM{_"B<.J>mICJCHAzzGHI{y7{%JVz%R~yJHIji`y> =?iso-8859-1?q?Y=7Dk1C4TfysrsUI=0A=09-=25GU9V5=5DiUZF=26nRn9mJ=27=3F=26?=>O MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Message-Id: <201209102033.54948.hselasky@c2i.net> Cc: Andreas Longwitz Subject: Re: ISDN4BSD (HPS version) is going into ports X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Sep 2012 18:37:58 -0000 On Monday 10 September 2012 18:53:45 Andreas Longwitz wrote: > Hi, >=20 Hi, > I try to get ISDN4BSD from ports (rev 2349) with FreeBSD 8.3 working. > My first step was to run isdnd, that works fine now. Second step is to > run asterisk with chan_capi. So far I had run FreeBSD 8.2 and i4b > integrated manually, but that should not make any difference. Two > problems appeared after my update and I could not find the reason. >=20 > Problem 1: If I take up the receiver of a ISDN telephone I do not hear > the dial tone. I hear nothing. I can dial and that works. The phone > sends a SETUP messages and asterisk/isdn4bsd answers with SETUP ACK: You need to check the settings in capi.conf for chan_capi. It should tell I= 4B=20 to provide a dialtone. >=20 > -- TE->NT - unit:11 > L3 04 08 00001000 Protocol =3D Q.931/I.451/DSS1 (0x08) > L3 05 01 0000---- Call Reference > ----0001 Call Reference length is 1 byte > L3 06 01 0------- Call Reference is sent from call originator > -0000001 Call Reference =3D 1 =3D 0x01 > L3 07 05 0------- Message type extension =3D 0 > -0000101 Message type =3D SETUP > L3 04 08 00001000 Protocol =3D Q.931/I.451/DSS1 (0x08) > L3 05 01 0000---- Call Reference > ----0001 Call Reference length is 1 byte > L3 06 01 0------- Call Reference is sent from call originator > -0000001 Call Reference =3D 1 =3D 0x01 > L3 07 05 0------- Message type extension =3D 0 > -0000101 Message type =3D SETUP (0x05) > L3 08 04 0------- Variable length Information element > -0000100 IE =3D bearer capability > L3 09 03 00000011 IE Length =3D 3 bytes > L3 0A 80 1------- Extension Bit =3D 1 (no extension, final octet) > -00----- Coding standard =3D CCITT > ---00000 Capability =3D 0x00, speech > L3 0B 90 1------- Extension Bit =3D 1 (no extension, final octet) > -00----- Mode =3D 0x00, circuit > ---10000 Rate =3D 0x10, 64 kbit/s > L3 0C A3 1------- Extension Bit =3D 1 (no extension, final octet) > -01----- Layer 1 identity =3D 1 > ---00011 Layer 1 Protocol =3D 0x03, G.711 a-Law > L3 0D 6C 0------- Variable length Information element > -1101100 IE =3D calling party number > L3 0E 09 00001001 IE Length =3D 9 bytes > L3 0F 00 0------- Extension Bit =3D 0 (with extension, octet follows) > -000---- Type =3D Unknown > ----0000 Plan =3D Unknown (0x0) > L3 10 80 1------- Extension Bit =3D 1 (no extension, final octet) > -00----- Presentation =3D allowed > ---000-- Spare > ------00 Screening =3D user provided, not screened > L3 11 34 00110100 Number digit =3D 4 > L3 12 39 00111001 Number digit =3D 9 > L3 13 39 00111001 Number digit =3D 9 > L3 14 34 00110100 Number digit =3D 9 > L3 15 30 00110000 Number digit =3D 9 > L3 16 36 00110110 Number digit =3D 9 > L3 17 38 00111000 Number digit =3D 9 > L3 18 7D 0------- Variable length Information element > -1111101 IE =3D high layer compatibility > L3 19 02 00000010 IE Length =3D 2 bytes > L3 1A 91 1------- Extension Bit =3D 1 (no extension, final octet) > -00----- Coding standard =3D CCITT > ---100-- Interpretation =3D first > ------01 Presentation =3D High layer protocol profile > L3 1B 81 1------- Extension Bit =3D 1 (no extension, final octet) > -0000001 Characteristics =3D Telephony (0x01) (0x05) > L3 08 04 0------- Variable length Information element >=20 > - NT->TE - unit:11 > L3 04 08 00001000 Protocol =3D Q.931/I.451/DSS1 (0x08) > L3 05 01 0000---- Call Reference > ----0001 Call Reference length is 1 byte > L3 06 81 1------- Call Reference is sent to call originator > -0000001 Call Reference =3D 1 =3D 0x01 > L3 07 0D 0------- Message type extension =3D 0 > -0001101 Message type =3D SETUP_ACKNOWLEDGE (0x0d) > L3 08 18 0------- Variable length Information element > -0011000 IE =3D channel identification > L3 09 01 00000001 IE Length =3D 1 bytes > L3 0A 89 1------- Extension Bit =3D 1 (no extension, final octet) > -0------ Interface Id present =3D No > --0----- Interface Type =3D BRI > ---0---- Spare > ----1--- Channel is exclusive > -----0-- Channel is not the D-Channel > ------01 Channel =3D B-1 > L3 0B 1E 0------- Variable length Information element > -0011110 IE =3D progress indicator > L3 0C 02 00000010 IE Length =3D 2 bytes > L3 0D 82 -00----- Coding standard =3D CCITT > ----0010 location =3D Public network serving local user > L3 0E 88 -0001000 description =3D In-band info or appropriate pattern now > available >=20 > There are no more packets in L3. The last "description" in the SETUP ACK > indicates that the missing dialtone should be send in-band by asterisk, > but I am not quite sure. In my configuration I did nothing special for > getting the dialtone, this worked always out of the box. >=20 > Problem 2: I tried to get more information for problem 1 with the > analyze mode of isdndecode using the custom cable as decribed in cable.tx= t. > I connected my ISDN phone to an "ISDN Basisanschlu=DF" with my cable box > between them (receiving side unit 8, sending side unit 9), but after > the commands > cat /dev/ihfc8.X > /dev/null 2>&1 & (X=3D0,1,2) > cat /dev/ihfc9.X > /dev/null 2>&1 & > isdndecode -a -b -R 8 -T 9 -i -x > I can only see D-channel data from the NT-side, nothing from the phone > and no information from any B-channel, but the phone works correct. >=20 > The hardware jumpers on my HFC-4S card of unit 8 and 9 are set to TE > and I have > isdnconfig -u 8 intr_mode pcm_64 pcm_map 0 1 end pcm_master \ > te_mode -p DRVR_DSS1_TE \ > -u 9 intr_mode pcm_64 pcm_map 0 1 end pcm_master > nt_mode -p DRVR_DSS1_NT >=20 > Some time ago this analyze mode worked fine, but now it looks that I am > missing something. >=20 This might have something to do with the default protocol selected. There h= as=20 been some changes in this area. Can you check the manpage of isdndebug, and= =20 the protocol options available? You will need to set the default protocol=20 before opening the device nodes. =2D-HPS