diff --git a/src/modules/tm/doc/event_routes.xml b/src/modules/tm/doc/event_routes.xml
index 5742edee492..f52f04fe9ce 100644
--- a/src/modules/tm/doc/event_routes.xml
+++ b/src/modules/tm/doc/event_routes.xml
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" 
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
    "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
 
 <section id="tm.event_routes" xmlns:xi="http://www.w3.org/2001/XInclude">
@@ -13,18 +13,21 @@
 	    <function moreinfo="none">event_route[tm:branch-failure]</function>
 	</title>
 	<para>
-	    Named branch failure routes can be defined to run when when a failure response is received.
-            This allows handling failures on individual branches, for example, retrying an alternative outbound flow.
+		Named branch failure routes can be defined to run when when a failure
+		response is received. This allows handling failures on individual
+		branches, for example, retrying an alternative outbound flow.
 	</para>
         <para>
-	    The format of the event_route name is "tm:branch-failure:&lt;name&gt;" and is enabled with the t_on_branch_failure function.
+			The format of the event_route name is "tm:branch-failure:&lt;name&gt;"
+			and is enabled with the t_on_branch_failure function.
             This event_route uses the BRANCH_FAILURE_ROUTE route type.
         </para>
 	<example>
 	    <title><function>event_route[tm:branch-failure]</function> usage</title>
 	    <programlisting>
 ...
