Explorar el Código

nathelper: documented the use of add_rcv_param() for Contact URI case

Daniel-Constantin Mierla hace 7 años
padre
commit
57bd759e19
Se han modificado 1 ficheros con 10 adiciones y 6 borrados
  1. 10 6
      src/modules/nathelper/doc/nathelper_admin.xml

+ 10 - 6
src/modules/nathelper/doc/nathelper_admin.xml

@@ -554,11 +554,15 @@ if (search("User-Agent: Cisco ATA.*") {fix_nated_sdp("3");};
 		</title>
 		<para>
 		Add a received parameter to the <quote>Contact</quote> header fields
-		or the Contact URI. The parameter will contain the URI created from the
-		source IP, port, and protocol of the packet containing the SIP message.
-		The parameter can be then processed by another registrar. This is useful,
-		for example, when replicating register messages using <function>t_replicate</function>
-		function to another registrar.
+		(available for all transports) or to the Contact URI (available only
+		for UDP traffic).
+		</para>
+		<para>
+		The parameter will contain the URI created from the
+		source IP, port, and protocol (if different than UDP) of the packet
+		containing the SIP message. The parameter can be then processed by
+		another registrar. This is useful, for example, when replicating register
+		messages using <function>t_replicate</function> function to another registrar.
 		</para>
 		<para>Meaning of the parameters is as follows:</para>
 		<itemizedlist>
@@ -566,7 +570,7 @@ if (search("User-Agent: Cisco ATA.*") {fix_nated_sdp("3");};
 			<emphasis>flag</emphasis> - flags to indicate if the parameter
 			should be added to Contact URI or Contact header. If the flag is
 			non-zero, the parameter will be added to the Contact URI. If not
-			used or equal to zero, the parameter will go to the Contact 
+			used or equal to zero, the parameter will go to the Contact
 			header.
 			</para></listitem>
 		</itemizedlist>