Servings network name is hard-coded with MCC, MNC value. It will be good if MCC, M

Thank You <a class="user-mention notranslate" data-hovercard-type="user" data-hovercar

Hi <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="

Sure. <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-ur

We should create SN_NAME here <a href="https://github.com/omec-project/gnbsim/blob

Servings network name is hardcoded about gnbsim HOT 4 CLOSED

omec-project commented on August 16, 2024

Servings network name is hardcoded

from gnbsim.

Comments (4)

thakurajayL commented on August 16, 2024

Thank You @orion-belt . Do you have bandwidth to add this code ?

from gnbsim.

orion-belt commented on August 16, 2024

Hi @thakurajayL
Sorry. I am quite occupied actually, but i will try to check it out.

from gnbsim.

thakurajayL commented on August 16, 2024

Sure. @orion-belt & @gajjarvini if you have proposal about how this can be fixed and where we can have configuration then I can see how to add this support. Thank You

from gnbsim.

orion-belt commented on August 16, 2024

We should create SN_NAME here
https://github.com/omec-project/gnbsim/blob/main/realue/handler.go#L57 by extracting MNC and MCC info from object ue.Plmn.mcc & ue.Plmn.mnc. I tried this but looks like it is still hardcoded in some upstream. Then we can keep realm (3gppnetwork.org) as it is.

from gnbsim.

Related Issues (6)

Recommend Projects