Billing and Revenue Management (MOSC)

MOSC Banner

pipeline to identify member service using the subscription service login

edited Apr 13, 2016 5:08AM in Billing and Revenue Management (MOSC) 1 commentAnswered

We configured /service/telco/gsm as subscription service and /service/telco/gsm/telephony 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. Also configured the parent service for TEL as GSM. When we pass the cdr for TEL service we expect the account to 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

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

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

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center