1 Introduction
This document describes how to configure the Originating Calling Name Identity Presentation (OCNIP) and the Calling Name Identity Presentation (CNIP) service in the 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 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)
- MTAS Service Management Guide
- MTAS Supplementary Service Codes Management Guide
- NameDb
1.1.2 Conditions
The following condition must apply:
An Ericsson Common Command-Line Interface (ECLI) session in Exec mode is in progress.
To change the administrative state of the OCNIP service, the following conditions must apply:
- The mtasIdPresAdministrativeState attribute must be unlocked, refer to MTAS Service Management Guide.
To change the administrative state of the CNIP service, the following conditions must apply:
- The mtasIdPresAdministrativeState attribute must be unlocked, refer to MTAS Service Management Guide.
- If mtasIdPresCnipProtocol is 0 (SOAP), then mtasIdPresDbUri attribute must contain a valid URI.
- If mtasIdPresCnipProtocol is 1 (SIP), then mtasIdPresCnipServerName attribute must contain a valid address of Calling Name Server (CNS).
- Note:
- When mtasIdPresCnipProtocol is set to SIP (1), MTAS still behaves as if SOAP (0) is set. This is for future use.
2 Overview
The purpose of the OCNIP as well as the CNIP service is to alter the originating identity presented in a communication based on the preferences of the participants. These services are managed by the operator and not by the end user..
The OCNIP is an originating service that retrieves the callers display name from already provisioned subscribers data and inserts this in the outgoing SIP signalling from the originating MTAS.
The CNIP is a terminating service that retrieves the caller's display name from the CNS and inserts this in the outgoing SIP signalling from the terminating MTAS.
There are two categories of configuration on node level:
For more information on service management of the Identity Presentation, refer to MTAS Service Management Guide.
For more information on supplementary service codes, refer to MTAS Supplementary Service Codes Management Guide.
It is the administrative state of the OCNIP or CNIP function that decides if the function is activated (Unlocked) or deactivated (Locked).
The OCNIP service replaces the display name portion of the originating user identity with a name retrieved from the subscriber data.
- Note:
- Provisioning of display name in the subscriber data is outside the scope of this document.
The CNIP service replaces the display name portion of the identity information in the From and PAI headers of the originating participant with the retrieved calling name from an external database CNS.
Both OCNIP and CNIP services can operate in one of the two modes, where the operator can control when to query the name database CNS:
- always: In this mode, the CNS is always queried or the provisioned display name always used.
- interrogate-on-unavailability: In this mode, the CNS is only queried or the provisioned display name only used when the display names are absent in both the From and P-Asserted-Identity headers.
The operator can control whether the query to the CNS or use of provisioned display name is to take place always or only when both the From and P-Asserted-Identity display names are absent from the request.
The amount of time that the MTAS waits for the CNS to answer a query can be controlled by the mtasIdPresCnipTimeout attribute.
The CNIP function relies on the Web Services interface to perform the queries to the CNS.
For more information about the Web Services, refer to the following document:
3 Configure OCNIP or CNIP Service
The following sections describe how to configure the OCNIP or CNIP service.
3.1 Activate OCNIP or CNIP Service
To be able to activate the OCNIP or CNIP service, the mtasIdPresAdministrativeState attribute must be unlocked. For CNIP, a valid URI for the mtasIdPresDbUri attribute must exist.
For more details, refer to MTAS Service Management Guide, and Managed Object Model (MOM).
To activate the OCNIP or CNIP service:
- Navigate to the MtasIdPres MO.
- Set the mtasIdPresOcnipAdminState or mtasIdPresCnipAdminState attribute to 1 (Unlocked).
- Click Submit.
- Perform a backup. For more information, refer to Create Backup.
3.2 Deactivate OCNIP or CNIP Service
To deactivate the OCNIP or CNIP service:
- Navigate to the MtasIdPres MO.
- Set the mtasIdPresOcnipAdminState or mtasIdPresCnipAdminState attribute to 0 (Locked).
- Click Submit.
- Perform a backup. For more information, refer to Create Backup.
3.3 Modify OCNIP or CNIP Mode
The mtasIdPresOcnipMode and mtasIdPresCnipMode attributes allow control of when to query the name database CNS in CNIP and if provisioned display name is used in OCNIP.
The value 1 indicates mode always and the CNS is always queried (CNIP) or subscriber data display name is always used (OCNIP). When in mode interrogate-on-unavailability, that is, value 0, the CNS is only queried (CNIP) or the provisioned display name is only used (OCNIP), when the display names are absent in both the From and P-Asserted-Identity headers.
To modify the OCNIP or CNIP mode:
- Navigate to the MtasIdPres MO.
- Set the mtasIdPresCnipMode / mtasIdPresOCnipMode attribute to either 0 (Interrogate-on-unavailability) or 1 (Always).
- Click Submit.
- Perform a backup. For more information, refer to Create Backup.
3.4 Modify CNIP Time-out
The mtasIdPresCnipTimeout attribute sets the amount of time that the MTAS waits for the CNS to answer a query. The default value is 500 ms.
To modify the time-out attribute:
- Navigate to the MtasIdPres MO.
- Set the mtasIdPresCnipTimeout attribute to a new value within the range 200-5000.
- Click Submit.
- Perform a backup. For more information, refer to Create Backup.
3.5 Calling Name Server Redundancy
MTAS supports DNS-based redundancy of the CNS, for SOAP/HTTP protocols.
The following events can trigger failover to another CNS server:
- The CNIP Time-out timer attribute mtasIdPresCnipTimeout expires.
- HTTP Error 404 or 503 is received from the CNS.
- A communication error between MTAS and CNS occurs.
When one of the failure situations is encountered and there is alternative CNS address received from the DNS, the request is resent to the alternative Server, the CNIP Time-out timer is restarted, and the mtasFuncFailover Performance Management (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.
For more information about DNS configuration, refer to Managed Object Model (MOM).
3.6 Select IP Protocol Version
The mtasIdPresDbIpVersion attribute sets the IP protocol version of the SOAP interface NameDb.
To modify the IP version attribute:
- Navigate to the MtasIdPres MO.
- Set the mtasIdPresDbIpVersion attribute to 0 (IPv4) or 1 (IPv6).
- Click Submit.
- Perform a backup. For more information, refer to Create Backup.
3.7 Modify Default Display Name
The mtasIdPresDefaultDisplayName attribute defines the default display name (for example, "Unavailable") that is copied to the FROM/PAI header(s) in the outgoing SIP signalling when there is no display name available for OCNIP or CNIP, or when OCNIP or CNIP is disabled.
To modify the default display name attribute:
- Navigate to the MtasIdPres MO.
- Set the mtasIdPresDefaultDisplayName attribute to a new value.
- Click Submit.
- Perform a backup. For more information, refer to Create Backup.
3.8 Modify Privacy Display Name
The mtasIdPresPrivacyDisplayName attribute defines a display name (for example, "Restricted") that is copied to the FROM/PAI header(s) in the outgoing SIP signalling when privacy is requested or the Calling Name Server returns the information that the Calling Name Status is Restricted for OCNIP or CNIP.
To modify the privacy display name attribute:
- Navigate to the MtasIdPres MO.
- Set the mtasIdPresPrivacyDisplayName attribute to a new value.
- Click Submit.
- Perform a backup. For more information, refer to Create Backup.
3.9 Modify Oir Override Skip Query
The mtasIdPresCnipOirOverrideSkipQuery attribute defines whether the query to the name database (CNS) is to take place when OIR override is active. The default value is 0, that is, the query is done when OIR override is active.
To modify the Oir Override Skip Query attribute:
- Navigate to the MtasIdPres MO.
- Set the mtasIdPresCnipOirOverrideSkipQuery attribute to either 0 (query is done) or 1 (query is not done when OIR override is active).
- Click Submit.
- Perform a backup. For more information, refer to Create Backup.

Contents