Versions Compared

Old Version 7

changes.mady.by.user Former user

Saved on

compared with

New Version 8

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The following library components are used

  • 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 interface, which can be used for bulk configuration transactions.
    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.

 

Architecture of the Media Server

The sipXecs Media Server provides voicemail and auto-attendant services. It is based on VXML using the OpenVXI library.

Image Removed
Legend:

  1. Configuration Server generates configuration files for the Media Server and stores them in the file system of the host on which Media Server runs. These configuration files are read by Media Server when it starts.
  2. On an ongoing basis during operation Configuration Server provides updated information on users, their credentials, routing information etc. into the In-Memory Data Base (IMDB) through a replication interface. The transactions are done using HTTPS through the Apache Web server and using the Replication CGI.
  3. The Replication CGI writes the information to the IMB (we use FastDB).
  4. Information is retrieved from the IMDB by the MediaServer CGI
  5. Configuration Server also provides process control for the media server and its components. A Process CGI is used to communicate with the watchdog that runs on every host that participates in a sipX system.
  6. The sipXvxml RPM includes both the OpenVXI component as well as an interface that allows OpenVXI to communicate with MediaServer CGI using HTTP.
  7. MediaServer also communicates with the Status server using HTTPS for the purpose of exchanging Message Waiting status information (MWI)
  8. OpenVXI communicates with the rest of the system using SIP. Calls are transferred to the Media Server.
  9. OpenVXI generates prompts that can be played by Media Server. These prompts are stored to the file system from where Media Server can retrieve them.
  10. Media Server retrieves stored prompts