eCSFB + Voice Failures

Troubleshooting steps for eCSFB

 Check alarms for 3G,4G and D1 sites

 Check forms, reference cell ID, nbr Settings on eCSFB

 If the issue is related to TRIMBLE GPS then reset the site (Fix is with LR14.3 CL3)

 Check if the Clearwire (D1) site has right reference cell number

 Also check if D1 sites points to CDMA cell which is either in growth state or legacy.
Recommendation is to remove those cells from D1 NL
eCSFB
 sync tool updates 3G Nbr List and match with SAM NL (Top 20)
 eFEMTO scripts changed for 5++ Cell IDs to 2499+ (Completed)
 Provisioning on SAM: Two reference IDs defined for the sector ; 0 to F1 and 1 to F16
* if 800 is G or Non Commercial than point to F2

©2015 Sprint. This information is subject to Sprint policies regarding use and
is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended
recipient. Any review, use, distribution or disclosure is prohibited without
authorization.
eCSFB Issues
1. Implicit Detach on MME
UE network location is unknown – UE has been detached from LTE network implicitly, and is not
registered via 1X. When a UE has expired its attached state timers, in the MME or PGW, due to
inactivity, the UE is implicitly detached. Once detached, all the incoming calls go to voice mail until
the subscriber makes an outgoing call which results in reattach. Implicit detach is done without
notifying the UE, so subscriber is not aware of its detached status.
Sprint is deploying MME Explicit Detach feature nationwide by 10/16. Explicit Detach is done with
notification to the UE. When an Explicit Detach occurs, options can be set for the UE to reattach.
Alert 15−1123 published 9/30

2. AR 1-5924609 MME does not respond to Extended Service Request

Occurs due to higher UE detected Radio Link Failure associated with iPhone6s. iPhone 6S generating
double S1 TAU causing MME to reject eCSFB and thus directing the call to VM. Fix is on target for
MME load WM900M3 (planned for nationwide deployment). Performance improved after new iPhone
6S/6S+ software release.

3. eNB Timing issue causing high eCSFB failure and calls going to VM (UE unable to
locate correct 1X cell due to timing issue):
AR 1-5768273 Trimble GPS “time shift” issue in alert 15-1050. Fixed in TDD and FDD 14.3 CL3. Seen in
multiple markets
Non-Trimble GPS time drift issue on TDD sites. Fix in TDD 14.3 CL3 load

©2015 Sprint. This information is subject to Sprint policies regarding use and
is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended
recipient. Any review, use, distribution or disclosure is prohibited without
authorization.
Steps to check GPS
Commands to check GPS
> /pltf/pltf/grip/getInventory
INTERNAL Receiver: GPS inventory:

COPYRIGHT 2008 Trimble Navigation Ltd.

SFTW P/N # 0000
SOFTWARE VER # 2.22.0
SOFTWARE REV # 00
SOFTWARE DATE 01/17/2013
MODEL # 3018
HDWR P/N # 0000
SERIAL # 1532031623
MANUFACTUR DATE 01/01/2014
OPTIONS LIST 0000
▒
• Verify state at OMP
OMP TICLI 49> op:a21serv 2,status

©2015 Sprint. This information is subject to Sprint policies regarding use and
is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended
recipient. Any review, use, distribution or disclosure is prohibited without
authorization.
Forms to check for eSCFB

©2015 Sprint. This information is subject to Sprint policies regarding use and
is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended
recipient. Any review, use, distribution or disclosure is prohibited without
authorization.
Forms to check for eSCFB

Below Param is on SAM

©2015 Sprint. This information is subject to Sprint policies regarding use and
is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended
recipient. Any review, use, distribution or disclosure is prohibited without
authorization.
KPIs to check for voice failures

 Check Resource Blocking, Power Blocking, RF Blocking, Check

TCCFs

 To solve AF from RF side

• Check power is balanced on each carrier
• NL is updated
• Check settings on SW (active set)
• Check Settings on SW (Nbr Set)
• Optimize DBOT
• Optimize Paging Channel = 72
• Work on TCCFs: For instance if you see low fwd link power usage , you can
inc paging channel power
• If cross carrier assignments are high optimize with RF loading factor

©2015 Sprint. This information is subject to Sprint policies regarding use and
is the property of Sprint and/or its relevant affiliates and may contain restricted,
confidential or privileged materials intended for the sole use of the intended
recipient. Any review, use, distribution or disclosure is prohibited without
authorization.