MHealth is currently in beta. There are a number of issues and enhancements 
we are currently working on which are listed below.

If you find or come up with any additional problems, bugs, 
or suggestions, please contact us at davidm@cs.ucsb.edu or 
almeroth@cs.ucsb.edu and we will be glad to address it.

- Scalability of the data: because of the bounded nature of RTCP reports
  and the time it takes to do an mtrace, as multicast groups grow the 
  courseness of our data also increases. We are looking at ways to reduce
  this.
- Scalability of the GUI: as the multicast group becomes large the GUI
  becomes cumbersome. You cannot see the entire tree at one time, and it
  is difficult to scroll. We are investigating ways to zoom in and out 
  so the entire tree can be drawn on one screen even when it is very large.
- Tree drawing errors: when routes change radically, a node is both a
  router and a receiver, and similar situations, the tree drawing can
  draw connecting lines through unrelated nodes. Leaf grouping is less
  than ideal and is based on the order the nodes are placed in the tree rather
  than their location in the tree.
- Handling multiple sources: MHealth currently chooses the first source it
  hears from as the root. Additional sources are listed but cannot be 
  made root. We will be adding the ability to swap any of the sources into
  the root of the tree by selecting it.
- Flexibility of the data logging: currently the data logging for the
  RTCP packets is only the data we were most interested in. We intend to
  allow the user to customize which data elements of the RTCP packet they
  are interested in logging.
- Behavior of mtraces: we plan to add the ability to specify mtrace behavior 
  at high level (to concentrate on unplaced receivers or distribute evenly). 
- Cross-platform issues: In order to make MHealth truly cross-platform,
  mtrace can be rewritten in Java.
- Batch logging: a "no-GUI" mode which does only logging.
- Additional sources of information: SNMP, etc...