RE: Opensmppbox throughput

2011-12-09 Thread Rene Kluwen
Onfurtunately, this isn't possible.

 

From: Otandeka Simon Peter [mailto:sotand...@gmail.com] 
Sent: Thursday, 08 December, 2011 14:56
To: Rene Kluwen
Cc: Kannel Users
Subject: Opensmppbox throughput

 


Hi Rene,

Is it possible to configure a throughput for each smppbox login created? 
Or can there be a limit on each login created?

Thanks,
Peter.



smsc send only

2011-12-09 Thread Marcin

Hi,

Is it possible to set kannel config, that for some smsc kannel only send 
messages but is not requesting to receive messages. (I don't know if I 
understand smsc driver).


We have 3 locations, but only one physical number (123 456 789) and many 
alphanumeric 'labels' ( 'Test','SuperSMS', etc.). I wont to send 
messages from 3 locations, but receive them in only one. Is it possible 
to set config to handle such situation?


Thanks for answer.
Marcin



Re: SMS push performance problem

2011-12-09 Thread Fabio Sangiovanni
Hi Mohammed,

thanks for your reply.
Unfortunately I won't be at my workplace again until next monday, so I won't be 
able to provide detailed logs since then.
On the other hand, I can post the kannel.conf file currently in use on the test 
machine.
Thanks again for your help. I'll post relevant log entries ASAP.

Cheers,
Fabio



#
# BEARERBOX
#


group = core
admin-port = 13000
admin-password = SECRET
#status-password = SECRET
admin-deny-ip = *.*.*.*
admin-allow-ip = 127.0.0.*;192.168.1.*
smsbox-port = 13003
#wapbox-port = 13002
#wdp-interface-name = *
box-deny-ip = *.*.*.*
box-allow-ip = 127.0.0.1
log-file = /var/log/kannel/bearerbox.log
access-log = /var/log/kannel/access.log
store-type = spool
store-location = /var/spool/kannel
log-level = 1
#log-level = 0
sms-incoming-queue-limit = -1
sms-outgoing-queue-limit = -1
sms-resend-retry = 0
dlr-storage = internal



#
# SMSBOX
#


group = smsbox
bearerbox-host = localhost
sendsms-port = 13013
sendsms-chars = 0123456789 
log-file = /var/log/kannel/smsbox.log
log-level = 1
#log-level = 0
access-log = /var/log/kannel/access.log



#
# ACCOUNT/SMSC MAPPINGS
#



# SMSC FAKEPLEX
group = sendsms-user
username = USERNAME1
password = SECRET1
name = user_smsc_fake
user-deny-ip = *.*.*.*
user-allow-ip = 127.0.0.*;192.168.1.*
forced-smsc = smscfake
default-sender = mycompany
max-messages = 3
concatenation = 1
omit-empty = 1
#

# SMSC PRODUCTION
group = sendsms-user
username = USERNAME2
password = SECRET2
name = user_smsc_prod
user-deny-ip = *.*.*.*
user-allow-ip = 127.0.0.*;192.168.1.*
forced-smsc = smscprod
default-sender = mycompany
max-messages = 3
concatenation = 1
omit-empty = 1
#



#
# SMSC CONFIG
#



# SMSC FAKEPLEX
group = smsc
smsc = smpp
smsc-id = smscfake
allowed-smsc-id = smscfake
host = SMSC HOSTNAME (GATEWAY A)
port = 3205
receive-port = 3205
transceiver-mode = true
smsc-username = USERNAME_SMSC
smsc-password = SECRET_SMSC
system-type = mycompany3
service-type = 18170
max-pending-submits = 10
msg-id-type = 0x01
log-file = /var/log/kannel/smsc.gatewayA.log
log-level = 1

group = smsc
smsc = smpp
smsc-id = smscfake
allowed-smsc-id = smscfake
host = SMSC HOSTNAME (GATEWAY B)
port = 3205
receive-port = 3205
transceiver-mode = true
smsc-username = USERNAME_SMSC
smsc-password = SECRET_SMSC
system-type = mycompany3
service-type = 18170
max-pending-submits = 10
msg-id-type = 0x01
log-file = /var/log/kannel/smsc.gatewayB.log
log-level = 1
#

# SMSC PRODUCTION
group = smsc
smsc = smpp
smsc-id = smscprod
allowed-smsc-id = smscprod
host = SMSC HOSTNAME (GATEWAY A)
port = 3205
receive-port = 3205
transceiver-mode = true
smsc-username = USERNAME_SMSC
smsc-password = SECRET_SMSC
system-type = mycompany4
service-type = 16570
max-pending-submits = 10
msg-id-type = 0x01
log-file = /var/log/kannel/smsc.gatewayA.log
log-level = 1

