Changeset 6674

Timestamp:

09/09/08 13:33:07 (5 years ago)

Author:

fskrotzki

Message:

update inline help for file referances, fixed a few typos in extensions comments.

Files:

• modules/branches/2.5/core/etc/extensions.conf (modified) (3 diffs)
• modules/branches/2.5/core/etc/iax.conf (modified) (1 diff)
• modules/branches/2.5/core/etc/sip.conf (modified) (1 diff)

modules/branches/2.5/core/etc/extensions.conf

@@ -22 +22 @@
-; This include file is to be used with extreme caution. In almost all cases    *
-; any custom dialplan SHOULD be put in extensions_custom.conf which will       *
-
-
-
+
+
+
+
+
+
-;                                                                              *
-#include extensions_override_freepbx.conf
@@ -34 +37 @@
-
-; Customizations to this dialplan should be made in extensions_custom.conf
-
+
+
+
+
-#include extensions_custom.conf
-
@@ -674 +680 @@
-[macro-dialout-trunk-predial-hook]
-; this macro intentially left blank so it may be safely overwritten for any custom
-
+o
-;
-; MACRO RETURN CODE: ${PREDIAL_HOOK_RET}

modules/branches/2.5/core/etc/iax.conf

@@ -16 +16 @@
-; These should all be expected to come after the [general] context
-;
+;iax_custom.conf is the proper place to start creating new contexts that you 
+;might have a need for.  Dundi IAX trunks is one example of when this file is needed.
+;
-#include iax_custom.conf
-#include iax_additional.conf
+;
+;iax_custom_post.conf will allow you to modify FreePBX generated IAX setups so
+;that you can add additional parameters to a auto-generated setup.
+;if you have a auto-generated context of [foobar] and need to add a parameter 
+;to it then create this line [foobar](+) and place your additions on the next line
+;
-#include iax_custom_post.conf
-

modules/branches/2.5/core/etc/sip.conf

@@ -7 +7 @@
-
-[general]
+
+; These files will all be included in the [general] context
-;
-
-
-
+
+
+
+
+
-;
-; jbenable=yes
-; jbforce=yes
+;
+;It is also the proper place to add the lines needed for sip nat'ing when going
+;through a firewall.  For nat'ing you'd need to add the following lines: 
+; nat=yes , externip= , localhost= , and optionally fromdomain= .
+;
+#include sip_general_custom.conf
-
-
+
+
+
+
+
+
+
+
-;
-#include sip_general_additional.conf
-#include sip_general_custom.conf
-#include sip_nat.conf
-#include sip_registrations_custom.conf
-#include sip_registrations.conf
-
-
+files 
-;
-#include sip_custom.conf
-#include sip_additional.conf
+
+;sip_custom_post.conf If you have extra parameters that are needed for a 
+;extension to work to for example, those go here.  So you have extension 
+;1000 defined in your system you start by creating a line [1000](+) in this 
+;file.  Then on the next line add the extra parameter that is needed.  
+;When the sip.conf is loaded it will append your additions to the end of 
+;that extension. 
+;
-#include sip_custom_post.conf