Re: (PM) Increase in "Call Circuit Closed" disconnects - ComOS 3.8

James Dutton (James@superbug.demon.co.uk)
Tue, 24 Nov 1998 11:49:57 +0000

Hello Mike
Here is a decode of the interesting bits of your output.

#First command sent to PM3 from remote switch Requesting Disconnect
#of the ISDN channel which the modem call was on.
D0:recv COMMAND SAPI=00, TEI=00, Info: N(S)=23, N(R)=01, Poll=0
Q.931 CRV=(From Origin)30DE Message=45-DISCONNECT
08-CAUSE 90-16:Normal call clearing

#Here the PM3 is decoding a bit. By saying it received a Disconnect
request. (set debug isdn on)
Skipping: S14: Received Disconnect Normal Clearing (B1 ID:5e5b)
Skipping: S14: Sending Disconnect Request

#The PM3 now allows the disconnect.
Echoing : D0: send 00 01 02 48 08 02 84 de 4d
D0:send COMMAND SAPI=00, TEI=00, Info: N(S)=01, N(R)=24, Poll=0
Q.931 CRV=(To Origin)30DE Message=4D-RELEASE

#The remote switch ack's it.
Echoing : D0: recv 02 01 48 04 08 02 04 de 5a
D0:recv COMMAND SAPI=00, TEI=00, Info: N(S)=24, N(R)=02, Poll=0
Q.931 CRV=(From Origin)30DE Message=5A-RELEASE COMPLETE

So although you manually reset the modem. The remote ISDN switch
initiated the disconnect at the ISDN level.
What probably happened is the modems negotiated disconnect. The remote
modem hung up first. This caused an ISDN level Circuit disconnect
request originating from the remote end.
(remote is other end,local is PM3)
So the PM3 is reporting correctly. It would be nicer if the report was a
bit more useful.
E.G. Local LAPM modem disconnect, Call Circuit closed remotely.
Or. Local Administrator reset.
But this will not be a high priority as far as Lucent are concerned,
unless a lot of their customers make it so.
Lucent priorities are Reliability, Stability, Urgent/Significant
Features, Nice features.
This will be in the nice features catagory.

> Where can I find the information to debug the stuff below ?
>
> neon> show m37
> Card Type: Lucent Chipset
> State: ACTIVE
> Active Port: S14
> Transmit Rate: 31200
> Receive Rate: 26400
> Connection Type: LAPM/V42BIS
> Chars Sent: 1041998264
> Chars Received: 107155900
> Retrains: 0
> Renegotiations: 1
>
> Total Calls: 1113
> Modem Detects: 1039
> Good Connects: 1039
> neon> D1: send 00 01 01 17
> D1: recv 00 01 01 ff
> reset mD0: send 00 01 01 47
> D0: recv 00 01 01 03
> 37
> M37: Modem Resetting
> neon> D1: send 00 01 01 17
> D1: recv 00 01 01 ff
> D0: send 00 01 01 47
> D0: recv 00 01 01 03
> D0: recv 02 01 46 02 08 02 04 de 45 08 02 80 90
> D0: send 02 01 01 48
> S14: Received Disconnect Normal Clearing (B1 ID:5e5b)
> S14: Sending Disconnect Request
> D0: send 00 01 02 48 08 02 84 de 4d
> D0: recv 00 01 01 04
> D0: recv 02 01 48 04 08 02 04 de 5a
> D0: send 02 01 01 4a
> S14: Received Clear Conf (B1 ID:5e5b)
> D1: send 00 01 01 17
> D1: recv 00 01 01 ff
> D0: send 00 01 01 4b
> D0: recv 00 01 01 05
> D1: send 00 01 01 17
> D1: recv 00 01 01 ff
>
>
> This resulted in a Call Circut closed...ComOS 3.8 against a DMS100,
> PRI
>
> ---Mike
> Mike Tancsa (mdtancsa@sentex.net)
> Sentex Communications Corp,
> Waterloo, Ontario, Canada
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.
Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>