MME cannot reach to HSS for 4G call

[nitinbhat]

Hi ,

I am using srsRAN to emulate eNB, UE and open5GS charts. When I try 4G attach, MME throws this error. I wonder if MME is not able to reach HSS. I am using default configuration and I assume MME will try to send it to HSS 'service - open5gs-hss-frdi

I also checked configmap of mme and it seems to pointing out to correct has

ConnectPeer = "hss.localdomain" { ConnectTo = "open5gs-hss-frdi"; TcTimer = 60; TwTimer = 30; No_TLS; Port=3868; };

What could have gone wrong here?

Error I see on MME >

02/02 11:02:00.420: [emm] INFO: [] Attach request (../src/mme/emm-sm.c:364)
02/02 11:02:00.420: [emm] INFO:     IMSI[999700000000001] (../src/mme/emm-handler.c:227)
02/02 11:02:00.421: [diam] ERROR: pid:Routing-OUT (0x557e99b1d880) in md_hook_cb_tree@dbg_msg_dumps.c:112: ROUTING ERROR 'No remaining suitable candidate to route the message to' for:
 ((null):0)
02/02 11:02:00.421: [diam] ERROR: pid:Routing-OUT (0x557e99b1d880) in md_hook_cb_tree@dbg_msg_dumps.c:113:      'Authentication-Information-Request'
 ((null):0)
02/02 11:02:00.421: [diam] ERROR: pid:Routing-OUT (0x557e99b1d880) in md_hook_cb_tree@dbg_msg_dumps.c:113:        Version: 0x01
 ((null):0)
02/02 11:02:00.421: [diam] ERROR: pid:Routing-OUT (0x557e99b1d880) in md_hook_cb_tree@dbg_msg_dumps.c:113:        Length: 20
 ((null):0)
02/02 11:02:00.421: [diam] ERROR: pid:Routing-OUT (0x557e99b1d880) in md_hook_cb_tree@dbg_msg_dumps.c:113:        Flags: 0xC0 (RP--)
 ((null):0)
02/02 11:02:00.421: [diam] ERROR: pid:Routing-OUT (0x557e99b1d880) in md_hook_cb_tree@dbg_msg_dumps.c:113:        Command Code: 318
 ((null):0)
02/02 11:02:00.421: [diam] ERROR: pid:Routing-OUT (0x557e99b1d880) in md_hook_cb_tree@dbg_msg_dumps.c:113:        ApplicationId: 16777251
 ((null):0)
02/02 11:02:00.421: [diam] ERROR: pid:Routing-OUT (0x557e99b1d880) in md_hook_cb_tree@dbg_msg_dumps.c:113:        Hop-by-Hop Identifier: 0x00000000
 ((null):0)
02/02 11:02:00.421: [diam] ERROR: pid:Routing-OUT (0x557e99b1d880) in md_hook_cb_tree@dbg_msg_dumps.c:113:        End-to-End Identifier: 0x8868F3FA
 ((null):0)
02/02 11:02:00.421: [diam] ERROR: pid:Routing-OUT (0x557e99b1d880) in md_hook_cb_tree@dbg_msg_dumps.c:113:         {internal data}: src:(nil)(0) rwb:(nil) rt:0 cb:0x557e999e666e,(nil)(0x7fdd1800c510) qry:(nil) asso:0 sess:0x7fdd1800cca0
 ((null):0)
02/02 11:02:00.421: [diam] ERROR: pid:Routing-OUT (0x557e99b1d880) in md_hook_cb_tree@dbg_msg_dumps.c:113:         AVP: 'Session-Id'(263) l=8 f=-M val="mme.localdomain;1706854534;6;app_s6a"
 ((null):0)
02/02 11:02:00.421: [diam] ERROR: pid:Routing-OUT (0x557e99b1d880) in md_hook_cb_tree@dbg_msg_dumps.c:113:         AVP: 'Auth-Session-State'(277) l=12 f=-M val='NO_STATE_MAINTAINED' (1 (0x1))
 ((null):0)
02/02 11:02:00.421: [diam] ERROR: pid:Routing-OUT (0x557e99b1d880) in md_hook_cb_tree@dbg_msg_dumps.c:113:         AVP: 'Origin-Host'(264) l=8 f=-M val="mme.localdomain"
 ((null):0)
