Page Comparison

...

• Jetty: Java HTTP Server and Servlet Container
• Spring Framework: Java Application Server Framework
• Tapestry: Apache Jakarta Tapestry
• Hibernate: Idiomatic Persistence for Java
• Velocity: Java based Template Engine
• Lucene*:*Java-based indexing and search A Web browser directly connects to the Jetty HTTP server and the Apache server is no longer required. Web Services integration is possible using the provided SOAP / REST interface, which can be used for bulk configuration transactions.
  

  Note
  Starting with version 4.2 sipXconfig provides a set of REST APIs using RESTlet* library. The plan for next releases is to expose all sipXconfig functionalities in REST calls.

  For persistent storage we use the PostgreSQL database.
  Configuration Server communicates with other sipXecs server components using the file system or its XML RPC interface. Using the local file system, configuration files are written to the /etc/sipxpbx directory.
  Two different mechanisms are supported for phones and gateways to get access to their respective configuration files at boot time: a) Both an FTP and TFTP server provide access to the tftproot directory on the sipXecs server; and b) HTTP Web access is possible to the docroot directory. docroot access is provided on port 8090 using the Apache Web server.
  Phones and gateways can be auto-configured on the LAN, which further simplifies deployment. |