Re: non standard message_id breaks DLR

[Jeetendra Singh]

The same problem I also observed from one of my network operator and *interestingly* the operator was on SMPP. But I couldn't find any source of confusion in SMPP docs regarding the same. But seeing so many providers doing the same mistake(???), are we sure?   SMPP specs are very clear in suggesting that a deliver receipt format (Appendix B : Delivery Receipt Format) should contain id in C-Octet String in *decimal* format but same is not true when they specify message id in Submit Response. What is clearly stated is: " message_id is set according to SMSC implementation." Also there's difference in the octet size of message_id in submit_sm_resp(65 Octets) and delivery receipt (10 octets).   Don't take me wrong, am not supporting those SMPP providers but nevertheless I have introduced a configuration parameter in my Kannel code to *support* such providers ;)   regards, JS   ----- Original Message ----- From: Edwin Pratomo To: David Tully ; [EMAIL PROTECTED] Sent: Friday, June 27, 2003 11:18 AM Subject: Re: non standard message_id breaks DLR On Thursday 26 June 2003 18:05, David Tully wrote: > Hi! > > > The middle bit of the submit_sm_resp is the message_id - 'b9637bb4' out of > '02/00/b9637bb4/11353872920997' > The rest is junk - the last number is the destination number. Interesting, I've just noticed that I get a similar problem with an operator here.  SMPP PDU 0x8168850 dump:    type_name: submit_sm_resp    command_id: 2147483652 = 0x80000004    command_status: 0 = 0x00000000    sequence_number: 5 = 0x00000005    message_id: "51f25d96" and in deliver_sm's short_message I got:       data: 69 64 3a 31 33 37 34 38   id:13748       data: 33 38 31 36 36 20 73 75   38166 su       data: 62 3a 30 30 31 20 64 6c   b:001 dl so dlr->timestamp comparison in dlr_mem_entry_match() in gw/dlr_mem.c always fails. The fix for my problem is easy, just a hex num conversion will do it. rgds, Edwin.