Hi, Seems like i am gonna get lost in the binary.
The hex dumps are different BECAUSE kannel is doing 8 bit coding for a as can be seen straight away. nowsms is doing 7 bit coding and here is some explanation Let's try pack "a" into 7 bits - 1100001 and now let's try multiple times 1100 0011 1000 0111 0000 1110 0001 1100 0011 1000 0111 0000 1110 0001 1100 001 3 C 1 E 0 7 8 3 C 1 E 0 7 8 C If you compare the HEX in your Now SMS logs with upper one. you may find some analogy. HINT - Read it reverse byte-wise. I am sorry that i am unable to justify the first C2 with my logic here but some geeks on this list or NOWSMS can explain that for sure. BUT you can compare every SINGLE bit/hex/octet after that. Hope this helps. Navjot Singh PS - You really made me look into 1s and 0s :-) -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Sahil Aggarwal Sent: Saturday, March 27, 2004 6:23 PM To: [EMAIL PROTECTED] Subject: message concatenation Hi all i am trying to send a message containing 161 'a' ,the message split up by kannel into two but i am receiving junk on my mobile, although concatenated 2004-03-22 17:31:43 [5] DEBUG: data: 05 00 03 02 02 01 61 61 ......aa 2004-03-22 17:31:43 [5] DEBUG: data: 61 61 61 61 61 61 61 61 aaaaaaaa 2004-03-22 17:31:43 [5] DEBUG: data: 61 61 61 61 61 61 61 61 aaaaaaaa 2004-03-22 17:31:43 [5] DEBUG: data: 61 61 61 61 61 61 61 61 aaaaaaaa 2004-03-22 17:31:43 [5] DEBUG: data: 61 61 61 61 61 61 61 61 aaaaaaaa 2004-03-22 17:31:43 [5] DEBUG: data: 61 61 61 61 61 61 61 61 aaaaaaaa 2004-03-22 17:31:43 [5] DEBUG: data: 61 61 61 61 61 61 61 61 aaaaaaaa 2004-03-22 17:31:43 [5] DEBUG: data: 61 61 61 61 61 61 61 61 aaaaaaaa 2004-03-22 17:31:43 [5] DEBUG: data: 61 61 61 61 61 61 61 61 aaaaaaaa 2004-03-22 17:31:43 [5] DEBUG: data: 61 61 61 61 61 61 61 61 aaaaaaaa 2004-03-22 17:31:43 [5] DEBUG: data: 61 61 61 61 61 61 61 61 aaaaaaaa 2004-03-22 17:31:43 [5] DEBUG: data: 61 61 61 61 61 61 61 61 aaaaaaaa 2004-03-22 17:31:43 [5] DEBUG: data: 61 61 61 61 61 61 61 61 aaaaaaaa 2004-03-22 17:31:43 [5] DEBUG: data: 61 61 61 61 61 61 61 61 aaaaaaaa 2004-03-22 17:31:43 [5] DEBUG: data: 61 61 61 61 61 61 61 61 aaaaaaaa 2004-03-22 17:31:43 [5] DEBUG: data: 61 61 61 61 61 61 61 61 aaaaaaaa 2004-03-22 17:31:43 [5] DEBUG: data: 61 61 61 61 61 61 61 61 aaaaaaaa 2004-03-22 17:31:43 [5] DEBUG: data: 61 61 61 61 61 61 61 61 aaaaaaaa 2004-03-22 17:31:43 [5] DEBUG: data: 61 61 61 61 61 61 61 61 aaaaaaaa 2004-03-22 17:31:43 [5] DEBUG: data: 61 61 61 61 61 61 61 aaaaaaa 2004-03-22 17:31:43 [5] DEBUG: data: 05 00 03 02 02 02 61 61 ......aa 2004-03-22 17:31:43 [5] DEBUG: data: 61 61 61 61 61 61 aaaaaa i tried the same with nowsms and the log reads as: Binary=1;UDH=050003870201; Data=C2E170381C0E87C3E170381C0E87C3E170381C0E87C3E170381C0E87C3E170381C0E87C3E170381C0E87C3E170381C0E87C3E170381C0E87C3E170381C0E87C3E170381C0E87C3E170381C0E87C3E170381C0E87C3E170381C0E87C3E170381C0E87C3E170381C0E87C3E170381C0E87C3E170381C0E87C3E170381C0E87C3E170381C0E87C3 Binary=1;UDH=050003870202; Data=C2E170381C0E8701 if both are hex dumps why are the two dumps different? concatenated message sent from nowsms is received properly, but its junk in case of kannel i have added concatenation=true max-messages=3 is thr something am i missing? -Regards Sahil Aggarwal
