UNS CDR

The User Notification Service (UNS) which interacts with the USSD SI over the SE interface to send USSD messages to mobile devices has CDRs that are generated and stored in the file: /tango/data/cdr/uns.cdr.

Field Name Description

1

Subscriber ID

The MSISDN of the subscriber in Tango format.

2

Service ID

The Tango CDR Service ID. This is 91 for UNS CDRs.

3

Transaction Type

The CDR transaction type. This is 1 on a successful plan purchase.

4

Tenant ID

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

5

CDR Generation Date

The date the CDR was created. Format: DD/MM/YY.

6

CDR Generation Time

The time the CDR was created. Format: HH:MM:SS.

7

Source Address

The source address of the sending application.

8

Sending User

The MSISDN of the subscriber sending the message.

9

To

The MSISDN of the subscriber sending the message.

10

Message

The notification text.

If the message contains a comma, the comma is rendered as %2C. If the message contains a percentage sign, the sign is rendered as %25.

11

Expiry Date

The date the notification expires. Format: DD/MM/YYYY.

12

Expiry Time

The time the notification expires. Format: HH:MM:SS.

13

Connection ID

This ID identifies the SMPP connection.

14

Sequence Number

The sequence number used in the SMPP PDU sent over the given connection to the SMSC.

This value wraps from 65535.

15

Part Number

Indicates the CDR part.

This only occurs when the message is segmented.

16

Total Parts

The total number of parts in the CDR.

This only occurs when the message is segmented.

17

Request Status

The status of the submit request.

possible values

  • 0 = request sent

  • 1 = request not sent or no response received

  • 2 = request response received

Reasons for values 1 and 2 can be seen in Field 15.

18

Request Fail Reason

The notification failure reason.

See Request Fail Reasons for specific codes.

19

Request Target

Indicates where the notifications are sent.

possible values

  • 0 = SMSC

  • 1 = USSD Gateway

  • 2 = HRG

Sample

UNS CDR Sample
00041000060200000001010001,91,1,tenantb,23/10/2018,12:13:21,0035361501900,0620001101,+0620001101,TEST_1MB_1DAY_FUP pack is purchased on Tue Oct 23 12:13:21 BDST 2018 at Tk1.15 and is not auto renewable and will expire on  Wed Oct 24 00:01:00 BDST 2018.,23/10/2018,13:13:21,5,119749,,,0,0,0

Request Fail Reasons

Request Target 0 (SMSC) and 1 (USSD Gateway)

Code Description

0

No failure.

1

Throttled.

2

Encoding error.

3

No service available.

4

Blackout.

5

Date format error.

6

Integer out of range.

7

Timed out waiting for SMSC response.

8

String is wrong length.

9

Unsupported notification type.

10

Notification type set to none.

11

Service is temporarily overloaded.

12

SMPP DDU send error.

13

Service failure.

14

Timer Start Exception.

16

SE send failure.

Request Target 2 (HRG)

When the Request Target is the HRG (2), the reason will be displayed as follows:

“<hrg http response code>; <server http result code>;
<server result success code>; <server result failure code>”
String Description

<hrg http response code>

Standard HTTP response code.

<server http result code>

Standard HTTP response code.

<server result success code>

The service the HRG returns.

<server result failure code>

The service the HRG returns.