atcomsystems.ca/forum Forums TDM Business Telephone Systems Mitel Telephones & Systems Indeterminate and Not Seizable

I have a pair of point-to-point DS1s between two SX2000s that fail every night after active plane switch. Circuits work well otherwise, but require reset each morning. Another pair of P2Ps (between a 2k and a 3300) do not have this problem. Can anyone clarify the indeterminate message when doing a 'status'? Also looking for guidelines on trunk-service and digital link descriptors for msdn configurations. Thanks,

Indeterminate means there has been no activity on the circuit since the reboot/activity switch. Can you give a little more detail as to why your circuit is failing and has to be reset every night?

(Thanks for asking) They seem to be failing each morning at the Activity Switch. I set the far-end to Act Sw an hour earlier than the near-end, no effect. Sometimes reseting the CSU will bring them back, other times the entire card needs to be loaded (bus/rts doesn't do it). DTSTATS doesn't show many/any slips or bpvs.

As Alex said, Indeterminate means it has not been used yet. If you want to change it to idle, test the plid. Are there any maintenance logs?

Maintenance logs were showing a loss of sync. We found a possible mismatch in coding (formatter 1 cards only support ami/d4, right?). What functionality is lost with incorrect Inverted D channel setting in a P2P DPNSS environment? Thanks,

If it is only happening at activity switch, do you have a network sync set on both sides? I'll pull up the tech docs about the formatter 1 card later. The Inverted D channel should be set to yes.

Yes, both ends are sync'd, no problems there. The carrier is esf/b8zs and we're using the adtrans to convert to ami/d4 to the pbx. Also considering the use of Formatter II cards so we can have esf/b8zs all the way through.

OK - lets slow this down for the dumb guy ( me ) when you get into the office in the morning can you call across this circuit?

And what happens when you make a call across the circuit, whats on the display and what shows up in the logs after the call is made?

Are your controllers redundant on both PBX's ?

I am under the impression your circuit is not going down after the activity switch.

Trunk status is "Not Seizable". Call reroutes to 2nd choice (another formatter I card connected to a 3300 LX acting as a gateway across a 3gb link - no problems there). Yes, both 2k controllers are redundant. Circuit remains error-free (checking dts on regular basis) until the activity switch. Far-end activity switch occurs at 0115, near end at 0215. CSU reports frame-slips toward the CPE side, clear to the network.

What do the logs show on both switches and what time does the span go down? We need to see if it is the near side, far side or both activity switches. You may want to set the activity switch on both to Monday morning only for a while and see if it still happens without the switch.

I've already done the activity switch disable on all 3 sx2k systems to isolate which one is 'hosting' the problem. I've separated switchover time-frames by an hour between sites. When I come in each a.m., the faulty circuit shows frame slips toward the CPE. I can clear the problem by either reseting the CSU (Adtran) or loading the formatter I card. I've swapped formatter I with known good and rolled the CSUs.

I've attached the maintenance log showing entries from activity switch start to end, plus the scheduled DBMS check several hours later (this is a typical log from each day at the same time):

2007-OCT-17 05:06:19 MAINTENANCE B/Active *Major* PBX0101 #0052
DBMS info: DBMS CHECK completed.
00 database error(s) detected.
00 form(s) could not be accessed.


2007-OCT-17 02:43:09 MAINTENANCE B/Active *Major* PBX0101 #0051
The PROGRAMMED ACTIVITY SWITCH sequence has COMPLETED.

2007-OCT-17 02:19:26 MAINTENANCE B/Active *Major* PBX0101 #0050
The link from MC215AD Main Controller IIIE at location 01 1 02 Inactive
to MC312AB Peripheral Cont I at location 07 1 16 Active
is now OPEN.

2007-OCT-17 02:19:25 MAINTENANCE B/Active *Major* PBX0101 #0049
The link from MC215AD Main Controller IIIE at location 01 1 02 Inactive
to MC312AB Peripheral Cont I at location 07 1 16 Active
is now in SCANNING mode.

2007-OCT-17 02:17:25 MAINTENANCE B/Active *Major* PBX0101 #0048
MC215AD Main Controller IIIE at location 1 1 2
Tone Detector circuit 2 was returned to service


2007-OCT-17 02:17:24 MAINTENANCE B/Active *Major* PBX0101 #0047
The link from MC215AD Main Controller IIIE at location 01 1 07 Active
to MC215AD Main Controller IIIE at location 01 1 02 Inactive
is now OPEN.

2007-OCT-17 02:17:13 MAINTENANCE B/Active *Major* PBX0101 #0046
MC215AD Main Controller IIIE at location 1 1 2
Conference circuit 3 was returned to service


2007-OCT-17 02:17:03 MAINTENANCE B/Active *Major* PBX0101 #0045
MC215AD Main Controller IIIE at location 1 1 2
Tone Generator circuit 4 was returned to service


2007-OCT-17 02:17:02 MAINTENANCE B/Active *Major* PBX0101 #0044
The link from MC215AD Main Controller IIIE at location 01 1 02 Inactive
to MC312AB Peripheral Cont I at location 07 1 16 Active
is now OPEN.

2007-OCT-17 02:17:02 MAINTENANCE B/Active *Major* PBX0101 #0043
The link from MC215AD Main Controller IIIE at location 01 1 02 Inactive
to MC312AB Peripheral Cont I at location 07 1 16 Active
is now in SCANNING mode.

2007-OCT-17 02:15:55 MAINTENANCE B/Active *Major* PBX0101 #0042
MC270AA Universal T1 at location 02 1 03 02
Type of diagnostics : Background
Scope of report : Hybrid
Reason(s) for report:
- Signalling Medium Present

2007-OCT-17 02:15:55 MAINTENANCE B/Active *Major* PBX0101 #0041
MC270AA Universal T1 at location 02 1 03 01
Type of diagnostics : Background
Scope of report : Hybrid
Reason(s) for report:
- Signalling Medium Present

2007-OCT-17 02:15:45 MAINTENANCE B/Active *Major* PBX0101 #0040
The link from MC215AD Main Controller IIIE at location 01 1 07 Active
to MC215Ax Main Controller IIIE at location 01 1 02 Inactive
is now CLOSED.

2007-OCT-17 02:15:42 MAINTENANCE B/Active *Major* PBX0101 #0039
---------------+--------+-------+-------+-------+---------+---------+----------
|Total In| Unavailable | Alarm Threshold Percentages
Category | System | Total | % | Alarm | MINOR | MAJOR | CRITICAL
---------------+--------+-------+-------+-------+---------+---------+----------
Trunks | 146 | 23 | 15 % | Major | > 0 % | 10 % | 100 % |
Digital Links | 6 | 1 | 16 % | Major | - | > 0 % | - |
---------------+--------+-------+-------+-------+---------+---------+----------


2007-OCT-17 02:15:42 MAINTENANCE B/Active *Major* PBX0101 #0038
------------
Current System Alarm : | MAJOR | viewed from Active
------------


2007-OCT-17 02:15:23 MAINTENANCE B/Active -Info- PBX0101 #0037
MC215AD Main Controller IIIE at location 1 1 7
Tone Detector circuit 2 was returned to service


2007-OCT-17 02:15:20 MAINTENANCE B/Active -Info- PBX0101 #0036
MC263BA DS1 Formatter at location 03 1 05 01
Type of diagnostics : Background
Scope of report : Hybrid
Reason(s) for report:
- Far end alarm : Present

2007-OCT-17 02:15:20 MAINTENANCE B/Active -Info- PBX0101 #0035
MC215AD Main Controller IIIE at location 1 1 2
Tone Detector circuit 2 was returned to service


2007-OCT-17 02:15:20 MAINTENANCE B/Active -Info- PBX0101 #0034
MC312AB Peripheral Cont I at location 8 1 16
DTMF Receiver circuit 7 was returned to service


2007-OCT-17 02:15:20 MAINTENANCE B/Active -Info- PBX0101 #0033
MC312AB Peripheral Cont I at location 8 1 16
DTMF Receiver circuit 1 was returned to service


2007-OCT-17 02:15:20 MAINTENANCE B/Active -Info- PBX0101 #0032
MC312AB Peripheral Cont I at location 5 1 16
DTMF Receiver circuit 7 was returned to service


2007-OCT-17 02:15:20 MAINTENANCE B/Active -Info- PBX0101 #0031
MC312AB Peripheral Cont I at location 5 1 16
DTMF Receiver circuit 1 was returned to service


2007-OCT-17 02:15:16 MAINTENANCE B/Active -Info- PBX0101 #0030
ACTIVITY SWITCH to MC215AD Main Controller IIIE at location 01 1 07
from MC215AD Main Controller IIIE at location 01 1 02
was SUCCESSFUL.
The reason(s) for the switch attempt :
- Programmed Activity Switch

2007-OCT-17 02:15:16 MAINTENANCE B/Active -Info- PBX0101 #0029
MC215AD Main Controller IIIE at location 1 1 2
Conference circuit 3 was returned to service


2007-OCT-17 02:15:16 MAINTENANCE B/Active -Info- PBX0101 #0028
MC215AD Main Controller IIIE at location 1 1 2
Tone Generator circuit 4 was returned to service


2007-OCT-17 02:15:14 MAINTENANCE B/Active -Info- PBX0101 #0027
MC312AB Peripheral Cont I at location 4 1 16
DTMF Receiver circuit 7 was returned to service


2007-OCT-17 02:15:14 MAINTENANCE B/Active -Info- PBX0101 #0026
MC312AB Peripheral Cont I at location 4 1 16
DTMF Receiver circuit 1 was returned to service


2007-OCT-17 02:15:12 MAINTENANCE B/Active -Info- PBX0101 #0025
MC312AB Peripheral Cont I at location 7 1 16
DTMF Receiver circuit 7 was returned to service


2007-OCT-17 02:15:12 MAINTENANCE B/Active -Info- PBX0101 #0024
MC312AB Peripheral Cont I at location 7 1 16
DTMF Receiver circuit 1 was returned to service


2007-OCT-17 02:15:10 MAINTENANCE B/Active -Info- PBX0101 #0023
MC312AB Peripheral Cont I at location 06 1 16 installed

2007-OCT-17 02:15:10 MAINTENANCE B/Active -Info- PBX0101 #0022
MC312Ax Peripheral Cont I at location 06 1 16 removed

2007-OCT-17 02:15:08 MAINTENANCE B/Active -Info- PBX0101 #0021
MC215AD Main Controller IIIE at location 1 1 7
Conference circuit 3 was returned to service


2007-OCT-17 02:15:08 MAINTENANCE B/Active -Info- PBX0101 #0020
MC215AD Main Controller IIIE at location 1 1 7
Tone Generator circuit 4 was returned to service


2007-OCT-17 02:15:08 MAINTENANCE B/Active -Info- PBX0101 #0019
MC312AB Peripheral Cont I at location 6 1 16
DTMF Receiver circuit 7 was returned to service


2007-OCT-17 02:15:08 MAINTENANCE B/Active -Info- PBX0101 #0018
MC312AB Peripheral Cont I at location 6 1 16
DTMF Receiver circuit 1 was returned to service


2007-OCT-17 02:15:07 MAINTENANCE B/Active -Info- PBX0101 #0017
MC215AD Main Controller IIIE at location 1 1 7
Tone Detector circuit 2 was taken out of service
due to loss of sanity

These logs just show the system coming back on line after a reboot, When you come in the morning can you make a call over each one of your tie circuits before you reset anything? does the call fail or are you basing your failure on the "indeterminate " status of the circuit? Have you tried doing a DT Clear (plid) to clear up any alarms?

"the faulty circuit shows frame slips toward the CPE" Where are you getting this info from? what piece of equipment is telling you this?

The 2K will show you a digital link alarm if there is a problem like slips,clocking, carrier failure. and Doing a DT Clear will correct these errors. They are info alarms to let you know something has happened that requries some attention but not usually service effecting.

Let us know

Disregard the "indeterminate" status, the trunks are "not seizable". Calls will not go over the link.

Each morning when I arrive, it's a major alarm, and calls route to 2nd choice.
**********************************************
Current System Alarm : | MAJOR | viewed from Active
------------


---------------+--------+-------+-------+-------+---------+---------+----------
|Total In| Unavailable | Alarm Threshold Percentages
Category | System | Total | % | Alarm | MINOR | MAJOR | CRITICAL
---------------+--------+-------+-------+-------+---------+---------+----------
Trunks | 146 | 23 | 15 % | Major | > 0 % | 10 % | 100 % |
Digital Links | 6 | 1 | 16 % | Major | - | > 0 % | - |
---------------+--------+-------+-------+-------+---------+---------+----------
*************************************

A stat of the affected card:

*************************************
3 1 5 1 1| DS1 Formatter | Not Seizable | | |
3 1 5 1 2| DS1 Formatter | Not Seizable | | |
3 1 5 1 3| DS1 Formatter | Not Seizable | | |
3 1 5 1 4| DS1 Formatter | Not Seizable | | |
3 1 5 1 5| DS1 Formatter | Not Seizable | | |
3 1 5 1 6| DS1 Formatter | Not Seizable | | |
3 1 5 1 7| DS1 Formatter | Not Seizable | | |
3 1 5 1 8| DS1 Formatter | Not Seizable | | |
3 1 5 1 9| DS1 Formatter | Not Seizable | | |
3 1 5 1 10| DS1 Formatter | Not Seizable | | |
3 1 5 1 11| DS1 Formatter | Not Seizable | | |
3 1 5 1 12| DS1 Formatter | Not Seizable | | |
3 1 5 1 13| DS1 Formatter | Not Seizable | | |
3 1 5 1 14| DS1 Formatter | Not Seizable | | |
3 1 5 1 15| DS1 Formatter | Not Seizable | | |
3 1 5 1 16| DS1 Formatter | Not Seizable | | |
3 1 5 1 17| DS1 Formatter | Not Seizable | | |
3 1 5 1 18| DS1 Formatter | Not Seizable | | |
3 1 5 1 19| DS1 Formatter | Not Seizable | | |
3 1 5 1 20| DS1 Formatter | Not Seizable | | |
3 1 5 1 21| DS1 Formatter | Not Seizable | | |
3 1 5 1 22| DS1 Formatter | Not Seizable | | |
3 1 5 1 23| DS1 Formatter | Not Seizable | | |

*********************************
DTS for the last 24 hours:

*********************************
DS1 Formatter 3 1 5 1
Link is not available, receiving lost of multiframe
level max avg mode duty bit
2 re- CRC re- re- con- cycle framing error
Time resets trans error trans trans gestion (%) losses slips rate
-----------------------------------------------------------------------------
6:08 0 0 0 0 0 0 0 0 0 0
6:00 0 0 0 0 0 0 0 0 0 0
5:00 0 0 0 0 0 0 0 0 0 0
4:00 0 0 0 0 0 0 0 0 0 0
3:00 0 0 4 3 3 0 25 5 1 0
2:00 0 0 0 4 2 0 100 0 0 0
1:00 0 0 0 3 2 0 100 0 0 0
0:00 0 0 0 4 2 0 100 0 0 0
23:00 0 0 0 4 3 0 100 0 0 0
22:00 0 0 0 0 0 0 100 0 0 0
21:00 0 0 0 4 3 0 100 0 0 0
20:00 0 0 0 3 3 0 100 0 0 0
19:00 0 0 0 4 2 0 100 0 0 0
18:00 0 0 0 4 2 0 100 0 0 0
17:00 0 0 0 4 2 0 100 0 0 0
16:00 0 0 0 4 2 0 100 0 0 0
15:00 0 0 0 4 2 0 100 0 0 0
14:00 0 0 0 4 2 0 100 0 0 0
13:00 0 0 0 4 2 0 100 0 0 0
12:00 0 0 0 4 2 0 100 0 0 0
11:00 0 0 0 4 2 0 100 0 0 0
10:00 0 0 0 4 2 0 100 0 0 0
9:00 0 0 0 4 2 0 100 0 0 0
8:00 0 0 0 4 2 0 100 0 0 0
7:00 0 0 0 2 1 0 70 0 0 0
-----------------------------------------------------------------------------

The other "frame slips" error is read from the CSU. The external CSU is used to convert AMI/D4 from the PBX to ESF/B8ZS from the carrier.

I'd like to verify the particular settings in the Link Descrip form:

**************************************

│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 │
DS1 Parameters: │
│Alarm Debounce Timer - Service Limit (300-3200). . . . . . 500 │
│B8ZS Zero Code Suppression - (Yes/No). . . . . . . . . . . No │
│ │
│ Universal T1 and Enhanced Dual T1 Card only: │
│Operation Mode (CSU/DSX-1) . . . . . . . . . . . . . . . . CSU │
│CSU Tx Line Build-Out(0,7.5,15,22.5 db). . . . . . . . . . 0 │
│DSX-1 line Length(0-133,134-266,267-399,400-533,534-655 ft) 0-133 │
│Extended Super Frame (Yes/No). . . . . . . . . . . . . . . No │
│Inverted D channel ( DPNSS only ) (Yes/No) . . . . . . . . Yes │
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) . 0-133 │
│E1 Impedance (75,120 ohms) . . . . . . . . . . . . . . . . 120 │
│ │
│ 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 │
***********************************

