I actually share this view. Having the SMSC's ID in hand can help a
lot in such cases, especially when you dont want to go though
gigabytes of logs. But the delivery reports have the ID's in them and
this is the only feedback mechanism we have towards the sender.
What for sure would be a big hassle is if we have to provide on the
HTTP answer because at that point in time we dont have the message id
in our hand (as we have not submitted the message yet).
On 23.09.2006, at 16:07, Ben Suffolk wrote:
@Ben: can you describe a senseful scenario for this need?
Sure,
Let suppose you are sending reverse billed SMS messages, i.e. ones
that you should get a share of the revenue from the operator for.
At the end of the charging period they tell you how many chargeable
message you sent. When you reconcile this with the number you
actually sent, the chances of it matching are slim. If you have the
DLR with the operators assigned ID you are then able to add a
little more weight to your argument that supports your message
counts not theirs.
Its would also be useful for other support resolution issues, such
as message that don't get delivered, by having the ID you can pass
it to the operators TS people. Although I guess in this instance
the ID would be available through the DLR table in the ts field.
Regards
Ben
