101
MSG_PARTS
A count of a message parts per a CDR record. Different cases:
1) a message is splitted by SMSC GW == 1
2) a message is splitted by a peer == 1
3) a message is not splitted and sent as a solid one == a count of parts if we split it
For cases 2 and 3 (that are identical from SMSC GW point of view) we need to calculate the parameter at delivering time (a new Sms field “msgParts” that is not stored into a database))
102
DVL_MESSAGE_ID
A messsageID that is used at SMPP protocol when sending a message to a peer. Only for SMPP terminated messages.
A new Sms field “dlvMessageId” that is not stored into a database
103
RECEIPT_LOCAL_MESSAGE_ID
For DLR receipt – an original messageId that was used in the original message in field MESSAGE_ID (for correlation between an original message and DLR)
1) Reuse of – Sms.receiptLocalMessageId field - for DLR transit
2) reuse Sms.messageId field – for local originated DLR
104
MPROC_NOTES
An extra info that “mproc rules” application may put here
create Sms.comment fileld (must be stored in a reserved fild in the database)
105
CHAR_NUMBERS
A number of characters of a sending message. We will calulate it when CDR sending. This means a number of characters per a CDR record.
106
ORIGINATION_TYPE
A message origination: SMPP, SS7_MO, SS7_HR, SIP, HTTP
reuse of a field: sms.originationType
107
MESSAGE_TYPE
A message type: message, dlr
we need to create a new field or reuse of sms. receiptLocalMessageId
Extra configuring:
1) we need to add an extra general config parameter - “Generating of CDRs for temporary failures” (true for default) – to prevent of logging of non final records (for ESME case: partial_esme, success_esme,failed_esme will be generated and “temp_failed_esme” not)
We need to add following CDR fields:
101 MSG_PARTS A count of a message parts per a CDR record. Different cases: 1) a message is splitted by SMSC GW == 1 2) a message is splitted by a peer == 1 3) a message is not splitted and sent as a solid one == a count of parts if we split it For cases 2 and 3 (that are identical from SMSC GW point of view) we need to calculate the parameter at delivering time (a new Sms field “msgParts” that is not stored into a database)) 102 DVL_MESSAGE_ID A messsageID that is used at SMPP protocol when sending a message to a peer. Only for SMPP terminated messages. A new Sms field “dlvMessageId” that is not stored into a database 103 RECEIPT_LOCAL_MESSAGE_ID For DLR receipt – an original messageId that was used in the original message in field MESSAGE_ID (for correlation between an original message and DLR)
1) Reuse of – Sms.receiptLocalMessageId field - for DLR transit 2) reuse Sms.messageId field – for local originated DLR 104 MPROC_NOTES An extra info that “mproc rules” application may put here
Extra configuring:
1) we need to add an extra general config parameter - “Generating of CDRs for temporary failures” (true for default) – to prevent of logging of non final records (for ESME case: partial_esme, success_esme,failed_esme will be generated and “temp_failed_esme” not)