-route {
+request_route {
+    ...
     t_on_branch_failure("myroute");
     t_relay();
 }
diff --git a/src/modules/tm/doc/rpc.xml b/src/modules/tm/doc/rpc.xml
new file mode 100644
index 00000000000..a846e1a67e3
--- /dev/null
+++ b/src/modules/tm/doc/rpc.xml
@@ -0,0 +1,166 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+   "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+
+<section id="tm.rpcs" xmlns:xi="http://www.w3.org/2001/XInclude">
+    <sectioninfo>
+    </sectioninfo>
+	<title>RPC Commands</title>
+
+	<section id="tm.rpc.t_uac_start">
+		<title>
+		<function moreinfo="none">tm.t_uac_start</function>
+		</title>
+		<para>
+		Generates and sends a local SIP request.
+		</para>
+		<para>Parameters: </para>
+		<itemizedlist>
+			<listitem><para>
+				<emphasis>method</emphasis> - request method
+			</para></listitem>
+			<listitem><para>
+				<emphasis>RURI</emphasis> - request SIP URI
+			</para></listitem>
+			<listitem><para>
+				<emphasis>NEXT HOP</emphasis> - next hop SIP URI (OBP);
+				use <quote>.</quote> if no value.
+			</para></listitem>
+			<listitem><para>
+				<emphasis>socket</emphasis> - local socket to be used for
+				sending the request; use <quote>.</quote> if no value.
+			</para></listitem>
+			<listitem><para>
+				<emphasis>headers</emphasis> - set of additional headers to
+				be added to the request; at least
+				<quote>From</quote> and <quote>To</quote> headers must be
+				provided)
+			</para></listitem>
+			<listitem><para>
+				<emphasis>body</emphasis> - (optional, may not be present)
+				request body (if present, requires the
+				<quote>Content-Type</quote> and <quote>Content-length</quote>
+				headers)
+			</para></listitem>
+		</itemizedlist>
+	</section>
+
+	<section id="tm.rpc.t_uac_wait">
+		<title>
+		<function moreinfo="none">tm.t_uac_wait</function>
+		</title>
+		<para>
+		Similar to rm.t_uac_start, but waits for the SIP reponse and tries to
+		provide its details via RPC response.
+		</para>
+	</section>
+
+	<section id="tm.rpc.cancel">
+		<title>
+		<function moreinfo="none">tm.cancel</function>
+		</title>
+		<para>
+		Generates and sends a CANCEL for an existing local SIP request.
+		</para>
+		<para>Parameters: </para>
+		<itemizedlist>
+			<listitem><para>
+				<emphasis>callid</emphasis> - callid of the INVITE request
+				to be cancelled.
+			</para></listitem>
+			<listitem><para>
+				<emphasis>cseq</emphasis> - cseq of the INVITE request to be
+				cancelled.
+			</para></listitem>
+		</itemizedlist>
+	</section>
+
+	<section id="tm.rpc.hash_stats">
+		<title>
+		<function moreinfo="none">tm.hash_stats</function>
+		</title>
+		<para>
+		Gets information about the load of TM internal hash table.
+		</para>
+		<para>Parameters: </para>
+		<itemizedlist>
+			<listitem><para>
+				<emphasis>none</emphasis>
+			</para></listitem>
+		</itemizedlist>
+	</section>
+
+	<section id="tm.rpc.reply">
+		<title>
+		<function moreinfo="none">tm.reply</function>
+		</title>
+		<para>
+		Generates and sends a reply for an existing inbound SIP transaction.
+		</para>
+		<para>Parameters: </para>
+		<itemizedlist>
+			<listitem><para>
+				<emphasis>code</emphasis> - reply code
+			</para></listitem>
+			<listitem><para>
+				<emphasis>reason</emphasis> - reason phrase.
+			</para></listitem>
+			<listitem><para>
+				<emphasis>trans_id</emphasis> - transaction identifier
+				(has the hash_entry:label format)
+			</para></listitem>
+			<listitem><para>
+				<emphasis>to_tag</emphasis> - To tag to be added to TO header
+			</para></listitem>
+			<listitem><para>
+				<emphasis>new_headers</emphasis> - extra headers to be
+				appended to the reply; use a dot (<quote>.</quote>) char
+				only if there are no headers;
+			</para></listitem>
+			<listitem><para>
+				<emphasis>body</emphasis> - (optional, may not be present)
+				reply body (if present, requires the
+				<quote>Content-Type</quote> and <quote>Content-length</quote>
+				headers)
+			</para></listitem>
+		</itemizedlist>
+	</section>
+	<section id="tm.rpc.reply_callid">
+		<title>
+		<function moreinfo="none">tm.reply_callid</function>
+		</title>
+		<para>
+		Generates and sends a reply for an existing inbound SIP transaction.
+		</para>
+		<para>Parameters: </para>
+		<itemizedlist>
+			<listitem><para>
+				<emphasis>code</emphasis> - reply code
+			</para></listitem>
+			<listitem><para>
+				<emphasis>reason</emphasis> - reason phrase.
+			</para></listitem>
+			<listitem><para>
+				<emphasis>callid</emphasis> - SIP Call-ID header
+			</para></listitem>
+			<listitem><para>
+				<emphasis>cseq</emphasis> - SIP CSeq header
+			</para></listitem>
+			<listitem><para>
+				<emphasis>to_tag</emphasis> - To tag to be added to TO header
+			</para></listitem>
+			<listitem><para>
+				<emphasis>new_headers</emphasis> - extra headers to be
+				appended to the reply; use a dot (<quote>.</quote>) char
+				only if there are no headers;
+			</para></listitem>
+			<listitem><para>
+				<emphasis>body</emphasis> - (optional, may not be present)
+				reply body (if present, requires the
+				<quote>Content-Type</quote> and <quote>Content-length</quote>
+				headers)
+			</para></listitem>
+		</itemizedlist>
+	</section>
+
+</section>
diff --git a/src/modules/tm/doc/tm.xml b/src/modules/tm/doc/tm.xml
index 823d942bba8..94eb2e49a3a 100644
--- a/src/modules/tm/doc/tm.xml
+++ b/src/modules/tm/doc/tm.xml
@@ -324,8 +324,9 @@ failure_route["serial"]
 
     <xi:include href="params.xml"/>
     <xi:include href="functions.xml"/>
-    <xi:include href="api.xml"/>
+    <xi:include href="rpc.xml"/>
     <xi:include href="event_routes.xml"/>
+    <xi:include href="api.xml"/>
 
     <section id="tm.known_issues">
 	<title>Known Issues</title>