group = smsc
smsc = smpp
smsc-id = smscprod
allowed-smsc-id = smscprod
host = SMSC HOSTNAME (GATEWAY B)
port = 3205
receive-port = 3205
transceiver-mode = true
smsc-username = USERNAME_SMSC
smsc-password = SECRET_SMSC
system-type = mycompany4
service-type = 16570
max-pending-submits = 10
msg-id-type = 0x01
log-file = /var/log/kannel/smsc.gatewayB.log
log-level = 1
#


Il giorno 07/dic/2011, alle ore 17:08, Mohammed Saleem ha scritto:

Hi Fabio

did you check bearerbox and smsbox for errors?

Also share your full configurations.



On Wed, Dec 7, 2011 at 4:50 PM, Fabio Sangiovanni 
sangiova...@nweb.itmailto:sangiova...@nweb.it wrote:
Hello list,

the company I work for is using Kannel 1.4.3 on CentOS 6 as SMS gateway between 
our application servers and an SMSC. We have developed a multithreaded 
application that sends HTTP GET requests to our internal Kannel proxy. 
Everything goes smooth up to 5 application threads. The problem is that when 
the number of threads goes beyond 5, the responsiveness of Kannel seems to fall 
down to the point that it doesn't even accept more requests. I couldn't figure 
out where the problem is, nor which parameters adjust to widen the number of 
possible concurrent requests.

Are there any limitations on the HTTP side of the gateway? Shouldn't Kannel 
accept requests at max speed, queue them and then deliver to the SMSC according 
to the accept rate of the SMSC itself?

I've read through the documentation multiple times but I couldn't find any 
solutions yet.

Thanks a lot for your support!

Cheers,
Fabio




Re: SMS push performance problem

2011-12-09 Thread Mohammed Saleem
Hey Fabio

I can't provide a 100% solution for this issue before seeing the log. Try
to check the log and see if there is any error. But most probably it is an
open-files limitation problem, because you haven't set a limit to
sms-outgoing-queue-limit.
But Actually this depends on your throughput and how many messages you put
in the queue of each connection. Try to do the following:


(1) increase the limit of open-files for the user running kannel.
(2) set a limit for sms-outgoing-queue-limit, for example don't make it
more than 100 per 40 SMS/S throughput. This way kannel will reject any
message when the queue is full (see the HTTP response for the client
application which sends messages, you need to handle this kind of response
to retry on the rejected messages due to Queue Full)




Best Regards,
Mohammed M I Sleem

http://www.abusleem.net  - Personal blog



On Fri, Dec 9, 2011 at 4:01 PM, Fabio Sangiovanni sangiova...@nweb.itwrote:

  Hi Mohammed,

  thanks for your reply.
 Unfortunately I won't be at my workplace again until next monday, so I
 won't be able to provide detailed logs since then.
 On the other hand, I can post the kannel.conf file currently in use on the
 test machine.
 Thanks again for your help. I'll post relevant log entries ASAP.

  Cheers,
 Fabio


  
 #
 # BEARERBOX
 #
 

  group = core
 admin-port = 13000
 admin-password = SECRET
 #status-password = SECRET
 admin-deny-ip = *.*.*.*
 admin-allow-ip = 127.0.0.*;192.168.1.*
 smsbox-port = 13003
 #wapbox-port = 13002
 #wdp-interface-name = *
 box-deny-ip = *.*.*.*
 box-allow-ip = 127.0.0.1
 log-file = /var/log/kannel/bearerbox.log
 access-log = /var/log/kannel/access.log
 store-type = spool
 store-location = /var/spool/kannel
 log-level = 1
 #log-level = 0
 sms-incoming-queue-limit = -1
 sms-outgoing-queue-limit = -1
 sms-resend-retry = 0
 dlr-storage = internal


  
 #
 # SMSBOX
 #
 

  group = smsbox
 bearerbox-host = localhost
 sendsms-port = 13013
 sendsms-chars = 0123456789 
 log-file = /var/log/kannel/smsbox.log
 log-level = 1
 #log-level = 0
 access-log = /var/log/kannel/access.log


  
 #
 # ACCOUNT/SMSC MAPPINGS
 #
 


  # SMSC FAKEPLEX
 group = sendsms-user
 username = USERNAME1
 password = SECRET1
 name = user_smsc_fake
 user-deny-ip = *.*.*.*
 user-allow-ip = 127.0.0.*;192.168.1.*
 forced-smsc = smscfake
 default-sender = mycompany
 max-messages = 3
 concatenation = 1
 omit-empty = 1
 #

  # SMSC PRODUCTION
 group = sendsms-user
 username = USERNAME2
 password = SECRET2
 name = user_smsc_prod
 user-deny-ip = *.*.*.*
 user-allow-ip = 127.0.0.*;192.168.1.*
 forced-smsc = smscprod
 default-sender = mycompany
 max-messages = 3
 concatenation = 1
 omit-empty = 1
 #


  
 #
 # SMSC CONFIG
 #
 


  # SMSC FAKEPLEX
 group = smsc
 smsc = smpp
 smsc-id = smscfake
 allowed-smsc-id = smscfake
 host = SMSC HOSTNAME (GATEWAY A)
 port = 3205
 receive-port = 3205
 transceiver-mode = true
 smsc-username = USERNAME_SMSC
 smsc-password = SECRET_SMSC
 system-type = mycompany3
 service-type = 18170
 max-pending-submits = 10
 msg-id-type = 0x01
 log-file = /var/log/kannel/smsc.gatewayA.log
 log-level = 1

  group = smsc
 smsc = smpp
 smsc-id = smscfake
 allowed-smsc-id = smscfake
 host = SMSC HOSTNAME (GATEWAY B)
 port = 3205
 receive-port = 3205
 transceiver-mode = true
 smsc-username = USERNAME_SMSC
 smsc-password = SECRET_SMSC
 system-type = mycompany3
 service-type = 18170
 max-pending-submits = 10
 msg-id-type = 0x01
 log-file = /var/log/kannel/smsc.gatewayB.log
 log-level = 1
 #

  # SMSC PRODUCTION
 group = smsc
 smsc = smpp
 smsc-id = smscprod
 allowed-smsc-id = smscprod
 host = SMSC HOSTNAME (GATEWAY A)
 port = 3205
 receive-port = 3205
 transceiver-mode = true
 smsc-username = USERNAME_SMSC
 smsc-password = SECRET_SMSC
 system-type = mycompany4
 service-type = 16570
 max-pending-submits = 10
 msg-id-type = 0x01
 log-file = /var/log/kannel/smsc.gatewayA.log
 log-level = 1

  group = smsc
 smsc = smpp
 smsc-id = smscprod
 allowed-smsc-id = smscprod
 host = SMSC HOSTNAME (GATEWAY B)
 port = 3205
 receive-port = 3205
 transceiver-mode = true
 smsc-username = USERNAME_SMSC
 smsc-password = SECRET_SMSC
 system-type = mycompany4
 service-type = 16570
 max-pending-submits = 10
 msg-id-type = 0x01
 log-file = /var/log/kannel/smsc.gatewayB.log
 log-level = 1
 #


  Il giorno 07/dic/2011, alle ore 17:08, Mohammed Saleem ha scritto:

  Hi Fabio

  did you check bearerbox and smsbox for errors?

  Also share your full configurations.



  On Wed, Dec 7, 2011 at 4:50 PM, Fabio Sangiovanni sangiova...@nweb.itwrote:

 Hello list,

 the company I work for is using Kannel 1.4.3 on CentOS 6 as SMS gateway
 between our application servers and an SMSC. We have developed a
 multithreaded application that 

