Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Cleanup Unused Extensions - SX2000

Status
Not open for further replies.

tundranugget

Technical User
Sep 4, 2003
98
US
We inherited the SX2000 system from another department that believed that documenting anything was bad for your health. We have zero documentation, except for what is intrinsic to the SX2000. There are extensions assigned that have no desksets attached, some have no cross-connects, and for some the building they were in no longer exists.

Since we are running short of DID trunks, management has decided to purchase more. I believe we can avoid this.

What is the easiest (best) way to determine all the extensions that are valid? As in: there is a functioning deskset attached to a live outlet.

Also, just determining that there is a live outlet somewhere would be helpful, even with no deskset attached. I can't think how to determine that, though.

Of those valid extensions, is there a way to determine any that have not been used for an extended period (that might be reclaimed)? There is call accounting software on a separate server - Genesis, I think.
 
For digital sets you can type the maintenance command:

Use the state command on each DNIC card on you system.

It will return Out Of Service for any ports without phones plugged in.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
 
Open a capture file on your terminal emulator then as kwbMitel says use the state command. However you needn't break it down to the individual card or board level. You can give the command to the entire peripheral node (or peripheral pair if you have extended pers) thusly:

Stat 2 (gets everything in 2nd per node or pair)
stat 3 (gets everything in 3rd node or pair
stat 4 Etc., etc.

This will only give you valid OOS indications for your DNIC ports, but hopefully that will give you a good starting point. The ONS ports (modems, faxes, polycoms, etc) will be another matter and will require a walk-thru of the building. Anything you can't find just pull the pair and fan it back in for a month or so. If no one's bitched in a month, pull it down.

The 'CONFIG LONG ALL' command will give you your programmed/installed card inventory in a similar matter, except the "all" qualifier will dump the info for the whole switch without having to interrogate individual cans.

Next we expect to learn that you've managed to generate a full set of cross connect records. :)




 
Thanks for all your help and suggestions. I have removed a couple dozen "phantom" digital phones os far, and removed the cross connects. They were the easy ones - the buildings were gone.

One sentence I didn't understand: "Next we expect to learn that you've managed to generate a full set of cross connect records." Ha, ha. That's a good one. I have some panels with any number of 25 pair cables arriving, with no indication where they are from and where they are going; bix connectors hanging loose with unlabeled (the default) wires connected any which way; junction boxes with unlabeled wires spliced together, or sometimes just twisted together; one long inaccessible run consists of several partial reels of 25 pair and they only connected the pairs as they needed them; etc. Sigh. Me and my trusty toner....
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top