Skip to content

Commit

Permalink
nathelper: documented the use of add_rcv_param() for Contact URI case
Browse files Browse the repository at this point in the history
  • Loading branch information
miconda committed Jan 24, 2018
1 parent 64303a9 commit 57bd759
Showing 1 changed file with 10 additions and 6 deletions.
16 changes: 10 additions & 6 deletions src/modules/nathelper/doc/nathelper_admin.xml
Expand Up @@ -554,19 +554,23 @@ 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>
<listitem><para>
<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>
Expand Down

0 comments on commit 57bd759

Please sign in to comment.