PRI goes down every couple of hours. 1

[PhonesBrokeHuh]

I have a PRI that is going up and down after it was cutover. I believe that telco is using a siemens switch
NI2,B8zs,esf,desending, we can make calls and take calls just fine for up to several hours at a time then it will go down possibly several times in a row. Telco says that they can loop to the smartjack just fine but when they loop to the card they get errors. any ideas on my next step?

 

[PhonesBrokeHuh]

Jerry

What timing options do you use, I set mine to Primary (clocking with the carrier as a reference). This has usually worked ok in the past. I do have one site though that l;ooks like it is loosing timing every couple of days and I was going to try maybe becoming the master, what do you think?

 

[jerryreeve]

What I was refering to was not so much as settings like that but rather a clock/timing source actually going bad.
You should always use the telco as the primary timing source since their clocks are assumed more stable than you can get on site. the only time you should have a T-1 set as primary/master is when you are going between two PBX's without getting your timing from telco.

JerryReeve
Communications Systems Int'l
com-sys.com

 

[panstain]

I understand a possible cabling problem, which may be the cause of your problem. I would like to let you know that I have had a similiar problem on using MICS 4.0 with PRI, I upgraded to 4.1 MICS software and that corrected my problem. Apparently the bugs on PRI were not completely worked out on 4.0...... and of course I tried cabling, CSU replacement, bypass surge protections, everything physical, it ended up being the 4.1 upgrade that fixed it.

 

[PhonesBrokeHuh]

This site is currently at 6.0, after a complete swappout of cable pairs, DTI, patch cords, and smartjack, the site started to run clean. There have been about 4 losses over the last few months. Most of them have happened after hours and I contributed them to b eing telco issues only.
I am now starting leaning toward the DTI card was the culprit.

 

[cowenby]

We had similar problems for seven months. During that time we swapped out everything: the telco's Network Interface Unit, Digital Trunk Interface cartridge, Combination Fiber 6-Port Services cartridge, NVRAM cartridge, the Modular ICS Core Hardware, upgraded the Software Feature cartridge to version 6.1 and "hand-packing" the programming for a 160-station system. We still had problems!

B-Channel Service Messaging contributed to our problems, but the final resolution came with a simple programming modification, changing the destination code for outbound calls from "9" to "9Any". We've had no problems since this change was made.

PRI circuits can be a pain when they don't work, but they sure are sweet when they finally do work!

 

[cowenby]

Thanks for sharing the solution to your problem...

 

[Refire]

be sure all unused channels are deprovisioned in mics