Welcome SMS notification update CDR
The Welcome SMS SIBB generates a Notification Update CDR each time a WSMS notification is sent to the subscriber.
| A unique identifier is generated for each Location Update CDR which is present in the Notification CDR to link the two CDRs. |
| Field | Name | Description | ||||
|---|---|---|---|---|---|---|
1 |
|
The MSISDN of the subscriber. This is in Tango internal format. |
||||
2 |
|
The CDR Service ID. This is 67 for the Welcome SMS notification service. |
||||
3 |
|
Denotes the transaction type. possible values
|
||||
4 |
|
Alphanumeric string that displays the ID of the network operator for which the CDR was produced.
|
||||
5 |
|
Normalised MSISDN. |
||||
6 |
|
The UUID for the
|
||||
7 |
|
The date the CDR was generated. Format: |
||||
8 |
|
The time the CDR was generated. Format: |
||||
9 |
|
The name of the container. |
||||
10 |
|
The result code. possible values
|
||||
11 |
|
A short description of the error code. |
||||
12 |
|
The subscriber’s IMSI.
|
||||
13 |
|
The value of the service key received in the request.
|
||||
14 |
|
The Visited Public Land Mobile Network. This is the PLMN on which the mobile subscriber has roamed when leaving his or her HPLMN.
|
||||
15 |
|
The network name as per the location mapping lookup. |
||||
16 |
|
The resolved country name as per location mapping lookup. |
||||
17 |
|
The resolved zone name as per location mapping lookup. |
||||
18 |
|
The delay that is configured for this offer action (notification).
|
||||
19 |
|
The relative position (or sequence number) of the offer action.
|
||||
20 |
|
The HTTP notification response code.
|