Hi, does higher spool memory in kannel low down the speed

2011-12-09 Thread Anshu Sah
Hi,

I would like you to see this scenario.


   1. With One SMSC Server I have Multiple PORT connectivity as diff. SMSC
   IDs
   2. Every Port has 2 session allowed . I am using 1 as TX and other as RX.
   3. In the beginning of PUSH kannel Accept by better speed of 14 TPS
   each. But later On this value start decreasing and more MT SMSs start get
   stored in SPOOL.


What can be possible reason for it. *
Does bigger spool Size affect kannel performance. *
I wonder, How the same configuration in starting of PUSH give me better
result and later on it decreases even till 1 TPS

===
My SMSC Configuration i am pasting below.

group=smsc
smsc=smpp
smsc-id=xxx
#allowed-smsc-id = xxx
host = xxx
port = xxx
transceiver-mode = 0
#receive-port = xx
log-file = /projects/kannel/logs/live/xxx_TX.log
log-level = 1
alt-charset = ASCII
smsc-username = xx
smsc-password = xx
#msg-id-type = 0x01
source-addr-ton = 5
source-addr-npi = 9
dest-addr-ton = 1
dest-addr-npi = 1
enquire-link-interval = 60
system-type = xx
reconnect-delay = 60
interface-version = 34
throughput = 25





Regards
Anshu Sah


Re: SMS push performance problem

2011-12-09 Thread Fabio Sangiovanni
Thanks again Mohammed, I'll change those settings as soon as I get back to work.
I'll keep you posted! :)

Cheers,
Fabio


Il giorno 09/dic/2011, alle ore 15:21, Mohammed Saleem ha scritto:

Hey Fabio

I can't provide a 100% solution for this issue before seeing the log. Try to 
check the log and see if there is any error. But most probably it is an 
open-files limitation problem, because you haven't set a limit to 
sms-outgoing-queue-limit. But Actually this depends on your throughput and 
how many messages you put in the queue of each connection. Try to do the 
following:


(1) increase the limit of open-files for the user running kannel.
(2) set a limit for sms-outgoing-queue-limit, for example don't make it more 
than 100 per 40 SMS/S throughput. This way kannel will reject any message when 
the queue is full (see the HTTP response for the client application which sends 
messages, you need to handle this kind of response to retry on the rejected 
messages due to Queue Full)




Best Regards,
Mohammed M I Sleem

http://www.abusleem.nethttp://www.abusleem.net/  - Personal blog



