User Guide

Chapter 6: Core network configuration 10
Otherwise, if other test SIM cards with different IMSI or secret key values are used, they must
be declared in the EPC database (HSS)
For that, open the /root/mme/config/ue_db-ims.cfg and add an entry for each sim card
in the ue_db array . Example :
{
sim algo: "milenage",
imsi: "001010000000001",
opc: "000102030405060708090A0B0C0D0E0F",
amf: 0x9001,
sqn: "000000000000",
K: "00112233445566778899AABBCCDDEEFF",
},
 
Note: Secret key parameters are mandatory as both UE and Network need to authenticate
each other .
 
6.2.3 Commercial SIM card
Any SIM card can be used with the AMARI callbox as long as it’s been declared in the UE
database as described in the section above.
However, it is very unlikely that you get the secret key parameters from the network operator
required for the authentication and the security mechanism.
In that case, the solution consists in disabling the authentication using one of the two methods
described below :
1) If the UE accepts the use of EIA0 (Null Integrity algorithm) in the NAS/RRC security
mode control procedures outside of an emergency call, then set the following option in your
MME configuration file:
authentication_mode: skip,
2) If you know the command at UE side to skip both the authentication and security mode
control procedures, then set the following options in your MME configuration file:
authentication_mode: skip,
skip_smc_proc: true,
and set the following option in your eNB configuration file (eNB configuration object, not
the cell configuration object)
skip_smc_proc: true,
6.2.4 APN configuration
MME is configured by default with four APN :
1. Default
2. Internet
3. IMS
4. SOS
For connecting your device to the callbox, one of these APN must be configured at UE side.
See [UE configuration], page 12, for more details.
Otherwise, if for any reason, the device under test must use a specific APN, the modification
can be done at MME side:
1. Open /root/mme/config/mme.cfg file.