MTAS Parlay X Management Guide
MTAS

Contents

1Introduction
1.1Prerequisites

2
Overview
2.1Call Notification
2.2Third-Party Call
2.3External Parlay X Application Server Redundancy
2.4Subfunctions
2.5Interaction with Other Services

3
Parlay X Configuration
3.1Call Notification
3.2Third-Party Call
3.3Change Local Port
3.4Service Data Configuration
3.5Select IP Protocol Version

4
Performance Management

5
Fault Management

1   Introduction

This document describes how to configure the Parlay X 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 Parlay X services, the Parlay X license must be installed.

For more information about the Parlay X 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

This document describes the Parlay X services that the MTAS offers to its subscribers. The Parlay X service is not part of the MMTel service format, they execute in a separate Parlay X service format.

The MTAS partly supports two Parlay X interfaces. For 3GPP Call Notification standard, refer to 3GPP TS 29.199-02 Open Service Access (OSA); Parlay X web services; Part 2: Third party calland for Third-Party Call 3GPP standard, refer to 3GPP TS 29.199-02 Open Service Access (OSA); Parlay X web services; Part 3: Call notification.

For details about the support, refer to Parlay X MMTEL Extensions.

Call Notification enables a Parlay X application, external to MTAS, to translate the originally called party number into a new target number.

Third-Party Call enables a Parlay X application, external to MTAS, to initiate a call setup between two parties.

2.1   Call Notification

The Parlay X Call Notification interface in MTAS operates on number ranges. These number ranges must be provisioned as CSCF triggers. When a called number is within a provisioned range, a CSCF trigger fire and direct the call to a port in MTAS that is configured to handle this number range. For details about configuration, related to Parlay X, see Section 3.

2.2   Third-Party Call

Charging for the use of the Third-Party Call interface relies on that a user, representing the Parlay X application that initiates the Third-Party Call, is provisioned in the HSS. This user is charged for the two outgoing calls created by the Third-Party Call interface, using the data provisioned for this user. MTAS supports using the Third-Party Call interface without any user representing the Parlay X application defined in the HSS. In this case, no charging for using the Third-Party Call interface.

2.3   External Parlay X Application Server Redundancy

MTAS supports DNS-based redundancy of the External Parlay X Application Server in relation with the Call Notification interface.

The following failure situations exist:

When one of the failure situations are encountered, and there is alternative Parlay X Application Server address received from DNS, the request is resent to the alternative Server, the Parlay X request timer is restarted, and the mtasFuncFailover PM counter is stepped.

If a communication error occurs, the failed server is put on the blacklist for the time duration specified by CM attribute IcmpBarringTime. (If the network error is detected by receiving an ICMP Destination Unreachable (3) packet with net unreachable (0), host unreachable (1), protocol unreachable (2), port unreachable (3) reason, or ICMP Parameter Problem (12) packet) or by CM attribute mtasFunctionBlackListTime (any other reason). While the server is on the blacklist, new requests cannot be received.

2.4   Subfunctions

There are no subfunctions included in the Parlay X service.

2.5   Interaction with Other Services

There is no interaction with other services.

3   Parlay X Configuration

The Parlay X service is controlled by the MtasParlayX Managed Object (MO). The MtasParlayX MO has a child, MtasParlayXBehaviourProfile, that can be referenced by an instance of a MtasParlayXCallNotificationService.

An overview of the Parlay X MO structure is shown in Figure 1.

Figure 1   Parlay X MO Structure

For configurable MOs and attributes related to general Parlay X configuration, refer to Managed Object Model (MOM).

3.1   Call Notification

The Call Notification interface is controlled by the MtasParlayXCallNotification MO and the instances of the MtasParlayXCallNotificationService MO. A Call Notification service can reuse a certain behavior by referencing a MtasParlayXBehaviourProfile.

Figure 2   Call Notification MO Structure

For configurable MOs and attributes related to the CallNotification interface, refer to Managed Object Model (MOM).

3.2   Third-Party Call

The Third-Party Call interface is controlled by the MtasParlayX3pcc MO.

Figure 3   Parlay X MO Structure

For configurable MOs and attributes related to the Third-Party Call interface, refer to Managed Object Model (MOM).

3.3   Change Local Port

Note:  
This procedure is also affect the HTTP Cr interface used in the External MRFC.

To change the local HTTP port, do the following:

  1. Deactivate the MtasFunction MO, as described in the following document:MTAS Node Management Guide.
  2. Check that the mtasFunctionAdministrativeState attribute is set to 0 (Locked).
  3. Navigate to the MtasWebServices MO.
  4. Change the following parameter:
    • mtasWebServicesLocalPort

    For a complete description of the parameters, refer to Managed Object Model (MOM).

  5. Click Submit.
  6. To open traffic for a new port number, remove VIP Mappings for old UDP and TCP port number, and then insert VIP Mappings with the same data for the new UDP and TCP port number. This process is for the used IPv4 or IPv6 protocol.
    For information on VIP Mappings, refer to Virtual IP Address Management.
  7. Perform a backup, as described in the following document: Create Backup.

3.4   Service Data Configuration

This section describes how to configure the service data.

3.4.1   Operator Subscription Level Service Configuration

No service data for Parlay X is configured in the operator part of the subscriber data.

3.4.2   Subscriber Subscription Level Service Configuration

No service data for Parlay X is configured in the subscriber part of the subscriber data.

3.5   Select IP Protocol Version

The mtasParlayXIpVersion attribute sets the IP protocol version.

To modify the IP version attribute, do the following:

  1. Navigate to the mtasParlayX MO.
  2. Set the mtasParlayXIpVersion attribute to 0 (IPv4) or 1 (IPv6).
  3. Click Submit.
  4. Perform a backup, as described in the following document: Create Backup.

4   Performance Management

For measurements related to the Parlay X service, refer to Managed Object Model (MOM).

5   Fault Management

For alarms related to the Parlay X service, refer to MTAS Alarm List.



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 Parlay X Management Guide         MTAS