02/02 11:02:00.421: [diam] ERROR: pid:Routing-OUT (0x557e99b1d880) in md_hook_cb_tree@dbg_msg_dumps.c:113:         AVP: 'Origin-Realm'(296) l=8 f=-M val="localdomain"
 ((null):0)
02/02 11:02:00.421: [diam] ERROR: pid:Routing-OUT (0x557e99b1d880) in md_hook_cb_tree@dbg_msg_dumps.c:113:         AVP: 'Destination-Realm'(283) l=8 f=-M val="localdomain"
 ((null):0)
02/02 11:02:00.421: [diam] ERROR: pid:Routing-OUT (0x557e99b1d880) in md_hook_cb_tree@dbg_msg_dumps.c:113:         AVP: 'User-Name'(1) l=8 f=-M val="999700000000001"
 ((null):0)
02/02 11:02:00.421: [diam] ERROR: pid:Routing-OUT (0x557e99b1d880) in md_hook_cb_tree@dbg_msg_dumps.c:113:         AVP: 'Requested-EUTRAN-Authentication-Info'(1408) vend='3GPP'(10415) l=12 f=VM val=(grouped)
 ((null):0)
02/02 11:02:00.421: [diam] ERROR: pid:Routing-OUT (0x557e99b1d880) in md_hook_cb_tree@dbg_msg_dumps.c:113:            AVP: 'Number-Of-Requested-Vectors'(1410) vend='3GPP'(10415) l=16 f=VM val=1 (0x1)
 ((null):0)
02/02 11:02:00.421: [diam] ERROR: pid:Routing-OUT (0x557e99b1d880) in md_hook_cb_tree@dbg_msg_dumps.c:113:            AVP: 'Immediate-Response-Preferred'(1412) vend='3GPP'(10415) l=16 f=VM val=1 (0x1)
 ((null):0)
02/02 11:02:00.421: [diam] ERROR: pid:Routing-OUT (0x557e99b1d880) in md_hook_cb_tree@dbg_msg_dumps.c:113:         AVP: 'Visited-PLMN-Id'(1407) vend='3GPP'(10415) l=12 f=VM val=<99 F9 07>
 ((null):0)
02/02 11:02:00.421: [diam] ERROR: pid:Routing-OUT (0x557e99b1d880) in md_hook_cb_tree@dbg_msg_dumps.c:113:         AVP: 'Vendor-Specific-Application-Id'(260) l=8 f=-M val=(grouped)
 ((null):0)
02/02 11:02:00.421: [diam] ERROR: pid:Routing-OUT (0x557e99b1d880) in md_hook_cb_tree@dbg_msg_dumps.c:113:            AVP: 'Vendor-Id'(266) l=12 f=-M val=10415 (0x28af)
 ((null):0)
02/02 11:02:00.421: [diam] ERROR: pid:Routing-OUT (0x557e99b1d880) in md_hook_cb_tree@dbg_msg_dumps.c:113:            AVP: 'Auth-Application-Id'(258) l=12 f=-M val=16777251 (0x1000023)
 ((null):0)
02/02 11:02:00.421: [mme] INFO:     Result Code: 3002 (../src/mme/mme-fd-path.c:938)
02/02 11:02:00.421: [mme] WARNING: Authentication Information failed [3002] (../src/mme/mme-s6a-handler.c:54)
02/02 11:02:00.421: [mme] INFO: [999700000000001] Attach reject [OGS_NAS_EMM_CAUSE:15] (../src/mme/mme-sm.c:413)
02/02 11:02:00.622: [mme] INFO: UE Context Release [Action:3] (../src/mme/s1ap-handler.c:1526)
02/02 11:02:00.623: [mme] INFO:     ENB_UE_S1AP_ID[5] MME_UE_S1AP_ID[7] (../src/mme/s1ap-handler.c:1527)
02/02 11:02:00.623: [mme] INFO:     IMSI[999700000000001] (../src/mme/s1ap-handler.c:1530)
02/02 11:02:00.623: [mme] INFO: [Removed] Number of eNB-UEs is now 0 (../src/mme/mme-context.c:4042)
02/02 11:02:00.623: [mme] INFO: [Removed] Number of MME-UEs is now 0 (../src/mme/mme-context.c:2791)

[avrodriguezgrad]

Hi @nitinbhat

Everything you've used are with the default configuration? I'll check it next week.

BR, Álvaro

[nitinbhat]

Hi @avrodriguezgrad ,

Yes, I have used default configuration.