Re: smsc routing & throughput

"Chaitanya Bhatt // Viva" <[email protected]>
Newsgroups gmane.comp.mobile.kannel.devel
Message-ID <[email protected]>
On Sat, Dec 20, 2008 at 12:46 PM, Chaitanya Bhatt // Viva <
[email protected]> wrote:

> Thanks a lot for your precious help
>
> I have done following changes:
> ->default-smsc=1
> ->commented smsbox-route group
> ->commented throughput=20
>
> But it's giving warning
>  WARNING: Message rejected by bearerbox, no router!
>  WARNING: Cannot find SMSCConn for message to <xxxxxxxxxx>, rejected.
>
> Second thing i am specifying dlr-mask & dlr-url in CGI-BIN URL.
>
> Temporary i am splitting my Mobile No. series into batches & sending each
> batch with different smsc by specifying smsc on URL.
>
> Please Reply
>
>
>
> On Sat, Dec 20, 2008 at 12:13 PM, Nikos Balkanas <[email protected]>wrote:
>
>>  Hi,
>>
>> Concerning my response (3), not setting dlr-mask in your URL has the same
>> exactly effect as setting it to 0.
>>
>> I didn't notice it before, but you spcify throughput = 20 in each smsc.
>> Therefore, since you are routing only from one smsc, your total throughput
>> cannot exceed 20.  This could explain what you have. Comment it out and you
>> should see much faster processing.
>>
>> You mentioned that only 1 smsc is used. I imagine it is sms1. Right?
>>
>> Comment out the smsbox route group. You are restricting routing only to 2
>> smscs.
>>
>> What is the URL you are sending?
>>
>> In sendsms-user you specify default-smsc = 1.
>>
>> If this doesn't help, kill kannel.
>> Then:
>>
>> bearerbox <confFile> &
>> smsbox -v 4 <confFile> &
>>
>> Try ~5 smss and post output to the list.
>>
>> BR,
>> Nikos
>>
>> ----- Original Message -----
>>  *From:* Chaitanya Bhatt // Viva <[email protected]>
>>  *To:* Nikos Balkanas <[email protected]> ; [email protected]
>> *Sent:* Saturday, December 20, 2008 8:19 AM
>> *Subject:* Re: smsc routing & throughput
>>
>> Thanks a lot for reply.
>>
>> I got how to check routing in core group.
>> But my all msgs are routed through only one smsc.
>>
>> To solve it i am specifying smsc on cgi-bin URL through php, but i think
>> it works slow to split them into batches for each smsc.
>>
>> I want to configure kannel in such a way that it route msgs automatically.
>> I am attaching my smskannel.conf, Please let me know why
>> routing is not working & throughput is much less.
>>
>> Please reply.
>>
>>
>> # CORE
>>
>> group = core
>> admin-port = 13000
>> smsbox-port = 13001
>> admin-password = xxxx
>> #status-password = xxx
>> #admin-deny-ip = ""
>> #admin-allow-ip = ""
>> #log-file = "/tmp/kannel.log"
>> #log-level = 0
>> box-deny-ip = "*.*.*.*"
>> box-allow-ip = "127.0.0.1"
>> #maximum-queue-length=20
>> sms-incoming-queue-limit=-1
>> sms-resend-retry=-1
>> sms-resend-freq=1800
>> #unified-prefix = "+358,00358,0;+,00"
>> #access-log = "/tmp/access.log"
>> #store-file = "kannel.store"
>> #ssl-server-cert-file = "cert.pem"
>> #ssl-server-key-file = "key.pem"
>> #ssl-certkey-file = "mycertandprivkeyfile.pem"
>>
>> #----------------------------- ----------------
>> # SMSC CONNECTIONS
>>
>> group= smsc
>> smsc= smpp
>> smsc-id=smsc1
>> host=xxx.xxx.xxx.xxx
>> port = xxxx
>> smsc-username=xxxx
>> smsc-password=xxxx
>> connect-allow-ip = 127.0.0.1
>> system-type="SMPP"
>> address-range=""
>> transceiver-mode=1
>> source-addr-ton=1
>> source-addr-npi=1
>> dest-addr-ton=1
>> dest-addr-npi=1
>> msg-id-type =0x02
>> reroute-dlr = true
>> throughput=20
>> allowed-smsc-id="smsc1,smsc2"
>> preferred-smsc-id=smsc1
>>
>>
>> group=smsc
>> smsc=smpp
>> smsc-id=smsc2
>> host=xxx.xxx.xxx.xxx
>> port = xxxx
>> smsc-username=xxxx
>> smsc-password=xxxx
>> system-type="SMPP"
>> source-addr-ton=1
>> source-addr-npi=1
>> dest-addr-ton=1
>> dest-addr-npi=1
>> msg-id-type=0x02
>> reroute-dlr=true
>> throughput=20
>> allowed-smsc-id="smsc2;smsc3"
>> preferred-smsc-id=smsc2
>>
>>
>> group=smsc
>> smsc=smpp
>> smsc-id=smsc3
>> host=xxx.xxx.xxx.xxx
>> port = xxxx
>> smsc-username=xxxx
>> smsc-password=xxxx
>> system-type="SMPP"
>> source-addr-ton=1
>> source-addr-npi=1
>> dest-addr-ton=1
>> dest-addr-npi=1
>> msg-id-type=0x02
>> reroute-dlr=true
>> throughput=20
>> allowed-smsc-id="smsc1;smsc2;smsc3"
>> preferred-smsc-id=smsc3
>>
>> #---------------------------------------------
>> # SMSBOX SETUP
>>
>> group = smsbox
>> bearerbox-host = 127.0.0.1
>> smsbox-id=s1
>> sendsms-port = 13013
>> global-sender = 13013
>> sendsms-chars = "0123456789 +-"
>> #immediate-sendsms-reply = 1
>> log-file = "/smsbox.log"
>> log-level = 0
>> mo-recode=1
>> #smsc-ids=smsc1;smsc2;smsc3
>> #access-log = "/tmp/access.log"
>>
>> group=smsbox-route
>> smsbox-id=s1
>> smsc-ids="smsc1;smsc2"
>>
>> #---------------------------------------------
>> # SEND-SMS USERS
>>
>> group = sendsms-user
>> username = xxxx
>> password = xxxx
>> concatenation = true
>> max-messages=3
>> default-smsc=smsc1
>> #forced-smsc=smsc2
>> #user-deny-ip = ""
>> #user-allow-ip = ""
>>
>> #---------------------------------------------
>> # SERVICES
>>
>> group = sms-service
>> keyword = default
>> concatenation = true
>> max-messages=3
>> text = "No service specified"
>> accepted-smsc=smsc2
>>
>> group = sms-service
>> keyword = nop
>> concatenation = true
>> max-messages=3
>> text = <text app 410 characters>
>> accepted-smsc=smsc1
>>
>>
>> On Sat, Dec 20, 2008 at 1:43 AM, Nikos Balkanas <[email protected]>wrote:
>>
>>>  I would appreciate not yelling. *Bold* and *CAPS* mean just that. We
>>> are just volunteers.
>>>
>>> 1) You can fiddle with the parameters in core access.log. %I is the
>>> smsc-id sent /message.
>>> 2) Run benchmarks on your kannel installation. If you run test_ppg and
>>> route it through fake smsc, you should be getting smt like 1000 msg/sec on
>>> an average PC (64bit Solaris, 2.9 Ghz Opteron processor (dual core AMD)).
>>> Why this is not realized? A million reasons. Your line could be really
>>> bad, but not so bad as to the throughput you have (15 x400 = 6000 B/s or
>>> 60kbps). I imagine you are better than that. My guess would be that you
>>> should either change smsc or ask your smsc for some benchmarks. You have 3
>>> lines, why not try a couple of those to different providers and go with the
>>> fastest?
>>> 3) Bysetting dlr-mask = 0.
>>>
>>> BR,
>>> Nikos
>>>
>>>  ----- Original Message -----
>>>  *From:* Chaitanya Bhatt // Viva <[email protected]>
>>> *To:* [email protected]
>>> *Sent:* Friday, December 19, 2008 12:19 PM
>>> *Subject:* smsc routing & throughput
>>>
>>>  Hi
>>>
>>> I want to use 3 smsc connection in my smskannel.conf.
>>> I have configured it as follow:
>>>
>>> # CORE
>>>
>>> group = core
>>> admin-port = 13000
>>> smsbox-port = 13001
>>> admin-password = xxxx
>>> #status-password = xxx
>>> #admin-deny-ip = ""
>>> #admin-allow-ip = ""
>>> #log-file = "/tmp/kannel.log"
>>> #log-level = 0
>>> box-deny-ip = "*.*.*.*"
>>> box-allow-ip = "127.0.0.1"
>>> #maximum-queue-length=20
>>> sms-incoming-queue-limit=-1
>>> sms-resend-retry=-1
>>> sms-resend-freq=1800
>>> #unified-prefix = "+358,00358,0;+,00"
>>> #access-log = "/tmp/access.log"
>>> #store-file = "kannel.store"
>>> #ssl-server-cert-file = "cert.pem"
>>> #ssl-server-key-file = "key.pem"
>>> #ssl-certkey-file = "mycertandprivkeyfile.pem"
>>>
>>> #---------------------------------------------
>>> # SMSC CONNECTIONS
>>>
>>> group= smsc
>>> smsc= smpp
>>> smsc-id=smsc1
>>> host=xxx.xxx.xxx.xxx
>>> port = xxxx
>>> smsc-username=xxxx
>>> smsc-password=xxxx
>>> connect-allow-ip = 127.0.0.1
>>> system-type="SMPP"
>>> address-range=""
>>> transceiver-mode=1
>>> source-addr-ton=1
>>> source-addr-npi=1
>>> dest-addr-ton=1
>>> dest-addr-npi=1
>>> msg-id-type =0x02
>>> reroute-dlr = true
>>> throughput=20
>>> allowed-smsc-id="smsc1,smsc2"
>>> preferred-smsc-id=smsc1
>>>
>>>
>>> group=smsc
>>> smsc=smpp
>>> smsc-id=smsc2
>>> host=xxx.xxx.xxx.xxx
>>> port = xxxx
>>> smsc-username=xxxx
>>> smsc-password=xxxx
>>> system-type="SMPP"
>>> source-addr-ton=1
>>> source-addr-npi=1
>>> dest-addr-ton=1
>>> dest-addr-npi=1
>>> msg-id-type=0x02
>>> reroute-dlr=true
>>> throughput=20
>>> allowed-smsc-id="smsc2;smsc3"
>>> preferred-smsc-id=smsc2
>>>
>>>
>>> group=smsc
>>> smsc=smpp
>>> smsc-id=smsc3
>>> host=xxx.xxx.xxx.xxx
>>> port = xxxx
>>> smsc-username=xxxx
>>> smsc-password=xxxx
>>> system-type="SMPP"
>>> source-addr-ton=1
>>> source-addr-npi=1
>>> dest-addr-ton=1
>>> dest-addr-npi=1
>>> msg-id-type=0x02
>>> reroute-dlr=true
>>> throughput=20
>>> allowed-smsc-id="smsc1;smsc2;smsc3"
>>> preferred-smsc-id=smsc3
>>>
>>> #---------------------------------------------
>>> # SMSBOX SETUP
>>>
>>> group = smsbox
>>> bearerbox-host = 127.0.0.1
>>> smsbox-id=s1
>>> sendsms-port = 13013
>>> global-sender = 13013
>>> sendsms-chars = "0123456789 +-"
>>> #immediate-sendsms-reply = 1
>>> log-file = "/smsbox.log"
>>> log-level = 0
>>> mo-recode=1
>>> #smsc-ids=smsc1;smsc2;smsc3
>>> #access-log = "/tmp/access.log"
>>>
>>> group=smsbox-route
>>> smsbox-id=s1
>>> smsc-ids="smsc1;smsc2"
>>>
>>> #---------------------------------------------
>>> # SEND-SMS USERS
>>>
>>> group = sendsms-user
>>> username = xxxx
>>> password = xxxx
>>> concatenation = true
>>> max-messages=3
>>> default-smsc=smsc1
>>> #forced-smsc=smsc2
>>> #user-deny-ip = ""
>>> #user-allow-ip = ""
>>>
>>> #---------------------------------------------
>>> # SERVICES
>>>
>>> group = sms-service
>>> keyword = default
>>> concatenation = true
>>> max-messages=3
>>> text = "No service specified"
>>> accepted-smsc=smsc2
>>>
>>> group = sms-service
>>> keyword = nop
>>> concatenation = true
>>> max-messages=3
>>> text = <text app 410 characters>
>>> accepted-smsc=smsc1
>>>
>>>
>>>
>>> Now , *1. I want to check whether routing is correct through 3 SMSCs: ?
>>> How to check this?
>>>           2.Kannel performing throughput as total 15sms/second including
>>> all 3 smsc . How to increase throughput ? SMPP account provider has given
>>> 30sms/second for EACH smsc.
>>>          3.How to off delivery report on runtime if load increases ?
>>>
>>> PLEASE REPLY !!
>>>
>>> *Thanks & Regards
>>> Chaitanya Bhatt
>>> *
>>> *
>>>
>>>
>>>
>>
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.