Dcahnnel monitoring 3

[pigsooie]

I have a option 81 and an option 11 linked with a T1 while doing D channel monitoring I see this error coming up SWED EQIP CONGESTION. Anyone know what this means?
DCH 3 IMSG SETUP REF 8017 CH 1 23 TOD 7:48:22
PROGRESS: ORIG ADDR IS NOT ISDN
CALLING #:74306 NUM PLAN: PRIVATE
CALLED #:10578998 NUM PLAN: PRIVATE

DCH 3 OMSG SETUP REF 0016 CH 1 22 TOD 7:48:22
PROGRESS: ORIG ADDR IS NOT ISDN
CALLING #:74306 NUM PLAN: PRIVATE
CALLED #:105 NUM PLAN: PRIVATE

DCH 3 OMSG CALLPROC REF 8017 CH 1 23 TOD 7:48:22

DCH 3 IMSG REL COMP REF 0016 CH 1 22 TOD 7:48:22
CAUSE :SWED EQIP CONGESTION
DIAG: 161

DCH 3 OMSG DISC REF 8017 CH 1 23 TOD 7:48:22
CAUSE :SWED EQIP CONGESTION

DCH 3 IMSG RELEASE REF 8017 CH 1 23 TOD 7:48:22

DCH 3 OMSG REL COMP REF 8017 CH 1 23 TOD 7:48:22


Thanks for the help Mike Patti

 

[galifax]

Hi, I thing you problem is:
"Cause #42 "switching equipment congestion"
This cause indicates that the switching equipment generating this cause is experiencing a period of high traffic

 

[Avaya911PLM]

Congestion may not always mean high traffic. It means it has no routes available for YOUR call. This may actually be a class of service or FRL issue that is blocking your from continuing. Does this happen on all calls?

--
Fletch
Visit the Nortel Technical Support Portal at:

http://www.nortelnetworks.com/support

 

[johnpoole]

i have seen that prob when someone had to much on one msdl card, if your using that card for mail and 2 or 3 dch's move some of the trraffic off of it.. you can enl msgi/o x to mon a dch, but do not turn that on during heavy traffic.. it a load 96 command. and gives you a page of trash per call set up and tear down.. best to turn it on on just one direction when you are under very light traffic..

john poole
bellsouth business
columbia,sc

 

[Avaya911PLM]

By looking at the message:

PROGRESS: ORIG ADDR IS NOT ISDN
CALLING #:74306 NUM PLAN: PRIVATE
CALLED #:10578998 NUM PLAN: PRIVATE

It appears that you are using ESN based signaling on the outboud RDB. This is evident by the 10578998 as the dialed number. the '105' means the station is NCOS 5.

If the recieving RDB is set for STD signalling, the destination PBX is being confused by the 105. If the destination is also set for ESN siganlling, then check the destination NCTL table in LD 87 to see what NCOS 5 has for an FRL mapping. This could be where the failure is. Looking at the messaging it does not appear to be an overloaded MSDL. If this was the case, then messages would be dropped causing the failure.



--
Fletch
Visit the Nortel Technical Support Portal at:

http://www.nortelnetworks.com/support