Testing VoLTE (Voice Over LTE)
version 2024-10-17*
This document is based on the latest test release.
Features may not be present in your current installed software. You may check their availability in your release documentation.
If you require an up to date release, ask for it in a ticket.

1 Introduction
- 1.1 Background
- 1.2 Amarisoft IMS Architecture
2 Making VoLTE Calls
3 Logging & Wireshark
4 Troubleshooting
5 Additional Information

1 Introduction

This application note explains the procedure for testing Voice over LTE (VoLTE) phones using Amarisoft EPC and IMS server. Some configuration changes may apply if you use Amarisoft IMS server with a third party EPC or if you use Amarisoft EPC with an external IMS server. The verification steps could also be different depending on the commands available on third party EPC and IMS servers.

Following sections give you a brief background on IMS followed by an overview of Amarisoft IMS architecture. Next chapter gives some hints to check if your device is VoLTE capable as well as the steps to make your VoLTE call. The last 2 chapters focus on logging and troubleshooting to ease the debug process.

1.1 Background

IMS (IP Multimedia Subsystem) provides the framework for IP based multimedia services in a mobile network. IMS uses IETF protocol SIP (Session Initiation Protocol) to set up and control voice and video calls, as well as instant messaging. The most common application of SIP is the setup and termination of Voice over IP (VoIP) telephone calls. The inconvenience of VoIP is its lack of guarantee for a good quality voice communication. Voice calls typically require less than 150 ms of one-way latency from mouth to ear as per the ITU G.114 standard. This could not be guaranteed when using VoIP calls with voice traffic being transmitted over default bearer in LTE on a best effort basis.

VoLTE (Voice over LTE) is a GSMA (Global System for Mobile Communications Association) initiative proposed by operators for optimum support of voice and SMS over IMS in LTE. VoLTE is the service that enables operators to provide improved QoS over SIP-based VoIP. This is basically done by using dedicated bearers to carry voice traffic. The voice dedicated bearer should have typically a QCI (QoS Class Identifier) of one as per Table Table 6.1.7 of 3GPP TS 23.203. The QCI=1 represents conversational speech with guaranteed bit rate and a packet delay budget of 100 msec.

A user requesting access to the IMS domain requires a new level of registration. To provide the necessary attributes for registration to IMS, an ISIM (IP multimedia Services Identity Module) application was added to the UICC (Universal Integrated Circuit Card).

The ISIM application includes:

A private ID called IMPI (IP multimedia private identity). IMPI is typically assigned by the home operator and is used to identify the IMS user’s subscription. Its main role is to support the authentication procedure during registration. For its syntax, the IMPI shall have the form username@realm as specified in clause 2.1 of RFC 4282 in accordance with 3GPP TS 23.003 and 3GPP TS 23.228.
One or more public IDs called IMPU (IP Multimedia Public Identity). IMPU is primarily used for user-to-user communication. The public identifier serves as a basis for message routing for IMS session-based SIP messages (e.g. INVITE). An IMPU could take the form of either a SIP URI (Uniform Resource Identifier) or a tel URI. A SIP URI is represented by sip:user@domain as per 3GPP TS 23.003 or 3GPP TS 23.228 while a tel URI is typically defined as a series of digits tel:+15551234567.
Home domain ID. The Home Domain ID provides the means by which that IMS routes a users’ registration request to the Home IMS Network.

If there is no ISIM application, a backward compatibility mechanism is in place to derive the Home Network Domain name from the IMSI as described in the following steps:

Take the first 5 or 6 digits, depending on whether a 2 or 3 digit MNC is used as per 3GPP TS 31.102 and separate them into MCC and MNC; if the MNC is 2 digits then a zero shall be added at the beginning.
Use the MCC and MNC derived in step 1 to create the domain name mnc<MNC>.mcc<MCC>.3gppnetwork.org.
Add the label "ims." to the beginning of the domain.
The result would be in the form of ims.mnc<MNC>.mcc<MCC>.3gppnetwork.org.

In the same way as above and in the absence of ISIM, IMPI could be derived from the IMSI as per 3GPP TS 23.003 clause 13.3:

Use the whole string of IMSI digits as the username part of the private identifier.
Convert the leading digits of the IMSI, i.e. MNC and MCC, into a domain name, as described above.
The result would be in the form of IMSI@ims.mnc<MNC>.mcc<MCC>.3gppnetwork.org.

