Network AS Management Guide
MTAS

Contents

1Introduction
1.1Prerequisites

2
Overview

3
NW AS Configuration
3.1NW AS Administrative State Configuration
3.2NW AS Name Configuration
3.3NW SIP Port Configuration

1   Introduction

This document describes how to configure the Network Application Server (NW AS) in the MTAS. The NW AS node in the the IP Multimedia Subsystem (IMS) provides the interworking SIP signaling between the entities lacking few capabilities. Current version of NW AS supports Quality of Service (QoS) precondition SIP signaling interworking for terminating endpoints, which lack precondition support.

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

To enable the functionality in the NW AS, the NW AS Communication IWF Capacity license must be installed.

For more information about the NW AS Communication IWF 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

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 is an interworking node in the IMS to provide communication interworking SIP signaling between entities that are missing some capabilities. The NW AS acts as a Back-to-Back User Agent (B2BUA) between these entities. Current version supports QoS precondition SIP signaling for the terminating UEs, which does not support QoS preconditions.

This interworking node sits between two UEs and seamlessly fulfills the need of QoS Precondition signaling for terminating UE.

The NW AS is deployed on MTAS as a standalone node and also as collocated.

3   NW AS Configuration

The Communication IWF functionality in the NW AS is controlled by the MtasNw Managed Object (MO).

The NW AS MO structure is shown in Figure 1.

Figure 1   NW AS MO Structure

For MOs and attributes related to the NW AS, refer to Managed Object Model (MOM).

3.1   NW AS Administrative State Configuration

The NW AS is enabled by setting the mtasNwAdministrativeState attribute in the MtasNw MO to 1 (Unlocked). If the mtasNwAdministrativeState is set to 0 (Locked), the NW AS function is not provided by the MTAS.

3.2   NW AS Name Configuration

The NW AS name is configured by setting the mtasNwAsName attribute in the MtasNw MO to define the name of the AS variant in network AS. This configured name is matched with received "as" attribute value in top most route header from the Call Session Control Function (CSCF).

3.3   NW SIP Port Configuration

It is possible to change the SIP port used for SIP Communication IWF traffic in the NW AS.

For configuration of the NW AS SIP port, refer to MTAS SIP Management Guide.



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.

    Network AS Management Guide         MTAS