SMS Services
DN File Download Procedure
Document History
Issue Date Author Description
-1-
Objective
This document outlines the process flow on how CP can obtain an offline daily DN report from
Celcom CMP system.
The daily DN report will enable CP to determine the status of all the content transactions that were
sent through CMP to Celcom’s subscribers.
Implementation
Celcom CMP
• CMP System generate daily DN report for every CP and their respective short code and to
be store on the designated Celcom’s server according to their specific folder.
• Offline DNs for all transactions for the day will be generated starting 12:00 midnight and
expected to complete by 6:00 am.
CP – Daily activities
CMP daily DN report will be archived up to a maximum of 30 days, after which it will be purged
from the server.
-2-
Process Flow
CMP
System
FTP
Push
Celcom
FTP Server
DN Report
FTP Pull
CP
DN FTP Server
The detail for the Celcom’s designated server is as below:
-3-
The following format will be used for the CP DN report folder/file naming in the FTP server.
Annex:
This document provides detail explanation on the events recorded in the Detail DN Report with
examples.
CP TX ID - Transaction ID sent by CP
The below are some common events seen on the Detail DN Report with the explanation of each
events.
Example 1
This shows for CP TX ID 3984653 the message was DELIVERED to subscriber and the DN was
DELIVERED to CP.
Example 2
-4-
CP TX ID MESSAGE STATUS DN STATUS
4003183 DN_DELIVERED STATUS_FAILED
This shows for CP TX ID 4003183 the message was DELIVERED to subscriber and the DN was
NOT DELIVERED to CP.
Example 3
This shows for CP TX ID 4015061 the message was DELIVERED to subscriber and status of DN
is STATUS_NOT_AVAILABLE (i.e unable to identify if the DN was DELIVERED or NOT
DELIVERED to CP)
Example 4
This shows for CP TX ID 4015061 the message was DELIVERED to SMSC and status of DN is
DN_WAITING (i.e DN is pending from SMSC, and this may take up to 24 hours).
Example 5
This shows for CP TX ID 3988039 the message was NOT DELIVERED to subscriber and the DN
was DELIVERED to CP.
Example 6
This shows for CP TX ID 4009319 the message was NOT DELIVERED to subscriber and the DN
was NOT DELIVERED to CP.
Example 7
-5-
This shows for CP TX ID 4009319 the message was NOT DELIVERED to subscriber and the DN
Transaction Status is STATUS_NOT_AVAILABLE (i.e unable to identify if the status was
DELIVERED or NOT DELIVERED to CP).
Example 8
This shows for CP TX ID 4051497 the message was NOT DELIVERED to subscriber because of
InsufficientBalance and Transaction Status is STATUS_NOT_AVAILABLE (i.e unable to identify
if the status was DELIVERED or NOT DELIVERED to CP)
Example 9
This shows for CP TX ID 4051497 the message was NOT DELIVERED to subscriber because of
ORIGINATOR_BARRED (equivalent to PSAChargeFailure) and Transaction Status is
STATUS_NOT_AVAILABLE (i.e unable to identify if the this status was DELIVERED or NOT
DELIVERED to CP).
Example 10
This shows for CP TX ID 4051497 the message was NOT DELIVERED to subscriber because of
failure in sending to SMSC and Transaction Status is STATUS_NOT_AVAILABLE (i.e unable to
identify if the this status was DELIVERED or NOT DELIVERED to CP).
Example 11
This shows for this message the CP TXN ID is unknown and the message was DELIVERED to
subscriber and the DN was not DELIVERED to CP.
Example 12
-6-
UNKNOWNCMPTXID DN_NEGATIVE STATUS_FAILED
This shows for this message the CP TXN ID is unknown and the message was NOT DELIVERED
to subscriber and the DN was not DELIVERED to CP.
-7-