On Fri, Dec 9, 2011 at 4:01 PM, Fabio Sangiovanni 
sangiova...@nweb.itmailto:sangiova...@nweb.it wrote:
Hi Mohammed,

thanks for your reply.
Unfortunately I won't be at my workplace again until next monday, so I won't be 
able to provide detailed logs since then.
On the other hand, I can post the kannel.conf file currently in use on the test 
machine.
Thanks again for your help. I'll post relevant log entries ASAP.

Cheers,
Fabio



#
# BEARERBOX
#


group = core
admin-port = 13000
admin-password = SECRET
#status-password = SECRET
admin-deny-ip = *.*.*.*
admin-allow-ip = 127.0.0.*;192.168.1.*
smsbox-port = 13003
#wapbox-port = 13002
#wdp-interface-name = *
box-deny-ip = *.*.*.*
box-allow-ip = 127.0.0.1
log-file = /var/log/kannel/bearerbox.log
access-log = /var/log/kannel/access.log
store-type = spool
store-location = /var/spool/kannel
log-level = 1
#log-level = 0
sms-incoming-queue-limit = -1
sms-outgoing-queue-limit = -1
sms-resend-retry = 0
dlr-storage = internal



#
# SMSBOX
#


group = smsbox
bearerbox-host = localhost
sendsms-port = 13013
sendsms-chars = 0123456789 
log-file = /var/log/kannel/smsbox.log
log-level = 1
#log-level = 0
access-log = /var/log/kannel/access.log



#
# ACCOUNT/SMSC MAPPINGS
#



# SMSC FAKEPLEX
group = sendsms-user
username = USERNAME1
password = SECRET1
name = user_smsc_fake
user-deny-ip = *.*.*.*
user-allow-ip = 127.0.0.*;192.168.1.*
forced-smsc = smscfake
default-sender = mycompany
max-messages = 3
concatenation = 1
omit-empty = 1
#

# SMSC PRODUCTION
group = sendsms-user
username = USERNAME2
password = SECRET2
name = user_smsc_prod
user-deny-ip = *.*.*.*
user-allow-ip = 127.0.0.*;192.168.1.*
forced-smsc = smscprod
default-sender = mycompany
max-messages = 3
concatenation = 1
omit-empty = 1
#



#
# SMSC CONFIG
#



# SMSC FAKEPLEX
group = smsc
smsc = smpp
smsc-id = smscfake
allowed-smsc-id = smscfake
host = SMSC HOSTNAME (GATEWAY A)
port = 3205
receive-port = 3205
transceiver-mode = true
smsc-username = USERNAME_SMSC
smsc-password = SECRET_SMSC
system-type = mycompany3
service-type = 18170
max-pending-submits = 10
msg-id-type = 0x01
log-file = /var/log/kannel/smsc.gatewayA.log
log-level = 1

group = smsc
smsc = smpp
smsc-id = smscfake
allowed-smsc-id = smscfake
host = SMSC HOSTNAME (GATEWAY B)
port = 3205
receive-port = 3205
transceiver-mode = true
smsc-username = USERNAME_SMSC
smsc-password = SECRET_SMSC
system-type = mycompany3
service-type = 18170
max-pending-submits = 10
msg-id-type = 0x01
log-file = /var/log/kannel/smsc.gatewayB.log
log-level = 1
#

# SMSC PRODUCTION
group = smsc
smsc = smpp
smsc-id = smscprod
allowed-smsc-id = smscprod
host = SMSC HOSTNAME (GATEWAY A)
port = 3205
receive-port = 3205
transceiver-mode = true
smsc-username = USERNAME_SMSC
smsc-password = SECRET_SMSC
system-type = mycompany4
service-type = 16570
max-pending-submits = 10
msg-id-type = 0x01
log-file = /var/log/kannel/smsc.gatewayA.log
log-level = 1

group = smsc
smsc = smpp
smsc-id = smscprod
allowed-smsc-id = smscprod
host = SMSC HOSTNAME (GATEWAY B)
port = 3205
receive-port = 3205
transceiver-mode = true
smsc-username = USERNAME_SMSC
smsc-password = SECRET_SMSC
system-type = mycompany4
service-type = 16570
max-pending-submits = 10
msg-id-type = 0x01
log-file = /var/log/kannel/smsc.gatewayB.log
log-level = 1
#


Il giorno 07/dic/2011, alle ore 17:08, Mohammed Saleem ha scritto:

Hi Fabio

did you check bearerbox and smsbox for errors?

Also share your full configurations.



On Wed, Dec 7, 2011 at 4:50 PM, Fabio Sangiovanni 
sangiova...@nweb.itmailto:sangiova...@nweb.it wrote:
Hello list,

the company I work for is using Kannel 1.4.3 on CentOS 6 as SMS 

Plz help regarding. SMSC rejected login to transmit, code 0x0000000d (Bind Failed).

2011-12-09 Thread Anshu Sah
Hi,

