Searching for disabled digital lines

[Quadzi]

I have an inherited Meridian 81c that evidentally someone took to disconnecting lines on the punch board, without removing them in software. I'm now just about out of available TNs and it's going to be time consuming to check all of the existing TN's that have nothing punched to them. Is it possible to list all of the disabled TNs so that I can check to see if they are phones on the floor that are unplugged, or if they are unproperly reclaimed phones?

 

[GHTROUT]

Look in LD117

The first command is

INV GENERATE SETS

It can be scheduled to run night as well

Then, run

INV PRT SETS

And every digital TN with serial number, will be output in a CSV compatible screen print.

Those that have no serial number will list as "unavailable", meaning the telset could not be detected.

That is far better than any results from LD30 SHLF tests and LD32 LDIS commands





GHTROUT.com | FAQs | Recent Replies

 

[Quadzi]

When I go in to LD 117, it says SCH0099 INV? when I type INV GENERATE SETS, or even just INV.

 

[GHTROUT]

The INV feature may be on Rlease 25.?? and newer.

If your system is oder, then here is what I'd do...with some info about how to get the most accurate info:

First and formost, you need to enable all cards and units so the system starts fresh before the LD30 test that follows. The easy way to enable everything is a shelf by shelf "ENLS" commsnd in LD32

ENLS 0 0
ENLS 0 1
ENLS 2 0

and so on/

Then, during the Midnight Routines (or you can manuaaly run this during quiet periods), LD30 runs something like:

LD30
.LOOP ALL

and it outputs a bunch of "NWS??? " codes for cards and TNs.

Disregard the NWS output since it is only accurate when very few TNs per shelf are "phoneless"

What is accurate is a shelf by shelf commanbd in LD32 "List Disabled" (but you have to run this after the LD30 test above)

LD32
.LDIS L S (loop number and shelf number)

and so on for each shelf.

All TNs that disabled will be output for your enjoyment







GHTROUT.com | FAQs | Recent Replies

 

[Quadzi]

How much of a quiet period do I need?
Will this disrupt calls?
How long will the ld 30 test take?
Can I run the LD32 LDIS tests a few hours after the LD30 loop?

 

[GHTROUT]

Pick the last hour of your business day ends is a safe bet.

The LD30 LOOP ALL test will take 20 minutes on a 3000 line system. What users "might see" is lamps/LCD flash on the set. No calls will drop, regardless of when you run the test. The test is simply most effective if it has access to the TNs when they are idle.

The LD32 tests can be run the minute you are returned to the "dot" of LD30...even the next day is fine. Any time of the day is no issue.

Like this

LD30
.LOOP ALL

NWS bla bla
NWS bla bla
NWS bla bla

. <---that dot means "done"








GHTROUT.com | FAQs | Recent Replies

 

[johnpoole]

i've never had that command stop calls or even slow down the cpu more then 10 percent... i perfer ld 117 inv generate midnight, then each Wed i do a inv prt sets.. that shows missing sets as well as sets that don't match the as built.. ld 30 and ld 32 commands will show analog if they are disabled ld 117 just shows digital..

john poole
bellsouth business
columbia,sc