I agree with James on this - using relative times is much easier to deal
with - clocks don't matter. I've got a patch for this around here
somewhere if anyone's keen.
But for backwards compatibility (support 3.3) the gwqdiff calculation
could just be improved to consider years (+ leap), months an
Hi Alex,
How about this (see patch) - not sure if it's *nice* to use difftime but
it keeps it clean.
Cheers,
Alan
ps. will look at have a relative vs absolute patch if 3.3 or >=3.4, etc
On Thu, 2004-11-18 at 03:23, Alexander Malysh wrote:
> Paul Keogh wrote:
>
> >
> >>
> >> Btw. I don't kno
kannel sends reply back via SMSC2 too.
> Then i set config block of SMSC2 above SMSC1. And if I send sms
> request from SMSC1, kannel sends reply back via SMSC1, but if i send
> sms request from SMSC2 kannel send reply back via SMSC1 too.
>
> Only if i set routing based on "allowed-prefix" in my config, then all
> work fine. But kannel users guide shows than i can do routing based on
> "smsc-id, denied-smsc-id, accepted-smsc" params.
>
> What i do wrong?
>
> Thank you beforehand.
>
>
--
Alan McNatty <[EMAIL PROTECTED]>
--
Alan McNatty <[EMAIL PROTECTED]>
:
>
> 2005-02-03 12:31:37 [7737] [4] INFO: Starting to service from
> <+27828553923> to <+2782121>
>
> It looks like it received "Play" correctly.
>
> However, I will test the mo-recode = true as you suggested.
>
> Thanks again
>
> Johann
>
>
>
>
--
Alan McNatty <[EMAIL PROTECTED]>
--
Alan McNatty <[EMAIL PROTECTED]>
Hi there,
There is an opening at Catalyst IT (www.catalyst.net.nz) for someone
familiar with Kannel and related technologies. Ideally also skilled in
Java, Perl, and Php. If you are interested in working in Wellington, New
Zealand please email [EMAIL PROTECTED]
Cheers,
Alan
--
Alan McNatty
ask(077);
-
/* Leave file descriptors 0, 1, and 2 pointing to harmless
* places, and close all other file descriptors. */
rebind_standard_streams();
I am happy to submit some debian patches to get the discussion going also.
Cheers,
Alan
--
Alan McNatty
Catalyst IT
DDI: +64 (0)4 8032201, or
TEL: +64 (0)4 4992267
ighly
welcome...
Alan McNatty schrieb:
Hi All,
We're been on stock standard debian kannel installs for awhile now so
it's simply a matter of using kannel out of the box these days which
is great.
However we've had an ongoing annoyance running kannel on servers which
we don
run_kannel_box because it's deprecated, just use:
/.../bearerbox --daemon
/.../smsbox --daemon
Thanks,
Alex
P.S. A new init scripts for debian using --daemon option are highly
welcome...
Alan McNatty schrieb:
Hi All,
We're been on stock standard debian kannel installs for awhile no
tar.gz
Extract it and you'll find a "new" init.d script and a sample
configuration file you can use to be running in no time. It is designed
to be used with user "kannel". You can of course tweak it to suit your
needs.
Regards,
Alejandro Guerrieri
El 17/11/2008, a las
CE"
- END
After patching, autoconf needs to be run to recreate the ./configure script
Regards,
Alejandro Guerrieri
--
Alan McNatty
Catalyst IT
DDI: +64 (0)4 8032201, or
TEL: +64 (0)4 4992267
x ...
kannel5569 1 0 08:39 ?00:00:00 /usr/sbin/wapbox ...
kannel5570 5569 0 08:39 ?00:00:00 /usr/sbin/wapbox ...
Thanks,
Alex
Alan McNatty schrieb:
Hi Alex,
How about this simple change for default kannel init.d script. Does
this look sensible?
If this looks
h only one
>>>>>> at-smsc even if messages have a destination smsc-id specified in
>>>>>> sendsms url call
>>>>>>
>>>>>> This is an snippet of the config I have:
>>>>>>
>>>>>> smsc-id = id1
>>>>>> allowed-smsc = id1,id_op1
>>>>>>
>>>>>> smsc-id = id2
>>>>>> allowed-smsc = id2,id_op1
>>>>>>
>>>>>> smsc-id = id3
>>>>>> allowed-smsc = id3,id_op1
>>>>>>
>>>>>> smsc-id = id4
>>>>>> allowed-smsc = id4,id_op2
>>>>>>
>>>>>> smsc-id = id5
>>>>>> allowed-smsc = id5,id_op2
>>>>>>
>>>>>> etc...
>>>>>>
>>>>>> Note there is no smsc defined with smsc-id=id_op1 nor id_op2 in
>>>>>> config
>>>>>> file.
>>>>>>
>>>>>> When sending the messages I use &smsc-id=id_op1 or id_op2 into url so
>>>>>> kannel load-balance through the smsc of corresponding operator and
>>>>>> send the message. This works fine until I restart kannel.
>>>>>>
>>>>>> After kannel reset, All QUEUED messages are sent through ONLY ONE of
>>>>>> the smsc without load-balancing between smsc even though there are
>>>>>> hundreds of queued messages; however if, at the same time, I send
>>>>>> messages to any of the id_op1 or id_op2, this new messages are
>>>>>> correctly load-balanced between smsc-at
>>>>>>
>>>>>> I use:
>>>>>>
>>>>>> Kannel bearerbox version `1.4.3'. Build `Feb 13 2009 17:32:59',
>>>>>> compiler `4.1.2 20070626 (Red Hat 4.1.2-13)'. System Linux, release
>>>>>> 2.6.20-1.2962.fc6, version #1 SMP Tue Jun 19 19:27:14 EDT 2007,
>>>>>> machine i686. IP 10.10.5.2. Libxml version 2.6.29. Using OpenSSL
>>>>>> 0.9.8b 04 May 2006. Compiled with MySQL 5.0.27, using MySQL 5.0.27.
>>>>>> Using native malloc.
>>>>>>
>>>>>>
>>>>>> Any ideas?
>>>>>>
>>>>>>
>>>>>> Regards
>>>>>>
>>>>>> Alvaro
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> |-|
>>>>>>
>>>>>> 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. Use
>>>>>> aplicaciones 2 vias
>>>>>> via
>>>>>> SMS y GPRS online
>>>>>> Visitenos en www.perusms.NET www.smsglobal.com.mx y
>>>>>> www.pravcom.com
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
--
Alan McNatty, Wellington, New Zealand
Catalyst IT Limited <http://www.catalyst.net.nz/>
DDI: +64 4 8032201
n this will startup without all SMScs available.
>
> Available is different than Active. Available means anything but Failed
> (Dead,etc.). An available SMSc could be down, or coming up or connecting.
>
> In this patch, router will wait to start until all SMScs become active.
>
&g
7;stuff' (from SMPP) perspective - it's obviously
in my interest here ;). As of now I haven't used a-lot of the routing
features so this is a bit new to me (I will try and get back into it and
hopefully make some suggestions).
Cheers,
Alan
--
Alan McNatty, Wellington, New Zealand
Catalyst IT Limited <http://www.catalyst.net.nz/>
DDI: +64 4 8032201
gw/msg.h
+ line 179: Msg *msg_unpack_wrapper(Octstr *os);
but this appears?
--
Alan McNatty, Wellington, New Zealand
Catalyst IT Limited <http://www.catalyst.net.nz/>
DDI: +64 4 8032201
# Core stuff
group = core
admin-port = 13000
admin-password = bar
admin-deny-ip = "*.*.*.*"
admin-
kannel version (e.g. before the meta-data
patch) it could cause such problems.
Regards,
--
Alejandro Guerrieri
aguerri...@kannel.org
On 10/07/2009, at 6:53, Alan McNatty wrote:
Hi all,
I have just been testing sqlbox with a modem for monitoring purposes.
Without the sqlbox (bearerbox-port
> to do it here where the main developers coexist (you're also on the
> users list, but most don't participate that much on it).
>
> What do you guys think?
>
>
--
Alan McNatty, Wellington, New Zealand
Catalyst IT Limited <http://www.catalyst.net.nz/>
DDI: +64 4 8032201
MOB: +64 21 02950201
Hi Werner,
Do you mean something like this (ignore white-space differences)?
Index: gw/smsbox.c
===
RCS file: /home/cvs/gateway/gw/smsbox.c,v
retrieving revision 1.284
diff -u -b -r1.284 smsbox.c
--- gw/smsbox.c 6 Dec 2009 17:24:14
Hi All,
Just following up on this historical thread [1] as I came across it
recently building 1.5.0 on an old box running Solaris 10. The upshot is
it's all do-able (I had success with OpenCSW) - just check your paths
(and run a ldd on the resulting binaries to make sure you haven't
incorporated a
Hi Alex,
Thanks for rolling us a new deb.
Thanks also for building with Postgres support - that will save me
rolling my own :)
Just a couple of questions:
1) I notice we have the usual binaries ... but I thought there was talk
of run_kannel_box being deprecated since we have --parachute --daemo
Hi All,
I found a thread on this from back in Feb 2005 (having received a query
from provided now myself) .. last word by Alejandro and a lukewarm (+0 -
+1) comment from Stipe about committing if patch provided. I would
provide a config patch if anyone would vote in it's favour?
Consider:
gw/sms
>
> BR,
> Nikos
> - Original Message -
> From: "Alan McNatty"
> To:
> Sent: Monday, August 01, 2011 6:21 AM
> Subject: Making SMPP esm_class configurable?
>
>
> > Hi All,
> >
> > I found a thread on this from back in Feb 2005 (having
_class = pdu->u.submit_sm.esm_class |
ESM_CLASS_SUBMIT_UDH_INDICATOR;
On Tue, 2011-08-02 at 15:59 +1200, Alan McNatty wrote:
> Hi Nikos,
>
> You mean simply change the default:
>
> Index: gw/smsc/smsc_smpp.c
>
those, only reliable store and forward. Therefore the
> default mode wouldn't be appropriate.
> Configuration would be fine for those buggy SMScs, that do store and
> forward, but do not accept it as an option.
>
> BR,
> Nikos
>
> ----- Original Message -
>
patch attached.
Votes / comments, etc?
On Wed, 2011-08-03 at 09:39 +1200, Alan McNatty wrote:
> Thanks Nikos/Alex for the feedback - I will work on config patch.
>
> On Tue, 2011-08-02 at 23:10 +0300, Nikos Balkanas wrote:
> > Hi Alan,
> >
> > Just to clarify on
hex (0xA5).
>
>
> +1
>
>
>
> Nikos
>
> On Mon, Aug 8, 2011 at 4:02 AM, Alan McNatty
> wrote:
> patch attached.
>
> Votes / comments, etc?
>
> On Wed, 2011-08-03 at 09:39 +1200, Alan McNatty
;
>
> Value for esm_class according to the SMPP spec. Accepted values are 0
> (Default smsc mode) and 3 (Store and Forward). Defaults to 3.
>
>
> HTH,
> Nikos
>
> On Mon, Aug 8, 2011 at 5:01 AM, Alan McNatty
> wrote:
> Thanks Nikos,
>
Hi All,
I'm finding what I think is incorrect use of gwlist_extract_first in the
postgres dlr implementations (it may also exist in others - I've not
checked yet). The DLR methods issue 'error's when they fail to return
results, etc but subsequent calls to gwlist_extract_first on NULL lists
cause
being a running bearerbox without any smsbox(es)
attached.
On Wed, 2011-08-10 at 16:51 +1200, Alan McNatty wrote:
> Hi All,
>
> I'm finding what I think is incorrect use of gwlist_extract_first in the
> postgres dlr implementations (it may also exist in others - I've not
&
nd stops responding to the
> heartbeats that smsbox sends. As a result, smsbox logs in "bearerbox
> gone, shutting down" and shuts down. The parent bb process should
> handle heartbeats, not the child.
>
>
>
> HTH,
> Nikos
>
> On Wed, Aug 10, 2011 at 9:56 AM, Al
09 August, 2011 02:11
> To: Alan McNatty
> Cc: devel@kannel.org
> Subject: Re: Making SMPP esm_class configurable?
>
>
>
>
> Looks great! +1.
>
>
> Nikos
>
>
>
>
> On Tue, Aug 9, 2011 at 2:59 AM, Alan McNatty
> wrote:
>
> Th
t; wait for commission. Don't worry, he never misses a patch. He is the
> gateway maintainer.
>
>
>
> BR,
> Nikos
>
> On Mon, Aug 15, 2011 at 3:22 AM, Alan McNatty
> wrote:
> Thanks Rene,
>
> Can anyone with commit access give a
ist_get(gwlist_get(res, 0), 0)));
> }
>
> -gwlist_destroy(gwlist_extract_first(res), octstr_destroy_item);
> +if ( res != NULL )
> + gwlist_destroy(gwlist_extract_first(res), octstr_destroy_item);
>
> I put this inside else because there we know the list is n
; >
> > For cannel it's equal, which value to set as esm-class
> > because kannel doesn't interpreting it.
> >
> > Thanks,
> > Alex
> >
> > Am 15.08.2011 um 09:35 sc
write my response late (I was on vacation), but I
> > don't think we need some restriction on configured
> > esm-class.
> > If we allow to change esm-class in the config, IMHO there is
> > no need to restrict it's value, because
>
;
> >> On Sep 8, 2011, at 12:29 PM, Alexander Malysh wrote:
> >>
> >>> Hi Alan,
> >>>
> >>> thanks for the patch but I'm waiting for more comments in this topic.
> >>> If no comments coming, I will commit your patch next week.
> &g
Ah that's great, thanks Alex.
On Wed, 2011-09-14 at 22:08 +0200, Alexander Malysh wrote:
> Hi Alan,
>
> after the long discussion this patch commited to SVN.
>
> Thanks,
> Alexander Malysh
>
> Am 15.08.2011 um 09:35 schrieb Alan McNatty:
>
> > Thanks
Hi Stipe,
Sounds great - as you say being able to use disk based replication
techniques would be good but also providing persistence as a default
option is also very valuable. I'll be keen to do some tests on IO
performance - my biggest concern for larger installs (as often disk
choice is not nece
On Wed, 2012-08-08 at 09:43 +1200, Alan McNatty wrote:
> also providing persistence as a default option is also very valuable.
An additional enhancement might be to spool the current in memory hash
on shut-down and load on start-up.
/dlr.c:252
#12 0x08053155 in main (argc=2, argv=0xb164) at gw/bearerbox.c:706
I'm still trying to get my head around how the unpack func is
set-up ,etc.
Cheers,
Alan
On Thu, 2012-08-09 at 13:47 +0200, Stipe Tolj wrote:
> Am 07.08.2012 23:43, schrieb Alan McNatty:
> > Hi St
-09 at 14:00 +0200, Stipe Tolj wrote:
> Am 07.08.2012 23:54, schrieb Alan McNatty:
> > On Wed, 2012-08-08 at 09:43 +1200, Alan McNatty wrote:
> >> also providing persistence as a default option is also very valuable.
> >
> > An additional enhancement might be to sp
Hey spameden,
Watch the x-posting. Search the mailing archives the author did post
from memory. I tried to build but didn't success (likely issues at my
end with make related things).
My 2c .. Whilst I was interested we already have DB set-up on related
platforms so adding more to the mix doesn't
Hi Rene,
That's incorrect ..
r4926 | amalysh | 2011-09-15 08:07:10 +1200 (Thu, 15 Sep 2011) | 3 lines
* doc/userguide/userguide.xml, gw/smsc/smsc_smpp.c, gwlib/cfg.def:
applied
patch that allows setting of esm_class in SMPP module.
Thanks to Alan McNatty for the
Hi Brenton,
To me one consistent message I am hearing is environment (network /
comms) issues - mySQL disconnect, monitoring showing up and down ..
status slow response. These don't sound like issues with Kannel
itself .. but possibly how you are trying to implement it. It could be
something like
but I am unable to locate the file. The post
> is old so maybe the file name has changed. Can
> someone tell me where I can locate it please.
>
>
> --
> Regards,
> Eric Magutu
>
Gerrit worth considering also
On Mon, 2014-04-21 at 05:15 +, Rachman Chavik wrote:
> Hi,
>
> Is there any plans to migrate to git? Or even to github?
> IMO, this will make contributions much easier.
>
>
signature.asc
Description: This is a digitally signed message part
Very, very sad news. Thank you for sharing Stipe - our thoughts with
his family and friends at this time.
RIP René. Your reach was global - your contributions will live on.
On Fri, 2021-06-11 at 15:00 +0200, Stipe Tolj wrote:
> Dear all,
> With deep regret and sorrow we let you know that René Klu
wsgram.c
> wmlscript/wsgram.y:138: invalid @ value
> wmlscript/wsgram.y:405: invalid @ value
> make: *** [wmlscript/wsgram.c] Error 1
>
> This problem came out also from the devel list.
>
> And there was no answer, how can i solve this?
>
> im trying to update my 1.3.0.
>
> thanks
--
Alan McNatty <[EMAIL PROTECTED]>
attached).
As a result shouldn't need the cp config.sub, config.guess in
debian/rules - no harm in leaving as is... but attached patch for
completeness.
Cheers,
Alan
--
Alan McNatty <[EMAIL PROTECTED]>
Index: Makefile.in
id:02706
[6] DEBUG: data: 36 32 38 30 38 20 73 75
62808 su
...
--
Alan McNatty <[EMAIL PROTECTED]>
nnecting to server `...' at port
'...'
2003-07-08 09:46:56 [6] ERROR: SMPP[..]: Couldn't connect to server.
2003-07-08 09:46:56 [6] ERROR: SMPP[..]: Couldn't connect to SMS center
(retrying in 10 seconds).
--
Alan McNatty <[EMAIL PROTECTED]>
Hello,
run_kannel_box is a strange beast (at least to me). It's purpose seems
unclear (or more appropriately 'undocumented'). I understand it's part
of the utils directory (out of main source) but it is part of standard
build (eg: debian packages).
Andres could you explain a bit about what it's
es the first word regardless of case with
> words starting with 'SEC' and second words starting with 'WOR'
>
> Aliases are handled in the same way.
>
> Basically this involves some fairly heavy rewrites to Kannel's
> behaviour but my thoughts are it would be better to keep this in
> Kannel, than to move the second + x word matching to separate code.
>
> Thoughts from everyone?
>
> Regards
>
> Alex
--
Alan McNatty <[EMAIL PROTECTED]>
actually get the wapbox syslogging to work I believe.
Please comment/vote, etc ...
--
Alan McNatty <[EMAIL PROTECTED]>
Patch to run_kannel_box to log to syslog.
On Wed, 2003-07-09 at 12:54, Andreas Fink wrote:
> On Dienstag, Juli 8, 2003, at 11:13 Uhr, Alan McNatty wrote:
>
> Hello,
>
> run_kannel_box is a strange beast (at least to me). It's
> purpose
patch attached.
On Wed, 2003-07-30 at 10:13, Alan McNatty wrote:
> Hello,
>
> I have attached a small patch to add syslog logging support for both
> smsbox and bearerbox as was done for wapbox some time ago. I have made
> some minor changes to gwlib/log.c to reformat in case of
>
> Thanks in advance...
>
> On Wednesday 30 July 2003 00:16, Alan McNatty wrote:
> > Patch to run_kannel_box to log to syslog.
> >
> > On Wed, 2003-07-09 at 12:54, Andreas Fink wrote:
> > > On Dienstag, Juli 8, 2003, at 11:13 Uhr, Alan McNatty wrote:
> >
On Fri, 2003-08-08 at 21:25, Aaron Brady wrote:
> > Looks good, however I'd potentially make it more configurable so that the
> X
> > x wait is one of the default settings and can be configured should it need
> > be.
>
> If it's easy enough, then I don't see why not, but I'm not altogether
> famil
Hi Alexander,
I prefer Alex's patch as it conforms more closely to spec I believe.
Alex I have added a couple of bits to your patch (cfg.def and
docs/userguide.xml). Please double check this and vote.
Cheers,
Alan
On Tue, 2003-08-19 at 05:10, Alexander Malysh wrote:
> Hi Alex,
>
> sorry for
On Tue, 2003-08-19 at 09:45, Alexander Malysh wrote:
> sorry but Alex's patch is not closely conforms to spec. Please read smpp v3.4.
> issue 1.2 page 165.
> Quote:
> inactivity_timer - This timer specifies the maximum time lapse allowed
> between _transactions_ , after which period of inac
Hi Stefan,
Your problem seems to be that the SMSC is switching source and
destination address (between submit_sm and deliver_sm). I have one SMSC
which does this ... ie: (from your logs)
submit_sm
DEBUG: destination_addr: "46708443600"
deliver_sm
DEBUG: source_addr: "46708443600"
WARNING: D
w you get on ... I haven't submitted because
> > this is broken implementation of SMPP.
>
> I had assumed that it was a bug in Kannel..?
>
>
> David.
>
>
> - Original Message -
> From: "Stefan Cars" <[EMAIL PROTECTED]>
> To: "
On Wed, 2003-09-24 at 23:21, Alexander Malysh wrote:
> >
> > I'm voting -1 for this mix feature
>
> I'm -0 for removing it. It's a nice mix ;) Some smsc's are soo broken , that
> msgs are rejected even when msg is correct... Ok I know , you would say: use
> DLR_SMSC_FAIL ;)
If you know the SMSC
On Thu, 2003-09-25 at 18:26, Andreas Fink wrote:
> >From a user's perspective you ask for a delivery report. You want
> toknow success or failure which are the two things you are
> interestedin. Those are the two most important ones to know. The end
> userdoesn't want to know exactly where it fail
> Be aware that if you get "message expired" this usuall ymeans that
> youcouldn't reach the destination phone for 7 days so I'm not
> thatconvinced you really want to resend in such a case.
Usually yes but not if you set validity period to a number of hours, etc
...
Hello list,
Experimenting with optional parameters in SMPP pdu's. Slowly getting my
head around pdu packing/unpacking (some clever stuff - taxing my poor
brain) ..
Reviewing previous posts to this list I found references to
append_encoded_integer which in cvs lives in both radius_pdu and
smpp_pd
Hello All,
Just a question really. I've been looking at the X-Kannel headers and
noted that if you receive an MO message from SMSC 'A' and you specify
the message should go back via SMSC 'A' for normal short message fine.
However if you respond with content with content that gets split. The
first
riggered?
Cheers,
Alan
[1] http://bugs.kannel.org/view_bug_page.php?f_id=101
On Thu, 2003-11-27 at 13:22, Stipe Tolj wrote:
> Alan McNatty wrote:
> >
> > Just a question really. I've been looking at the X-Kannel headers and
> > noted that if you receive an MO mess
Thanks - I will re-test with this set in config. May be able to close
out bug as a result.
Cheers,
Alan
On Sat, 2003-11-29 at 00:47, Stipe Tolj wrote:
> Alan,
>
> > Note my config doesn't include any allowed or preferred sections in smsc
> > configurations (except for MODEL connection). So it se
Hi Stipe,
Tested again with TEST1 and TEST2 connections both with allowed-smsc-id
= "TEST1;TEST2" - this makes them available as 'best' choices but not
preferred (so the first best choice wins, TEST1 or TEST2). So, if I have
smsc=TEST2 I still can't guarantee delivery via TEST2. I don't want to
se
in cgi
variables been superseded with the new routing process? Should it be
removed?
Cheers,
Alan
On Mon, 2003-12-01 at 12:24, Stipe Tolj wrote:
> Alan McNatty wrote:
> >
> > Tested again with TEST1 and TEST2 connections both with allowed-smsc-id
> > = "TEST1;TEST2"
Hi Rene (just replying to list this time).
If you delete the wmlscript/wsgram.y file everything is good. I've had
this problem before. Can't remember I'm thinking I was lazy and maybe
copied code from one server to the other (which used different yak type
animal).
Question: should distclean rem
Hi Bruno,
I've tested the pgsql dlr storage on 7.2.1 (debian stable) but found
that Kannel utilised a DELETE ... LIMIT 1 in dlr_pgsql_remove from
gw/dlr_pgsql.c which is not supported in 7.2.1.
ERROR: PGSQL: DELETE FROM dlr WHERE smsc='foo' AND ts='243251116' LIMIT
1;
ERROR: PGSQL: ERROR: parse
ne out of testing ages ago. 7.5 is halfway under development,
> because everyone in the "postgres world" (hate these tags, but they are
> sometimes needed) has implemented 7.4.
>
> These are the 2 cents from a deep-into-postgres-point of view.
>
> \\pb
>
>
&
by me and as
> stated on the ML was not stress tested!
>
>
> Alan McNatty wrote:
>
> > I agree completely - just highlighting for Bruno.
> >
> > If he's going to make a Debian package for stable it will be an issue if
> > package has is compiled --wi
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 confi
s) is made of ceo's, directors, chiefs and the rest of
> the "upper class management positions" plethora.
>
>
> \\pb
>
> Alan McNatty wrote:
>
> > Hi All,
> >
> > Just checking - the SMPP password field can be max octets of 9 in
> >
Hi All,
Small scenario where a receipted_message_id is provided with no
message_state (optional parameters).
The attached patch changes current behaviour - fails the dlr, but rather
falls through to try old style short_message (where some may succeed)
before failing.
Seems that some (SMSC) are
Hi Alex,
One of the problems in the past with the DLR search using destination
address is that it has been contrary to SMPP v3.4 specs. In section 2.11
Message Types we can note:
'The destination address will be taken from the source address of the
original short message which generated the deliv
Hi Kalle,
I'm hoping I've understood your post. Apologies if I've lost the plot -
I've put some questions/comments in-line below.
On Thu, 2004-10-07 at 01:52, Kalle Marjola wrote:
> So, what does this first version do:
> Instead of immediately saying '202 Send' for valid sendsms request, this
>
80 matches
Mail list logo