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 biv343 on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

UP Time 3

Status
Not open for further replies.

billkennedy32

IS-IT--Management
Aug 11, 2004
106
CA
Is there anywere i can find info on how long our IP office pbx was up, yesterday we had some lost calls and wondering to see if this was due by some one rebooting the pbx.


Thanks
Bill
 
Use the Monitor application.

When you have entered the correct IP and password for the IPO, the Monitor's first line will tell you the up time.

If the system has rebooted because of an error, it will then appear in an alarm log dump, which will appear shortly after.
 
you make any sence of that

1mS PRN: Monitor Started IP=192.168.130.3 IP 406 3.0(44) E-Sync
1mS PRN: LAW=U PRI=2, BRI=0, ALOG=0, ADSL=0 VCOMP=0, MDM=0, WAN=0, MODU=4 LANM=0 CkSRC=1 VMAIL=1(VER=2 TYP=1) CALLS=3(TOT=535)
489mS RES: Tue 14/3/2006 10:11:49 FreeMem=4406752(50) CMMsg=8 (10) Buff=100 657 499 1399 4 Links=6050 Elements=0
3010mS PRN: +++ START OF ALARM LOG DUMP +++
3010mS PRN: ALARM: 23/01/2005 13:58:01 IP 406 2.1(15) <TLB Insruction Error> CRIT RAISED addr=0164e3b0 d=5 pc=00000000 0161c358 01634bcc 01635e74 016c4434 016a9944
3010mS PRN: ALARM: 13/03/2006 14:03:20 IP 406 3.0(44) <TLB Data Error> CRIT RAISED addr=45200015 d=5 pc=01580a54 01580a44 01583028 01583194 015832c8 016f6470
3010mS PRN: +++ END OF ALARM LOG DUMP +++
3717mS PRN: CMCall::Forced Sending Complete
 
It looks like it rebooted once yesterday and once in january before you upgraded to 3.0.

Uptime is actually before that daya you've displayed (about half-an-inch above). You've also taken/made 535 calls since the last reboot.

Force Sending Complete. For lack of a better route to send an outbound call (that happened to be going on at the moment you connected to the system with Monitor) it sent it out the default route in the System Short Codes. Most likely unrelated to your reboot issue, but FYI.

Hope this helps...

Kris
 
Do you think there could be anything els in the log that would tell us why it rebooted .

Thanks
Again

Bill
 
Not really. I usually keep monitor running (and logging to a text file) so I can trace that kind of stuff. Lack of a background kills in this type of troubleshooting. What kind of phones? If 44xx, did their "message lights" flash (happens on boot up). On 64xx and 54xx/24xx the names disappear for a while on the display until the system is back up.

We know it rebooted, but the cause is what we can't figure out w/o having trace from that moment. I'd see if you can arrange to have your VM Server keep MONITOR running all the time, then if this happens again we can look at exactly what happened on the IPO to cause the reboot.

I will say this, 3.0 had issues with phones sometimes not coming up after soft-reboots and I see you have 2 PRIs (which was part of the issue). 3.1 is much better, but the problem still exists. I would recommend upgrading the system to 3.1.48-PB4501. Its a private build based on 3.1.48 that corrects an issue with rebooting when CDR is active (a new feature of 3.1) and someone from a conference call hangs up. If you have no need for the CDR feature, 3.1.48 or 3.1.56 would be fine. If you do have a desire for CDR, use the 3.1.48-PB4501 because 3.1.56 does not have the fix in it for CDR yet.

BTW, since you do have 2 PRIs, make sure only one of them is set for Clock Quality=Network. The other should be set to Fallback. This can cause issues.

Hope this helps...

Kris G.
 
HG calls overflowing to a busy HG are a known cause of reboots, this could be your problem
 
Typicaly the TLB errors you see are some sort of software loop. Try running (even though i hate it) your config thru the Wizard and see what kind of errors it finds.
 
I am now trying this as well on my box's to see what ifo I can find.. all looks too complicated.. what things should be checked to monitor ??
 
I would suggest reducing the items monitored to a minumum & increasing if you do not get any usefull information

Error & printmsgs in System are important (many other settings will not work without them) allso the settings under the call tab are worth setting
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top