APPSL - ATA .....?

[JMarine0811]

I attached a screen capture. This one is new for me. Mitel 3300 MXeIII v. 13.0.1.28

I was told that this just started happening around 0700 this morning. Page 198 and 199 shows...


2381 2016/Jan/26 07:58:21 SAC SacSendCallInfoChange->msgQSend CALL_INFO_CHANGE FAILED for DevIndex 161 SacCallInfo.cpp;133
2380 2016/Jan/26 07:58:21 APPSL - ATA AtaCallLogger::submitCallLogs->Call to msgQSend failed. ERRNO = 0x3d0002 AtaCallLogger.cpp;1053
2379 2016/Jan/26 07:58:21 SAC SacSendCallInfoChange->msgQSend CALL_INFO_CHANGE FAILED for DevIndex 179 SacCallInfo.cpp;133
2378 2016/Jan/26 07:58:16 APPSL - ATA AtaCallLogger::submitCallLogs->Call to msgQSend failed. ERRNO = 0x3d0002 AtaCallLogger.cpp;1053
2377 2016/Jan/26 07:58:16 SAC SacSendCallInfoChange->msgQSend CALL_INFO_CHANGE FAILED for DevIndex 333 SacCallInfo.cpp;133
2376 2016/Jan/26 07:58:11 APPSL - ATA AtaCallLogger::submitCallLogs->Call to msgQSend failed. ERRNO = 0x3d0002 AtaCallLogger.cpp;1053
2375 2016/Jan/26 07:58:11 SAC SacSendCallInfoChange->msgQSend CALL_INFO_CHANGE FAILED for DevIndex 341 SacCallInfo.cpp;133
2374 2016/Jan/26 07:58:11 APPSL - ATA AtaCallLogger::submitCallLogs->Call to msgQSend failed. ERRNO = 0x3d0002 AtaCallLogger.cpp;1053
2373 2016/Jan/26 07:58:11 SAC SacSendCallInfoChange->msgQSend CALL_INFO_CHANGE FAILED for DevIndex 227 SacCallInfo.cpp;133
2372 2016/Jan/26 07:58:06 SAC SacSendCallInfoChange->msgQSend CALL_INFO_CHANGE FAILED for DevIndex 179 SacCallInfo.cpp;133
2371 2016/Jan/26 07:58:06 SAC SacSendCallInfoChange->msgQSend CALL_INFO_CHANGE FAILED for DevIndex 161 SacCallInfo.cpp;133
2370 2016/Jan/26 07:58:06 APPSL - ATA AtaCallLogger::submitCallLogs->Call to msgQSend failed. ERRNO = 0x3d0002 AtaCallLogger.cpp;1053
2369 2016/Jan/26 07:58:06 SAC SacSendCallInfoChange->msgQSend CALL_INFO_CHANGE FAILED for DevIndex 214 SacCallInfo.cpp;133
2368 2016/Jan/26 07:58:05 SAC SacSendCallInfoChange->msgQSend CALL_INFO_CHANGE FAILED for DevIndex 227 SacCallInfo.cpp;133
2367 2016/Jan/26 07:58:05 SAC SacSendCallInfoChange->msgQSend CALL_INFO_CHANGE FAILED for DevIndex 341 SacCallInfo.cpp;133
2366 2016/Jan/26 07:58:04 SAC SacSendCallInfoChange->msgQSend CALL_INFO_CHANGE FAILED for DevIndex 214 SacCallInfo.cpp;133
2365 2016/Jan/26 07:58:04 APPSL - ATA AtaCallLogger::submitCallLogs->Call to msgQSend failed. ERRNO = 0x3d0002 AtaCallLogger.cpp;1053
2364 2016/Jan/26 07:58:04 SAC SacSendCallInfoChange->msgQSend CALL_INFO_CHANGE FAILED for DevIndex 102 SacCallInfo.cpp;133
2363 2016/Jan/26 07:58:00 SAC SacSendCallInfoChange->msgQSend CALL_INFO_CHANGE FAILED for DevIndex 333 SacCallInfo.cpp;133
2362 2016/Jan/26 07:58:00 SAC SacSendCallInfoChange->msgQSend CALL_INFO_CHANGE FAILED for DevIndex 179 SacCallInfo.cpp;133
2361 2016/Jan/26 07:58:00 SAC SacSendCallInfoChange->msgQSend CALL_INFO_CHANGE FAILED for DevIndex 161 SacCallInfo.cpp;133
2360 2016/Jan/26 07:57:58 SAC SacSendCallInfoChange->msgQSend CALL_INFO_CHANGE FAILED for DevIndex 179 SacCallInfo.cpp;133
2359 2016/Jan/26 07:57:57 SAC SacSendCallInfoChange->msgQSend CALL_INFO_CHANGE FAILED for DevIndex 227 SacCallInfo.cpp;133
2358 2016/Jan/26 07:57:51 APPSL - ATA AtaCallLogger::submitCallLogs->Call to msgQSend failed. ERRNO = 0x3d0002 AtaCallLogger.cpp;1053
2357 2016/Jan/26 07:57:51 SAC SacSendCallInfoChange->msgQSend CALL_INFO_CHANGE FAILED for DevIndex 43 SacCallInfo.cpp;133
2356 2016/Jan/26 07:57:49 SAC SacSendCallInfoChange->msgQSend CALL_INFO_CHANGE FAILED for DevIndex 214 SacCallInfo.cpp;133
2355 2016/Jan/26 07:57:49 SAC SacSendCallInfoChange->msgQSend CALL_INFO_CHANGE FAILED for DevIndex 102 SacCallInfo.cpp;133
2354 2016/Jan/26 07:57:49 SAC SacSendCallInfoChange->msgQSend CALL_INFO_CHANGE FAILED for DevIndex 43 SacCallInfo.cpp;133
2353 2016/Jan/26 07:57:49 APPSL - ATA AtaCallLogger::submitCallLogs->Call to msgQSend failed. ERRNO = 0x3d0002 AtaCallLogger.cpp;1053
2352 2016/Jan/26 07:57:49 SAC SacSendCallInfoChange->msgQSend CALL_INFO_CHANGE FAILED for DevIndex 8 SacCallInfo.cpp;133
2351 2016/Jan/26 07:57:44 SAC SacSendCallInfoChange->msgQSend CALL_INFO_CHANGE FAILED for DevIndex 214 SacCallInfo.cpp;133
2350 2016/Jan/26 07:57:44 SAC SacSendCallInfoChange->msgQSend CALL_INFO_CHANGE FAILED for DevIndex 102 SacCallInfo.cpp;133
2349 2016/Jan/26 07:57:42 SAC SacSendCallInfoChange->msgQSend CALL_INFO_CHANGE FAILED for DevIndex 193 SacCallInfo.cpp;133

