PI CCSCD1=CHG Fails to Assign a New MSISDN if the MSISDN is in a CUG (Closed User Group) (Doc ID 1304033.1)

Last updated on SEPTEMBER 12, 2016

Applies to:

Oracle Communications Network Charging and Control - Version: 3.1.0 and later   [Release: 3.1.0 and later ]
Information in this document applies to any platform.

Symptoms

  Background info

  • Closed User Group

    A CUG (Closed User Group) defines a group of users that use an alternative tariff plan when both the calling and the called numbers are part of the same group. The alternative tariff plan normally reduces the rate of calls or provides free calls.

  • Swap MSISDN with PI command

    Every user in the OCNCC application has a number assigned. It is often referred as the MSISDN or the CLI.

    To be able to easily change the user's MSISDN without having to delete it and recreate it with another number, the OCNCC application provides a PI (Provisioning Interface), that specifically serves this need:, its most basic form is:

    CCSCD1=CHG:MSISDN=1234567890,NEW_MSISDN=0987654321,SYNSTAMP=2010121616311039

    to which the system should reply - if successful - with the following PI response:

    CCSCD1=CHG:ACK,SYNSTAMP=2010121616311039;

    The same user who used to carry number 1234567890 now is associated to number 0987654321.

  Symptom description

If the user is in a CUG, swapping its MSISDN with a new MSISDN using the CCSCD1=CHG PI command does not successfully complete.

This problem will only happen with NCC (Network Charging and Control) software prior to NCC 4.4.1.0.0 from which version the MSISDN swap will be possible.

To the following PI command sent on a PI port:

CCSCD1=CHG:MSISDN=1234567890,NEW_MSISDN=0987654321,SYNSTAMP=2010121616311039

The system will reply with the following PI response on the same port:

CCSCD1=CHG:NACK:69-Could not update CLI, account number or profile for msisdn 123456789,SYNSTAMP=2010121607535541;

In the PI manager main log file, usually /IN/service_packages/PI/tmp/PImanager.log, the following error messages will happen:

Dec 16 16:19:17 PIprocess:2999(3084) Oracle=-2292 CCSCD1_oracle.pcc@2269: : ORA-02292: integrity constraint (CCS_ADMIN.CCS_CUG_R_FK) violated - ch
Dec 16 16:19:17 PIprocess:2999(3084) Error ocurred running C function CCSCD1 in shared library PI_CCSCD1. Output is CCSCD1=CHG:NACK:69-Could not update CLI, account number or profile for  msisdn 1234567890

Important

As of NCC 4.4.0.1.0, the application is more explicit when it fails to swap the MSISDN in such cases. It displays a clear error message:
As of NCC 4.4.1.0.0, the product design has changed and the MSISDN swap for CUG registered numbers is allowed.

Changes

  • The user is included in one or more CUG when the CCSCD1=CHG is used to change the user's MSISDN.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms