From owner-freebsd-isdn Thu May 28 09:46:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA07615 for freebsd-isdn-outgoing; Thu, 28 May 1998 09:46:55 -0700 (PDT) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from foobar.franken.de (root@foobar.franken.de [194.94.249.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA07605 for ; Thu, 28 May 1998 09:46:46 -0700 (PDT) (envelope-from logix@foobar.franken.de) Received: (from logix@localhost) by foobar.franken.de (8.8.8/8.8.5) id SAA00440; Thu, 28 May 1998 18:25:01 +0200 (CEST) Message-ID: <19980528182501.41880@foobar.franken.de> Date: Thu, 28 May 1998 18:25:01 +0200 From: Harold Gutch To: freebsd-isdn@FreeBSD.ORG Subject: Re: i4b not working References: <19980528151603.23028@foobar.franken.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <19980528151603.23028@foobar.franken.de>; from Harold Gutch on Thu, May 28, 1998 at 03:16:03PM +0200 X-Organisation: BatmanSystemDistribution X-Mission: To free the world from the Penguin Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, May 28, 1998 at 03:16:03PM +0200, Harold Gutch wrote: > installing isdn4bsd worked without the slightest problem for me, > as did the compiling of the new kernel. > > The kernel now finds my ISDN-card: > > isic0 at 0xd80 irq 5 maddr 0xd0000 msize 4096 flags 0x2 on isa > isic0: Teles S0/16, Creatix ISDN S0-16 or Niccy 1016 > isic0: ISAC 2085 Version V2.3 (B3) (IOM-1) (Addr=0xf00d0100) > isic0: HSCX 82525 or 21525 Version 2.1 (AddrA=0xf00d0180, > AddrB=0xf00d01c0) > [...] > i4b: ISDN call control device attached > i4bisppp: 4 ISDN SyncPPP device(s) attached > i4bctl: ISDN system control port attached > i4bipr: 4 IP over raw HDLC ISDN device(s) attached > i4btel: 2 ISDN telephony interface device(s) attached > i4brbch: 4 raw B channel access device(s) attached > i4btrc: 4 ISDN trace device(s) attached > > After playing around a little i found out what /etc/rc.isdn, > /etc/isdn/isdnd.rc etc. were good for - but i still am not able > to dial out or receive incoming calls. Not even isdntest works: > > root@foobar:~ # /usr/src/i4b/isdntest/isdntest -c 0 -i 12345 > -o 98765 > isdntest: accepting calls from telephone number [12345] > isdntest: calling out telephone number [98765] > isdntest: got cdid 46 from kernel > isdntest: calling out to telephone number [98765] > isdntest: incoming disconnect indication, cdid 46, cause 0 > > (using real phonenumbers of course - which i tried with and > without the city code, neither worked) > > perhaps the following error messages will help: > > /kernel: i4b-L2-i4b_mdl_error_ind: unit = 0, location = F_AE11 > /kernel: i4b-L2-i4b_mdl_error_ind: error = MDL_ERR_G: unsuccessful > transmission N200times - SABME > > (which btw is exactly the same errormsg i get when configuring > isppp0 using ifconfig while isdnd is running) > > I dont know wether isdntrace-logs will provide any more > debugging-help, and I dont really know how to cut out the really > relevant information either, but I of course could provide a > complete isdntrace-log of this time-frame. > > I still have another ISDN-card, the Teledat 100, but i dont know > what cards it is compatible to, if any, so i dont know if i could > try using that card instead of the Creatix card. > > Oh, btw, i have a running modem-connection using pppd when > testing isdn4bsd - but i dont think that might make any problems, > or did i perhaps discover some bug ? :) > Ok, after doing a few tests, i found out the following: If i shutdown my modem-connection, kill pppd etc., i in fact can dial-out (I only tested it with isdntest). I discovered that i was able to call another of my MSNs, but i guess it should make no difference wether i call one of my MSNs or any other "external" number. That was where the next problems arose :). When starting isdntest the first time my phone rang very shortly (~0.3s) and i got a bunch of errormsgs: /kernel: i4b-L2-i4b_tei_assign: tx TEI ID_Request /kernel: i4b-L2-i4b_tei_rx_frame: TEI ID Assign - TEI = 65 /kernel: i4b-L4-i4b_l4_setup_timeout: 896369451: ERROR: idletime[536961280]+earlyhup[-272638980] > unitlength[11781]! I then started isdntest a second time directly afterwards. Now my phone rang longer, i got more errormsgs ending with a message on the screen asking me to press a key to reboot, which i did. Some time during the bootup-sequence (i guess when probing isic0) the ringing of my phone stopped. Here are the errormsgs i got: /kernel: i4b-L2-i4b_i_frame_queued_up: V(S) == ((V(A) + k) & 127)! /kernel: i4b-L2-i4b_i_frame_queued_up: state = ST_TIMREC /kernel: i4b-L2-i4b_print_l2var: unit0 V(R)=3, V(S)=4, V(A)=3,ACKP=0,PBSY=0,OBSY=0 /kernel: i4b-L2-i4b_invoke_retransmission: nr = 4 /kernel: i4b-L2-i4b_i_frame_queued_up: V(S) == ((V(A) + k) & 127)! /kernel: i4b-L2-i4b_i_frame_queued_up: state = ST_MULTIFR /kernel: i4b-L2-i4b_print_l2var: unit0 V(R)=5, V(S)=5, V(A)=4,ACKP=0,PBSY=0,OBSY=0 /kernel: i4b-L3-i4b_decode_q931: cannot find calldescriptor for cr = 0xa, crflag = 0x1, msg = 0x4d, frame = 0x4d 0x1c 0x15 0x91 0xa1 0x12 0x2 0x2 0x3f 0x5f 0x2 0x1 0x24 0x30 0x9 0x30 0x7 0xa1 0x5 0x30 0x3 0x2 0x1 0x1 /kernel: i4b-L3-T308_timeout: REL not answered, cr = 1 /kernel: i4b-L3-next_l3state: FSM illegal state, state = ST_U12 - Disc Ind, event = EV_T308EXP - T308 timeout! /kernel: i4b-L3-i4b_l3_tx_status: tx STATUS for cr 1 /kernel: i4b-L2-i4b_i_frame_queued_up: V(S) == ((V(A) + k) & 127)! /kernel: i4b-L2-i4b_i_frame_queued_up: state = ST_MULTIFR The next time i tried it, i got the following errors (i am sorry, but i dont know exactly when i got them - this happened when starting isdntest, perhaps for the first time after the reboot, perhaps for the second time): /kernel: i4b-L2-i4b_tei_assign: tx TEI ID_Request /kernel: i4b-L1-timer3_expired: state = F4 Awaiting Signal /kernel: i4b-L2-i4b_T202_timeout: unit 0, N202 = 3 /kernel: i4b-L2-i4b_tei_assign: tx TEI ID_Request /kernel: i4b-L1-ph_data_req: still in state F3! /kernel: i4b-L1-timer3_expired: state = F4 Awaiting Signal /kernel: i4b-L2-i4b_T202_timeout: unit 0, N202 = 3 /kernel: i4b-L2-i4b_tei_assign: tx TEI ID_Request /kernel: i4b-L1-ph_data_req: still in state F3! /kernel: i4b-L1-ph_data_req: No Space in TX FIFO, state = F4 Awaiting Signal /kernel: i4b-L3-T303_timeout: SETUP not answered, cr = 19 /kernel: i4b-L3-next_l3state: FSM illegal state, state = ST_OW - Out Wait EST, event = EV_T303EXP - T303 timeout! And the following 5 msgs were repeated once every 2 seconds until i pressed a key to reboot: /kernel: i4b-L1-timer3_expired: state = F4 Awaiting Signal /kernel: i4b-L2-i4b_T202_timeout: unit 0, N202 = 3 /kernel: i4b-L2-i4b_tei_assign: tx TEI ID_Request /kernel: i4b-L1-ph_data_req: still in state F3! /kernel: i4b-L1-ph_data_req: No Space in TX FIFO, state = F4 Awaiting Signal Note that this only occured when my ppp-line was down ! When it was up, I got the errormsgs mentioned above (i4b-L2-i4b_mdl_error_ind). I forgot mentioning in my first mail that i am using FreeBSD 2.2.6 and isdn4bsd 0.61 alpha-220598. I am sorry if i flooded this list with useless information, but I considered (at least parts of it) to perhaps be useful for general i4b-debugging, like for example the non-working together with pppd. -- bye, logix Sleep is an abstinence syndrome wich accurs due to lack of coffein. Wed Mar 4 04:53:33 CET 1998 #unix, ircnet To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message