Re: SMPP 3.4 C-Octet String Termination

Alexander Malysh <[email protected]>
Newsgroups gmane.comp.mobile.kannel.devel
Organization Centrium GmbH
Message-ID <[email protected]>
Hi,

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 ;)

Am Mittwoch, 26. Februar 2003 16:00 schrieb Stipe Tolj:
> Alex Judd wrote:
> > We're working with a SMPP 3.4 server that validly (according to the 3.4
> > specs) terminates the C-Octet Strings it sends us with a NULL character.
> > This currently isn't handled directly by Kannel and ends up as an extra
> > character on the message content.
> >
> > For example a message of AAA, length 3, now arrives at Kannel as AAA@,
> > length 4 [which is obviously wrong]
> >
> > I've made a short term workaround to remove the character by using the
> > octstr_strip_nonalphanums on the msg-sms.msgdata however I'm interested
> > in whether everyone thinks Kannel should strip off this null character
> > (like I do) or whether this should occur at application level?
> >
> > If it's Kannel I'll submit a proper patch
>
> hmm, so someone is not acting spec conform, either Kannel or they?!
>
> 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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.