atcomsystems.ca/forum Forums TDM Business Telephone Systems Mitel Telephones & Systems log info

Can anyone tell me what these logs mean. I have a customer with this new mitel that's having some problems with incoming calls ringing busy intermitantly. They have 1 PRI w/NI2 protocol utilizing DID's.Their vendor states it's not their problem. I'm schooled in NEC, so unable to decipher these logs. Can anyone help?


All Software Logs
Log Number Severity Date Time Source Description File Name and Line Number
4993 Warning 2006/Apr/03 08:40:11 VDSU-1 Connect Ind in invalid state = 7, callID=4cad, portID=a2b99e8, CH=4 logfile.cpp;162
4992 Warning 2006/Apr/03 08:40:04 VDSU-1 Connect Ind in invalid state = 7, callID=4cac, portID=a2b99e8, CH=4 logfile.cpp;162
4970 Warning 2006/Apr/03 08:31:09 Call Control - Software Program: cpprog Offset: 0:0000079C PC: 0003B18C
Program: cpprog Offset: 0:00000B84 PC: 0003B574
Program: cpprog Offset: 2:00001A8C PC: 002DB520
log_outputs_util_en.c;2078
4969 Warning 2006/Apr/03 08:31:08 Call Control - Software Overwriting a non-nil call log idx: $01C6
Traceback:
Program: cplowlvl Offset: 2:00001B00 PC: 002932C8
Program: cphold Offset: 2:0000011C PC: 00363730
Program: cpprog Offset: 2:00000C9A PC: 002DA72E
log_outputs_util_en.c;2078
4882 Warning 2006/Apr/03 04:48:24 Heartbeat Server ICP has lost contact with (66.0.10.50 (08-00-0F-19-49-9B)), motfcc cluster pool free: 2886 and low water mark: 2787 HeartbeatRecvTimeoutHandler.cpp;260
4881 Warning 2006/Apr/03 04:48:04 Heartbeat Server ICP has lost contact with (66.0.10.50 (08-00-0F-19-58-A4)), motfcc cluster pool free: 2887 and low water mark: 2787 HeartbeatRecvTimeoutHandler.cpp;260
4880 Warning 2006/Apr/03 04:48:03 Heartbeat Server ICP has lost contact with (66.0.10.50 (08-00-0F-19-58-84)), motfcc cluster pool free: 2887 and low water mark: 2787 HeartbeatRecvTimeoutHandler.cpp;260
4879 Warning 2006/Apr/03 04:48:02 Heartbeat Server ICP has lost contact with (66.0.10.50 (08-00-0F-19-4A-7C)), motfcc cluster pool free: 2887 and low water mark: 2787 HeartbeatRecvTimeoutHandler.cpp;260
4874 Warning 2006/Apr/03 04:36:52 Heartbeat Server ICP has lost contact with (66.0.10.50 (08-00-0F-19-49-9B)), motfcc cluster pool free: 2887 and low water mark: 2787 HeartbeatRecvTimeoutHandler.cpp;260
4873 Warning 2006/Apr/03 04:36:49 Heartbeat Server ICP has lost contact with (66.0.10.50 (08-00-0F-19-4A-7C)), motfcc cluster pool free: 2887 and low water mark: 2787 HeartbeatRecvTimeoutHandler.cpp;260

Psersonaly I would not be overly concerned with translating the software logs . I would be looking into the dt stats and condition of the PRI . What model Mitel are you working on ? I don't know all the Mitel models but there are enough people in this forum so that most any Mitel is covered . Thanks and

I'm sorry, forgot to mention that important tidbit. :rolleyes: It's a 3300 ICP. Thanks.

Find out the the PLID of the PRI Card . From the maint screen type "dtstat" and the plid location then "last 24" with 24 for being the previous 24 hour period . Also stat the card and make sure no channels are manbusy or out of service . If you can duplicate the issue . Try reloading the card then see if you can duplicate the issue again . Let us know . Hope this helps .

It would also be helpful to know if the 3300 is connect to an NSU and what version of IMAT the PRI has .so at the command prompt you would type in something like this DTSTAT 7 1 1 1 LAST 24 . If you don't know the cabinet number look it up in the digital links form . Thanks

We isolated the problem from the telco as channel 5. I didn't receive your post in time to look at dtstat and stat. I had the telco turn down the circuit, even though all channels tested good from them, which cleared the problem for a second time. This last occurred at the end of Feb., and the vendor did the same thing to clear the trouble. What would cause a channel to busy out in the PBX? How do I get the version of IMAT? And it is connected to an NSU.
PS, thanks for the "Welcome" it's nice to have this forum. :thumb:

It sounds like the PRI card may be intermittenly failing . The only sure way to tell is to stat the plid when this trouble occurs . From the maint screen you would type lets say STAT 7 1 1 1 you would then see the condition of all 23 channels . They should all list back as being IDLE or BUSY . If some or all list back as either OUT OF SERVIVE, NOT SEIZEABLE , MANBUSY . Then change back to IDLE or BUSY without any intervention you most likely have a faulty PRI card . You may also want to check your clocking stats and clocking source . When I have a chance I will Private Message you with how to check your IMAT version . Thanks

I think I may have unintentionaly mislead you . You can check the load the PRI is running by typing in lets say FIRMPLID 7 1 1 . The IMAT is software you load on you pc to load the PRI software info&cpn range/ranges.

If you are lucky it will turn out to be the providers circuit and not their PRI card . The whole NSU would have to be replaced . I don't think just the PRI circuit pack is an FRU .

I AM HAVING A PROBLEM WITH DIGITAL SETS GOING INTO DND BY THEMSELVES THIS IS ON AN SX200EL SYSTEM RUNNING Q29 LW19 SOFTWARE , THE ACCESS CODE FOR DND IS *10 SO DIFFICULT FOR THE END USERS TO MISDIAL THE CODE.HAS ANYONE HEARD OF THIS I REPORTED THE PROBLEM TO,MITEL TECH SUPPORT BUT THEY HAVE NOT HEARD OF THE PROBLEM.