No, it’s not U2L.
L2U is issue after LTE release finish.
Is it L2U (LTE to 3G)?
UtranNCell
Ok this issue had faced, please carefully check colocated L2U are defined.
Nope, it’s for 3G to LTE.
LST UTRANNCELL
Check at LTE end.
But why when we connect force 3G it is going to no service mode?
Forcefully mean Lock to 3G?
Also check this issue in MO or MT case.
Yes, Lock to 3G in both case.
Check cause of attach reject when locked in 3G.
Put a snapshot here what layer 3 messages after rach success in 3G.
In that cell all 3G there are 3 carriers other 2 carriers if working fine delete that utranncell of that carrier and try to make csfb with other two carriers.
If coverage is there.
No suitable cell in location area.
Your cell is not defined for voice services in core.
2 Likes
Yes exactly.
But RRC SR KPI is fine in 3g as per him.
RRC is always OK.
There are NAS problems…
Ok, but he can try with other two carriers in csfb, and delete that carrier utranncell.
But it should be in entire site.
How come one cell of site?
Yeah it’s strange.
Delete that cell utranncell and try with other two carriers which are getting connected.
Check the cell’s definition in Core.
Yeah, seems to be issue at higher entity.
Maybe there is an issue in the cell definition in Core or wrong CID mapping between RAN and Core.