Erorr In Compile PDU

Many Thanks jon,


I have anther querstion about:

How I can decode Sender ID if it like following (it's not hex but it
7bit How I can know that):

07911989414057500414D032584C4683DD7239580C00087011 91406024006006270644063306440627064500200639064406 4A06430645002006480

thank again

alfarok@gmail.com wrote:

> How I can decode Sender ID if it like following (it's not hex
> but it 7bit How I can know that):

It's encoded in exactly the same way as 7-bit text in a User
Data field. In other words, using the packing algorithm from
GSM 03.38, section 6.1.2.1.1. The unpacked septets (7-bit
characters) then get looked up in the table from GSM 03.38,
section 6.2.1.

The Originator Address field from your message is
14D032584C4683DD7239580C. It decodes like this:

14 OA length: 14 hex (20 decimal) semi-octets
D0 OA encoding: alphanumeric (GSM 03.40, 9.1.2.5)
32584C4683DD7239580C OA string "20124079901", as follows:

Numbering the octets of 7-bit data from 1 to 10 gives us this
binary data:

1 32 00110010
2 58 01011000
3 4C 01001100
4 46 01000110
5 83 10000011
6 DD 11011101
7 72 01110010
8 39 00111001
9 58 01011000
10 0C 00001100

The decode goes like this: Numbering the bits in a octet from 1
on the right to 8 on the left, the first septet consists of
octet 1, bits 1 to 7: 0110010, = "2" (from lookup in GSM 03.38,
6.2.1).

The second septet contains octet 2, bits 1 to 6 and octet 1, bit
8: 0110000, "0".

Putting the whole 10 octets (encoding 11 septets) into columns
we get:

septet from octet, bits bit pattern value
1 1, 1-7 0110010 2
2 2, 1-6 & 1, 8 011000 0 0
3 3, 1-5 & 2, 7-8 01100 01 1
4 4, 1-4 & 3, 6-8 0110 010 2
5 5, 1-3 & 4, 5-8 011 0100 4
6 6, 1-2 & 5, 4-8 01 10000 0
7 7, 1 & 6, 3-8 0 110111 7
8 7, 2-8 0111001 9
9 8, 1-7 0111001 9
10 9, 1-6 & 8, 8 011000 0 0
11 10, 1-5 & 9, 7-8 01100 01 1

John

Hi John,

I have 3 different problem
1. I can not get 'normal text' for this message :
06912618010000640B912618819088F200F570211080530082 6C06050423F40000424547494E3A56434152440D0A56455253 494F4E3A322E310D0A5245563A323030373131323554303335 3935325A0D0A4E3A3B4172656B2D5374616E6C65793B3B3B0D 0A54454C3B43454C4C3A30383838313135353333330D0A454E 443A56434152440D0A
another sample message :
07912618485400F9440B912618274067F100F5601002021061 828406050423F40000424547494E3A56434152440D0A564552 53494F4E3A322E310D0A4E3A48656E64726F3B0D0A54454C3B 43454C4C3A2B363539333637333132310D0A4F52473A363320 48756D6520417665202330322D30312048696C6C7669657720 477265656E20436F6E646F202862697320393633290D0A454E 443A56434152440D0A
Can you explain me, how to get the 'normal text' for that PDU
2. I need to get text for Originator Address. The Originator Address
must be TELKOMSEL. How to get that Originator Address text and do you
have any link about the documentation for this.
Message :
07912618018758F30410D0D42273F96C4E8B4C000080404221 91328297D0323BEC3E9FC36E50968E6629EBED301D24ABBD60 B4170C070ABAC96150BBEC26C3E9EBB01B749687E9E9390807 6ABBE920717A1C968741F3F23CDC0E83A865F6FADD9E97D92E 10B42C47A7E975F739EC0685C96110390D0AAFD1693948CC76 83E8E1731A1D76834C207A593E2ED3C36B109C0C92A7DDE374 D80D8297E5E3F03A0C0FBB01
3. When I try to get total parts of message using your explanation, it
gets 53. Actually, In my mobile phone only about 3 or 4 concatenated
message. How to get the right total parts of message ? The message :
06912618010000600C91261892931174000040306102947400 A006080400350201CCB7BD0C4ACF41F0303D5D76D341613719 949E83D66937990562BFED65507A0E72BFE9207539CC7ED7E7 A0B71C247E87E774739DBD03A5E9A0F41CE47ED34161B9FC7D 0EBBE9A0B71C24AF93CB2E970BC47CDBCB2071392C9F83C26C 36888E4EBBCF7316485C66A7CBF6F21C1466B3417474DA7D9E B340E837BC0C0AB3D9203A3AED3ECF59

Thank you,

Best regards,

Martha

msasongko@gmail.com wrote:

> Hi John,
>
> I have 3 different problem
> 1. I can not get 'normal text' for this message :

I'll handle your two messages in your part 1 query seperately.

I seriously doubt that these two messages are meant to be
human-readable. They're 8-bit data, specifically addressed to
a particular "machine" port on the destination handset.

Nevertheless, I have begun the decoding process for the first
message as follows:

