RE: DLR sql select problem with message id containing space

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Fix would be not too hard to implement... BUT...
In the SMPP specs that I have (note: I am talking about v3.3) it says:
Message ID, var max. 9. So taking off the terminating NUL this means that
message ids can be 8 characters at most.
I noticed this 'quirk' (message ids of more than 8 chars) also with a
certain upstream provider that I have.

Question: Has this changed in successive SMPP versions? Or is it just
plainly against specifications?

Regards,

Rene Kluwen
Chimit
  -----Original Message-----
  From: [email protected] [mailto:[email protected]]On Behalf Of
Alex Kinch
  Sent: dinsdag 23 december 2003 18:47
  To: [email protected]
  Subject: DLR sql select problem with message id containing space


  Hi,

  Just hooked up another SMPP connection, and they use rather large message
ids. For example:

  00047274 20031223170148.364

  Kannel is inserting this whole value (including characters after the
space) into the ts field on the dlr table. However, when it comes to
receiving the delivery report, it's truncating the message id after the
first space, so it does:

   DLR[mysql]: Looking for DLR smsc=XXXX, ts=00047274, dst=44xxxxxxxxxx,
type=1

  Which of course it won't find, as it's lost the rest of the message id.

  My C coding skills aren't up to much, but I would imagine it requires
something that tests the first character after the space to see if it's
numeric.

  Alex
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (MingW32)

iD8DBQE/6LKR4zfyqeBw6xURAn/nAKCdrFMWdTRzwNUfFbLMaeDktnV2iACgouSO
BEiaK+FLIIo04QY3lSDl34w=
=aR9U
-----END PGP SIGNATURE-----