... and that's the furthest back it goes.

Everything is working, no alarms, all clear "everything green". 3 reports of 3 extensions stuck at "Loading Apps". They claim "Phone went dark, came back up and stuck there ever since."

I am thinking of coming in early in the A.M. and reboot the system to see if that clears it up. Any other suggestions??

Thanks in advance

 

[JMarine0811]

In addition... Those extensions that reported "Stuck at Applications Loading" do work. They receive calls, make calls etc. Just the screen seems to be stuck at Apps Loading. They have been unplugged and plugged back in. With the first report of this happening, I blew away one of the extensions that had 2 users... one no longer needed. I set it up again from scratch, had my runner do the ###<ext>hold and it came back up but stuck at Apps Loading. Time does not sync. However, the phone is completely operable.

 

[kwbMitel]

Is the TFTP source the same as the RTC?

If these phones are 53xx they will come up without a TFTP source and boot from an internal stored file.

**********************************************
What's most important is that you realise ... There is no spoon.

 

[JMarine0811]

Yes the source is the same.

These are 5330's, sorry should have given that info. Here we have 5330's 5340's a few 5360's.

This all started happening today. All those errors. No other reports, All phones are running great. No other screens/phones are showing the App loading screen. As if everything is completely normal... that is until I look at these Software Warning logs. If you notice the info given at 1512 ext 2088. I called him, all is working perfect and his screen is "normal".

This is a strange one, I'm thinking I might be in for an early morning to watch a reboot. Unless there is anything else anyone can think of to fix this to avoid that.


