Out of the Box Test - Ping


The purpose of this tutorial is to show you how to do IPv4 ping from  Amari Callbox to UE. It is assumed that you don't have any previous experience with Amari callbox. For IPv6 ping, refer to another tutorial : Ping IPv6.

I don't think I need to explain on what is ping since everybody would know it. I think more important thing is why we do ping test and what are the things to be considered about the ping test.  For any kind of data related test, for example, udp throughput (udp flooding), tcp throughput (tcp flooding), ftp(file download/upload) or streaming (e.g, YouTube streaming), the first thing you have to make it sure is that the required data pipe is properly established and the simplest way to check if the data pipe is established or not is to use ping test. Regarding the ping test,  I would suggest to check a few things listed below.

If the ping does not go through, refer to the ping throubleshoot Tips section.



Table of Contents



Test Setup


Test setup for this tutorial is as shown below.


TestSetup Callbox UE 1sdr 01






This test can be done with any configuration that assigns any one or more IP address to the UE.  If you just want to use what I have used for this tutorial, you can do as follows.

Go to the directory /root/enb/config and make a symbolic link as follows. (NOTE : If you are doing the test right out of the box you may not need to do this since this is the default configuration of Amari Callbox, but it is no harm to do this again).

OutOfBox Lte Config 01

Now you should see the enb.cfg file linked to enb.default.cfg as follows.

OutOfBox Lte Config 02

Now go to the directory /root/mme/config. You should see the configuration files as below.

OutOfBox Lte Config 03

If ims.cfg and mme.cfg is not linked to the files as shown above, you may run following commands to make proper link.

"ln -sf mme-ims.cfg mme.cfg" mean 'link mme-ims.cfg to mme.cfg' and "ln -sf ims.default.cfg ims.cfg" mean "link ims.default.cfg to ims.cfg"

OutOfBox Lte Config 04




Check if LTE service is Running


Whatever you want to test, the first thing you need to do is that call box program (LTE Service) is running. You can check on the execution status of the call box program by running following command and you should get the result as shown below


LteServiceStatus 01


NOTE : Getting this result is pre-requisite for Call Box Operation, but this result itself does not guarantee the normal operation. If you see some unexpected issues. You may restart the call box with following command




Run Screen


If it is confirmed that the lte service is running, go to screen mode by running 'screen -r' and follow through the steps as shown below. The steps shown here is the procedure that you would use for almost every test and it is highly recommended to get familiar with these steps. For further commands you can use in this screen mode, refer to the tutorial : Command Line Command


Run following command

screen r 01


You will get the screen as shown below.

This screen shows all the network components installed in the callbox. In this tutorial, it indicates MME, ENB, IMS, MBMSGW are installed in the callbox. You would see a number before each component name. With Ctrl+A and the number before the component name, you can switch to command line window for the specific component. For example, if you press Ctrl+A+1, the command line window switches to ENB and if you press Ctrl+A+0, the command line window switches to MME and so on.

Screen mode switch 01


Switch to [ENB] by pressing { Ctrl + A + 1 }. You will get the screen as shown below, When you switches to [ENB] there are some important information provided without running any specific command. It provides RF information showing the sample_rate, dl_freq, ul_freq, band, dl_ant, ul_ant that gives you very fundamental RF information. Check out the details of these info and see if the RF is configured as you intended.

OutOfBox SA Run 01


Start trace logging by 't' command as shown below . You can run this command any time during the test, but it is always good idea to run this command before you power on UE to get the log from very beginning of initial attach.

OutOfBox SA Run 04






In this tutorial, it is assumed that you are familiar with how to get UE attached (Initial Attach) to Callbox. If you are completely new to Amari Callbox and never tried anything before, I would suggest you to try the tutorial LTE Attach first and get back to this tutorial.

Power On UE and let it complete the attach.  If you started 't' command before you powe on UE, you will get the traces for PRACH attempt. The presence of PRACH trace can be a good troubleshooting indicator for initial attach problem.  If PRACH is properly received and the entire RACH process is completed, it is highly likely that the initial attach gets completed and start getting traffic log. Regarding the details on the meaning of each column of this log and how to use the information for troubleshoot, refer to this tutorial.

OutOfBox Ping Attach 01




Figure Out UE and Server IP


Run the command [ue] in (mme) and it will show whether UE is assigned with any IP and what are those IPs. The IPs assigned to the UE is configured in mme.cfg file as indicated below.(NOTE : If you don't see any of this kind of information, it may indicates there is some problems with the initial registration or IP allocation process and you need to troubleshoot until you get the result like this).

OutOfBox Ping FigureOut IP 01


Make it sure that the call box has network interface that is required for IP traffic with UE.

Following is the whole result of [ifconfig] on my Callbox. These are some of the network interface automatically setup by Operating system (Fedora on Amari Callbox Classic in my case). These are not directly involved in IP traffics with UE

OutOfBox Ping FigureOut IP 02

Make it sure that the network interface with internet connectivity is up and tun0,1,2,3 are up.  You may see different name in your setup.  The interface tun0,1,2,3 are network interface crated by Callbox. The IP assigned to these interfaces are configured in /root/mme/config/mme.cfg

OutOfBox Ping FigureOut IP 03

OutOfBox Ping FigureOut IP 04




Try ping


Now you can try ping on Callbox to the IP that is assigned to the UE.  

OutOfBox Ping TryPing 01


Then try ping from UE to Callbox. I downloaded and installed an Android Ping App on the UE for test. You may use any other App that is capable of ping test.

OutOfBox Ping TryPing 02

NOTE : As you saw here,  UE is assigned with two IPv4 address, one with internet pdn and the other with ims pdn. Depending on UE implementation, the ping may not work with ims pdn. In that case, try with ipv4 address with internet pdn.

NOTE : If ping from callbox to UE does not work, first check with your UE (DUT) allows inbound ping or not (For example, some UE may set firewall or any special internal settings to prevent the ping)

NOTE : If ping from UE to Callbox does not work, first check with your UE (DUT) allows outbound ping or not (For example, some UE may set firewall or any special internal settings to prevent the ping)




Troubleshoot Tips


If ping does not go through, I would suggest you to check on followings.