IMPU can also be derived from the IMSI if UICC does not contain an ISIM. This IMPU takes the format of a SIP URI and is represented by sip:IMPI where IMPI is derived as described above. Note that this does not prevent the user to define other IMPUs.

The following example explains the above rules:

IMSI = 234150999999999
MCC = 234
MNC = 15
Domain Name = ims.mnc015.mcc234.3gppnetwork.org 
IMPI = 234150999999999@ims.mnc015.mcc234.3gppnetwork.org 
IMPU = sip:234150999999999@ims.mnc015.mcc234.3gppnetwork.org

1.2 Amarisoft IMS Architecture

The main components of an IMS server are as follows:

P-CSCF (Proxy-Call Session Control Functions): The P-CSCF is the first point of contact for a user. It is assigned to an IMS terminal before registration, and does not change for the duration of the registration.
I-CSCF (Interrogating-CSCF): The I-CSCF is the entry contact within an operatorâs network for all connections destined to a subscriber. It also forwards SIP request or response to the S-CSCF.
Serving-CSCF (S-CSCF): The S-CSCF is basically a SIP server. It is also responsible for handling the registration process and downloading user information and service profiles from the HSS.
The HSS (Home Subscriber Server) is the user database containing all subscribers information to handle calls.

Amarisoft IMS component, LTEIMS, is an IMS standalone simple server. It has a built-in P-CSCF, I-CSCF, S-CSCF and an internal HSS. It supports precondition and dedicated bearer using Rx interface.

The LTEIMS server could only be used for voice calls between 2 UEs registered within the Amarisoft LTE network. It can not be used for voice calls between a UE registered in Amarisoft network and any external UE in other networks. Connection to Circuit Switch networks is also not possible.

2 Making VoLTE Calls

2.1 UE Configuration

There is no generic rule to activate VoLTE in a UE as different phones might have different menus. Below, you can find some useful information for Samsung S5 and OnePlus 3 devices.

For a Samsung S5 device, please go to Settings/More networks/Mobile networks of your handset and check VoLTE Call is ticked:

For a OnePlus3 device, the menu is under Settings/SIM & network

Note that the availability of the VoLTE menu also depends on the UICC used. The default Amarisoft MME configuration file defines two PDNs that you should add to your device.
On a Samsung S5 device:

Go to Settings/More networks/Mobile networks
Turn on Data roaming
Go back to Mobile network.
Add the first APN with the following parameters:
- Name = Internet
- APN = internet
- APN type = internet,default or APN type = default depending on the UE model
Save it and select it.
Add second APN with following parameters:
- Name = IMS
- APN = ims
- APN type = ims
Save it and do not select it (This APN may not be displayed).
Reboot your phone

On OnePlus3 device:

Go to Settings/SIM & network/SIM1
Turn on Data roaming
Go to Settings/SIM & network/SIM1/Access Point Names
Add the 2 APNs as explained above.

In order to test VoLTE in IPv6, make sure you set the following parameters in your APN setting:

APN protocol = IPv4/IPv6
APN roaming protocol = IPv4/IPv6

2.2 Network Configuration

Edit the file config/ims.cfg to set the address of the SIP interface. You can keep the current config as it is if you use Amarisoft LTEIMS and LTEMME and if they are both running on the same PC.
Create an entry for your UE in the UE database file config/ue_db-ims.cfg. This file is included in config/mme-ims.cfg and config/ims.cfg. Your UE entry should include
1. LTE authentication parameters such as IMSI and authentication algorithm. These parameters should match the ones stored in the UICC of your device.
2. IMS authentication parameters IMPI, IMPU and domain name. There are 2 cases:
  - - Your device UICC includes an ISIM application. IMPI, IMPU and domain name in the UE database should match the ISIM parameters of your device. If you do not know your ISIM parameters, you can always retrieve your IMPI by looking at IMS logs inside REGISTER request. The IMPI must match the username argument inside Authorization header. As for IMPU, you can check the FROM field of the SIP INVITE message.
  - - Your device UICC does not include an ISIM application. IMPI, IMPU and domain name should be derived from your IMSI as explained in section Background (See Background).
