Browse code

outbound(k) Minor edit of documentation.

Please ignore, keep calm and carry on.

Olle E. Johansson authored on 09/01/2013 19:18:42
Showing 2 changed files
... ...
@@ -4,7 +4,7 @@ Peter Dunkley
4 4
 
5 5
    Crocodile RCS Ltd
6 6
 
7
-   Copyright © 2012 Crocodile RCS Ltd
7
+   Copyright � 2012 Crocodile RCS Ltd
8 8
      __________________________________________________________________
9 9
 
10 10
    Table of Contents
... ...
@@ -87,9 +87,9 @@ make all
87 87
    responses to REGISTERs.
88 88
 
89 89
    When using TCP or TLS as the SIP transport care should be taken to set
90
-   the “tcp_connection_lifetime” on the Edge Proxy to a value slightly
90
+   the "tcp_connection_lifetime" on the Edge Proxy to a value slightly
91 91
    larger than the interval the Registrar is using for flow timer. Setting
92
-   “tcp_connection_lifetime” to less than the interval could cause
92
+   "tcp_connection_lifetime" to less than the interval could cause
93 93
    connections to be lost, and setting it to a value much larger than the
94 94
    interval will keep connections open far longer than is required (which
95 95
    is wasteful).
... ...
@@ -97,9 +97,9 @@ make all
97 97
    Application-layer keep-alives are optional when the underlying
98 98
    transport already has a keep-alive mechanism. The WebSocket transport
99 99
    has a transport-layer keep-alive. When using the WebSocket transport
100
-   the “keepalive_timeout” should be set to a value a little greater than
100
+   the "keepalive_timeout" should be set to a value a little greater than
101 101
    the Registrar flow timer interval and a little less than the
102
-   “tcp_connection_lifetime”.
102
+   "tcp_connection_lifetime".
103 103
 
104 104
    Example 1.2. Edge Proxy Configuration
105 105
 ...
... ...
@@ -295,7 +295,9 @@ failure_route[FAIL_OUTBOUND] {
295 295
    Default value is -1.
296 296
 
297 297
    Example 1.4. Set force_outbound_flag parameter
298
+...
298 299
 modparam("outbound", "force_outbound_flag", 1)
300
+...
299 301
 
300 302
 3.2. flow_token_key (string)
301 303
 
... ...
@@ -310,7 +312,9 @@ Note
310 312
    Default value is: "".
311 313
 
312 314
    Example 1.5. Set flow_token_key parameter
315
+...
313 316
 modparam("outbound", "flow_token_key", "!!!Kamailio rocks!!!")
317
+...
314 318
 
315 319
 4. Functions
316 320
 
... ...
@@ -268,7 +268,9 @@ failure_route[FAIL_OUTBOUND] {
268 268
 		<title>Set <varname>force_outbound_flag</varname> parameter
269 269
 		</title>
270 270
 		<programlisting format="linespecific">
271
+...
271 272
 modparam("outbound", "force_outbound_flag", 1)
273
+...
272 274
 </programlisting>
273 275
 		</example>
274 276
 	</section>
... ...
@@ -285,7 +287,9 @@ modparam("outbound", "force_outbound_flag", 1)
285 287
 		<title>Set <varname>flow_token_key</varname> parameter
286 288
 		</title>
287 289
 		<programlisting format="linespecific">
290
+...
288 291
 modparam("outbound", "flow_token_key", "!!!Kamailio rocks!!!")
292
+...
289 293
 </programlisting>
290 294
 		</example>
291 295
 	</section>