I am getting very strange error. SMSC rejected login to transmit, code
0x000d (Bind Failed).
I got your reference from
http://www.kannel.org/pipermail/devel/2008-May/001709.html

Please find the logs below.


2011-12-09 20:36:31 [16601] [46] WARNING: SMPP: Unknown
TLV(0x0006,0x0001,03) for PDU type (deliver_sm) received!
2011-12-09 20:36:41 [16601] [45] WARNING: SMPP: PDU NULL terminated string
(system_id) has no NULL.
2011-12-09 20:36:41 [16601] [45] ERROR: SMPP[x]: SMSC rejected
login to transmit, code 0x000d (Bind Failed).
2011-12-09 20:36:41 [16601] [45] ERROR: SMPP[x]: Couldn't connect
to SMS center (retrying in 60 seconds).
2011-12-09 20:37:19 [16601] [46] WARNING: SMPP: Unknown
TLV(0x000e,0x0001,01) for PDU type (deliver_sm) received!
2011-12-09 20:37:19 [16601] [46] WARNING: SMPP: Unknown
TLV(0x0006,0x0001,03) for PDU type (deliver_sm) received!
2011-12-09 20:37:41 [16601] [45] WARNING: SMPP: PDU NULL terminated string
(system_id) has no NULL.
2011-12-09 20:37:41 [16601] [45] ERROR: SMPP[x]: SMSC rejected
login to transmit, code 0x000d (Bind Failed).
2011-12-09 20:37:41 [16601] [45] ERROR: SMPP[x]: Couldn't connect
to SMS center (retrying in 60 seconds).


Please guide me regarding this.

Regards
Anshu Sah


Re: Plz help regarding. SMSC rejected login to transmit, code 0x0000000d (Bind Failed).

2011-12-09 Thread ha...@aeon.pk
Your connection is configured/binded as RECEIVER only on the SMSC side. Ask
your opreator to allow TRANSCEIVER mode binding for your LA, or give you
TRANSMITTER settings separately.

On Fri, Dec 9, 2011 at 8:13 PM, Anshu Sah sah.an...@ymail.com wrote:


 Hi,

 I am getting very strange error. SMSC rejected login to transmit, code
 0x000d (Bind Failed).
 I got your reference from
 http://www.kannel.org/pipermail/devel/2008-May/001709.html

 Please find the logs below.


 2011-12-09 20:36:31 [16601] [46] WARNING: SMPP: Unknown
 TLV(0x0006,0x0001,03) for PDU type (deliver_sm) received!
 2011-12-09 20:36:41 [16601] [45] WARNING: SMPP: PDU NULL terminated string
 (system_id) has no NULL.
 2011-12-09 20:36:41 [16601] [45] ERROR: SMPP[x]: SMSC rejected
 login to transmit, code 0x000d (Bind Failed).
 2011-12-09 20:36:41 [16601] [45] ERROR: SMPP[x]: Couldn't connect
 to SMS center (retrying in 60 seconds).
 2011-12-09 20:37:19 [16601] [46] WARNING: SMPP: Unknown
 TLV(0x000e,0x0001,01) for PDU type (deliver_sm) received!
 2011-12-09 20:37:19 [16601] [46] WARNING: SMPP: Unknown
 TLV(0x0006,0x0001,03) for PDU type (deliver_sm) received!
 2011-12-09 20:37:41 [16601] [45] WARNING: SMPP: PDU NULL terminated string
 (system_id) has no NULL.
 2011-12-09 20:37:41 [16601] [45] ERROR: SMPP[x]: SMSC rejected
 login to transmit, code 0x000d (Bind Failed).
 2011-12-09 20:37:41 [16601] [45] ERROR: SMPP[x]: Couldn't connect
 to SMS center (retrying in 60 seconds).


 Please guide me regarding this.

 Regards
 Anshu Sah




Re: SMS push performance problem

2011-12-09 Thread ha...@aeon.pk
Why dont u use SQLBOX?