Thanks again for your input!

Log into maintenance, and issue the command
Back off ds1.
That will turn off the back ground diagnostics for the Ds1 channels.
Check tomorrow morning to see if it's had an effect on your symptons.
Contact us anytime if we can be of any assistance!

2007-OCT-17 02:15:20 MAINTENANCE B/Active -Info- PBX0101 #0036
MC263BA DS1 Formatter at location 03 1 05 01
Type of diagnostics : Background
Scope of report : Hybrid
Reason(s) for report:
- Far end alarm : Present

CSU reports frame-slips toward the CPE side, clear to the network


CSU is reporting Slips, DTS shows 1 at 3:00
What model of Aldtran are you using?
What is your first clock source?

“Far end alarm: Present” indicates CSU / far end setting an alarm…


“Operation Mode (CSU/DSX-1) . . . . . . . . . . . . . . . . CSU”
If you have an external CSU, this should be set to DSX-1

Are there any logs prior to activity switch… inactive plane.

Have you tried another CSU?
Have you tried a new DS1 card or swapping with the one going to the 3300?

If you change to a Formatter II card, you can do away with the external CSU.

"not seizable" is losing channels from the CSU or Carrier, I would follow JimmyV's suggestions of changing or eliminating the CSU and roll formatters to see if problem follows card.

Let us know

wow - great input, thank you.

Yes, I've rolled the CSUs and Formatter I cards, nothing follows the hardware. The errors occur on either of the 2k P2Ps, sometimes random, sometimes both. Never occurs on P2Ps attached to 3300. I've swapped DSU to eliminate backplane & power supply. Clocking is set to c.o. PRIs as 1st choice.

I only like changing one thing at a time, but I'll kill background diags and change DSX/CSU flag to indicate use of external CSUs, will advise tomorrow.

I've also recommended to mgmnt (a while back) that we 'upgrade' to Formatter II cards to eliminate the external CSUs.

Your digital link desc shows address for msg control set to B - have you verified that the other end of the link is set to A?
Also - B8ZS Zero Code Suppression - could be set to yes on both ends.

yes, message control (near end=A far end=B) is set ok for all nodes. Please clarify: you're suggesting B8ZS is set = yes for an AMI/D4 trunk? It's B8ZS/ESF to the carrier (converted at the CSU), but AMI/D4 to the pbx.

All is well this morning - no errors. I'll post again after a few days of running clean. Thanks all for your input.

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