Re: Priority parameter on sendsms, is it used?

2013-11-26 Thread Paulo Correia

Hi Alex,

Thank you for the reply.

Is kannel 1.5.X or SVN versions production ready? We are processing 
around 10M SMS/month and we cannot change unless the new version is 
production ready.


Best regards,
Paulo Correia

Em 25-11-2013 11:00, Alexander Malysh escreveu:

Hi,

use kannel SVN or at least 1.5.X where priority queue implemented.

Alex

Am 21.11.2013 um 11:46 schrieb Paulo Correia paulo.corr...@pdmfc.com 
mailto:paulo.corr...@pdmfc.com:



Hi all!

Again I have the same situation:

  * More than 20K messages pending:
curl -s
'http://kannel-host:kannel-port/store-status?password=*'
http://kannel-host:kannel-port/store-status?password=*%27
| wc -l
29291
  * Most of the pending messages were submitted with priority=0
  * One of the messages sent to kannel with priority=2 and is still
pending after 45minutes ... it should have been sent before the
others

Is there a way to resolve this?
I'm using kannel-1.4.3: bearerbox and smsbox (no sqlbox) with spool 
storage.


Any help is appreciated!

Best regards,
Paulo Correia

On 18-11-2013 09:39, Paulo Correia wrote:

Hi again!

Has anyone ever experienced strange behaviour with priorities on 
kannel 1.4.3 for large amount of messages?
In this case we are just using smsbox and bearerbox and for large 
amounts of messages (over 100/second and over 20K messages) we tend 
to get most in the spool and the priorities seem to be changed.


Best regards,
Paulo Correia

Em 06-11-2013 12:14, Paulo Correia escreveu:

Hi!

I'm having some trouble with the priority parameter of the sendsms 
not being respected on kannel 1.4.3.


If I send a large ammount of messages to kannel with sendsms, let's 
say around 2, most of them with priorities 0 or 1, and in the 
middle of them I send some other messages with priorities 2 or 3, I 
tippically get some of the messages with higher priority being held 
back, waiting for some lower priority messages to be sent to the SMSC.


The SMSC used is EMI/UCP.

Is this the normal behaviour? Is there a way to make the messages 
with higher priority to be sent before the others?


Thanks in advance.

Best regards,
Paulo Correia













Re: routing sms using smsc-id not working

2013-11-26 Thread Pablo Gus
Hi Alejandro,

I think you should use the following url, using the paramater smsc-id
instead of smsc:

http://xxx:xx/cgi-bin/sendsms?
username=xxpassword=xxxto=+595981414913from=1244@3
binfo=CCOTItext=Cotizacion+del+diasmsc-id=tigo
dlr-url=http%3A%2F%2Fdxxx%2Fsms%2Fapi%2Fdlr.php%3FmyId%3D10215%26type%3D%25ddlr-mask=3

If you do not choose any smsc, kannel will send the sms with a round robin
algorythm.

Regards.
Pablo.


2013/11/26 Alejandro Mussi alemu...@gmail.com

 Hi,

 I have 2 smsc setup in kannel. When i send an sms i specified the smsc id
 in the url but kannel sometimes sends using the other smsc (it seems to
 choose randomly)

 Here is my http request for sending a message using smsc-id tigo but in
 some cases it sends using personal:

 http://xxx:xx/cgi-bin/sendsms?username=xxpassword=xxxto=+595981414913
 from=1244@3binfo=CCOTItext=Cotizacion+del+diasmsc=tigo
 dlr-url=http%3A%2F%2Fdxxx%2Fsms%2Fapi%2Fdlr.php%3FmyId%3D10215%26type%3D%25ddlr-mask=3

 Here my conf file

 group = smsc
 smsc = smpp
 host = xxx.xxx.xxx.xx
 port = 8089
 receive-port = 8089
 smsc-username = yyy
 smsc-password = yy
 system-type = VMA
 address-range = 
 smsc-id = personal

 group = smsc
 smsc = smpp
 smsc-id = tigo
 host = xxx.xx.xxx.xx
 port = 5600
 receive-port = 5600
 smsc-username = yy
 smsc-password = yyy
 system-type = VMA
 address-range = 


 Thanks



 --
 -
 Alejandro Mussi Campos Cervera




-- 
Pablo Gus


Re: routing sms using smsc-id not working

2013-11-26 Thread Alejandro Mussi
Hi Pablo,

I have the same problem even changing the smsc paramter to smsc-id. In the
kannel user-guide specified smsc as the parameter to use for defining the
smsc-id.

