INI after loops down

[Jaimegu]

We have experienced inits after several loops fail or when a loop is restored repeatedly.
It happens in Succession 3.0 and 25.40 (and happened in Rls 22, 23 and 24.30). Both PBX are 81C FNF.
I have to mention that our loops are E1s.
It is really annoying because we have over 45 E1s (some of them are euroPRIs)on each M1 and it's impossible to guarantee their stability (both, E1s and Meridians).
Do you know any fix for that? Have you experienced similar situations?

TIA

Jaime

 

[mluckie1]

You will need to change the threshold values in ld 73 (DDB Digital Data Block) for those loops. Check the CEQU to find what ThreshHold is assigned. Set RALM and BIPC to 128, set LFAC to 0.

 

[johnpoole]

the thershold will let them run dirtier, but want stop the ini problem.. that's a little deeper. how many errors/sch etc do you see during the day under normal conditions.. if it's more then a few..ie pri227 err80 err095 etc, those errors are using to much cpu.. do you have a lot of sets that are either programed as the wronge type, (check them all), or sets that are programed and not plugged in.. if you have ld 30 out of the ovly, the problem will only get worse.. the swtich lets us get away with dirty software and maint practices for long enough to get us lazy.. when the switch get as large as ours, cpu usage reaches a point where a string of trash eiter fills up the ram or overload the cpu.. this 81 was doing the same thing when i 1st got here. you could lose a couple of pri's and ini was the next prompt you got.. that has went away with ROUTINE maint..

john poole
bellsouth business
columbia,sc