Re: SMS message ids
Hi Mattew, To get the message-id, i dont think we have a provision in the kannel to get it, but there is a way if UR SMSC provides the message-id in the deliver report, for the msg submitted to the SMSC, then u can ask for a deliver report for the msg submited and then store the msg-id from the deliver report sent by UR SMSC. On Wed, 2005-01-26 at 22:41, Matthew Hixson wrote: > In bearerbox.log I see this: > > SMPP PDU 0x81a00a0 dump: > 2005-01-26 09:02:42 [394] [7] DEBUG: type_name: submit_sm > 2005-01-26 09:02:42 [394] [7] DEBUG: command_id: 4 = 0x0004 > 2005-01-26 09:02:42 [394] [7] DEBUG: command_status: 0 = 0x > 2005-01-26 09:02:42 [394] [7] DEBUG: sequence_number: 1154 = > 0x0482 > 2005-01-26 09:02:42 [394] [7] DEBUG: service_type: NULL > 2005-01-26 09:02:42 [394] [7] DEBUG: source_addr_ton: 1 = 0x0001 > 2005-01-26 09:02:42 [394] [7] DEBUG: source_addr_npi: 1 = 0x0001 > 2005-01-26 09:02:42 [394] [7] DEBUG: source_addr: "55416" > 2005-01-26 09:02:42 [394] [7] DEBUG: dest_addr_ton: 1 = 0x0001 > 2005-01-26 09:02:42 [394] [7] DEBUG: dest_addr_npi: 1 = 0x0001 > 2005-01-26 09:02:42 [394] [7] DEBUG: destination_addr: "4252837796" > 2005-01-26 09:02:42 [394] [7] DEBUG: esm_class: 3 = 0x0003 > 2005-01-26 09:02:42 [394] [7] DEBUG: protocol_id: 0 = 0x > 2005-01-26 09:02:42 [394] [7] DEBUG: priority_flag: 0 = 0x > 2005-01-26 09:02:42 [394] [7] DEBUG: schedule_delivery_time: NULL > 2005-01-26 09:02:42 [394] [7] DEBUG: validity_period: NULL > 2005-01-26 09:02:42 [394] [7] DEBUG: registered_delivery: 1 = > 0x0001 > 2005-01-26 09:02:42 [394] [7] DEBUG: replace_if_present_flag: 0 = > 0x > 2005-01-26 09:02:42 [394] [7] DEBUG: data_coding: 0 = 0x > 2005-01-26 09:02:42 [394] [7] DEBUG: sm_default_msg_id: 0 = 0x > 2005-01-26 09:02:42 [394] [7] DEBUG: sm_length: 5 = 0x0005 > 2005-01-26 09:02:42 [394] [7] DEBUG: short_message: "test\n" > 2005-01-26 09:02:42 [394] [7] DEBUG: SMPP PDU dump ends. > 2005-01-26 09:02:43 [394] [7] DEBUG: SMPP[wsc_wireless_services]: Got > PDU: > 2005-01-26 09:02:43 [394] [7] DEBUG: SMPP PDU 0x81a00a0 dump: > 2005-01-26 09:02:43 [394] [7] DEBUG: type_name: submit_sm_resp > 2005-01-26 09:02:43 [394] [7] DEBUG: command_id: 2147483652 = > 0x8004 > 2005-01-26 09:02:43 [394] [7] DEBUG: command_status: 0 = 0x > 2005-01-26 09:02:43 [394] [7] DEBUG: sequence_number: 1154 = > 0x0482 > 2005-01-26 09:02:43 [394] [7] DEBUG: message_id: "F39E35D" > > I was hoping that Kannel 1.4.0 would send me the message_id value when > I used the escape code %I, however I'm seeing this instead. > > /notification?smsc-id=wsc_wireless_services&smsid=da03662a-731a-4e22 > -8a18 > -2d982663eb4f&msg=ACK%2F&status=8&answer=ACK%2F&to=55416&from=4252837796 > &time=2005-01-26+17:02:43 > > What is "da03662a-731a-4e22-8a18-2d982663eb4f" from? I can't find it > anywhere in bearerbox.log. >Is there a way to get Kannel to send me the message_id value of > "F39E35D"? >Thanks, > -M@ > -- shyam kumar <[EMAIL PROTECTED]> tanlasolutions ltd * This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful. *
Re: SMS message ids
I don't own the SMSC, the carrier does. If I've told Kannel that I am interested in all delivery reports, by specifying a dlr-mask of 31, should the SMSC be reporting a status back to Kannel and Kannel would then relay that status back to my dlr-url? So, I would be getting more than one delivery report from Kannel per SMS that I send through it. Is that how it works? Thanks for the reply, -M@ On Jan 26, 2005, at 9:13 PM, shyam kumar wrote: Hi Mattew, To get the message-id, i dont think we have a provision in the kannel to get it, but there is a way if UR SMSC provides the message-id in the deliver report, for the msg submitted to the SMSC, then u can ask for a deliver report for the msg submited and then store the msg-id from the deliver report sent by UR SMSC. On Wed, 2005-01-26 at 22:41, Matthew Hixson wrote: In bearerbox.log I see this: SMPP PDU 0x81a00a0 dump: 2005-01-26 09:02:42 [394] [7] DEBUG: type_name: submit_sm 2005-01-26 09:02:42 [394] [7] DEBUG: command_id: 4 = 0x0004 2005-01-26 09:02:42 [394] [7] DEBUG: command_status: 0 = 0x 2005-01-26 09:02:42 [394] [7] DEBUG: sequence_number: 1154 = 0x0482 2005-01-26 09:02:42 [394] [7] DEBUG: service_type: NULL 2005-01-26 09:02:42 [394] [7] DEBUG: source_addr_ton: 1 = 0x0001 2005-01-26 09:02:42 [394] [7] DEBUG: source_addr_npi: 1 = 0x0001 2005-01-26 09:02:42 [394] [7] DEBUG: source_addr: "55416" 2005-01-26 09:02:42 [394] [7] DEBUG: dest_addr_ton: 1 = 0x0001 2005-01-26 09:02:42 [394] [7] DEBUG: dest_addr_npi: 1 = 0x0001 2005-01-26 09:02:42 [394] [7] DEBUG: destination_addr: "4252837796" 2005-01-26 09:02:42 [394] [7] DEBUG: esm_class: 3 = 0x0003 2005-01-26 09:02:42 [394] [7] DEBUG: protocol_id: 0 = 0x 2005-01-26 09:02:42 [394] [7] DEBUG: priority_flag: 0 = 0x 2005-01-26 09:02:42 [394] [7] DEBUG: schedule_delivery_time: NULL 2005-01-26 09:02:42 [394] [7] DEBUG: validity_period: NULL 2005-01-26 09:02:42 [394] [7] DEBUG: registered_delivery: 1 = 0x0001 2005-01-26 09:02:42 [394] [7] DEBUG: replace_if_present_flag: 0 = 0x 2005-01-26 09:02:42 [394] [7] DEBUG: data_coding: 0 = 0x 2005-01-26 09:02:42 [394] [7] DEBUG: sm_default_msg_id: 0 = 0x 2005-01-26 09:02:42 [394] [7] DEBUG: sm_length: 5 = 0x0005 2005-01-26 09:02:42 [394] [7] DEBUG: short_message: "test\n" 2005-01-26 09:02:42 [394] [7] DEBUG: SMPP PDU dump ends. 2005-01-26 09:02:43 [394] [7] DEBUG: SMPP[wsc_wireless_services]: Got PDU: 2005-01-26 09:02:43 [394] [7] DEBUG: SMPP PDU 0x81a00a0 dump: 2005-01-26 09:02:43 [394] [7] DEBUG: type_name: submit_sm_resp 2005-01-26 09:02:43 [394] [7] DEBUG: command_id: 2147483652 = 0x8004 2005-01-26 09:02:43 [394] [7] DEBUG: command_status: 0 = 0x 2005-01-26 09:02:43 [394] [7] DEBUG: sequence_number: 1154 = 0x0482 2005-01-26 09:02:43 [394] [7] DEBUG: message_id: "F39E35D" I was hoping that Kannel 1.4.0 would send me the message_id value when I used the escape code %I, however I'm seeing this instead. /notification?smsc-id=wsc_wireless_services&smsid=da03662a-731a-4e22 -8a18 -2d982663eb4f&msg=ACK%2F&status=8&answer=ACK%2F&to=55416&from=42528377 96 &time=2005-01-26+17:02:43 What is "da03662a-731a-4e22-8a18-2d982663eb4f" from? I can't find it anywhere in bearerbox.log. Is there a way to get Kannel to send me the message_id value of "F39E35D"? Thanks, -M@ -- shyam kumar <[EMAIL PROTECTED]> tanlasolutions ltd *** ** This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful. *** **
Re: SMS message ids
Answers inline On Thu, 2005-01-27 at 10:42, Matthew Hixson wrote: > I don't own the SMSC, the carrier does. i mean by UR SMSC is the SMSC that U Use from the carrier. > If I've told Kannel that I am > interested in all delivery reports, by specifying a dlr-mask of 31, > should the SMSC be reporting a status back to Kannel and Kannel would > then relay that status back to my dlr-url? YES, it will report back the status to the kannel, if the SMSC UR using has the provision to send for all types, but anyway U will definitely get the msg failed, pending, or either sucessful status from ur carrier SMSC. > So, I would be getting more > than one delivery report from Kannel per SMS that I send through it. > Is that how it works? > Thanks for the reply, >-M@ > > On Jan 26, 2005, at 9:13 PM, shyam kumar wrote: > > > Hi Mattew, > > > > To get the message-id, i dont think we have a provision in the kannel > > to > > get it, but there is a way if UR SMSC provides the message-id in the > > deliver report, for the msg submitted to the SMSC, then u can ask for a > > deliver report for the msg submited and then store the msg-id from the > > deliver report sent by UR SMSC. > > > > On Wed, 2005-01-26 at 22:41, Matthew Hixson wrote: > >> In bearerbox.log I see this: > >> > >> SMPP PDU 0x81a00a0 dump: > >> 2005-01-26 09:02:42 [394] [7] DEBUG: type_name: submit_sm > >> 2005-01-26 09:02:42 [394] [7] DEBUG: command_id: 4 = 0x0004 > >> 2005-01-26 09:02:42 [394] [7] DEBUG: command_status: 0 = 0x > >> 2005-01-26 09:02:42 [394] [7] DEBUG: sequence_number: 1154 = > >> 0x0482 > >> 2005-01-26 09:02:42 [394] [7] DEBUG: service_type: NULL > >> 2005-01-26 09:02:42 [394] [7] DEBUG: source_addr_ton: 1 = 0x0001 > >> 2005-01-26 09:02:42 [394] [7] DEBUG: source_addr_npi: 1 = 0x0001 > >> 2005-01-26 09:02:42 [394] [7] DEBUG: source_addr: "55416" > >> 2005-01-26 09:02:42 [394] [7] DEBUG: dest_addr_ton: 1 = 0x0001 > >> 2005-01-26 09:02:42 [394] [7] DEBUG: dest_addr_npi: 1 = 0x0001 > >> 2005-01-26 09:02:42 [394] [7] DEBUG: destination_addr: "4252837796" > >> 2005-01-26 09:02:42 [394] [7] DEBUG: esm_class: 3 = 0x0003 > >> 2005-01-26 09:02:42 [394] [7] DEBUG: protocol_id: 0 = 0x > >> 2005-01-26 09:02:42 [394] [7] DEBUG: priority_flag: 0 = 0x > >> 2005-01-26 09:02:42 [394] [7] DEBUG: schedule_delivery_time: NULL > >> 2005-01-26 09:02:42 [394] [7] DEBUG: validity_period: NULL > >> 2005-01-26 09:02:42 [394] [7] DEBUG: registered_delivery: 1 = > >> 0x0001 > >> 2005-01-26 09:02:42 [394] [7] DEBUG: replace_if_present_flag: 0 = > >> 0x > >> 2005-01-26 09:02:42 [394] [7] DEBUG: data_coding: 0 = 0x > >> 2005-01-26 09:02:42 [394] [7] DEBUG: sm_default_msg_id: 0 = > >> 0x > >> 2005-01-26 09:02:42 [394] [7] DEBUG: sm_length: 5 = 0x0005 > >> 2005-01-26 09:02:42 [394] [7] DEBUG: short_message: "test\n" > >> 2005-01-26 09:02:42 [394] [7] DEBUG: SMPP PDU dump ends. > >> 2005-01-26 09:02:43 [394] [7] DEBUG: SMPP[wsc_wireless_services]: Got > >> PDU: > >> 2005-01-26 09:02:43 [394] [7] DEBUG: SMPP PDU 0x81a00a0 dump: > >> 2005-01-26 09:02:43 [394] [7] DEBUG: type_name: submit_sm_resp > >> 2005-01-26 09:02:43 [394] [7] DEBUG: command_id: 2147483652 = > >> 0x8004 > >> 2005-01-26 09:02:43 [394] [7] DEBUG: command_status: 0 = 0x > >> 2005-01-26 09:02:43 [394] [7] DEBUG: sequence_number: 1154 = > >> 0x0482 > >> 2005-01-26 09:02:43 [394] [7] DEBUG: message_id: "F39E35D" > >> > >> I was hoping that Kannel 1.4.0 would send me the message_id value when > >> I used the escape code %I, however I'm seeing this instead. > >> > >> /notification?smsc-id=wsc_wireless_services&smsid=da03662a-731a-4e22 > >> -8a18 > >> -2d982663eb4f&msg=ACK%2F&status=8&answer=ACK%2F&to=55416&from=42528377 > >> 96 > >> &time=2005-01-26+17:02:43 > >> > >> What is "da03662a-731a-4e22-8a18-2d982663eb4f" from? I can't find it > >> anywhere in bearerbox.log. > >>Is there a way to get Kannel to send me the message_id value of > >> "F39E35D"? > >>Thanks, > >> -M@ > >> > > -- > > shyam kumar <[EMAIL PROTECTED]> > > tanlasolutions ltd > > > > > > > > > > *** > > ** > > > > This e-mail and any files transmitted with it are for the sole use > > of the intended recipient(s) and may contain confidential and > > privileged > > information. If you are not the intended recipient, please contact the > > sender by reply e-mail and destroy all copies of the original message. > > > > Any unauthorized review, use, disclosure, dissemination, forwarding, > > printing or copying of this email or any action taken in reliance on > > this e-mail is strictly prohibited and may be unlawful. > > > > *** > > ** > > > *
Re: SMS message ids
On Jan 26, 2005, at 9:37 PM, shyam kumar wrote: Answers inline On Thu, 2005-01-27 at 10:42, Matthew Hixson wrote: I don't own the SMSC, the carrier does. i mean by UR SMSC is the SMSC that U Use from the carrier. Ok. If I've told Kannel that I am interested in all delivery reports, by specifying a dlr-mask of 31, should the SMSC be reporting a status back to Kannel and Kannel would then relay that status back to my dlr-url? YES, it will report back the status to the kannel, if the SMSC UR using has the provision to send for all types, but anyway U will definitely get the msg failed, pending, or either sucessful status from ur carrier SMSC. So, how would I get Kannel to send me a notification containing the message id? I'd still need to know what escape code to put into my dlr-url, if one exists. Thanks, -M@
Re: SMS message ids
**>To: users@kannel.org **>From: Matthew Hixson <[EMAIL PROTECTED]> **>Subject: SMS message ids **>Date: Wed, 26 Jan 2005 09:11:42 -0800 **> **>In bearerbox.log I see this: **> **>SMPP PDU 0x81a00a0 dump: [ ... lines deleted ... ] **>2005-01-26 09:02:43 [394] [7] DEBUG: SMPP[wsc_wireless_services]: Got **>PDU: **>2005-01-26 09:02:43 [394] [7] DEBUG: SMPP PDU 0x81a00a0 dump: **>2005-01-26 09:02:43 [394] [7] DEBUG: type_name: submit_sm_resp **>2005-01-26 09:02:43 [394] [7] DEBUG: command_id: 2147483652 = **>0x8004 **>2005-01-26 09:02:43 [394] [7] DEBUG: command_status: 0 = 0x **>2005-01-26 09:02:43 [394] [7] DEBUG: sequence_number: 1154 = **>0x0482 **>2005-01-26 09:02:43 [394] [7] DEBUG: message_id: "F39E35D" **> **>I was hoping that Kannel 1.4.0 would send me the message_id value when **>I used the escape code %I, however I'm seeing this instead. **> **>/notification?smsc-id=wsc_wireless_services&smsid=da03662a-731a-4e22 **>-8a18 **>-2d982663eb4f&msg=ACK%2F&status=8&answer=ACK%2F&to=55416&from=4252837796 **>&time=2005-01-26+17:02:43 **> **>What is "da03662a-731a-4e22-8a18-2d982663eb4f" from? I can't find it **>anywhere in bearerbox.log. **> Is there a way to get Kannel to send me the message_id value of **>"F39E35D"? Kannel's dlr-url will only return the message-id embedded in the deliver_sm, not from the submit_sm_resp. Kannel's bearerbox will use the message-id from the submit_sm_resp to generate and entry in its own dlr-url lookup table. But, again, this information is not forwarded to you via the dlr-url. The dlr-url is activated when the DLR comes from the operator via a deliver_sm. Then, and only then, will Kannel make the HTTP_GET to your URL specified in the dlr-url. Therefore, if your SMPP operator is not returning the message-id in the short_message part of the deliver_sm (i.e. message body of a regular SMS...I call it the old embedded method), then the information must be conveyed through the Tag-Length-Value (TLV) optional parameters (specifically TLV 0x001E [receipted_message_id]). Kannel examines the deliver_sm and first looks for the message-id via a TLV and then tries to scan the message body for the old embedded method. Kannel handles the old embedded method by scanning the message body for the ascii keyword "id:" and assumes the message-id is after that keyword. If you operator is not using TLV and their message body has somethings else with an "id:" in it, then Kannel will get and incorrect message-id parse. If you can also post to the list the deliver_sm decoding, then we can get a better idea what happened. It appears to me that your provider might be generating non-standard DLRs (hence the message-id of da03662a-731a-4e22-8a18-2d982663eb4f). See ya... d.c.
Re: SMS message ids
On Wed, 2005-01-26 at 22:26 -0800, Matthew Hixson wrote: > So, how would I get Kannel to send me a notification containing the > message id? I'd still need to know what escape code to put into my > dlr-url, if one exists. Just generate a unique message ID before submitting the message, save it to a safe place, use the ID somewhere in your dlr-url (/test.php?msgid=191234325&status=%d), and when Kannel calls your dlr-url, you'll get your ID back. Enjoy, -- Enver ALTIN |http://skyblue.gen.tr/ Software developer @ Parkyeri | http://www.parkyeri.com/ signature.asc Description: This is a digitally signed message part
Re: SMS message ids
On Jan 27, 2005, at 11:35 AM, Enver ALTIN wrote: On Wed, 2005-01-26 at 22:26 -0800, Matthew Hixson wrote: So, how would I get Kannel to send me a notification containing the message id? I'd still need to know what escape code to put into my dlr-url, if one exists. Just generate a unique message ID before submitting the message, save it to a safe place, use the ID somewhere in your dlr-url (/test.php?msgid=191234325&status=%d), and when Kannel calls your dlr-url, you'll get your ID back. I need the message_id that I see in bearerbox.log. I don't know whether Kannel or the SMSC generates this number. We need it because we will be comparing it to logs generated by the carrier's system for billing purposes and their logs include those same message_ids. I wish I could just make up my own message ids, but I can't. -M@
Re: SMS message ids in delivery report
Hi, Please read User's guide about msg-id-type. BR, Nikos - Original Message - From: "Adam Di Blasio" To: Sent: Thursday, July 22, 2010 7:15 PM Subject: SMS message ids in delivery report Hi, I am trying to use DLR reports through SMPP but have noticed that the SMSC returns a hex id with submit_sm_resp and a decimal id with deliver_sm: 2010-07-22 15:42:37 [6284] [8] DEBUG: SMPP PDU 0x81af020 dump: 2010-07-22 15:42:37 [6284] [8] DEBUG: type_name: submit_sm_resp 2010-07-22 15:42:37 [6284] [8] DEBUG: command_id: 2147483652 = 0x8004 2010-07-22 15:42:37 [6284] [8] DEBUG: command_status: 0 = 0x 2010-07-22 15:42:37 [6284] [8] DEBUG: sequence_number: 3 = 0x0003 2010-07-22 15:42:37 [6284] [8] DEBUG: message_id: "70767AFF" 2010-07-22 15:42:41 [6284] [9] DEBUG: SMPP PDU 0x81af020 dump: 2010-07-22 15:42:41 [6284] [9] DEBUG: type_name: deliver_sm 2010-07-22 15:42:41 [6284] [9] DEBUG: command_id: 5 = 0x0005 ... 2010-07-22 15:42:41 [6284] [9] DEBUG: data: 69 64 3a 31 38 38 36 38 31 32 39 32 37 20 73 75 id:1886812927 When looking at the source in gw/smsc/smsc_smpp.c lines 1365 - 1392 (cvs version) I can see that kannel attempts to convert the id's so that they match - unfortunately this does not appear to be happening. Short of taking this up with the SMSC provider I wanted to see if anyone else had come across this problem and found a workaround? Kind Regards -- ADAM DI BLASIO
Re: SMS message ids in delivery report
Many Thanks Nikos. This solved the problem immediately. Adam On Thu, 22 Jul 2010 19:51:59 +0300 "Nikos Balkanas" wrote: > Hi, > > Please read User's guide about msg-id-type. > > BR, > Nikos > - Original Message - > From: "Adam Di Blasio" > To: > Sent: Thursday, July 22, 2010 7:15 PM > Subject: SMS message ids in delivery report > > > > Hi, > > > > I am trying to use DLR reports through SMPP but have noticed that the SMSC > > returns a hex id > > with submit_sm_resp and a decimal id with deliver_sm: > > > > 2010-07-22 15:42:37 [6284] [8] DEBUG: SMPP PDU 0x81af020 dump: > > 2010-07-22 15:42:37 [6284] [8] DEBUG: type_name: submit_sm_resp > > 2010-07-22 15:42:37 [6284] [8] DEBUG: command_id: 2147483652 = > > 0x8004 > > 2010-07-22 15:42:37 [6284] [8] DEBUG: command_status: 0 = 0x > > 2010-07-22 15:42:37 [6284] [8] DEBUG: sequence_number: 3 = 0x0003 > > 2010-07-22 15:42:37 [6284] [8] DEBUG: message_id: "70767AFF" > > > > > > 2010-07-22 15:42:41 [6284] [9] DEBUG: SMPP PDU 0x81af020 dump: > > 2010-07-22 15:42:41 [6284] [9] DEBUG: type_name: deliver_sm > > 2010-07-22 15:42:41 [6284] [9] DEBUG: command_id: 5 = 0x0005 > > ... > > 2010-07-22 15:42:41 [6284] [9] DEBUG: data: 69 64 3a 31 38 38 36 38 > > 31 32 39 32 37 20 73 > > 75 id:1886812927 > > > > When looking at the source in gw/smsc/smsc_smpp.c lines 1365 - 1392 (cvs > > version) I can see > > that kannel attempts to convert the id's so that they match - > > unfortunately this does not > > appear to be happening. > > Short of taking this up with the SMSC provider I wanted to see if anyone > > else had come across > > this problem and found a workaround? > > > > Kind Regards > > > > > > -- > > ADAM DI BLASIO > > > -- ADAM DI BLASIO adam.dibla...@adiqglobal.com T +44 (0)20 7729 0700 F +44 (0)20 7729 1619 UNIT 4.02 · THE TEA BUILDING 56 SHOREDITCH HIGH STREET · LONDON · E1 6JJ · UK WWW.ADIQGLOBAL.COM
Re: [Kannel-Users] Re: SMS message ids
On Thu, 27 Jan 2005, Davy Chan wrote: **>2005-01-26 09:02:43 [394] [7] DEBUG: SMPP[wsc_wireless_services]: Got **>PDU: **>2005-01-26 09:02:43 [394] [7] DEBUG: SMPP PDU 0x81a00a0 dump: **>2005-01-26 09:02:43 [394] [7] DEBUG: type_name: submit_sm_resp **>2005-01-26 09:02:43 [394] [7] DEBUG: command_id: 2147483652 = **>0x8004 **>2005-01-26 09:02:43 [394] [7] DEBUG: command_status: 0 = 0x **>2005-01-26 09:02:43 [394] [7] DEBUG: sequence_number: 1154 = **>0x0482 **>2005-01-26 09:02:43 [394] [7] DEBUG: message_id: "F39E35D" **> **>I was hoping that Kannel 1.4.0 would send me the message_id value when **>I used the escape code %I, however I'm seeing this instead. **> **>/notification?smsc-id=wsc_wireless_services&smsid=da03662a-731a-4e22 **>-8a18 **>-2d982663eb4f&msg=ACK%2F&status=8&answer=ACK%2F&to=55416&from=4252837796 **>&time=2005-01-26+17:02:43 **> **>What is "da03662a-731a-4e22-8a18-2d982663eb4f" from? I can't find it **>anywhere in bearerbox.log. **> Is there a way to get Kannel to send me the message_id value of **>"F39E35D"? Kannel's dlr-url will only return the message-id embedded in the deliver_sm, not from the submit_sm_resp. Kannel's bearerbox will use the message-id from the submit_sm_resp to generate and entry in its own dlr-url lookup table. But, again, this information is not forwarded to you via the dlr-url. That's the question. Why, if the in submit_sm_resp does the message_id come over in, does the generated URL by kannel for the dlr report (type=8 is generated by kannel, NOT the SMSC) not include the message_id, passed exactly how the SMSC passed it? Let the user handle the conversion from hex to decimal, or a string or whatnot. Why does kannel not pass it then if it stores it in the DLR db? Therefore, if your SMPP operator is not returning the message-id in the short_message part of the deliver_sm (i.e. message body of a regular SMS...I call it the old embedded method), then the information must be conveyed through the Tag-Length-Value (TLV) optional parameters (specifically TLV 0x001E [receipted_message_id]). This problem has NOTHING to do with the SMPP operator. Kannel in version 1.3.2 and later calls the DLR URL with type=8 when the SMPP operator accepts (ACK/'s) the message. KANNEL generates the above message, not the SMPP operator. If you can also post to the list the deliver_sm decoding, then we can get a better idea what happened. It appears to me that your provider might be generating non-standard DLRs (hence the message-id of da03662a-731a-4e22-8a18-2d982663eb4f). I don't know where that message ID comes from... I assume it is kannel's primary key for the store table (internal storage I assume, since the primary key would be an int). Or it could be an MD5 hash of something. Whatever it is, it seems to be useless. I, too, would find getting the remote SMSC message ID in the kannel-generated DLR report at submit_sm_resp success very useful and handy, since not all SMSC's and carriers in the US do further delivery receipts, unlike Europe. Beckman --- Peter Beckman Internet Guy [EMAIL PROTECTED] http://www.purplecow.com/ ---
RE: [Kannel-Users] Re: SMS message ids
Hi, This is something that I'd also find very useful. The message_id is available in some Kannel variable, so you should be able to pass it back. I wonder if someone who is reading this and has had experience in programming for kannel, would add this to CVS. Regards -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Peter Beckman Sent: Thursday, January 27, 2005 4:20 PM To: Davy Chan Cc: users@kannel.org Subject: Re: [Kannel-Users] Re: SMS message ids On Thu, 27 Jan 2005, Davy Chan wrote: > **>2005-01-26 09:02:43 [394] [7] DEBUG: SMPP[wsc_wireless_services]: Got > **>PDU: > **>2005-01-26 09:02:43 [394] [7] DEBUG: SMPP PDU 0x81a00a0 dump: > **>2005-01-26 09:02:43 [394] [7] DEBUG: type_name: submit_sm_resp > **>2005-01-26 09:02:43 [394] [7] DEBUG: command_id: 2147483652 = > **>0x8004 > **>2005-01-26 09:02:43 [394] [7] DEBUG: command_status: 0 = 0x > **>2005-01-26 09:02:43 [394] [7] DEBUG: sequence_number: 1154 = > **>0x0482 > **>2005-01-26 09:02:43 [394] [7] DEBUG: message_id: "F39E35D" > **> > **>I was hoping that Kannel 1.4.0 would send me the message_id value when > **>I used the escape code %I, however I'm seeing this instead. > **> > **>/notification?smsc-id=wsc_wireless_services&smsid=da03662a-731a-4e22 > **>-8a18 > **>-2d982663eb4f&msg=ACK%2F&status=8&answer=ACK%2F&to=55416&from=4252837796 > **>&time=2005-01-26+17:02:43 > **> > **>What is "da03662a-731a-4e22-8a18-2d982663eb4f" from? I can't find it > **>anywhere in bearerbox.log. > **> Is there a way to get Kannel to send me the message_id value of > **>"F39E35D"? > > Kannel's dlr-url will only return the message-id embedded in the > deliver_sm, not from the submit_sm_resp. Kannel's bearerbox will > use the message-id from the submit_sm_resp to generate and entry > in its own dlr-url lookup table. But, again, this information is > not forwarded to you via the dlr-url. That's the question. Why, if the in submit_sm_resp does the message_id come over in, does the generated URL by kannel for the dlr report (type=8 is generated by kannel, NOT the SMSC) not include the message_id, passed exactly how the SMSC passed it? Let the user handle the conversion from hex to decimal, or a string or whatnot. Why does kannel not pass it then if it stores it in the DLR db? > Therefore, if your SMPP operator is not returning the message-id > in the short_message part of the deliver_sm (i.e. message body > of a regular SMS...I call it the old embedded method), then the > information must be conveyed through the Tag-Length-Value (TLV) > optional parameters (specifically TLV 0x001E [receipted_message_id]). This problem has NOTHING to do with the SMPP operator. Kannel in version 1.3.2 and later calls the DLR URL with type=8 when the SMPP operator accepts (ACK/'s) the message. KANNEL generates the above message, not the SMPP operator. > If you can also post to the list the deliver_sm decoding, then > we can get a better idea what happened. It appears to me that > your provider might be generating non-standard DLRs (hence the > message-id of da03662a-731a-4e22-8a18-2d982663eb4f). I don't know where that message ID comes from... I assume it is kannel's primary key for the store table (internal storage I assume, since the primary key would be an int). Or it could be an MD5 hash of something. Whatever it is, it seems to be useless. I, too, would find getting the remote SMSC message ID in the kannel-generated DLR report at submit_sm_resp success very useful and handy, since not all SMSC's and carriers in the US do further delivery receipts, unlike Europe. Beckman --- Peter Beckman Internet Guy [EMAIL PROTECTED] http://www.purplecow.com/ ---
Re: [Kannel-Users] Re: SMS message ids
I will send a pizza voucher to the developer who adds this to Kannel. -M@ On Jan 27, 2005, at 2:41 PM, Hillel Bilman wrote: Hi, This is something that I'd also find very useful. The message_id is available in some Kannel variable, so you should be able to pass it back. I wonder if someone who is reading this and has had experience in programming for kannel, would add this to CVS. Regards -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Peter Beckman Sent: Thursday, January 27, 2005 4:20 PM To: Davy Chan Cc: users@kannel.org Subject: Re: [Kannel-Users] Re: SMS message ids On Thu, 27 Jan 2005, Davy Chan wrote: **>2005-01-26 09:02:43 [394] [7] DEBUG: SMPP[wsc_wireless_services]: Got **>PDU: **>2005-01-26 09:02:43 [394] [7] DEBUG: SMPP PDU 0x81a00a0 dump: **>2005-01-26 09:02:43 [394] [7] DEBUG: type_name: submit_sm_resp **>2005-01-26 09:02:43 [394] [7] DEBUG: command_id: 2147483652 = **>0x8004 **>2005-01-26 09:02:43 [394] [7] DEBUG: command_status: 0 = 0x **>2005-01-26 09:02:43 [394] [7] DEBUG: sequence_number: 1154 = **>0x0482 **>2005-01-26 09:02:43 [394] [7] DEBUG: message_id: "F39E35D" **> **>I was hoping that Kannel 1.4.0 would send me the message_id value when **>I used the escape code %I, however I'm seeing this instead. **> **>/notification?smsc-id=wsc_wireless_services&smsid=da03662a-731a -4e22 **>-8a18 **> -2d982663eb4f&msg=ACK%2F&status=8&answer=ACK%2F&to=55416&from=425283779 6 **>&time=2005-01-26+17:02:43 **> **>What is "da03662a-731a-4e22-8a18-2d982663eb4f" from? I can't find it **>anywhere in bearerbox.log. **> Is there a way to get Kannel to send me the message_id value of **>"F39E35D"? Kannel's dlr-url will only return the message-id embedded in the deliver_sm, not from the submit_sm_resp. Kannel's bearerbox will use the message-id from the submit_sm_resp to generate and entry in its own dlr-url lookup table. But, again, this information is not forwarded to you via the dlr-url. That's the question. Why, if the in submit_sm_resp does the message_id come over in, does the generated URL by kannel for the dlr report (type=8 is generated by kannel, NOT the SMSC) not include the message_id, passed exactly how the SMSC passed it? Let the user handle the conversion from hex to decimal, or a string or whatnot. Why does kannel not pass it then if it stores it in the DLR db? Therefore, if your SMPP operator is not returning the message-id in the short_message part of the deliver_sm (i.e. message body of a regular SMS...I call it the old embedded method), then the information must be conveyed through the Tag-Length-Value (TLV) optional parameters (specifically TLV 0x001E [receipted_message_id]). This problem has NOTHING to do with the SMPP operator. Kannel in version 1.3.2 and later calls the DLR URL with type=8 when the SMPP operator accepts (ACK/'s) the message. KANNEL generates the above message, not the SMPP operator. If you can also post to the list the deliver_sm decoding, then we can get a better idea what happened. It appears to me that your provider might be generating non-standard DLRs (hence the message-id of da03662a-731a-4e22-8a18-2d982663eb4f). I don't know where that message ID comes from... I assume it is kannel's primary key for the store table (internal storage I assume, since the primary key would be an int). Or it could be an MD5 hash of something. Whatever it is, it seems to be useless. I, too, would find getting the remote SMSC message ID in the kannel-generated DLR report at submit_sm_resp success very useful and handy, since not all SMSC's and carriers in the US do further delivery receipts, unlike Europe. Beckman --- Peter Beckman Internet Guy [EMAIL PROTECTED] http://www.purplecow.com/ ---
Re: [Kannel-Users] Re: SMS message ids
Hi, On Thu, 2005-01-27 at 11:47 -0800, Matthew Hixson wrote: > I will send a pizza voucher to the developer who adds this to Kannel. At least half of your pizza goes to Kalle Marjola. See the devel list archive on 7 October, 2004 (Preliminary confirmed sendsms). With little tweaking, you can earn the other half of the pizza yourself :) Enjoy, -- Enver ALTIN |http://skyblue.gen.tr/ Software developer @ Parkyeri | http://www.parkyeri.com/ signature.asc Description: This is a digitally signed message part
Re: [Kannel-Users] Re: SMS message ids
On Thu, 27 Jan 2005, Enver ALTIN wrote: On Wed, 2005-01-26 at 22:26 -0800, Matthew Hixson wrote: So, how would I get Kannel to send me a notification containing the message id? I'd still need to know what escape code to put into my dlr-url, if one exists. Just generate a unique message ID before submitting the message, save it to a safe place, use the ID somewhere in your dlr-url (/test.php?msgid=191234325&status=%d), and when Kannel calls your dlr-url, you'll get your ID back. We already do that. What I DO NOT get back is the SMSID from the remote SMSC. My id? 12345. Theirs? A35293FF. If delivery receipts are not sent by the SMSC, my only chance of putting their SMSID into my DB is via the DLR report that Kannel generates when the SMSC accepts my message. How can I associate my SMS with what they got if they don't use MY smsid? Beckman --- Peter Beckman Internet Guy [EMAIL PROTECTED] http://www.purplecow.com/ ---
Re: [Kannel-Users] Re: SMS message ids
On Thu, 27 Jan 2005, Matthew Hixson wrote: I need the message_id that I see in bearerbox.log. I don't know whether Kannel or the SMSC generates this number. We need it because we will be comparing it to logs generated by the carrier's system for billing purposes and their logs include those same message_ids. I wish I could just make up my own message ids, but I can't. The remote SMSC generates the message_id in the submit_sm_resp PDU. Beckman --- Peter Beckman Internet Guy [EMAIL PROTECTED] http://www.purplecow.com/ ---
Re: [Kannel-Users] Re: SMS message ids
did you guys forwarded this "request" to the [EMAIL PROTECTED] Since it is more
like a feature request and developers (like me ;) don't tend to keep up track
with the users@ list to much ;)
Stipe
Matthew Hixson wrote:
I will send a pizza voucher to the developer who adds this to Kannel.
-M@
On Jan 27, 2005, at 2:41 PM, Hillel Bilman wrote:
Hi,
This is something that I'd also find very useful. The message_id is
available in some Kannel variable, so you should
be able to pass it back. I wonder if someone who is reading this and
has had
experience in programming for kannel, would
add this to CVS.
Regards
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Peter Beckman
Sent: Thursday, January 27, 2005 4:20 PM
To: Davy Chan
Cc: users@kannel.org
Subject: Re: [Kannel-Users] Re: SMS message ids
On Thu, 27 Jan 2005, Davy Chan wrote:
**>2005-01-26 09:02:43 [394] [7] DEBUG: SMPP[wsc_wireless_services]:
Got
**>PDU:
**>2005-01-26 09:02:43 [394] [7] DEBUG: SMPP PDU 0x81a00a0 dump:
**>2005-01-26 09:02:43 [394] [7] DEBUG: type_name: submit_sm_resp
**>2005-01-26 09:02:43 [394] [7] DEBUG: command_id: 2147483652 =
**>0x8004
**>2005-01-26 09:02:43 [394] [7] DEBUG: command_status: 0 =
0x
**>2005-01-26 09:02:43 [394] [7] DEBUG: sequence_number: 1154 =
**>0x0482
**>2005-01-26 09:02:43 [394] [7] DEBUG: message_id: "F39E35D"
**>
**>I was hoping that Kannel 1.4.0 would send me the message_id value
when
**>I used the escape code %I, however I'm seeing this instead.
**>
**>/notification?smsc-id=wsc_wireless_services&smsid=da03662a-731a -4e22
**>-8a18
**>
-2d982663eb4f&msg=ACK%2F&status=8&answer=ACK%2F&to=55416&from=425283779 6
**>&time=2005-01-26+17:02:43
**>
**>What is "da03662a-731a-4e22-8a18-2d982663eb4f" from? I can't
find it
**>anywhere in bearerbox.log.
**> Is there a way to get Kannel to send me the message_id value of
**>"F39E35D"?
Kannel's dlr-url will only return the message-id embedded in the
deliver_sm, not from the submit_sm_resp. Kannel's bearerbox will
use the message-id from the submit_sm_resp to generate and entry
in its own dlr-url lookup table. But, again, this information is
not forwarded to you via the dlr-url.
That's the question. Why, if the in submit_sm_resp does the
message_id
come over in, does the generated URL by kannel for the dlr report
(type=8
is generated by kannel, NOT the SMSC) not include the message_id,
passed
exactly how the SMSC passed it? Let the user handle the conversion
from
hex to decimal, or a string or whatnot. Why does kannel not pass
it then
if it stores it in the DLR db?
Therefore, if your SMPP operator is not returning the message-id
in the short_message part of the deliver_sm (i.e. message body
of a regular SMS...I call it the old embedded method), then the
information must be conveyed through the Tag-Length-Value (TLV)
optional parameters (specifically TLV 0x001E [receipted_message_id]).
This problem has NOTHING to do with the SMPP operator. Kannel in
version
1.3.2 and later calls the DLR URL with type=8 when the SMPP operator
accepts (ACK/'s) the message. KANNEL generates the above message,
not the
SMPP operator.
If you can also post to the list the deliver_sm decoding, then
we can get a better idea what happened. It appears to me that
your provider might be generating non-standard DLRs (hence the
message-id of da03662a-731a-4e22-8a18-2d982663eb4f).
I don't know where that message ID comes from... I assume it is
kannel's
primary key for the store table (internal storage I assume, since the
primary key would be an int). Or it could be an MD5 hash of
something.
Whatever it is, it seems to be useless.
I, too, would find getting the remote SMSC message ID in the
kannel-generated DLR report at submit_sm_resp success very useful and
handy, since not all SMSC's and carriers in the US do further delivery
receipts, unlike Europe.
Beckman
---
Peter Beckman
Internet Guy
[EMAIL PROTECTED]
http://www.purplecow.com/
---
--
Für weitere Fragen stehe ich Ihnen gerne telefonisch
oder via E-Mail zur Verfügung.
Mit freundlichen Grüßen
Stipe Tolj
Department Management
Technology Center & Research Lab
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
Re: [Kannel-Users] Re: SMS message ids
Answers inline... **>Date: Thu, 27 Jan 2005 12:20:22 -0500 (EST) **>From: Peter Beckman <[EMAIL PROTECTED]> **>To: Davy Chan <[EMAIL PROTECTED]> **>cc: users@kannel.org **>Subject: Re: [Kannel-Users] Re: SMS message ids **>In-Reply-To: <[EMAIL PROTECTED]> **> **>On Thu, 27 Jan 2005, Davy Chan wrote: **> **>>**>2005-01-26 09:02:43 [394] [7] DEBUG: SMPP[wsc_wireless_services]: Got **>>**>PDU: **>>**>2005-01-26 09:02:43 [394] [7] DEBUG: SMPP PDU 0x81a00a0 dump: **>>**>2005-01-26 09:02:43 [394] [7] DEBUG: type_name: submit_sm_resp **>>**>2005-01-26 09:02:43 [394] [7] DEBUG: command_id: 2147483652 = **>>**>0x8004 **>>**>2005-01-26 09:02:43 [394] [7] DEBUG: command_status: 0 = 0x **>>**>2005-01-26 09:02:43 [394] [7] DEBUG: sequence_number: 1154 = **>>**>0x0482 **>>**>2005-01-26 09:02:43 [394] [7] DEBUG: message_id: "F39E35D" **>>**> **>>**>I was hoping that Kannel 1.4.0 would send me the message_id value when **>>**>I used the escape code %I, however I'm seeing this instead. **>>**> **>>**>/notification?smsc-id=wsc_wireless_services&smsid=da03662a-731a-4e22 **>>**>-8a18 **>>**>-2d982663eb4f&msg=ACK%2F&status=8&answer=ACK%2F&to=55416&from=4252837796 **>>**>&time=2005-01-26+17:02:43 **>>**> **>>**>What is "da03662a-731a-4e22-8a18-2d982663eb4f" from? I can't find it **>>**>anywhere in bearerbox.log. **>>**> Is there a way to get Kannel to send me the message_id value of **>>**>"F39E35D"? **>> **>>Kannel's dlr-url will only return the message-id embedded in the **>>deliver_sm, not from the submit_sm_resp. Kannel's bearerbox will **>>use the message-id from the submit_sm_resp to generate and entry **>>in its own dlr-url lookup table. But, again, this information is **>>not forwarded to you via the dlr-url. **> **> That's the question. Why, if the in submit_sm_resp does the message_id **> come over in, does the generated URL by kannel for the dlr report (type=8 **> is generated by kannel, NOT the SMSC) not include the message_id, passed **> exactly how the SMSC passed it? Let the user handle the conversion from **> hex to decimal, or a string or whatnot. Why does kannel not pass it then **> if it stores it in the DLR db? I've explained this in another email to the list, but, just in case a search on this topic does not return my other email... The message-id retrieved from a submit_sm_resp is on available to the bearerbox. Once the information is persisted into storage (be it SQL database or bearerbox memory store) it is thrown away and not passed to the smsbox. Since the smsbox does not have the message-id, it cannot put the information into an HTTP_GET generated from the dlr-url parameter. **>>Therefore, if your SMPP operator is not returning the message-id **>>in the short_message part of the deliver_sm (i.e. message body **>>of a regular SMS...I call it the old embedded method), then the **>>information must be conveyed through the Tag-Length-Value (TLV) **>>optional parameters (specifically TLV 0x001E [receipted_message_id]). **> **> This problem has NOTHING to do with the SMPP operator. Kannel in version **> 1.3.2 and later calls the DLR URL with type=8 when the SMPP operator **> accepts (ACK/'s) the message. KANNEL generates the above message, not the **> SMPP operator. Sorry...myoptic vision made me focus only on the message-id stuff. I overlooked the fact that the poster was talking about the value returned via an '%I' parameter. The '%I' (as of v1.3.2) returns the sms.id Kannel assigns to the SMS. This entity is derived from the following information: 32-bit time_low 16-bit time_mid 16-bit time_hi_and_version 16-bit clock_sequence 8-bit node [hashed from ethernet address] The '%I' escape code just prints out a human-digestible form it the UUID. **> **>>If you can also post to the list the deliver_sm decoding, then **>>we can get a better idea what happened. It appears to me that **>>your provider might be generating non-standard DLRs (hence the **>>message-id of da03662a-731a-4e22-8a18-2d982663eb4f). **> **> I don't know where that message ID comes from... I assume it is kannel's **> primary key for the store table (internal storage I assume, since the **> primary key would be an int). Or it could be an MD5 hash of something. **> Whatever it is, it seems to be useless. **> **> I, too, would find getting the remote SMSC message ID in the **> kannel-generated DLR report at submit_sm_resp success very useful and **> handy, since not all SMSC's and carriers in the US do further delivery **> receipts, unlike Europe. Working on it... **>Beckman **>--- **>Peter Beckman Internet Guy **>[EMAIL PROTECTED] http://www.purplecow.com/ **>--- See ya... d.c.
Re: [Kannel-Users] Re: [Kannel-Users] Re: SMS message ids
On Fri, 28 Jan 2005, Davy Chan wrote: Answers inline... **>Date: Thu, 27 Jan 2005 12:20:22 -0500 (EST) **>From: Peter Beckman <[EMAIL PROTECTED]> **>To: Davy Chan <[EMAIL PROTECTED]> **>cc: users@kannel.org **>Subject: Re: [Kannel-Users] Re: SMS message ids **>In-Reply-To: <[EMAIL PROTECTED]> **> **>On Thu, 27 Jan 2005, Davy Chan wrote: **> **>>**>2005-01-26 09:02:43 [394] [7] DEBUG: SMPP[wsc_wireless_services]: Got **>>**>PDU: **>>**>2005-01-26 09:02:43 [394] [7] DEBUG: SMPP PDU 0x81a00a0 dump: **>>**>2005-01-26 09:02:43 [394] [7] DEBUG: type_name: submit_sm_resp **>>**>2005-01-26 09:02:43 [394] [7] DEBUG: command_id: 2147483652 = **>>**>0x8004 **>>**>2005-01-26 09:02:43 [394] [7] DEBUG: command_status: 0 = 0x **>>**>2005-01-26 09:02:43 [394] [7] DEBUG: sequence_number: 1154 = **>>**>0x0482 **>>**>2005-01-26 09:02:43 [394] [7] DEBUG: message_id: "F39E35D" **>>**> **>>**>I was hoping that Kannel 1.4.0 would send me the message_id value when **>>**>I used the escape code %I, however I'm seeing this instead. **>>**> **>>**>/notification?smsc-id=wsc_wireless_services&smsid=da03662a-731a-4e22 **>>**>-8a18 **>>**>-2d982663eb4f&msg=ACK%2F&status=8&answer=ACK%2F&to=55416&from=4252837796 **>>**>&time=2005-01-26+17:02:43 **>>**> **>>**>What is "da03662a-731a-4e22-8a18-2d982663eb4f" from? I can't find it **>>**>anywhere in bearerbox.log. **>>**> Is there a way to get Kannel to send me the message_id value of **>>**>"F39E35D"? **>> **>>Kannel's dlr-url will only return the message-id embedded in the **>>deliver_sm, not from the submit_sm_resp. Kannel's bearerbox will **>>use the message-id from the submit_sm_resp to generate and entry **>>in its own dlr-url lookup table. But, again, this information is **>>not forwarded to you via the dlr-url. **> **> That's the question. Why, if the in submit_sm_resp does the message_id **> come over in, does the generated URL by kannel for the dlr report (type=8 **> is generated by kannel, NOT the SMSC) not include the message_id, passed **> exactly how the SMSC passed it? Let the user handle the conversion from **> hex to decimal, or a string or whatnot. Why does kannel not pass it then **> if it stores it in the DLR db? I've explained this in another email to the list, but, just in case a search on this topic does not return my other email... The message-id retrieved from a submit_sm_resp is on available to the bearerbox. Once the information is persisted into storage (be it SQL database or bearerbox memory store) it is thrown away and not passed to the smsbox. Since the smsbox does not have the message-id, it cannot put the information into an HTTP_GET generated from the dlr-url parameter. But I don't care about the message-id at the HTTP GET/POST -- I want it in the DLR message generated by kannel's bearerbox once the remote SMSC has accepted the message (if it is rejected, no message-id is available). **>>Therefore, if your SMPP operator is not returning the message-id **>>in the short_message part of the deliver_sm (i.e. message body **>>of a regular SMS...I call it the old embedded method), then the **>>information must be conveyed through the Tag-Length-Value (TLV) **>>optional parameters (specifically TLV 0x001E [receipted_message_id]). **> **> This problem has NOTHING to do with the SMPP operator. Kannel in version **> 1.3.2 and later calls the DLR URL with type=8 when the SMPP operator **> accepts (ACK/'s) the message. KANNEL generates the above message, not the **> SMPP operator. Sorry...myoptic vision made me focus only on the message-id stuff. I overlooked the fact that the poster was talking about the value returned via an '%I' parameter. The '%I' escape code just prints out a human-digestible form it the UUID. Working on it... Sweet. Sorry for the delay in reply, I was in Tobago . Sun. Beckman --- Peter Beckman Internet Guy [EMAIL PROTECTED] http://www.purplecow.com/ ---
