[Version 1.3.10] 1) The Firewall configuration gui has been made easier to understand which fields are required for each action and protocol. Some javascript was added to enable/disable the address and port fields based upon the selected action and protocol. [Version 1.3.09] 1) Added a new feature that allows the fdisk-genunion-genkd operations to be performed via /admin/setup.php in the web interface. A new user would "dd" or physdiskwrite the .img to a CF card, boot and then... Type in the browser: (assuming Bonjour/mDNSResponder) https://pbx.local/admin/setup.php ...and follow the two steps. Currently, this automatic procedure gives the user a 'choice' of one drive (the Runnix drive) as the target. Both "Separate Unionfs and /mnt/kd/" and "Combined Unionfs and /mnt/kd/" format modes are supported. This feature also works from the command line: $ initial-setup status ok-format /dev/hda $ initial-setup format separate /dev/hda 128 $ reboot $ initial-setup configure /dev/hda $ reboot [Version 1.3.08] 1) The CDR Log tab has several new search options: Match Date-Time: Match CID Name: Match CID Num: Match Extension: Match Src Channel: The search text is simple (not ereg), case insensitive and can contain spaces as part of the match. [Version 1.3.07] 1) The OpenVPN configuration gui now supports automatic creation of server and client credentials utilizing a self-signed CA. 1a) Clicking "Create New" will generate the ca.crt, server.crt and server.key files. The server.crt has the 'nsCertType=server' parameter set. Additionally, the dh1024.pem will automatically be created the first time. 1b) Clicking "New Client" will generate the client_name.crt and client_name.key files signed by the self-signed ca.crt. 1c) Clicking "Download" generates a ZIP file containing client_name.crt, client_name.key and ca.crt credentials files for the selected client. Restarting OpenVPN will make the new credentials active. Note: The first time the server credentials are generated the dh1024.pem file is created. This one-time process can take a few minutes to complete, so be patient. Note: This requires PHP5 as configured in trunk-2241 and later. 2) The Network tab now supports automatic creation of the HTTPS Certificate File. If the check-box "Create New HTTPS Cert." is checked, a new self-signed certificate is created using the HOSTNAME as the commonName. The file is stored as /mnt/kd/ssl/webinterface.pem . A System Reboot is required for the new certificate to take effect. Note: This requires PHP5 as configured in trunk-2241 and later. 3) The OpenVPN configuration gui now has a "Cipher" menu. [Version 1.3.06] 1) The Reboot/Restart System (Network and System tabs) command used now adds a delay and executes in the background. This fixes a problem with changes in the reboot command in Busybox. This problem does not effect AstLinux 0.6 or earlier. 2) Status tab, "Disk Usage" filters better to only show physical drive status. [Version 1.3.05] 1) The Network tab supports a DMZ Internal Interface specification. The layout of the internal interfaces in the Network tab has been improved. If a DMZ interface is defined, a LAN interface must also be specified. 2) The Network tab now has some basic sanity checking. If after a sucessful [Save Settings] and the same interface was used to define two different subnets, an Error message is displayed. 3) The firewall gui has been enhanced to support creating arno firewall rules related to a DMZ. The new Firewall Rule Actions include: NAT EXT->DMZ Pass DMZ->Local Pass DMZ->LAN Deny EXT->DMZ Deny DMZ->EXT By default, DMZ hosts are totally blocked from the LAN and the AstLinux box itself. If DHCP is enabled on the NAT'ed DMZ subnet, the default DMZ firewall will block both DHCP and DNS to the local AstLinux box. (The DMZ requires "Pass DMZ->Local" UDP 53,67,68 for DNS-forwarding and DHCP to work.) Note that you may require an update to your /mnt/kd/arno-iptables-firewall/astlinux.shim file to enable DMZ support using the arno 1.8.8 firewall. http://lonnie.abelbeck.com/astlinux/astlinux.shim.tar.gz 4) The Prefs tab has additional Follow-Me Tab Options; "Dialed Number Context" and "Caller Music Class", defining the followme.conf entries "context=>" and "musicclass=>" respectively. If not defined, they use asterisk's default value of "default". Note that these values are only added when a new, non-preexisting extension is defined in the Follow-Me tab. Preexisting followme.conf extension values of "context=>" and "musicclass=>" will not be changed when the dial numbers change. This allows unique options for each extension for administrators with custom followme.conf files. [Version 1.3.04] 1) Yet more cosmetic layout fixes. [Version 1.3.03] 1) Added support in the Follow-Me tab for users choosing not to use the Asterisk FollowMe module. If the /etc/asterisk/followme.conf file is not found, then that file is not edited and the asterisk FollowMe module is not reloaded. In this situation the user's dialplan must handle all the Follow-Me dialing. 2) Previously when using the Firewall gui, undefined arno variables were set to a null string (""). Realizing this is somewhat futile, since there many variables in the arno firewall.conf file that are not used by the Firewall gui, now unused arno variables are simply not specified. It is now assumed that the underlying arno firewall.conf is an unedited, default configuration. 3) A new Prefs tab option: __ Exclude 4-digit Extensions in SIP/IAX2 Peer Status When checked, 4-digit extensions will be filtered out of the SIP/IAX2 Peer Status section. Actually, checking this option has been a standard feature of the web interface since the beginning, but after thinking about this, it should be an option, and disabled by default. 4) The Blacklist and Whitelist tabs' Action menus can now be defined via the Prefs tab; "Blacklist Menu" and "Whitelist Menu" in the "Caller*ID, Blacklist & Whitelist Tab Options" section. A list of tilde (~) seperated strings can be defined. The result will be a menu in the order of your defined list. Your first string is "0", second string "1", etc... This value is easily retrieved from the dialplan. 5) The Prefs tab now contains "Topic Info" icons at the bottom of the page where the various tabs can be marked to be shown. Clicking on the small icon yields a new window containing text, often example dialplans for the associated tab. 6) Some cosmetic layout fixes for browser compatibility. [Version 1.3.02] 1) A new Follow-Me tab has been added, hidden by default. The Follow-Me tab uses Asterisk's internal database (astdb) to maintain a list of Follow-Me numbers and their state. In particular, Asterisk 1.4 supports a Follow-Me application, which makes adding this feature into your dialplan about as easy as it gets. ---- /etc/asterisk/extensions.conf snippet ---- [macro-local-followme] exten => s,1,GotoIf($[${DB_EXISTS(followme/${ARG1})}=0]?nofollow) exten => s,n,GotoIf($[${DB_RESULT:0:1}=0]?nofollow:follow) exten => s,n(follow),Dial(SIP/${ARG1},20) exten => s,n,Followme(${ARG1},san) exten => s,n,Goto(s-${DIALSTATUS},1) exten => s,n(nofollow),Dial(SIP/${ARG1},20) exten => s,n,Goto(s-${DIALSTATUS},1) exten => s-NOANSWER,1,Voicemail(${ARG1},u) ; If unavailable, send to voicemail exten => s-BUSY,1,Voicemail(${ARG1},b) ; If busy, send to voicemail w/ busy ann exten => _s-.,1,Goto(s-NOANSWER,1) ---- /etc/asterisk/extensions.conf snippet ---- Warning! The Follow-Me tab uses the astdb database family "followme", be warned if you already use this in your dialplan! The tab may be safely viewed, but clicking [Save Changes] will write to the database. The Asterisk followme.conf file is automatically edited and the Asterisk app_followme.so application module is automatically reloaded. Note that the source database is astdb, so if you already have a followme.conf file, you will need to reenter your numbers into the Follow-Me tab. The Prefs tab has several options for the Follow-Me tab... 1a) Follow-Me Numbers Displayed: 1 - 6 The number of numbers available in the Follow-Me tab, defaults to 4. 1b) Schedule Menu: | Never~Skip Local Dial | The Schedule menu will appear in the Follow-Me tab if this text entry is defined. A list of tilde (~) seperated strings can be defined. The result will be a menu starting with "Always" and then followed in the order of your defined list. The value of "Always" is 0, your first string is 1, etc... This value is easily retrieved from a dialplan, but is not automatically supported by the Asterisk Follow-Me application. Another example... ---- /etc/asterisk/extensions.conf snippet ---- [macro-ring-inside] exten => s,1,GotoIf($[${DB_EXISTS(followme/${ARG1})}=0]?100) exten => s,n,Set(FM_OPTIONS=${CUT(DB_RESULT,~,1)}) exten => s,n,Set(FM_COUNT=${CUT(FM_OPTIONS,:,1)}) exten => s,n,Set(FM_SCHEDULE=${CUT(FM_OPTIONS,:,3)}) exten => s,n,GotoIf($[${FM_SCHEDULE}=1]?100) ; Never exten => s,n,GotoIf($[${FM_SCHEDULE}=2]?50) ; Skip Local Dial exten => s,n,GotoIf($[${FM_COUNT}=0]?100) ; Local Dial then Follow-Me then Voicemail exten => s,n,Dial(SIP/${ARG1},20) exten => s,n,Goto(50) ; Follow-Me then Voicemail exten => s,50,Followme(${ARG1},sn) exten => s,n,Voicemail(${ARG1},u) ; Local Dial then Voicemail exten => s,100,Dial(SIP/${ARG1},20) exten => s,n,Voicemail(${ARG1},u) ---- /etc/asterisk/extensions.conf snippet ---- 1c) Use Caller*ID Tab Number Format Rules for Follow-Me This option is checked by default, giving a sanity check to your phone number entries. The administrator can define the format rule or simply uncheck to disable this feature. All three security levels are supported by the Follow-Me tab: admin, staff and 'numbered' user. The non-admin 'numbered' user can only edit the status of their Follow-Me numbers. Finally, it is suggested in the Prefs tab to have _X_ Use Asterisk Manager Interface for Asterisk Commands checked, since the performance of the Follow-Me tab will be greatly improved. [Version 1.3.01] 1) Added support for Dynamic DNS Update in the Network tab. All fields must be specified for the Dynamic DNS client to be started. The current inadyn 1.96.2 has a problem with ZoneEdit using it's native support. The menu choice ZoneEdit [generic] uses inadyn's generic method which should work properly. 2) At the top of the Network tab, "Restart Dynamic DNS" is added, allowing the client to be restarted without rebooting the system. 3) In the "Advanced Configuration" section at the bottom of the Network tab a new feature allows either the /mnt/kd/dnsmasq.conf or /mnt/kd/dnamasq.static files to be edited. "Full DNS & DHCP Configuration" or "Additional DNS & DHCP Configuration" respectively. 4) At the top of the Network tab, "Restart DNS & DHCP" is added, allowing DNSMasq server to be restarted without rebooting the system. 5) The Edit tab now has the ability to restart processes just as the Network tab. This allows a text file to be edited and the associated process to be restarted without leaving the Edit tab. [Version 1.3.00] 1) Fixed a problem in the Firewall gui where if "NAT EXT->LAN" contained a source address of 0/0 the rule would not be generated properly within the arno firewall. Workaround for 1.2.08 users (AstLinux 0.6.2): In the Firewall gui, "NAT EXT->LAN" Source: is to use 0.0/0 for all hosts instead of 0/0 2) Added support for arno firewall version 1.9.x . The version of the arno executable script is used to automatically support both arno firewall 1.8.8 and 1.9.x . 3) The [Edit Firewall Config...] gui now includes a "Traffic Shaping" section provided the "traffic-shaper" arno plugin is installed. Both "htb" and "hfsc" types are supported. AstLinux Traffic-Shaper arno plugin: http://lonnie.abelbeck.com/astlinux/traffic-shaper-plugin.tar.gz (extracts traffic-shaper.plugin and traffic-shaper.conf file in place) [Version 1.2.08] 1) Tagged to AstLinix 0.6.2 2) Yet another enhancement to the arno firewall gui. A new "Firewall Options" section offers several check-box options related to ICMP and logging. 3) System Firmware Upgrade: A new feature beginning with AstLinux 0.6.2 allows firmware upgrades of the run-image via the System tab. Check for New, Upgrade with New, Show Installed, and Revert to Previous (Firmware) are the available options. The goal is to automatically maintain two run-images. The "System Firmware Upgrade" repository can be a private or trusted public URL. The Prefs tab allows the Repository URL to be specified. The file format of the repository is described below for three example platforms for the "astlinux-0.6.2" run image: ./net5501/ver ./net5501/astlinux-0.6.2.tar.gz.sha1 ./net5501/astlinux-0.6.2.tar.gz ./via/ver ./via/astlinux-0.6.2.tar.gz.sha1 ./via/astlinux-0.6.2.tar.gz ./via-serial/ver ./via-serial/astlinux-0.6.2.tar.gz.sha1 ./via-serial/astlinux-0.6.2.tar.gz where: echo "astlinux-0.6.2" > ver After an upgrade is successful, the system must be rebooted for the new run-image to be made active. By default, the previous run-image is saved and can "Revert to Previous" if desired. [Version 1.2.07] 1) An enhancement to the new arno firewall support, firewall plugin config file support. In the Network tab, a new "Firewall Plugins" feature lists all available .conf files in a menu-list, as well as indicating the Enabled/Disabled status. Select a plugin to configure, then click on the [Edit Plugin Config...] button to edit the plugin config file. Setting the ENABLE= variable determines if the plugin is used. Either of two directories can be used for the .conf files, in this order... First: /mnt/kd/arno-iptables-firewall/plugins Second: /mnt/kd/arno-firewall [Version 1.2.06] 1) A new feature allows the arno firewall to be edited with a gui. This feature requires astLinux version 0.6 and later, or builds since June 2008. One or more internal interfaces must be defined for the firewall to be active. The Network tab has a new section... Firewall Configuration: Arno Firewall: [Edit Firewall Config...] When the [Edit Firewall Config...] button is selected, the Firewall Configuration is shown. After firewall rules are defined and saved, the [Restart Firewall] button will make the rules active without the need to reboot the system. Clicking the the [ + ] at the left of each rule will load the input fields with that rule's values. Make changes and then [Save Settings]. The original rule will remain, if that is not desired, simply delete the original rule. Any firewall rule may be 'Disabled' without deleting, by checking the box under the Disabled column, and then click [Save Settings] and then [Restart Firewall]. Remember that new firewall rules are not applied until after a [Restart Firewall]. Be sure to test each firewall rule before it is placed into production. 2) The previous Network tab "Firewall Type" has been removed. By default the FWVERS variable is set to "astfw", so the Advanced Configuration section of the Network tab may be used to define any of the related "astfw" firewall settings. Note that if the [Edit Firewall Config...] button is selected AND then [Save Settings] is clicked, then a gui.firewall.conf file is created with FWVERS="arno", thereby enabling the arno firewall. [Version 1.2.05] 1) The Network tab now allows a 2nd and 3rd internal network interface to be defined. Note: If you previously defined theses variables in the Advanced/User System Variables section, be sure to remove them so the Network tab values won't be overidden. [Version 1.2.04] 1) Fixed a problem with the Monitor Tab if a filename contained URL special characters. [Version 1.2.03] 1) The CDR Log tab has a new option menu under "Download Call Detail Records". The new menu contains [Formatted] and [Raw CDR]. The default [Formatted] selection acts as it did previously. The new [Raw CDR] selection downloads raw (not formatted) records that match the date range selected. 2) The Prefs tab has a new option in the "CDR Log Tab Options" section. ___ Display [disposition] CDR value When checked, the chosen CDR value will be additionally displayed in the CDR Log tab. Note: This option does not apply to the "Special cdr-custom" log format. 3) Increased 'maxlength' of a few Network tab text entries. [Version 1.2.02] 1) The Prefs tab has a new option under "System Tab Options" _X_ Backup tar archives compressed with gzip [.gz] When checked (the default), all backup tar archive sets (and optional unionfs partition backup) will be be compressed using gzip, creating a .tar.gz archive. When unchecked, no compression will be used, creating a .tar archive. This is much faster, but results in larger backup files. Users will most likely want to also check: _X_ Backup temporary file uses /mnt/kd/ instead of /tmp/ when gzip compression is not used. Note: This gzip option also appiles to the optional unionfs partition backup, if not checked, the unionfs partition is saved as /mnt/kd/asturw.tar with no gzip compression. 2) The System tab has a new item in the "Download Backup" menu, "Non-/mnt/kd/ unionfs files" When chosen, only the non-/mnt/kd/ asturw files will be downloaded, reguardless of the value of the Prefs tab "Backup unionfs partition..." value. 3) If either the /mnt/kd/asturw.tar or asturw.tar.gz file is generated for the backup, the file will be automatically deleted after the backup is completed. 4) Fixed a button width issue with FF 3 and Linux [Version 1.2.01] The Prefs tab has a new option under "System Tab Options" ___ Backup unionfs partition as /mnt/kd/asturw.tar[.gz] When checked, the unionfs partition archive is saved under /mnt/kd/, then when a backup set [All...|Core...|All Except...] in the System tab is chosen, the unionfs archive is included in the backup. Note: The resulting tar archive is created to extract in-place. To restore the non-/mnt/kd/ unionfs data, type: tar xzvf /mnt/kd/asturw.tar.gz -C /oldroot/mnt/asturw/ or tar xvf /mnt/kd/asturw.tar -C /oldroot/mnt/asturw/ and then reboot to allow unionfs to use the updated files. [Version 1.2.00] 1) A minor fix to the 1.1.05 countdown feature. When the countdown is finished, the user is redirected to the Status tab. If the Status tab took more than 1 second to load, the browser would try again, and again, every second. The redirection now only tries once. If the Prefs tab option "Use Asterisk Manager..." is checked, the Status tab will load in less than a second, so the multi-reload issue does not occur. (see the 1.0.05 feature to overcome slow asterisk command execution) [Version 1.1.08] 1) Tagged to AstLinix 0.6.1 2) The /mnt/kd/rc.conf.d/user.conf file is now always automatically created. Often this file will not have any variable definitions, but instructive comments are included to help define the purpose of this file. 3) The Network tab has a new "Advanced Configuration" section. The "User System Variables" has a button [Edit User Config...], when clicked, the user.conf file is edited. With this addition, any/all of the system configuation variables can be specified from the Network tab. 4) The Prefs tab General Options: "External URL Link" has a new feature. If the URL contains the string "://localhost" then this special case will replace the "localhost" string with the hostname the user's browser is currently using to access altweb. For example, if you use https://my.public.tld/status.php to access altweb, you can specify http://localhost:8088/asterisk/ as the "External URL Link" will expand to http://my.public.tld:8088/asterisk/ in the href= link. If a port number exists in both the browser and ://localhost:NNNN in the "External URL Link" the "External URL Link" port number NNNN has precedence. [Version 1.1.07] Previously, the /mnt/kd/rc.conf.d/user.conf file was automatically created with any variables that were defined in the current /etc/rc.conf that were not defined in /mnt/kd/rc.conf.d/gui.network.conf file. This only occurs when there is no rc.conf.d/ directory and the user clicks "Save Settings" in the Network tab, thereby creating the rc.conf.d/ directory. As such, any variable definitions beginning with IPSEC_ and OVPN_ would previously be added to the user.conf file. This version properly places variables beginning with IPSEC_ to the gui.ipsec.conf file and variables beginning with OVPN_ to the gui.openvpn.conf file. [Version 1.1.06] 1) Support Philip's latest IPsec tweaks. 2) Allow both IPsec and OpenVPN tunnels at the same time. (Requires Philip's trunk-1956 revisions or branches-0.6-1958) The VPN section of the Network tab has changed from version 1.1.03. Each VPN type now has a checkbox (enabled or not) and a button to edit the VPN configuration. [Version 1.1.05] When the system is rebooted, a few lines of JavaScript shows a countdown during a reboot. System is Rebooting... back in 135 seconds. After the countdown is complete, the Status tab is automatically displayed. The default value of the countdown time is 135 seconds, if that is too short it can be increased or provided as a Prefs option if users see that need. [Version 1.1.04] The Network tab "Reboot/Restart" button now has a menu to allow different processes to be restarted. Reboot System Restart PPPoE Restart NTPd Restart IPsec Restart OpenVPN Restart Asterisk Any configuration changes with a "Save Settings" will be used when the process is restarted. The PPPoE restart code has been made more robust. Please report any problems. [Version 1.1.03] The Network tab supports new functions. 1) NTP Server: [Edit NTP Config...] button. If the file /mnt/kd/ntpd.conf exists this button appears. When clicked the Edit tab is invoked with the ntpd.conf file to be editied. 2) VPN Type: [Edit VPN Config...] button. Both IPsec and OpenVPN configurations are now supported. After selecting a "VPN Type", clicking "Edit VPN Config..." will present a dialog to manage the VPN configuration. The /mnt/kd/rc.conf.d/ files are gui.ipsec.conf and gui.openvpn.conf . If you had VPN variables set in your /mnt/kd/rc.conf.d/user.conf previously, be sure to edit your user.conf and remove those entries. For OpenVPN, if the file /mnt/kd/openvpn/openvpn.conf exists, the Edit tab is invoked with the openvpn.conf file to be editied. Note: Restarting either IPsec or OpenVPN requires AstLinux 0.6 or recent trunk builds. [Version 1.1.02] 1) CDR Log tab searching text has been enhanced. The "Search For Text" action now allows multiple patterns to be matched by OR'ing (|) or AND'ing (&). For example, a search action of "dog|cat" finds all CDR's that contain "dog" OR "cat". A search action of "dog&cat" finds all CDR's that contain "dog" AND "cat". All searches are case-insensitive, and obey basic regular expression rules. Two helper actions are added "Match All Words", and "Match Any Words"; in each case words seperated by a space delimiter will issue the proper search. Additionally, the | and & delimiters can be used, but "Match All Words" will replace any delimiter with & and "Match Any Words" will replace any delimiter with a | . This allows switching from one to the other without changing the search patterns. Note: Both &'s and |'s cannot occur within a single search string. 2) Edit tab now allows any writeable /mnt/kd/*.conf file to be edited, including a useful description for the common ones. Additionally, the /mnt/kd/ files; ethers, hosts and dnsmasq.static can be editied if they exist. 3) System tab, "View System Files" now includes any readable /etc/*.conf file. [Version 1.1.01] 1) A new Prefs tab option, under "Status Tab Options:" ___ Require Authentication for Status Tab When unchecked (the default), anyone can view the Status tab. When checked, only authenticated users can view the Status tab. Authenticated users include "admin", "staff" and "NNNN" (numbered user). [Version 1.1.00] 1) First public release in AstLinux 0.6 [Version 1.0.08] 1) Speed Dial 'prefix' defined in the Prefs tab has been increased to a max of 8 characters. 2) When the asterisk manager interface (AMI) is used to communicate with asterisk, informative error messages are displayed if the AMI connection fails. 3) Status tab displays error message if asterisk is running but can't communicate via AMI. [Version 1.0.07] 1) Prefs tab, system location of 'prefs' data, now has two possible locations. By default, at the base of the web directory ($HTTPSDIR), the file prefs.txt contains the 'prefs' data. Optionally, at the base of the keydisk directory (/mnt/kd/), the file webgui-prefs.txt contains the 'prefs' data. If the /mnt/kd/webgui-prefs.txt file exists, it will have priority and be used. Placing the 'prefs' data in the /mnt/kd/ directory has the advantage that standard backups via the Stytem tab will backup the webgui-prefs.txt file. Additionally, this removes the prefs.txt from being viewed via a browser, not that any sensitive data is stored in this file. [Version 1.0.06] 1) Status tab, added AstLinux Release and Asterisk version. 2) Status tab, prettified basic information. Note: A new style class was added, your browser may cache the previous style sheet, so reload (or SHIFT-reload) your browser of the top status area does not have a box around it. [Version 1.0.05] 1) A new Prefs tab option, under "Status Tab Options:" ___ Use Asterisk Manager Interface for Asterisk Commands When unchecked (the default), the system shell uses "asterisk -rx ..." calls to issue commands to asterisk. When checked, the asterisk manager interface (AMI) is used to issue commands to asterisk, using user/password 'webinterface'. Using the asterisk manager interface requires the /etc/asterisk/manager.conf file to be properly configured. Note that only connections from localhost to localhost are allowed in the snippet below. ---- /etc/asterisk/manager.conf snippet ---- [general] enabled = yes port = 5038 bindaddr = 127.0.0.1 ; Web interface localhost user for AstLinux ; [webinterface] secret = webinterface deny=0.0.0.0/0.0.0.0 permit=127.0.0.1/255.255.255.255 read = command write = command ---- /etc/asterisk/manager.conf snippet ---- For changes to the manager.conf to be applied, reboot/restart the system. [Version 1.0.04] 1) The CDR Log tab, "Display Call Detail Records" has an action menu including "Last Entries" (as before) and "Text Search" (new). The "Text Search" does a 'grep -i "string"' of the raw Master.csv file to determine which lines are displayed. Display results are limited to 1000 entries as a sanity limit. 2) The CDR Log tab, a major rewrite of how Master.csv files are parsed and which format they were generated with. 3) The Prefs tab now allows three CDR Log Format's: [Standard cdr-csv] The standard default format logged to /var/log/asterisk/cdr-csv/Master.csv. [Default cdr-custom] The default format described in the cdr_custom.conf file, commented-out by default. (Yes, it is different from the [Standard cdr-csv]) [Special cdr-custom] The previous default setting, simple format, documented in the help pages. If you were using this format, you will have to re-select this in the Prefs tab since the default has changed. 4) The CDR Log Path: now defaults to /var/log/asterisk/cdr-csv/Master.csv and CDR Log Format: [Standard cdr-csv]. [Version 1.0.03] 1) The System tab "View System Files" has two new entries near the top. system: Default Variables system: /stat/etc/rc.conf When either is chosen, the /stat/etc/rc.conf file is displayed. [Version 1.0.02] 1) The Status tab now includes a "Disk Usage" section. This can be hidden via a Prefs tab option. 2) The Status tab now displays a "GUI Version:". Additionally, the download site automatically displays the current version number. Added: common/version.php 3) A new Prefs option under System Tab Options: __ Backup temporary file uses /mnt/kd/ instead of /tmp/ unchecked by default. When checked, the tar temporary file is prefixed with "/mnt/kd/." such that it won't be listed with the "ls -1" which is passed to tar to generate the input list. This feature allows tar backups greater than 10MB, the default /tmp/ size. [Version 1.0.01] 1) The System tab now offers multiple backup sets to choose from under "Configuration/File Backup:". Please suggest any other backup sets and I will add them. Note: The resulting tar archives are created to extract in-place. For example, if you have a backup named "pbx-core-2008-08-09.tar.gz" and want to restore the data, simply ftp the file to your system and type: tar xzvf pbx-core-2008-08-09.tar.gz -C /mnt/kd/ 2) The Network tab has removed TFTPDOPTIONS and FTPDOPTIONS definitions since they are not longer supported in future AstLinux versions. If a /mnt/kd/vsftpd.conf file exists, the gui silently sets FTPDOPTIONS=/mnt/kd/vsftpd.conf to support current and previous versions of AstLinux. If users need to set these variables to anything else, add them to /mnt/kd/rc.conf.d/user.conf 3) The Speed Dial tab now accepts an optional "Name" entry. Up to 100 speed dial entries can now be defined (still defaults to 50). The Prefs tab allows the user to set the digits from "00 to 09" through "00 to 99". The extension number can be clicked to load it's values for easy updating or used as a template for another speed dial number. 4) A new Directory tab displays the Speed Dial "Names" and extensions. If the Speed Dial entry does not have a "Name", it will not appear in the Directory tab. This tab requires no authentication, like the Status tab. Added: directory.php 5) In the Prefs tab -> General Options: Two new options... "External URL Link:" and "External URL Name:". The link with name will appear in the upper-right corner of all altweb screens. The link is passed to the html anchor href=, it could point to local/remote help files, support website, mailto address, asterisk-gui link, etc. 6) Both NTPSERV and NTPSERVS is supported in the Network tab. Multiple ntp servers should be space separated. 7) Fixed PHP redirect issue. Previously, I redirected using php's $_SERVER['SERVER_NAME']. Now, I redirect using $_SERVER['HTTP_HOST']. This should allow either a DNS-name or a numeric-IP to be entered in the browser. 8) A Users tab as been added which provides Voicemail Users Management. The asterisk voicemail.conf file is edited via the web-gui. Additionally, web-gui usernames/passwords (admin/.htpasswd) are automatically generated/deleted to match asterisk's VoiceMailMain() passwords. 9) Voicemail "externpass=" script: http://lonnie.abelbeck.com/astlinux/ast-vmpass.txt The script above should keep the web-gui .htpasswd file sync'ed to the voicemail.conf file when a voicemail user manually changes his/her password from a phone via asterisk's VoiceMailMain(). In the online documentation (link below) see the "Voicemail Users:" section for installation instructions. 10) Support for "externnotify=" voicemail.conf variable. When using the Voicemail tab, and while changes to the inbox occur, if this variable is defined in the voicemail.conf file, this script is executed. Additionally, the Prefs tab option "Enable Voicemail External Notify Script" must be checked for this feature to be enabled. 11) New "staff" user authentication. The System tab now allows both "admin" and "staff" user passwords to be changed, and no longer resets the .htpasswd file, but rather edits the file keeping other defined users intact. Authentication Summary: A) "admin" authentication; ALL tabs are available. B) "staff" authentication; Status, Directory, Voicemail, Monitor, CDR Log, Speed Dial, Caller*ID, Blacklist, Whitelist and Users tabs are available. C) "NNNN" (numbered user) authentication; Status, Directory, Voicemail and Monitor tabs are available. The htpasswd shell command is no longer required to add users. [pre-Version 1.0.01] // directory.php for AstLinux // 08-06-2008 // // phone-dir.php for AstLinux // 08-06-2008 // // Usage: https://pbx/phone-dir.php?type=generic // type= generic, polycom // // status.php for AstLinux // 03-01-2007 // 01-15-2008, Added ntpq support // 01-21-2008, Added core show channels support // 02-13-2008, Improved ntpq display format // 03-31-2008, Reworked system stats, ntpd and syslog sections // 04-08-2008, Added Preferneces Support // 04-10-2008, Added Password Warning // 04-12-2008, Added PPPoE Status // 04-18-2008, Changed System Time to use PHP date // 08-10-2008, Added Disk Usage and GUI Version // // blacklist.php for AstLinux // 03-24-2008 // // cdrlog.php for AstLinux // 03-28-2008 // 04-13-2008, Add user defined logfile location // 06-04-2008, Add Darrick Hartman's extra columns w/ Prefs option // 06-04-2008, Change CDR.csv to not be a binary image of Master.csv // 06-06-2008, Add filter by date for download CDR.csv // // cidname.php for AstLinux // 03-24-2008 // // edit.php for AstLinux // 04-28-2008 // // monitor.php for AstLinux // 04-15-2008 // 04-25-2008, Added inline wav // 06-05-2008, Added multi-user support // // network.php for AstLinux // 04-04-2008 // 04-08-2008, Added Network Services // 04-22-2008, Added user.conf generation // 08-01-2008, Added tftpd - dnsmasq option // 08-05-2008, Added NTPSERVS support // 08-07-2008, Added HTTPUSER and HTTPSUSER support // 08-07-2008, Removed TFTPDOPTIONS and FTPDOPTIONS support // // prefs.php for AstLinux // 04-06-2008 // 04-20-2008, Never-ending Additions // // sysdial.php for AstLinux // 03-24-2008 // 04-12-2008, Added Extension Prefix // // system.php for AstLinux // 03-26-2008 // 04-02-2008, Added rc.conf display // 04-09-2008, Added view file // 07-29-2008, Added staff password generation // 08-09-2008, Added multiple backup sets // // view.php for AstLinux // 04-09-2008 // // voicemail.php for AstLinux // 04-20-2008 // 06-04-2008, Added multi-user support // 07-20-2008, Added special user "staff" permissions // 07-21-2008, Added externnotify support // // whitelist.php for AstLinux // 04-12-2008 // // functions.php for AstLinux // 03-25-2008 // 04-02-2008, Added parseRCconfig() // 04-03-2008, Added getETHinterfaces() // 04-04-2008, Added getVARdef() // 04-10-2008, Added getTITLEname() // // header.php for AstLinux // 03-25-2008 // // insert-wav-inline.php for AstLinux // 04-26-2008 // // result.php for AstLinux // 03-25-2008 // // version.php for AstLinux // 08-10-2008