On Fri, Dec 9, 2011 at 7:44 PM, Fabio Sangiovanni sangiova...@nweb.itwrote:

  Thanks again Mohammed, I'll change those settings as soon as I get back
 to work.
 I'll keep you posted! :)

  Cheers,
 Fabio


  Il giorno 09/dic/2011, alle ore 15:21, Mohammed Saleem ha scritto:

  Hey Fabio

  I can't provide a 100% solution for this issue before seeing the log.
 Try to check the log and see if there is any error. But most probably it is
 an open-files limitation problem, because you haven't set a limit to 
 sms-outgoing-queue-limit.
 But Actually this depends on your throughput and how many messages you put
 in the queue of each connection. Try to do the following:


  (1) increase the limit of open-files for the user running kannel.
 (2) set a limit for sms-outgoing-queue-limit, for example don't make it
 more than 100 per 40 SMS/S throughput. This way kannel will reject any
 message when the queue is full (see the HTTP response for the client
 application which sends messages, you need to handle this kind of response
 to retry on the rejected messages due to Queue Full)




  Best Regards,
 Mohammed M I Sleem

 http://www.abusleem.net  - Personal blog



 On Fri, Dec 9, 2011 at 4:01 PM, Fabio Sangiovanni sangiova...@nweb.itwrote:

  Hi Mohammed,

  thanks for your reply.
 Unfortunately I won't be at my workplace again until next monday, so I
 won't be able to provide detailed logs since then.
 On the other hand, I can post the kannel.conf file currently in use on
 the test machine.
 Thanks again for your help. I'll post relevant log entries ASAP.

  Cheers,
 Fabio


  
 #
 # BEARERBOX
 #
 

  group = core
 admin-port = 13000
 admin-password = SECRET
 #status-password = SECRET
 admin-deny-ip = *.*.*.*
 admin-allow-ip = 127.0.0.*;192.168.1.*
 smsbox-port = 13003
 #wapbox-port = 13002
 #wdp-interface-name = *
 box-deny-ip = *.*.*.*
 box-allow-ip = 127.0.0.1
 log-file = /var/log/kannel/bearerbox.log
 access-log = /var/log/kannel/access.log
 store-type = spool
 store-location = /var/spool/kannel
 log-level = 1
 #log-level = 0
 sms-incoming-queue-limit = -1
 sms-outgoing-queue-limit = -1
 sms-resend-retry = 0
 dlr-storage = internal


  
 #
 # SMSBOX
 #
 

  group = smsbox
 bearerbox-host = localhost
 sendsms-port = 13013
 sendsms-chars = 0123456789 
 log-file = /var/log/kannel/smsbox.log
 log-level = 1
 #log-level = 0
 access-log = /var/log/kannel/access.log


  
 #
 # ACCOUNT/SMSC MAPPINGS
 #
 


  # SMSC FAKEPLEX
 group = sendsms-user
 username = USERNAME1
 password = SECRET1
 name = user_smsc_fake
 user-deny-ip = *.*.*.*
 user-allow-ip = 127.0.0.*;192.168.1.*
 forced-smsc = smscfake
 default-sender = mycompany
 max-messages = 3
 concatenation = 1
 omit-empty = 1
 #

  # SMSC PRODUCTION
 group = sendsms-user
 username = USERNAME2
 password = SECRET2
 name = user_smsc_prod
 user-deny-ip = *.*.*.*
 user-allow-ip = 127.0.0.*;192.168.1.*
 forced-smsc = smscprod
 default-sender = mycompany
 max-messages = 3
 concatenation = 1
 omit-empty = 1
 #


  
 #
 # SMSC CONFIG
 #
 


  # SMSC FAKEPLEX
 group = smsc
 smsc = smpp
 smsc-id = smscfake
 allowed-smsc-id = smscfake
 host = SMSC HOSTNAME (GATEWAY A)
 port = 3205
 receive-port = 3205
 transceiver-mode = true
 smsc-username = USERNAME_SMSC
 smsc-password = SECRET_SMSC
 system-type = mycompany3
 service-type = 18170
 max-pending-submits = 10
 msg-id-type = 0x01
 log-file = /var/log/kannel/smsc.gatewayA.log
 log-level = 1

  group = smsc
 smsc = smpp
 smsc-id = smscfake
 allowed-smsc-id = smscfake
 host = SMSC HOSTNAME (GATEWAY B)
 port = 3205
 receive-port = 3205
 transceiver-mode = true
 smsc-username = USERNAME_SMSC
 smsc-password = SECRET_SMSC
 system-type = mycompany3
 service-type = 18170
 max-pending-submits = 10
 msg-id-type = 0x01
 log-file = /var/log/kannel/smsc.gatewayB.log
 log-level = 1
 #

  # SMSC PRODUCTION
 group = smsc
 smsc = smpp
 smsc-id = smscprod
 allowed-smsc-id = smscprod
 host = SMSC HOSTNAME (GATEWAY A)
 port = 3205
 receive-port = 3205
 transceiver-mode = true
 smsc-username = USERNAME_SMSC
 smsc-password = SECRET_SMSC
 system-type = mycompany4
 service-type = 16570
 max-pending-submits = 10
 msg-id-type = 0x01
 log-file = /var/log/kannel/smsc.gatewayA.log
 log-level = 1

  group = smsc
 smsc = smpp
 smsc-id = smscprod
 allowed-smsc-id = smscprod
 host = SMSC HOSTNAME (GATEWAY B)
 port = 3205
 receive-port = 3205
 transceiver-mode = true
 smsc-username = USERNAME_SMSC
 smsc-password = SECRET_SMSC
 system-type = mycompany4
 service-type = 16570
 max-pending-submits = 10
 msg-id-type = 0x01
 log-file = /var/log/kannel/smsc.gatewayB.log
 log-level = 1
 #


  Il giorno 07/dic/2011, alle ore 17:08, Mohammed Saleem ha scritto:

  Hi Fabio

  did you check bearerbox and 

Re: smsc send only

2011-12-09 Thread ha...@aeon.pk
You can supress incoming messages for desired LAs.

