> > The SMPP 3.4 spec indicates that the submit_sm resp should > return the > > message id in hex format. > > I guess there room for error here - the message_id is defined as a > C-Octet String - not explicitly hex or decimal unlike the Delivery > Receipt id field unfortunately.
Yes you are correct, I forgot that its the 3.3 specification not the 3.4 that specifies that the message ID is in HEX. >The receipted_message_id doesn't seem to be supported in kannel. Is >anyone getting one back in deliver_sm? If so can anyone provide some >indication as to whether it matchs the submit_sm message_id, hex, dec, >etc .. ie: whether or not if implimented might help. As the receipted_message_id is 3.4 it should match the message id directly. However that is just my interpretation. I haven't seen any SMSCs using the receipted_message_id parameter yet! I suggest that you may enquire about this on the www.smsforum.net website, this website has a discussion forum for SMPP 3.4 that is very useful. Warm Regards, Michael Mulcahy ANAM Wireless Internet Solutions http://www.anam.com mailto:[EMAIL PROTECTED] +353 1 284 7555 Castle Yard, Saint Patrick's Road, Dalkey, County Dublin, Ireland > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Alan McNatty > Sent: 27 June 2002 23:55 > To: [EMAIL PROTECTED] > Cc: Kannel Dev > Subject: RE: SMPP dlr reports > > > Thanks for your feedback Michael, > > > The SMPP 3.4 spec indicates that the submit_sm resp should > return the > > message id in hex format. > > I guess there room for error here - the message_id is defined as a > C-Octet String - not explicitly hex or decimal unlike the Delivery > Receipt id field unfortunately. > > > The delivery report is typically a deliver_sm message. > > The necessary information though may be stored in two different > > formats. The first format has the necessary information in > the appropriate > > smpp fields and the other format has the details formatted > in the short > > message field. > > > > For the first format the message id will be in the > receipted_message_id > > field and it should be in hex. The second format specifies > the message id > > in the short message field and it is specified as decimal, > a bit annoying > > to say the least as this is what appears to be mostly used. > > The receipted_message_id is optional - unfortunately it isn't being > populated for me so I'm forced to use the short_message which > is defined > in .. more detail. > > Time to follow these up with provider. Cheers, > Alan
