| | 449 | // AMPASTERISKUSER |
|---|
| | 450 | $set['value'] = 'asterisk'; |
|---|
| | 451 | $set['description'] = 'The user Asterisk should be running as, used by freepbx_engine. Most systems should not change this.'; |
|---|
| | 452 | $set['type'] = CONF_TYPE_TEXT; |
|---|
| | 453 | $set['level'] = 4; |
|---|
| | 454 | $freepbx_conf->define_conf_setting('AMPASTERISKUSER',$set); |
|---|
| | 455 | $set['level'] = 0; |
|---|
| | 456 | |
|---|
| | 457 | // AMPASTERISKGROUP |
|---|
| | 458 | $set['value'] = 'asterisk'; |
|---|
| | 459 | $set['description'] = 'The user group Asterisk should be running as, used by freepbx_engine. Most systems should not change this.'; |
|---|
| | 460 | $set['type'] = CONF_TYPE_TEXT; |
|---|
| | 461 | $set['level'] = 4; |
|---|
| | 462 | $freepbx_conf->define_conf_setting('AMPASTERISKGROUP',$set); |
|---|
| | 463 | $set['level'] = 0; |
|---|
| | 464 | |
|---|
| | 465 | // AMPASTERISKWEBUSER |
|---|
| | 466 | $set['value'] = 'asterisk'; |
|---|
| | 467 | $set['description'] = 'The user your httpd should be running as, used by freepbx_engine. Most systems should not change this.'; |
|---|
| | 468 | $set['type'] = CONF_TYPE_TEXT; |
|---|
| | 469 | $set['level'] = 4; |
|---|
| | 470 | $freepbx_conf->define_conf_setting('AMPASTERISKWEBUSER',$set); |
|---|
| | 471 | $set['level'] = 0; |
|---|
| | 472 | |
|---|
| | 473 | // AMPASTERISKWEBGROUP |
|---|
| | 474 | $set['value'] = 'asterisk'; |
|---|
| | 475 | $set['description'] = 'The user group your httpd should be running as, used by freepbx_engine. Most systems should not change this.'; |
|---|
| | 476 | $set['type'] = CONF_TYPE_TEXT; |
|---|
| | 477 | $set['level'] = 4; |
|---|
| | 478 | $freepbx_conf->define_conf_setting('AMPASTERISKWEBGROUP',$set); |
|---|
| | 479 | $set['level'] = 0; |
|---|
| | 480 | |
|---|
| | 481 | // AMPDEVUSER |
|---|
| | 482 | $set['value'] = 'asterisk'; |
|---|
| | 483 | $set['description'] = 'The user that various device directories should be set to, used by freepbx_engine. Examples include /dev/zap, /dev/dahdi, /dev/misdn, /dev/mISDN and /dev/dsp. Most systems should not change this.'; |
|---|
| | 484 | $set['type'] = CONF_TYPE_TEXT; |
|---|
| | 485 | $set['level'] = 4; |
|---|
| | 486 | $freepbx_conf->define_conf_setting('AMPDEVUSER',$set); |
|---|
| | 487 | $set['level'] = 0; |
|---|
| | 488 | |
|---|
| | 489 | // AMPDEVGROUP |
|---|
| | 490 | $set['value'] = 'asterisk'; |
|---|
| | 491 | $set['description'] = 'The user group that various device directories should be set to, used by freepbx_engine. Examples include /dev/zap, /dev/dahdi, /dev/misdn, /dev/mISDN and /dev/dsp. Most systems should not change this.'; |
|---|
| | 492 | $set['type'] = CONF_TYPE_TEXT; |
|---|
| | 493 | $set['level'] = 4; |
|---|
| | 494 | $freepbx_conf->define_conf_setting('AMPDEVGROUP',$set); |
|---|
| | 495 | $set['level'] = 0; |
|---|
| 973 | | /* TODO: These go in the modules |
|---|
| 974 | | |
|---|
| 975 | | dashboard: |
|---|
| 976 | | |
|---|
| 977 | | ('DASHBOARD_INFO_UPDATE_TIME','',0,'These can be used to change the refresh rate of the System Status Panel. Most of the stats are updated based on the STATS interval but a few items are','uint',NULL,NULL,NULL,NULL), |
|---|
| 978 | | ('DASHBOARD_STATS_UPDATE_TIME','',0,'These can be used to change the refresh rate of the System Status Panel. Most of the stats are updated based on the STATS interval but a few items are','uint',NULL,NULL,NULL,NULL), |
|---|
| 979 | | |
|---|
| 980 | | daynight: |
|---|
| 981 | | |
|---|
| 982 | | ('DAYNIGHTTCHOOK','0',0,'By default, the Day/Night module will not hook Time Conditions allowing one to associate a daynight manual override with a time condition since now time conditions have their own feature code. If there is already an associaiton configured (on an upgraded system), this will have no affect for the Time Conditions that # are effected. Setting this to true reverts the previous behavior by allowing for the continued use of a daynight toggle to be associated with a time conditon. This can be useful for two scenarios. First, to override a Time Condition without the automatic resetting that occurs with the built in Time Condition overrides. The second use is the ability to associate a single daynight toggle with multiple time conditions thus creating a <b>master switch</b> that can be used to override several possible call flows through different time conditions.<br>Default = false','bool',NULL,'1',NULL,NULL), |
|---|
| 983 | | |
|---|
| 984 | | timeconditions: |
|---|
| 985 | | |
|---|
| 986 | | ('TCINTERVAL','60',0,'The polling interval used by the Time Conditions manintenace task, launched by an Asterisk call file used to update Time Conditions override states as well as keep custom device state hint values up-to-date when being used with BLF. This interval should be shorter than the shortest time condition true (open) or false (closed) interval to assure that an override is reset after the current time period has expired that it was set in.<br>Default value 60 seconds.','uint',NULL,'60',NULL,NULL), |
|---|
| 987 | | ('TCMAINT','1',0,'If set to false, this will override the execution of the Time Conditons maintenace task launched by call files. If all the feature codes for time conditions are disabled, the maintenance task will not be launched so this is not needed for that condition. Setting this to false would be fairly un-common. On an extremely active system that has constant calls flowing throught all time conditions of interest that might be overriden one might set this to avoid the additional polling that would otherwise occur since calls traversing the time conditions contexts will also maintain all the necessary state information. You may also set this temporarily if debugging a system to avoid the periodic dialplan running through the CLI that the maintenance task otherwise creates.<br>Default = true','bool',NULL,'1',NULL,NULL), |
|---|
| 988 | | |
|---|
| 989 | | queues: |
|---|
| 990 | | |
|---|
| 991 | | ('USEQUEUESTATE','0',0,'Setting this flag will generate the required dialplan to integrate with the following Asterisk patch: <b>https://issues.asterisk.org/view.php?id=15168</b>. This feature is planned for a future 1.6 release but given the existence of the patch can be used prior. Once the release version is known, code will be added to automatically enable this format in versions of Asterisk that support it<br>Default = false','bool',NULL,'0',NULL,NULL), |
|---|
| 992 | | |
|---|
| 993 | | music: |
|---|
| 994 | | |
|---|
| 995 | | ('AMPMPG123','1',0,'When set to false, the old MoH behavior is adopted where MP3 files can be loaded and WAV files converted to MP3. The new default behavior assumes you have mpg123 loaded as well as sox and will convert MP3 files to WAV. This is highly recommended as MP3 files heavily tax the system and can cause instability on a busy phone system<br>Default = true','bool',NULL,'1',NULL,NULL), |
|---|
| 996 | | |
|---|
| 997 | | |
|---|
| | 1020 | // TODO: temporary, this is all going to be removed, just transitionary work |
|---|
| | 1021 | function bogus_for_now() { |
|---|
| | 1022 | // TODO: CODE FOR MODULES |
|---|
| | 1023 | |
|---|
| | 1024 | /* |
|---|
| | 1025 | TODO: I think I need these |
|---|
| | 1026 | |
|---|
| | 1027 | ASTMANAGERPROXYPORT |
|---|
| | 1028 | SSHPORT |
|---|
| | 1029 | |
|---|
| | 1030 | TODO: Check what version we have the patch for? Possibly skip, possibly not. |
|---|
| | 1031 | |
|---|
| | 1032 | PARKINGPATCH |
|---|
| | 1033 | |
|---|
| | 1034 | TODO: Check these, probably skip |
|---|
| | 1035 | |
|---|
| | 1036 | AMPBACKUPEMAILFROM |
|---|
| | 1037 | AMPBACKUPSUDO |
|---|
| | 1038 | AMPBACKUPADVANCED |
|---|
| | 1039 | */ |
|---|
| | 1040 | |
|---|
| | 1041 | // TODO: skipping some of the BACKUP MIGRATION, IF THEY DIDN'T DO IT ALREADY, TOUCH LUCK! |
|---|
| | 1042 | |
|---|
| | 1043 | // USEQUEUESTATE |
|---|
| | 1044 | // |
|---|
| | 1045 | $set['value'] = false; |
|---|
| | 1046 | $set['defaultval'] =& $set['value']; |
|---|
| | 1047 | $set['readonly'] = 0; |
|---|
| | 1048 | $set['hidden'] = 0; |
|---|
| | 1049 | $set['level'] = 3; |
|---|
| | 1050 | $set['module'] = 'queues'; |
|---|
| | 1051 | $set['category'] = ''; |
|---|
| | 1052 | $set['emptyok'] = 0; |
|---|
| | 1053 | $set['description'] = 'Setting this flag will generate the required dialplan to integrate with the following Asterisk patch: <b>https://issues.asterisk.org/view.php?id=15168</b>. This setting is obsolete on Asterisk 1.8+ systems where the hint state is now standard and always used. This asterisk patch is only available on Asterisk 1.4, trying to use this setting on Asterisk 1.6 will break some queue behavior and should be avoided'; |
|---|
| | 1054 | $set['type'] = CONF_TYPE_BOOL; |
|---|
| | 1055 | $freepbx_conf->define_conf_setting('USEQUEUESTATE',$set); |
|---|
| | 1056 | |
|---|
| | 1057 | |
|---|
| | 1058 | // DASHBOARD_INFO_UPDATE_TIME |
|---|
| | 1059 | // |
|---|
| | 1060 | $set['value'] = 6; |
|---|
| | 1061 | $set['defaultval'] =& $set['value']; |
|---|
| | 1062 | $set['readonly'] = 0; |
|---|
| | 1063 | $set['hidden'] = 0; |
|---|
| | 1064 | $set['level'] = 0; |
|---|
| | 1065 | $set['module'] = 'dashboard'; |
|---|
| | 1066 | $set['category'] = ''; |
|---|
| | 1067 | $set['emptyok'] = 1; |
|---|
| | 1068 | $set['description'] = 'Update rate in seconds of all sections of the System Status panel except the Info box.'; |
|---|
| | 1069 | $set['type'] = CONF_TYPE_UINT; |
|---|
| | 1070 | $freepbx_conf->define_conf_setting('DASHBOARD_INFO_UPDATE_TIME',$set); |
|---|
| | 1071 | |
|---|
| | 1072 | // DASHBOARD_INFO_UPDATE_TIME |
|---|
| | 1073 | // |
|---|
| | 1074 | $set['value'] = 30; |
|---|
| | 1075 | $set['defaultval'] =& $set['value']; |
|---|
| | 1076 | $set['readonly'] = 0; |
|---|
| | 1077 | $set['hidden'] = 0; |
|---|
| | 1078 | $set['level'] = 0; |
|---|
| | 1079 | $set['module'] = 'dashboard'; |
|---|
| | 1080 | $set['category'] = ''; |
|---|
| | 1081 | $set['emptyok'] = 1; |
|---|
| | 1082 | $set['description'] = 'Update rate in seconds of the Info section of the System Status panel.'; |
|---|
| | 1083 | $set['type'] = CONF_TYPE_UINT; |
|---|
| | 1084 | $freepbx_conf->define_conf_setting('DASHBOARD_INFO_UPDATE_TIME',$set); |
|---|
| | 1085 | |
|---|
| | 1086 | |
|---|
| | 1087 | // AMPMPG123 |
|---|
| | 1088 | // |
|---|
| | 1089 | $set['value'] = true; |
|---|
| | 1090 | $set['defaultval'] =& $set['value']; |
|---|
| | 1091 | $set['readonly'] = 0; |
|---|
| | 1092 | $set['hidden'] = 0; |
|---|
| | 1093 | $set['level'] = 0; |
|---|
| | 1094 | $set['module'] = 'music'; |
|---|
| | 1095 | $set['category'] = ''; |
|---|
| | 1096 | $set['emptyok'] = 0; |
|---|
| | 1097 | $set['description'] = 'When set to false, the MP3 files can be loaded and WAV files converted to MP3 in the MoH module. The default behavior of true assumes you have mpg123 loaded as well as sox and will convert MP3 files to WAV. This is highly recommended as MP3 files heavily tax the system and can cause instability on a busy phone system'; |
|---|
| | 1098 | $set['type'] = CONF_TYPE_BOOL; |
|---|
| | 1099 | $freepbx_conf->define_conf_setting('AMPMPG123',$set); |
|---|
| | 1100 | |
|---|
| | 1101 | |
|---|
| | 1102 | // |
|---|
| | 1103 | // NEW TO 2.9: |
|---|
| | 1104 | // |
|---|
| | 1105 | |
|---|
| | 1106 | |
|---|
| | 1107 | // DAYNIGHTTCHOOK |
|---|
| | 1108 | // |
|---|
| | 1109 | $set['value'] = false; |
|---|
| | 1110 | $set['defaultval'] =& $set['value']; |
|---|
| | 1111 | $set['readonly'] = 0; |
|---|
| | 1112 | $set['hidden'] = 0; |
|---|
| | 1113 | $set['level'] = 0; |
|---|
| | 1114 | $set['module'] = 'daynight'; |
|---|
| | 1115 | $set['category'] = ''; |
|---|
| | 1116 | $set['emptyok'] = 0; |
|---|
| | 1117 | $set['description'] = 'By default, the Day/Night module will not hook Time Conditions allowing one to associate a daynight manual override with a time condition since time conditions have their own feature code as of version 2.9. If there is already an associaiton configured (on an upgraded system), this will have no affect for the Time Conditions that are effected. Setting this to true reverts the 2.8 and prior behavior by allowing for the use of a daynight toggle to be associated with a time conditon. This can be useful for two scenarios. First, to override a Time Condition without the automatic resetting that occurs with the built in Time Condition overrides. The second use is the ability to associate a single daynight toggle with multiple time conditions thus creating a <b>master switch</b> that can be used to override several possible call flows through different time conditions.'; |
|---|
| | 1118 | $set['type'] = CONF_TYPE_BOOL; |
|---|
| | 1119 | $freepbx_conf->define_conf_setting('DAYNIGHTTCHOOK',$set); |
|---|
| | 1120 | |
|---|
| | 1121 | // TCINTERVAL |
|---|
| | 1122 | // |
|---|
| | 1123 | $set['value'] = '60'; |
|---|
| | 1124 | $set['defaultval'] =& $set['value']; |
|---|
| | 1125 | $set['readonly'] = 0; |
|---|
| | 1126 | $set['hidden'] = 0; |
|---|
| | 1127 | $set['level'] = 0; |
|---|
| | 1128 | $set['module'] = 'timeconditions'; |
|---|
| | 1129 | $set['category'] = ''; |
|---|
| | 1130 | $set['emptyok'] = 0; |
|---|
| | 1131 | $set['description'] = 'The polling interval in seconds used by the Time Conditions manintenace task, launched by an Asterisk call file used to update Time Conditions override states as well as keep custom device state hint values up-to-date when being used with BLF. A shorter interval will assure that BLF keys states are accurate. The interval should be less than the shortest configured span between two time condition states, so that a manual overide during such a period is properly reset when the new period starts.'; |
|---|
| | 1132 | $set['type'] = CONF_TYPE_SELECT; |
|---|
| | 1133 | $set['options'] = '60, 120, 180, 240, 300, 600, 900'; |
|---|
| | 1134 | $freepbx_conf->define_conf_setting('TCINTERVAL',$set); |
|---|
| | 1135 | |
|---|
| | 1136 | // TCMAINT |
|---|
| | 1137 | // |
|---|
| | 1138 | $set['value'] = true; |
|---|
| | 1139 | $set['defaultval'] =& $set['value']; |
|---|
| | 1140 | $set['readonly'] = 0; |
|---|
| | 1141 | $set['hidden'] = 0; |
|---|
| | 1142 | $set['level'] = 0; |
|---|
| | 1143 | $set['module'] = 'timeconditions'; |
|---|
| | 1144 | $set['category'] = ''; |
|---|
| | 1145 | $set['emptyok'] = 0; |
|---|
| | 1146 | $set['description'] = 'If set to false, this will override the execution of the Time Conditons maintenace task launched by call files. If all the feature codes for time conditions are disabled, the maintenance task will not be launched anyhow. Setting this to false would be fairly un-common. You may want to set this temporarily if debugging a system to avoid the periodic dialplan running through the CLI that the maintenance task launches and can be distracting.'; |
|---|
| | 1147 | $set['type'] = CONF_TYPE_BOOL; |
|---|
| | 1148 | $freepbx_conf->define_conf_setting('TCMAINT',$set); |
|---|
| | 1149 | } |
|---|
| | 1150 | |
|---|
| | 1151 | /* |
|---|
