Meridian Option 61 - Stop TN disabling w/ Midnight Process

[olympus41]

I have an Option 61 Meridian phone system. I am trying to stop the function in MIDNIGHT PROCESS that disables a TN in the system when a phone is not hooked up. The OVLY used to look like this.

OVLY
SID 0
BKGD 044
PBXH X
TODR 00
DROL 030 034 036 038 045 054 060 135 137
MULTI_USER ON

I removed DROL "030" and now the OVLY looks like this:

OVLY
SID 0
BKGD 044
PBXH X
TODR 00
DROL 034 036 038 045 054 060 135 137
MULTI_USER ON

The next day (after the midnight process) I did a LDIS # #, and the phone system had disabled a bunch of TN's without phones hooked up. What would cause this to still happen?

 

[PERRYPJ]

I've seen this on early releases like 17.76 but not in later releases like 25.40. You can contact Nortel if you are running a later release to get an answer.

OLD ROLMEN WORKING ON NORTELS

 

[johnpoole]

never a good idea to leave missing phones enabled, i will not even leave missing phones in my switch.. maybe nortel has fixed the problem and will not let do things that slow down the cpu

john poole
bellsouth business
columbia,sc

 

[coniglio]

Dear JohnPoole, why do you discourage removing overlay 30? I'm curious because I also had it in my midnight routine and my manager suggested I remove it, because we are constantly moving employees between seven floors and there are no cable records and it's a big process to get access to the closets plus it can take forever just to tone out one jack. Now that I've removed ovly 30 I just plug in a phone and copy software to it. But I figured there must be a reason to have it in there in the first place so I'm anxious to read your response. Thanks.

 

[senk1s]

mainly security reasons, as far as i know.
unused extensions are a haven for hackers ...

 

[johnpoole]

it would be easy for a hacker to build a rcfw on a unused phone that would work if the station is enabled, but if a hacker gets in to your switch at that level, you can not stop him anyway

john poole
bellsouth business
columbia,sc

 

[Firebird Scrambler]

I've seen this problem before. To stop TN's disabling, you are correct to remove "30" in "DROL". I also don't agree in doing this, but for the later software releases such as V25.xx. A warm start or Sys load after a "edd" was needed.
It never used to be a issue before, But I found that this was now the way on how to do it.

All the best

Firebird Scrambler
Meridian Programmer in the UK

 

[johnpoole]

that's one fo the things that comes with time, turn it off long enough and you will see a few comp ini's under heavy traffic. i've also seen techs turn off scpu to hide a marginal cni, never works for long

john poole
bellsouth business
columbia,sc

 

[M1PBXtech]

Olympus41 I was wondering if you enabled all the disabled TN's after you "X'ed 30" out of DROL?? Seems obvious but thought it was worth asking.

Also you said your Meridian is a 61C. It is important to know that by removing 30 your clocks will not switch each night. So you are no longer testing your redundant clock each day. I typically like to see if I am on Core 0 that I am also on clock 0 and the next day would be Core 1 and Clock 1. You will notice that does not happen anymore with 30 missing in the DROL.

Additionally if there are specific TN's you are trying to keep from being tested you can add CLS- flxa to the TN's and midnight routine will not disable them.

Ron Daniels

 

[johnpoole]

just take all the loads out of midnight and then blame the switch when it quits

john poole
bellsouth business
columbia,sc