This means that, for example, if I 
submit a message that cannot be delivered immediately (for some 
reason) I should get a DLR for "enqueueing to the SMSC" and later on 
one for the actual delivery to the handset. 
Is this true? 
Yes - you’ll get a DLR from the SMPP interface (depending on whom provides it) 
with an update of the state of the message in the network. You can use the 
dlr-mask for more finite control of the state (so that you do not need to 
process text strings which in my experience are rarely normalised to follow a 
standard / specification).

Do I need to implement a web service to be linked with the dlr-url 
parameter, of should I simply enable an SQL based dlr-storage? 
I use a web service for this. The GET-URL is called, which allows me to process 
the content of the message and store / forward etc as needed.

Christopher Burke
http://simulity.com
Office: +44 (0) 1248 679 281
Fax: +44 (0) 1248 660 323
Skype:krslynx



UK
Unit 8, Ash Court,
Parc Menai, Bangor,
Gwynedd, LL57 4DF,
Wales, UK

Malaysia
Level 30,
The Gardens North Tower,
Mid Valley City,
Lingkaran Syed Putra,
59200, Kuala Lumpur,
Malaysia

NOTICE: This message contains privileged & confidential information intended 
only for the use of the addressee named above. If you are not the intended 
recipient of this message, you are hereby notified that you must not 
disseminate, copy or take any action in reliance on it. If you have received 
this message in error, please notify Simulity Labs immediately. Any views 
expressed in this message are those of the individual sender except where the 
sender specifically states them to be the view of Simulity Labs


On 5 November 2014 at 13:57:02, Vincenzo Romano (vincenzo.rom...@notorand.it) 
wrote:

Hi all.  
I would like to better understand how the DLR messages are handled, in  
particular with GSM modems.  

I understood that if I submit an SMS with dlr-flag=31 I should get all  
status changes to my submission. This means that, for example, if I  
submit a message that cannot be delivered immediately (for some  
reason) I should get a DLR for "enqueueing to the SMSC" and later on  
one for the actual delivery to the handset.  
Is this true?  

Second, I would like to keep track of all DLR for every message (I  
undestand that usually there is only one for each message).  
Do I need to implement a web service to be linked with the dlr-url  
parameter, of should I simply enable an SQL based dlr-storage?  

Thanks in advance.  

Reply via email to