Hi Kyriacos
The MySQL field type was varchar(100) so that wasn't the problem. In the
end we fixed it by asking Nexmo/Vonage to change the message ID types to
match (hex) and then removed msg-id-type so the conversion was no longer
needed.
Thanks
Alex
On Mon, 7 Aug 2023 at 01:04, Kyriacos/Netsmar
And your mysql table create statement. It might be that you are using a
filed type that can not hold such large numbers. Can easily be converted
to a char based storage if you don't have extreme space limit issues on
the DB side.
On 06/08/2023 6:16 pm, Mesbahuddin Malik wrote:
Send your Smpp
Send your Smpp Config.
On Sun, Aug 6, 2023 at 8:26 PM Alex Kinch wrote:
> Hi all,
>
> I've run into an issue with a certain SMS provider (Nexmo/Vonage) that is
> using message IDs greater than 9223372036854775807 (e.g.
> 6142530091694509440651642911224527237), which is in turn breaking DLR
> pro
Hi all,
I've run into an issue with a certain SMS provider (Nexmo/Vonage) that is
using message IDs greater than 9223372036854775807 (e.g.
6142530091694509440651642911224527237), which is in turn breaking DLR
processing in Kannel.
They use hex in submit_sm_resp and decimal in deliver_sm so I have
Dear Gabriel,
The actual DLRs are 1, 2 and 4 and been returned from SMSCs (deliver_sm
packet) .The 8 is SMSC acceptance receipt and 16 is SMSC reject receipt but
kannels will send you if you set correct dlr-mask. with dlr=0 you asked
kannel not send you any.
I think if you set 1,2,3 bits in DLR
hot/userguide.html#delivery-reports
>
>
> You need dlr mask 8 and 16 set -> 24
>
> Regards,
> Alexander Malysh
> Am 25. Aug. 2021, 03:32 +0200 schrieb Gabriel Augusto Diaz Zapata <
> gabriel.d...@gmail.com>:
>
> Hello People
>
> I'm having an issue wi
People
>
> I'm having an issue with submt_sm_response failed and DLRS
>
> If I set DLR =0 sending and MT, and the submit_sm is rejected by SMSC, I
> don't receive the NACK in kannel Table. I checked the logs and the error was
> logged and detected, but I don't have
Hello People
I'm having an issue with submt_sm_response failed and DLRS
If I set DLR =0 sending and MT, and the submit_sm is rejected by SMSC, I
don't receive the NACK in kannel Table. I checked the logs and the error
was logged and detected, but I don't have the NACK (like
l as existing attached files, may be confidential and
> privileged. Use or disclosure by anyone other than an intended recipient is
> not authorised.
> If you have received this message by error, you are kindly requested to
> delete it and notify the sender. Thank you for your cooperat
hank you for your cooperation.*
>
> --
> *From:* Alexander Malysh on behalf of Alexander
> Malysh
> *Sent:* 22 May 2020 15:38
> *To:* Paulo Correia
> *Cc:* users@kannel.org
> *Subject:* Re: Unable to deliver DLRs: "Couldn't fetch..."
>
__
From: Alexander Malysh on behalf of Alexander Malysh
Sent: 22 May 2020 15:38
To: Paulo Correia
Cc: users@kannel.org
Subject: Re: Unable to deliver DLRs: "Couldn't fetch..."
Hi,
do you have any errors except couldn’t fetch? mostly it’s because either kannel
ran
:35 schrieb Paulo Correia :
>
> Hi fellow kannel users,
>
> We've been using kannel for quite some years and on the latest months we've
> seen an issue when processing DLRs on high traffic.
>
> We send the messages to kannel using HTTP with the /cgi-bin/sendsms adding
Hi fellow kannel users,
We've been using kannel for quite some years and on the latest months we've
seen an issue when processing DLRs on high traffic.
We send the messages to kannel using HTTP with the /cgi-bin/sendsms adding the
dlr-url and dlr-mask values as always have been sen
Dear Antony,
May be this helps.
The Kannel DLR mechanism works as follows:
1. Kannel sends your message in submit_sm packet to smsc.
2. SMSC replies with submit_sm_resp, witch have a *ID* in it.
3. if SMSC accepts the message, there will be an *ID *and kannel sends
status=8 , kannel
x
reply to the SMSC.
Davor
-Original Message-
From: users On Behalf Of Antony Stone
Sent: Saturday, August 17, 2019 3:54 PM
To: users@kannel.org
Subject: Re: DLRs
On Saturday 17 August 2019 at 15:48:19, Antony Stone wrote:
> Indeed - if I turn off one of my kannel instances, so th
Replying to myself in case it helps others looking for this information in
future.
On Saturday 17 August 2019 at 15:42:38, Antony Stone wrote:
> It looks like I'm going to have to look into using a database for my DLR
> storage. I do happen to have a MariaDB Galera cluster available, but I've
>
On Saturday 17 August 2019 at 15:48:19, Antony Stone wrote:
> Indeed - if I turn off one of my kannel instances, so there is only one
> running to either send or receive message to/from my SMSC provider, I get
> DLR status=8 when the message is sent (with the phone turned off), and I
> then get DL
6176.html
> which addresses this, and it looks like suggestion 1 is my problem. I do
> have two machines running kannel, each with a connection to my upstream
> carrier (for load balancing / high availability), and I have no control
> over which connection that carrier will use to send m
on 1 is my problem. I do have two
machines running kannel, each with a connection to my upstream carrier (for
load balancing / high availability), and I have no control over which
connection that carrier will use to send me messages or DLRs.
It looks like I'm going to have to look into usin
t; have set, whatever comes first.
>
> Davor
>
>> On Aug 17, 2019, at 1:45 PM, Antony Stone
>> wrote:
>>
>> Hi.
>>
>> I'm now wondering whether I've misunderstood how DLRs actually work.
>>
>> I just tried the following:
>>
>&g
> On Aug 17, 2019, at 1:45 PM, Antony Stone
> wrote:
>
> Hi.
>
> I'm now wondering whether I've misunderstood how DLRs actually work.
>
> I just tried the following:
>
> 1. Make sure my mobile phone is turned on and has good signal.
>
> 2. Send
Hi.
I'm now wondering whether I've misunderstood how DLRs actually work.
I just tried the following:
1. Make sure my mobile phone is turned on and has good signal.
2. Send a message via kannel to my mobile phone, with dlr_mask=31, indicating
that I want to get all status reports po
wrote:
>
>> I have kannel v1.4.4 running properly am able to sending messages and
>> receive dlrs as per access log.
>>
>> but I cant see it getting saved to msql as table dlr in temp_dlr is
>> empty. I have checked bearerbox.log and am getting below action that d
SMSC, I'm updating my queue table and Kannel delete the record from the dlr
On Tue, Dec 11, 2018 at 6:07 PM christopher kamutumwa <
chriskamutu...@gmail.com> wrote:
> I have kannel v1.4.4 running properly am able to sending messages and
> receive dlrs as per access log.
>
I have kannel v1.4.4 running properly am able to sending messages and
receive dlrs as per access log.
but I cant see it getting saved to msql as table dlr in temp_dlr is empty.
I have checked bearerbox.log and am getting below action that dlr is
getting deleted. How do I resolve this
a big difference.
== Rene
Van: users [mailto:users-boun...@kannel.org] Namens Nanda Kumar P
Verzonden: zondag 24 april 2016 7:11
Aan: users@kannel.org
Onderwerp: Create SMS box for handling dlrs
Hi,
I'm using one instance of bearer box and sms box each and I use kannel to
send sms to the
s@kannel.org<mailto:users@kannel.org>
Subject: Re: Create SMS box for handling dlrs
Hi Alvaro,
Thanks for the information. I'm currently interested in delivered and
undelivered messages only. Hence my dlr-mask is 3. Please suggest what I need
to do in order to get the expected throughput?
there is no predictability in
how long it will take to send all my messages. Is there anything in the data
structure used for the dlr registration at the bearer box that causes the
sluggishness when more and more dlrs are getting registered ?
Thanks,Nanda
Original message
From: A
refore you should carefully select which dlrs you are interested in.
Hope helps,
Alvaro
|-|
Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier
celular y Nextel
en el Pe
'
Subject: Create SMS box for handling dlrs
Hi,
I'm using one instance of bearer box and sms box each and I use kannel to send
sms to the SMSC with delivery report parameters (dlr-mask & dlr-url) included
in the send-sms url. I have no trouble functionality wise in sending the sms o
Hi,
I'm using one instance of bearer box and sms box each and I use kannel to send
sms to the SMSC with delivery report parameters (dlr-mask & dlr-url) included
in the send-sms url. I have no trouble functionality wise in sending the sms or
getting the delivery. However, I do have a problem in
Check if routing delay is from telecom side (SMSC often sends DLR pretty
late). It should be visible in bearerbox logs. Logically, bbox should not
be delaying DLRs.
On Wed, Oct 21, 2015 at 8:51 AM, Amelye Chatila wrote:
> I experience a delay in DLRs routing. I have couple of smsboxes
I experience a delay in DLRs routing. I have couple of smsboxes and couple
of SMSC connections. What is causing this? What adjustments can I make?
Thanks in advance!
ot;
> Копия: "users"
> Отправленные: Пятница, 27 Февраль 2015 г 9:15:32
> Тема: Re: Issue with Sending DLRs back to the SMPP Client
>
> I was trying the latest 1.4.4 version, and then latest build of 1.5.0
> version.
>
> The result was the same.
>
> In my openbo
04/03 06:45 PM, Cliff Court wrote:
I have an issue with getting DLRs working.
The kannel instance is up and sending SMS messages with dlr-storage
set to internal. In the smsc.log, I see the submit_sm, the
submit_sm_resp and the deliver_sm receipt. The message IDs in the
submit_sm_resp an
I have an issue with getting DLRs working.
The kannel instance is up and sending SMS messages with dlr-storage set
to internal. In the smsc.log, I see the submit_sm, the submit_sm_resp
and the deliver_sm receipt. The message IDs in the submit_sm_resp and
the deliver_sm are the same (and are
uot;Rene Kluwen"
Копия: "users"
Отправленные: Пятница, 27 Февраль 2015 г 9:15:32
Тема: Re: Issue with Sending DLRs back to the SMPP Client
I was trying the latest 1.4.4 version, and then latest build of 1.5.0 version.
The result was the same.
In my openboxsmpp.conf I don't have s
boxid = yes
--
With best Regards
Maxim Kovalenko
Software Engineer
tel/fax. :+34916426301
skype : c--mak
www.avystele.com
- Исходное сообщение -
От: "Rene Kluwen"
Кому: "Maksim Kovalenko" , "users"
Отправленные: Пятница, 27 Февраль 2015 г 0:57:09
Т
p-tlv that contains it, if you don't use it.
== Rene
-Original Message-
From: users [mailto:users-boun...@kannel.org] On Behalf Of Maksim Kovalenko
Sent: donderdag 26 februari 2015 12:43
To: users@kannel.org
Subject: Issue with Sending DLRs back to the SMPP Client
Hello!
I have an
Hello!
I have an issue with using Kannel along with opensmppbox.
The version I am using is 1.4.4.
Messages are being delivered but I experience troubles with delivering DLRs
back to the SMPP Client.
Routing is SMPP Client - opensmppbox - bearerbox - SMSC.
In the tcpdump I can see that from
On Tue, 2014-12-02 at 17:07, ha...@aeon.pk wrote:
> A good question! :-)
>
> I did use 63, as I am using it since quite some time (and it works).
> However on your alert, I checked the userguide to see that 63 should not be
> a combination at all. But I am pretty sure that I read it somewhere else
A good question! :-)
I did use 63, as I am using it since quite some time (and it works).
However on your alert, I checked the userguide to see that 63 should not be
a combination at all. But I am pretty sure that I read it somewhere else,
that's why I started using it. It would be something like
>with DLR mask 63
did you mean 31 ?
2014-12-01 23:34 GMT+03:00 ha...@aeon.pk :
> Resolved.
>
> In connection 'group = smsc', add line 'msg-id-type = 0x01' to fix the
> issue.
>
> On Tue, Dec 2, 2014 at 12:04 AM, ha...@aeon.pk wrote:
>
>> Hi,
>>
>> I have 2 SMSC connections. I am sending the sam
Resolved.
In connection 'group = smsc', add line 'msg-id-type = 0x01' to fix the
issue.
On Tue, Dec 2, 2014 at 12:04 AM, ha...@aeon.pk wrote:
> Hi,
>
> I have 2 SMSC connections. I am sending the same message with DLR mask 63
> (to get all possible delivery states). One SMSC connection is givin
Hi,
I have 2 SMSC connections. I am sending the same message with DLR mask 63
(to get all possible delivery states). One SMSC connection is giving me
submission-to-SMSC DLR and then DELIVERED DLR, both appearing in kannel
traffic logs. The other connection is only giving me submission-to-SMSC
DLR,
...@kannel.org] *On Behalf Of
*Kyriacos/Netsmart
*Sent:* maandag 6 oktober 2014 11:58
*To:* Vikas Wasiya
*Cc:* kannel users@kannel.org
*Subject:* Re: Can we pull DLRs instead of PUSH by kannel?
If the DB hit is the big issue and not the URL call, then simply have
that URL write the DLRs in some
If you use sqlbox, they will be inserted in the log table and you can select
them any time afterwards.
From: users [mailto:users-boun...@kannel.org] On Behalf Of Kyriacos/Netsmart
Sent: maandag 6 oktober 2014 11:58
To: Vikas Wasiya
Cc: kannel users@kannel.org
Subject: Re: Can we pull DLRs
If the DB hit is the big issue and not the URL call, then simply have
that URL write the DLRs in some serialized file that will allow easy
processing latter.
Still is probably more efficient overall to just push them to a DB table
without processing, and then pull them from that for
How big is your daily DLR volume? My suggestion is to tune up your DB, either
the engine (MyISAM to InnoDB maybe) or configuration.
Also I want to know how will you store the DLR? Parsing Kannel’s log? Save it
to plain text? When you do the bunch or batch will it still update the DB? Then
it wi
This is doable but you need to change the way the kannel handle the DLRs.
You need to modify the code to make kannel inserts the incoming DLRs into
another DLR table instead of matching and submitting.
Or if you are worried about your DB you can run a standalone MySQL server
for kannel only
Hello,
We have certain queries related to kannel dlr reports.
We do not want Kannel to call our URL and delete delivery reports from
Spool.
Instead, we want to pull the delivery report in bunch and delete.
Reason: reducing our DB load because every URL runs the update query on our
DB.
Thanks
scratcher integrating with an SMSC and I'm not
> sure which is the smoking gun. Sending and receiving messages works
> fine, but DLRs are not.
>
> Looking at the log I have a few theories, but I'm not sure which might be
> right:
>
> 1) My leading theory is that the se
Howdy,
Have a bit of a head scratcher integrating with an SMSC and I'm not
sure which is the smoking gun. Sending and receiving messages works
fine, but DLRs are not.
Looking at the log I have a few theories, but I'm not sure which might be right:
1) My leading theory is that the se
Hi,
Does anyone have any experience with DLRs running over loopbacks?
We're having difficulty sending back TLV based DLRs
We're taking SMPP traffic in to a sqlbox to store in a DB.
We then read the traffic from sqlbox, to a loopback, which then sends the
message to an opensm
2014-04-07 23:29 GMT+04:00 Douglas Calzzetta Filho :
> Hi Kannel users,
>
> I am developing a solution to manage massive SMS campaigns using Kannel.
> Performance is really important for me. For that I built many modules to
> send messages, to treat delivery status, etc.
> Kannel seems to work wel
Hi Kannel users,
I am developing a solution to manage massive SMS campaigns using Kannel.
Performance is really important for me. For that I built many modules to
send messages, to treat delivery status, etc.
Kannel seems to work well while receiving messages via smsbox and sending
via a SMPP SMSC
The docs for this say "Value 0 means giving strict priority to outgoing
> messages" What exactly does this mean? Could this affect incoming DLRs (or
> MOs for that matter) if we are doing a heavy volume of MTs?
>
> Thanks again!
>
> Jeff
>
>
> On Wed, Nov 27, 2013 a
Here is one other thought
we do have the following setting on the core group.
sms-incoming-queue-limit = 0
The docs for this say "Value 0 means giving strict priority to outgoing
messages" What exactly does this mean? Could this affect incoming DLRs (or
MOs for that matter) if we
s not interested in it" ERRORS but I don't think this is
related. I am getting < 20 of these errors for over 3,000,000 DLRs received
today. So I am not too concerned about these.
The errors I am talking about "Window on receiver full" are not occurring
in my logs. They are bein
I think he meant that he set receive-port = 0 on transmitters only and
he only expects DLRs to come through on receiver binds. For some
reason, he's getting DLRs on transmitter binds as well.
Are you able to post your PDU logs? Just the sections with DLRs.
On 27 November 2013 22:32, spa
Most likely that's because you set receiver-port = 0.
Check your smsc log as well and post here any errors you find.
2013/11/27 Jeff Thorn
> The SMSC Operator said they were getting "Window on receiver link full"
> errors from us when trying to send DLRs. Is that pos
The SMSC Operator said they were getting "Window on receiver link full"
errors from us when trying to send DLRs. Is that possible?
We are not using sqlbox and we do have the dlr table indexed. I will
confirm the version of kannel.
On Wed, Nov 27, 2013 at 1:52 PM, spameden wrote:
&g
2013/11/27 Jeff Thorn
> I see. So does that mean the the DLRs I am seeing on the transmit binds
> are only status 8s? Would the volume of 8 messages impact the sending of
> other status from the SMSC? I am trying to understand the cause of the
> error from the operator "Window
I see. So does that mean the the DLRs I am seeing on the transmit binds are
only status 8s? Would the volume of 8 messages impact the sending of other
status from the SMSC? I am trying to understand the cause of the error from
the operator "Window on receiver link full".
I appreciate
2013/11/27 Jeff Thorn
> The documentation says to set receive-port = 0 to disable I/O on this
> bind. I tested this on the one sample config I posted and it had no effect.
> Our other binds look like this and they too are receiving DLRs. What should
> be changed to make this a "
2013/11/27 Jeff Thorn
> Thanks for the response. In my scenario, we want to be able to send as
> fast as possible. We are regularly submitting MTs at a rate of 200 /
> second. We get DLRs at a rate of 1.5 - 2 times this (300 - 400 / second).
> This makes sense to me since we get m
The documentation says to set receive-port = 0 to disable I/O on this bind.
I tested this on the one sample config I posted and it had no effect. Our
other binds look like this and they too are receiving DLRs. What should be
changed to make this a "pure transmitter bind"? Will DLRs be r
possible. We are regularly submitting MTs at a rate of 200 /
> second. We get DLRs at a rate of 1.5 - 2 times this (300 - 400 / second).
> This makes sense to me since we get multiple DLRs for every MT (status
> 8,4,1). We do need the DLRs for reporting purposes. Our architecture was
> ju
Thanks for the response. In my scenario, we want to be able to send as fast
as possible. We are regularly submitting MTs at a rate of 200 / second. We
get DLRs at a rate of 1.5 - 2 times this (300 - 400 / second). This makes
sense to me since we get multiple DLRs for every MT (status 8,4,1). We
You can control DLR via dlr_mask parameter, if its unset you won't receive
any DLRs.
About speed - it's strange for me that speed of DLRs is much higher than MT
submit speed.
Don't think there is any algorhythm implemented to control inbound
information coming, you might turn i
It looks like setting receive-port=0 has no effect on DLRs. Is there any
way to control which binds receive DLRs or to somehow control how fast they
are received?
On Wed, Nov 27, 2013 at 10:15 AM, Jeff Thorn wrote:
> If we are getting DRs faster than we can process them, I assume if we
>
ov 26, 2013 at 5:36 PM, Jeff Thorn wrote:
> Hello Group,
> We are receiving DLRs from the SMSC faster than we can process them. Our
> setup is supposed to have 6 transmit binds and 4 receive binds. However, I
> just looked at status page showing all our binds and it looks like all 10
> of o
Hello Group,
We are receiving DLRs from the SMSC faster than we can process them. Our
setup is supposed to have 6 transmit binds and 4 receive binds. However, I
just looked at status page showing all our binds and it looks like all 10
of our binds are receiving DLRs and they are coming in at a
, México y en mas de 180 paises. Use aplicaciones 2 vias via
SMS y GPRS online
Visitenos en www.perusms.NET www.smsglobal.com.mx y
www.pravcom.com
On Sun, Sep 2, 2012 at 4:38 AM, Tomasz wrote:
> I've solved the problem myself.
>
> In at2_pdu_decode function those DL
I've solved the problem myself.
In at2_pdu_decode function those DLRs have type 1 ("AT_SUBMIT_SM")
instead of 2 ("AT_STATUS_REPORT_SM").
Probably operator make some modifications in DLR PDUs he sends.
After adding support for AT_SUBMIT_SM type there all DLRs are
Hi,
I'll offer 50 EUR for the first person who will help me modify kannel
sources to solve the described problem with DLRs.
Tomasz
W Twoim liście datowanym 30 sierpnia 2012 (12:36:59) można przeczytać:
> Hello,
> I'm using Kannel since few years as a core for gateway based on
Hello,
I'm using Kannel since few years as a core for gateway based on GSM
modems (AT). Since few days I've got a problem with DLRs. I'm
receiving only DLRs for some messages (before DLRs for all SMS were
delivered correctly). No configuration changes were made from that
time o
On Thu, Jul 12, 2012 at 12:45 PM, neo nortan wrote:
>
> Please help
> i have configure two instances of kannel on two different ports.both are
> working fine, messages or going properly and dlrs are also recieving
> properly in sent_sms table. but not able to understand after sen
Please help
i have configure two instances of kannel on two different ports.both are
working fine, messages or going properly and dlrs are also recieving properly
in sent_sms table. but not able to understand after sending some message one or
two messages get stuck, not getting dlrs of these
database = kannel
> #max-connections = 1
>
>
>
> Regards
> Abhi
>
>
> On Sun, Jun 17, 2012 at 6:22 PM, Julien Buratto
> wrote:
>
>> **
>> Do you also run the smsbox ?
>> If so, check also that when inserting the row in the db, you set the
>> smsbox
Tel.02 30321419
> --
> *From: * alok srivastava
> *Sender: * users-boun...@kannel.org
> *Date: *Sun, 17 Jun 2012 18:14:42 +0530
> *To: *
> *Subject: *not getting DLRs
>
> dear
> my kannel is working fine when things are passed from url. but when i try
> to send the message from send_sms table message send and move to sent_sms
> and also delivered to phone properly but not getting Delivery report.
>
>
> regards
> abhi
>
gDate: Sun, 17 Jun 2012 18:14:42
To:
Subject: not getting DLRs
dear
my kannel is working fine when things are passed from url. but when i try
to send the message from send_sms table message send and move to sent_sms
and also delivered to phone properly but not getting Delivery report.
regards
abhi
dear
my kannel is working fine when things are passed from url. but when i try
to send the message from send_sms table message send and move to sent_sms
and also delivered to phone properly but not getting Delivery report.
regards
abhi
online
Visitenos en www.perusms.NET www.smsglobal.com.mx y
www.pravcom.com
On Wed, Jun 13, 2012 at 3:14 AM, alok srivastava wrote:
> daer
> pl tell me kannel_dlr table not recieving every sent sms dlrs while every
> time i insert same data from send_table some times it'
can you please paste some portion of logs ?
It might be a wrong database table (so kannel is not able to write the dlr
in it) or simply the process is very quick and you don't see it :-)
2012/6/13 alok srivastava
> daer
> pl tell me kannel_dlr table not recieving every sent sms
daer
pl tell me kannel_dlr table not recieving every sent sms dlrs while every
time i insert same data from send_table some times it's showing the dlr
entry in kannel_dlr table and sometimes not. plz help me not able to
understand why it's going on.
regards
abhi
you need to specify dlr_mask when inserting message into send_sms in order
to get DLR report
if you want all reports simply insert with dlr_mask=31
2012/6/7 alok srivastava
> *my core group log file giving (kannel/logs/kannel4.log)*
>
> 2012-06-07 21:07:58 [21767] [6] DEBUG: type_name: enquir
*my core group log file giving (kannel/logs/kannel4.log)*
2012-06-07 21:07:58 [21767] [6] DEBUG: type_name: enquire_link_resp
2012-06-07 21:07:58 [21767] [6] DEBUG: command_id: 2147483669 = 0x8015
2012-06-07 21:07:58 [21767] [6] DEBUG: command_status: 0 = 0x
2012-06-07 21:07:58 [
ts subject line). I also saw a full opensmppbox config
attached to another post to this list where this option was used
inside a http smsc with system-type set to 'kannel'. Since I wrote my
last message to this list I realized that the DLRs he was referring to
work only in the opposite di
10 May 2011 13:52
To: users@kannel.org
Subject: DLRs and the http smsc
Dear Nikos, Rene, Alexander and everyone else,
I'm sorry to bother this list and particularly the maintainers with this
question, but I'm puzzled about kannel's behavior (or my
ignorance) regarding DLRs and t
Dear Nikos, Rene, Alexander and everyone else,
I'm sorry to bother this list and particularly the maintainers with
this question, but I'm puzzled about kannel's behavior (or my
ignorance) regarding DLRs and the http smsc.
I'm trying to set up kannel with opensmppbox to r
Before I scope a patch to address this, any comments or disagreements?
>
> Also, I haven't tried this with memory-only DLRs - is this an issue limited
> to SQL DLR storage? From looking at my logs, it seems that a DLR is indeed
> created in memory for the second and s
emory-only DLRs - is this an issue limited
to SQL DLR storage? From looking at my logs, it seems that a DLR is indeed
created in memory for the second and subsequent message parts, just not
written to the DB.
Thanks,
Toby
-Original Message-
From: Alvaro Cornejo [mailto:cornejo.alv...@gmail.
eturns a DLR for each part. Kannel recognizes the first DLR and updates
> the database. When the DLRs for the remaining parts arrive, Kannel tries to
> find them in the database and fails, spitting out an error (see below).
>
> Specifically:
>
> 1. When the submit_sm_resp PDU
rt. Kannel recognizes the first DLR and updates
the database. When the DLRs for the remaining parts arrive, Kannel tries to
find them in the database and fails, spitting out an error (see below).
Specifically:
1. When the submit_sm_resp PDU for the first message part arrives, Kannel
happily creates
Hi!
I have a really urgent problem! We have Kannel 1.4.3 Operating on the customer
site.. using the protocol cimd2 to an SMSC (actually we have 5 different SMSC)
but the customer wants us to send the SMS only to the first SMSC (named sc1)-
the SMSC provider has confirmed that he allows DLR (so
Hi,
Not with system-type generic. It doesn't provide a receive endpoint. You
should use system-type kannel for that.
BR,
Nikos
- Original Message -
From: "Garth Patil"
To: "Users mailing list"
Sent: Sunday, January 09, 2011 2:52 AM
Subject: DLRs using
Hi,
I'm trying to use the "generic" system type with the HTTP content
gateway (smsc = http, system-type = generic). The content gateway I am
using provides a delivery report that is posted back to a specified
URL. Is it possible for Kannel to be the endpoint for this delivery
report, so that it can
while doing the patch to make this work, i found out that all things are
in place except a way to configure bearerbox to route to source boxes
and line that would add boxc_id to dlrs. as i have no idea what would be
the best way to make it configurable, i just did simple patch that
hardcodes the
PDUs to see what's wrong.
BR,
Nikos
- Original Message -
From: James E
To: Nikos Balkanas ; users@kannel.org
Sent: Wednesday, December 08, 2010 1:11 PM
Subject: Re: opensmpp, sqldlr, bearorbox multiple dlrs
Thanks Nikos for making it clearer.. I will dig a little deeper and get to
t
1 - 100 of 239 matches
Mail list logo