Best





On Tue, Nov 26, 2013 at 11:19 AM, Pablo Gus pablo...@gmail.com wrote:

 Hi Alejandro,

 I think you should use the following url, using the paramater smsc-id
 instead of smsc:

 http://xxx:xx/cgi-bin/sendsms?
 username=xxpassword=xxxto=+595981414913from=1244@3
 binfo=CCOTItext=Cotizacion+del+diasmsc-id=tigo
 dlr-url=http%3A%2F%2Fdxxx%2Fsms%2Fapi%2Fdlr.php%3FmyId%3D10215%26type%3D%25ddlr-mask=3

 If you do not choose any smsc, kannel will send the sms with a round robin
 algorythm.

 Regards.
 Pablo.


 2013/11/26 Alejandro Mussi alemu...@gmail.com

 Hi,

 I have 2 smsc setup in kannel. When i send an sms i specified the smsc id
 in the url but kannel sometimes sends using the other smsc (it seems to
 choose randomly)

 Here is my http request for sending a message using smsc-id tigo but in
 some cases it sends using personal:

 http://xxx:xx/cgi-bin/sendsms?username=xxpassword=xxxto=+595981414913
 from=1244@3binfo=CCOTItext=Cotizacion+del+diasmsc=tigo
 dlr-url=http%3A%2F%2Fdxxx%2Fsms%2Fapi%2Fdlr.php%3FmyId%3D10215%26type%3D%25ddlr-mask=3

 Here my conf file

 group = smsc
 smsc = smpp
 host = xxx.xxx.xxx.xx
 port = 8089
 receive-port = 8089
 smsc-username = yyy
 smsc-password = yy
 system-type = VMA
 address-range = 
 smsc-id = personal

 group = smsc
 smsc = smpp
 smsc-id = tigo
 host = xxx.xx.xxx.xx
 port = 5600
 receive-port = 5600
 smsc-username = yy
 smsc-password = yyy
 system-type = VMA
 address-range = 


 Thanks



 --
 -
 Alejandro Mussi Campos Cervera




 --
 Pablo Gus




-- 
-
Alejandro Mussi Campos Cervera


Re: routing sms using smsc-id not working

2013-11-26 Thread Alvaro Cornejo
Hi

You need to add allowed/denied smsc. on each group.

Check documentation for details.

Regards

Alvaro

|-|
Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier
celular y Nextel
en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via
SMS y GPRS online
  Visitenos en www.perusms.com


On Tue, Nov 26, 2013 at 10:02 AM, Alejandro Mussi alemu...@gmail.com wrote:
 Hi Pablo,

 I have the same problem even changing the smsc paramter to smsc-id. In the
 kannel user-guide specified smsc as the parameter to use for defining the
 smsc-id.

 Best





 On Tue, Nov 26, 2013 at 11:19 AM, Pablo Gus pablo...@gmail.com wrote:

 Hi Alejandro,

 I think you should use the following url, using the paramater smsc-id
 instead of smsc:

 http://xxx:xx/cgi-bin/sendsms?

 username=xxpassword=xxxto=+595981414913from=1244@3binfo=CCOTItext=Cotizacion+del+diasmsc-id=tigodlr-url=http%3A%2F%2Fdxxx%2Fsms%2Fapi%2Fdlr.php%3FmyId%3D10215%26type%3D%25ddlr-mask=3

 If you do not choose any smsc, kannel will send the sms with a round robin
 algorythm.

 Regards.
 Pablo.


 2013/11/26 Alejandro Mussi alemu...@gmail.com

 Hi,

 I have 2 smsc setup in kannel. When i send an sms i specified the smsc id
 in the url but kannel sometimes sends using the other smsc (it seems to
 choose randomly)

 Here is my http request for sending a message using smsc-id tigo but in
 some cases it sends using personal:


 http://xxx:xx/cgi-bin/sendsms?username=xxpassword=xxxto=+595981414913from=1244@3binfo=CCOTItext=Cotizacion+del+diasmsc=tigodlr-url=http%3A%2F%2Fdxxx%2Fsms%2Fapi%2Fdlr.php%3FmyId%3D10215%26type%3D%25ddlr-mask=3

 Here my conf file

 group = smsc
 smsc = smpp
 host = xxx.xxx.xxx.xx
 port = 8089
 receive-port = 8089
 smsc-username = yyy
 smsc-password = yy
 system-type = VMA
 address-range = 
 smsc-id = personal

 group = smsc
 smsc = smpp
 smsc-id = tigo
 host = xxx.xx.xxx.xx
 port = 5600
 receive-port = 5600
 smsc-username = yy
 smsc-password = yyy
 system-type = VMA
 address-range = 


 Thanks



 --
 -
 Alejandro Mussi Campos Cervera




 --
 Pablo Gus




 --
 -
 Alejandro Mussi Campos Cervera



