SPCM subscriber lifecycle CDR
The SPCM generates subscriber lifecycle CDRs for creating, updating, and deleting subscribers.
Subsections include:
Field | Name | Description | ||||
---|---|---|---|---|---|---|
1 |
|
The MSISDN of the subscriber in Tango format. |
||||
2 |
|
The Tango service ID. This is 38 for SPCM subscriber lifecycle CDRs. |
||||
3 |
|
The CDR transaction type. types
|
||||
4 |
|
Alphanumeric string that displays the ID of the network operator for which the CDR was produced. |
||||
5 |
|
Date the CDR was generated. Format: |
||||
6 |
|
Time the CDR was generated. Format: |
||||
7 |
|
The subscriber’s IMSI.
|
||||
8 |
|
The payment method used for the plan purchase. possible values
|
||||
9 |
|
The subscriber class name provisioned to a subscriber.
|
||||
10 |
|
The language provisioned to a subscriber.
|
||||
11 |
|
The subscriber’s status. possible values
|
||||
12 |
|
A flag that indicates if the subscriber is a member of a group. possible values
|
||||
13 |
|
The subscriber group identifier. |
||||
14 |
|
A flag that indicates if the subscriber is eligible for dynamic discounts. possible values
|
||||
15 |
|
A flag that indicates if the suscriber receives DPS notifications. possible values
|
||||
16 |
|
A flag that indicates whether the subscriber receives EOS notifications. possible values
|
||||
17 |
|
A flag that indicates whether the subscriber recieves PAYG notifications. possible values
|
||||
18 |
|
The subscriber’s home location zone.
|
||||
19 |
|
The subscriber’s renewal date for monthly plans.
|
||||
20 |
|
The subscriber’s QoS category.
|
||||
21 |
|
The subscriber ID. |
||||
22 |
|
This is an optional string that is used to tag certain subscribers for batch updates. You can use whatever string you like to attach to subscribers - maybe `chivas` or `lovesPonyRides`. |
||||
23 |
|
Specifies the original MSISDN of the subscriber. NOTE: This field is only populated when the transaction type is |