Northbound interface: Difference between revisions
(Updated link to make it clearer) |
|||
| Line 22: | Line 22: | ||
HTTP requests are sent to the [[Toolpack_Application:web_server|web server]] using standard HTTP methods(e.g., GET, PUT, POST, or DELETE). Data exchanged in requests and responses is in [http://en.wikipedia.org/wiki/JSON JSON] format. | HTTP requests are sent to the [[Toolpack_Application:web_server|web server]] using standard HTTP methods(e.g., GET, PUT, POST, or DELETE). Data exchanged in requests and responses is in [http://en.wikipedia.org/wiki/JSON JSON] format. | ||
More information [[Northbound_interface:RESTful|here]] | More information on the TelcoBridges implementation of the [[Northbound_interface:RESTful|RESTful API here]] | ||
== Dictionary == | == Dictionary == | ||
Revision as of 11:03, 15 January 2020
The Northbound interface allows a higher-level component to configure. This is particularly useful for deployment of large number of units in the field.
TelcoBridges and Northbound interface
Starting with v2.9, EMS or the tbconfig tool can now configure the Tmedia through its Northbound interface.
Configuration
The Northbound interface offers multiple ways to configure your system:
tbconfig
The tbconfig tools allows user to directly modify your system's configuration through multiple modes:
- cli
- shell
- command line
More information about tbconfig here
Integration with EMS
Introduced in version 2.9, the RESTful API allows the provisioning of a Tmedia VoIP gateway or a Tdev development platform. The configuration of the device is seen as collections of resources than can be queried/modified through this interface.
HTTP requests are sent to the web server using standard HTTP methods(e.g., GET, PUT, POST, or DELETE). Data exchanged in requests and responses is in JSON format.
More information on the TelcoBridges implementation of the RESTful API here