Browse code

topos: docs - more details about what SIP traffic is handled

Daniel-Constantin Mierla authored on 15/09/2020 05:33:00
Showing 1 changed files
... ...
@@ -16,20 +16,23 @@
16 16
 	<section>
17 17
 	<title>Overview</title>
18 18
 	<para>
19
-		This module offers topology hiding by stripping the SIP routing
20
-		headers that show topology details.
19
+		This module offers topology hiding for INVITE-based dialogs, by stripping
20
+		the SIP routing headers that show topology details .
21 21
 		The script interpreter gets the SIP messages with full content,
22 22
 		so all existing functionality is preserved.
23 23
 	</para>
24 24
 	<para>
25 25
 		The module is transparent for the configuration writer. It only needs to be
26
-		loaded (tune the parameters if needed).
26
+		loaded (tune the module parameters if needed).
27 27
 	</para>
28 28
 	<para>
29 29
 		It also works for SIP MESSAGE or other requests that do not create
30
-		a call dialog -- record_route() must be used for them as well, the
30
+		a dialog -- record_route() must be used for them as well, the
31 31
 		headers are not going to be in the messages sent to the network, they
32 32
 		are needed to know local addresses used to communicate with each side.
33
+		At this moment it is not designed to work for presence (SUBSCRIBE-based)
34
+		dialogs. The REGISTER and PUBLISH requests are skipped from processing
35
+		by this module, expected to be terminated on a local SIP server.
33 36
 	</para>
34 37
 	</section>
35 38
 	<section>