CDRs can be downloaded for messages submitted to the platform by customers and for messages submitted to suppliers by the platform. The date/time range, customer, supplier or customer-supplier combination can be specified for the CDRs produced.

CDRs are generated for database records that are updated within 15 seconds of message submission or message state being updated.

CDRs can be downloaded from the Reports > CDRs and Reports > CDRs > Advanced section of the SSG Admin Portal.

Customer CDRs

Download CDRs based on customer who submitted messages.

The following types of CDR can be produced:

Type	Description
Completed messages	Only messages that have reached a final state (delivered or undeliverable) are included in the CDRs.
All messages	All messages regardless of state are included in the CDRs.
Pending messages	Only messages that have not yet reached a final state are included in the CDRs.
Failed messages	Only messages that have reached the undeliverable final state are included in the CDRs.

CDR format:

ts_completion, svc_node, esme_msg_id, customer, system_id, ts_esme_submit, srcton, srcnpi, srcaddr, msisdn, country, network, status, error, ts_dlr_ack, revenue_val, revenue_cur, registered_delivery, data_coding, esm_class, type, short_message, short_message_raw

Supplier CDRs

Download CDRs based on supplier to where messages were submitted.

CDR format:

ts_submit, svc_node, esme_msg_id, smsc, system_id, ts_completion, msgid, submit_error, cost_val, cost_cur, network, status, error

Full CDRs

CDRs based on customer who submitted messages and the suppliers to where messages were onward submitted by the platfrom.

CDR format:

ts_completion, svc_node, esme_msg_id, customer, system_id, ts_esme_submit, srcton, srcnpi, srcaddr, msisdn, country, network, status, error, ts_dlr_ack, revenue_val, revenue_cur, registered_delivery, data_coding, esm_class, type, short_message, short_message_raw, ts_submit, smsc, smsc_system_id, msgid, submit_error, cost_val, cost_cur

CDR fields

Field	Description
ts_completion	Timestamp for when message reached final state (i.e. delivered or undeliverable)
svc_node	SSG node to where message was submitted by customer
esme_msg_id	ID of message on SSG node
customer	Identifier for customer
system_id	SMPP system ID used by customer to submit message
ts_esme_submit	Timestamp for when customer submitted message to platform
srcton	Source address TON
srcnpi	Source address NPI
srcaddr	Source address
msisdn	Destination address
country	Country of destination address
network	Network of destination address
status	Delivery status
error	Delivery error (normally as returned by supplier SMSC)
ts_dlr_ack	Timestamp for when customer acknowledged DLR
revenue_val	Price value of message from pricing plan
revenue_cur	Price currency of message from pricing plan
registered_delivery	Registered delivery value as set by customer when message submitted
data_coding	Data coding value as set by customer when message submitted
esm_class	ESM class value as set by customer when message submitted
type	Type of message (inbound/outbound)
short_message	Short message field in text form
short_message_raw	Binary representation of short message field
ts_submit	Timestamp for when platform submitted message to supplier
smsc	Identifier for supplier SMSC to where message submitted
smsc_system_id	SMPP system ID used with the supplier SMSC
msgid	Message ID returned by supplier SMSC
submit_error	SMPP command status returned by supplier SMSC in submit_sm_resp
cost_val	Cost value of message from supplier costs
cost_cur	Cost currency of message from supplier costs