ISDN-PRI trunk problem 2

[nord860]

I've been trying to get a new ISDN-PRI trunk working for quite some time now . Working with CLEC and Avaya Tier 2.
BerkTester takes test calls on the PBX side of the CSU - Adtran 120e, and have checked the config many times.

Here's what I have: Software Load: R011i.02.0.110.4 Memory Configuration: G3siV11, Offer Category: B
DS1 card TN2464BP HW02 FW018

I've tried changing every setting I can think of.

Has anyone had problems with these software and hardware loads?

Here are most of the setting I've played with.

Line Coding: b8zs
Framing Mode: esf
Signaling Mode: isdn-pri
Country Protocol: 1
Protocol Version: a
Near-end CSU Type: other

SIGNALING GROUP
Group Type: isdn-pri
Associated Signaling? y
Primary D-Channel: 1B1524
Trunk Group for Channel Selection: 12
Supplementary Service Protocol: a

TRUNK GROUP
Group Type: isdn
Direction: two-way
Carrier Medium: PRI/BRI
Dial Access? n
Service Type: cbc

TRUNK PARAMETERS
Codeset to Send Display: 6
Codeset to Send National IEs: 6
Supplementary Service Protocol: a
Digit Handling (in/out): enbloc/enbloc
Digital Loss Group: 13
Synchronization: async
Duplex: full
Disconnect Supervision - In? y Out? y
Answer Supervision Timeout: 0

TRUNK FEATURES
ACA Assignment? n
Wideband Support? n
Data Restriction? n
Used for DCS? n
Suppress # Outpulsing? n
Outgoing Channel ID Encoding: preferred UUI IE Treatment: service-provider
Ds1 Echo Cancellation? n

Thanks in advance for any suggestions!

 

[irisngen]

What test is the board failing? when you status the trunk, what state are the ports in? it could be a protocol change needed.

 

[nord860]

I've removed all translations at this time so I don't have the tests, but the board state was out-of-service NE - planning on moving the board to the A carrier - We have switched between a and b protocol with no luck.

 

[irisngen]

Any screen shots you can send us would be very helpfull.

 

[4merAvaya]

Protocol a = AT&T Custom (4ESS)
Protocol b = NI2 (5ESS/DMS 100)
Protocol c = DMS 250

Try doing 'test board [slot]'. Tests 138 & 139 are for the basic transport.

Kevin

 

[nord860]

Prior to today we moved the card to a different slot in the same carrier e.g 1b12 to 1b15 which did not help - I just moved it to carrier a and the circuit came up. I think we have a problem with PKT-BUS.

 

[irisngen]

Then you should have alarms in the log that have to do with the PKT-BUS.

 

[bhanson184]

Did you build a signal group?
Add signal-group 1:

SIGNALING GROUP

Group Number: 1 Group Type: isdn-pri
Associated Signaling? n Max number of NCA TSC: 0
Primary D-Channel: 02B1924 Max number of CA TSC: 0
Secondary D-Channel: 02C2024 Trunk Group for NCA TSC:
Trunk Group for Channel Selection:
Supplementary Service Protocol: a Network Call Transfer? n

Trunk Brd Interface ID Trunk Brd Interface ID
1: 02B19 0 11:
2: 02C20 1 12:

Good luck

 

[nord860]

We had a PKT-BUS alarm about a week after installing the trunk. Avaya dispatched and cleared the alarm (no hardware replaced) however that did not fix the problem. I moved the board to the primary carrier today and the circuit works, but it looks like there's still a problem with the PKT-BUS eventhough it's not in alarm. I'll re-open the ticket with Avaya.

Thanks everyone for your input!!

 

[irisngen]

Update us, i would like to know what they find on the bus.

 

[nord860]

Still working on this, D-Channel goes in and out of service - Avaya replaced the processor, didn't help. Telco redesigned the circuit to be on a 5ESS, didn't help. We're checking all hardware from the NIU for the fourth time. New DS1 card, Different slot, New CSU, New DS1 cables.

 

[nord860]

Problem was a bad CSU, but we still can't get it to work anywhere other than the A carrier.