Home page logo
/

wireshark logo Wireshark mailing list archives

Descepancy in 7-to-8 bit decoding
From: Ajay Garg <ajaygargnsit () gmail com>
Date: Sun, 12 Jan 2014 11:50:54 +0530

Hi all.

(This might actually serve as a follow-up to
http://www.wireshark.org/lists/wireshark-users/201311/msg00014.html, but
since the issue this time is a bit different, I preferred starting a new
thread, so as not to clutter up things).


We captured some USSD network traces, and found that the following *7-bit
encoded* message was being transferred over the wire :
*c2301b249dbb663617ce056abee56510391d668354b1584c151bb914532a111883c15fcdb43b0422be41d2612d070abbc9a0b25bfdce83a65422681866b3e720fa1b1474e741ce32fdfe96af41c0180cfe6abb40d6201324c391c3f9b90b44350d4141389c9d7701*



Wireshark shows the decoded-message to be


*Bal Rs.36.8. More dial *111*1#.STD¡10p/Min! Do RC59 and enjoy STD Calls to
Any Network ¡10p/m. VAL 28days. T&C Apply.*

while our 7-to-8 bit decoder shows this to be


*Bal Rs.36.8. More dial *111*1#.STD () 10p/Min! Do RC59 and enjoy STD Calls to
Any Network @10p/m. VAL 28days. T&C Apply.*

(Note the difference of "¡" and "@").


The wireshark rpm being used is wireshark-1.6.16-2.fc17.i686


Is this another case of using a special charcater ("*¡*" in the present
case), when some particular byte-stream is received?
Or am I being plain stupid?



We will be grateful for some pointers, that could help clear our doubts !!

Looking forward to a reply




Thanks and Regards,
Ajay
___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
             mailto:wireshark-users-request () wireshark org?subject=unsubscribe

  By Date           By Thread  

Current thread:
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]