浏览代码

Update toll_allow.rst

Len 8 年之前
父节点
当前提交
38f3de34a7
共有 1 个文件被更改,包括 7 次插入1 次删除
  1. 7 1
      source/additional_information/toll_allow.rst

+ 7 - 1
source/additional_information/toll_allow.rst

@@ -9,7 +9,13 @@ An example for the contents of the toll_allow variable would be:
 
 
 You can then add information to your dialplan to process this variable.  In the example XML below, if the valid allow value isn't present then an extension shouldn't be able to dial out.  However extension -> extension should still work.
 You can then add information to your dialplan to process this variable.  In the example XML below, if the valid allow value isn't present then an extension shouldn't be able to dial out.  However extension -> extension should still work.
 
 
-The following code are example XML for standard outbound routes (Dialplan->OutboundRoutes).  Effectively you are applying an additional condition to EACH outbound route that you want to limit.  So in the FusionPBX GUI select an outbound route and add a condition, type "${toll_allow}", data "local".  Order is important, this should be the FIRST condition of your outbound route.
+The following code are example XML for standard outbound routes (Dialplan->OutboundRoutes).  Effectively you are applying an additional condition to EACH outbound route that you want to limit.  So in the FusionPBX GUI select an outbound route and add
+
+::
+
+ condition, type "${toll_allow}", data "local".
+ Order is important, this should be the FIRST condition of your outbound route.
+
 You'll need to do that for all of your outbound routes, tag them local, domestic, or international depending on what they are.
 You'll need to do that for all of your outbound routes, tag them local, domestic, or international depending on what they are.
 On some installations this example file will be present in /usr/local/freeswitch/conf/dialplan/default/01_example.com.xml:
 On some installations this example file will be present in /usr/local/freeswitch/conf/dialplan/default/01_example.com.xml: