Thursday, November 10, 2011
Telnet on Windows Vista
On Start menu, click on "Run..." option, then write "optionalfeatures" (without quotes) and click OK button.
"Windows Features" window will open so you can enable Telnet Client feature. Click OK and wait some minutes (MANY MINUTES in my case) while the features are been enabled.
When it is finished you have to restart the system before having fun with Telnet Client.
Tuesday, November 1, 2011
How to find UtcTimeOffsetCode table in TAP3 files
One of the information in Moc (Mobile Originated Calls) and Mtc (Mobile Terminated Calls) is Call Event Start Time Stamp.
It is formed by Local Time Stamp (yyyyMMddhhmmss) plus Utc Time Offset Code.
Utc Time Offset Code (5F-81-68) can be any integer from 0 to 99 and with this information you will be able to discover the Utc Time Offset (5F-81-67).
The problem is this information is not standardized for all TAP files, it is an information self-contained in TAP3 file, in another section. In other words, each file has its own Utc Time Offset Code list, mapping codes to real offsets.
This table is named Utc Time Offset Info and is located in Network Information section. Utc Time Offset Info can have one or more Utc Time Offset Definition and each Definition has the mapping between Utc Time Offset Code to Utc Time Offset.
In the example shown in pictures above, the offset code 65 (0x41) was linked to Utc Time Offset -05:00.
TAP3 protocol was designed this way to minimize the amount of data transferred and to avoid the repetition of
frequently identical information at the call/event level.
Tip:
Nice programs to work with TAP3 files:
TAP3 Editor (http://www.combil.com/tap3ed2.htm): Used to see structured information
ASN1VE (http://www.obj-sys.com/asn1-viewer.php): Used to see binary content of ASN.1 data
It is formed by Local Time Stamp (yyyyMMddhhmmss) plus Utc Time Offset Code.
Utc Time Offset Code (5F-81-68) can be any integer from 0 to 99 and with this information you will be able to discover the Utc Time Offset (5F-81-67).
The problem is this information is not standardized for all TAP files, it is an information self-contained in TAP3 file, in another section. In other words, each file has its own Utc Time Offset Code list, mapping codes to real offsets.
This table is named Utc Time Offset Info and is located in Network Information section. Utc Time Offset Info can have one or more Utc Time Offset Definition and each Definition has the mapping between Utc Time Offset Code to Utc Time Offset.
In the example shown in pictures above, the offset code 65 (0x41) was linked to Utc Time Offset -05:00.
TAP3 protocol was designed this way to minimize the amount of data transferred and to avoid the repetition of
frequently identical information at the call/event level.
Tip:
Nice programs to work with TAP3 files:
TAP3 Editor (http://www.combil.com/tap3ed2.htm): Used to see structured information
ASN1VE (http://www.obj-sys.com/asn1-viewer.php): Used to see binary content of ASN.1 data
Subscribe to:
Posts (Atom)