-Original Message-
From: Alan McNatty [mailto:[EMAIL PROTECTED]]
I experience the same problem but haven't been working on it lately
(dlr's on back burner at present). I have patched local copy to get
working though, my patch does something simple like ...
from handle_pdu -
Hi Oded,
I experience the same problem but haven't been working on it lately
(dlr's on back burner at present). I have patched local copy to get
working though, my patch does something simple like ...
from handle_pdu - deliver_sm
if ( pdu-u.deliver_sm.destination_addr !=
Sorry Oded I misread your original post - the deliver_sm pdu I receive
from smsc has source addr not destination, no relation to result of
dlr_find. Ignore me it's late here ;-)
On Wed, 2002-10-02 at 21:00, Oded Arbel wrote:
-Original Message-
From: Alan McNatty [mailto:[EMAIL
-Original Message-
From: Alan McNatty [mailto:[EMAIL PROTECTED]]
Sorry Oded I misread your original post - the deliver_sm pdu I receive
from smsc has source addr not destination,
Ok - and for DLR - does the source address contain the number of the original message
receiver or
ey, I like this. Early nothing."-- from 'The Big
Heat'
-Original Message-From: erick.fuentes
[mailto:[EMAIL PROTECTED]]Sent: Thursday, June 06,
2002 4:49 PMTo: Patrick Mignott;
[EMAIL PROTECTED]Subject: RE: DLR and SMPP fixed
yet?
If I
remember well you must defin
hello is the problem bellow fixed in the latest CVS
yet?
i am getting crashes with 1.1.6
2001-12-31 21:42:27 [9] DEBUG:
** SMPP
handle_pdu Got DELIVER REPORT2001-12-31
21:42:27 [9] PANIC: gwlib/octstr.c:2032: seems_valid_real:
Assertion `ostr != NULL' failed. (Called from
It is kind of weird that this problem exists in smpp, cimd AND emi/ucp ?
I'm gonna look through the source and do some packetscannning to see what
might be the problem..
On Sun, 6 Jan 2002, Andreas Fink wrote:
Stefan Cars wrote:
The same thing happens when connecting through EMI2.., so
It is kind of weird that this problem exists in smpp, cimd AND emi/ucp ?
I'm gonna look through the source and do some packetscannning to see what
might be the problem..
one possibility is if lets say the EMI driver returns a timestamp
being NULL and then an incoming message from CIMD is
Andreas Fink wrote:
Note on smsc-id:
if you got multiple links to the same SMSC then you MUST name the
smsc-id's all the same. I have for example 4 EMI links to the same
SMSC and I might send an SMS on the first link and receive the
delivery report on the 3rd link. If the smsc-id's
The same thing happens when connecting through EMI2.., so something must
be broken in the DLR implementation.
On Wed, 2 Jan 2002, Stefan Cars wrote:
The patched worked (it doesn't crash anymore) but the problem that it
doesn't find the DLR id is still there:
2002-01-02 11:01:41 [7] ERROR:
The patched worked (it doesn't crash anymore) but the problem that it
doesn't find the DLR id is still there:
2002-01-02 11:01:41 [7] ERROR: Got DELIV REPORT but couldnt find message
or was not interested in it
A similar problems occurs when using CIMD2 (when receiving the delivery
report from
]
To: Stefan Cars [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Tuesday, January 01, 2002 2:30 PM
Subject: Re: DLR and SMPP..
When using DLR with my SMSC that uses SMPP kannel crashes (cvs
version):
2001-12-31 21:42:27 [9] DEBUG: ** SMPP handle_pdu
Got DELIVER REPORT
2001-12-31 21
[EMAIL PROTECTED] wrote:
As I see it this approach with octstr_compare is a part of the Kannel's
protective coding style where the NULL pointers are not meant to be used
as any other similar pointer. So the assert prevents the NULL pointer to
go on loosely and stops it before it may cause a
[EMAIL PROTECTED] wrote:
As I see it this approach with octstr_compare is a part of the Kannel's
protective coding style where the NULL pointers are not meant to be used
as any other similar pointer. So the assert prevents the NULL pointer to
go on loosely and stops it before it may
When using DLR with my SMSC that uses SMPP kannel crashes (cvs
version):
2001-12-31 21:42:27 [9] DEBUG: ** SMPP handle_pdu
Got DELIVER REPORT
2001-12-31 21:42:27 [9]
PANIC: gwlib/octstr.c:2032: seems_valid_real: Assertion `ostr != NULL'
failed. (Called from
When using DLR with my SMSC that uses SMPP kannel crashes (cvs
version):
2001-12-31 21:42:27 [9] DEBUG: ** SMPP handle_pdu
Got DELIVER REPORT
2001-12-31 21:42:27 [9]
PANIC: gwlib/octstr.c:2032: seems_valid_real: Assertion `ostr != NULL'
failed. (Called from
When using DLR with my SMSC that uses SMPP kannel crashes (cvs
version):
2001-12-31 21:42:27 [9] DEBUG: ** SMPP handle_pdu
Got DELIVER REPORT
2001-12-31 21:42:27 [9]
PANIC: gwlib/octstr.c:2032: seems_valid_real: Assertion `ostr != NULL'
failed. (Called from
Andreas Fink wrote:
Why dont we modify octstr_compare that a NULL string can be compared too?
NULL would then be equal to . Does that make sense?
I'm not sure how deep the impact would be. Anyone from the core
architects still reading the list and have their heads up, please?!
Stipe
[EMAIL
When using DLR with my SMSC that uses SMPP kannel crashes (cvs
version):
2001-12-31 21:42:27 [9] DEBUG: ** SMPP handle_pdu
Got DELIVER REPORT
2001-12-31 21:42:27 [9]
PANIC: gwlib/octstr.c:2032: seems_valid_real: Assertion `ostr != NULL'
failed. (Called from
19 matches
Mail list logo