On Fri, Dec 9, 2011 at 5:21 PM, Marcin iwa...@gmail.com wrote:

 Hi,

 Is it possible to set kannel config, that for some smsc kannel only send
 messages but is not requesting to receive messages. (I don't know if I
 understand smsc driver).

 We have 3 locations, but only one physical number (123 456 789) and many
 alphanumeric 'labels' ( 'Test','SuperSMS', etc.). I wont to send messages
 from 3 locations, but receive them in only one. Is it possible to set
 config to handle such situation?

 Thanks for answer.
 Marcin




Re: Plz help regarding. SMSC rejected login to transmit, code 0x0000000d (Bind Failed).

2011-12-09 Thread Alejandro Guerrieri
You need to speak with the carrier, they're returning that error, so you
can rule out connectivity at least.

Regards,

Alex

On Fri, Dec 9, 2011 at 10:13 AM, Anshu Sah sah.an...@ymail.com wrote:


 Hi,

 I am getting very strange error. SMSC rejected login to transmit, code
 0x000d (Bind Failed).
 I got your reference from
 http://www.kannel.org/pipermail/devel/2008-May/001709.html

 Please find the logs below.


 2011-12-09 20:36:31 [16601] [46] WARNING: SMPP: Unknown
 TLV(0x0006,0x0001,03) for PDU type (deliver_sm) received!
 2011-12-09 20:36:41 [16601] [45] WARNING: SMPP: PDU NULL terminated string
 (system_id) has no NULL.
 2011-12-09 20:36:41 [16601] [45] ERROR: SMPP[x]: SMSC rejected
 login to transmit, code 0x000d (Bind Failed).
 2011-12-09 20:36:41 [16601] [45] ERROR: SMPP[x]: Couldn't connect
 to SMS center (retrying in 60 seconds).
 2011-12-09 20:37:19 [16601] [46] WARNING: SMPP: Unknown
 TLV(0x000e,0x0001,01) for PDU type (deliver_sm) received!
 2011-12-09 20:37:19 [16601] [46] WARNING: SMPP: Unknown
 TLV(0x0006,0x0001,03) for PDU type (deliver_sm) received!
 2011-12-09 20:37:41 [16601] [45] WARNING: SMPP: PDU NULL terminated string
 (system_id) has no NULL.
 2011-12-09 20:37:41 [16601] [45] ERROR: SMPP[x]: SMSC rejected
 login to transmit, code 0x000d (Bind Failed).
 2011-12-09 20:37:41 [16601] [45] ERROR: SMPP[x]: Couldn't connect
 to SMS center (retrying in 60 seconds).


 Please guide me regarding this.

 Regards
 Anshu Sah




Re: SMS push performance problem

2011-12-09 Thread Fabio Sangiovanni
Hi hamza,

do you mean using a database as dlr storage, don't you? I'm kind of a newbie of 
Kannel, so I've tried to keep things simple at first. But if this is going to 
solve mi performance issue, I'll dig more deep into it.
Have you got some good reading on the matter to suggest?

Thanks a lot,
Fabio

Il giorno 09/dic/2011, alle ore 16:29, ha...@aeon.pkmailto:ha...@aeon.pk ha 
scritto:

Why dont u use SQLBOX?

On Fri, Dec 9, 2011 at 7:44 PM, Fabio Sangiovanni 
sangiova...@nweb.itmailto:sangiova...@nweb.it wrote:
Thanks again Mohammed, I'll change those settings as soon as I get back to work.
I'll keep you posted! :)

Cheers,
Fabio


Il giorno 09/dic/2011, alle ore 15:21, Mohammed Saleem ha scritto:

Hey Fabio

I can't provide a 100% solution for this issue before seeing the log. Try to 
check the log and see if there is any error. But most probably it is an 
open-files limitation problem, because you haven't set a limit to 
sms-outgoing-queue-limit. But Actually this depends on your throughput and 
how many messages you put in the queue of each connection. Try to do the 
following:


(1) increase the limit of open-files for the user running kannel.
(2) set a limit for sms-outgoing-queue-limit, for example don't make it more 
than 100 per 40 SMS/S throughput. This way kannel will reject any message when 
the queue is full (see the HTTP response for the client application which sends 
messages, you need to handle this kind of response to retry on the rejected 
messages due to Queue Full)




Best Regards,
Mohammed M I Sleem

http://www.abusleem.nethttp://www.abusleem.net/  - Personal blog



On Fri, Dec 9, 2011 at 4:01 PM, Fabio Sangiovanni 
sangiova...@nweb.itmailto:sangiova...@nweb.it wrote:
Hi Mohammed,

thanks for your reply.
Unfortunately I won't be at my workplace again until next monday, so I won't be 
able to provide detailed logs since then.
On the other hand, I can post the kannel.conf file currently in use on the test 
machine.
Thanks again for your help. I'll post relevant log entries ASAP.

Cheers,
Fabio



#
# BEARERBOX
#


