* Write up more tests in /t/
	- Each transport
	- PDU
	- OTA stuff

* Automate configuration when installing (PIN-code, port etc ...)
* Automate the test in /t/ also in function of choosing the config parameters
* Clean up and refine the logging. COnsolidate this in one logfile for the
  complete system
	
	- Log::Agent: Need to investigate

* Try to investigate the possibility to build in a QUEUE ( cache?)

	- Transport Spool would be mandatory ( super class transport )
	- Use Cache::File ??? -> probably Cache::Cache!
	- When system crashes, should be able to pick them up

* MCube support and Clickatel support
* Delivery report support (message status)
	- How to give a message an ID (possible link to caching here)
	- How to communicate the message ID back? Probably need to
          change NBS.pm interface, because a message ID must be brought back
	- Probably Message.pm class that has a ->body, ->status method?
	- SMS-SUBMIT-REPORT, SMS-DELIVER-REPORT PDU types		
	  !! OBJECTIFY PDU.pm !!

* Refactor Transport.pm -> error message needs to be included in which 
  stack fails! 
	- Look at cache and ID ... integrate closer!

* EMS ( Enhanced Message System )
	- Specs
	- Forms possible?