Mitel Forums - The Unofficial Source
Mitel Forums => Mitel MiVoice Business/MCD/3300 => Topic started by: pakman on November 16, 2016, 11:31:05 AM
-
I had a 3-5 minute outage where if you called any DID's an one particular site you would get a busy signal. However, from that site I could make an outbound call. I wasn't able to call internally from the affected site to another location. I don't know if I could of made internal calls on the site that was affected as the issue cleared itself up rather quickly. My first instinct was that the circuit was over utilized but checking netflow it wasn't. Even in the 3300 logs there wasn't much but only these 3 logs that occurred in and around the time of the outage. Side note...I was on a conference call during the outage and we didn't lose anyone on those calls already in place.
any thoughts on how else to track down why this happened would be appreciated.
thanks,
9:59
CCC_Ipsw
Description CompleteFsmRequest: MID:9af80c11 CID: 6f81e5c PCC[ 0x6F81E5C ]:Tx[ IP_TRUNK, PortId:2724, CompId:2, DN:IPTrk ] Rx[ IP_PHONE, PortId=703, CompId=1, DN:1337 ] completed in [ 10110 ] msec in state [ RX_CLOSED ] with a failure [ FSM_RX_CLOSE_TIMEDOUT ]
Module Main
File Name and Line Number IPSwSP_fsm.cpp;5377
10:16
Heartbeat Server
Description ICP has lost contact with (10.161.80.106 (08-00-0F-A0-58-D6)), network driver cluster pool free: 6104 and low water mark: 5621
Module Main
File Name and Line Number HeartbeatRecvTimeoutHandler.cpp;277
10:20
Call Control - Software
Description DAM audit recovered trk swid 5 at cab = 2 shelf = 1 slot = 1 circ = 9 in transient state 5 for too long owned by process hex 00 application 0
Module Main
File Name and Line Number log_outputs_util_en.c;1227
-
The site has no alarms either.
-
It's not uncommon for a carrier to have a temporary issue like that. I've seen it many times where some inbound DID ranges would fail and then start working by some PFM.
Doubtful if they'd own up to it unless it was still happening when you reported it.
Ralph