MOV, NCOS, and MAN INT

[rondphig]

Hello everyone,
3 questions please.

1) Once and for all, (as there is still much mixed opinions on the net) are LD 11 movs bad? are they really that much of a risk for corruption? i find them much easier for changes as i can do them remotely and dont have to go onsite and punch down cross connects. Also, is there a difference in doing 1 mov in a period of time vs 30 movs in the same period of time?

2) Is there an easy way to print out what each NCOS level allows and disallows? is there an unwritten set of standards as to what each level of NCOS is usually set up as?

3) Lastly, what "real" consequences are there from pressing the man int button to clear things up? My vendor usually recommends that they do this as opposed to me. Once, one of the techs muttered that if the switch doesnt come back up within 90 seconds, and if you dont do something right away then all h3ll will break loose and if if that happened to me without them there, i'd violate the service contract blah blah etc etc. Is there truth behind this? Or do they just want their $200 an hour house call?
thanks

 

[makemorebeer]

I'm not an expert by any means, but i've used my man int button on our system here, and on our remote system multiple times in the last two years without any problems.

 

[phonz1]

Question 1. The theory is that you shouldn't move ACD sets in software. Standard digital/analog sets should be okay

Question 2. In LD87, Prt NCTL, you'll see NCOS 0 0
NCOS 1 1, etc
In that scenario, NCOS 0 would be the lowest. I usually set up switches with NCOS of 0-7, with 0 being the most restricted, 7 the least.

Question 3. A Manual INIT will clean up minor corruption etc. Your vendor is partially correct, if you INIT your switch and something breaks and they have to clean it up, I could see them billing you and they can see if and when it may have been init'd..

 

[GHTROUT]

I think the MOV command is fine, unless you encounter a problem...if you do, an INIT is certainly not going to wear out anything. If the set is an ACD agent, most people will say not to use MOV and I would agree it's not worth the risk.

If you can afford the 60 to 90 second interuption, use the INIT button whenever something seems out of whack and cant be solved by service change or maintenance overlays. Just make sure you also know how enable AMLs in LD48, DCHs in LD96 and have easy access to the maintenance overlays book...not a warning, but rather a timesaver.

GHTROUT.com | FAQs | Recent Replies

 

[acewarlock]

I have used the MOV Command for 27 years and never had a problem, even moving ACD sets but thats me. Don't do what you don't feel comfortable doing.




This is a Signature and not part of the answer, it appears on every reply.

This is an Analogy so don't take it personally as some have.

Why change the engine if all you need is to change the spark plugs.

 

[GHTROUT]

I decided to look in the rls5 books for "MOV" and now they actually have a disclaimer:

MOV command can be used to move
analogue "IPE" telephones from one loop,
shelf, card, unit to another lscu with the
following restrictions (includes moves across
Superloops):
basic-25.4
-ACD sets must not be moved. Remove (out)
data and re-enter at destination.
-Telephones with mixed directory numbers
can only be moved to a TN on the same loop;
unless the prompt MLDN = Yes in LD 17.
-Cannot be used for Small System and CS
1000S Model sets
MOV command can be used to move
analogue "EPE" telephones from one unit or
card to another, but does not support moving
these phones across shelves or loops.


~~ However, I've also done MOV on ACD sets...

GHTROUT.com | FAQs | Recent Replies

 

[mikeyb123]

Q2. as Phonz says use 87 for part of the answer but you'll also need to use ld 49 as below to give you whats allowed and denied number wise:

>ld 49
DGT000
MEM AVAIL: (U/P): 46068816 USED U P: 5140869 420391 TOT: 51630076
DISK SPACE NEEDED: 615 KBYTES
REQ prt
TYPE fcr
CUST 0
CRNO

CRNO 0
INIT ALOW

CRNO 1
INIT DENY
ALOW 112
999

CRNO 2
INIT DENY
ALOW 112
131
1320

And for my 2 pence worth never had any issue with moving acd sets in 12 years

It's not getting any smarter out there. You have to come to terms with stupidity, and make it work for you.

 

[johnpoole]

1.. we do 100 mov's a month, without a problem.. i am a vendor but the 2 inhouse techs that i trained here use that command every day... zero corruption

2.. you need to print your rlb's and nctl...quick and dirty.. if i have ncos 0= frl 0 thru 7=7 (most switches) .. if i want dial the west coast, i dial 9 (ac1) that takes me to ld 90, i dial 1213, that matches a defined rli.(ld 86).. entry 0 sends me to my ld route, BUT the frl is 4, (the cost of the call), so if my ncos is 4 or higher, the call goes to LA.. but if my ncos is 3, the switch looks at entry 1 then 2 etc.. if one entry has an frl of 3 or lower my call can use that route..

that was pretty common when ld cost 10 times as much as we pay now... worker bees could dial the number and if the cheap route was not busy the call went, otherwise he got a all trunks busy (120 ipm).. but if a big shot dialed the same number with a higher ncos, the cheap route was busy, he could still use all possible routes..

3... we need the money, i do not want my paycheck to bounce.. i have not ini'ed a switch to clean it up in almost a decade, other then on an install or upgrade.. the only reason you might want to slow down prior to pushing the silver bullet is, can you recover if the switch does not boot?.. there is no magic 10 min window, they never did give us any magic words to chant.. 99.9 percent of all problems can be fixed at the command line.. i had a good friend that ini'ed every meridian he ever got a trouble on worse then an bad handset, back in the day we had less maint commands and a lot of us were learning together.. and we didn't have the internet

john poole
bellsouth business
columbia,sc

 

[a12ozbottle]

1. I have seen corruption from the mov command but only when moving acd sets asscoiated with a supervisor set. If you have symposium make sure the set is deaquired.

2. PRT NCTL in ld 87 look at the FRL on each NCOS. PRT RLB in ld 86 the NOCS FRL must be the same or greater than the FRL setting on the RLB to go out the route. Not all PBXs are configured the same so there is no consistant answer, NCOS 0 could be programmed to be higher that NCOS 10.

3. MAN INIT 99% of the time will not cause any problems, usually resolves them. But if it does it can take some experience to get things back to normal operation.

 

[acewarlock]

The INI won't cause a problem, but whatever is causing a problem that you can't resolve any other way except by doing an INI, may seem like a new problem after the INI but was really the original problem that you couldn't see.




This is a Signature and not part of the answer, it appears on every reply.

This is an Analogy so don't take it personally as some have.

Why change the engine if all you need is to change the spark plugs.

 

[rondphig]

thanks everyone. that helped.