No Suitable Cells In Tracking Area Code In The

Does this always happen when you switch to Flight mode and try to connect again Whenever this happens, I always wonder if the UE cannot connect.

Therefore, we need to know in what circumstances the MME deleted ENB-UE-S1AP-ID(65) before that.

Ive tried to reproduce with eNB restart, S1-Reset message, etc, but it didnt reproduce.

However, in order to find the underlying problem, we need to know the situation before packet 42 and packet 43.

If you provide additional logs and pcaps, I will do my best to find out the cause.

Zip renamed 1028 01.z011028 01 02.

Zip renamed 1028 01.z021028 01 03.

Zip renamed 1028 01.z031028 01 04.

Zip renamed 1028 01.z04, and then unzip.

This problem can occur if MME is received S1-reset or eNB is restarted.

Before it appears, there are downlinknastranport, service reject (UE identity cannot be derived by the network) pcap: 11030105.zip 11030104.zip 11030102.zip 110301.zip 11030101.zip 11030103.zip.

Zip renamed 1103 01.z011103 01 02.

Zip renamed 1103 01.z021103 01 03.

Zip renamed 1103 01.z04, 1103 01 05 Zip renamed 1103 01.z05, and then unzip.

No Suitable Cells In Tracking Area Code In The

So Ive added the exception handling code in the master branch.

You can either use the current commit (v2.0.20-11-g9a1824f) or use a new version(v2.0.21) from the main branch.

If S1-reset occurred, I can know if VoLTE works well in IDLE state, but I cant see VoLTE IDLE state with S1-reset.

And let me know if you run into any problems while using it.

Src IP: 127.0.0.1 Src Port: 3871 Dst IP: 192.168.4.123 Dst Port: 47978.