group = core
admin-port = 13000
admin-password = SECRET
#status-password = SECRET
admin-deny-ip = *.*.*.*
admin-allow-ip = 127.0.0.*;192.168.1.*
smsbox-port = 13003
#wapbox-port = 13002
#wdp-interface-name = *
box-deny-ip = *.*.*.*
box-allow-ip = 127.0.0.1
log-file = /var/log/kannel/bearerbox.log
access-log = /var/log/kannel/access.log
store-type = spool
store-location = /var/spool/kannel
log-level = 1
#log-level = 0
sms-incoming-queue-limit = -1
sms-outgoing-queue-limit = -1
sms-resend-retry = 0
dlr-storage = internal



#
# SMSBOX
#


group = smsbox
bearerbox-host = localhost
sendsms-port = 13013
sendsms-chars = 0123456789 
log-file = /var/log/kannel/smsbox.log
log-level = 1
#log-level = 0
access-log = /var/log/kannel/access.log



#
# ACCOUNT/SMSC MAPPINGS
#



# SMSC FAKEPLEX
group = sendsms-user
username = USERNAME1
password = SECRET1
name = user_smsc_fake
user-deny-ip = *.*.*.*
user-allow-ip = 127.0.0.*;192.168.1.*
forced-smsc = smscfake
default-sender = mycompany
max-messages = 3
concatenation = 1
omit-empty = 1
#

# SMSC PRODUCTION
group = sendsms-user
username = USERNAME2
password = SECRET2
name = user_smsc_prod
user-deny-ip = *.*.*.*
user-allow-ip = 127.0.0.*;192.168.1.*
forced-smsc = smscprod
default-sender = mycompany
max-messages = 3
concatenation = 1
omit-empty = 1
#



#
# SMSC CONFIG
#



# SMSC FAKEPLEX
group = smsc
smsc = smpp
smsc-id = smscfake
allowed-smsc-id = smscfake
host = SMSC HOSTNAME (GATEWAY A)
port = 3205
receive-port = 3205
transceiver-mode = true
smsc-username = USERNAME_SMSC
smsc-password = SECRET_SMSC
system-type = mycompany3
service-type = 18170
max-pending-submits = 10
msg-id-type = 0x01
log-file = /var/log/kannel/smsc.gatewayA.log
log-level = 1

group = smsc
smsc = smpp
smsc-id = smscfake
allowed-smsc-id = smscfake
host = SMSC HOSTNAME (GATEWAY B)
port = 3205
receive-port = 3205
transceiver-mode = true
smsc-username = USERNAME_SMSC
smsc-password = SECRET_SMSC
system-type = mycompany3
service-type = 18170
max-pending-submits = 10
msg-id-type = 0x01
log-file = /var/log/kannel/smsc.gatewayB.log
log-level = 1
#

# SMSC PRODUCTION
group = smsc
smsc = smpp
smsc-id = smscprod
allowed-smsc-id = smscprod
host = SMSC HOSTNAME (GATEWAY A)
port = 3205
receive-port = 3205
transceiver-mode = true
smsc-username = USERNAME_SMSC
smsc-password = SECRET_SMSC
system-type = mycompany4
service-type = 16570
max-pending-submits = 10
msg-id-type = 0x01
log-file = /var/log/kannel/smsc.gatewayA.log
log-level = 1

group = smsc
smsc = smpp
smsc-id = smscprod
allowed-smsc-id = smscprod
host = SMSC HOSTNAME (GATEWAY B)
port = 3205
receive-port = 3205
transceiver-mode = true
smsc-username = USERNAME_SMSC

Re: smsc send only

2011-12-09 Thread Marcin
Can you explain a little bit more how can I 'supress incoming messages'? 
I couldn't find any info in user guide.


W dniu 09.12.2011 16:30, ha...@aeon.pk pisze:

You can supress incoming messages for desired LAs.

On Fri, Dec 9, 2011 at 5:21 PM, Marcin iwa...@gmail.com 
mailto:iwa...@gmail.com wrote:


Hi,

Is it possible to set kannel config, that for some smsc kannel
only send messages but is not requesting to receive messages. (I
don't know if I understand smsc driver).

We have 3 locations, but only one physical number (123 456 789)
and many alphanumeric 'labels' ( 'Test','SuperSMS', etc.). I wont
to send messages from 3 locations, but receive them in only one.
Is it possible to set config to handle such situation?

Thanks for answer.
Marcin






Re: Kannel training / conferences / seminar

2011-12-09 Thread Willy Mularto
I am not sure there is one. All the seminars and training is going through via 
this mailing list ;)



On Dec 10, 2011, at 2:00 AM, Allen Chan wrote:

 All,
 
 I have been tasked to build a scalable, high available SMS platform with 
 kannel from ground up. 
 I was wondering if there are any seminars/training that my company can send 
 me to as a kannel bootcamp.
 
 Thanks,
 Allen Chan

Willy Mularto
F300HD+MR18DE (NLC1725)