Hafidz Zulkifli

The below article was taken from Hot Billing Concept by Advanced Multimedia System Design . Prehistory Darwin teaches us that far ancestors of billing systems were simple log files, or record books. All they could do automatically was regular information storage, " The client dialed in at 19:00 and disconnected at 21:00 "; information retrieval was a less trivial procedure. When computers left the developers' pools and migrated to the commercial land, logs had to be taught to detect account overdraft automatically, not at the end of the month. Billing systems of the newer generation were reptile guardians, timing a given delay, " This is the first day of the rest of your life! ", and biting the connection off when the session timed out. But the evolution went on. Cold-blooded billing systems could prevent a single-user debit account with a constant dollars-per-minute rate from overdraft; they failed if faced a herd of users exploiting a single shared...

One of the most helpful webpages when it comes to how-to in using the sort command. Click me! (ok, so it wasn't a lot. but it does lead you to a good direction doesn't it.)

I've had this problem (ok,..so I usually write a how-to when I got a problem to fix) whereby my recently acquired laptop (my last one was stolen..#uck#n thieves..) was not able to play any movies at all. Talk about NOT being able to play movies on your laptop! Such blasphemy! Ok, so I know that you're not even suppose to go around and watch a movie using your company's property, but I mean come on..who does'nt? Anywho, after months of surviving without my own able-to-watch-laptop (I've been using my wife's since then :P ), recently I found this comments which attributed my problem to a DirectDraw problem. Full coverage of that thread here : System freezes when trying to play ANY movie So after disabling the hardware accelaration on my laptop - I could play them movies again! Yippee! Time to watch some episodes of the X-Men cartoon (the one that usually airs at 7pm back then) that I've been downloading.

Below is a picture depicting the SS7 architecture. With SS7, a packet data network overlays and controls the operation of the underlying voice networks, signaling information is carried on an entirely different path than voice and data traffic. Signaling in essence does not take a lot of time, hence it is possible to multiplex many signaling messages over one channel - and that's why the signaling system is a packet network. SS7 entire architecture performs out-of-band signaling (in which conversation and signaling take over different paths). It (the architecture) defines the procedure for the setup, ongoing management, and clearing of a call, and it enables the passing along of customer-related information that helps in routing calls. The key components of SS7 are: 1. SSP:Service-switching points Them switches that originate and terminate calls. It serves as the source and destination point for the SS7 messages 2. STP: Signal transfer point Responsible for translatin...

Several useful commands. Basic Retrieval from single table SELECT [DISTINCT] display_fields FROM tables WHERE field_conditions ORDER BY field_name [ASC | DESC]; e.g: select * from MethodParameter; e.g: select * from MethodParameter where NAME=DUNHAM; Delete the whole content of table DROP TABLE tablename ; e.g: drop table MethodParameter; Delete one or more records from a table DELETE FROM table_name WHERE record_retrieval_conditions ; e.g: delete from MethodParameter where NAME='DUNHAM BUSH';

Should you ever see these types of message, there are several 'must-know' unix commands that can be used in order to start investigating. 1. du | sort -n : lists all file usage from smallest to largest. 2. df -k -b : see how much allocation is used in the directory. For more help, go to links below:- 1. An IT-admin guide to clearing up disk space 2. df unix command definitions and usage 3. du unix command definitions and usage

From http://www.ncl.ac.uk/iss/unix/unixhelp/kill.html and http://www.decf.berkeley.edu/help/unix/kill.html If you are logged in to a Unix system and your session "hangs" or "freezes" (i.e. nothing happens for a long time and it does not respond to Ctrl/Q Ctrl/C or Ctrl/D), you can attempt to unfreeze it yourself by "killing" the process which has stopped your session. You can also use Ctrl/Z to get out of a process in UNIX. Login to the system where your session is frozen Type the command: w usid where usid is your own username. This will produce a line of output for each login something like this: 9:53am up 82 day(s), 15:58, 132 users, load average: 6.50, 6.25, 5.70 User tty login@ idle JCPU PCPU what nabc pts/160 9:12am -csh nabc pts/166 9:53am w nabc Note the contents of the tty column for the frozen login -- in this example attached to pts/...