GNU Gatekeeper Logo

Home
· Download
· Support
· Site Map

Documentation
· English Manual
· French Manual
· Spanish Manual
· Persian Manual
· Portuguese Manual
· Chinese Manual
· FAQ
· Interoperability
· Intro to H.323
· Usage Examples
· Configuration Notes
· GnuGk and SIP

Tools & Addons
· Java GUI
· ISDN Gateway
· CTI / ACD
· GnuGk Addons
· Endpoints
· Gateways
· MCUs
· IVRs
· Billing
· Commercial Addons

Development
· Compiling
· Development Version
· NAT Traversal
· Tools
· Authors

Misc
· Events
· Logos
· Recommended Books
· Success Stories

Ideas for new features

This list is a list of requested features from the user surveys. It is meant as food for thought which features to add to GnuGk in the near future.

  • H.460.18 + H.460.19 support (firewall/NAT) implemented in 2.3.0 (for endpoints)
  • codec filtering (disallow certain codecs) implemented in 2.3.0
  • gatekeeper-to-gatekeeper H.460.18 ("traversal-zones")
  • SNMP agent to monitor GnuGk
  • encryption for the status port connection (ssh)
  • better bandwidth management
  • ability to limit the total capacity per gateway (in + out)
  • listen to multiple ports to avoid VoIP blockage or ALGs
  • database drivers as loadable modules
  • store registrations in a database (for redundancy)
  • store call table in a database: a stateless gatekeeper could use IP load balancing
  • native Oracle database driver (not using ODBC)
  • better statistics about call quality
  • extend the ACD and add a user interface
  • LDAP authentication
  • extend call failover to all routing policies (neighbors, vqueue etc.)
  • performance optimization (more concurrent calls per server)
  • implement lawful interception (signaling and/or media)
  • extend SQLBill for rate matching by alias (not gateway IP)
  • better ANI checking
  • set multiple failover routes via virtual queue
  • set proxy mode via virtual queue
  • rewriting / routing simulation to test the configuration
  • regex support when rewriting destinations
  • routing policy based on codec
  • a better GUI (maybe in ASP.Net)
  • user defined event handlers, maybe Perl API
  • QoS marking
  • IPv6 support
  • implement a CPL routing policy based on RFC 3880 (Call Processing Language)
  • ability to use different H.245 tunneling setting per endpoint (not just for the whole call)

If you want to help implement or sponsor a feature, please contact me.



Last updated: 04. Jan 2010
Page maintained by Jan Willamowius