From version 69.1
edited by Buildbot
on 2018/03/01 01:02
To version 70.1
edited by Buildbot
on 2018/06/01 01:01
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,4 +1,4 @@
1 -// Documentation based on repostory git version commit 1.0.12-321-gf002da0
1 +// Documentation based on repostory git version commit 1.0.12-405-gca78774
2 2  //
3 3  =Module Router=
4 4  
... ... @@ -18,6 +18,7 @@
18 18  |=(% style="text-align: center; vertical-align: middle; border: 1px solid #999" %)treat-all-as-urgent|(% style="text-align: left; border: 1px solid #999" %)During a fork procedure, treat all failure response as urgent|(% style="text-align: center; vertical-align: middle; border: 1px solid #999" %) ##false##|(% style="text-align: center; vertical-align: middle; border: 1px solid #999" %)Boolean
19 19  |=(% style="text-align: center; vertical-align: middle; border: 1px solid #999" %)call-fork-timeout|(% style="text-align: left; border: 1px solid #999" %)Maximum time for a call fork to try to reach a callee, in seconds.|(% style="text-align: center; vertical-align: middle; border: 1px solid #999" %) ##90##|(% style="text-align: center; vertical-align: middle; border: 1px solid #999" %)Integer
20 20  |=(% style="text-align: center; vertical-align: middle; border: 1px solid #999" %)call-fork-urgent-timeout|(% style="text-align: left; border: 1px solid #999" %)Maximum time before delivering urgent responses during a call fork, in seconds. The typical fork process requires to wait the best response from all branches before transmitting it to the client. However some error responses are retryable immediately (like 415 unsupported media, 401, 407) thus it is painful for the client to need to wait the end of the transaction time (32 seconds) for these error codes.|(% style="text-align: center; vertical-align: middle; border: 1px solid #999" %) ##5##|(% style="text-align: center; vertical-align: middle; border: 1px solid #999" %)Integer
21 +|=(% style="text-align: center; vertical-align: middle; border: 1px solid #999" %)call-fork-current-branches-timeout|(% style="text-align: left; border: 1px solid #999" %)Maximum time before trying the next branches with lower priotiries|(% style="text-align: center; vertical-align: middle; border: 1px solid #999" %) ##10##|(% style="text-align: center; vertical-align: middle; border: 1px solid #999" %)Integer
21 21  |=(% style="text-align: center; vertical-align: middle; border: 1px solid #999" %)call-push-response-timeout|(% style="text-align: left; border: 1px solid #999" %)Optional timer to detect lack of push response, in seconds.|(% style="text-align: center; vertical-align: middle; border: 1px solid #999" %) ##0##|(% style="text-align: center; vertical-align: middle; border: 1px solid #999" %)Integer
22 22  |=(% style="text-align: center; vertical-align: middle; border: 1px solid #999" %)message-fork-late|(% style="text-align: left; border: 1px solid #999" %)Fork messages to client registering lately. |(% style="text-align: center; vertical-align: middle; border: 1px solid #999" %) ##true##|(% style="text-align: center; vertical-align: middle; border: 1px solid #999" %)Boolean
23 23  |=(% style="text-align: center; vertical-align: middle; border: 1px solid #999" %)message-delivery-timeout|(% style="text-align: left; border: 1px solid #999" %)Maximum duration for delivering a text message. This property applies only if message-fork-late if set to true, otherwise the duration can't exceed the normal transaction duration.|(% style="text-align: center; vertical-align: middle; border: 1px solid #999" %) ##3600##|(% style="text-align: center; vertical-align: middle; border: 1px solid #999" %)Integer
... ... @@ -27,4 +27,7 @@
27 27  |=(% style="text-align: center; vertical-align: middle; border: 1px solid #999" %)generated-contact-expected-realm|(% style="text-align: left; border: 1px solid #999" %)Require presence of authorization header for specified realm. [Realm]|(% style="text-align: center; vertical-align: middle; border: 1px solid #999" %) ####|(% style="text-align: center; vertical-align: middle; border: 1px solid #999" %)String
28 28  |=(% style="text-align: center; vertical-align: middle; border: 1px solid #999" %)generate-contact-even-on-filled-aor|(% style="text-align: left; border: 1px solid #999" %)Generate a contact route even on filled AOR.|(% style="text-align: center; vertical-align: middle; border: 1px solid #999" %) ##false##|(% style="text-align: center; vertical-align: middle; border: 1px solid #999" %)Boolean
29 29  |=(% style="text-align: center; vertical-align: middle; border: 1px solid #999" %)remove-to-tag|(% style="text-align: left; border: 1px solid #999" %)Remove to tag from 183, 180, and 101 responses to workaround buggy gateways|(% style="text-align: center; vertical-align: middle; border: 1px solid #999" %) ##false##|(% style="text-align: center; vertical-align: middle; border: 1px solid #999" %)Boolean
30 -|=(% style="text-align: center; vertical-align: middle; border: 1px solid #999" %)preroute|(% style="text-align: left; border: 1px solid #999" %)rewrite username with given value.|(% style="text-align: center; vertical-align: middle; border: 1px solid #999" %) ####|(% style="text-align: center; vertical-align: middle; border: 1px solid #999" %)String
31 +|=(% style="text-align: center; vertical-align: middle; border: 1px solid #999" %)preroute|(% style="text-align: left; border: 1px solid #999" %)Rewrite username with given value.|(% style="text-align: center; vertical-align: middle; border: 1px solid #999" %) ####|(% style="text-align: center; vertical-align: middle; border: 1px solid #999" %)String
32 +|=(% style="text-align: center; vertical-align: middle; border: 1px solid #999" %)resolve-routes|(% style="text-align: left; border: 1px solid #999" %)Whether or not to resolve all routes and forward the event to it if it's not us|(% style="text-align: center; vertical-align: middle; border: 1px solid #999" %) ##false##|(% style="text-align: center; vertical-align: middle; border: 1px solid #999" %)Boolean
33 +|=(% style="text-align: center; vertical-align: middle; border: 1px solid #999" %)fallback-route|(% style="text-align: left; border: 1px solid #999" %)Default route to apply when the recipient is unreachable. [sip:host:port]|(% style="text-align: center; vertical-align: middle; border: 1px solid #999" %) ####|(% style="text-align: center; vertical-align: middle; border: 1px solid #999" %)String
34 +|=(% style="text-align: center; vertical-align: middle; border: 1px solid #999" %)parent-domain-fallback|(% style="text-align: left; border: 1px solid #999" %)Whether or not to fallback to the parent domain if there is no fallback route set and the recipient is unreachable|(% style="text-align: center; vertical-align: middle; border: 1px solid #999" %) ##false##|(% style="text-align: center; vertical-align: middle; border: 1px solid #999" %)Boolean