Mute Call Root Analysis Doc - James
Mute Call Root Analysis Doc - James
STEP1:
STEP 2:
MML Command: COL LOG: LOGTYPE=PFM_RESULT-0&HOST_PFM_RESULT-0&ACTIVE_DEF_MEAS_FILE-0&STANDBY_DEF_MEAS_FILE-0&PFM_SWITCHS-0&PFM_NOM_RESULT-
0&HISTORY_ALARM-0&HISTORY_FAULT-0&ALM_SYSTEM_CFG-0&OPT_LOG-0&OMU_LOG-0&OMU_SIM_LOG-0&OS_LOG-0&BSC_CFG_MML-0&BSC_DYNAMIC_CFG_INFO-0&BSC_SERIES_NO-
0&DB_BAK-0&CELL_BASIC_INFO-0&RESERVED_PARA_INFO-0&BTS_BASIC_INFO-0&BTS_CHECK_LOG-0&BTS_DEBUG_LOG-0&BTS_CHR_LOG-0&TRX_LOG-0&BTS_NET_TABLE-
0&TRANSIPROUTE_LOG-0&GBTSSTARTUP_LOG-0&SDBG_LOG-0&DEBUG_LOG-0&LAST_WORD-0&DSP_DEBUG_LOG-0&AITFRESMSG_LOG-0&HOST_LOG-0&2G_CHR_LOG-1&CHR_LOG-
0&2G_UNILATERAL_CONNECT-0&BSC_INFO-0&GCSR_LOG-0&GPSR_LOG-0&AIDG_LOG-0&BIOS_LOG-0&CALLFAULT_LOG-0&PCHR_LOG-0&SYSFAULT_LOG-0;
STEP 3:
STEP 5
STEP 6:
TOOL:
OUTPUT RESULT:
CHECK alarm on Site(s) with highest count of Failures and escalate accordingly.
From above chart> Site 47 with 1015 failures from 400 failures and above are always suspected to have
alarms // faulty link and should be escalated.
ALARM:
TT SHOULD BE RAISED AFTERWARDS AND ESCALATED STATING THE IMPACT AS SILENT CALLS OR MUTE
CALLS >>>> Confirming resolution >>> Record of Mute call on site should = reduce below 100 or
non-existence