Hi Users,
I have installed and configured SQLBOX with mysql support.
When I insert a record in send_sms table, message received successfully but
the log shows the empty *message_id* that causing the DLR receipt failure.
Also unable to retrieve all columns for dlr_rpt table for the given dlr-url
transceiver-mode = 1
Message id from smsc2 is saved correctly message_id=ts:
2011-05-13 20:29:33 [19825] [8] DEBUG: SMPP[smsc2]: Got PDU:
2011-05-13 20:29:33 [19825] [8] DEBUG: SMPP PDU 0x1c00b730 dump:
2011-05-13 20:29:33 [19825] [8] DEBUG: type_name: submit_sm_resp
2011-05-13 20:29:33 [19825] [8] DEBUG
host = X.X.X.X
log-file = /var/log/kannel/smsc2-1.log
log-level = 0
max-pending-submits = 10
msg-id-type = 0x00
port =
smsc-id = smsc2
smsc-password =
smsc-username =
system-type =
transceiver-mode = 1
Message id from smsc2 is saved correctly message_id=ts:
2011-05-13
-pending-submits = 10
msg-id-type = 0x00
port =
smsc-id = smsc2
smsc-password =
smsc-username =
system-type =
transceiver-mode = 1
Message id from smsc2 is saved correctly message_id=ts:
2011-05-13 20:29:33 [19825] [8] DEBUG: SMPP[smsc2]: Got PDU:
2011-05-13 20:29:33
Hi
I was checking in the SMPP 3.4 spec and came across the submit_sm_resp PDU
which specifies a message_id field. According to the spec:
This field contains the SMSC
message ID of the submitted
message. It may be used at a
later stage to query the status
of a message, cancel or
replace
Yes, that's the expected behavior.
Regards,
Alex
On Tue, Jun 29, 2010 at 1:21 PM, brett skinner tatty.dishcl...@gmail.comwrote:
Hi
I was checking in the SMPP 3.4 spec and came across the submit_sm_resp PDU
which specifies a message_id field. According to the spec:
This field contains
the message_id from a submit_sm_resp into
timestamp for a DLR using SMPP 3.4
Hi
I was checking in the SMPP 3.4 spec and came across the submit_sm_resp PDU
which specifies a message_id field. According to the spec:
This field contains the SMSC
message ID of the submitted
message. It may be used
the URL how this entry got to db.
Anyways what i am looking at is to get message_id from kannel as soon
as any sms is sent for particular sms store that sms id the
message_id from kannel in some separate table or just in sent_sms
table in say new field called message_id so that the next time i have
message_id from kannel as soon
as any sms is sent for particular sms store that sms id the
message_id from kannel in some separate table or just in sent_sms
table in say new field called message_id so that the next time i have
some DLR with that particular message id i can associate it.
I saw
as something like this id:1024541450 sub:001 dlvrd:001 submit
date:1001041916 done date:1001041916 stat:DELIVRD err:000 text:
I wonder instead of invoking the URL how this entry got to db.
Anyways what i am looking at is to get message_id from kannel as soon
as any sms is sent for particular sms
Hi,
Is the patch that get the message_id from
submit_sm_responsehttp://www.blogalex.com/archives/10by Alejandro
included in the Last stable release.
Thanks Alejandro for your effort.
Regards,
--
Hafez A.Ahmad
On Fri, Oct 31, 2008 at 1:18 PM, Kyriacos Sakkas
[EMAIL PROTECTED] wrote:
Is there some conf parameter that will switch the Id in one of the two
places to match the other?
Check the msg-id-type parameter
BR, Jovan
Hi,
I have a problem getting DLRs correctly from one operator. When I submit
a message the message Id is passed back in the submit_sm_resp as a HEX
number.
Now when DLRs come latter the ID is passed as part of the short_message,
but as a Decimal.
This causes kannel to ignore the DLR, as it can
Kyriacos Sakkas schrieb:
Thanks,
Sorted now, got my bits confused for a bit their.
Hi,
it's simple: we need to tell Kannel via the 'msg-id-type' how the SMPP based
SMSC handles the msg IDs.
In normal cases, where no 'msg-id-type' is set, we use the SAME semantics on the
[EMAIL PROTECTED]
Sent: September 19, 2008 6:42 AM
To: [EMAIL PROTECTED] [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED] [EMAIL PROTECTED]
Subject: Re: [PATCH] message_id from submit_sm_response on DLR's
Kannel uses the message_id internally to track DLR's (otherwise it would
be impossible to hit
PROTECTED]mailto:[EMAIL PROTECTED]
Subject: Re: [PATCH] message_id from submit_sm_response on DLR's
Kannel uses the message_id internally to track DLR's (otherwise it would be
impossible to hit the same record twice).
The message_id translates to the ts field on the DLR table, my patch only
makes
);*
Replace this line with
*char id[UUID_STR_LEN + 1];
uuid_unparse(msg-sms.id, id);
answer = octstr_create(id);
*Then recompile again.*
*
Regards,
Remon
Luis Valencia wrote:
Hi all,
I want to capture the message_id of every sms sent by kannel, I
already set up the debug level to 0 on my
Hi all,
I want to capture the message_id of every sms sent by kannel, I already set
up the debug level to 0 on my bearerbox.conf but this log is growing huge
very fast.
There is another way to do this, or anyone has a better idea to do it. Im
even starting to think on modify the source
well this is the way man
all the MO/MT/DLR traffic first goes to the db :)
the smsId is he unique/primary key you could use to fetch the needed
additional info
cheers
-Original Message-
From: Peter Lum [EMAIL PROTECTED]
Sent: 20 Август 2007 г.
To: seik
Subject:getting message_id from
man,
do you urlencode the dlr-url value ?
:)
cheers
-Original Message-
From: Peter Lum [EMAIL PROTECTED]
Sent: 20 Август 2007 г.
To: seik
Subject:getting message_id from submit_sm_resp
Hi Seik
Ok, I think I get what you mean... By setting the dlr-url during the SENDING
part
.
Regards
Ben
On 26 Jul 2007, at 23:00, Ravi Bhalotia wrote:
Thanks Seik. However, in my case the kannel ID is important, it is
getting assigned a value of message_id that is being passed by the
smsc we are using. So, in case of issues or messages getting
rejected we need to store that ID
Thanks a lot Ben, Seik and Fajar. All your pointers and advice are very
helpful and I am able to get it to work now. I am getting the message_id
from kannel now and storing in our database for lookup purpose with our
SMSC later.
Thanks again for the help, I recompiled kannel and installed
-
From: Ravi Bhalotia [mailto:[EMAIL PROTECTED]
Sent: Friday, July 27, 2007 11:30 PM
To: Ben Suffolk
Cc: users@kannel.org
Subject: Re: getting message_id from submit_sm_resp
Thanks a lot Ben, Seik and Fajar. All your pointers and advice are very
helpful and I am able to get it to work now. I am
The rejected message do not contain the PDU message_id in the answer text
the text of the message is like this one:
NACK/62/Unknown/Reserved
its highly dependable on the SMSC config
so one can not get the smsc_id in case of failure/reject by smsc.
so all you can get from the NACK DLR
to insert the unique ID as well
after processing the MT messages.
cheers
-Original Message-
From: Peter Lum [EMAIL PROTECTED]
Sent: 28 Юли 2007 г.
To: seik
Subject:getting message_id from submit_sm_resp
Hi Ravi
I am also trying to do the same thing but I am a bit confused
PROTECTED]
Sent: Saturday, July 28, 2007 1:17 PM
To: Peter Lum
Cc: users@kannel.org
Subject: Re[2]: getting message_id from submit_sm_resp
check the mails, especially this one:
http://www.kannel.org/pipermail/users/2006-October/000859.html
paste here the http request you use
according the docs
request
that kannel makes ...
this happens, because kannel writes down the dlr-url value in the dlr queue in
case the dlr-mask is more that 0
:)
cheers
-Original Message-
From: Peter Lum [EMAIL PROTECTED]
Sent: 28 Юли 2007 г.
To: seik
Subject:getting message_id from submit_sm_resp
hi All - I am trying to get message_id from submit_sm_resp message and
pass it to the application we are running through a dlr url. Passing a
dlr-mask of 31 and a dlr-url but the message_id parameter seems to be
omitted from the dlr-url. The dlr url is getting called but without the
value
Hi Ravi,
i have no problems here to get the kannel message_id value
i just tested that in working environment
release info:
Kannel bearerbox version `cvs-20070424'.
Build `Apr 26 2007 02:19:45', compiler `3.3.6'.
System Linux, release 2.6.20ipsec-smp, version #2 SMP Fri Apr 20 22:55:23 EEST
Thanks Seik. However, in my case the kannel ID is important, it is
getting assigned a value of message_id that is being passed by the smsc
we are using. So, in case of issues or messages getting rejected we need
to store that ID in our database to look up in our SMSC's system. What I
want
it from the kannel dlr GET request
use your unique smsid value, its just enough :)
cheers
-Original Message-
From: Ravi Bhalotia [EMAIL PROTECTED]
Sent: 26 ??? 2007 ?.
To: seik
Subject:getting message_id from submit_sm_resp
hi All - I am trying to get message_id from submit_sm_resp
As I understand things the SMSC is in charge of creating message_ids
for each SMS. Should there ever be a case where two consecutive SMS
messages are assigned the same message_id? I ask because this is what
I see from a recent test while sending a ringtone that was chopped into
two SMS
**To: users@kannel.org
**From: Matthew Hixson [EMAIL PROTECTED]
**Subject: message_id uniqueness?
**Date: Tue, 15 Feb 2005 11:41:52 -0800
**
**As I understand things the SMSC is in charge of creating message_ids
**for each SMS. Should there ever be a case where two consecutive SMS
**messages
I just sent a ringtone through Kannel 1.4.0 and I see this in
bearerbox.log. Just wondering why the message_id C8BCDBA shows up
twice. I notice that the time on the log for both lines where the
message_id appears is exactly the same, 09:44:33.
I just sent the exact same SMS to the same
34 matches
Mail list logo