Web OAM&P
Line 10: | Line 10: | ||
When used with the gateway application it is also possible to: | When used with the gateway application it is also possible to: | ||
− | *Monitor call | + | *Monitor call activity. |
*Configure dial plans. | *Configure dial plans. | ||
Line 23: | Line 23: | ||
'''Web application''' | '''Web application''' | ||
− | The web application is a full working example (also | + | The web application is a full working example (also optional) of how to integrate with the framework’s database: |
− | *Written in Ruby using the Ruby on Rails framework. The framework is easy to learn and use; it simplifies | + | *Written in Ruby using the Ruby on Rails framework. The framework is easy to learn and use; it simplifies traditional web design by a great factor. Since the framework is based on the MVC pattern, it is very easy to add new pages without risking to break the rest of the application. |
*Implements all of the database tables. | *Implements all of the database tables. | ||
*Uses cascading stylesheets extensively to allow for "look and feel" customization. | *Uses cascading stylesheets extensively to allow for "look and feel" customization. | ||
Line 33: | Line 33: | ||
== Usage == | == Usage == | ||
− | Usage depends on the server used to run the web application and the database. In any case there is some configuration | + | Usage depends on the server used to run the web application and the database. In any case there is some configuration that must be modified in the web application. The "database.yml" file must be changed to point to the client’s framework database. Starting the web server (using Webrick or Mongrel) can then be done as follows from the web application’s directory: |
− | that must be modified in the web application. The "database.yml" file must be changed to point to the client’s | + | |
− | framework database. Starting the web | + | |
− | application’s directory: | + | |
ruby script/server | ruby script/server | ||
Line 45: | Line 42: | ||
− | The framework database must be one supported by Ruby On Rails to use the supplied web application. Such a list is | + | The framework database must be one supported by Ruby On Rails to use the supplied web application. Such a list is maintained at [http://wiki.rubyonrails.com/rails/pages/DatabaseDrivers]. |
− | maintained at http://wiki.rubyonrails.com/rails/pages/DatabaseDrivers. | + | |
Revision as of 14:47, 7 May 2009
A tool is provided to configure/monitor the framework. Using this tool it is possible to:
- Manage users.
- Manage configurations.
- Configure/monitor Hardware.
- IP Interfaces.
- TDM Interfaces.
- ISDN stacks.
- SIP service access points.
- Configure network access points.
When used with the gateway application it is also possible to:
- Monitor call activity.
- Configure dial plans.
There are three terms that are often used in the framework when referring to this tool:
- Configuration : An element’s configuration can always be viewed but can only be changed on non active configurations.
- States : An element’s state can only be viewed/changed on active configurations.
- Status : An element’s state can only be viewed on active configurations. It may never be changed.
Database
The web application queries and updates the framework database that acts as an interface to configure the underlying framework. The database is the only required part of the configuring tool. This means clients can build their own configuration GUI as long as it uses the database correctly. For more information see the framework database. Note that the naming convention is one that is used widely and easy to understand. This is also the naming convention used by the Ruby on rails framework.
Web application The web application is a full working example (also optional) of how to integrate with the framework’s database:
- Written in Ruby using the Ruby on Rails framework. The framework is easy to learn and use; it simplifies traditional web design by a great factor. Since the framework is based on the MVC pattern, it is very easy to add new pages without risking to break the rest of the application.
- Implements all of the database tables.
- Uses cascading stylesheets extensively to allow for "look and feel" customization.
- When it makes sense, Ajax is used to provide better responsiveness.
- Supports at least the following browsers: IE, Mozilla, Opera and Safari.
- Can run on the following web servers: Apache, lighttpd, or nginx proxying to Mongrel (or using FastCGI)
Usage
Usage depends on the server used to run the web application and the database. In any case there is some configuration that must be modified in the web application. The "database.yml" file must be changed to point to the client’s framework database. Starting the web server (using Webrick or Mongrel) can then be done as follows from the web application’s directory:
ruby script/server
Caveats
The framework database must be one supported by Ruby On Rails to use the supplied web application. Such a list is maintained at [1].
Return to the Toolpack User Guide