Following is the default configuration for Anritsu UICC, already available in config/ue_db-ims.cfg. This UICC does not contain ISIM application and as you can observe, the IMS related parameters are all derived from the IMSI.
```
ue_db: [{
    sim_algo: "xor", /* USIM authentication algorithm: xor, milenage or tuak */
    imsi: "001010123456789",
    amf: 0x9001, /* Authentication Management Field */
    sqn: "000000000000", /* Sequence Number */
    K: "00112233445566778899aabbccddeeff",

    impi: "001010123456789@ims.mnc001.mcc001.3gppnetwork.org",
    impu: ["001010123456789", "tel:0600000000", "tel:600"],
    domain: "ims.mnc001.mcc001.3gppnetwork.org",
    multi_sim: true, /* Experimental */
}
```
In the above example, you can observe that we have defined 3 IMPUs:
1. 001010123456789 corresponds to the SIP mandatory IMPU derived from IMSI sip:001010123456789@ims.mnc001.mcc001.3gppnetwork.org. Note that SIP URI for IMPU must not include the domain name. If IMPU does not start by a scheme, it is assumed to be a SIP URI.
2. tel URI 0600000000 which is a number where you can reach your device.
3. tel URI 600 which is a second phone number of your device.
Make sure your system is started with the right configuration files. If you are running the system manually, simply make sure that you are using mme-ims.cfg as LTEMME config file and ims.cfg as LTEIMS config file. If you are using an automatic service, the used LTEMME configuration file is mme.cfg. Make sure that mme.cfg is a symbolic link pointing to mme-ims.cfg in your mme/config directory.
The IMS program should be started as root if you want IPsec support. For manual start up, you can type the following commands:
```
sudo cd /root/mme
sudo ./ltemme config/mme-ims.cfg
sudo ./lteims config/ims.cfg
sudo cd /root/enb
sudo ./lteenb config/enb.cfg
```
If you have changed anything in configuration files and you are using automatic service, make sure you restart the system
```
sudo service lte restart
```

The ims PDN defined in fille mme-ims.cfg allows you to test VoLTE in IPv4 and IPv6. The IP version to be used could be controlled by setting pdn_type to ipv4, ipv6 or ipv4v6 in file mme-ims.cfg.

2.3 Step by Step Volte Call Testing

This section provides instructions for establishing a VoLTE call.

In the default configuration, the IMS PDN is called ims with a range of IPv4 addresses from 192.168.4.2 to 192.168.4.254 and IPv6 prefixes from 2001:468:3000:1:: to 2001:468:3000:ffff::. Make sure your UE is correctly attached to APN "ims" and has obtained an IPv4 and/or IPv6 address. You can type ue command in LTEMME screen. The ouput should look like below:

In this example, the UE has obtained IPv4 address 192.168.4.2 and IPv6 prefix of 2001:468:3000:1::.
The IMS command line interface is used to monitor the operation of LTEIMS. At the IMS window, check the output of users command which lists the user database and registering state of each device. Example below

If your UE is correctly registered in IMS server, you should see a line starting by Binding as shown in the above image.

At this step, you can start the VoLTE call. You have the possibility to do

MO (Mobile Originated) ECHO test: The echo phone number is specified in file ims.cfg as below
```
/* Echo phone number */
echo: ["tel:666", "tel:+666"],
```
You can simply call 666 to have a voice echo test.
MT (Mobile Terminated) call test: You can directly initiate a MT call from the IMS server by typing
```
mt_call <impi>
```
in LTEIMS screen.
End-to-end call test: you can directly originate a call from one device to another. You can use the other device IMPU tel URI to initiate a call. In the default config with Anritsu UICC, you just need to dial 600 to call the other device.

2.4 VoLTE with Test SIM Cards

Test sim cards usually have the same IMSI which means that there is no way in EPC and IMS server to distinguish between devices using the same test SIM card. Amarisoft feature multi-sim allows you to use the same test SIM card in several devices and yet be able to differentiate UEs with the same IMSI. Note that this is only valid if XOR authentication algorithm is used in the SIM card. To enable this feature, you need to set multi_sim field in ue_db-ims.cfg file to true. In this case, the UEs could be distinguished with their IMEIs (International Mobile Equipment Identity).

As long as you have only 2 phones and you would like to initiate an end to end call between the 2 phones, our default configuration with multi_sim: true in ue_db-ims.cfg is sufficient. You can call other phone by calling 600. For more than 2 phones, it is mandatory to create an IMPU associated to each device IMEI as follows:

impu: [  
        "001010123456789",
        { impu: "tel:0701", imei: "359027072930540" },
        { impu: "tel:0702", imei: "356853053276500" },
        { impu: "tel:0703", imei: "359027072637360" },
],

Of course you have to update the imei fields by the ones for your UEs. The easiest way to find imei of your UEs is to check the output of ue command in LTEMME window. It will show you the IMEISV (IMEI Software Version) of the attached devices. You can also find IMEI directly from your phone. Check settings/more/about device/status in Android and you would see IMEI.

