Re: Help: Kannel users from the Philippines
On 2004-08-10 22:47:13 +0800 Josephine Forte [EMAIL PROTECTED] wrote: Hi, Anybody here who's a kannel user from the phillipines? We are using kannel cvs20040621 version on Red Hat Linux 7.3. I used CIMD2 protocol to connect to SMART Telecom. I just need some help because we already set up kannel, MO and MT are ok, so is sendsms(PUSH) but I'm having problems with kannel receiving and sending out messages too slow. about 3-5 sms/sec. I already turned off delivery report request, but still, message sending/receiving rate is too slow and queue is getting bigger and bigger. Any advice? I think thats already fast for cimd2. unless you mean 3-5 sec per sms.
Re: Help: Kannel users from the Philippines
Sir, They(SMSC Engrs) are saying that we can send out as much as 500sms/sec and our target rate is only 20-30sms/sec. Any ideas how to improve this rate, the queue we had keeps on getting bigger specially when we do broadcasting where sending out rate at worst goes to 2-3sms/sec. I badly need to improve this performance but i don't know where to start. :( I've already used test_cimd2 to test kannel performance, everything works well and traffic rate is around more than a 100/sec. But when I connect to SMSC traffic rate slows down to: SMS: inbound 0.07 msg/sec, outbound 1.11 msg/sec But looking at access.log, message processing is @ 3-5sms/sec rate. Thanks in advance -- Josephine G. Forte
Re: Help: Kannel users from the Philippines
We were assigned 2 accounts, one for receiving sms and another for sending. Yes we send MT-reply via HTTP sendsms. We also send PUSH messages using HTTP sendsms. We only logon once, and maintain connection through keepalive of 60 sec. for a better view, kindly see attached configuration and access logs. Thanks again. I really appreciate all the help i can get. Best Regards, Josephine On Tuesday 10 August 2004 08:47, you wrote: On 2004-08-11 00:33:11 +0800 Josephine Forte [EMAIL PROTECTED] wrote: Sir, They(SMSC Engrs) are saying that we can send out as much as 500sms/sec and our target rate is only 20-30sms/sec. Any ideas how to improve this rate, the queue we had keeps on getting bigger specially when we do broadcasting where sending out rate at worst goes to 2-3sms/sec. I badly need to improve this performance but i don't know where to start. :( I've already used test_cimd2 to test kannel performance, everything works well and traffic rate is around more than a 100/sec. But when I connect to SMSC traffic rate slows down to: SMS: inbound 0.07 msg/sec, outbound 1.11 msg/sec But looking at access.log, message processing is @ 3-5sms/sec rate. Thanks in advance Do you login everytime you send data? Do you keep your cimd sessions short? I think there is a login limit with smart smscs. How long is the keepalive in your configurations? Are you traversing a smart firewall? -- Josephine G. Forte Applications Developer Intermedia Solutions, Inc. 64 Washington St. GreenHills, San Juan, M.M. Tel. No. +632 7261443 Fax +632 7276134 004-08-01 00:24:28 Receive SMS [SMSC:receive] [SVC:] [ACT:] [BINF:] [from:639102866123] [to:01] [flags:-1:0:-1:0:-1] [msg:3:new] [udh:0:] 2004-08-01 00:24:28 send-SMS request added - sender:X: 192.168.0.158 target:639102866123 request: 'Invalid keyword. For help, send NEW HELP to 386. ' 2004-08-01 00:24:28 SMS HTTP-request sender:639102866123 request: '' url: 'http://192.168.0.158/smart.php?from_no=639102866123to_no=386message=new' reply: 200 ' successful ' 2004-08-01 00:24:28 Sent SMS [SMSC:send] [SVC:X] [ACT:] [BINF:1486] [from:] [to:639102866123] [flags:-1:0:-1:-1:31] [msg:49:Invalid keyword. For help, send NEW HELP to 386.] [udh:0:] 2004-08-01 00:24:28 DLR SMS [SMSC:send] [SVC:X] [ACT:] [BINF:] [from:] [to:639102866123] [flags:-1:-1:-1:-1:8] [msg:4:ACK/] [udh:0:] 2004-08-01 06:22:40 Receive SMS [SMSC:receive] [SVC:] [ACT:] [BINF:] [from:639192554458] [to:02] [flags:-1:0:-1:0:-1] [msg:4:MEGA] [udh:0:] 2004-08-01 06:22:40 send-SMS request added - sender:X: 192.168.0.158 target:639192554458 request: 'Winner MEGA STARTXT:U can WIN Nokia3530, P10,000 or P100,000 CASH! Start playing! Right or Wrong? Jaya is host of ASAP MANIA. Reply with MEGA R or MEGA W! ' 2004-08-01 06:22:40 SMS HTTP-request sender:639192554458 request: '' url: 'http://192.168.0.158/smart.php?from_no=639192554458to_no=386message=MEGA' reply: 200 ' successful ' 2004-08-01 06:22:40 Sent SMS [SMSC:send] [SVC:X] [ACT:] [BINF:1486] [from:] [to:639192554458] [flags:-1:0:-1:-1:31] [msg:155:Winner MEGA STARTXT:U can WIN Nokia3530, P10,000 or P100,000 CASH! Start playing! Right or Wrong? Jaya is host of ASAP MANIA. Reply with MEGA R or MEGA W! ] [udh:0:] 2004-08-01 06:22:40 DLR SMS [SMSC:send] [SVC:X] [ACT:] [BINF:] [from:] [to:639192554458] [flags:-1:-1:-1:-1:8] [msg:4:ACK/] [udh:0:] 2004-08-01 08:03:24 Receive SMS [SMSC:receive] [SVC:] [ACT:] [BINF:] [from:639189290721] [to:06] [flags:-1:0:-1:0:-1] [msg:4:Mega] [udh:0:] 2004-08-01 08:03:24 send-SMS request added - sender:X: 192.168.0.158 target:639189290721 request: 'Winner MEGA STARTXT:U can WIN Nokia3530, P10,000 or P100,000 CASH! Start playing! Right or Wrong? Vic Sotto is host of MTB. Reply with MEGA R or MEGA W! ' 2004-08-01 08:03:24 SMS HTTP-request sender:639189290721 request: '' url: 'http://192.168.0.158/smart.php?from_no=639189290721to_no=386message=Mega' reply: 200 ' successful ' 2004-08-01 08:03:24 Sent SMS [SMSC:send] [SVC:X] [ACT:] [BINF:1486] [from:] [to:639189290721] [flags:-1:0:-1:-1:31] [msg:153:Winner MEGA STARTXT:U can WIN Nokia3530, P10,000 or P100,000 CASH! Start playing! Right or Wrong? Vic Sotto is host of MTB. Reply with MEGA R or MEGA W! ] [udh:0:] 2004-08-01 08:03:24 DLR SMS [SMSC:send] [SVC:X] [ACT:] [BINF:] [from:] [to:639189290721] [flags:-1:-1:-1:-1:8] [msg:4:ACK/] [udh:0:] 2004-08-01 08:04:40 Receive SMS [SMSC:receive] [SVC:] [ACT:] [BINF:] [from:639189290721] [to:10] [flags:-1:0:-1:0:-1] [msg:6:Mega w] [udh:0:] 2004-08-01 08:04:41 send-SMS request added - sender:X: 192.168.0.158 target:639189290721 request: '1/2 Congrats! U just earned 1Pt for today's Nokia phone draw! Keep playing! U CAN WIN P100,000 CASH! Sponsored by Winner Corned Beef per DOH-BFAD 0372 s 2004. ' 2004-08-01 08:04:41 send-SMS request added - sender:X:386 192.168.0.158
WARNING: SMPP: PDU element password to long (length is 9, should be 9)
Hi All, Just checking - the SMPP password field can be max octets of 9 in length. But when I set it to be 9 characters in length I get a warning that's it's too long, etc. My understanding of octets is not fantastic (like a C string - has a null char which takes up 1?) so looking for some confirmation on what's happening here (and maybe adjust the warning to be less confusing?). Should the warning read 'should be 8'? Cheers, Alan 2004-08-11 09:25:18 [12549] [14] DEBUG: password: PASSWORD1 ... 2004-08-11 09:25:18 [12549] [14] DEBUG: SMPP PDU dump ends. 2004-08-11 09:25:18 [12549] [14] WARNING: SMPP: PDU element password to long (length is 9, should be 9)
Re: WARNING: SMPP: PDU element password to long (length is 9, should be 9)
Pedro B. wrote:
Let alone the fact that too long is not spelled correctly. At least in
10 locations of the code. and i only checked 4 .c files.
as I said. Patches in 'diff -u' format always welcome ;) So if you
spott something, send in a patch and we'll apply it.
I'm sorry for what i'm about to say, but it's a proven fact:
There is a vast amount of misspelling in both the old docs (that Stipe
aspelled, good stuff), and throughout all the code comments that shade a
very strong lack of credibility to Kannel.
now, Kannel was never been an US project. Finish people started it and
several other european citizen have continued it. Speaking of personal
implications: I'm a croatian citizen, born and living in Germany,
working on a finish project ;)
Everyone can make a typo, but if Kannel is really an english-based
product, there should be at least some being-elementary-school level of
spelling on all the code.
isn't it?
The english is not my mother language is a feeble and worn out excuse
for a development team that (all except Bruno, according to the first
lines of the docs) is made of ceo's, directors, chiefs and the rest of
the upper class management positions plethora.
now, Bruno is also in a remarkable position at a very large operator
(with a red logo in it). He may only be to shy to address this ;)
I guess, the problem is that we all live and work in european
countries that utilize the english language for international
communication, but none of us is really living the english language,
except Paul, Nick and the other guys that live on the islands out there ;)
So, it would be great to let us know where(!) those typos are, and
we're willing to kick them.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
-BEGIN PGP PUBLIC KEY BLOCK-
Version: GnuPG v1.2.2 (Cygwin)
mIsEP6mcYwEEAMDnUiUwrbb+xwTFWN6TxF2+XZu7/alwJMeCwMBRvXtPZqfjpPhS
OkBpU0F4TrVuugz1HINTSaJTYq10AzDQXp5NkyWgckqW79nPAWuOX0dicbJk+cN2
nM2TI4KaxUDe6u8hghNEnH/i2lXsUu9apnP/iixzV81VC2je3uc9hZpnAAYptEVT
dGlwZSBUb2xqIChUZWNobm9sb2d5IENlbnRlciAmIFJlc2VhcmNoIExhYikgPHRv
bGpAd2FwbWUtc3lzdGVtcy5kZT6ItAQTAQIAHgUCP6mcYwIbAwYLCQgHAwIDFQID
AxYCAQIeAQIXgAAKCRABV0w1BqPYRuSqA/wPzsQxao2YePENCtgRTrO86U6zg3sl
OcS6CJFI4FZP5h/xD3GRsNH1+MPSvZlomDdpFnr547DGz/Kq9MXuQwVvlVig5yWZ
K5dtKp1r5YLhxJQBhfirZbRFFnYmf19f18J8OoS28tuFVftDl1AIwJS3HLyBTv6H
g2HyLAEKQIp30Q==
=aYCI
-END PGP PUBLIC KEY BLOCK-
Re: WARNING: SMPP: PDU element password to long (length is 9, should be 9)
Stipe Tolj wrote: Pedro B. wrote: So this is a generic trade-off situation. Would you pick rather a good software/system architect that is not perfect in english, or have a person that does not any grammer typos, but fails to understand and inherit crussial system design aspects? That's why i picked this recent example that i have experienced. I have to confess, guys that pick software and use spellchecking as a deciding factor kind of scare me too. I guess that i wanted to share that scary image. *text insulting consultants removed by conscience* :) And now... where are the damn patches? ;)) I'm on it, i'm on it! :) \\pb
Re: WARNING: SMPP: PDU element password to long (length is 9, should be 9)
Stipe Tolj wrote:
Ok, now about the warning. I see this in gw/smsc/smpp_pdu.c:236:
...
#define NULTERMINATED(name, max_octets) \
if (p-name != NULL) { \
if (octstr_len(p-name) = max_octets) { \
warning(0, SMPP: PDU element %s to long \
(length is %ld, should be %d), \
#name, octstr_len(p-name), max_octets); \
temp = octstr_copy(p-name, 0, max_octets-1); \
} else \
temp = octstr_duplicate(p-name); \
octstr_append(os, temp); \
octstr_destroy(temp); \
} \
octstr_append_char(os, '\0');
...
Which means the warning will go out even when we have the max octets in
the pdu field.
Question should be: why do we compare = and not only ???
I don't see any good reason on the equal compare here.
ok, confirmed that I have been muggling arround that code, see:
http://www.kannel.org/cgi-bin/viewcvs.cgi/gateway/gw/smsc/smpp_pdu.c.diff?r1=1.1r2=1.2
but I actualy don't see a reason why we shouldn't change the if
statement from = compare to pure compare.
Any objections here?
Sitpe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
-BEGIN PGP PUBLIC KEY BLOCK-
Version: GnuPG v1.2.2 (Cygwin)
mIsEP6mcYwEEAMDnUiUwrbb+xwTFWN6TxF2+XZu7/alwJMeCwMBRvXtPZqfjpPhS
OkBpU0F4TrVuugz1HINTSaJTYq10AzDQXp5NkyWgckqW79nPAWuOX0dicbJk+cN2
nM2TI4KaxUDe6u8hghNEnH/i2lXsUu9apnP/iixzV81VC2je3uc9hZpnAAYptEVT
dGlwZSBUb2xqIChUZWNobm9sb2d5IENlbnRlciAmIFJlc2VhcmNoIExhYikgPHRv
bGpAd2FwbWUtc3lzdGVtcy5kZT6ItAQTAQIAHgUCP6mcYwIbAwYLCQgHAwIDFQID
AxYCAQIeAQIXgAAKCRABV0w1BqPYRuSqA/wPzsQxao2YePENCtgRTrO86U6zg3sl
OcS6CJFI4FZP5h/xD3GRsNH1+MPSvZlomDdpFnr547DGz/Kq9MXuQwVvlVig5yWZ
K5dtKp1r5YLhxJQBhfirZbRFFnYmf19f18J8OoS28tuFVftDl1AIwJS3HLyBTv6H
g2HyLAEKQIp30Q==
=aYCI
-END PGP PUBLIC KEY BLOCK-
Re: WARNING: SMPP: PDU element password to long (length is 9, shouldbe 9)
- Original Message - now, Kannel was never been an US project. Finish people started it and several other european citizen have continued it. Speaking of personal implications: I'm a croatian citizen, born and living in Germany, working on a finish project ;) Finnish you mean ;) ducks I'm happy to have a look through the docs sometime and correct any spelling mistakes, do I just check the HTML or is there a better way of doing it? Alex
Re: WARNING: SMPP: PDU element password to long (length is 9, shouldbe 9)
Pedro B. wrote:
Alex,
I'm halfway looking (more like digging) through all the code to make a
manual-spellcheck-patch.
Maybe we can split the work, or maybe you review my patch when i have it
done... can never spellcheck too much, i say :)
I guess running apspell over the diff would help too.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
-BEGIN PGP PUBLIC KEY BLOCK-
Version: GnuPG v1.2.2 (Cygwin)
mIsEP6mcYwEEAMDnUiUwrbb+xwTFWN6TxF2+XZu7/alwJMeCwMBRvXtPZqfjpPhS
OkBpU0F4TrVuugz1HINTSaJTYq10AzDQXp5NkyWgckqW79nPAWuOX0dicbJk+cN2
nM2TI4KaxUDe6u8hghNEnH/i2lXsUu9apnP/iixzV81VC2je3uc9hZpnAAYptEVT
dGlwZSBUb2xqIChUZWNobm9sb2d5IENlbnRlciAmIFJlc2VhcmNoIExhYikgPHRv
bGpAd2FwbWUtc3lzdGVtcy5kZT6ItAQTAQIAHgUCP6mcYwIbAwYLCQgHAwIDFQID
AxYCAQIeAQIXgAAKCRABV0w1BqPYRuSqA/wPzsQxao2YePENCtgRTrO86U6zg3sl
OcS6CJFI4FZP5h/xD3GRsNH1+MPSvZlomDdpFnr547DGz/Kq9MXuQwVvlVig5yWZ
K5dtKp1r5YLhxJQBhfirZbRFFnYmf19f18J8OoS28tuFVftDl1AIwJS3HLyBTv6H
g2HyLAEKQIp30Q==
=aYCI
-END PGP PUBLIC KEY BLOCK-
Re: WARNING: SMPP: PDU element password to long (length is 9, shouldbe 9)
Don't mind, my C coding skills aren't great but I have a B in English so I can help there :) Alex - Original Message - From: Pedro B. [EMAIL PROTECTED] To: Kannel Dev [EMAIL PROTECTED] Sent: Wednesday, August 11, 2004 12:34 AM Subject: Re: WARNING: SMPP: PDU element password to long (length is 9,shouldbe 9) Alex, I'm halfway looking (more like digging) through all the code to make a manual-spellcheck-patch. Maybe we can split the work, or maybe you review my patch when i have it done... can never spellcheck too much, i say :) What do you think? \\pb Alex Kinch wrote: - Original Message - now, Kannel was never been an US project. Finish people started it and several other european citizen have continued it. Speaking of personal implications: I'm a croatian citizen, born and living in Germany, working on a finish project ;) Finnish you mean ;) ducks I'm happy to have a look through the docs sometime and correct any spelling mistakes, do I just check the HTML or is there a better way of doing it? Alex
Re: WARNING: SMPP: PDU element password to long (length is 9, shouldbe 9)
Alex Kinch wrote:
- Original Message -
now, Kannel was never been an US project. Finish people started it and
several other european citizen have continued it. Speaking of personal
implications: I'm a croatian citizen, born and living in Germany,
working on a finish project ;)
Finnish you mean ;)
ok ok, got me again.
ducks
that was too fast for me ;)
I'm happy to have a look through the docs sometime and correct any spelling
mistakes, do I just check the HTML or is there a better way of doing it?
I did some aspell'ing on the userguide.xml and the .shtml files of the
kannel.org web site.
I guess we'd need some fixing in the .[ch] files comments.
Stipe
mailto:stolj_{at}_wapme.de
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf, NRW, Germany
phone: +49.211.74845.0
fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de
http://www.wapme-systems.de/
---
-BEGIN PGP PUBLIC KEY BLOCK-
Version: GnuPG v1.2.2 (Cygwin)
mIsEP6mcYwEEAMDnUiUwrbb+xwTFWN6TxF2+XZu7/alwJMeCwMBRvXtPZqfjpPhS
OkBpU0F4TrVuugz1HINTSaJTYq10AzDQXp5NkyWgckqW79nPAWuOX0dicbJk+cN2
nM2TI4KaxUDe6u8hghNEnH/i2lXsUu9apnP/iixzV81VC2je3uc9hZpnAAYptEVT
dGlwZSBUb2xqIChUZWNobm9sb2d5IENlbnRlciAmIFJlc2VhcmNoIExhYikgPHRv
bGpAd2FwbWUtc3lzdGVtcy5kZT6ItAQTAQIAHgUCP6mcYwIbAwYLCQgHAwIDFQID
AxYCAQIeAQIXgAAKCRABV0w1BqPYRuSqA/wPzsQxao2YePENCtgRTrO86U6zg3sl
OcS6CJFI4FZP5h/xD3GRsNH1+MPSvZlomDdpFnr547DGz/Kq9MXuQwVvlVig5yWZ
K5dtKp1r5YLhxJQBhfirZbRFFnYmf19f18J8OoS28tuFVftDl1AIwJS3HLyBTv6H
g2HyLAEKQIp30Q==
=aYCI
-END PGP PUBLIC KEY BLOCK-
Re: WARNING: SMPP: PDU element password to long (length is 9, shouldbe 9)
Yes, it's what i'm doing... *trying* to ignore the code and just take care of the more pure text. Although there are some problems with polling (as in database) appearing as pooling (as in i wish i had one) in approximately 200 places, including variable names and .c filenames i won't (can't) touch... with the heat wave we're having here, this is becoming tough, i keep getting distracted :) I'll send you a patch soon (probably tomorrow or so), you re-review it, then we present it for global appreciation. Is that ok? \\pb Alex Kinch wrote: Don't mind, my C coding skills aren't great but I have a B in English so I can help there :) Alex - Original Message - From: Pedro B. [EMAIL PROTECTED] To: Kannel Dev [EMAIL PROTECTED] Sent: Wednesday, August 11, 2004 12:34 AM Subject: Re: WARNING: SMPP: PDU element password to long (length is 9,shouldbe 9) Alex, I'm halfway looking (more like digging) through all the code to make a manual-spellcheck-patch. Maybe we can split the work, or maybe you review my patch when i have it done... can never spellcheck too much, i say :) What do you think? \\pb Alex Kinch wrote: - Original Message - now, Kannel was never been an US project. Finish people started it and several other european citizen have continued it. Speaking of personal implications: I'm a croatian citizen, born and living in Germany, working on a finish project ;) Finnish you mean ;) ducks I'm happy to have a look through the docs sometime and correct any spelling mistakes, do I just check the HTML or is there a better way of doing it? Alex
Re: Help: Kannel users from the Philippines
On Tue, Aug 10, 2004 at 02:47:13PM +, Josephine Forte wrote: Hi, Anybody here who's a kannel user from the phillipines? We are using kannel cvs20040621 version on Red Hat Linux 7.3. I used CIMD2 protocol to connect to SMART Telecom. I just need some help because we already set up kannel, MO and MT are ok, so is sendsms(PUSH) but I'm having problems with kannel receiving and sending out messages too slow. about 3-5 sms/sec. I already turned off delivery report request, but still, message sending/receiving rate is too slow and queue is getting bigger and bigger. Any advice? We're also connected to Smart, and don't seem to experience the kind of slowness you observe. Our service peaked at some 200 messages per second once, without breaking a sweat. Our SMSC config looks something like this: group = smsc smsc = cimd2 smsc-id = smart-outgoing host = x.x.x.x port = keepalive = 60e smsc-username = x smsc-password = * sender-prefix = group = smsc smsc = cimd2 smsc-id = smart-incoming host = x.x.x.x port = keepalive = 60 smsc-username = xxx smsc-password = * sender-prefix = Don't see much difference between your config and mine. Perhaps your bandwidth to Smart is not all it could be, or you have a firewall that's rate limiting your connection? Apparently, a misconfigured Cisco firewall once totally blocked the SMSC connection of one of our client's servers, perhaps the same thing could be happening to you. 3-5 messages per second translates to roughly 16 kbps of bandwidth given the overhead involved with the CIMD2 protocol, so if you have dangerously close to that amount you can't really expect better performance than that. Try talking to the MVAS department; they should be able to tell you what they see from their side of the connection. -- dido Sans les mathematiques on ne penetre point au fond de la philosophie. Sans la philosophie on ne penetre point au fond des mathematiques. Sans les deux on ne penetre au fond de rien.
