SSRV UCIP CDR
The User Communication Interface Protocol (UCIP) CDRs are generated daily and are stored in the /tango/data/cdr/ssrv_ucip.cdr file.
| This is part of the SSRV component of the Subscription Manager. |
| Field | Name | Description | ||
|---|---|---|---|---|
1 |
|
The MSISDN of the subscriber in Tango format. |
||
2 |
|
The Tango CDR Service ID. This is 23 for SSRV UCIP services. |
||
3 |
|
The transaction type. values
|
||
4 |
|
The date on which the UCIP request was submitted. Format = |
||
5 |
|
The time on which the UCIP request was submitted. Format = |
||
6 |
|
The date on which the CDR was created. Format = |
||
7 |
|
The time on which the CDR was created. Format = |
||
8 |
|
Denotes the session ID for this UCIP session. |
||
9 |
|
The transaction type. values
|
||
10 |
|
The language ID used for the subscriber. This is retrieved from a local database or from an external source.
|
||
11 |
|
Denotes the subscriber type. options
|
||
12 |
|
The A number. The number that initiates the communication. |
||
13 |
|
The B number. The number that receives the communication. |
||
14 |
|
The UCIP |
||
15 |
|
Denotes the service name received. |
||
16 |
|
Defines the result string. This comes in strong format. Example 1. example
|
||
17 |
|
The result code received for the request from the IN (if available).
|
||
18 |
|
The result string received for the request from the IN (if available).
|
||
19 |
|
The URL used to invoke the UCIP service. |
||
20 |
|
The time (in milliseconds) to process the request. |
||
21 |
|
The time (in milliseconds) to read the subscriber. |
||
22 |
|
The time (in milliseconds) to save the subscriber data. |
||
23 |
|
The time (in milliseconds) for the |
||
24 |
|
The time (in milliseconds) to read the response string from the database. |
||
25 |
|
The time (in milliseconds) for the SMPP Request to be processed.
|
||
26 |
|
The ending fields of the CDR can contain customer CDR data.
|