Hi all,
 
I am currently using Kannel to send SMS messages from a web application. I have 
noticed a problem with SMS messages not getting delivered to two test phones I 
have. Typically the message is only received on the first phone I send to, on 
about four out of every five times I test. Some testers have also sent larger 
batches of messages (10+) and have noticed that usually three or four never 
arrive at the phones. I am aware that sms is normally only best effort delivery 
anyhow, but messages are going missing in almost every batch I send.  
 
The messages are sent to kannel as seperate http requests, one after the other, 
the http requests themselves being constructed and sent in a loop using Java 
code. (I also tried to get a message to more than one phone in a single http 
request; someone was kind enough to supply instructions for this but I could 
not get it working reliably- please see attached. Following those instructions, 
I only received all the messages expected about one out every five tests). 
 
I check my application logs and smsbox.log each time, and it appears that all 
messages are being received by and forwarded from kannel to the configured 
smsc. The log-level configuration is set to 0, which according to the user 
guide is the most detailed level... 
I therefore requested some UCP trace from the smsc itself, but we never see all 
the  OT51 requests. Typically if we test with two http requests to kannel, we 
will see only the one OT51 (I believe is the request to send an sms message).
I have double checked and triple checked my configuration files, but I am out 
of ideas for what could be causing this... Please see attached kannel.conf.... 
I know it is most likely something wrong with the kannel configuration, so I 
would like to know if anyone has experienced this problem with intermittent 
delivery before, and what they did about it. 
 
Thanks v much for your help,
Karen
 
kannel.conf (with ip addresses blanked out for security)
 
group = coreadmin-port = 13000admin-password = buddycSMSstatus-password = 
buddycSMSadmin-deny-ip = "*.*.*.*"admin-allow-ip = "*.*.*.*"smsbox-port = 
13001#wapbox-port = 13002box-deny-ip = "*.*.*.*"box-allow-ip = 
"127.0.0.1"wdp-interface-name = "*"log-file = 
"/var/log/kannel/bearerbox.log"log-level = 0dlr-storage = internal
 
# smsbox group configgroup = smsboxbearerbox-host = localhostsendsms-port = 
13013global-sender = 13013access-log = "/var/log/kannel/access.log"log-file = 
"/var/log/kannel/smsbox.log"log-level = 0
 
# SMS-C configuration (1) fakesmsc only to be able to test# group = smsc# smsc 
= fake# smsc-id = BC_FAKE_SMSC# denied-smsc-id = BC_PROD_SMSC# port = 10000# 
connect-allow-ip = "127.0.0.1"
 
# SMS-C configuration (2) CMG production smscgroup = smscsmsc = emismsc-id = 
BC_PROD_SMSCdenied-smsc-id = BC_FAKE_SMSChost = *.*.*.*port = 7000smsc-username 
= ****smsc-password = buco****keepalive = 55# our-port = 600 (optional bind in 
our end)
 
 
-my previous post on related matter...
Hi Karen,  You should add %20 - url encoded space only , the + is another way 
tocode space.So your url should be: 
http://localhost:13013/cgi-bin/sendsms?username=fake&password=fakeword&to=00447775704910%2000447708821845&text=Hello+world+&from=buddy
 Check the sendsms-chars parameter value in the smsbox group if you can sendthe 
space character as a part of the to field. If it's not defined itwill accept 
thefollowing characters "0123456789 +-" which is the default value.  Cheers, 
Jovan
_________________________________________________________________
Win a voice over part with Kung Fu Panda & Live Search   and   100’s of Kung Fu 
Panda prizes to win with Live Search
http://clk.atdmt.com/UKM/go/107571439/direct/01/

Reply via email to