Hi!

I am still quite new to kannel, but I managed to get bearerbox and smsbox 
working together with an external smsc via smpp and MySQL DLR storage. I also 
installed opensmpp to serve as a smpp smsc myself to others, but this still 
produces some headache to me.

1. Question: query_sm?

Does kannel/opensmpp support the query_sm command? Query_sm should, together 
with the message ID tell the SMSC to give the delivery status of the message 
belonging to the referenced message ID back to the ESME. For me it seems that 
kannel and opensmpp do not support this because there is no data storage where 
the status of all the messages submitted through this kannel instance are kept 
forever. I just want to make sure I am right, and if not, I would love to see 
an example of the corresponding doc.


2. DLR delivery to opensmppbox

I don't get opensmppbox working to route DLRs back to the client that has 
connected via opensmppbox. I have kannel and opensmppbox writing into two 
separate mysql tables (I believe this is what opensmppbox's userguide tells me 
to do) while the kannel one does not have and the opensmppbox one does have a 
"id" field. Kannel connects to the upstream smsc using the transceiver method 
and gets DLRs back if they have been requested. It puts a line into the 
database table once the message is submitted to the smsc, and once it gets the 
dlr, the line is deleted again. I believe this is the way it should work.


Now I have some general questions regarding opensmppbox:

Is it true opensmppbox needs its own DLR storage? I have understood that it 
does, because it needs the message ID in the entries, but I have found out that 
opensmppbox only writes entries to this database when "use_smppboxid" is 
enabled.

What is the difference between having "use_smppboxid" enabled or not? Okay, 
when using it, then the connection to bearerbox happens using the box id's 
name, not the user name that logged one to the box, and I would have one 
permanent connection instead of many single ones, but what is the difference in 
behavior? Which ones works best and which mode is recommended in what situation?

Does anyone of you have a sample configuration that actually works, uses mysql 
dlr storage and manages to route the DLRs back to the originator? It would be 
great if you could share that with me.

I have used a number of combinations with different error messages and symptoms 
with each of them. Therefore I would first like to get my questions answered to 
not flood you with a huge amount of "if I do this, then that happens" debug 
logging.


Thanks for any feedback in advance!


Christian Anton


Reply via email to