PRI Help

[FortKnox]

I just tried to turn up a PRI.

Qwest says they arent seeing anything on the D-channel.

I configured the ds1, the signaling group, and the trunk group identical as the other one that I have with them, using the corresponding d-channel of course.

On my end, I have out-of-service-NE, I supposed meaning 'near-end.'

At first I used a csu that goes on the back, then I used on of my old Acculink 3150's, on the Acculink its green all the way.

What else can I check?

BTW, on the csu that goes on the back of the cp, I used a straight through cable, it tests out fine.

 

[bwilch]

Are they able to loop the smartjack? Are they able to loop your CSU?

 

[dimas]

First: make test board xxx of your PRI and look for results of tests 138...146.

 

[mikeydidit]

Did you fix this CaNiBuS. If not post and I will see if I can help.


Mike Jones
Louisiana State University Health Sciences center

 

[FortKnox]

Thanks Mike. Its more difficult now b/c I am remote; I was at the location in TN, but I am now in Baton Rouge working at my new full-time job.

When I ordered the PRI from Qwest I told them to set it up identical to the other PRI that I have. The have compared and they say they have. I on the other hand have printed the new signalling group, the DS1, and the trunk group and compared and they are the same.

Qwest asked if I had my end set to 'network' when I looked its set to 'public-network' When I go to change it to anything else, my Definity throws up a nasty warning saying that it can cause 'corruption' and am I sure I want to do that. So I left it at 'public-network.'

Qwest can loop the smart jack. Qwest can loop the CSU.

How can I loop the CSU from the Definity? Is there a way? I have tested the board yet. Will do that tonight when I get off work.

Thanks,

-CaN

 

[FortKnox]

Here is what I have:

display ds1 01c04
DS1 CIRCUIT PACK
[PAGE_1]
Location: 01C04
Name: QWEST PRI CORP
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: speech
Slip Detection? y
Near-end CSU Type: other
[PAGE2]
ESF DATA LINK OPTIONS
Network Management Protocol: tabs
Send ANSI-T1.403 One-Second Performance Reports? n
Far-end CSU Address: b


display signaling-group 3
[PAGE_1]
SIGNALING GROUP
Group Number: 3 Group Type: isdn-pri
Associated Signaling? y Max number of NCA TSC: 0
Primary D-Channel: 01C0424 Max number of CA TSC: 0
Trunk Group for NCA TSC:
Trunk Group for Channel Selection: X-Mobility/Wireless Type: NONE
Supplementary Service Protocol: a



display trunk-group 16
[PAGE_1]
Group Number: 16 Group Type: isdn CDR Reports: y
Group Name: QWEST ISDN/PRI CORPORATE COR: 59 TN: 1 TAC: 116
Direction: two-way Outgoing Display? n Carrier Medium: PRI/BRI
Dial Access? n Busy Threshold: 22 Night Service:
Queue Length: 0
Service Type: public-ntwrk Auth Code? n TestCall ITC: rest
Far End Test Line No:
TestCall BCC: 4
TRUNK PARAMETERS
Codeset to Send Display: 6 Codeset to Send National IEs: 6
Max Message Size to Send: 260 Charge Advice: none
Supplementary Service Protocol: a Digit Handling (in/out): enbloc/enbloc

Trunk Hunt: cyclical
Digital Loss Group: 13
Calling Number - Delete: Insert: Numbering Format:
Bit Rate: 1200 Synchronization: async Duplex: full
Disconnect Supervision - In? y Out? n
Answer Supervision Timeout: 0

[PAGE_2]
TRUNK FEATURES
ACA Assignment? n Measured: none Wideband Support? n
Maintenance Tests? y
Data Restriction? n NCA-TSC Trunk Member:
Send Name: n Send Calling Number: n
Used for DCS? n
Suppress # Outpulsing? n Numbering Format: public
Outgoing Channel ID Encoding: preferred UUI IE Treatment: service-provider

Replace Restricted Numbers? n
Replace Unavailable Numbers? n
Send Connected Number: y

Send UUI IE? y
Send UCID? n
Send Codeset 6/7 LAI IE? y Ds1 Echo Cancellation? y

US NI Delayed Calling Name Update? n

SBS? n Network (Japan) Needs Connect Before Disconnect? n

[PAGE_4]
Port Code Sfx Name Night Sig Grp
1: 01C0401 TN464 F CHANNEL 1 3
2: 01C0402 TN464 F CHANNEL 2 3
3-23 etc.....


Does the service type need to be something else? Would that prevent the D-channel from coming up?

 

[dimas]

