Date: Tue, 11 Sep 2012 16:52:17 +0200 From: Hans Petter Selasky <hselasky@c2i.net> To: Andreas Longwitz <longwitz@incore.de> Cc: freebsd-isdn@freebsd.org Subject: Re: ISDN4BSD (HPS version) is going into ports Message-ID: <201209111652.17974.hselasky@c2i.net> In-Reply-To: <504F4383.2080503@incore.de> References: <504E1B19.3020901@incore.de> <201209102033.54948.hselasky@c2i.net> <504F4383.2080503@incore.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, On Tuesday 11 September 2012 15:58:27 Andreas Longwitz wrote: > Hi Hans, thanks for reply ! >=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 > >=20 > >> sends a SETUP messagewant_s and asterisk/isdn4bsd answers with SETUP A= CK: > > You need to check the settings in capi.conf for chan_capi. It should te= ll > > I4B to provide a dialtone. >=20 > I have checked capi.conf and did not find something usefull for > dialtone, but your statement gives me the correct hint: >=20 > In struct i4b_controller is a bit called no_layer1_dialtone and this bit > is never initialized, therefore it is zero. In dss1_l3fsm.h the variable > want_dialtone gets value 1 and the call > dss1_l3_tx_setup_acknowledge(cd,NT_MODE(sc),want_dialtone) > therefore sets the flag L3_TX_PROGRESSI and the SETUP_ACK fram created > in dss1_l3_tx_message has the progress indicator included. Everything ok > so far. Then I found, that the creation of the dialtone is done by the > driver type DRVR_DIAL_GEN and therefore the i4b module i4btel is needed. > After make config and activate "Build TEL driver" dialtone works. >=20 > I think this option should be on as a default. Done. >=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.txt. 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 > >>=20 > >> 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 > >>=20 > >> 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 > >>=20 > >> isdnconfig -u 8 intr_mode pcm_64 pcm_map 0 1 end pcm_master \ > >> =20 > >> 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 > For clarification I add that of course I first give the isdnconfig > commands and then the cat's and isdndecode. >=20 > > This might have something to do with the default protocol selected. The= re > > has been some changes in this area. Can you check the manpage of > > isdndebug, and the protocol options available? You will need to set the > > default protocol before opening the device nodes. >=20 > The concept of a "default protocol" is not clear to me. Please can you > describe the difference between > isdnconfig -u 9 -p DRVR_DSS1_NT > and > isdndebug -u 9 -p DRVR_DSS1_NT ? > If I try the latter, the command "cat /dev/ihfc9.0" returns with "device > not configured". You need to run something like this first: isdndebug -u 9 -b 0 -p P_HDLC -b 1 P_HDLC -b 2 P_TRANSPARENT If it doesn't work, I will check later. A bit busy right now. =2D-HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201209111652.17974.hselasky>