mi_json Module

Stephane Alnet

   <stephane@shimaore.net>

Edited by

Stephane Alnet

   Copyright © 2013 shimaore.net
   Revision History
   Revision $Rev$ $Date$
     __________________________________________________________

   Table of Contents

   1. Admin Guide

        1.1. Overview
        1.2. Dependencies

              1.2.1. External Libraries or Applications
              1.2.2. OpenSIPS Modules

        1.3. Exported Parameters

              1.3.1. mi_json_root(string)
              1.3.2. trace_destination (string)
              1.3.3. trace_bwlist (string)

        1.4. Exported Functions
        1.5. Known issues
        1.6. Examples

   List of Examples

   1.1. Set mi_json_root parameter
   1.2. Set trace_destination parameter
   1.3. Set trace_destination parameter
   1.4. JSON request
   1.5. JSON request

Chapter 1. Admin Guide

1.1. Overview

   This module implements a JSON server that handles GET requests
   and generates JSON responses.

1.2. Dependencies

1.2.1. External Libraries or Applications

   None

1.2.2. OpenSIPS Modules

   The following modules must be loaded before this module:
     * httpd module.

1.3. Exported Parameters

1.3.1. mi_json_root(string)

   Specifies the root path for JSON requests:
   http://[opensips_IP]:[opensips_httpd_port]/[mi_json_root]

   The default value is "json".

   Example 1.1. Set mi_json_root parameter
...
modparam("mi_json", "mi_json_root", "opensips_mi_json")
...

1.3.2. trace_destination (string)

   Trace destination as defined in the tracing module. Currently
   the only tracing module is proto_hep. This is where traced mi
   messages will go.

   WARNING: A tracing module must be loaded in order for this
   parameter to work. (for example proto_hep).

   Default value is none(not defined).

   Example 1.2. Set trace_destination parameter
...
modparam("proto_hep", "trace_destination", "[hep_dest]10.0.0.2;transport
=tcp;version=3")

modparam("mi_json", "trace_destination", "hep_dest")
...

1.3.3. trace_bwlist (string)

   Filter traced mi commands based on a blacklist or a whitelist.
   trace_destination must be defined for this parameter to have
   any purpose. Whitelists can be defined using 'w' or 'W',
   blacklists using 'b' or 'B'. The type is separate by the actual
   blacklist by ':'. The mi commands in the list must be separated
   by ','.

   Defining a blacklists means all the commands that are not
   blacklisted will be traced. Defining a whitelist means all the
   commands that are not whitelisted will not be traced. WARNING:
   One can't define both a whitelist and a blacklist. Only one of
   them is allowed. Defining the parameter a second time will just
   overwrite the first one.

   WARNING: A tracing module must be loaded in order for this
   parameter to work. (for example proto_hep).

   Default value is none(not defined).

   Example 1.3. Set trace_destination parameter
...
## blacklist ps and which mi commands
## all the other commands shall be traced
modparam("mi_json", "trace_bwlist", "b: ps, which")
...
## allow only sip_trace mi command
## all the other commands will not be traced
modparam("mi_json", "trace_bwlist", "w: sip_trace")
...

1.4. Exported Functions

   No function exported to be used from configuration file.

1.5. Known issues

   Commands with large responses (like ul_dump) will fail if the
   configured size of the httpd buffer is to small (or if there
   isn't enough pkg memory configured).

   Future realeases of the httpd and mi_json modules will address
   this issue.

1.6. Examples

   This is an example showing the JSON format for the
   “get_statistics net: uri:” MI command. Notice how the
   parameters are comma-separated then URI-encoded.

   Example 1.4. JSON request

GET /json/get_statistics?params=net%3A%2Curi%3A HTTP/1.1
Accept: application/json
Host: example.net

HTTP/1.1 200 OK
Content-Length: 49
Content-Type: application/json
Date: Fri, 01 Nov 2013 12:00:00 GMT

["net:waiting_udp = 0", "net:waiting_tcp = 0", "uri:positive checks = 0"
, "uri:negative_checks = 0"]


   Here is another example showing the JSON format for the “ps” MI
   command.

   Example 1.5. JSON request

GET /json/ps HTTP/1.1
Accept: application/json
Host: example.net

HTTP/1.1 200 OK
Content-Length: 428
Content-Type: application/json
Date: Fri, 01 Nov 2013 12:00:00 GMT

[{"name":"Process", "value":null, "attributes":{"ID": "0", "PID": "7400"
, "Type": "stand-alone SIP receiver udp:127.0.0.1:5060"}}, {"name":"Proc
ess", "value":null, "attributes":{"ID": "1", "PID": "7402", "Type": "HTT
PD INADDR_ANY:8888"}}, {"name":"Process", "value":null, "attributes":{"I
D": "2", "PID": "7403", "Type": "time_keeper"}}, {"name":"Process", "val
ue":null, "attributes":{"ID": "3", "PID": "7404", "Type": "timer"}}]
