Bug #2765

umts auth timed out on a 2G network.

Added by lynxis 7 months ago. Updated 7 months ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:


The UMTS is timing out when using UMTS auth over an 2G network.

<001e> vlr.c:1070 VLR_Authenticate(901700000021082)[0x5555558fcbf0]{VLR_SUB_AS_WAIT_RESP}: Received Event VLR_AUTH_E_MS_AUTH_RESP
<001e> vlr_auth_fsm.c:142 SUBSCR(IMSI:901700000021082) received res: b1 40 fc 94 0f c1 47 dd 
<001e> vlr_auth_fsm.c:179 SUBSCR(IMSI:901700000021082) AUTH established UMTS security context
<001e> vlr_auth_fsm.c:231 VLR_Authenticate(901700000021082)[0x5555558fcbf0]{VLR_SUB_AS_WAIT_RESP}: Authentication terminating with result VLR_AUTH_RES_PASSED
<001e> vlr_auth_fsm.c:235 VLR_Authenticate(901700000021082)[0x5555558fcbf0]{VLR_SUB_AS_WAIT_RESP}: state_chg to VLR_SUB_AS_AUTHENTICATED
<001e> vlr_auth_fsm.c:240 VLR_Authenticate(901700000021082)[0x5555558fcbf0]{VLR_SUB_AS_AUTHENTICATED}: Terminating (cause = OSMO_FSM_TERM_REGULAR)
<001e> vlr_auth_fsm.c:240 VLR_Authenticate(901700000021082)[0x5555558fcbf0]{VLR_SUB_AS_AUTHENTICATED}: Removing from parent vlr_lu_fsm(901700000021082)[0x5555558fc470]
<001e> vlr_auth_fsm.c:240 VLR_Authenticate(901700000021082)[0x5555558fcbf0]{VLR_SUB_AS_AUTHENTICATED}: Freeing instance
<001e> fsm.c:287 VLR_Authenticate(901700000021082)[0x5555558fcbf0]{VLR_SUB_AS_AUTHENTICATED}: Deallocated
<001e> vlr_auth_fsm.c:240 vlr_lu_fsm(901700000021082)[0x5555558fc470]{VLR_ULA_S_WAIT_AUTH}: Received Event VLR_ULA_E_AUTH_RES
<001e> vlr_lu_fsm.c:820 vlr_lu_fsm(901700000021082)[0x5555558fc470]{VLR_ULA_S_WAIT_AUTH}: vlr_loc_upd_post_auth()
<001e> vlr_lu_fsm.c:838 vlr_lu_fsm(901700000021082)[0x5555558fc470]{VLR_ULA_S_WAIT_AUTH}: state_chg to VLR_ULA_S_WAIT_CIPH
<001e> vlr_lu_fsm.c:1445 vlr_lu_fsm(901700000021082)[0x5555558fc470]{VLR_ULA_S_WAIT_CIPH}: Connection timed out

Breakpoint 1, gsm0408_loc_upd_rej (conn=0x5555558fc030, cause=22 '\026') at gsm_04_08.c:166
166        return gsm48_conn_sendmsg(msg, conn, NULL);
(gdb) bt
#0  gsm0408_loc_upd_rej (conn=0x5555558fc030, cause=22 '\026') at gsm_04_08.c:166
#1  0x0000555555582e39 in msc_vlr_tx_lu_rej (msc_conn_ref=0x5555558fc030, cause=22 '\026') at gsm_04_08.c:3334
#2  0x000055555559fac7 in lu_fsm_failure (fi=0x5555558fc470, rej_cause=22 '\026') at vlr_lu_fsm.c:718
#3  0x00005555555a1d65 in vlr_loc_update_conn_timeout (fi=0x5555558fc470) at vlr_lu_fsm.c:1446
#4  0x000055555559ae6a in vlr_subscr_conn_timeout (vsub=0x5555558fc7a0) at vlr.c:978
#5  0x0000555555590c98 in subscr_conn_fsm_timeout (fi=0x5555558fc220) at subscr_conn.c:235
#6  0x00007ffff73393c5 in fsm_tmr_cb (data=0x5555558fc220) at fsm.c:185
#7  0x00007ffff73351e6 in osmo_timers_update () at timer.c:257
#8  0x00007ffff73357e6 in osmo_select_main (polling=<optimized out>) at select.c:253
#9  0x00005555555736eb in main (argc=3, argv=0x7fffffffeb98) at msc_main.c:552

Related issues

Is duplicate of OsmoMSC - Bug #2745: UMTS ciphering on GSM does not work when both 2G and 3G keys are present in the HLR.Resolved2017-12-13


#1 Updated by lynxis 7 months ago

  • Related to Bug #2745: UMTS ciphering on GSM does not work when both 2G and 3G keys are present in the HLR. added

#2 Updated by lynxis 7 months ago

  • Status changed from New to Rejected

#3 Updated by neels 7 months ago

  • Related to deleted (Bug #2745: UMTS ciphering on GSM does not work when both 2G and 3G keys are present in the HLR.)

#4 Updated by neels 7 months ago

  • Is duplicate of Bug #2745: UMTS ciphering on GSM does not work when both 2G and 3G keys are present in the HLR. added

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)