On Sun, Mar 4, 2012 at 7:20 PM, Alberto Mijares <[email protected]> wrote: > Hi List, > > Recently we added a second AT SMSC with another operator. we need to > keep track of DLR, so we ask for them within each MT sent. > > The issue here is that DLR's with the new operator are interpreted as > SMS's by kannel. I guess it's a missconfiguration of the SMSC. So, for > each MT, I get a SMS and kannel sends back a response with the content > from _default_ service, as it should.
Well, I'll try to reconfigure my question: 1.- Kannel 1.5 running on FreeBSD 8.2 with MySQL for DLR storage and GSM modem as SMSC (operator1). Everything working fine so far since long time. For each MT sent, we receive a DLR identified in logs (access.log) by string "Receive DLR". 2.- We added a second GSM modem as SMSC (operator2) two weeks ago. Now, for each MT routed through operator2, I receive a DLR identified in logs by string "Receive SMS". This message works like a MO _in_some_way_ and triggers the "default" service. This is not the expected behavior. Why do we say "_in_some_way_? Because we created a service like this group=sms-service keyword=mensaje get-url="http://localhost/cgi-bin/null.cgi?q=%s"; max-messages=0 # Every message starts with the word "Mensaje" # null.cgi returns a fixed string to avoid erros. And if we send a MO to this service we get no response, as expected; however, this kind of message we receive as DLR by operator2, saying it's a SMS in logs, doesn't trigger this service. Now we are thinking it could be an issue in kannel. It could be a missconfigured SMSC too. How could we know which option is true? May we help to debug? How could we give a solution to this issue meanwhile? Thank you very much. Regards Alberto Mijares
