Hi David,
strange...
I have not never seen such message_id! One think i can say, SMSC is s
buggy! It's not allowed to get one message id in submit_sm_resp and another
one or part of them in delivery receipt. I would propose, you contact your
operator and give him a hint to look in SMPP spe
Alexander Malysh wrote:
>
> Hi David,
>
> strange...
>
> I have not never seen such message_id! One think i can say, SMSC is s
> buggy! It's not allowed to get one message id in submit_sm_resp and another
> one or part of them in delivery receipt. I would propose, you contact your
> operator
Hi
At 01:12 PM 6/26/03 +0200, Alexander Malysh wrote:
Hi David,
strange...
I have not never seen such message_id! One think i can say, SMSC is s
we have.. (No provider names mentioned) and yes they are real
flaky..Although this is a valid msg_id albeit very long.
NULTERMINATED(message_id
Hi Nisan,
I believe, you have not undestand the issue...
Very long is not a problem for kannel, the problem is, that message_id
received in submit_sm is not the same as in delivery receipt later. Just look
this example:
submit_sm -> submit_sm_resp -> msg_id = 02/00/b9637bb4/1135387292099
hi
At 06:40 PM 6/26/03 +0200, Alexander Malysh wrote:
Hi Nisan,
I believe, you have not undestand the issue...
yes, sorry.. my patch is for another message_id issue.
I have seen this same behaviour, allthough the provider failed many of our
other tests, so never made it to actual live usage
N
On Donnerstag, Juni 26, 2003, at 06:40 Uhr, Alexander Malysh wrote:
Hi Nisan,
I believe, you have not undestand the issue...
Very long is not a problem for kannel, the problem is, that message_id
received in submit_sm is not the same as in delivery receipt later. Just look
this example:
submi
Am Donnerstag, 26. Juni 2003 19:39 schrieb Andreas Fink:
> On Donnerstag, Juni 26, 2003, at 06:40 Uhr, Alexander Malysh wrote:
> > Hi Nisan,
> >
> > I believe, you have not undestand the issue...
> > Very long is not a problem for kannel, the problem is, that message_id
> > received in submit_sm i
On Thursday 26 June 2003 18:05, David Tully wrote:
> Hi!
>
>
> The middle bit of the submit_sm_resp is the message_id - 'b9637bb4' out of
> '02/00/b9637bb4/11353872920997'
> The rest is junk - the last number is the destination number.
Interesting, I've just noticed that I get a similar problem wi
oviders
;)
regards,
JS
- Original Message -
From:
Edwin Pratomo
To: David Tully ; [EMAIL PROTECTED]
Sent: Friday, June 27, 2003 11:18
AM
Subject: Re: non standard message_id
breaks DLR
On Thursday 26 June 2003 18:05, David Tully wrote:>
Hi!>>>
Edwin Pratomo wrote:
>
> On Thursday 26 June 2003 18:05, David Tully wrote:
> > Hi!
> >
> >
> > The middle bit of the submit_sm_resp is the message_id - 'b9637bb4' out of
> > '02/00/b9637bb4/11353872920997'
> > The rest is junk - the last number is the destination number.
>
> Interesting, I've ju
PROTECTED]
Sent: Thursday, June 26, 2003 6:39
PM
Subject: [-] Re: non standard message_id
breaks DLR
On Donnerstag, Juni 26, 2003, at 06:40 Uhr, Alexander
Malysh wrote:
Hi Nisan,I believe, you have not undestand the
issue...Very long is not a problem for kannel, the proble
On Donnerstag, Juni 26, 2003, at 11:30 Uhr, David Tully wrote:
Yes - saw that..
That's the consolation prize.. :)
I need to strip off the extra stuff and I'll have the hex message_id. Any ideas out there on the quickest way to do that? ;)
ask your SMPP link supplier to conform to the SMPP
From: "Edwin Pratomo" <[EMAIL PROTECTED]>
To: "David Tully" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Friday, June 27, 2003 6:48 AM
Subject: [-] Re: non standard message_id breaks DLR
On Thursday 26 June 2003 18:05, David Tully wrote:
> Hi!
>
>
&
Andreas Fink schrieb:
>
> On Donnerstag, Juni 26, 2003, at 11:30 Uhr, David Tully wrote:
>
> Yes - saw that..
> That's the consolation prize.. :)
>
> I need to strip off the extra stuff and I'll have the hex message_id. Any ideas
> out there on the quickest way to do that? ;)
an
start);
exit(0);
}
Regards,
David.
- Original Message -
From: "Stipe Tolj" <[EMAIL PROTECTED]>
To: "Alexander Malysh" <[EMAIL PROTECTED]>
Cc: "David Tully" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Thursday, June 26, 2003 4
On Thu, 3 Jul 2003 13:24:31 +0100, David Tully <[EMAIL PROTECTED]>
wrote:
Hey there.
I'm having a bit of a nightmare with this code mod..
I've a program that strips out the bit I need, but I can't figure out how
to work with the struct octstr..
Could someone help me out please?
hi,
IIRC, your
Angus M Wood <[EMAIL PROTECTED]> wrote:
> On Thu, 3 Jul 2003 13:24:31 +0100, David Tully <[EMAIL PROTECTED]>
> wrote:
>
> HTH.
>
> Side issue: would it be worth adding regexp support to Kannel? It could
> come in handy in the SMS service selection, this kind of weirdness, etc.
> The PCRE libra
, 2003 7:20 PM
Subject: Re: [-] Re: non standard message_id breaks DLR
> On Thu, 3 Jul 2003 13:24:31 +0100, David Tully <[EMAIL PROTECTED]>
> wrote:
>
> > Hey there.
> >
> > I'm having a bit of a nightmare with this code mod..
> >
> > I've a p
On Thu, 3 Jul 2003 20:55:32 + (UTC), Bruno Rodrigues
<[EMAIL PROTECTED]> wrote:
glibc already includes an regexp library. If you want to do this (and I
would really appreciate some octstr_reg_match and octstr_reg_replace ;))
you should create an abstraction layer in gwlib/ and compile it agai
19 matches
Mail list logo
