Module: sip-router Branch: master Commit: 22cb194483a7b0d15b823cb8f851cd1fe9746a8c URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=22cb194… Author: Marius Zbihlei &lt;marius.zbihlei(a)1and1.ro&gt; Committer: Marius Zbihlei &lt;marius.zbihlei(a)1and1.ro&gt; Date: Fri Oct 1 12:52:33 2010 +0300 modules/carrierroute: change doc to reflect latest changes in append branch --- modules/carrierroute/README | 10 +++++----- modules/carrierroute/doc/carrierroute_admin.xml | 2 +- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/modules/carrierroute/README b/modules/carrierroute/README index 5c4f15d..1c28e22 100644 --- a/modules/carrierroute/README +++ b/modules/carrierroute/README @@ -272,11 +272,11 @@ Chapter 1. Admin Guide modules. But for smaller installations it probably make more sense to use the lcr and dispatcher module. - Starting with version 3.0 of kamailio, if you want to use this module - in failure routes, it is not needed to call“append_branch()” after - rewriting the request URI in order to relay the message to the new - target. Its also supportes the usage of database derived failure - routing descisions with the carrierfailureroute table. + Starting with version 3.1 , if you want to use this module in failure + routes, it is not needed to call“append_branch()” after rewriting the + request URI in order to relay the message to the new target. Its also + supportes the usage of database derived failure routing descisions with + the carrierfailureroute table. 2. Dependencies diff --git a/modules/carrierroute/doc/carrierroute_admin.xml b/modules/carrierroute/doc/carrierroute_admin.xml index f83b2c0..d30bb29 100644 --- a/modules/carrierroute/doc/carrierroute_admin.xml +++ b/modules/carrierroute/doc/carrierroute_admin.xml @@ -66,7 +66,7 @@ installations it probably make more sense to use the lcr and dispatcher module. </para> <para> - Starting with version 3.0 of kamailio, if you want to use this module in failure routes, + Starting with version 3.1 , if you want to use this module in failure routes, it is not needed to call<quote>append_branch()</quote> after rewriting the request URI in order to relay the message to the new target. Its also supportes the usage of database derived failure routing descisions with the carrierfailureroute table.