[RFC] Mapping message ID (SMPP)
Rachman Chavik <[email protected]>
| Newsgroups | gmane.comp.mobile.kannel.devel |
|---|---|
| Message-ID | <[email protected]> |
Dear all, I have an application that connects to bearerbox and directly sends Msg through it. The application generates its own message id for the Msg. Bearerbox will then terminate the message using its smsc connection. Using cvs-20030404, I find that upon receiving a DLR message, bearerbox does forward the DLR message back to the application. So, I'm quite happy. However, I need to map the message id in the DLR (given by SMSC) back to the original message id generated by my application. I will need to map the other tuples as well, but the critical part now is to map the message id. I have done some investigation and work on this issue, and my approach is as follows: 1. Add a new tuple in Msg definition to store the original message. 2. Upon receiving the new message, create new entry in a dictionary storing the original id with key: submit_sm_resp.message_id 3. Upon receiving deliver_sm (with DLR), parse the message id from the deliver_sm.short_message ; lookup the original ID from the dictionary and replace the id portion of the short_message. My hangup about this is that I have modify the Msg structure. Furthermore, this is only SMPP specific. What do you guys think of this approach? Does anyone want this capability in the standard bearerbox? If anyone's interested, I could send patch. Thanks and best regards, Rachman.