From owner-freebsd-isdn Wed May 12 2: 4:45 1999 Delivered-To: freebsd-isdn@freebsd.org Received: from fredead.systems.pavilion.net (fredead.systems.pavilion.net [194.242.128.49]) by hub.freebsd.org (Postfix) with ESMTP id 388BF15D8D for ; Wed, 12 May 1999 02:04:30 -0700 (PDT) (envelope-from sam@pavilion.net) Received: by fredead.systems.pavilion.net (Postfix, from userid 105) id 4D3C225874; Wed, 12 May 1999 10:04:29 +0100 (BST) Date: Wed, 12 May 1999 10:04:29 +0100 From: Sam Eaton To: Hellmuth Michaelis Cc: freebsd-isdn@FreeBSD.ORG Subject: Strange ISDN Failures Message-ID: <19990512100428.A28943@fredead.pavilion.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've got one box out of 25 or so out on customer sites, that is having no end of ISDN errors. All the rest are basically fine. I was hoping someone could at least point me at what to debug next... The machine is running FreeBSD 2.2.7, with i4b 0.70 (yes I know it's old, but it's the same config as lots of other machines that are fine) We're also running Eivind's raw b-channel patches, and a modified MPD to do multilink, but I don't think that's the problem. Basically, several times a day, their ISDN line just 'stops working' as far as the customer is concerned - and they have to kill and restart the isdnd to restore service. The log file does show errors, but I'm not sure how to interpret them : May 12 09:40:39 ninaa /kernel: EE-rbch0: attempting dialout (DTR) May 12 09:40:39 ninaa /kernel: i4b-L2-i4b_rxd_ack: ((N(R)-1)=3) != (UA=4) !!! May 12 09:40:39 ninaa /kernel: i4b-L2-i4b_i_frame_queued_up: V(S) == ((V(A) + k) & 127)! May 12 09:40:39 ninaa /kernel: i4b-L2-i4b_i_frame_queued_up: state = ST_MULTIFR May 12 09:40:39 ninaa /kernel: i4b-L2-i4b_print_l2var: unit0 V(R)=7, V(S)=5, V(A)=4,ACKP=0,PBSY=0,OBSY=0 May 12 09:40:39 ninaa /kernel: EE-rbch1: Disconnecting (0xf027accc) And then a little later : May 12 09:40:43 ninaa /kernel: EE-rbch0: attempting dialout (DTR) May 12 09:40:43 ninaa /kernel: i4b-L3-T308_timeout: REL not answered, cr = 31 May 12 09:40:43 ninaa /kernel: i4b-L3-next_l3state: FSM illegal state, state = ST_U12 - Disc Ind, event = EV_T308 EXP - T308 timeout! And then a few seconds later : May 12 09:40:49 ninaa /kernel: i4b-L3-T303_timeout: SETUP not answered, cr = 112 May 12 09:41:21 ninaa /kernel: i4b-L3-T305_timeout: DISC not answered, cr = 112 May 12 09:41:23 ninaa /kernel: i4b-L3-i4b_decode_q931: cannot find calldescriptor for cr = 0x70, crflag = 0x1, ms g = 0x5a, frame = 0x5a 0x8 0x2 0x82 0x90 May 12 09:41:27 ninaa /kernel: i4b-L3-T303_timeout: SETUP not answered, cr = 101 May 12 09:41:28 ninaa /kernel: i4b-L3-i4b_decode_q931_message: STATUS message May 12 09:41:58 ninaa /kernel: i4b-L3-T305_timeout: DISC not answered, cr = 101 May 12 09:42:01 ninaa /kernel: i4b-L3-i4b_decode_q931: cannot find calldescriptor for cr = 0x65, crflag = 0x1, ms g = 0x5a, frame = 0x5a 0x8 0x2 0x82 0x90 May 12 09:42:05 ninaa /kernel: i4b-L3-T303_timeout: SETUP not answered, cr = 15 It continues for a while like this (it's trying to dial out during this) and then the customer kills the isdnd and restarts it - after which it works for a while, then fails again. We've tried swapping all the hardware and cabling. The only thing that is different in this setup from all the working machines is that the ISDN line comes from a different company (cable and wireless as opposed to BT for all the working ones). Cable and Wireless claim the line is fine, and have had a protocol analyzer on the line for testing, at which point they still claim that the line is fine and our machine is at fault. We're going to upgrade them to i4b 0.80, but I'm not convinced this will help, seeing as the other machines work fine as they are... Any help would be greatly appreciated. I'd be happy to put another machine in to capture packets for analysis, if someone can help me interpret them - I've read the specs, and mostly understand what's happening, but I don't understand all of the i4b code as well as some of you.... Thanks, Sam. -- ------------------------------------------------------------------------ Sam Eaton Senior Systems Manager, Pavilion Internet Plc "Fortified with essential bitterness and sarcasm" ------------------------------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message