Ok it is broke
something.
But I disagree with
you about “SMPP standard clearly
states that short_message may not be longer then 160
characters”.
I have SMPP 3.4
specification. And in SUBMIT_SM, it is mention that short_message is up to 254
octet. It means, we can send SM more than 160 via SMPP 3.4.
I can send you this
document (1,5 Mbytes) if you will
Regards,
-dedy-
-----Original
Message-----
From: Oded Arbel
[mailto:[EMAIL PROTECTED]]
Sent: Tuesday, September
17, 2002 4:51
PM
To: Dedy Sutanto;
[EMAIL PROTECTED]
Subject: RE: Concatenation Problem in
SMPP
If
you've changed the behaviour of smsbox to solve a driver specific issue,
in a non portable way - they heck yes : you broke something. your smsbox
will probably not work with any other driver. nor with any other SMPP server
except the comverse one, as IIRC the SMPP standard clearly states that
short_message may not be longer then 160 characters.
You're
using a non compliant SMPP server, even if non-compliant in a good way,
meaning - handles non-compliant clients. your "messages are received
binary" is probably related to improer DCS setting.
+972-9-9581711
(116)
+972-67-340014
::..
In /dev/null
no one can hear you scream
-----Original
Message-----
From: Dedy
Sutanto [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, September
17, 2002 11:04
AM
To: [EMAIL PROTECTED]
Cc: Oded Arbel
Subject: RE: Concatenation Problem in
SMPP
The
problem is, when I send plain SMS (7-bit) with length more than 160 (240)
and smsbox split it and add UDHI, SMSC send me 2 binary messages. I thought,
it because the UDH.
Then I
did a dirty hack in smsbox.c. I change value MAX_SMS_OCTETS from 140 to
1600.
And
try sending other plain SMS more than 160. It’s work!
I test
for logo and ringtones which more than 160 characters. And it’s work
too.
I
don’t know if my dirty hack will broke something or not.
I
don’t know either if MMS implementation in my SMSC differs. (I use Comverse
SMSC)
It
seem, SMSC done the concatenation.
Regards
-dedy-