PRI, one last try

[msteeler]

Hello,

So I'm about ready to give up on this PRI thing, but I'll run it by the the ones who know more than I about PRI.

I have 2 PRI's both with their own primary D, Telco says they are set the same. NI2 and they have a 5ESS switch, I'm set as NI2 and ATT to match them.

Here's the problems I'm having.

1) I can FDL to one DCH but not the 2nd DCH (FDL not Allowed) Is that normal?
2) I'll unplug from the Smart jack to test recovery of the PRI's. Takes about 5 minutes and they come up. As soon as I call out (working bottom to top calling out) all my channels on Loop 25 lockout and the call goes out Loop 24, channel 23. Telco or PBX issue?
3) wait another 5 minutes, locked channels on Loop 25 become Idle and now calls go out starting at the bottom of Loop 25.

I'm using a MSDL Daugherboard (this is a Option 61c, 25.3) ADAN DCH 24 is port 0 and ADAN 25 is port 1.

The PRI's on the Telco side are set to Asending on both PRI's, could that be a issue?

Thanks much

 

[RickyPone]

Your route should be set to linear. When entering the commands for the secondary d are you typing bdch? I don't fdl the dch only the msdl card. Ld 48 enl msdl x fdl. I recently had a trouble similar to what you are describing. I had to out it all and rebuild. Corruption of some sort.

 

[RickyPone]

Throw a loopback on the circuit back to you and see if they come up release wrong mode.

 

[bhassell2000]

well, I have never FDl'ed a DCH, only the MSDL card, so once you do that both should be good to go. I dont think the ascending would be an issue but you could change one end to descending to see if it helps.

Thanks,

Buddy

Linked in Profile

http://www.linkedin.com/in/buddyhassell

 

[AbneyTim]

Sounds like a timing thing on the CO side to me. If at first the channels go lockout and then a few minutes later you can complete calls it would appear that the CO was not fully ready to take the calls even if they were idle on your PBX. Do the PRIs both function properly after the initial problem?

FYI I think the release wrong mode is the state if you have a Nortel to Nortel link. On a CO link I believe the PRI's come up but the B channels are maint busy.

 

[msteeler]

Thanks for the replies. Both D-channels are built the same on the PBX except one is port 0 and the other is port 1. Telco has it built as 2 primary D's so I did the same. Loop 24, D-Channel 24 on channel 24 and Loop 25, D-channel 25 on channel 24.

So maybe a FDL only works for one DCH then. I did FDL the MSDL first and that worked.

Not sure how I can change ascending and dscending on the PBX side... how would I go about that?

For Route 5 (my PRI Route) it was set to LIN. I changed that to RRB just to see if it made a difference. I'm not sure if it did or not. I did test again pulling the cables to the Smart jacks and by the time I got backto my desk both D's were up and all channels on my Loops were Idle, however I get a busy signal in and out. Oops, there they went... all channels locked up.

Since AT&T says they are perfect, I going to have to change my config. Should I build DCH 25 as a backup?

Thanks

 

[RickyPone]

Yeah that's right about the release wrong mode. Your route should be linear.

Your proble sounds just like the one I had back in the winter. I was trying to interface with att and my trunks would come up idle and then would go lockout. Everything worked fine after I blew it all away and rebuilt. And yes I would configure a bdch.

 

[bhassell2000]

if you build a BDCH your carrier will also have to do the same

Thanks,

Buddy

Linked in Profile

http://www.linkedin.com/in/buddyhassell

 

[RickyPone]

It probably already is built that way.

 

[bhassell2000]

One last thought from the release wrong mode, are you built as User or Net?

Thanks,

Buddy

Linked in Profile

http://www.linkedin.com/in/buddyhassell

 

[RickyPone]

I just looked at my att route. The ifc is ni2 and the co type is standard.

 

[msteeler]

Release wrong mode... what is that? To answer your question though both are set to USR at the SIDE prompt.

I changed my route back to LIN.

I did wipe the config once before and started all over... still had my same problem. The Vendor (also AT&T) did the PRI config the first time around.

I changed my CO_Type to Standard.

Just pulled the cable again from the Smart Jack to test and Loop 24 is all Idle except for the first for channels (MBSY) and same goes for Loop 25, first 5 channels are MBSY. All went Idle, made a call and all locked.

 

[RickyPone]

You need to work with att and verify programming on both ends.

 

[msteeler]

Yeah, I tried that with AT&T this morning and got no where. The circuit was first set up with AT&T as 2 PRI with one D. We couldn't get that to work to work so we had AT&T build it as 2 PRI each with a D.

For grins I could build DCH 25 as a backup and see what happens. Can I just out it and then rebuild as BDCH 25?

 

[bhassell2000]

the release wrong mode message usually means either you have a loop towards you on the circuit or both sides are set to Network or both sides are ser to user in my experience

Thanks,

Buddy

Linked in Profile

http://www.linkedin.com/in/buddyhassell

 

[msteeler]

Oh my head hurts....

So I disabled everything, removed DCH 25 and built it as a backup D. That didn't work, just got a busy signal. Removed everyting and rebuilt... same problem. They come up Idle but I get a busy signal right away. Then it acts like I can make a call out and then there go all my channels on both Loops locking out. Wait 5 minutes and the channels are Idle and I'm making and receiving calls.

 

[RickyPone]

One other thing to look at is framing and line code method. Verify with att and then check your programming and dip switches on the pri card. My guess is you have already done this. Do the d-channels establish?

 

[msteeler]

Hello,

Framing and line coding are all good. I actually don't get any errors on the loop's. I unplug the the Smart Jack and the d-channels goes down. Couple seconds after plugging it back in I get the EST Confirm and Remote.

I think the dip switches are correct. Based on DNUM 15 I have 1-4 up, 5-7 down, and 8 up... I think that's correct?

 

[bhassell2000]

if the dnum switch setting were incorrect you wouldnt be able to fdl the msdl card or turn up the d channels

Thanks,

Buddy

Linked in Profile

http://www.linkedin.com/in/buddyhassell

 

[RickyPone]

You need to put a t-berd on the circuit since you can't get att to work with you.