DCH counter 27 number of times owner receiver busy condition was entered 1

[Opie the Phoneman]

Ladies and Gentlemen,

I have a CS1000

VERSION 3621

System type is - Communication Server 1000M MG/CP PIV
CP PIV - Pentium M 1.1 GHz

RELEASE 7
ISSUE 50 Q +
IDLE_SET_DISPLAY NORTEL


I have the occasional, DCH: XX MSG LOG INDICATION TIME: 8:00:00

so I Plog the DCH in LD 96:

DCH: XX MAINT CONFIRM TIME: 11:00:00
COUNTER VALUE
15 1
27 26
53 1

I see that the 27 counter is: 27 number of times owner receiver busy condition was entered .

I have disconnected several sets from this PBX recently. Could invalid routing cause these DCH busy condition? Or is the DCH itself overwhelmed and going busy?

Thanks in Advance,

Opie the phone man

 

[Opie the Phoneman]

I just had another DCH: XX MSG LOG print out:

% DCH: XX MSG LOG INDICATION TIME: 5:00:00
% CC ALERTING : 423
% CC DISCONNECT : 130
% CC CALL PROCEEDING : 520
% CC PROGRESS : 27
% CC REJECT : 2160
% CC RELEASE : 439
% CC SETUP : 49
% CC SETUP ACK : 285
% CC STATUS : 65150
% CC RESTART ACK : 1
% CC SERVICE : 1
% CC SERVICE ACK : 382
% H.1A : 128
% H.1B : 47
% ALERTING : 107
% CALL PROCEEDING : 20
% CONNECT : 285
% CONNECT ACK : 441
% NOTIFY : 43
% PROGRESS : 132
% RELEASE : 439
% RELEASE COMPLETE : 1
% RESTART ACK : 65535
% SERVICE : 108
% SERVICE ACK : 2684
% SETUP ACK : 1
% 2ND T303 TIMEOUT : 65136
% T304 TIMEOUT : 5
%


Notice the Restart Ack closely followed by 2nd T303 timeout and CC status are the three highest counters. Is this normal or should I look for problems with the DCH?

 

[StanleySteamer]

The counters print out automatically when any of them reaches 65535 and then all are set back to zero. It doesn't mean there's a problem.

 

[Opie the Phoneman]

This D-channel was printing out a lot of MSG logs. With a lot of CC Status, restart ACK and 2ND T303 TIMEOUT. I was worried about these restart and timeout occrances.

% DCH: XX MSG LOG INDICATION TIME: 5:00:00
% CC ALERTING : 423
% CC DISCONNECT : 130
% CC CALL PROCEEDING : 520
% CC PROGRESS : 27
% CC REJECT : 2160
% CC RELEASE : 439
% CC SETUP : 49
% CC SETUP ACK : 285
% CC STATUS : 65150
% CC RESTART ACK : 1
% CC SERVICE : 1
% CC SERVICE ACK : 382
% H.1A : 128
% H.1B : 47
% ALERTING : 107
% CALL PROCEEDING : 20
% CONNECT : 285
% CONNECT ACK : 441
% NOTIFY : 43
% PROGRESS : 132
% RELEASE : 439
% RELEASE COMPLETE : 1
% RESTART ACK : 65535
% SERVICE : 108
% SERVICE ACK : 2684
% SETUP ACK : 1
% 2ND T303 TIMEOUT : 65136
% T304 TIMEOUT : 5

When I monitored the D-channel I would notice 23 out of service and No channel cause #34 messages.

DCH XX UIPE_IMSG CC_SERVICE_IND REF 00000000 TOD 11:00:00 CK EB026357
STATUS: OUT OF SERVICE

DCH XX UIPE_OMSG CC_STATUS_REQ REF 00000000 CH 0 TOD 11:00:01 CK EB026357
CAUSE: #34 - NO CHANNEL/CIRC AVAIL
STATE:NULL

I checked my route that used this PRI:

>ld 21

REQ: ltm
CUST 0
ROUT x

TYPE TLST
TKTP DID
ROUT x
DES TW_LOCAL
TN xxx 01 MBER 1 TW_LOCAL
TN xxx 02 MBER 2 TW_LOCAL
I went to ld 60 and checked all of the PRI's associated with this route. I found the last PRI (there are 382 members in this route) uneq. I restored that PRI and the messages have stopped. I will see if this reduces the timeout and reset ACK messages as well.