On 26.09.2006, at 14:28, Ben Suffolk wrote:
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.
When you say the DLRs have the IDs in them, do you mean I can get
at them already, or that it would be relatively easy to add them
into the code for the URL call back as they exist in the internal
data structure for the DLR?
the message text in a SMPP dlr contains the ID
same is true for EMI / UCP. Just takes a bit of parsing to break them
out of a message like
"The mesage 1233456789 to 012345 has been delivered at 00:11:22"
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).
I can see that, and as long as you can access it via the DLRs then
its not really that much of an issue.
Regards
Ben
