SIM SWAP Problem - SERVICE_ALIAS_LIST_T Table not Populated Correctly
(Doc ID 2151920.1)
Last updated on APRIL 22, 2024
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 to 7.5.0.15.0 [Release 7.5.0]Information in this document applies to any platform.
Symptoms
On : 7.5.0.11.0 version, Device Management
ACTUAL BEHAVIOR
-----------------------
When a customer swaps the SIM number, the SERVICE_ALIAS_LIST_T table is not populated correctly for one service. It lead to the problem that the customer cannot use the service.
EXPECTED BEHAVIOR
---------------------------
SERVICE_ALIAS_LIST_T table should be populated correctly.
The old SIM number is still present in table along with new SIM number.
Alias List in service object
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create account with telephony and sms service. During that process sim and msisdn numbers are assigned to both services.
2. Open account in Customer Center and under services tab change sim number on both services. Click Save.
Old SIM is disassociated from telephony and gprs services and then new SIM is associated with same telephony and gprs services. The sim is changed but the SERVICE_ALIAS_LIST_T table is wrongly populated..
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |