Hi Alexander,
patch applied to cvs. Thanks.
Stipe
[EMAIL PROTECTED]
---
Wapme Systems AG
Vogelsanger Weg 80
40470 Düsseldorf
Tel: +49-211-74845-0
Fax: +49-211-74845-299
E-Mail: [EMAIL PROTECTED]
Internet: http://www.wapme-systems
> BTW, after sending this patch I found a small BUG ;)
>
> +{ /* Read optional parameters */ \
> +while (pos+4 < len) { \
>
> Here must be:
> +{ /* Read option
hi
At 03:06 PM 1/26/03 +0100, Alexander Malysh wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Stipe,
On Sunday 26 January 2003 14:13, Stipe Tolj wrote:
> Hi Alexander,
>
> Alexander Malysh schrieb:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > Hi,
> >
> > attached patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Stipe,
On Sunday 26 January 2003 14:13, Stipe Tolj wrote:
> Hi Alexander,
>
> Alexander Malysh schrieb:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > Hi,
> >
> > attached patch make parsing of SMPP optional parameters more robust
>
Hi Alexander,
Alexander Malysh schrieb:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi,
>
> attached patch make parsing of SMPP optional parameters more robust (IMHO).
> Patch include some cleanups , increasing MAX_SMPP_PDU_LEN (because
> message_payload can be up to 64K octets) and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
attached patch make parsing of SMPP optional parameters more robust (IMHO).
Patch include some cleanups , increasing MAX_SMPP_PDU_LEN (because
message_payload can be up to 64K octets) and add ability to dump optional
parameters.
I have rewritt
