This briefly describes the settings for using VoLTE and SMS of docker_open5gs.
- One SGW-C/PGW-C, Multiple SGW-Us/PGW-Us and APNs
- One SMF, Multiple UPFs and DNNs
- Select nearby UPF according to the connected gNodeB
- Select UPF based on S-NSSAI
- SCP Indirect communication Model C
- VoLTE and SMS Configuration for docker_open5gs (this article)
- Monitoring Metrics with Prometheus
- Overview of Network Configuration
- Use the master branch of docker_open5gs
- Use the open5gs_hss_cx branch of docker_open5gs
- Changelog (summary)
This describes the following setting example.
eNodeB Docker host - 172.22.0.0/24
--------- -------------
| | | |
| | | |
--------- -------------
| |
-------------------------------------------------------
.10 .20 192.168.0.0/24
For reference, the Docker host VM on VirtualBox I have tried is as follows:
| CPU Cores | Memory | SSD | OS |
|---|---|---|---|
| 2 | 4GB | 40GB | Ubuntu 20.04 |
For eNodeB, set static routing to eNodeB for packets going from eNodeB to the Docker host network (172.22.0.0/24).
# ip route add 172.22.0.0/24 via 192.168.0.20
If eNodeB does not have a static routing setting function, build a network so that the Docker host becomes the default GW.
The PDNs are as follows.
| PDN | TUNnel interface of PDN | APN | U-Plane # |
|---|---|---|---|
| 192.168.100.0/24 | ogstun | internet | U-Plane1 |
| 192.168.101.0/24 | ogstun2 | ims | U-Plane1 |
In this branch you can try VoLTE and SMS over IMS / SMS over SGs.
Note. For SMS over SGs of docker_open5gs, 2G/3G radio access is not used at all rather it uses only the core network (MSC + SMSC + HLR).
# git clone https://github.com/herlesupreeth/docker_open5gs
# cd docker_open5gs
.env)
| Item | Value |
|---|---|
| MCC | 001 |
| MNC | 01 |
| DOCKER_HOST_IP | 192.168.0.20 |
| SGWU_ADVERTISE_IP | 192.168.0.20 |
docker-compose.yaml)
Publish the following ports of SGW-U and MME. And also remove the connection settings and dependencies to NRF.
--- docker-compose.yaml.orig 2022-11-24 13:08:54.241241214 +0900
+++ docker-compose.yaml 2022-11-24 13:11:09.745798200 +0900
@@ -258,16 +258,13 @@
expose:
- "8805/udp"
- "2152/udp"
- # ports:
- # - "2152:2152/udp"
+ ports:
+ - "2152:2152/udp"
networks:
default:
ipv4_address: ${SGWU_IP}
smf:
image: docker_open5gs
- depends_on:
- - nrf
- - scp
container_name: smf
env_file:
- .env
@@ -287,7 +284,6 @@
- "5868/sctp"
- "8805/udp"
- "2123/udp"
- - "7777/tcp"
- "9091/tcp"
networks:
default:
@@ -295,8 +291,6 @@
upf:
image: docker_open5gs
depends_on:
- - nrf
- - scp
- smf
container_name: upf
env_file:
@@ -382,8 +376,8 @@
- "36412/sctp"
- "2123/udp"
- "9091/tcp"
- # ports:
- # - "36412:36412/sctp"
+ ports:
+ - "36412:36412/sctp"
networks:
default:
ipv4_address: ${MME_IP}mme/mme.yaml)
Change the following tac according to the TAC of eNodeB.
mme:
...
sgsap:
addr: OSMOMSC_IP
map:
tai:
plmn_id:
mcc: MCC
mnc: MNC
--> tac: 1
...
tai:
plmn_id:
mcc: MCC
mnc: MNC
--> tac: 1
...
smf/smf.yaml)
Remove the binding on SBI and the connection settings to NRF.
--- smf.yaml.orig 2022-11-24 13:08:34.409159793 +0900
+++ smf.yaml 2022-11-24 13:13:03.458266393 +0900
@@ -6,9 +6,6 @@
smf:
freeDiameter: /open5gs/install/etc/freeDiameter/smf.conf
- sbi:
- - addr: SMF_IP
- port: 7777
gtpc:
- addr: SMF_IP
gtpu:
@@ -40,12 +37,6 @@
- addr: SMF_IP
port: 9091
-scp:
- sbi:
- - addr:
- - SCP_IP
- port: 7777
-
upf:
pfcp:
- addr: UPF_IPPlease install the following first.
See docker_open5gs for build instructions.
# cd docker_open5gs/base
# docker build --no-cache --force-rm -t docker_open5gs .
...
# cd ../ims_base
# docker build --no-cache --force-rm -t docker_kamailio .
...
For example, I prepare terminals for each of the following NF groups and execute them in order while checking the startup.
terminal#1
# set -a
# source .env
# docker-compose up mongo mysql dns webui
terminal#2
# set -a
# source .env
# docker-compose up osmohlr osmomsc
terminal#3
# set -a
# source .env
# docker-compose up hss mme pcrf sgwc sgwu smf upf
terminal#4
# set -a
# source .env
# docker-compose up rtpengine fhoss
terminal#5
# set -a
# source .env
# docker-compose up smsc icscf scscf pcscf
Please also register MSISDN. At that time, set the APN setting information as follows.
| APN | Type | QCI | ARP | Capability | Vulnerablility | MBR DL/UL(Kbps) | GBR DL/UL(Kbps) |
|---|---|---|---|---|---|---|---|
| internet | IPv4 | 9 | 8 | Disabled | Disabled | unlimited/unlimited | |
| ims | IPv4 | 5 | 1 | Disabled | Disabled | 3850/1530 | |
| 1 | 2 | Enabled | Enabled | 128/128 | 128/128 |
See below for details.
18. Install Open5GS in the same machine as Kamailio IMS - Install Open5GS from source
https://open5gs.org/open5gs/docs/tutorial/02-VoLTE-setup/
http://192.168.0.20:3000/
user: admin
password: 1423
Please login to the osmohlr container and register by referring to the following.
6.1 Example: Add/Update/Delete Subscriber via VTY
https://downloads.osmocom.org/docs/latest/osmohlr-usermanual.pdf
The following is an example of registering subscriber information for IMSI=001010000001001 and MSISDN=1001.
First, login to the osmohlr container.
# docker exec -it osmohlr /bin/bash
Then telnet to localhost.
# telnet localhost 4258
...
OsmoHLR> enable
OsmoHLR#
Next, register the subscriber information for IMSI=001010000001001 and MSISDN=1001.
OsmoHLR# subscriber imsi 001010000001001 create
% Created subscriber 001010000001001
ID: 1
IMSI: 001010000001001
MSISDN: none
OsmoHLR# subscriber imsi 001010000001001 update msisdn 1001
% Updated subscriber IMSI='001010000001001' to MSISDN='1001'
OsmoHLR#
Make sure this subscriber information is registered.
OsmoHLR# show subscribers all
ID MSISDN IMSI IMEI NAM
----- ------------ ---------------- ---------------- -----
1 1001 001010000001001 ------------- CSPS
Subscribers Shown: 1
OsmoHLR#
This setting is required to function as SMS over SGs.
Please refer to the following to register.
20. Add IMS subscription use in FoHSS as follows from the Web GUI
https://open5gs.org/open5gs/docs/tutorial/02-VoLTE-setup/
http://192.168.0.20:8080/hss.web.console/
user: hssAdmin
password: hss
Then, for each IMPU, you need to select smsc_sp for Service profile rather than default_sp.
Make sure that you can make a VoLTE call and SMS to the MSISDN. If your device does not support SMS over IMS, you can send SMS with SMS over SGs depending on your device.
Note. Kamailio's SMS (SMS over IMS) doesn't seem to handle multibyte messages properly, which causes garbled characters in SMS. On the other hand, OsmoMSC (SMS over SGs) seems to handle multibyte messages properly without garbled characters.
You can send SMS to the destination terminal by command operation on the OsmoMSC VTY terminal (SMS over SGs).
Please login to the osmomsc container and send SMS from the command line as following.
14 Configuring the Core Network
11.3.3 The list command
https://downloads.osmocom.org/docs/latest/osmomsc-usermanual.pdf
For example, if the following IMSI and MSISDN are registered in OsmoHLR)
| IMSI | MSISDN | SIM |
|---|---|---|
| 001010000001000 | 1000 | x |
| 001010000001001 | 1001 | o |
| 001010000001002 | 1002 | o |
First, login to the osmomsc container.
# docker exec -it osmomsc /bin/bash
Then telnet to localhost.
# telnet localhost 4254
...
OsmoMSC> enable
OsmoMSC#
- Command line to send SMS from MSISDN=1001 to MSISDN=1002 where the corresponding SIM exists
OsmoMSC# subscriber msisdn 1002 sms sender msisdn 1001 send TEST MESSAGE
- Command line to send SMS from MSISDN=1000 to MSISDN=1002 for which there is no corresponding SIM
OsmoMSC# subscriber msisdn 1002 sms sender msisdn 1000 send TEST MESSAGE
In this branch you can try VoLTE and SMS over IMS / SMS over SGs. Kamailio's S-CSCF and I-CSCF can communicate with Open5GS HSS(Cx) instead of FHoSS.
# git clone https://github.com/herlesupreeth/docker_open5gs
# cd docker_open5gs
# git checkout open5gs_hss_cx
...
docker_open5gs is a excellent software to try VoLTE and SMS easily. I would like to thank all the software developers and contributors related.
- [2022.04.11] Open5GS HSS Cx interface now supports the settings related to SMSC application server.
- [2022.02.27] Initial release.