IMEI = IMEISV - last 2 digits + 0

Note that you should always maintain the default IMPU derived from your IMSI in your IMPU list.

2.5 Emergency calls

Emergency calls are supported (with and without SIM card), but might require a few settings in the various configuration files:

eNB configuration file
ims_emergency_support parameter must be set to true.
MME configuration file
ims_vops_eps and emc_bs parameters must be set to true. For 5GC, ims_vops_5gs_3gpp or ims_vops_5gs_n3gpp parameter must be set to true, and emc parameter must be set to 1 or 3 or emc_n3gpp must be set to true.

One PDN should be defined with the emergency parameter set to true (it identifies the PDN used for emergency calls and the associated P-CSCF address).
IMS configuration file
Add one entry to the echo list with the following parameters:
- impu parameter set to "urn:service:sos" or any other specific string you might need.
- anonymous parameter set to true to allow calls without SIM card.
- authentication parameter set to false if you want to skip authentication for anonymous calls.

You can look at the configuration files delivered for examples.

3 Logging & Wireshark

The Amarisoft IMS server generates a log file /tmp/ims.log that could be used for for further analysis and debugging. There is also the possibility to take a Wireshark log of the interface between LTEMME and LTEIMS. Wireshark is the industry-standard free IP and SIP protocol logging and analysis tool. Wireshark complements our internal IMS logging capability by providing an independent SIP log.

The name of the interface to log with Wireshark could be checked with ifconfig command. If the LTEMME and the LTEIMS run on the same machine, by default the loopback interface is used for their communication. The loopback interface is usually named lo. Assuming lo interface is used, you can take a Wireshark log by running the below command:

tcpdump -i lo -w ims.pcap

Note that you need to deactivate IPsec to be able to visualize SIP messages by replacing

ipsec_ealg_list: ["null", "aes-cbc", "des-cbc", "des-ede3-cbc"],

ipsec_ealg_list: ["null"],

4 Troubleshooting

Below are some of the most common issues encountered during testing with recommended actions to address each issue.

Issue	Cause/Correction
Can not initiate VoLTE call	First thing is to check the LTEMME log. There must be a P-CSCF address request in NAS Attach request or NAS PDN connectivity request messages. [NAS] UL 0064 ESM: PDN connectivity request Protocol discriminator = 0x7 (EPS Mobility Management) Security header = 0x2 (Integrity protected and ciphered) Auth code = 0x50ad48d0 Sequence number = 0x04 Protocol discriminator = 0x2 (EPS Session Management) EPS bearer identity = 0 Procedure transaction identity = 3 Message type = 0xd0 (PDN connectivity request) Request type = 1 PDN type = 3 (IPv4v6) Access point name = "ims" Protocol configuration options: ext = 1 configuration protocol = 0 Protocol ID = 0x8021 (IPCP) Data = 01 00 00 10 81 06 00 00 00 00 83 06 00 00 00 00 Protocol ID = 0x000d (DNS Server IPv4 Address Request) Data = Protocol ID = 0x0003 (DNS Server IPv6 Address Request) Data = Protocol ID = 0x0001 (P-CSCF IPv6 Address Request) Data = Protocol ID = 0x000c (P-CSCF IPv4 Address Request) Data = Protocol ID = 0x0002 (IM CN Subsystem Signaling Flag) Data = Protocol ID = 0x000a (IP address allocation via NAS signalling) Data = Assuming P-CSCF request has been sent, you must check in the Wireshark capture of the interface or the LTEIMS log file that the UE is sending a REGISTER SIP message. This message is generally sent via UDP on port 5060. In some rare cases, TCP is used instead.
There is no P-CSCF address request in NAS messages	Check if you see a VoLTE menu in your phone. If you do not see it, it means VoLTE support is not enabled. Sometimes, you need to access hidden menus to activate IMS and VoLTE. On some Android phones, you have the possibility to access these hidden menus by typing `##4636##`. Some phones require a firmware update before activating IMS and VoLTE. Make sure you accept and install updates on your phone. Some phones only enable VoLTE with certain mobile operators and UICC cards.
There is a P-CSCF address request in NAS messages but no REGISTER SIP message is sent by the UE	Some phones require a special name for their IMS APN. Check NAS Attach request or NAS PDN connectivity request messages in the LTEMME log to see which APN names your device is requesting. Change the `access_point_name` of your PDN in file `mme-ims.cfg` accordingly. Some phones require an ISIM application in the UICC before enabling VoLTE. Some phones only enable VoLTE with certain mobile operators and UICC cards.

5 Additional Information

This document is available without any express or implied warranty and is subject to change without notice. In no event will Amarisoft be held liable for any damages arising from the use of this document.

For any technical issue, please raise a ticket from our support site at https://support.amarisoft.com/.
To learn more about our technology and solutions, e-mail us at customer@amarisoft.com or visit https://www.amarisoft.com.

License terms

Amarisoft SAS - www.amarisoft.com
16-18 rue Rivay, 92300 LEVALLOIS PERRET, France SAS with a capital of 300,000 Euros - VAT FR21753998269 - SIREN: 753998269 (RCS Nanterre) - NAF 6201Z – DUNS 264482426

SOFTWARE LICENSE TERMS
NOTICE: THE AMARISOFT SOFTWARE PRODUCT, TOGETHER WITH ITS ACCOMPANYING DOCUMENTATION,
(THE "PRODUCT") IS THE PROPERTY OF AMARISOFT. THE PRODUCT IS MADE AVAILABLE TO YOU, THE
PURCHASER, SUBJECT TO THE FOLLOWING LICENSE AGREEMENT ("LICENSE AGREEMENT"). PLEASE READ
THIS LICENSE CAREFULLY BEFORE INSTALLING OR USING THE PRODUCT. A COPY OF THIS LICENSE IS
AVAILABLE FOR YOUR FUTURE REFERENCE IN THE "LICENSE.TXT" FILE PROVIDED WITH THE PRODUCT.
IF YOU DO NOT AGREE TO THE TERMS AND CONDITIONS OF THIS AGREEMENT AND THE TERMS AND
CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED BELOW,
THEN YOU MAY NOT USE THE PRODUCT. ANY USE BY YOU OF THIS PRODUCT OR INSTALLATION OF THE
PRODUCT ALSO CONSTITUTES YOUR ACCEPTANCE OF THESE TERMS.
AMARISOFT is only willing to grant you a license under this License Agreement if you obtained the Product
from AMARISOFT or an AMARISOFT authorized distributor or reseller, a list of which is available on
AMARISOFT website. If you obtained the Product from any other source you may not install or use the
Product.