Do test board .
If you execute test, that possible loop will not to be necessary.
if Test 138 - Fail (bad wiring or swaped TRANSMIT/RCV)
if Test 138 - PASS (good wiring)
if Test 139 - Fail (Yellow alarm from remote end)
if Test 140 - Fail (No frame syncronization, may be no identical settings of framing mode from both ends or at the CSUs, if CSUs have switches)
if Test 141 - Fail (Out-of-Frame from remote end)
...

Show results here - will see.

 

[mikeydidit]

Do a "sta sig 3" and see what state the primary D-Signaling channel shows to be in. It should be (in-service)I also see that you have 2 464 packs in this group. Make sure the second one is programmed as pri-ext so you can assign all 24 b channels to your group. "ch ds1 01c0402". I would also put the new CSU 120A on and use it. Let us know how this turns out.

Mike Jones
Louisiana State University Health Sciences center

 

[FortKnox]

My first PRI from Qwest I turned up about 2 years ago. This is an additional PRI that will be partitioned off so that only one department uses it.

Are you saying that on this new PRI I should set it to pri-ext and its d-channel should use the d-channel of the other pri?

 

[schned99]

You should only set it up as pri-ext if you ordered the circuit as NFAS (Non Facailty Associated Signalling) 24b channels and the b-channels are all part of the same CLEC hunt group as the first circuit and they use the d-channel of the first circuit.

It sounds like that is not the case and you ordered it FAS (Fsacility Associated Signalling) 23b+d channel. In which case, you set it up correctly. It's too bad you are not on site.

Like dimas said, you need to run a test board 01C04. If any of the tests fail, run loop-back to the PBX and they should all pass. If they don't, replace the cable, if they still fail, replace the DS1. If they all pass, the problem is somewhere between Qwest and your smart jack. I have seen issues like this caused by there being a loop-back left up at one of the COs between the smart jack and the CLEC or a card optioned incorrectly between the CLEC and the smart jack (usually a card left at d4 ami when it should have been changed to b8zs esf) both are issues that can only be fixed between Qwest and the LEC that owns the infrastructure (Verizon, Bell South, Pac Bell, etc)

 

[mikeydidit]

You would only program the second PRI (01c0402) as FAS or ISDN-PRI in the DS1 form if you were using this as a secondary D-Signaling channel. Looking at the signaling group (3) their is only one D channel. Then the second would need to be set up as (01c0402) a PRI-EXT (NFAS)in the switch or it will only allow you to assign 23 b's.

Basically the first DS1 will do the signaling for the first 23 trunks and the rest of the group.

I pulled up my primary D channel and it is set to "Network" but I would see how your other group is setup and program it the same.



Mike Jones
Louisiana State University Health Sciences center

 

[schned99]

It looks like CaNiBuS ordered this to be a stand alone circuit for another department to use, identical to the existing circuit from 2 years ago. If this is the case, and the trunks are going to be in seperate trunk groups on the PBX, then it should be FAS with seperate signalling groups and d-channels, not NFAS with a primary and secondary d-channel in one signalling group.

The only reason he would change the existing signaling group and add 01C0424 as the secondary d-channel is if he ordered the circuit that way and will have all 46 b-channels in the same trunk group in his switch and the same hunt group on the CLEC switch.

Without being on site and running tests, from a lot of experience turning up T1s all over the country, baring hardware failure, I'd say it's either a protocol mismatch (you are set up for protocol a which is AT&T custom), the smart jack or one of the cards in an intermediate CO optioned incorrectly, or a loop-back up somewhere in the cicuit.

 

[mikeydidit]

schned99, I am like you and think either a software loop or other problem in the circuit or mismatch with the protocol will end up being the problem. I am not sure why his switch would give him the software corruption warning when setting his primary DS1 to "network". (disp DS1 04c0401)

Both of my PRI groups are set to "network" but I guess that is an option that varies from carrier.

Thanks for your time and trying to help him.

Mike Jones
Louisiana State University Health Sciences center

 

[schned99]

Any time you have a signal group and b-channels administered on a DS1 board, the PBX will give you that warning if you try to make a change to the DS1. The way to avoid that is to remove all the b-channels from the trunk group and remove the signal group entirely.

 

[FortKnox]

Well, guess what? And this isnt the first time this has ever happened....

I havent touched this switch since lastnight, this morning I status-ed signal group 3 and it was still out of service.

I just checked it and now its in-service.

Someone at Qwest or somewhere in between tweaked something somewhere.

 

[mikeydidit]

Imagine that.... A circuit that no one has touched and yet it just popped up.

Yeah I have never seen that happen either.... LOL

Glad you got it going.

Mike Jones
Louisiana State University Health Sciences center

 

[schned99]

It's magic.