Hi Friends,
Can anyone tell me the proper reason of this drop?
All sectors have call drops.
Only change done for power saving.
Hi Friends,
Can anyone tell me the proper reason of this drop?
All sectors have call drops.
Only change done for power saving.
It is hard to understand exactly.
What about other KPIs?
SW upgrades?
Transport issues?
No SW update, No Transport issue.
No alarm, no physical activity on serving and neighbours.
Can you please list here exactly what you have changed?
Load based power saving duration 660 to 480.
Look for all HO KPI, counters and failure reasons.
So you turn off one carrier for power saving and users go to mobility layer?
If that is, look for CM configuration for the HO.
Due to Power saving may handover SR is changes , compare with HO KPIs and if it is match , go to change some mobility settings between neighs which are defined for QCI1 ( for example for Huawei we have group 0 and group 1 etc ).
An increase in this counter usually indicates that there are requests to release the bearer that supports voice calls. When these requests result in a drop call, it suggests issues with maintaining the VoLTE call session
Poor signal quality possible to impact mobility relation and may interference situation changed related fields. So interference and dominance and proper serving cells state possible to changes. All these reason can impact the epc_eps_bear_rel_req_r_qci1.
If you couldn’t match with mobility KPIs with epc_eps_bear_rel_req_r_qci1. Than you can confuse about TNL or Core.