Major problems with DS1 and new ISDN-PRI T1

[jcloud]

Please keep in mind that I'm new at this, so don't be afraid to point out the obvious.

Us: We're running CM 1.3.1, S8700's, etc. I'm using ASA to access the switch (of course). Don't ask why they granted an idiot like me all the permissions in the world to the switch.

The problem:

We ordered a new ISDN-PRI T1 from the phone company, expecting increased call volume soon. Added a DS1 to the port cabinet and the phone company says we're sending them a "yellow signal from our switch" during their testing. They claim they can't frame our signal (they requested b8zs/esf), though ASA shows the DS1 is setup as following:

Page 1 of 2
DS1 CIRCUIT PACK
Location: 05A13 Name: name
Bit Rate: 1.544 Line Coding: b8zs
Line Compensation: 1 Framing Mode: esf
Signaling Mode: isdn-pri
Connect: network
TN-C7 Long Timers? n Country Protocol: 1
Interworking Message: PROGress Protocol Version: a
Interface Companding: mulaw CRC? n
Idle Code: 11111111
DCP/Analog Bearer Capability: 3.1kHz
Slip Detection? n Near-end CSU Type: integrated
Echo Cancellation? n

All of our other (working) DS1's are setup the same way.

The status lights on the front of the board: blank, red, blank, red.

I added the DS1 (05a03), created a signalling group (9 - uses 05a1324 for D channel), and added them to an existing trunk (7).

Status Trunk 7 gives me "out-of-service-NE" on all the new ports I added.

Status sign group 9 gives me:
status signaling-group 9
STATUS SIGNALING GROUP
Group ID: 9 Active NCA-TSC Count: 0
Group Type: isdn-pri Active CA-TSC Count: 0
Signaling Type: facility associated signaling
Group State: out-of-service
Primary D-Channel
Port: 05A1324 Level 3 State: out-of-service
Secondary D-Channel
Port: Level 3 State: no-link

Will sign group 9 become "active" when the phone company "flips the switch?"

Please help. Avaya wants minimum $2k for rescue-me/expedited services. Plus, I just feel plain dumb.

TIA - Jacob

 

[jcloud]

PS: We've swapped out DS1 cards (464GP HW06 FW017, even tried going back to FW013 - our other (working) DS1's are still at FW008), CSU's (Avaya 120A4), cables (we're using "normal" cat 5 stuff...not shielded T1 specific...were told it should still work)...w/ loopback jack and w/o...no difference (were told it'd be fine w/o a loopback jack).

 

[schned99]

I hate to point out the obvious, but you are in trouble. Unless you have MSPs (Maintenance Service Permissions), you will not have a high enough level login to even do the basic troubleshooting required to figure out the problem.

On a basic level, check ang make sure your cable is plugged in the port labeled "network" on the 120A4 and not "alarm".

There is a whole list of tests that I run to prove out the equipment so I can point to the network side as the problem.

You might have to bite the bullet and pay Avaya, or try and call a business partner and see if they will respond at a lower cost. I wish you luck.

Statements expressed in this post are my own opinions and should not be considered as the opinion of my employer.

 

[jcloud]

I do have a lot of permissions, actually. Enough to get me in trouble.

Removed the loopback jack and reprogrammed everything from the start, and am no longer getting errors when running a test on board 05a03! Was previously getting a fail on test 140. Miraculously, my red lights have gone off as well...the status lights are now blank, blank, green, blank.

Still showing out-of-service-NE, though. :-/

Complete Noob. I'm trying!

 

[mikeydidit]

If you are assigning these to a group that already exsist, then you would not need the D-Signaling (Unless you are addind a secondary D-Signaling channel). You would just add the new members into your group and life is good. If you are setting up a new group, then of course you would need D-Signaling. Below is my signaling group 1. It is setup with a primary and secondary d signaling channel.

display signaling-group 1 Page 1 of 5 SPE B
SIGNALING GROUP

Group Number: 1 Group Type: isdn-pri
Associated Signaling? n Max number of NCA TSC: 0
Primary D-Channel: 01D2024 Max number of CA TSC: 0
Secondary D-Channel: 04D2024 Trunk Group for NCA TSC:
Trunk Group for Channel Selection: 5 X-Mobility/Wireless Type: NONE
Supplementary Service Protocol: a

Trunk Brd Interface ID Trunk Brd Interface ID
1: 02D15 2 11:
2: 02D04 3 12:
3: 02D05 4 13:
4: 02D16 5 14:
5: 04D17 7 15:
6: 01C20 6 16:
7: 01D20 0 17:
8: 04D20 1 18:
9: 03C09 8 19:

If you are just adding to a group then change your siganling group asigned to your trunk group and add the new DS1 to it. Add all 24 trunks and a way you go...

Mike Jones
Louisiana State University Health Sciences center

 

[nohuhu]

jcloud,

basically yellow alarm means that remote side has an out-of-frame condition. in your case, it means that YOUR side has an out-of-frame condition. being in your place, i'd first did a 'test board 05a13' and then proceeded according to repair procedure described in maintenance document for your server.
p.s. also the second thing to check (and it often comes from the first) is the mdf connection for this circuit pack and csu condition.

 

[bhanson184]

If this is being added to an existing trunk-group shouldn't your DS1 be programmed as isdn-ext. You do have to add it to a signalling group. The other thing your transmit and receive maybe reversed.
The first thing I like to try is loop back your circuit to the NIU and do a "test bo xxxxx long". After the actually board test cancel out. If every test passes your internal equipment is okay. Then you go back toward your provider and loop the circuit back to them and make curtain they see your loop back.

hope this helps

BHanson

 

[EchoSpark]

Hi,

1. Ensure that there is a signal on the transmit pair of the far-end cable, this can be tested by using an Led, which lights up when there is a signal on the Tx pair.
2. Ensure that the far end configuration is matched with the PBX, particularly:
a. Signal mode
b. Line coding
c. Cyclic redundancy check
d. DCP/Bearer capability
e. Interface companding

3. Ensure that the Tx and Rx pair from the far-end switch cross to the Rx and Tx pair of the PBX.