Hi Thanasis,

I'm sorry, the PDU I gave to you is truncated, here is the completed one
that I try with ParserTester.java:

        String
currentLine="06911111010000040D91111182688311F10004904051018253828C2670140D000201000111781092FF636FB80B0834100011781099FF636FBE0B08340000117810A4FF636FC00B0833F000117810AAFF636FC60B0833F000117810B2FF636FC60B08340000117810B8FF636FC60B08340000117810C4FF636FC40B08341000117810CAFF636FC90B08341000117810D0FF636FCC0B08342000117810D7FF636FC60B0834100000";
        PduParser parser = new PduParser();
        Pdu pdu = parser.parsePdu(currentLine);
        System.out.println(pdu);


The output is correct:

SMSC Address: [Length: 6 (06) octets, Type: 91 (10010001), Address:
1111100000]
First Octet: 04 [TP-MTI: (SMS-DELIVER), TP-MMS: (Has more messages), TP-SRI:
(No Status Report), TP-UDHI: (no UDH)]
Originator Address: [Length: 13 (0D), Type: 81 (10000001), Address:
1111288638111]
TP-PID: 00 (00000000)
TP-DCS: 04 (8-bit encoding) (00000100)
TP-SCTS: Wed Apr 15 10:28:35 WIT 2009

User Data Length: 140 (8C) octets
User Data (pdu) :
2670140D000201000111781092FF636FB80B0834100011781099FF636FBE0B08340000117810A4FF636FC00B0833F000117810AAFF636FC60B0833F000117810B2FF636FC60B08340000117810B8FF636FC60B08340000117810C4FF636FC40B08341000117810CAFF636FC90B08341000117810D0FF636FCC0B08342000117810D7FF636FC60B0834100000


User data (dump of binary) is correct, but when I run SMSServer, the result
is different on database. Here:

267014d02101117810ffffff92ffffffff636fffffffb8b834100117810ffffff99ffffffff636fffffffbeb83400117810ffffffa4ffffffff636fffffffc0b833fffffff00117810ffffffaaffffffff636fffffffc6b833fffffff00117810ffffffb2ffffffff636fffffffc6b83400117810ffffffb8ffffffff636fffffffc6b83400117810ffffffc4ffffffff636fffffffc4b834100117810ffffffcaffffffff636fffffffc9b834100117810ffffffd0ffffffff636fffffffccb834200117810ffffffd7ffffffff636fffffffc6b8341000


Regards,

Aryo Sanjaya



On Fri, Apr 17, 2009 at 21:07, Aryo Sanjaya <[email protected]> wrote:

> Thanasis,
>
> Yes, that is a binary message, 8bit. But it's an inbound message, not to be
> send.
> Here is the PDU:
>
> 0691xx1x010000040D91xx1x826883xxFx0004904051018253828C2670140D000201000111781092FF636FB80B0834100011781099FF636FBE0B08340000117810A4FF636FC00B0833F000117810AAFF636FC60B0833F000117810B2FF636FC60B08340000
>
> I mark the number for some reasons.
> Could you please help to decode the PDU, and dump the binary message into
> hexa string.
>
> Thank you.
>
>
> Aryo Sanjaya
> http://facebook.aryosanjaya.net
>
>
>
> On Fri, Apr 17, 2009 at 19:11, Thanasis <[email protected]> wrote:
>
>>
>> Aryo,
>>
>> What is the original message that you are trying to send?
>> Is it a binary one?
>>
>> On Apr 17, 2:29 pm, Aryo Sanjaya <[email protected]> wrote:
>> > I try that step, but still not fixing my problem. Seems there is too
>> many
>> > 0xff of the binary dump result.
>> >
>> > The correct one should be like this:
>> >
>> 2670025D000201000211429312FF6CBD6F0AF566100011429317FF6CBD6F0AF566100011429­31AFF6CBD6F0AF56610001142931DFF6CBD6D0AF566100011429328FF6CBD690AF566100011­42932CFF6CBD690AF566100011429333FF6CBD660AF566100011429336FF6CBD690AF566100­011429339FF6CBD690AF56610001142933CFF6CBD6F0AF566100000
>> >
>> > But SMSLib result is:
>> >
>> 267014b021011178d36ffffffff636fffffffc4b833ffffffd001178effffffa2ffffffff63­6fffffffafb8343001178fffffffffffffffff636fffffffa6b8342001178105ffffffff636­fffffffa9b834200117810cffffffff636fffffffacb83420011781012ffffffff636ffffff­fafb83420011781018ffffffff636fffffffb2b83430011781021ffffffff636fffffffb2b8­3430011781027ffffffff636fffffffb2b8343001178102dffffffff636fffffffb5b834300­0
>> >
>> > Hope someone can give the clue. Thanks.
>> >
>>
>
>
>
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"SMSLib User Group" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/SMSLib?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to