Using EMI/UCP protocol is know not to have a unique id to any message.
Infact if your kannel will send more than one message in a single second, ts will confuse the DLR and the reply is not unique.
J
Anand Gupta wrote:
Thx Beckman for taking time to reply.
Well the whole reason for which i want to track the message_id is based on that only. My smsc has the reports available in csv format after 24hrs. Now when the reports come in, how will i know which report is for which message ? There can be multiple sender id, multiple messages to same numbers... This is the reason i was looking for getting the message_id. When kannel sends the message id to mysql db, its strange why it can't send it to the dlr url as well.
I thought about a small hack on this, not perfect though.
The mysql db stores the dlr-url as well which has a unique sequence number called slid. If inside my url php file i search the db using regex with the slid number (since the same number is available inside the php file also as one of the parameters) and then copy the message id from there.
The above is not perfect and nor is efficient for when the messages volume increase, so will the db.
I hope someone else on this list has a better solution.
