Date: Sun, 11 Feb 2001 20:05:52 +0100 (CET) From: hm@kts.org (Hellmuth Michaelis) To: prallon@tmp.com.br (Sergio de Souza Prallon) Cc: igorp@inobject.com, freebsd-isdn@freebsd.org Subject: Re: Teles/PCI card Message-ID: <20010211190552.4AEF39B1E@bert.kts.org> In-Reply-To: <20010210174431.A26048@tmp.com.br> from Sergio de Souza Prallon at "Feb 10, 2001 5:44:31 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Sergio de Souza Prallon wrote: > > Feb 10 17:33:16 test /kernel: i4b-L2 F_ILL: FSM function F_ILL executing > > Feb 10 17:33:16 test /kernel: i4b-L2 i4b_next_l2state: FSM illegal state, > > state = ST_EST_AW_TEI, event = EV_DL This error messages are horrible, something - whatever - is really going wrong here. This is strange because the isdntrace output below indicates everything is well ... :-( > > Q931: pd=Q.931/I.451, cr=0x02 (from destination), message=STATUS: > > [cause: 100: Invalid information element contents (Q.850) > > (location=public network serving local user, std=CCITT)] > > [call state: Std=CCITT, State=Call initiated] > > <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< > This is (I think) an exchange generated message saying it disliked > something on the previous `SETUP' frame. Yes. The setup frame and its sub-elements (the information elements) are coded correctly but it does not like the contents of one of the information elements. Unfortunately it has no way of saying which it does not like. It would be helpful to know which type of exchange you are connected to and if there are any restrictions in the services you are subscribed to. > My guess are the phone numbers Seconded. > <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< > I don't know if the following ones are allowed by the specs: apparently > the exchange is trying to re-establish the connection (L2). I4B doesn't > seems to like it. This seems to be a bug in the i4b stack. Just a note: the contents of the frame isdntrace displays as an outgoing frame is the content of what i4b thinks goes out to the wire; it is NOT the contents of the wire which have been read back in some form !!! In other words: what isdntrace displays as frames going from TE->NT may not be what is really going out. I say that because there is a large discrepancy between the i4b kernel error messages at the top of your mail and the clean isdntrace output later on. To be really shure in what the exchange gets from i4b, you have to monitor the bus with an analyzer or a separate (cheap 486, even a 386 is sufficient) PC with 2 isdn cards and i4b/isdntrace in analyze mode. (Hint, Sergio: i still have some old Teles 8-bit ISDN cards here which i use for this purpose and which i´m willing to ship to you ...). hellmuth -- Hellmuth Michaelis hm@kts.org Hamburg, Europe We all live in a yellow subroutine, yellow subroutine, yellow subroutine ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010211190552.4AEF39B1E>