Send supported and current RAT type in GSUP to OsmoHLR
Particularly the CURRENT_RAT_TYPE is what tells OsmoHLR to provide tuples with AMF separation bit for EUTRAN, and not foe GERAN/UTRAN.changes/06/16906/1
parent
6f5290846f
commit
388d387dcc
|
@ -180,7 +180,8 @@ handle_request(#diameter_packet{msg = Req, errors = []}, _SvcName, {_, Caps}) wh
|
|||
NumUgran = req_num_of_vec(ReqUG),
|
||||
lager:info("Num EUTRAN=~p, UTRAN=~p~n", [NumEutran, NumUgran]),
|
||||
% construct GSUP request to HLR and transceive it
|
||||
GsupTx1 = #{message_type => send_auth_info_req, imsi => list_to_binary(UserName)},
|
||||
GsupTx1 = #{message_type => send_auth_info_req, imsi => list_to_binary(UserName),
|
||||
supported_rat_types => [rat_eutran_sgs], current_rat_type => rat_eutran_sgs},
|
||||
case ReqEU of
|
||||
#'Requested-EUTRAN-Authentication-Info'{'Re-Synchronization-Info' = ReSyncInfo}
|
||||
when is_binary(ReSyncInfo) ->
|
||||
|
|
Loading…
Reference in New Issue