Welcome SMS location update CDR

The Welcome SMS SIBB generates a Location Update CDR each time a location update trigger received. The CDR contains a variable part at the end of the CDR which is configurable.

A unique identifier is generated for each Location Update CDR.

Field Name Description

Subscriber ID

The MSISDN of the subscriber. This is in Tango internal format.

Service ID

The CDR Service ID. This is 66 for the Welcome SMS service.

Transaction Type

Denotes the transaction type. This is 0 for Location Update Triggers.

Tenant ID

Alphanumeric string that displays the ID of the network operator for which the CDR was produced.

MSISDN

The subscriber’s MSISDN in international format.

Location Update Reference ID

The UUID for the Location Update Trigger.

CDR Generation Date

The date the CDR was generated. Format: DD/MM/YYYY.

CDR Generation Time

The time the CDR was generated. Format: hh:mm:ss.

Container Name

The name of the container.

Result Code

The result code.

possible values

0 = Welcome SMS offer available
1 = Subscriber in DND DB
2 = Debounce (subscriber already sent a WSMS for the VPLMN within debounce period).
3 = No matching offer configured on RTE
4 = External subscriber lookup failed
5 = Notification failure
7 = PLMN not found
8 = List Manager Lookup failure

Result Description

Description of the error code.

IMSI

The subscriber’s IMSI.

ServiceKey

The value of the service key received in the request.

An example would be 10a9.

VPLMN

The Visited Public Land Mobile Network. This is the PLMN on which the mobile subscriber has roamed when leaving his or her HPLMN.

An example would be 51709.

Network Name

The network name as per location mapping lookup.

Country Name

The resolved country name as per location mapping lookup.

Zone Name

The resolved zone name as per location mapping lookup.

List Names

A delimited list of ListNames on which the subscriber is present.

An example might be VIP or TOP_SPENDER.

Offer Lookup Status

The offer lookup status.

values

0 = Offer found
1 = No offer

Number of Offer Actions

The number of notifications to be sent to the subscriber as part of the offer.

The number of actions are contained in the offer.

Number of Delayed Offer Actions

The number of notifications to be sent to the subscriber at a later time.

Campaign Name

The name of the campaign that matched this subscriber.

This is blank if there is no campaign.

Offer Name

The name of the offer that matched this subscriber.

This is blank if there is no offer.

Variable part

The Location Update CDR contains a variable part which is configurable.

If you require the variable part, you need to configure the fields that you wish to append to the end of the CDR via the common.properties file typically found at /tango/config/sibb/main/sibbs/service/common.properties.

How do I add the variable part to the CDR?

Navigate to /tango/config/sibb/main/sibbs/service/common.properties.
Set the sibb.cdr.dynamic.format.enabled property to true.
Add the desired fields as a comma-separate list to the sibb.cdr.dynamic.format property.

These fields are keys that are sent in the JSON payload sent to the Subscriber Offer Manager (SOM).

You can see the available JSON key-value pairs in the SIBB logs.

DEBUG com.tango.sibb.common.stages.SomTriggerOffer - [967178860] SOM send request message [{"serviceKey":"123","tenant":"sprint","Lists":"null","planNumber":0,"planList":"|","classificationList":" |","vplmn":"26806","country":"Portugal","region":"WSMS_EU","planType":"data","subscriberClass":"Standard","lang":"en","subscriberType":"postpaid","msisdn":"967178860","timestamp":"20/11/2019 14:36:51","channel":"USSD","trigger":"welcomeSMS","tenantId":"sprint"}]

Variable part example

Let’s say you configured sibb.cdr.dynamic.format=subscriberType,lang.

Field Name Description

subscriberType

The type of subscriber.

This is typically postpaid or prepaid.

language

The language of the subscriber.

These are ISO 639 codes such as en for English and es for Español/Spanish.