Schedule Reboot

[pakman]

Hello,

I thought I could go into the scheduler and setup the PBX to reboot on a weekly basis. However, under select activity I couldn't find anything that would allow me to do this. Does anyone know how to setup a PBX to reboot on a schedule or if it's even possible? While I am on the subject what is best practice daily, weekly or monthly? What's happening every so often is I will come in and one of our main sites that have our Call Center the main line will be busy until I reboot the PBX. When I look through the log it references memory being full. Reading Mitel logs is just a headache as there very vague. If anyone, has some KB articles about logs I would appreciate it as well. To give you an example of one of the logs see below.

Thanks,

Log Type  Software
Log Number  4610
Severity  Warning
Date  2013/Sep/12
Time  10:16:53
Source  Call Control - Software
Description  OS (Message) warning: Receiver process not found. Redun code: $02 $02 $02 TX/RX msid: $00 $01 $00 $00 $00 $00 $01 $00 $00 $00 TX/RX pid: ($0003,$00DA) cpprog ($0004,$05A5) ---------- appl/func: $01 $2C active pid: ($0003,$00DA) cpprog 
Module  Main
File Name and Line Number  log_outputs_util_en.c;1218

[bluewhite4]

Reboots are scheduled through Maintenance commands, not through the calendar.

Take a look at the "Programmed Reboot" commands,  those will show you the different options.

[ralph]

Here's the quick and dirty command

Prog res sched on
Prog res sched Monday 2:15

This will reboot your system on mondays at 2:15 am.

Ralph

[lundah]

Mitel Tech Support will tell you that you never have to do a programmed reboot any more, but I find that depending on the application and what software release, somewhere between weekly and monthly will keep things running smoothly.

As far as the trouble you describe, I don't think the log message shown is related to that, I see similar messages frequently even on a freshly rebooted controller. On the system that rings busy until a reboot, what's the setup look like (controller model, software release, trunk types involved, etc.)?

[pakman]

Thanks for the reply's guys.

Yes, the log I posted has nothing to do with the memory errors I see when the system goes busy. I just put that in there to make a point about how much Mitel sucks with their log descriptions. On the pbx that rings busy it's a MXE-III at 6.0 the trunks our PRI. Here's the log dealing with the memory "OS (Store) info: Free memory low water mark is 002EAA00 bytes." The one's that bother me are
Call Control - Maintenance   TRAFFIC CONGESTION REPORT  FROM  20 : 42 TO  00 : 47 No trunks available : (Route ID # : Total)   11 : 53

When I do a show faults alarms I get this.
Trunks                                                                         
----------------------------------------------------------                     
|                |                              | Total  |                     
| Cab Shelf Slot |      Card Description        | Faults |                     
----------------------------------------------------------                     
|  7    1     2  | MC270Ax Universal T1         |    8   |                     
----------------------------------------------------------                     
Digital Links                                                                   
----------------------------------------------------------                     
|                |                              | Total  |                     
| Cab Shelf Slot |      Card Description        | Faults |                     
----------------------------------------------------------                     
|  7    1     2  | MC270Ax Universal T1         |    1   |                     
----------------------------------------------------------                     

[ralph]

TRAFFIC CONGESTION REPORT  FROM  20 : 42 TO  00 : 47 No trunks available : (Route ID # : Total)   11 : 53

The traffic congestion report is normal.  It's telling you that you're getting busies on one of your outbound routes.  (11).

The alarms are showing you that you have some issues on your trunks (which could contribute to the traffic congestion).
Stat the Plid "stat 7 1 2 1" and look for channels that are suspect or out of service.
You may be able to busy out the channel and return to service to resolve but you may also have to call your carrier and report the channels being down.  After you busy and RTS the channels do a direct trunk select and test an outbound call.  If it fails call and work with your carrier.

 I've resolve similar things by simply pulling the plug on the T1, waiting 30 seconds and then plugging it back it.

Ralph

[august]

Maybe you have a dspool problem, but since you have an alarm with your pri card, I would take a look a that first

In the log, do you see something like software error, no ressource available?
If yes you may have a dspool issue and may try this:

If you get the busy signal, before you reboot:

open a first putty to telnet to your 3300 ip address on port 2001
open a second putty to telnet to your 3300 ip address on port 23.
login with the default sx2000 username and password
type: lldcli dspool audit

You will then see the number of free dspool bucket on the 1st putty session.  If you have more than 90% of the dspool in used, you will then cleared them and your system will be ok, until the next time without a reboot.  You will then have to find why the system does'nt released the dspool.