Mitel Forums > Mitel MiVoice Business/MCD/3300
5330 Phone Reset When Answering a Call
swilson:
Have a user who went to answer and call and when he hit the line his phone reset. I have the two resulting log entries below. Can anyone translate this into English for me please?
Software 1003 Warning 2008/Dec/15 15:25:27 CCC_Ipsw CompleteFsmRequest: MID:9a28d2de CID: 66a1630 PCC[ 0x66A1630 ]:Tx[ IP_TRUNK, PortId:3922, CompId:2, DN:IPTrk ] Rx[ IP_PHONE, PortId=3645, CompId=1, DN:1997 ]completed in [ 10000 ] msec in state [ RX_CLOSED ] with a failure [ FSM_RX_CLOSE_TIMEDOUT ] Main IPSwSP_fsm.cpp;5500
Software 1002 Warning 2008/Dec/15 15:25:27 CCC_Ipsw CompleteFsmRequest: MID:aa28d2dd CID: 628d62f PCC[ 0x628D62F ]:Tx[ IP_PHONE, PortId:3645, CompId:1, DN:1997 ] Rx[ IP_TRUNK, PortId=3922, CompId=2, DN:IPTrk ]completed in [ 10000 ] msec in state [ STREAM_CLOSED ] with a failure [ FSM_TX_CLOSE_TIMEDOUT ] Main IPSwSP_fsm.cpp;5500
chadmaynard:
Those are just messages about the stream sockets closing without the protocol closing the connection cleanly. There are two because a socket is created for each endpoint of the call. The constant FSM_TX_CLOSE_TIMEDOUT tells you that the connection was manually closed because it timed out. It timed out because your IP phone restarted.
In other words, these error messages are the result of your 5330 restarting. The 5330 didn't restart because of these errors, and the errors don't tell you anything about why the phone restarted.
Are you using 802.3af PoE ? It could be that your device is under-powered or that you simply have a bad phone set.
mle724:
I have 5 different locations with the Mitel 3300 ICP and 5000 series phones. In two of the locations, I have about a dozen phones combined that get a Fatal Exception Error on the display and then reboot. It has happened on 5212, 5330 and 5340 model phones. It usually happens when calls are placed between the two locations across our network. On some occasions, it will happen to the call initiator and the recipient at the same time. But only with these two locations. I've seen it happen once on an inbound call.
Service Provider and Mitel have not been able to resolve it thus far. Any help would be greatly appreciated.
Thanks
Chakara:
It is interesting that people see the issue - implies the phone is being actively used. I'd be curious as to what happens if you switch the phones with someone who is not having the issue. I'd ask both users to report back and see what you get....
-Chak
chadmaynard:
What exception is being thrown?
Look in the phone Diagnostics menu for the Last Assert/Except. Scroll through and write down everything and post it here. Are you running any applications on the 53xx phones?
Navigation
[0] Message Index
[#] Next page
Go to full version