Difference between revisions of "Apply Settings"
(→added reloadacl and rescan) |
|||
| Line 7: | Line 7: | ||
When you apply the settings you may see an error on the status page. For example: '+OK [[error near line 4968]: unclosed' or 'Cannot Initialize [[error near line 1159]: unexpected <]'. This means that something you changed prior to applying the settings has caused a syntax error in the XML. A good hint would be to look at what you last changed - that is probably when you caused the problem. To locate this error use an editor such as nano to look at freeswitch/log/freeswitchxml.fsxml - this file is generated by freeswitch when it is processing all the XML files in the freeswitch/conf directory structure. In nano CTRL-_ will allow you to enter the line number from the error message. When you have seen the line in that file you can then go back and look for the corresponding line in one of the XML files in the entire freeswitch/conf directory structure and fix the problem there. Note that the error might not be on that line - in these two example messages it says that the problem is near that line - hunt around and try to spot the error. | When you apply the settings you may see an error on the status page. For example: '+OK [[error near line 4968]: unclosed' or 'Cannot Initialize [[error near line 1159]: unexpected <]'. This means that something you changed prior to applying the settings has caused a syntax error in the XML. A good hint would be to look at what you last changed - that is probably when you caused the problem. To locate this error use an editor such as nano to look at freeswitch/log/freeswitchxml.fsxml - this file is generated by freeswitch when it is processing all the XML files in the freeswitch/conf directory structure. In nano CTRL-_ will allow you to enter the line number from the error message. When you have seen the line in that file you can then go back and look for the corresponding line in one of the XML files in the entire freeswitch/conf directory structure and fix the problem there. Note that the error might not be on that line - in these two example messages it says that the problem is near that line - hunt around and try to spot the error. | ||
| − | + | It performs a [http://wiki.freeswitch.org/wiki/Mod_commands#reloadacl reloadacl] and external profile [http://wiki.freeswitch.org/wiki/Sofia#Reloading_profiles_and_gateways rescan] | |
| − | == | + | == Changes == |
| − | * [http://wiki.freeswitch.org/wiki/Mod_commands#reloadacl reloadacl] | + | * [http://wiki.freeswitch.org/wiki/Mod_commands#reloadxml '''reloadxml'''] is not needed here anymore since [http://wiki.freeswitch.org/wiki/Mod_commands#reloadacl reloadacl] and [http://wiki.freeswitch.org/wiki/Sofia#Reloading_profiles_and_gateways rescan] always perform '''reloadxml''' |
| − | |||
| − | |||
Latest revision as of 16:48, 17 January 2011
Menu: (System-Apply Settings)
REMOVED from menu since it will appear on the page every time you make a change.
This tries to apply any config changes you have made from FusionPBX to your running Freeswitch server.
When you apply the settings you may see an error on the status page. For example: '+OK [[error near line 4968]: unclosed' or 'Cannot Initialize [[error near line 1159]: unexpected <]'. This means that something you changed prior to applying the settings has caused a syntax error in the XML. A good hint would be to look at what you last changed - that is probably when you caused the problem. To locate this error use an editor such as nano to look at freeswitch/log/freeswitchxml.fsxml - this file is generated by freeswitch when it is processing all the XML files in the freeswitch/conf directory structure. In nano CTRL-_ will allow you to enter the line number from the error message. When you have seen the line in that file you can then go back and look for the corresponding line in one of the XML files in the entire freeswitch/conf directory structure and fix the problem there. Note that the error might not be on that line - in these two example messages it says that the problem is near that line - hunt around and try to spot the error.
It performs a reloadacl and external profile rescan
