MTAS Network AS Precondition IWF Management Guide
MTAS

Contents

1Introduction
1.1Prerequisites

2
Overview

3
Precondition IWF Service Configuration
3.1Precondition IWF Administrative State Configuration
3.2Predefined Number Range Configuration
3.3Service Data Configuration

4
Performance Management

1   Introduction

This document describes how to configure the Network Application Server (NW AS) Precondition 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 the following condition is met:

2   Overview

The NW AS Precondition Interworking Function (IWF) service provides communication interworking SIP signaling between endpoints with missing precondition capability support. Current version of Precondition Interworking Function (IWF) service supports the following:

Lack of Precondition support in terminating UE is identified by the following:

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.

Figure 1   NW AS Precondition IWF MO Structure

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:

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.

4   Performance Management

For information on measurements, related to the NW AS Precondition IWF service, refer to Managed Object Model (MOM).



Copyright

© Ericsson AB 2016. All rights reserved. No part of this document may be reproduced in any form without the written permission of the copyright owner.

Disclaimer

The contents of this document are subject to revision without notice due to continued progress in methodology, design and manufacturing. Ericsson shall have no liability for any error or damage of any kind resulting from the use of this document.

Trademark List
All trademarks mentioned herein are the property of their respective owners. These are shown in the document Trademark Information.

    MTAS Network AS Precondition IWF Management Guide         MTAS