Contents

1   Introduction

This document describes how to configure the Address Policing 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 any of the subservices of the Address Policing service in the MTAS, the Address Policing license must be installed.

For more information about the Address Policing license, refer to MTAS Licenses.

1.1.2   Documents

Before starting any procedure in this document, ensure that the following documents are available:

• Ericsson Command-Line Interface User Guide
• Managed Object Model (MOM)

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 Address Policing service checks the format of the destination address entered by a caller, and rejects the communication attempt if the check fails.

2.1   Subfunctions

The subfunctions included in the Address Policing service are described in this section.

2.1.1   Reject Malformed Address

The Address Policing service rejects the communication if it finds that the destination address does not conform to the required format.

2.1.2   Play Generic Announcement

This subfunction is described in MTAS Generic Announcement Management Guide.

2.2   Subservices

The Address Policing service supports the following subservices:

• Long-distance Mobile Number Policing

2.3   Long-distance Mobile Number Policing

This check is intended for use in countries where mobile numbers are associated with geographic locations, and mobile numbers are distinguished from fixed numbers by the number of digits. It checks that, if the call is to a long-distance mobile number, the caller has included the National Dialing Prefix (NDP) in the destination address.

The following algorithm expresses the check:

IF call is National AND
   destination address doesn’t start with NDP AND
   length of destination address = Length of a mobile number AND
   length of caller’s identity = Length of a fixed number
THEN
    Play announcement
    Reject INVITE
ENDIF

2.3.1   Interaction with Other Services

This section describes the different interactions with other services.

2.3.1.1   Outgoing Communication Barring and Dial Plan

The Long-distance Mobile Number Policing check is performed after the Outgoing Communication Barring (OCB) Global Black List check, and before the OCB Operator Barring Program check.

For more details about OCB, refer to MTAS Barring and Dial Plan Services Management Guide.

2.3.1.2   Communication Diversion

The Long-distance Mobile Number Policing check does not apply to communications which have been diverted by the served Communication Diversion (CDIV) service of the user.

The served user is not involved in the call when it is diverted, and the caller can do nothing to improve the situation, so checking that a long-distance mobile number was entered with the National Dialing Prefix is not helpful.

For more details about CDIV, refer to MTAS Communication Diversion Management Guide.

2.3.1.3   Flexible Communication Distribution

The Long-distance Mobile Number Policing check does not apply to communications which have been sent to another user by the served Flexible Communication Distribution (FCD) service of the user.

The served user is not involved in the call when it is sent to a related user, and the caller can do nothing to improve the situation, so checking that a long-distance mobile number was entered with the National Dialing Prefix is not helpful.

For more details about FCD, refer to MTAS Flexible Communication Distribution Management Guide.

2.3.1.4   Abbreviated Dialing

The Long-distance Mobile Number Policing check applies to communications where the end user dialed an abbreviated number. The Long-distance Mobile Number Policing check is applied to the Abbreviated Dialing (AbDial) stored number.

The numbers are not checked when they are added to the AbDial store.

For more details about AbDial, refer to MTAS Abbreviated Dialing Management Guide.

2.3.1.5   Communication Completion

The Long-distance Mobile Number Policing check does not apply to the Communication Completion (CC) call generated by the CC service to the original called party.

The original call passed the Long-distance Mobile Number Policing check, so there is no need to repeat the check here.

For more details about CC, refer to MTAS Communication Completion Management Guide.

2.3.1.6   Conference

The Long-distance Mobile Number Policing check attempts to add users to an Ad Hoc conference, but the announcement is not played.

Participants are added to an Ad Hoc conference by the Conference Creator by sending the identity in a REFER inside the dialog with the Conference Focus. Long-distance Mobile Number Policing follows the pattern established by the OCB, which runs on the REFER, but never plays an announcement.

For more details about the Ad-hoc conference, refer to MTAS Ad-hoc Conference Management Guide.

3   Address Policing Service Configuration

The Address Policing service is controlled by the MtasAp MO. An overview of the Address Policing MO structure is shown in Figure 1.

Configurable MOs and attributes related to the Address Policing services are defined in Managed Object Model (MOM).

3.1   Configuration Activities

The configuration activities are listed in Table 1.

Table 1    Additional Configuration Activities

Activity	Attribute
Defining the National Dialing Prefix for Address Policing	mtasApNdp
Defining the Length of a fixed number for Long-distance Mobile Number Policing	mtasApLdmnpFixedNumberLength
Defining the Length of a mobile number for Long-distance Mobile Number Policing	mtasApLdmnpMobileNumberLength
Defining which announcement to play if Long-distance Mobile Number Policing rejects a call	mtasApLdmnpAnnouncementName

For more information about the Address Policing attributes, refer to Managed Object Model (MOM).

3.2   Long-distance Mobile Number Policing Administrative State Configuration

The Long-distance Mobile Number Policing subservice is enabled by setting the mtasApLdmnpAdministrativeState attribute in the MtasApLdmnp MO to 1 (Unlocked). If the mtasApLdmnpAdministrativeState is set to 0 (Locked), no Long-distance Mobile Number Policing service is provided by the MTAS.

3.3   Wholesale for Long-distance Mobile Number Policing Configuration

The Long-distance Mobile Number Policing subservice supports the Wholesale service and is configurable on Virtual Telephony Provider (VTP) level.

The Wholesale service for the Long-distance Mobile Number Policing subservice is activated when the following attributes are set to 1 (Unlocked):

• The vtasApLdmnpAdministrativeState attribute in the VtasApLdmnp MO
• The mtasApLdmnpAdministrativeState attribute in the MtasApLdmnp MO

For more information about the Wholesale service, refer to MTAS Wholesale Support Management Guide.

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 the Long-distance Mobile Number Policing subservice is configured in the operator part of the subscriber data.

3.4.2   Subscriber Subscription Level Service Configuration

No service data for the Long-distance Mobile Number Policing subservice is configured in the subscriber part of the subscriber data.

4   Performance Management

Measurements related to the Address Policing services are detailed in Managed Object Model (MOM).

5   Fault Management

Alarms related to the Address Policing service are listed in MTAS Alarm List.