sundance-communications.com/forum Forums TDM Business Telephone Systems Mitel Telephones & Systems Indeterminate and Not Seizable

Didn't quite make it through the weekend, alarms are back. Alarm stats from the CSU:

NI
LOS-Inactive
AIS-Active
Out Of Frame - Active
Yellow - Inact
Red - Active
Code Violations - Inact
BPV - Inact
Frame Bit Errors - Inact

T1
LOS-Inactive
AIS-Inact
Out Of Frame - Inact
Yellow - Active
Red - Inact
Code Violations - Inact
BPV - Inact
Frame Bit Errors - Inact

My suggestions for B8ZS zero code suppression - YES is based upon all MSDN links on my network - which are on D4/AMI circuits.

From Mitel docs:
Zero Code Suppression is a method of reducing timing errors by suppressing all-zero codes and replacing them with another bit pattern. Both ends of the link must specify the same type of zero code suppression. Default value is "Yes"

thanks becca1jane - would you mind sending me what the entire config for the link descrips are for your set-up? thanks,

becca1jane is correct, and as she pointed out earlier both sides must be set to YES. What did the Mitel logs and DT read show? What model CSU are you using?

I was able to find some MSDN links on our network that were set to B8ZS zero code suppression - NO on both sides. Otherwise all descriptors are similar other than opposites ends of each link being set to A/B for message control.


──────────────────────────────────────────────────────────── ───────────────────│
│ LINK DESCRIPTOR ASSIGNMENT │
│ │
│Digital Link Descriptor Number: 1 │
│ │
Description │ Value │
┌─────────────────────────────────────────────────────────── ┌──────────────────│
│Address for Message Control (A/B). . . . . . . . . . . . . B │
│BER - Maintenance Limit, 10**-n, n=(3,4,5,6) . . . . . . . 4 │
│BER - Service Limit, 10**-n, n=(3,4,5,6) . . . . . . . . . 3 │
│Data Call Alternate Digit Inversion (Yes/No) . . . . . . . Yes │
│Framing Losses in 24 hrs - Maintenance Limit (0-9000). . . 255 │
│Framing Losses in 24 hrs - Service Limit (0-9000). . . . . 9000 │
│Integrated Digital Access . . . . . . . . . . . . . . . . DPNSS │
│QSIG Private Network Access (Yes/No) . . . . . . . . . . . No │
│Vendor Inter-working Type . . . . . . . . . . . . . . . . . │
│Satellite Link Delay (Yes/No). . . . . . . . . . . . . . . No │
│Slip Rate - Maintenance Limit (0-9000) . . . . . . . . . . 255 │
│Slip Rate - Service Limit (0-9000) . . . . . . . . . . . . 7000 │
│Termination Mode (NT/LT). . . . . . . . . . . . . . . . . . │
│Send Malicious Call Indication to PSTN For Tagged Calls . . No │
│ │
│ DS1 Parameters: │
│Alarm Debounce Timer - Service Limit (300-3200). . . . . . 500 │
│B8ZS Zero Code Suppression - (Yes/No). . . . . . . . . . . Yes │
│ │
│ Universal T1 and Enhanced Dual T1 Card only: │
│Operation Mode (CSU/DSX-1) . . . . . . . . . . . . . . . . │
│CSU Tx Line Build-Out(0,7.5,15,22.5 db). . . . . . . . . . │
│DSX-1 line Length(0-133,134-266,267-399,400-533,534-655 ft) │
│Extended Super Frame (Yes/No). . . . . . . . . . . . . . . No │
│Inverted D channel ( DPNSS only ) (Yes/No) . . . . . . . . No │
│ │
│ Universal E1 and Enhanced Dual E1 only: │
│Operation Mode (CSU/DSX-1) . . . . . . . . . . . . . . . . │
│CSU Tx Line Build-Out(0,7.5,15,22.5 db). . . . . . . . . . │
│DSX-1 line Length(0-133,134-266,267-399,400-533,534-655 ft) │
│Extended Super Frame (Yes/No). . . . . . . . . . . . . . . No │
│Inverted D channel ( DPNSS only ) (Yes/No) . . . . . . . . No │
│ │
│ Universal E1 and Enhanced Dual E1 only: │
│CRC-4 enabled(Yes,No). . . . . . . . . . . . . . . . . . . No │
│E1 line Length(0-133,134-266,267-399,400-533,534-655 ft) . │
│E1 Impedance (75,120 ohms) . . . . . . . . . . . . . . . . │
│ │
│ Italian Parameters: │
│Digital Link Fault Delay Timer (0-360 sec) . . . . . . . . 240 │
│ │
│ Universal T1/E1 Coding Conversion Parameters: │
│Voice conversion (Nil/ADI/Invert/Inverted ADI). . . . . . . Nil │
│Data conversion (Nil/ADI/Invert/Inverted ADI). . . . . . . Nil │

jimmy - maint logs and dtstats are a few posts above. beccaj - thanks, that is exactally how I"m set up.... model is Adtran ESF csu dsu.

You mentioned you are clocking to the CO PRIs at each location - if you do a dt r on the PRIs are you seeing any errors at the time of the activity switch? Hope this doesn't sound stupid, but are both PBX's in the same timezone, or atleast in different timezones so that 1:15 on one PBX is not equal to 2:15 on the other? And is the time set correctly on each?

pri circuits are clean.
machines are in the time zone (across the street) and their time is synched.

What is the possibility of putting your own cable across the street, at least temporarily? Eliminate every bit of possible telco as a trouble source. I've done this twice, with P-P T1, and the problems ALL dissappeared! And companies were so happy with low cost, they put in a permanent link. Remember, arial may not be possible, but boring under the street probably is! Just make sure whoever does the job is bonded AND INSURED! John C. (Not Garand)

Your last CSU alarm post would indicate the problem is with your carrier. The 2000 on shows a Yellow alarm. You could double check with one of the guru’s in the T1 forum.

NI
AIS-Active
Out Of Frame - Active
Red - Active

T1
Yellow - Active


Network Interface Alarms

AIS Alarm Unframed all-ones received at NI
Out of Frame No framing pattern sync at NI
Red Alarm LOS (loss of signal)/out of frame (OOF) causing red alarm at NI


T1 terminal Interface Alarms

Yellow Alarm Receiving yellow alarm pattern from T1