Run the command in (mme) and it will show whether UE is assigned with any IP and what are those IPs. When UE is in connected mode in RRC, you can check the ue status as follows (you don’t get any result when UE is in idle mode) (NOTE : You should see one or more PRACH print and several traffic prints as shown below). Power On UE and let it complete the attach. 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.Ĭheck on basic cell configuration and see if it is configured as you wanted (e.g, band, bw, RAT type etc) In this tutorial, it is assumed that you are familiar with how to get UE attached (Initial Attach) to Callbox. Start trace logging by 't' command as shown below . For further commands you can use in this screen mode, refer to the tutorial : Command Line Command 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. 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. You may restart the call box with following command NOTE : Getting this result is pre-requisite for Call Box Operation, but this result itself does not guarantee the normal operation. 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 Whatever you want to test, the first thing you need to do is that call box program (LTE Service) is running. On UE side, I configured as below, but this configuration would vary depending on the mobile phone model or type of your DUT. I used as the configuration for this tutorial but you may use any configuration as long as your DUT(UE) would support it. If you want to change the configuration, The tutorial Configuration Guide would help. SIM Card used in this tutorial is the one delivered with the system as it is.I used the default configuration(cfg) file without changing anything in it.Test setup for this tutorial is as shown below. You need to know how to figure this out on UE side. In most case, UE assigns a random interface id (the second half (32 bits) of IPv6 address. In many cases, UE does not assign UE IPv6 address as specified in NAS message.So you need to know how to change the UE side setting if you want to use IPv6 as a default APN/PDN or if you want to create a specific APN/PDN for IPv6 In most of the test UE using the test USIM, the UE is configured to use IPv4 as a default APN.So you need to know how to change configuration file if you want to use IPv6 as a default APN/PDN or if you want to create a specific APN/PDN for IPv6 In most test equipment including Amarisoft default configuration, IPv4 is used as a default APN/PDN.The reason why I am writing a separate tutorial for ping IPv6 is because there are some specific issues that you need to pay attention to IPv6 and followings are some of those issues. So for general introduction for ping test, refer to ping IPv4 tutorial. The purpose of doing IPv6 ping is same as IPv4. It is assumed that you don't have any previous experience with Amari callbox. Difficulties in trying anything with IPv6 is to trigger UE to request IPv6 PDU and figure out right IPv6 to ping do. The purpose of this tutorial is to show you how to ping from Callbox to UE in IPv6.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |