GNU Gatekeeper Logo

Home
· Download
· Support
· Success Stories
· Imprint

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
· NAT Traversal
· Tools
· Authors

Misc
· Events
· Logos
· Recommended Books
· Site Map

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 future.
Please contact me, if you want to help implement or sponsor one of these items or have other ideas to add to this list.

  • better statistics about call quality (is in 2.3.5)
  • encryption for the status port connection (ssh) (is in 2.3.5)
  • LDAP authentication (is in 2.3.5)
  • IPv6 support (with IPv6-to-IPv4 interop) (is in 3.0)
  • gatekeeper-to-gatekeeper H.460.18 ("traversal-zones") (is in 3.0)
  • LDAP routing (eg. query an ActiveDirectory server where to route a call)
  • SNMP agent to monitor GnuGk (there is already a simple agent)
  • better bandwidth management: group endpoints, extend to unregistered endpoints
  • QoS marking (configurable DiffServ or TOS values)
  • ability to limit the total number of calls per gateway (in + out)
  • store call table in a database: a stateless gatekeeper could use IP load balancing
  • native Oracle database driver (without using ODBC)
  • extend the ACD and add a user interface
  • extend call failover to all routing policies (neighbors, vqueue etc.)
  • performance optimization (more concurrent calls per server)
  • extend SQLBill for rate matching by alias (not gateway IP)
  • improve BMV (web interface for SQLBill), extend to add clients/routes
  • better ANI checking and rewriting
  • set multiple failover routes via virtual queue
  • set proxy mode via virtual queue
  • rewriting / routing simulation to test the configurations
  • regex support when rewriting destinations
  • a better GUI (maybe in ASP.Net)
  • implement a CPL routing policy based on RFC 3880 (Call Processing Language)
  • ability to use different H.245 tunneling setting per call-leg (not just for the whole call)
  • support CAC (call access control) and RSVP
  • plugins to access number portability databases
  • ability to prioritize routing search patterns by type and by neighbor
  • make status port events configurable (like CDR strings) to specify which data fields to include
  • more flexible CLI rewriting
  • support multiple SQL queries (eg. by prefix) for all SQL modules

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



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