Where in books? DCH: 2 MAINT INDICATION TIME: 15:36:14 3

[GHTROUT]

I've never been that much concerned about looking this type of DCH message up until now. I can't find any reference to it in the books though. Is it documented? Where?

[tt]
% DCH: 2 MAINT INDICATION TIME: 15:36:14
% COUNTER VALUE
% 2 2
% 3 255
% 10 1
% 18 1
[/tt]

What I do know is: It is related to DCH 2; The far end of this circuit is getting a different message, like this:

[tt]
% MSDL0304 GROUP 3 MSDL 10 (8) 1685
% MSDL0304 GROUP 3 MSDL 10 (8) 1694
% MSDL0304 GROUP 3 MSDL 10 (8) 1725
% MSDL0304 GROUP 3 MSDL 10 (8) 1718

and lots of them
[/tt]

The above error specifically points to the related DCH on the far end.


~~~
[small]GHTROUT.com | Get the Input/Output Manuals | Tek-Tips FAQs | Recent Replies[/small]

 

[bigindian65]

I was always told those were strictly informational and not errors, is this incorrect?


Mato' Was'aka

 

[GHTROUT]

I believe they indicate errors. They are clearly counter values - but of _what_ counters?




~~~
[small]GHTROUT.com | Get the Input/Output Manuals | Tek-Tips FAQs | Recent Replies[/small]

 

[GHTROUT]

I found it! Look in LD96 in the Prompts and Possible Responses under "PLOG DCH x"

It lists each counters number - there are just over 50 counter types.


~~~
[small]GHTROUT.com | Get the Input/Output Manuals | Tek-Tips FAQs | Recent Replies[/small]

 

[bigindian65]

Seem pretty excited there Gene! *


Mato' Was'aka

 

[GHTROUT]

Oh, I'm pumped - because my "Count of unsuccessful retransmit N200 of SABME" is so high.

I'm beaming because of that.

What is "retransmit N200 of SABME"


~~~
[small]GHTROUT.com | Get the Input/Output Manuals | Tek-Tips FAQs | Recent Replies[/small]

 

[yyrkroon]

Set Asynchronous Balanced Mode (SABME)

call control, used to initiate setup between slave (you) and network (farend/telco)

that's all remember, before i fell into a deep, deep slumber, i'm sure there's more to it, don't have the notes in front of me.

 

[Phnman]

I've seen this error before and a previous post suggested it may be a protocol mismatch in your D ch config. I was able to clear mine by
correcting a Rls ID mismatch. Was 22 should have been 21.