Re: routing sms using smsc-id not working

2013-11-26 Thread Alejandro Mussi
Solved. Thanks Alvaro



On Tue, Nov 26, 2013 at 12:26 PM, Alvaro Cornejo
cornejo.alv...@gmail.comwrote:

 Hi

 You need to add allowed/denied smsc. on each group.

 Check documentation for details.

 Regards

 Alvaro


 |-|
 Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier
 celular y Nextel
 en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via
 SMS y GPRS online
   Visitenos en www.perusms.com


 On Tue, Nov 26, 2013 at 10:02 AM, Alejandro Mussi alemu...@gmail.com
 wrote:
  Hi Pablo,
 
  I have the same problem even changing the smsc paramter to smsc-id. In
 the
  kannel user-guide specified smsc as the parameter to use for defining the
  smsc-id.
 
  Best
 
 
 
 
 
  On Tue, Nov 26, 2013 at 11:19 AM, Pablo Gus pablo...@gmail.com wrote:
 
  Hi Alejandro,
 
  I think you should use the following url, using the paramater smsc-id
  instead of smsc:
 
  http://xxx:xx/cgi-bin/sendsms?
 
  username=xxpassword=xxxto=+595981414913from=1244@3
 binfo=CCOTItext=Cotizacion+del+diasmsc-id=tigodlr-url=http%3A%2F%2Fdxxx%2Fsms%2Fapi%2Fdlr.php%3FmyId%3D10215%26type%3D%25ddlr-mask=3
 
  If you do not choose any smsc, kannel will send the sms with a round
 robin
  algorythm.
 
  Regards.
  Pablo.
 
 
  2013/11/26 Alejandro Mussi alemu...@gmail.com
 
  Hi,
 
  I have 2 smsc setup in kannel. When i send an sms i specified the smsc
 id
  in the url but kannel sometimes sends using the other smsc (it seems to
  choose randomly)
 
  Here is my http request for sending a message using smsc-id tigo but
 in
  some cases it sends using personal:
 
 
  http://xxx:xx/cgi-bin/sendsms?username=xxpassword=xxxto=
 +595981414913from=1244@3
 binfo=CCOTItext=Cotizacion+del+diasmsc=tigodlr-url=http%3A%2F%2Fdxxx%2Fsms%2Fapi%2Fdlr.php%3FmyId%3D10215%26type%3D%25ddlr-mask=3
 
  Here my conf file
 
  group = smsc
  smsc = smpp
  host = xxx.xxx.xxx.xx
  port = 8089
  receive-port = 8089
  smsc-username = yyy
  smsc-password = yy
  system-type = VMA
  address-range = 
  smsc-id = personal
 
  group = smsc
  smsc = smpp
  smsc-id = tigo
  host = xxx.xx.xxx.xx
  port = 5600
  receive-port = 5600
  smsc-username = yy
  smsc-password = yyy
  system-type = VMA
  address-range = 
 
 
  Thanks
 
 
 
  --
  -
  Alejandro Mussi Campos Cervera
 
 
 
 
  --
  Pablo Gus
 
 
 
 
  --
  -
  Alejandro Mussi Campos Cervera




-- 
-
Alejandro Mussi Campos Cervera


Re: Priority parameter on sendsms, is it used?

2013-11-26 Thread Alexander Malysh
Hi,

Kannel SVN is production ready even more as 1.4.3 

Alex

Am 26.11.2013 um 09:42 schrieb Paulo Correia paulo.corr...@pdmfc.com:

 Hi Alex,
 
 Thank you for the reply.
 
 Is kannel 1.5.X or SVN versions production ready? We are processing around 
 10M SMS/month and we cannot change unless the new version is production ready.
 
 Best regards,
 Paulo Correia
 
 Em 25-11-2013 11:00, Alexander Malysh escreveu:
 Hi,
 
 use kannel SVN or at least 1.5.X where priority queue implemented.
 
 Alex
 
 Am 21.11.2013 um 11:46 schrieb Paulo Correia paulo.corr...@pdmfc.com:
 
 Hi all!
 
 Again I have the same situation:
 More than 20K messages pending:
 curl -s 'http://kannel-host:kannel-port/store-status?password=*' | 
 wc -l
 29291
 Most of the pending messages were submitted with priority=0
 One of the messages sent to kannel with priority=2 and is still pending 
 after 45minutes ... it should have been sent before the others
 Is there a way to resolve this?
 I'm using kannel-1.4.3: bearerbox and smsbox (no sqlbox) with spool storage.
 
 Any help is appreciated!
 
 Best regards,
 Paulo Correia
 
 On 18-11-2013 09:39, Paulo Correia wrote:
 Hi again! 
 
 Has anyone ever experienced strange behaviour with priorities on kannel 
 1.4.3 for large amount of messages? 
 In this case we are just using smsbox and bearerbox and for large amounts 
 of messages (over 100/second and over 20K messages) we tend to get most in 
 the spool and the priorities seem to be changed. 
 
 Best regards, 
 Paulo Correia 
 
 Em 06-11-2013 12:14, Paulo Correia escreveu: 
 Hi! 
 
 I'm having some trouble with the priority parameter of the sendsms not 
 being respected on kannel 1.4.3. 
 
 If I send a large ammount of messages to kannel with sendsms, let's say 
 around 2, most of them with priorities 0 or 1, and in the middle of 
 them I send some other messages with priorities 2 or 3, I tippically get 
 some of the messages with higher priority being held back, waiting for 
 some lower priority messages to be sent to the SMSC. 
 
 The SMSC used is EMI/UCP. 
 
 Is this the normal behaviour? Is there a way to make the messages with 
 higher priority to be sent before the others? 
 
 Thanks in advance. 
 
 Best regards, 
 Paulo Correia 
 
 
 
 
 
 
 



receiving DLRs too fast - how to throttle?

2013-11-26 Thread Jeff Thorn
Hello Group,
We are receiving DLRs from the SMSC faster than we can process them. Our
setup is supposed to have 6 transmit binds and 4 receive binds. However, I
just looked at status page showing all our binds and it looks like all 10
of our binds are receiving DLRs and they are coming in at a rate greater
than 250 / second.

If I set the receive-port setting to 0 on our transmit binds, will I stop
receiving DLRs on these binds?

If this reduces the number of binds that can receive DLRs, should the rate
they are received go down? Or is that totally dependent upon the SMSC?

Is there anything I can control in my config that would reduce the rate
they are received or is that something only the SMSC can control?

Thanks,
Jeff


dlr-url don't insert SMS in database if message parts 1

2013-11-26 Thread Б-т
Hello. Sending sms works fine, dlr-url works fine, BUT if the message
contain more than one part (message lenght  160) script in dlr-url do not
insert data into the base. Why?


I use kannel with this config:

group = core
dlr-storage = mysql
admin-port = 13000
admin-password = *
status-password = *
admin-allow-ip = *
smsbox-port = 13001
log-level = 0
log-file = /var/log/kannel/kannel.log
box-allow-ip = 127.0.0.1
dlr-retry-count = 3
dlr-retry-delay = 200

group = smsbox
smsbox-id = BOX1
bearerbox-host = 127.0.0.1
sendsms-port = 13013
log-file = /var/log/kannel/smsbox.log
log-level = 0
access-log = /var/log/kannel/access.log

group = sendsms-user
default-smsc = smsc1
username = **
password = **
max-messages = 10
concatenation = true

group = smsc
smsc = smpp
smsc-id = smsc1
allowed-smsc-id = smsc1
host = **
port = **
smsc-username = **
smsc-password = **
address-range = 
system-type = 
transceiver-mode = true
validityperiod = 1440
source-addr-npi = 0
source-addr-ton = 5
dest-addr-npi = 1
dest-addr-ton = 1

group = smsc
smsc = smpp
smsc-id = smsc2
allowed-smsc-id = smsc2
host = **
port = **
smsc-username = **
smsc-password = **
address-range = 
system-type = 
transceiver-mode = true
validityperiod = 1440
source-addr-npi = 0
source-addr-ton = 5
dest-addr-npi = 1
dest-addr-ton = 1

group = mysql-connection
id = mydlr
host = localhost
username = **
password = **
database = **
max-connections = 10

group = dlr-db
id = mydlr
table = dlr
field-smsc = smsc
field-timestamp = ts
field-destination = destination
field-source = source
field-service = service
field-url = url
field-mask = mask
field-status = status
field-boxc-id = boxc