Update UERANSIM images to use v3.2.7

This commit is contained in:
Borjis131
2025-03-30 16:43:09 +00:00
parent 42156927ac
commit 8c54c31df7
4 changed files with 10 additions and 10 deletions

View File

@@ -209,7 +209,7 @@ services:
gnb:
container_name: gnb
image: "ghcr.io/borjis131/gnb:v3.2.6"
image: "ghcr.io/borjis131/gnb:v3.2.7"
command: "-c /UERANSIM/config/gnb.yaml"
networks:
open5gs:
@@ -226,7 +226,7 @@ services:
ue:
container_name: ue
image: "ghcr.io/borjis131/ue:v3.2.6"
image: "ghcr.io/borjis131/ue:v3.2.7"
command: "-c /UERANSIM/config/ue.yaml"
networks:
open5gs:

View File

@@ -229,7 +229,7 @@ services:
gnb:
container_name: gnb
image: "ghcr.io/borjis131/gnb:v3.2.6"
image: "ghcr.io/borjis131/gnb:v3.2.7"
command: "-c /UERANSIM/config/gnb.yaml"
networks:
open5gs:
@@ -246,7 +246,7 @@ services:
ue1:
container_name: ue1
image: "ghcr.io/borjis131/ue:v3.2.6"
image: "ghcr.io/borjis131/ue:v3.2.7"
command: "-c /UERANSIM/config/ue.yaml"
networks:
open5gs:
@@ -263,7 +263,7 @@ services:
ue2:
container_name: ue2
image: "ghcr.io/borjis131/ue:v3.2.6"
image: "ghcr.io/borjis131/ue:v3.2.7"
command: "-c /UERANSIM/config/ue.yaml"
networks:
open5gs:
@@ -280,7 +280,7 @@ services:
ue3:
container_name: ue3
image: "ghcr.io/borjis131/ue:v3.2.6"
image: "ghcr.io/borjis131/ue:v3.2.7"
command: "-c /UERANSIM/config/ue.yaml"
networks:
open5gs:

View File

@@ -189,7 +189,7 @@ services:
gnb:
container_name: gnb
image: "ghcr.io/borjis131/gnb:v3.2.6"
image: "ghcr.io/borjis131/gnb:v3.2.7"
command: "-c /UERANSIM/config/gnb.yaml"
networks:
open5gs:
@@ -206,7 +206,7 @@ services:
ue1:
container_name: ue1
image: "ghcr.io/borjis131/ue:v3.2.6"
image: "ghcr.io/borjis131/ue:v3.2.7"
command: "-c /UERANSIM/config/ue1.yaml"
networks:
open5gs:
@@ -223,7 +223,7 @@ services:
ue2:
container_name: ue2
image: "ghcr.io/borjis131/ue:v3.2.6"
image: "ghcr.io/borjis131/ue:v3.2.7"
command: "-c /UERANSIM/config/ue2.yaml"
networks:
open5gs:

View File

@@ -24,7 +24,7 @@ sst: 1
sd: 000002
```
When this configuration is received in the 5G Core, the AMF uses it to select the appropiate SMF.
When this configuration is received in the 5G Core, the AMF uses it to select the appropiate SMF.
SMF1 is configured to serve the `sst: 1` and `sd: 000001`.