Then in smpp_pdu_unpack we check for these. It wont allways work, it
will depend on which other optional params are used by the SMSC. We
almost need an array type in the def file to handle this properly.
we have an SMPP v3.4 optional parameter patch running on our side
here.
As soon as I roll
On Dienstag, Oktober 22, 2002, at 09:53 Uhr, Stipe Tolj wrote:
Then in smpp_pdu_unpack we check for these. It wont allways work, it
will depend on which other optional params are used by the SMSC. We
almost need an array type in the def file to handle this properly.
we have an SMPP v3.4
-Original Message-
From: Andreas Fink [mailto:andreas;fink.org]
While we are at SMPP, in the SMPP code it does a gsm_to_latin1
conversion.
This breaks Unicode SMS coming in and a unicode test message shows up
as @T@E@S@T instead as of nullTnullEnullSnullT.
Now whats the
Hi
At 09:23 AM 10/21/02 +0200, Andreas Fink wrote:
yup - this is smpp 3.4. Your dump shows an optional parameter tag 04 24
which is the msg_payload parameter.
We have a hack where I have added the following into
smpp_pdu.def
OPT_INTEGER(id_1, 2)
OPT_INTEGER(len_1,2)
OPT_OCTETS(data_1, len_1)
