|
|
@@ -1,6 +1,10 @@
|
|
|
<?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">
|
|
|
+ "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
|
|
|
+
|
|
|
+<!ENTITY % docentities SYSTEM "../../../../doc/docbook/entities.xml">
|
|
|
+%docentities;
|
|
|
+]>
|
|
|
|
|
|
<book id="sl" xmlns:xi="http://www.w3.org/2001/XInclude">
|
|
|
<bookinfo>
|
|
|
@@ -43,7 +47,7 @@
|
|
|
<para>
|
|
|
The <acronym>SL</acronym> module needs to filter ACKs sent after a
|
|
|
local stateless reply to an INVITE was generated. To recognize such
|
|
|
- ACKs, ser adds a special "signature" in to-tags. This signature is
|
|
|
+ ACKs, &kamailio; adds a special "signature" in to-tags. This signature is
|
|
|
sought for in incoming ACKs, and if included, the ACKs are
|
|
|
absorbed.
|
|
|
</para>
|
|
|
@@ -61,7 +65,7 @@
|
|
|
module) for INVITE processing. Particularly, the problem happens when a UA
|
|
|
sends an INVITE which already has a to-tag in it (e.g., a
|
|
|
re-INVITE) and the server want to reply to it. Then, it will keep the
|
|
|
- current to-tag, which will be mirrored in ACK. SER will not see
|
|
|
+ current to-tag, which will be mirrored in ACK. &kamailio; will not see
|
|
|
its signature and forward the ACK downstream. Caused harm is not
|
|
|
bad, just a useless ACK is forwarded.
|
|
|
</para>
|
Mikko Lehto