Is It Mandatory for Member Services to Have Login Entry in service_aliast_list_t Table
Last updated on MAY 25, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 7.4.0 to 7.5.0]
Information in this document applies to any platform.
This article it to clarify the question on service alias list entry related to member services and subscription service.
* /service/telco/gsm is configured as subscription service and /service/telco/gsm/telephony is configured as the member service.
* MSISDN is added in the alias list of subscription service.
* Pipeline service code 'GSM' is mapped to /service/telco/gsm service with the event /event/delayed/session/telco/gsm, and the service code TEL is mapped to /service/telco/gsm/telephony with the event /event/delayed/session/telco/gsm/telephony.
* The parent service is configured for TEL as GSM.
When the CDR is passed for TEL service, one would expect the account to be identified using the MSISDN added in the subscription service alias list, but this approach is not working.
What would be the correct configuration for member service to be identified using parent service alias list entry?.
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