1. GRANT OF LICENSE AND SCOPE OF USE
For each license that you acquire to use the Product, you will be provided with a License Certificate (a "License
Certificate"), which may be either a certificate, the installation and licensing instructions, your invoice, or an
activation file and which may be provided to you either with the Product media or separately by AMARISOFT
or its authorized distributors or resellers. The License Certificate will contain information specific to the
Product, the type of license under which you may use the Product and the number of licenses that you have
acquired. In order to activate and use the Product as set forth in this License Agreement, you must follow the
instructions when prompted by the Product.
The type of license you may acquire is a Standard License or a Floating License, all defined in Sections 1.1 and
Section 1.2 of this License Agreement. Unless your License Certificate identifies your acquisition of another
license type, you have acquired a Standard License. For more information on which license types, if any, is
included with the Product media, you should contact AMARISOFT or your AMARISOFT authorized distributor or
reseller.
Unless otherwise agreed, one (1) AMARISOFT license provides the right to use only one instance of the Product
software at a time.
Subject to the other terms and conditions of this License, you may make a reasonable number of copies of the
Product to backup devices such as hard disks, optical media, or tape and one (1) physical CD media backup
copy of the Product solely to replace the original copy provided to you if the original copy is damaged or
destroyed. All rights not specifically granted to you herein are retained by AMARISOFT.

1.1 Standard License
The terms of this Section 1.1 are applicable to you only if you have purchased a Standard License, as defined
below, for the Product directly from AMARISOFT or an AMARISOFT authorized distributor or reseller.
Subject to the terms and conditions of this License, AMARISOFT grants you, if you are an individual or if you
are an entity, a personal, non-exclusive, non-transferable and limited license to use the Product solely with
one (1) designated single hardware in your organization (a "Standard License"). This hardware is either a
Personal Computer that you hold in your organization or that AMARISOFT has supplied you. This hardware can
also be a USB device supplied by AMARISOFT.
You may purchase from AMARISOFT or an AMARISOFT authorized distributor or reseller additional licenses to
permit multiple hardware to use the Product. This right shall be agreed in writing. The Standard License shall
provide you with the right to access and use the Product, only for the number of hardware for which you have
paid the applicable license fees and obtained a License Key Certificate. The Product may be used exclusively by
the specifically designated hardware, subject to all the terms and conditions of this License Agreement. You
agree that you will not designate more hardware than the number of Standard Licenses that AMARISOFT or an
AMARISOFT authorized distributor or reseller has expressly granted you and you will not allow the Product to
be used by any hardware other than the hardware designated by you.

1.2 Floating License
The terms of this Section 1.2 are applicable to you only if you have purchased a Floating License, as defined
below, for the Product directly from AMARISOFT or an AMARISOFT authorized distributor or reseller.
Subject to the terms and conditions of this License, AMARISOFT grants you, if you are an individual or if you
are an entity, a personal, non-exclusive, non-transferable and limited license to use the Product from our
floating license server in your organization ("FLS"). Our floating license server will allow you to run the license
on a virtual machine and thus use it on any hardware in your organization (an "FLS License").
You may purchase from AMARISOFT or an AMARISOFT authorized distributor or reseller additional licenses
and place them on our license server to permit multiple hardware to use the Product.

2. SPECIAL TERMS
The following terms and conditions ("Special Terms") are specific to certain editions, versions and components
of the Product and are in addition to the provisions of Section 1. If any provision of the Special Terms
applicable to the Product conflicts with any other provision of this License, then the provision of the Special
Terms will supersede and control.

2.1 Additional license terms applicable to third party software
Certain components of the Product use or incorporate third-party software programs and/or libraries ("Third-
Party Software"), which are loaded or integrated (in both object and source code form) on the Product. You
agree that AMARISOFT's third-party licensors and suppliers are intended third party beneficiaries of all terms
and conditions of this License intended to protect intellectual property rights in the Product (including the
Third-Party Software) and limit certain uses thereof.

3. LIMITATIONS
You may not:
(a) modify, adapt, alter, translate or create derivative works of the Product or merge the Product with other
software other than as described in the Product's accompanying documentation or as approved of in writing
by AMARISOFT;
(b) lease, rent or loan the Product to any third party;
(c) sublicense, distribute or otherwise transfer the Product or any component thereof to any third party except
as expressly authorized in this Agreement;
(d) reverse engineer, decompile, disassemble or otherwise attempt to derive the source code of the Product;
(e) remove, alter or obscure any confidentiality or proprietary notices (including copyright and trademark
notices) of AMARISOFT or its licensors or suppliers on or accompanying the Product;
(f) allow third parties to access or use the Product including but not limited to using the Product in a time-
sharing arrangement, operating the Product as part of a service bureau or, except as expressly authorized
under Sections 1 and 2 otherwise using the Product for the use or benefit of third parties;
(g) reproduce or use the Product except as expressly authorized under Sections 1 and 2;
(h) use the Product with any other hardware than the hardware designated in your organization; or
(i) disclose or publish performance benchmark results for the Product. The rights granted under this License
apply only to this Product.
You must procure a separate license to use other AMARISOFT software. Furthermore, you may not permit end
users of the Product ("End Users") to conduct the restricted activities limited by items (a) through (e), (g) and
(i) above insofar as they apply to certain files, libraries and/or source code specifically designated as
"redistributables" by AMARISOFT in the accompanying printed or on-line documentation and that are
necessary to use your own application programs and other works created using the Product
("Redistributables"), and such End User's sublicense rights to the Redistributables are conditioned upon
compliance with such limitations. The limitations in this Section 3 apply equally to your use of the Product, in
whole or in part, including any component or Redistributable.

4. LIMITED WARRANTY AND DISCLAIMER
AMARISOFT warrants you, the initial purchaser and no other party, that any physical media included with the
Product, as and when provided to you, will be free of physical defects in materials and workmanship for a
period of thirty (30) days after the date that you initially acquire the Product.
Your exclusive remedy and AMARISOFT's sole liability for breach of this warranty is that AMARISOFT will
replace any defective media returned to AMARISOFT within the thirty (30) day warranty period. This warranty
does not apply to damages resulting from misuse, abuse or neglect. Any replacement media will be warranted
as above for the remainder of the original warranty period or twenty (20) days from the date we ship it to you,
whichever is longer.
EXCEPT FOR THIS EXPRESS LIMITED WARRANTY, THE PRODUCT IS PROVIDED "AS IS" AND WITHOUT
WARRANTY OF ANY KIND. AMARISOFT HEREBY EXCLUDES AND DISCLAIMS ALL IMPLIED OR STATUTORY
WARRANTIES, INCLUDING ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE,
QUALITY, NONINFRINGEMENT, TITLE, RESULTS, EFFORTS OR QUIET ENJOYMENT. THERE IS NO WARRANTY
THAT THE PRODUCT WILL BE ERROR-FREE OR WILL FUNCTION WITHOUT INTERRUPTION. YOU ASSUME THE
ENTIRE RISK FOR THE RESULTS OBTAINED USING THE PRODUCT. TO THE EXTENT THAT AMARISOFT MAY NOT
DISCLAIM ANY WARRANTY AS A MATTER OF APPLICABLE LAW, THE SCOPE AND DURATION OF SUCH
WARRANTY WILL BE THE MINIMUM PERMITTED UNDER SUCH LAW.

5. SERVICES, UPDATES AND PRODUCT CHANGES
AMARISOFT is not required under this License Agreement to provide any installation, maintenance service,
training or other services to you, except those expressly provided herein. Such services, if available, must be
purchased separately.
If, pursuant to a separate support agreement or otherwise, AMARISOFT provides you with a new release, error
correction, update, upgrade or other modification to the Product, such modification will be deemed part of the
Product, and subject to the terms of this License Agreement, unless the modification is expressly provided
subject to a separate License Agreement.
AMARISOFT reserves the right at any time not to release or to discontinue release of any Product and to alter
prices, features, specifications, capabilities, functions, licensing terms, release dates, general availability or
other characteristics of any future releases of the Product.

5.1 Support extension
Unless otherwise indicated, AMARISOFT License includes a one-year email support period and update.
You can subscribe to an additional one-year support and update period, at the latest within the four months
following the expiry date of the initial purchase. You can then renew subscription to this extension every year,
with the same four-month deadline. The extended support and update period starts on the day after the initial
expiry date.
Once this four-month deadline is over, an extra administrative reactivation fee is invoiced in addition to the
extension cost. The extended support and update period starts when payment of the corresponding invoice is
received.

6. REGISTRATION
You must register the Product with AMARISOFT as a condition to your rights to use the Product.
For all concerned, you will be asked to provide identification information on the hardware (serial number,
internal inventory number, other) you plan to install the Product on.

7. CONFIDENTIALITY
You acknowledge that if part of the Product in source code form exists, it remains a confidential trade secret of
AMARISOFT. You agree to hold this information in confidence, not to disclose it to any person, and not to use it
for any purpose other than the use and operation of the Product as permitted under this License Agreement.

8. LIMITATION OF LIABILITY
IN NO EVENT WILL AMARISOFT BE LIABLE TO ANY PARTY FOR ANY INDIRECT, INCIDENTAL, CONSEQUENTIAL,
EXEMPLARY, SPECIAL OR PUNITIVE DAMAGES, INCLUDING ANY LOSS OF PROFIT, REVENUE, BUSINESS
OPPORTUNITY OR DATA, ARISING FROM OR RELATING TO THIS LICENSE AGREEMENT OR THE PRODUCT,
WHETHER IN CONTRACT, IN TORT, NEGLIGENCE OR OTHERWISE, EVEN IF AMARISOFT KNEW, SHOULD HAVE
KNOWN OR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. AMARISOFT'S TOTAL CUMULATIVE
LIABILITY ARISING FROM OR RELATED TO THIS LICENSE AGREEMENT OR THE PRODUCT, WHETHER IN
CONTRACT, IN TORT OR OTHERWISE, WILL NOT EXCEED THE FEES ACTUALLY PAID BY YOU UNDER THIS
LICENSE AGREEMENT. THIS SECTION 8 WILL APPLY EVEN IF AN EXCLUSIVE REMEDY HEREUNDER HAS FAILED
OF ITS ESSENTIAL PURPOSE.

9. TERM AND TERMINATION

9.1 Term
The term of this License Agreement will begin as of the date that you receive the Product and will remain in
effect unless terminated under this Section 9.

9.2 Termination for Convenience
You may terminate this License Agreement for any reason, or for no reason, by giving AMARISOFT a five-day
(5) written notice. You shall not be entitled to request repayment of any fee or payment made to AMARISOFT.

9.3 Termination for Cause
AMARISOFT may terminate this License Agreement if you breach your obligations hereunder. AMARISOFT will
affect such termination by giving you notice of termination, specifying therein the alleged breach. If your
breach is curable, you will have a grace period of thirty (30) days after such notice is served to cure the breach
described therein. If the breach is cured within the thirty (30) day grace period, then this License Agreement
will remain in effect; otherwise, this License Agreement will automatically terminate upon the conclusion of
the thirty (30) day grace period.

9.4 Effect of Termination
Upon the termination of this License Agreement for any reason the following terms shall apply:
(a) all rights granted under this License Agreement will immediately terminate and you must stop all use of the
Product and any Redistributables;
(b) you must return to AMARISOFT or destroy all copies of the Product provided to or made by you, and will,
within ten (10) days after the effective date of termination, provide AMARISOFT with written certification that
all such copies have been returned or destroyed; and
(c) all provisions of this License Agreement with the exception of the licenses granted in Sections 1 and 2, will
survive termination of this License Agreement for any reason.

10. GENERAL PROVISIONS

10.1 Audit
If you are entering into this License Agreement as an entity other than an individual (e.g., as a corporation, a
partnership, or other organization), during the term of this License and for three (3) years thereafter,
AMARISOFT or its outside auditors will have the right to conduct an audit of your records and computer
systems to verify that you have paid to AMARISOFT the correct amounts owed under this License Agreement
and determine whether the Products are being used in accordance with the terms of this License Agreement.
Any audit will be conducted during regular business hours at your facilities, with reasonable notice. You agree
to provide the audit team access to the relevant records and facilities and to provide reasonable assistance to
AMARISOFT in connection with this provision. You agree to pay the cost of the audit if any underpayments
during the period covered by the audit amount to more than five percent (5%) of the fees actually owed or if
the number of deployments of the Products is more than five percent (5%) of that licensed.

10.2 Hazardous Uses
The Product is not intended for use in connection with any application requiring fail-safe performance such as
the operation of nuclear power facilities, air traffic control or navigation systems, weapons control systems,
life support systems, or any other system whose failure could lead to injury, death, environmental damage or
mass destruction. You agree that AMARISOFT will have no liability of any nature, and you are solely
responsible, for any expense, loss, injury or damage incurred as a result of such use of the Product.

10.3 Entire License and Severability
This License Agreement constitutes the entire, final and exclusive agreement between you and AMARISOFT
regarding the specific license transaction described herein. If any provision of this License Agreement is held to
be illegal, invalid or unenforceable for any reason, then such provision will be enforced to the maximum extent
permissible and the remainder of the provisions of this License Agreement will remain in full force and effect.

10.4 Assignment
You may not transfer the Product, assign this License Agreement or assign any of your rights or delegate any of
your obligations under this License Agreement, by operation of law or otherwise (including by merger, sale of
assets or consolidation), without AMARISOFT's prior written consent. Any attempted assignment in violation
of this Section 10.4 will be void.

10.5 Export Control
You may not directly or indirectly transfer the Product, including its documentation, to any country if such
transfer would be prohibited by applicable law. You agree to the foregoing and you are representing and
warranting that you are not located in, under the control of, or a national or resident of any such country. You
will be solely responsible for identifying and complying with all laws of any jurisdiction regarding the import,
export or use of Products and technical data supplied by AMARISOFT. You will obtain at your own expense all
licenses, permits or approvals required by any government to use the Product.

10.6 Waiver and Modifications
All waivers must be in writing. Any waiver or failure to enforce a provision of this License Agreement on one
occasion shall not be deemed a waiver of any other provision or such provision on any other occasion. This
License Agreement may only be amended by a written document signed by both parties.

11. CRYPTOGRAPHY
The Product and the content provided by AMARISOFT may contain encryption software. The country in which
you are currently may have restrictions on the import, possession, and use, and/or re-export to another
country, of encryption software. BEFORE using any encryption software, please check the country's laws,
regulations and policies concerning the import, possession, or use, and re-export of encryption software, to
see if this is permitted.

12. NON-RECURRING ENGINEERING
The intellectual property of all items designed, developed and manufactured by AMARISOFT resides and
remains with AMARISOFT. The payment of Non-Recurring Engineering (NRE) charges by you does not confer
any rights to the intellectual property of any designs which emanate directly or indirectly from the
development. As part of any contract, whether it includes the payment of NRE or not, you must accept
without reservation that AMARISOFT is the rightful owner of all intellectual property rights for the Product
and/or other products which are supplied under this Licence Agreement or standard supplies to you. You must
not copy, or allow any third party to copy the designs of any AMARISOFT's products.

Testing VoLTE (Voice Over LTE) version 2024-10-17*This document is based on the latest test release.Features may not be present in your current installed software. You may check their availability in your release documentation.If you require an up to date release, ask for it in a ticket.

Table of Contents