06912618010000 SCA

64 PDU-type (hex)
01100100 PDU-type (binary) as follows:
0 reply path (not set)
1 UDHI (UDHI is set - UD has a UDH)
1 SRI (set - delivery acknowlegment requested)
00 spare
1 MMS (no more messages waiting delivery)
00 MTI (SMS type "MT" = SMS deliver = a "received" message)

0B912618819088F2 OA (originator address)

00 PID

F5 DCS (hex)
11110101 DCS (binary) as follows:
1111 data coding/message class
0 spare bit (must be zero)
1 message data is 8-bit
01 ME-specific (for phone, not SIM)

70211080530082 SCTS (1 Dec 07, 08:35:00, GMT + 7 hours)

6C UDL, 6C hex = 108 decimal
06 UDHL, the next 6 octets are UDH (header)
05 application port addressing, 16-bit address
04 information element length (4 octets follow)
23F4 destination port, 9204 decimal -
GSM 03.40 says: "As allocated by IANA (http://www.IANA.com/)"

0000 originator port

42 B (these are all just 8-bit ASCII values)
45 E
47 G
49 I
4E N
3A :
56 8
43 C
41 A
52 R
44 D
0D <carriage return>
0A <line feed>
56 8
45 E
52 R
53 S
49 I
4F O
4E N
3A :
32 2
2E .
31 1

I'll leave the rest of these two messages to you to decode.

John

msasongko@gmail.com wrote:

> 2. I need to get text for Originator Address. The Originator
> Address must be TELKOMSEL. How to get that Originator Address
> text and do you have any link about the documentation for
> this. Message :

OK, the OA (originator address) element for this next message
is:

10D0D42273F96C4E8B4C

10 OA is 10 hex (16 decimal) semi-octets long
D0 type of address (hex)
11010000 type of address (binary) as follows:
1 reserved (must be "1")
101 alphanumeric (7-bit default alphabet)
0000 must be "0000" when leading bits are "1101"

"D42273F96C4E8B4C" carries the encoded OA, which does indeed
decode to "TELKOMSEL".

The decoding of the OA element is covered in GSM 03.40, section
9.1.2.5. This is where the OA length and type-of-address are
covered in detail. Because type-of-address is alphanumeric in
this case (type = "D0"), you must decode it according to GSM
03.38 section 6.1.2.1.1 "Packing of 7-bit characters", and
section 6.2.1 (default alphabet lookup table). You can
download these GSM technical standards from www.etsi.org or
www.3gpp.org and other sources you can find using google.

"D42273F96C4E8B4C" decodes to "TELKOMSEL" using exactly the same
mechanical procedure as "32584C4683DD7239580C" decodes to
"20124079901" in the example I worked for alfarok in a recent
post. In this case, I decoded it using a program.

> 3. When I try to get total parts of message using your
> explanation, it gets 53. Actually, In my mobile phone only
> about 3 or 4 concatenated message. How to get the right total
> parts of message ? The message :

In the next message, the UDHI bit is set within the PDU-type
octet (as is correct for a concatenated message). There's
nothing special about the PID or the UDH (both are "00"). So
I'll go straight to the UDH field, beginning with the UDL:

A0 UDL: A0 hex = 160 decimal septets
06 UDHL, the next 6 octets are UDH (header)
08 concatenated short message using 16-bit numbering
04 information element length (4 octets follow)
0035 16-bit message number, 35 hex (53 decimal)
02 message has 2 parts
01 this is part 1

For the detailed explanation, please see GSM 03.40, sections
9.2.3.24 and 9.2.3.24.8.

John

I wrote:

> 42 B
> 45 E
> 47 G
> 49 I
> 4E N
> 3A :
> 56 8
> 43 C
> 41 A
> 52 R
> 44 D
> 0D <carriage return>
> 0A <line feed>
> 56 8
> 45 E
> 52 R
> 53 S
> 49 I
> 4F O
> 4E N
> 3A :
> 32 2
> 2E .
> 31 1

The two char 56 hex above, which I decoded as "8", should decode
to "V".

According to
http://mobile.act.cmis.csiro.au/comp3410/assignment.asp this
"port 23F4" message is an address book update. The URL has
much good detail on this type of SMS.

John

Hi john

Thanks very much

I'll try and if any prob. I'll back


thanks

OK john,

But is it like D0 always in alphanumeric sender id ?

in (D0 OA encoding: alphanumeric (GSM 03.40, 9.1.2.5) )

alfarok@gmail.com wrote:

> OK john,
>
> But is it like D0 always in alphanumeric sender id ?
>
> in (D0 OA encoding: alphanumeric (GSM 03.40, 9.1.2.5) )

Yes, type-of-address "D0" is always alphanumeric, always using
the 7-bit default alphabet, and always encoded in exactly the
same way as a 7-bit message text.

The other two common type-of-address (hex) values are:

91 international format. Always begins with the country code.
In other words, you understand that the number begins with "+".

81 national format. No country code is present - just a number
within a country.

John

That is good.

Thanks Very Much John ..