ソースを参照

xhttp_rpc: added notes about how to use the module

Daniel-Constantin Mierla 9 年 前
コミット
68cbac03d9
2 ファイル変更33 行追加4 行削除
  1. 18 4
      modules/xhttp_rpc/README
  2. 15 0
      modules/xhttp_rpc/doc/xhttp_rpc_admin.xml

+ 18 - 4
modules/xhttp_rpc/README

@@ -10,13 +10,11 @@ Ovidiu Sas
 
    <[email protected]>
 
-Edited by
-
 Alex Balashov
 
    <[email protected]>
 
-   Copyright © 2011 VoIPEmbedded Inc.
+   Copyright © 2011 VoIPEmbedded Inc.
      __________________________________________________________________
 
    Table of Contents
@@ -41,6 +39,8 @@ Alex Balashov
 
               4.1. dispatch_xhttp_rpc()
 
+        5. Usage
+
    List of Examples
 
    1.1. Set xhttp_rpc_root parameter
@@ -69,6 +69,8 @@ Chapter 1. Admin Guide
 
         4.1. dispatch_xhttp_rpc()
 
+   5. Usage
+
 1. Overview
 
    1.1. Limitations
@@ -145,7 +147,7 @@ modparam("xhttp", "xhttp_rpc_buf_size", 1024)
 
    4.1. dispatch_xhttp_rpc()
 
-4.1.  dispatch_xhttp_rpc()
+4.1. dispatch_xhttp_rpc()
 
    Handle the HTTP request and generate a response.
 
@@ -168,3 +170,15 @@ event_route[xhttp:request] {
                         "<html><body>Wrong URL $hu</body></html>");
 }
 ...
+
+5. Usage
+
+   The module is not intended to be used in a "scripted" mode with command
+   line tools. It only provides a simple web interface with all the
+   available RPC commands. Point a web browser to
+   http://serverip:port/http_rpc and browse through the available rpc
+   commands.
+
+   If you don't configure a dedicated port for HTTP, then you have to use
+   same port as for SIP TCP. If you load and configure TLS module, then
+   you can browse using HTTPS to the SIP TLS port.

+ 15 - 0
modules/xhttp_rpc/doc/xhttp_rpc_admin.xml

@@ -166,5 +166,20 @@ event_route[xhttp:request] {
 	    </example>
 	</section>
 	</section>
+	<section>
+	<title>Usage</title>
+	    <para>
+		The module is not intended to be used in a "scripted" mode with
+		command line tools.
+		It only provides a simple web interface with all the available
+		RPC commands. Point a web browser to http://serverip:port/http_rpc
+		and browse through the available rpc commands.
+		</para>
+		<para>
+		If you don't configure a dedicated port for HTTP, then you have
+		to use same port as for SIP TCP. If you load and configure TLS
+		module, then you can browse using HTTPS to the SIP TLS port.
+		</para>
+	</section>
 </chapter>