Date: Fri, 1 Jan 1999 19:58:19 +0100 (CET) From: Rene de Vries <rene@canyon.demon.nl> To: freebsd-isdn@FreeBSD.ORG Subject: Re: beta 0.70 (ii) Message-ID: <199901011858.TAA00352@canyon.demon.nl> In-Reply-To: <19981230135806.A29911@hcswork.hcs.de> from Hellmuth Michaelis at "Dec 30, 98 01:58:06 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
I get the same messages "i4b-L1-timer4_expired: state = F3 Deactivated" when
i pick up a normal (analog) phone (behind a Quadrovox; a small ISDN 'PABX')
and dialing (part of) a number an then putting it down again. It always takes
about 10 secs for the message to show-up.
My config is: a Teles S0/16.3 card and a Quadrovox on the same S0 bus. The
analog phones are then connected to the Quadrovox (there are no ISDN phones
;-().
I am located in the Netherlands.
Here is the isdntrace of the senario described above:
=========== isdntrace controller #0 =========== started Fri Jan 1 19:42:25 1999
-- NT->TE - unit:0 - frame:000001 - time:01.01 19:42:29.146517 - length:3 ------
Dump:000 00 c1 73 ..s
Q921: SAP=0 (Call Control), R, TEI=96, U-Frame: UA PF 1
-- NT->TE - unit:0 - frame:000002 - time:01.01 19:42:29.224869 - length:4 ------
Dump:000 00 c1 01 02 ....
Q921: SAP=0 (Call Control), R, TEI=96, S-Frame: RR N(R) 1 PF 0
-- NT->TE - unit:0 - frame:000003 - time:01.01 19:42:29.310381 - length:15 -----
Dump:000 02 c1 00 02 ....
Q921: SAP=0 (Call Control), C, TEI=96, I-Frame: N(S) 0 N(R) 1 P 0
Dump:004 08 01 9d 0d 18 01 89 1e 02 82 88 ...........
Q931: pd=Q.931/I.451, cr=0x1d (from destination), message=SETUP ACKNOWLEDGE:
[channel id: channel=B-1 (exclusive)]
[progress ind: Std=CCITT, Loc=Public network serving local user
Description: In-band info or appropriate pattern now available]
-- NT->TE - unit:0 - frame:000004 - time:01.01 19:42:32.798487 - length:4 ------
Dump:000 00 c1 01 04 ....
Q921: SAP=0 (Call Control), R, TEI=96, S-Frame: RR N(R) 2 PF 0
-- NT->TE - unit:0 - frame:000005 - time:01.01 19:42:33.953760 - length:4 ------
Dump:000 00 c1 01 06 ....
Q921: SAP=0 (Call Control), R, TEI=96, S-Frame: RR N(R) 3 PF 0
-- NT->TE - unit:0 - frame:000006 - time:01.01 19:42:34.590587 - length:4 ------
Dump:000 00 c1 01 08 ....
Q921: SAP=0 (Call Control), R, TEI=96, S-Frame: RR N(R) 4 PF 0
-- NT->TE - unit:0 - frame:000007 - time:01.01 19:42:36.190728 - length:4 ------
Dump:000 00 c1 01 0a ....
Q921: SAP=0 (Call Control), R, TEI=96, S-Frame: RR N(R) 5 PF 0
-- NT->TE - unit:0 - frame:000008 - time:01.01 19:42:36.766425 - length:4 ------
Dump:000 00 c1 01 0c ....
Q921: SAP=0 (Call Control), R, TEI=96, S-Frame: RR N(R) 6 PF 0
-- NT->TE - unit:0 - frame:000009 - time:01.01 19:42:37. 21398 - length:4 ------
Dump:000 00 c1 01 0e ....
Q921: SAP=0 (Call Control), R, TEI=96, S-Frame: RR N(R) 7 PF 0
-- NT->TE - unit:0 - frame:000010 - time:01.01 19:42:40.160047 - length:4 ------
Dump:000 00 c1 01 10 ....
Q921: SAP=0 (Call Control), R, TEI=96, S-Frame: RR N(R) 8 PF 0
-- NT->TE - unit:0 - frame:000011 - time:01.01 19:42:50.201022 - length:4 ------
Dump:000 00 c1 01 11 ....
Q921: SAP=0 (Call Control), R, TEI=96, S-Frame: RR N(R) 8 PF 1
-- NT->TE - unit:0 - frame:000012 - time:01.01 19:42:50.331116 - length:3 ------
Dump:000 02 c1 53 ..S
Q921: SAP=0 (Call Control), C, TEI=96, U-Frame: DISC PF 1
-- NT->TE - unit:0 - frame:000013 - time:01.01 19:43:00.535110 - length:8 ------
Dump:000 fe ff 03 0f 00 00 04 c1 ........
Q921: SAP=63 (TEI-Management), C, TEI=127, Ri=0x0000, IdCheckReq, Ai=96
I expect the IdCheckReq to trigger this time-out, it surely happens (as far as
I can see) at the same time.
Rene
> On Wed, Dec 30, 1998 at 12:47:45PM +0100, Andreas Gaertner wrote:
> > On Wed, 30 Dec 1998, Hellmuth Michaelis wrote:
> >
> > > > so this is to be considered absolutely normal, isn't it?
> > >
> > > No, not quite. What you see is the "persistent deactivation" timeout
> > > happening, which normally should not appear. Although i have no idea
> > > why it happenes at your site. isdntrace with its various options is
> > > your friend to find it out.
> >
> > ok, i will check that out. but as a matter of fact these messages show up
> > after an amount of time a telephone call has taken place.
>
> I have a telephone connected to my ISDN test box too and there this does
> not show up.
>
> So either this seems to be normal in certain environments and the messages
> should not be considered an error or the exchange you are conneted to does
> some strange things on the S0 (looking at your domain, is it possible that
> you are connectd to a HICOM ? :-))
>
> > maybe this is
> > due to isdnd is permanently up because of the call out of /etc/rc.local?
>
> No.
>
> hellmuth
--
Rene de Vries http://www.tcja.nl/~rene; mailto:rene@tcja.nl
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?199901011858.TAA00352>