Name convention
CDRF5_<CompanyNumber>_<DateTime>_<SEQNO>.DAT
| Names Component | Description |
|---|---|
| CompanyNumber | The company number in PayEx ledger system |
| DateTime | Date created in format YYYYMMDDHHMMSS |
| SEQNO | Unbroken serial number sequence. |
| [LABEL] | If label is used |
For example:
Example without [<LABEL>]: CDRF5_9999_200101124405_00001.DAT
Example with [<LABEL>]: CDRF5_9999_200101124405_00001[GSM].DAT
<label> is used in order to give the files a describing text according to [<text>] (text within []) where <text> can be maximum 20 characters. This is not obligatory but notice that <label> is set up per company so then all product files delivered from company must have <label>.
Change log
| Version | Date | Description | Created by |
|---|---|---|---|
| 1.4 | 2019-10-29 | Created document | Daniel Olsson |
General information and explanation of records
CDRF5 format is used to send rated usage to the Payex Billing System.
This file is used in combination with a destination file (DP without pricelists) with corresponding usage codes to connect the rated CDRs to a usage type defined in the PayEx Billing system.
If the call scenarios in CDR file (CPI) contains content services or roaming, additional information must be provided in separate files.
Format description
The file is semicolon-separated.
The format field is written in the way that numerical values are written as N and alphanumerical characters are written as X. where ”n” is the maximum number of characters/digits or in certain cases number of characters that must exist.
Maximum nr of records in file, excluding header and trailer, are 9 999 999 or maximum size of CDR-file is 100 Mb.
Use the first occurrence of the above limits.
Header- and Trailer-record are allowed only once. Multiple usage-records are allowed.
H - Header record
| Field name | Field no. | Format | Type | Description |
| Transaction type | 1 | H | Req | Header record |
| Company number | 2 | N(15) | Req | The company number you receive from PayEx |
| Company name | 3 | X(40) | Req | Your company name |
| Created date | 4 | N(10) | Req | YYYY-MM-DD |
| Created time | 5 | N(8) | Req | HH:MM:SS |
Example on the records appearance.
H;1234;Company;2019-01-01;12:20:00
U - Usage record
| Field name | Field no. | Format | Type | Description |
| Recordtype | 1 | U | Req. | U for usage record |
| Customer-number | 2 | N(15) | Req. | Same as in the customer-file |
| A-number | 3 | N(15) | Req. | The subscribers telephone number (MSISDN) |
| Specification text | 4 | X(60) | Req. | Text for presentation on the detailed specification. |
| Date of service | 5 | N(8) | Req. | Timestamp. YYYYMMDD |
| Start time | 6 | N(6) | Req. | Timestamp. HHMMSS |
| Volume | 7 | N(14) | Req. | Duration |
| Charged volume | 8 | N(14) | Req. | Charged duration |
| Volume code | 9 | X(3) | Req. | See table “Volume code” |
| Total charge | 10 | N(7).(3) | Req. | Total charge including start fee |
| Start fee | 11 | N(7).(3) | Req. | |
| Tax Rate | 12 | N(2).(2) | Req. | Only positive values are allowed. |
| Usage code | 13 | X(15) | Req. | Same as in the BDP01-file |
| Network prefix code | 14 | X(5) | Number portability code | |
| Charge per charging unit code | 15 | N(7).(3) | Only positive values are allowed | |
| Charging unit code | 16 | X(3) | See table “Charging unit code” | |
| Charging interval | 17 | N(7) | If charging interval is other than 1s or 1Kb. Otherwise leave empty. | |
| Content provider ID | 18 | X(30) | See separate comment | |
| Orig/Term Network | 19 | X(5) | The PLMN-code if roaming. See separate comment | |
| Free text | 20 | X(40) | ||
| Tariff | 21 | N(1) | Req. | Unknown/Not applicable = 0, OffPeak = 1, Peak = 3 |
| CDRID | 22 | N(20) | Req | Unique cdrid Maximum value 263 |
| Reserved | 23 | Reserved | Reserved for future use | |
| Reserved | 24 | Reserved | Reserved for future use | |
| Reserved | 25 | Reserved | Reserved for future use |
Example:
U;123;0498202000;0498202040;20080101;070001;52;52;S;0.500;0.250;25.00;ID1;;;;;;;;3;1;;;
T - Trailer record
| Field name | Field no. | Format | Type | Description |
| Recordtype | 1 | T | Req.. | Trailer record |
| Number of records | 2 | N(8) | Req.. | Total number of records including header and trailer |
Example:
Example on appearance
H;1234;Firm;2019-05-23;12:20:00
U;123;0498202000;0498202040;20090101;070001;52;52;S;0.500;0.250;25.00;ID1;;;;;;;;3;1;;;
U;123;0498202000;0498202040;20190102;070001;52;60;S;0.500;0.250;25.00;ID1;;;;60;;;;3;2;;;
T;4
Additional information Volume code -field
Describes the Volume code for the column “Volume”, column “Charge volume” and column “Charging interval”
| Volume code | Description |
| S | Seconds |
| E | Event |
| B | Byte |
| KB | Kilobyte |
| MB | Megabyte |
Additional information Charging unit code -field
Describes the Charging unit code for the column Charge per charging unit code.
| Charging unit code | Description |
| MIN | Minute |
| E | Event |
| B | Byte |
| KB | Kilobyte |
| MB | Megabyte |
| N/A | Unknown unit |
Additional information Content provider ID -field
This field is used when there is a content service scenario. For example pay call scenario or number inquiry scenario, where presentation of content provider information is required on invoice.
The id provided should refer to a service access which is provided to the PayEx Billing system in separate content provider information files.
If sent in content provider id is missing in content provider information collection, the CDR will be retained until valid content provider information has been processed.
Example CDR:
U;58;123456;09391119169;20190812;100646;89;89;S;50.000;0.000;25.00;CONTVOICE;;0.000;N/A;;E0067426;;;1;80000101;;;
Example from external content provider information file:
H;SOME_SOURCE_CPI;2019-08-22 14:33:00;1
P;P0000677;165592056930;042-4990444;willmax.dialog@hotmail.com;;SE55920569301;Willmax AB;;;;;
A;P0000677;E0067426;09391119169;2019-07-11 00:00:00;;Tarotcoachen;
T;1;1
Additional information Orig/Term Network -field
This field is used when there is a roaming call scenario. The PLMN code submitted, will be matched towards existing billing system collection of roaming operators.
If PLMN code is missing in the PayEx Billing system collection, the CDR will be retained until collection is updated. Therefore a parallel process where continuous update of the collection is needed when new roaming operators are added in network.