Re: Queue management in virtual SMSCs

2015-10-14 Thread ha...@aeon.pk
Set retry attempts counter, let the message fail after threshold. Then use some script to pick up failed messages, switch the SMSC ID to new modem and send it again. Kannel cannot automate so many things. YOu would need help on application end. On Thu, Oct 8, 2015 at 10:15 AM, Raghvendra Sahu

Re: impact of bearerbox running without smsbox

2015-10-14 Thread ha...@aeon.pk
BBOX is the front end of kannel towards SMSC. For incoming SMS, it accepts and forwards them to relevant sqlbox/smsbox defined in the config. If SMSBOX is not connected and only BBOX is up, it will receive and store the messages in temp file/directory, and wait for smsbox to connect to it. The

Re: NEED INFORMATION:

2015-10-14 Thread ha...@aeon.pk
I don't think you can get IMSI via kannel. On Mon, Oct 5, 2015 at 1:16 PM, John alero wrote: > Dear Team, > > I need one help from all, If we have configured Kannel with MODEM router > and we require IMSI number of each submission. Is it possible on > Kannel access log

Re: howto add delay between sending sms

2015-10-14 Thread ha...@aeon.pk
You need to control it from your application front. Kannel can go slow and fast, but cannot freeze for some time to introduce delay that you want. On Wed, Sep 30, 2015 at 10:15 AM, Syed Jahanzaib wrote: > Tapan Kumar Thapa gmail.com> writes: > > > > Dear Syed, > > This has

getting command_status with DLR/mysql

2015-10-14 Thread Alejandro Mussi
Hi all, I have compiled kannel with mysql support but i still not getting the records of DLR in my DB. Here are my conf file and an example for sending a sms What i need is to store in some way the command_status for all sequence_number (as i get in bearerbox.log) Here is how i call the api to

Re: getting command_status with DLR/mysql

2015-10-14 Thread Alvaro Cornejo
Hi Alejandro You need to store that in your app using dlr info. dlr table you set up in kannel config is only for internal dlr handling. Once kannel receives the final status from the smsc for a particular sms, it will delete its record; that is why this table (w3_sms in your case) is almost