Frame Slip Errors

[Jay2003]

Hi All,

I have a question regarding frame slips on a M1 Opt81.

I have seen this error before but it was due to moving a TN, This lead to a loop being corrupted and we had to off everything from the loop, Re Download the software to the loop then rebuild the TN etc's.

This is the only anomoly that I am aware of that can cause this.

The question is this, Our Vendor has stated that this can be caused by making changing IDC entries under heavy load.

The change was made around 18:05 so the only processing would have been out of hours, Could someone please clarify "If Possible" If in fact changing IDC's during production has any negative impact as I have never seen or heard of this before.

The only issue that I have heard of regarding IDC is the lag that it sometines takes to re route the calls, Couple of seconds until about 10.

Thanks in advance for shedding any light on this matter.

Jason

 

[wdhb]

Well I can say that doing changes on an active IDC table was in pre Rls21? a real big no - no & would cause corruption. As to it causing slip errors, well that sounds, quite frankly like bs to me, but then I'm wrong every day, so someone else might like to educate me. For slip errors I would be checking your clocking in LD60. Refer to your NTPs & use the commands SSCK & LCNT to check your loop.
By the way, the advice that doing a TN caused slip errors also sounds dubious to me.

 

[Jay2003]

I agree pre Rls21 was out but 24.x is ok, Or so I thought.

I had seen a few months ago a copy of a document from our other "Good" Vendor / maintainer that moving a TN can cause corruption, The RSIG keeps initializing and fails to respond.

The by product of this is that the clock with start erractically slipping. To test the fault I switched the clocks and this is where the RSIG arise. This gives me the loop in question.

So I then switch back the clocks, Disable the loop, The RSIG errors go away.

Previously we dumped the loop, Downloaded S|W then populated it again, This worked fine.

I am at a loss, If I was a betting man I would say that a MOV statement was initiated, There are around 5 users who have access to this and the switch isn't configured for MultiUser Login. "That will get fixed".

Thanks anyways.
I have a call in an hour to get to the bottom of it.

Thanks again

Jay

 

[johnpoole]

i have made several changes in an active idc, but the best thing to do is have a dup idc and make changes in the standyby, switch it to active. no one knows what causes that type of corruption in most cases, and if your in the switch the vendor has a easy out, i am a vendor i know. the mov command can cause trouble, make sure you disu the set before the move. multi-user is ld 17, chg ovly, yes at or multi prompt. i would perfer not to mov stations to or from a remote to a local supl but will not always cause trouble. and i guess it goes without saying, NEVER, move or copy a acd set. short cut is to nuk key 0 and then it's not a acd phone, but nortel don't support that, but then they don't live in a world were customers matter. Most of us do in the service industry.

john poole
bellsouth business
columbia,sc