2014-03-10 17:15 GMT+04:00 mydi...@gmail.com <mydi...@gmail.com>: > Thanks for your reply. > > As for the speed, you are right, it doesn't affect my kannel > receiving/sending speed, but what happens is sending to 100numbes in the > same URL, instead of sending to 100 number in 100urls (1number each url), > affects the sending script speed. I send through send-sms cgi using php, > and the speed is massively different between the two methods, which is why > i need to use 100numbers in one url. >
Try tuning your script / database setup. Preferrably use nginx + php5-fpm over slow apache2. > > As for type=8, and dlr-mask. I completely have read the user guide, and > know exactly how it works. My issue is different from that. And anyway I > need type=8, for the reason you mentioned, I need to know the submission... > Regardless of DLR-mask, shouldn't kannel provide ONLY 1 message ID for 1 > sms send request? Why is it giving different message IDs for the same > number, same request? Unless I am still missing a point... > As I said earlier kannel's internal message scheme is suitable only for kannel's internal needs. Basically, each msgid inside the kannel (%I modifier) means unique identifier either for MT, MO or DLR message types. So, after you submit a batch of 100 numbers through send-sms cgi script with dlr_mask=31, kannel first returns DLR with status = 8 and its unique msgid and after sms get to the receiver you get a new DLR from your SMSC with status=1 and thus it has new msgid because it's a new DLR. You need to use your own msgid instead of %I and pass it to your dlr_url. > > I mean, regardless of type=1,..4,8,..., the messages id must be constant. > That is the whole point, so the STATUS of one send request gets updated and > the only way to identify which request, is using the messages id. > No, the only constant messageid is SMSC message identifier, but you really shouldnt rely on it too, because if you use multiple SMSC they might be overlapping and different SMSC are using different types of message id (someone uses plain integers, someone hex, someone uses mixed text-integer type). > > Thank you, > Ali. >