2956 2016/Jan/26 15:15:08 APPSL - ATA AtaCallLogger::submitCallLogs->Call to msgQSend failed. ERRNO = 0x3d0002 AtaCallLogger.cpp;1053
2955 2016/Jan/26 15:14:58 APPSL - ATA AtaCallLogger::submitCallLogs->Call to msgQSend failed. ERRNO = 0x3d0002 AtaCallLogger.cpp;1053
2954 2016/Jan/26 15:14:25 APPSL - ATA AtaCallLogger::submitCallLogs->Call to msgQSend failed. ERRNO = 0x3d0002 AtaCallLogger.cpp;1053
2953 2016/Jan/26 15:14:07 APPSL - ATA AtaCallLogger::submitCallLogs->Call to msgQSend failed. ERRNO = 0x3d0002 AtaCallLogger.cpp;1053
2952 2016/Jan/26 15:13:43 APPSL - ATA AtaCallLogger::submitCallLogs->Call to msgQSend failed. ERRNO = 0x3d0002 AtaCallLogger.cpp;1053
2951 2016/Jan/26 15:13:35 APPSL - ATA AtaCallLogger::submitCallLogs->Call to msgQSend failed. ERRNO = 0x3d0002 AtaCallLogger.cpp;1053
2950 2016/Jan/26 15:13:25 APPSL - ATA AtaCallLogger::submitCallLogs->Call to msgQSend failed. ERRNO = 0x3d0002 AtaCallLogger.cpp;1053
2949 2016/Jan/26 15:13:04 APPSL - ATA AtaCallLogger::submitCallLogs->Call to msgQSend failed. ERRNO = 0x3d0002 AtaCallLogger.cpp;1053
2948 2016/Jan/26 15:13:03 APPSL - ATA AtaCallLogger::submitCallLogs->Call to msgQSend failed. ERRNO = 0x3d0002 AtaCallLogger.cpp;1053
2947 2016/Jan/26 15:12:59 APPSL - ATA AtaCallLogger::submitCallLogs->Call to msgQSend failed. ERRNO = 0x3d0002 AtaCallLogger.cpp;1053
2946 2016/Jan/26 15:12:45 APPSL - ATA AtaCallLogger::submitCallLogs->Call to msgQSend failed. ERRNO = 0x3d0002 AtaCallLogger.cpp;1053
2945 2016/Jan/26 15:12:43 APPSL - ATA AtaCallLogger::submitCallLogs->Call to msgQSend failed. ERRNO = 0x3d0002 AtaCallLogger.cpp;1053
2944 2016/Jan/26 15:12:35 APPSL - ATA AtaCallLogger::submitCallLogs->Call to msgQSend failed. ERRNO = 0x3d0002 AtaCallLogger.cpp;1053
2943 2016/Jan/26 15:12:30 APPSL - ATA AtaCallLogger::submitCallLogs->Call to msgQSend failed. ERRNO = 0x3d0002 AtaCallLogger.cpp;1053
2942 2016/Jan/26 15:12:29 APPSL - ATA AtaCallLogger::submitCallLogs->Call to msgQSend failed. ERRNO = 0x3d0002 AtaCallLogger.cpp;1053
2941 2016/Jan/26 15:12:28 APPSL - ATA AtaEventManager::triggerDeviceStateEvent-> Call to msgQSend has failed 4801 times. ERRNO = 0x3d0002 ERRNOTask = 0x3d0002 for DN '2088' AtaEventManager.cpp;1105
2940 2016/Jan/26 15:12:28 APPSL - ATA AtaCallLogger::submitCallLogs->Call to msgQSend failed. ERRNO = 0x3d0002 AtaCallLogger.cpp;1053
2939 2016/Jan/26 15:12:24 APPSL - ATA AtaCallLogger::submitCallLogs->Call to msgQSend failed. ERRNO = 0x3d0002 AtaCallLogger.cpp;1053
2938 2016/Jan/26 15:12:09 APPSL - ATA AtaCallLogger::submitCallLogs->Call to msgQSend failed. ERRNO = 0x3d0002 AtaCallLogger.cpp;1053
2937 2016/Jan/26 15:12:03 APPSL - ATA AtaCallLogger::submitCallLogs->Call to msgQSend failed. ERRNO = 0x3d0002 AtaCallLogger.cpp;1053
2936 2016/Jan/26 15:11:58 APPSL - ATA AtaCallLogger::submitCallLogs->Call to msgQSend failed. ERRNO = 0x3d0002 AtaCallLogger.cpp;1053
2935 2016/Jan/26 15:11:56 APPSL - ATA AtaCallLogger::submitCallLogs->Call to msgQSend failed. ERRNO = 0x3d0002 AtaCallLogger.cpp;1053
2934 2016/Jan/26 15:11:55 APPSL - ATA AtaCallLogger::submitCallLogs->Call to msgQSend failed. ERRNO = 0x3d0002 AtaCallLogger.cpp;1053
2933 2016/Jan/26 15:11:33 APPSL - ATA AtaCallLogger::submitCallLogs->Call to msgQSend failed. ERRNO = 0x3d0002 AtaCallLogger.cpp;1053
2932 2016/Jan/26 15:11:33 APPSL - ATA AtaCallLogger::submitCallLogs->Call to msgQSend failed. ERRNO = 0x3d0002 AtaCallLogger.cpp;1053

 

[JMarine0811]

Tried HTMLAPPUPGRADE... no go. Going to have to reboot it.

 

[kwbMitel]

my bet is that the TFTP server is not running and that as the DHCP lease expires, the problem is propagating.

**********************************************
What's most important is that you realise ... There is no spoon.

 

[cageycagey]

The SAC process is what is used for delivering config information to the 53xx phones so this would align with the problem you are seeing. A reboot of the controller would provide a quick fix for the problem to restore normal service

Part of the problems have been addressed by a fix that has been included in MiVB7.0_SP1_pr2 (13.0.1..53)

MN00556127 - 53xx Stuck in applications loading SacCallInfo.cpp errors.