Phone Disabled?

[phonenoob]

Last week before going on vacation I setup a handset for someone and all worked well. When I came back I got an email from her saying she was out of the office for a few days, came back and it isn't working anymore. I have confirmed the wiring and that the handset hasn't gone bad, and the PBX has a proper config for that TN.

I'm not sure what would cause this TN to magically not work, but it seems that someone told me there was a routine that ran every night that shut off TNs that had no handset plugged into them. If this handset just happened to be unplugged, this would explain my problem I think. This brings me to 2 questions:

1) How can I view if a handset has been disabled in this manner?
2) How can I re-enable the handset if this happens?

Thanks

 

[gwebster]

Do a STAT on the associated TN. If it is shown as disabled, then enable it.

 

[Klowndog]

You can get the status of a TN in LD 32 or 20 and enable it there too.
STAT l s c u Get status of specified unit.
ENLU l s c u Enable specified unit

In LD 32 you can get certain info on TN's in such a manner:
LBD l s List TN of all PBX units on specified shelf, with lamps flagged as defective.
LBSY l s List TNs of all busy units on specified shelf
LDIS l s List TNs of all disabled units on specified shelf
LIDL l s List TNs of all idle units on specified shelf
LLBD l s List TNs of 500/2500 sets with defective MWLs
LMNT l s List TNs of all maintenance busy units on specified shelf

LD 17 is where it is defined:
Gate Opener: OVLY (Overlay)
Prompt Response Comment
REQ CHG Request
TYPE OVLY Change Overlay area options
- SID xxxx System ID number
- BKGD xx xx Background Overlay task
- PBXH 00-23 Hour to perform Message Waiting lamp maintenance
- TODR 0-23 Time of Daily Routines
- DROL xx xx Daily Routine Overlays
- MULTI_USER (OFF) ON Multi-User Log In
- TRLL 1-31 1-31 Test RPE Local Loop back
- CY45 (0)-31 Cycles LD 45 can be run whenever a fault is detected

These are your options when making the CHG to DROL in LD 17:
DROL 30, 32, 33, 34, 35, 36, 37, 38, 40, 41, 43, 44, 45, 46, 51, 53, 60, 61 basic-1
Daily Routine Overlays. Daily or midnight routine
programs are run once a day at the time specified by
prompt TODR.
Programs 33, 45, 46 and 53 are not applicable to
Option 11C.


I'm not sure how to configure midnight routine results to go to the printer, all I know is that is was always on the printer in the morn and it would show the results.

 

[Klowndog]

I found this too:
Midnight and Background Routines
In the Configuration Record (LD 17), you can select the overlay programs
that will run in the Midnight Routine and Background Routine. These routines
automatically perform maintenance checks. Programs included in the
Midnight Routine are defined with the prompt DROL (derived from “daily
routine overlay”). Programs included in the Background Routine are defined
with the prompt BKGD.
The Midnight Routine runs once every 24 hours. This routine is preset to run
at midnight when a system is shipped, but you may assign a different time in
the Configuration Record. When it is time for the Midnight Routine to start,
the system cancels any other program.
The Background Routine runs when no other program is loaded in the overlay
area. The programs included in the Background Routine run in sequence
repeatedly until the Midnight Routine runs or there is another request to use
the overlay area (for example, if you log on to check the status of a circuit
card).
Page 54 of 76 Software maintenance tools
553-3001-500 Standard 14.00 April 2000
You may include the programs listed in Table 6 in Midnight and Background
Routines. Your maintenance requirements and the configuration of your
system determine the programs you include in Midnight and Background
Routines.
Note: Software Audit (LD 44) should always be used in the Background
Routine.
Table 6
Programs used in Midnight and Background Routines (Part 1 of 2)
Program number Program function
LD 30 Network and Signaling Diagnostic
LD 32 (Midnight only) Network and Peripheral Equipment Replacement
LD 33 1.5 Mbyte Remote Peripheral Equipment
Diagnostic
LD 34 Tone and Digit Switch and Digitone Receiver
LD 35 (see Note 1) Common Equipment Diagnostic
LD 36 Trunk Diagnostic 1
Note 1: For option 51C, 61C, 81, and option 81C, use LD 135 instead of LD 35.
Use LD 137 and LD 37.
Note 2: LD 43 will automatically be activated during midnight routines if changes
have been made within the past 24 hours.
Software maintenance tools Page 55 of 76
General maintenance information
LD 37 (see Note 1) Input/Output Diagnostic
LD 38 Conference Circuit Diagnostic
LD 40 Call Detail Recording Diagnostic
LD 41 Trunk Diagnostic 2
LD 43 (Midnight only) Data Dump (see Note 2)
LD 44 Software Audit
LD 45 Background Signal and Switching Diagnostic
LD 46 Multifrequency Sender Diagnostic for ANI
LD 60 (Midnight only) Digital Trunk Interface Diagnostic
LD 61 (Midnight only) Message Waiting Lamps Reset
Table 6
Programs used in Midnight and Background Routines (Part 2 of 2)
Program number Program function
Note 1: For option 51C, 61C, 81, and option 81C, use LD 135 instead of LD 35.
Use LD 137 and LD 37.
Note 2: LD 43 will automatically be activated during midnight routines if changes
have been made within the past 24 hours.

 

[Klowndog]

I think you can also go into LD 22 and do a VHST to view activity such as midnight routines.

 

[phonenoob]

Thank you for the information. Stating showed that it was ok, so I tested it in the wiring closet. Must have freaked out for some reason, but it works ok now.