Hi Alex,

Am Mittwoch, 26. Februar 2003 16:30 schrieb Alex Judd:
> Alexander
>
> Not sure if that's true.
>
> According to the SMPP3.4 specs "C-Octet String A series of ASCII characters
> terminated with the NULL character. Notes: (i) Reference made to NULL
> settings of Octet-String fields implies that the field consists of a single
                                                                                       
                           ^^^^^^
Single is single;) That means only NULL without message body !
But you received 0x410x6c0x650x780x00 ??? This is totally wrong ...

> NULL character, i.e., an octet encoded with value 0x00 (zero)."
>
> Which would mean it's valid to send a message content of <message received>
>
> 2003-02-26 12:24:42 [6] DEBUG: SMPP[Vittel]: Got PDU:
> ..
> 2003-02-26 12:24:42 [6] DEBUG:   short_message:
> 2003-02-26 12:24:42 [6] DEBUG:    Octet string at f4ef8:
> 2003-02-26 12:24:42 [6] DEBUG:      len:  5
> 2003-02-26 12:24:42 [6] DEBUG:      size: 6
> 2003-02-26 12:24:42 [6] DEBUG:      immutable: 0
> 2003-02-26 12:24:42 [6] DEBUG:      data: 41 6c 65 78 00            Alex.
> ..                                                    ^^                ^
>
> which then is translated by Kannel as
>
> 2003-02-26 12:24:42 [6] INFO: Starting to service <Alex@> from
> <447740305115> to <80118>
>
> which is defintiely wrong.
>
> Yes, no?
>
> Alex
>
> ----- Original Message -----
> From: "Alexander Malysh" <[EMAIL PROTECTED]>
> To: "Stipe Tolj" <[EMAIL PROTECTED]>
> Cc: "Alex Judd" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
> Sent: Wednesday, February 26, 2003 3:16 PM
> Subject: Re: SMPP 3.4 C-Octet String Termination
>
> > it can't be C-Octet-String at all ;) Just think that '@' in GSM 03.38 is
>
> 0x00 ;)
>
> > Am Mittwoch, 26. Februar 2003 16:10 schrieb Stipe Tolj:
> > > Alexander Malysh wrote:
> > > > this is not the kannel problem! Your smsc sned wrong pdu:
> > > > please look smpp v.3.4 issue 1.2 site 61...
> > > > short_message field is Octet-String and not C-Octet-String.
> > > > Your smsc is just buggy ;)
> > >
> > > if that's the case, Alex, could you ask which explicit SMSC it is? So
> > > we can put the vendor and the model on a "not spec conform black-list"
> > >
> > > :)
> > >
> > > 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.de
> > > -------------------------------------------------------------------
> > > wapme.net - wherever you are
> >
> > --
> > Best regards / Mit besten Grüßen aus Köln
> >
> > Dipl.-Ing.
> > Alexander Malysh
> > ___________________________________________
> >
> > Centrium GmbH
> > Ehrenstraße 2
> > 50672 Köln
> >
> > Fon: +49 (0221) 277 49 240
> > Fax: +49 (0221) 277 49 109
> >
> > email: [EMAIL PROTECTED]
> > web: www.centrium.de
> > msn: [EMAIL PROTECTED]
> > icq: 98063111

-- 
Best regards / Mit besten Grüßen aus Köln

Dipl.-Ing.
Alexander Malysh
___________________________________________

Centrium GmbH
Ehrenstraße 2
50672 Köln

Fon: +49 (0221) 277 49 240
Fax: +49 (0221) 277 49 109

email: [EMAIL PROTECTED]
web: www.centrium.de
msn: [EMAIL PROTECTED]
icq: 98063111



Reply via email to