Contents
1 Introduction
This document describes how to configure the Emergency Call Notification service in the MTAS.
1.1 Prerequisites
It is assumed that the user of this document is familiar with the O&M area, in general.
1.1.1 Licenses
To enable the Emergency Call Notification service, the basic MMTel license must be installed.
For more information about the basic MMTel license, refer to MTAS Licenses
1.1.2 Documents
Before starting any procedure in this document, ensure that the following documents are available:
1.1.3 Conditions
The following condition must apply:
An Ericsson Command Line Interface (ECLI) session in Exec mode is in progress.
2 Overview
The Emergency Call Notification service enables notifications for emergency calls. Based on SIP NOTIFY received from the Call Session Control Function (CSCF), the MTAS indicates the start and stop of an emergency call to the Online Charging System (OCS) over the Ro interface. The data in the SIP Event header received in the NOTIFY is used to populate the Service-Specific-Info Attribute Value Pair (AVP) having subAVPs Service-Specific-Type and Service-Specific-Data. An example of a call flow is shown in Figure 1.
The call flow for an emergency call notification is as follows:
- Emergency call is initiated or ended.
- The CSCF sends an unsolicited SIP NOTIFY on the IMS Service Control Interface (ISC) to the originating MMTel Application Server (AS) with session case unregistered and with Event header value emergencyCall and parameter start or stop.
- Emergency Call Notification function of the MTAS is invoked. The following conditions hold:
- The MTAS sends Credit Control Request (CCR) Event over the Ro interface with Service-Specific-Info AVP (and subAVPs) populated to report Emergency Call start or end according to data received in the Event header.
- The OCS answers with Credit Control Answer (CCA).
- The MTAS sends 200 OK to the CSCF as a response to the NOTIFY.
2.1 Subfunctions
The subfunctions included in the Emergency Call Notification service are described in this section.
2.1.1 Emergency Call Notification
Reporting emergency call notifications to the OCS can be enabled or disabled by the operator.
2.1.2 Reporting Start and Stop of Emergency Call to OCS
The MTAS reports start and stop of an emergency call to the OCS based on the unsolicited out-of-dialog SIP NOTIFY with Event header value emergencyCall and parameter start or stop received from the CSCF.
2.2 Interaction with Other Services
There is no interaction with other services.
3 Emergency Call Notification Configuration
The Emergency Call Notification service is controlled by the MtasChargingProfile MO. An overview of the MtasChargingProfile MO structure is shown in Figure 2.
Configurable MOs and attributes related to the Emergency Call Notification service are defined in the Managed Object Model (MOM).
3.1 Emergency Call Charging Profile Configuration
Reporting the received emergency call notifications (start or stop) to OCS is enabled by setting the mtasChargingProfileEmergencyCall attribute in the MtasChargingProfile MO to 1 (Online charging). If the mtasChargingProfileEmergencyCall is set to 0 (No charging), the received emergency call notifications are handled by MTAS but not reported to the OCS.
3.2 Service Data Configuration
No service data for the Emergency Call Notification service is not configured in the operator or subscriber part of the subscriber data.
4 Performance Management
For measurements, related to the Emergency Call Notification service, refer to Managed Object Model (MOM).
5 Fault Management
For alarms, related to the Emergency Call Notification service, refer to MTAS Alarm List.