SIP filters: the type of config options we should look for

Signed-off-by: Jason Etheridge <jason@EquinoxOLI.org>

diff --git a/SIPconfig.xml.example.evergreen b/SIPconfig.xml.example.evergreen
index 01f42ba..b8cd4ce 100644 (file)
--- a/SIPconfig.xml.example.evergreen
+++ b/SIPconfig.xml.example.evergreen
@@ -199,6 +199,19 @@
                 <checkin_hold_as_transit>1</checkin_hold_as_transit>
                 -->
 
+        <filters>
+            <!--
+                Filters allow SIPServer to strip or modify specified fields inline from outgoing SIP messages.  Currently, these
+                rules apply to all message types and only work for variable-length fields, but the config layout leaves room for
+                future enhancement.
+
+                Examples:
+
+                <field identifier="AE" replace_with="John Doe" />
+                <field identifier="BE" remove="true" />
+            -->
+        </filters>
+
       </implementation_config>
   
     </institution>

diff --git a/SIPconfig.xml.example.stock b/SIPconfig.xml.example.stock
index 84775a1..3cef29c 100644 (file)
--- a/SIPconfig.xml.example.stock
+++ b/SIPconfig.xml.example.stock
@@ -85,7 +85,21 @@
     </institution>
 
     <institution id="LPL" implementation="ILS">
-    <encoding>UTF-8</encoding>
+        <encoding>UTF-8</encoding>
+        <implementation_config>
+            <filters>
+                <!--
+                    Filters allow SIPServer to strip or modify specified fields inline from outgoing SIP messages.  Currently, these
+                    rules apply to all message types and only work for variable-length fields, but the config layout leaves room for
+                    future enhancement.
+
+                    Examples:
+
+                    <field identifier="AE" replace_with="John Doe" />
+                    <field identifier="BE" remove="true" />
+                -->
+            </filters>
+        </implementation_config>
     </institution>
 </institutions>
 </acsconfig>