On Mittwoch, September 17, 2003, at 02:24 Uhr, Rory Campbell-Lange wrote:
Hi. I've been playing around using sdb for my dlr storage. I've got it
working nicely for Postgresql. However I had to do some muddling around
with the code (I've never worked with C before) after noting some
oddities in t
Hi. I've been playing around using sdb for my dlr storage. I've got it
working nicely for Postgresql. However I had to do some muddling around
with the code (I've never worked with C before) after noting some
oddities in the database calls.
UPDATE and DELETE don't take "Limit" clauses, certainly n
I have a problem with only one incoming smsc being available as Orange
only give me one port to connect to.
I am using two outgoing smsc-groups for different ton values (short and
long numbers). However only the short code is set for incoming.
This is a REAL problem for delivery reports. These ar
In theory this will work with 16 + 2 + 1 -> 19
On 16/09/03, Bill Brigden ([EMAIL PROTECTED]) wrote:
> On one of the production servers I manage, we use a value of 7 - as that
> allows for success / failure / buffer... although buffer doesnt come..
>
> However, that brings something up in my mind
I think there is an easy response to this: duh!
- Original Message -
From: "Alexander Malysh" <[EMAIL PROTECTED]>
To: "Bill Brigden" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Tuesday, September 16, 2003 5:32 PM
Subject: Re: dlr mask question...
Hi,
On Tuesday 16 September 2003 18:2
Hi,
On Tuesday 16 September 2003 18:25, Bill Brigden wrote:
> Hi,
>
> Really obvious question. when I submit a message via sendsms with a
> dlrmask as 7 - why do I get a code 16 back if its rejected via the
> submit_sm_resp? Surely the dlrmask 7 stops this - or am I missing
> something?
it's
Hi,
Really obvious question. when I submit a message via sendsms with a
dlrmask as 7 - why do I get a code 16 back if its rejected via the
submit_sm_resp? Surely the dlrmask 7 stops this - or am I missing something?
Bill.
Hi,
should this be a joke?
On Tuesday 16 September 2003 17:53, Jarrod Hermer wrote:
> Hi Guys,
>
> Please bear with me as I am most certainly not technically capable of
> solving this problem myself, or even understanding it for that matter.
>
> One of the networks that we connect to has changed
Hello,
I have a question about the quality of service of the Kannel SMS
Gateway.
I will connect Kannel to a SMSC with a rate of 64 Kbit/s.
I would like to know how many sms could be received by Kannel ?
2 SMS per Sec 10, 100, 1000 ??
thanks a lot.
Hi Guys,
Please bear with me as I am most certainly not technically capable of
solving this problem myself, or even understanding it for that matter.
One of the networks that we connect to has changed to a different type
of SMSC. The full name of the product is: SchlumbergerSema MGA Gateway
v2.2
Thanks. Hoping that these would be recovered from the store file in the
recent releases.
Thanks for all the help.
Rory
On 16/09/03, Bill Brigden ([EMAIL PROTECTED]) wrote:
> Quote from the Kannel userguide:
>
> Delivery reports are supported by default internaly, which means all DLRs
> are store
Hi Rory,
Quote from the Kannel userguide:
Delivery reports are supported by default internaly, which means all DLRs
are stored in the memory of the bearerbox process. This is problematic if
bearerbox crashes or you take the process down in a controlled way, but
there are still DLRs open. Therefor
Ah, very interesting. So should I use a dlr-mask of 19? (smsc reject + delivery
failure + delivery success)? The "message buffered" value is therefore of no
interest to me?
* 1: delivery success
* 2: delivery failure
* 4: message buffered
* 8: smsc submit
* 16: smsc reject
Las
you will never get buffered dlr on smpp link, because smpp doesn't request
intermediately delivery notifications (if you got these, then smsc is 100%
broken)...
On Tuesday 16 September 2003 16:20, Rory Campbell-Lange wrote:
> Hi. It works with msg-id-type = 1
>
> There is still a small problem t
Hi. It works with msg-id-type = 1
There is still a small problem though. I set my dlr-mask to 7 but
although bearerbox reported that my message was buffered, this did not
get reported to the dlr-url.
To test this I turned my phone off and sent the message. I would have
expected two values to have
your sender/receiver are swapped. what SMSC are you connected to?
On Dienstag, September 16, 2003, at 03:36 Uhr, Rory Campbell-Lange wrote:
Thanks for the pointers, Bill. Recompilation seemed to go well. I am now
running 'cvs-20030915'.
I'm still having problems with dlr reports. The status h
Hi again,
try to define: msg-id-type = 1 in your smsc group...
On Tuesday 16 September 2003 15:36, Rory Campbell-Lange wrote:
> Thanks for the pointers, Bill. Recompilation seemed to go well. I am now
> running 'cvs-20030915'.
>
> I'm still having problems with dlr reports. The status html page s
Could you post the associated submit_sm and submit_sm_resp (or another pair
of submits and deliver's for the a message) - It could be either an SMSC
giving "extra receipts" where you haven't requested them, or the message ID
is getting confused between types (hex or decimal)
- Original Messag
Thanks for the pointers, Bill. Recompilation seemed to go well. I am now
running 'cvs-20030915'.
I'm still having problems with dlr reports. The status html page shows
the dlrs stored internally. I'm trying to specify a dlr-url in the
sending url (see below).
2003-09-16 14:01:22 [7] DEBUG: D
Andreas Fink wrote:
>
> Ok before reading your stuff, I start to shout *grin*
>
> Questions:
>
> a) can we change the license at all? wouldnt that violate the original license?
I guess yes. I'm no lawyer too, but I'd like to go this way.
WapIT assets have been managed by finish lawyers that tr
On Dienstag, September 16, 2003, at 12:06 Uhr, Stipe Tolj wrote:
Hi Kannel developers,
this is a "shout-and-vote" request. So please take it seriously.
As I mentioned some time ago, I'd like to change the Lincense of
Kannel. Which does not mean we want to move away from BSD-style. This
*will*
Hi,
Looking through cvs:
2003-06-19 Stipe Tolj <[EMAIL PROTECTED]>
* gw/dlr*.[ch], gw/smsc_[soap|smpp|oisd|emi2|cimd2|cgw|at2].c,
gw/bearerbox.c: Alexander's major DLR rewrite to support callbacks
for the various storage types.
[Msg-ID: <[EMAIL PROTECTED]>]
If you can do
Thanks for your message, Bill and Alexander.
I'm using 1.3.1. Have the cvs changes to the DLR system been made since
then? I really don't mind helping test, but my server is in almost
constant use, and I don't want to cause disruptions in service if that
isn't necessary.
Thanks!
Rory
On 16/09/03
Hi Kannel developers,
this is a "shout-and-vote" request. So please take it seriously.
As I mentioned some time ago, I'd like to change the Lincense of
Kannel. Which does not mean we want to move away from BSD-style. This
*will* remain!
Please see attached the modified LICENSE file I'd like to s
Hi Rory,
I observed this in 1.2.1 a while ago, and then switched over to the cvs
version (which I have found is completely stable) where the DLR mechanism
was re done, and that seemed to fix the problem
- Original Message -
From: "Rory Campbell-Lange" <[EMAIL PROTECTED]>
Cc: <[EMAIL
Hi,
I would propose, you retest with cvs version of kannel...Just check cvs
version out and retest, please report your success/fail stories, so we can
fix dlr code if a problem still there...
Thanks in advance...
On Tuesday 16 September 2003 11:25, Rory Campbell-Lange wrote:
> I'm sending mess
I'm sending messages out using SMPP and its working great. I need to get
DLRs working and I'm having some problems.
Problem 1: dlrmask and multiple reports
===
Last night I sent some messages with a dlrmask of 31, and I got a '12'
result but then that was it, a
27 matches
Mail list logo
