|
@@ -26,13 +26,13 @@ Nils Ohlmeier
|
|
|
requests which are suggested or even required by a RFC, but are not
|
|
|
available yet in the core of SIP-router.
|
|
|
|
|
|
- This checks are not required by SIP-router itself for its
|
|
|
+ These checks are not required by SIP-router itself for its
|
|
|
functionality. But on the other side it makes not much sence if a
|
|
|
broken request traverses through a SIP network if it is rejected sooner
|
|
|
- or later by a SIP device any way. As every sanity cost extra
|
|
|
- performance because of additional parsing and evaluation it is now with
|
|
|
- this module up to the SIP-router adminstrator which checks should be
|
|
|
- done on which request.
|
|
|
+ or later by a SIP device any way. As every sanity check cost extra
|
|
|
+ performance because of additional parsing and evaluation it is with
|
|
|
+ this module now up to the SIP-router adminstrator which checks should
|
|
|
+ be done on which request.
|
|
|
|
|
|
The following checks are available:
|
|
|
* ruri sip version - (1) - checks if the SIP version in the request
|
|
@@ -102,10 +102,10 @@ modparam("sanity", "uri_checks", 3)
|
|
|
|
|
|
1.3.3. proxy_require (string)
|
|
|
|
|
|
- This parameter set the list of supported extensions for this
|
|
|
- SIP-router. The value is expected as comma separated list of the
|
|
|
+ This parameter sets the list of supported extensions for this
|
|
|
+ SIP-router. The value is expected as a comma separated list of
|
|
|
extensions. This list is separated into single tokens. Each token from
|
|
|
- a proxy require header will be compare to the tokens from this list.
|
|
|
+ a proxy require header will be compared to the tokens from this list.
|
|
|
|
|
|
Example 3. Set proxy_require parameter
|
|
|
...
|
|
@@ -128,13 +128,13 @@ modparam("sanity", "autodrop", 1)
|
|
|
|
|
|
1.4. Functions
|
|
|
|
|
|
-1.4.1. sanity_check([msg_checks [, uri_checks]])
|
|
|
+1.4.1. sanity_check([msg_checks [, uri_checks]])
|
|
|
|
|
|
This function makes a row of sanity checks over the given SIP request.
|
|
|
- The behavior of the function is also controled by 'autodrop' parameter.
|
|
|
- If autodrop=0, the function returns false (-1) if one of the checks
|
|
|
- failed. When autodrop=1, the function stops the execution of
|
|
|
- configuration file. In both cases, ff one of the checks fails the
|
|
|
+ The behavior of the function is also controlled by 'autodrop'
|
|
|
+ parameter. If autodrop=0, the function returns false (-1) if one of the
|
|
|
+ checks failed. When autodrop=1, the function stops the execution of
|
|
|
+ configuration file. In both cases, if one of the checks fails the
|
|
|
module sends a precise error reply via SL send_reply(). Thus there is
|
|
|
no need to reply with a generic error message.
|
|
|
|