Contents
1 Introduction
This document describes how to configure the Network Application Server (NW AS) Precondition Interworking Function (IWF) service in MTAS.
1.1 Prerequisites
It is assumed that the user of this document is familiar with the Operation and Maintenance (O&M) area, in general.
1.1.1 Licenses
No license is required.
1.1.2 Documents
Before starting any procedure in this document, ensure that the following documents are available:
1.1.3 Conditions
Before starting any of the procedures in this document, ensure that an Ericsson Command-Line Interface (ECLI) session in Exec mode is in progress.
2 Overview
The NW AS Precondition IWF service provides communication interworking SIP signaling between endpoints with missing precondition capability support.
Current version of precondition IWF service supports Quality of Service (QoS) precondition SIP signaling for the terminating User Equipment (UE), which does not support QoS preconditions. Originating UE lacking the precondition support is not supported in the current release.
If terminating UE lacks the precondition support, it is identified by the following:
- A predefined list of called party number ranges not supporting QoS preconditions
- An indication of no support for precondition capabilities, such as SIP supported or Require header does not carry precondition tag, appears on the receipt of 18x (183 or 180) message from terminating side.
The precondition service does not act on any messages if the terminating endpoints support precondition capabilities.
3 Precondition IWF Service Configuration
The NW AS Precondition IWF service is controlled by the MtasPrIw Managed Object Class (MOC).
The Managed Object (MO) structure of the NW AS Precondition IWF service is shown in Figure 1.
For configurable MOs and attributes related to the NW AS Precondition IWF service, refer to Managed Object Model (MOM).
3.1 Precondition IWF Administrative State Configuration
The Precondition IWF service is enabled by setting the mtasPrIwAdministrativeState attribute in the MtasPrIw MO to 1 (Unlocked). If the mtasPrIwAdministrativeState is set to 0 (Locked), no Precondition IWF service is provided by the NW AS.
3.2 Predefined Number Range Configuration
The Precondition IWF service can be configured with the predefined number ranges in SIP domain of called party that does not support Preconditions capability by setting the mtasPrIwBnumRangeWithoutPrecond attribute in the MtasPrIw MO.
The mtasPrIwBnumRangeWithoutPrecond attribute defines the list of numeric strings with left string match with wildcard support. With this configuration, Originating Precondition IWF is enhanced with knowledge about called party in SIP domain with no support for preconditions and Precondition IWF signaling applied for those called parties by NW AS. For example, the following:
- mtasPrIwBnumRangeWithoutPrecond: 464
- mtasPrIwBnumRangeWithoutPrecond: 498
With above configuration call made to 464xxxx or 498xxxx will be subject to QoS Precondition by Precondition IWF.
3.3 Service Data Configuration
This service does not require any service level subscription from operator or user.
3.4 Media Resource Configuration
The precondition IWF service requires configuration of media resources for temporary media anchoring until originating QoS preconditions are fulfilled. For information on how to configure media resources, refer to MTAS Media Control Management Guide.
4 Performance Management
For information on measurements, related to the NW AS Precondition IWF service, refer to Managed Object Model (MOM).