Hi
I'm trying test my system by using smsbox to send messages.
lynx -dump
"http://localhost:13131/cgi-bin/sendsms?username=ma&password=ma2&to=31621290&text=Hello+world";
I looks like my outbound SMPP works (I can also verify this at the other SMMP
box where the con
Check your bearerbox logs. Your SMSc might have problems.
BR,
Nikos
- Original Message -
From: Peter Mohr
To: users@kannel.org
Sent: Wednesday, September 15, 2010 12:18 PM
Subject: Delayed reply - wait for bearerbox
Hi
I’m trying test my system by using smsbox to send messages.
Hi,
This is a known kannel limitation. In a multpart SMS it will request DLR
only for the first part. Nothing you can do about it.
BR,
Nikos
- Original Message -
From: "Ivan Kurnosov"
To:
Sent: Wednesday, September 15, 2010 8:28 AM
Subject: registered_delivery and multi-parts messa
Seems quite ok???
Bearerbox.log:
2010-09-15 13:13:32 [7669] [0] INFO: Added logfile
`/var/log/kannel/bearerbox.log' with level `1'.
2010-09-15 13:13:32 [7669] [0] INFO: Started access logfile
`/var/log/kannel/access-bearer.log'.
2010-09-15 13:13:32 [7669] [0] INFO: SSL not supported, no SSL init
Actually, I can ;-) I already fixed kannel (to be clear - i've just
commented 3 lines of code) to send only one DLR msg. So now I get N
delivery messages.
But I'm very curious - is it just kannel "feature" or some smpp
specification mandatory? I've asked this question because one of my
SMSC (curre
Hi,
The mobile must have an embeeded modem and respond to AT commands. This is
most probable if it has a serial or usb cable. There is a special section in
the UG about modem initialization, which you might helpful.
BR,
Nikos
- Original Message -
From: "Rui Ruas" <000...@apvm.net>
T
Hi,
This is because 500 errors are specific to each manufacturer and mobile.
Different solutions apply to each case. You should contact your mobile
manufacturer about it.
Some useful diagnostic AT commands are:
+CMGL (List SMS in SIM)
+CMGD (Delete SMS from SIM)
BR,
Nikos
- Original Mes
That's a kannel, not a spec limitation. And these 3 lines of code you
changed propably have broken your kannel.
BR,
Nikos
- Original Message -
From: "Ivan Kurnosov"
To: "Nikos Balkanas" ;
Sent: Wednesday, September 15, 2010 2:24 PM
Subject: Re: registered_delivery and multi-parts mes
How they can broke it? It is just removing registered_delivery from
other messages than 1st
2010/9/15 Nikos Balkanas :
> That's a kannel, not a spec limitation. And these 3 lines of code you
> changed propably have broken your kannel.
>
> BR,
> Nikos
> - Original Message - From: "Ivan Kurn
hello friends,
i had installed playsms-0.9.4, configured playsms as it has been directed in
INSTALL file.
now i want to become reseller of bulksms. suppose i buy 10, sms at 1 cent
and resell it to client at 4 cent per sms to clients, how to do that through
playsms.guys ill be really thankfu
True, it's a Kannel thing, not an smpp spec issue.
What you did probably won't break Kannel... but... you might get some log
messages where Kannel complains about not being able to find DLR or not
interested in it.
== Rene
-Original Message-
From: users-boun...@kannel.org [mailto:users-bo
You've set "immediate-sendsms-reply = false". That causes Kannel to wait for
the smsc to respond before giving control back.
I'd advise you to comment that line, it'll seriously hurt your MT queueing
performance (since your web interface won't return immediately).
Apart from that, check the logs
Why don't Kannel send DLR request for each part? Each part has its own
message_id and can be unique identified.
> On Wed, Sep 15, 2010 at 11:35 PM, Rene Kluwen wrote:
>> True, it's a Kannel thing, not an smpp spec issue.
>> What you did probably won't break Kannel... but... you might get some log
HI,
This is simple way how to install smppbox with kannel
run these commands
create a directory *gateway* under path /usr/local then run command
*svn co https://svn.kannel.org/gateway/trunk*
Create a directory *smppbox* under path /usr/local/gateway then run command
*svn co https://svn.kannel.o
Because Kannel sends the complete sms message through to smsbox. So it only
needs 1 DLR.
== Rene
-Original Message-
From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf
Of Ivan Kurnosov
Sent: Wednesday, 15 September, 2010 14:43
To: users@kannel.org
Subject: Re: regis
Yes. I wouldn't call it a bug, it was a design decision. Of course you're
absolutely entitled to disagree with it and change it on your local tree, as
you already did :)
Now, the issue is, since you define one dlr-url (probably with a unique id
you created) and Kannel splits the message into 2 or
subscribe int playsms list. This is a kannel list.
|-|
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.
Post your kannel related questions in kannel list and you will receive
--hopefully ;D -- support from many people
|-|
Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualqu
What is your smsc log? Did you see a submit or response pdu? Else does
you message is shown in kannels queue? check the admin interface.
You can add a log-file for your smsc so you can have its log separated
from the rest.
|-
Changed the SMSC section:
group = smsc
smsc = smpp
host = 10.2.1.2
port = 9000
receive-port = 0
smsc-username = "kannel"
smsc-password = "kannel"
system-type = "VMA"
log-file = "/var/log/kannel/smsc.log"
log-level = 1
restarted and retired... A 0-byte file called smsc.log is created but nothing
g
Put log-level 0.
Oh, and add an smsc-id.
On Wed, Sep 15, 2010 at 4:47 PM, Peter Mohr wrote:
> Changed the SMSC section:
> group = smsc
> smsc = smpp
> host = 10.2.1.2
> port = 9000
> receive-port = 0
> smsc-username = "kannel"
> smsc-password = "kannel"
> system-type = "VMA"
> log-file = "/var/l
Actually, it won't complain. Each received submit_sm_resp will generate a
separate dlr_entry, one for each part. When the respective DLRs arrive they
will be correctly matched and call a different dlr_url in smsbox one for
each part, as correctly pointed out by Alex.
smpp->sent_msgs is matched
Well it is actually a bug, but i am not sure how often it happens. The
correct behaviour would be for smsbox to know the parts of the original sms
and call the OK dlr-url only when all parts to the original SMS are
delivered OK. Imagine 2 parts of a 3-part sms are delivered and something
happen
It says "no boxes connected"... you should start smsbox
add smsc-is="my-smsc" to the smsc group and
Also add &smsc=my-smsc (urlencoded) to the link you are calling.
Check userguide for details.
Post logs if still with problems.
Regards
Alvaro
|---
Ok ok.. I get it... (sort of)
Bearerbox.log
2010-09-15 18:02:07 [9182] [0] INFO: Added logfile
`/var/log/kannel/bearerbox.log' with level `0'.
2010-09-15 18:02:07 [9182] [0] INFO: Started access logfile
`/var/log/kannel/access-bearer.log'.
2010-09-15 18:02:07 [9182] [0] INFO: SSL not supported,
Hmmm lloks like smsbox is dying after some time...
if you do a ps -ef | grep box, what do you get after verifying that
the admin shows no connected box?
If you do call your link, what do you get in smsbox log? it should
show your connection;
Have you another kannel instance running elsewhere?
|
I don't think this is the case:
p...@ubunto01:/var/log/kannel$ ps -ef | grep box
root 9215 7229 0 18:14 pts/000:00:00 bearerbox
/etc/kannel/kannel.conf
root 9232 9100 0 18:14 pts/200:00:00 smsbox kannel.conf
pm9243 7558 0 18:16 pts/100:00:00 grep --color=auto b
You're wrong. When you queue the message, you specify the dlr-url to use.
If kannel splits the message into 3 segments, and you modify kannel to ask
for DLR's on the 3 of them, you'll get the same dlr-url called 3 times.
If you set dlr-url=http://my.host.com/dlr.php?id=1234, it will be called 3
T
As far as I recall, the timestamp field in the DLR table is set to the
submit_resp message id.
But it has been a while since I've looked at the code. So I may be wrong.
Conclusion: It will only find one DLR entry and the other ones won't be
found.
== Rene
From: Alejandro Guerrieri [mailto
Hello everyone!!
Am relatively new to kannel but it's been an interesting ride so far.
I have a question though and hope someone out there will help me out.
I have 4 short codes that am running now the problem is that when I
send a request using one of the short codes, the response sometimes is
r
Actually you just misread my mail. As mentioned, we are in complete agreement.
I didn't mean different dlr-url locations, but 3 different dlr-url attempts,
one for each part. Don't jump the gun over nothing.
BR,
Nikos
- Original Message -
From: Alejandro Guerrieri
To: Nikos Balka
You don't remember well. The submit_sm_resp contains the SMSc messageid, aka
forreign ID, different one for each submit_sm_resp for each part. Therefore
there would be a different dlr_entry for each part.
BR,
Nikos
- Original Message -
From: Rene Kluwen
To: 'Alejandro Guerrieri' ; 'Ni
I've replied to the same one, where you referred to the dlr-url being called
3 times with different information and pointed that wasn't the case.
Now, regarding your second email, yes, something similar to what happens
with MO re-assembly would work wonders. An internal list with pending parts
is
I've replied to the same one, where you referred to the dlr-url being
called 3 times with different information and pointed that wasn't the case.
No, I repeat. I never said anything about calling dlr-url with different
information. Stop slandering my mails.
Nikos
- Original Message -
Could you post your config?
-Original Message-
From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf
Of mwamba chishimba
Sent: Wednesday, 15 September, 2010 18:34
To: users@kannel.org
Subject: Running Short Codes on Kannel
Hello everyone!!
Am relatively new to kannel
Actually I am pretty sure now that I am right and you are wrong.
Look here at some code from smsc_smpp.c:
Octstr *tmp;
/* check if msg_id is C string, decimal or hex for this SMSC
*/
if (smpp->smpp_msg_id_type == -1) {
/* the def
Okay, I just proved myself wrong as well.
Looking more closely in dlr.c, it seems that "ts" is replaced with the
original foreign id from the first message:
if (msg->sms.foreign_id != NULL)
octstr_destroy(msg->sms.foreign_id);
msg->sms.foreign_id = octstr_duplicate(ts);
if (msg
Hello,
Please copy the Kannel users list on consecutive messages. You might get
more and better response.
But if you do, mask sensitive data such as passwords.
If you want an sms-service to respond to just a particular shortcode, use
allowed-prefix in group = sms-service.
See:
http://www.kannel.
Thank you Rene, I will give you feedback let me just make the changes.
Kind Regards,
On 9/15/10, Rene Kluwen wrote:
> Hello,
>
> Please copy the Kannel users list on consecutive messages. You might get
> more and better response.
> But if you do, mask sensitive data such as passwords.
>
> If you
Very strange... seems smsbox is not connecting to bearerbox or is
connecting to _another_bearerbox_
can you try with this config and let us know.
Stop kannel (bearebox AND smsbox)
check no other kannel instance is running (ps -ef |grep box)
delete/rename log files
pray ;D
start kannel (bearebox T
It sends N sms parts through smsbox and there is no guarantee that all
of them will be delivered succesfully
On Thu, Sep 16, 2010 at 12:22 AM, Rene Kluwen wrote:
> Because Kannel sends the complete sms message through to smsbox. So it only
> needs 1 DLR.
>
> == Rene
>
> -Original Message-
Not the same id. Each part has its own SMSC message_id
On Thu, Sep 16, 2010 at 12:36 AM, Alejandro Guerrieri
wrote:
> Yes. I wouldn't call it a bug, it was a design decision. Of course you're
> absolutely entitled to disagree with it and change it on your local tree, as
> you already did :)
> Now
It only sends 1 (large) part through smsbox. Sms message is splitted in
bearerbox.
-Original Message-
From: zerk...@googlemail.com [mailto:zerk...@googlemail.com] On Behalf Of
Ivan Kurnosov
Sent: Wednesday, 15 September, 2010 23:57
To: Rene Kluwen; users@kannel.org
Subject: Re: registered
You guys are talking about different id's.
Smsc id (foreign id) is not the same id as you assign in dlr-url.
== Rene
-Original Message-
From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf
Of Ivan Kurnosov
Sent: Wednesday, 15 September, 2010 23:58
To: Alejandro Guer
H I'm talking about %F which is foreign id and as I said -
when it is multipart short message - I get it == 0 at my dlr-url
On Thu, Sep 16, 2010 at 10:43 AM, Rene Kluwen wrote:
> You guys are talking about different id's.
>
> Smsc id (foreign id) is not the same id as you assign in dlr-ur
Ivan, %F comes loaded with the information from the smsc. While it should be
unique, you don't know it in advance, so it can't be used to match back to
anything on your side. For the dlrs to be useful, you should be able to match
it against something known on your side, and that's where the id I
Hmhmhmh, may be I'm understanding wrong, but my task now is:
To be sure that ALL PARTS of multipart message has been delivered. Is
there any possible way of doing this?
Another point of view of this issue: If I get only the one dlr message
(for first msg, as kannel does) - can I be sure that all
On Mon, Sep 13, 2010 at 5:09 PM, Harbhag Singh Sohal
wrote:
> On Mon, Sep 13, 2010 at 4:53 PM, Rene Kluwen wrote:
>> See userguide about directive "access-log" in group = core.
I did as you said and now in access-log I can see the messages sent.
But I dont anything getting stored in the MySQL dat
Let's see:
Kannel currently functionality works as follows:
When a message longer than 160 chars is queued, Kannel splits it into 2 or
more messages. Only on the first one the registered_delivery flag is set.
That means that Kannel asks for DLR's only on the first part.
You could change Kannel t
>> The way dlr-url works would mean that the same dlr-url would be accessed 2
>> or more times, using the same user values you provided on all of them.
Actually - no. With %F it is the different urls
I'm feeling dummy but what is "MO"? Is it the way of manual splitting
the messages into parts wit
50 matches
Mail list logo
