VoLTE Setup with Kamailio IMS and Open5GS

[rkami78]

Hi,
I build the VoLTE setup with Kamailio on Ubuntu 18.04 VM. I assigned the VM to static IP address is 10.4.128.21.

network:
version: 2
ethernets:
enp0s8:
addresses:
-10.4.128.21/24
gateway4: 10.4.128.1
nameservers:
addresses: [10.4.128.1, 1.1.1.1]

I run the command curl icanhazip.com to get my Public IP is 174.70.25.98.

8. Populate MySQL database using kamctlrc command. What IP address I have to put here in SIP Domain
   SIP_DOMAIN=ims.mnc001.mcc001.3gppnetwork.org
   DBENGINE=MYSQL

9. Edit /etc/default/rtpproxy file as follows:

The control socket

#CONTROL_SOCK="unix:/var/run/rtpproxy/rtpproxy.sock"

To listen on an UDP socket, uncomment this line:

#CONTROL_SOCK=udp:127.0.0.1:22222
CONTROL_SOCK=udp:127.0.0.1:7722

Additional options that are passed to the daemon.

EXTRA_OPTS="-l 174.70.25.98 -d DBUG:LOG_LOCAL0"

$ systemctl restart rtpproxy

10. Edit configuration file to fit your requirements for the VoIP platform:
    #!define WITH_MYSQL
    #!define WITH_AUTH
    #!define WITH_USRLOCDB
    #!define WITH_NAT

(uncomment this line)
auto_aliases=no

(uncomment this line and enter the DNS domain created above)
alias="ims.mnc001.mcc001.3gppnetwork.org"

(uncomment this line, 10.4.128.21 is the internal IP and 172.24.15.30 is the Public/Floating IP)
listen=udp:10.4.128.21:5060 advertise 174.70.25.98:5060
listen=tcp:10.4.128.21:5060 advertise 174.70.25.98:5060

(Further down, we will need to modify the rtpproxy_sock value to match the CONTROL_SOCK option we set for RTPProxy in /etc/default/rtpproxy)
modparam("rtpproxy", "rtpproxy_sock", "udp:127.0.0.1:7722")

Followed 11 and 12 steps
11. The init.d script
12. A quick check for the basic working of SIP server can be done as follows:
13.
When I tired to make the SIP call over WiFi. I saw the message on phone SIP client app "MizuDriod" No response from server/ server is unavailable.
I want to build the VoLTE Open5gs. Please help me to resolve the issue.
Thank you,
Rifat
[email protected]

[herlesupreeth]

Please describe your setup. i.e. are you using a VM or a bare machine ?? If its a VM is it deployed over OpenStack or VirtualBox.

As far as I can see, you should not be using public IP 174.70.25.98. Rather just use your internal IP 10.4.128.21 i.e. I am assuming that your SIP client is connected to the same subnet to which machine running Kamailio is connected to.

[rkami78]

Please describe your setup. i.e. are you using a VM or a bare machine ?? If its a VM is it deployed over OpenStack or VirtualBox.

As far as I can see, you should not be using public IP 174.70.25.98. Rather just use your internal IP 10.4.128.21 i.e. I am assuming that your SIP client is connected to the same subnet to which machine running Kamailio is connected to.

I deployed the VM VirtualBox. I replaced the public IP with Internal IP. Now It's working I am able to make SIP call from UE1 to UE2.

Thank you very much.
Rifat

[SugarZhang]

Hello,
When I setup Open5GS and Kamailio and FHoSS, I am puzzled with the relationship with open5gs-hssd and hss of FHoSS.
Which one should I use as the HSS? Or both of them? I did not find APN configuration in FHoSS.
If both, is there and reference point between them?
Below is my network structure.
I run mme,sgwc,sgwu,smf,upf,pcrf,nrf,scp,sepp,ausf,udm,bsf,udr,webui of Open5GS, and pcscf,scscf,icscs of Kamailio, and hss of FHoSS. But it not work with use registration.

[herlesupreeth]

Which one should I use as the HSS? Or both of them? I did not find APN configuration in FHoSS.

open5gs HSS is used for LTE authentication and FHoSS is used for IMS authentication so both are needed. FHoSS does not need APN configuration

I run mme,sgwc,sgwu,smf,upf,pcrf,nrf,scp,sepp,ausf,udm,bsf,udr,webui of Open5GS, and pcscf,scscf,icscs of Kamailio, and hss of FHoSS. But it not work with use registration.

Please follow all the steps mentioned in the guide https://open5gs.org/open5gs/docs/tutorial/02-VoLTE-setup/ and registration should work. If it still does not post a tcpdump trace (without any filters) when you attempt IMS registration