Update to IPBrick v6.4. December 19, 2018

Transcription

1 Update to IPBrick v6.4 December 19, 2018

2 Contents 1 Introduction 3 2 Migrating an IPBrick v6.3 to Installation on an IPBrick with High Availability (HA) Migrating an IPBrick v6.2 to v Migrating an IPBrick v6.1 to v Migrating an IPBrick v6.0 to v Migrating from IPBrick versions previous to v Migration using IPBrick automatic installation DVD Before starting Reinstall server and replace configurations Reinstall Server Replacing IPBrick Configurations Applications Disaster Recovery Upgrade Applications after Disaster Recovery Important Notes VoIP Service UCoIP Page - Video Calls VoIP Statistics Management Archive and Restore Server Character encoding Software RAID

3 1 Introduction This document presents the migration process from previous IPBrick versions to IPBrick v Migrating an IPBrick v6.3 to 6.4 Migrating an IPBrick v6.3 to v6.4 is very simple: Install all available updates from our eshop for v6.3 (from 1 to 3) plus the security updates (1 and 2) and your IPBrick will migrate to version 6.4. VERY IMPORTANT: If there s iportaldoc in the IPBrick where this update is going to be installed, it s imperative that iportaldoc is updated to the last version. 2.1 Installation on an IPBrick with High Availability (HA) 1. When the resources are in the main node of the HA cluster, you must disable the configuration synchronization in the secondary node (if it is enabled). On Advanced Configurations IPBrick High Availability: 2. Install the updates by the following order and apply configurations when you are finished: update 01 v6.3 security_update 01 v6.3 security_update 02 v6.3 update 02 v6.3 update 03 v Repeat the procedure described in 1 and 2, in the main node. 4. Validate if the resources are in the main node of the HA cluster. If the resources are in the secondary node, please takeover the resources in the main node. 5. Enable the configurations synchronization again. In the secondary node, enable the synchronization and apply configurations. Wait for the process to end. On Advanced Configurations IPBrick High Availability: 3

4 6. In the main node, enable the synchronization again and apply configurations. 7. To confirm that the cluster is synchronized, access to the web interface of the secondary node and check that the last applied configuration was executed by the user Administrator high-availability. On Advanced Configurations IPBrick Disaster recovery Configurations Replace: 3 Migrating an IPBrick v6.2 to v6.4 To migrate an IPBrick v6.2 to v6.4 you first need to migrate it from v6.2 to v6.3 and then you can migrate it from v6.3 to v6.4, as it follows: Migrate an IPBrick v6.2 to v6.3: Install all available updates from our eshop for v6.2 (from 1 to 6), plus the security updates (from 1 to 4), and your IPBrick will migrate to version 6.3; Migrate an IPBrick v6.3 to v6.4: Follow the instructions presented on chapter 2 Migrating an IPBrick v6.3 to v Migrating an IPBrick v6.1 to v6.4 To migrate an IPBrick v6.1 to v6.4 you first need to migrate it from v6.1 to v6.2, then from v6.2 to v6.3 and, finally from v6.3 to v6.4, as it follows: Migrate an IPBrick v6.1 to v6.2: Install all available updates from our eshop for v6.1 (from 1 to 6), plus the security updates (1 and 2), and your IPBrick will migrate to version 6.2; Migrate an IPBrick v6.2 to v6.3: Follow the instructions presented on chapter 3 Migrating an IPBrick v6.2 to v6.4. Migrate an IPBrick v6.3 to v6.4: Follow the instructions presented on chapter 2 Migrating an IPBrick v6.3 to v6.4. 4

5 5 Migrating an IPBrick v6.0 to v6.4 If you currently have an IPBrick v6.0 and you want to migrate it to v6.4, first you need to migrate it to v6.1, second from v6.1 to v6.2, then from v6.2 to v6.3 and, finally, from v6.3 to v6.4. Follow the steps: Migrate an IPBrick v6.0 to v6.1: Install all available updates from our eshop for v6.0 (from 1 to 4) plus the security updates (from 1 to 3) and your IPBrick will migrate to version 6.1; Migrate an IPBrick v6.1 to v6.2: Follow the instructions presented on chapter 4 Migrating an IPBrick v6.1 to v6.4 ; Migrate an IPBrick v6.2 to v6.3: Follow the instructions presented on chapter 3 Migrating an IPBrick v6.2 to v6.4 ; Migrate an IPBrick v6.3 to v6.4: Follow the instructions presented on chapter 2 Migrating an IPBrick v6.3 to v Migrating from IPBrick versions previous to v6.0 You can only upgrade your system from previous versions of IPBrick v6.0, through an Upgrade/Reinstallation with the new ISO! The next section presents you with the necessary procedure. 7 Migration using IPBrick automatic installation DVD 7.1 Before starting Before starting the migration to v6.4, there are some previous requirements that must be taken into account: Backup server data: The IPBrick installation DVD detects a previous installation and ensures the backup of all data. However, and regardless of this, it is advisable to have a full backup of your server data; Available disk space: IPBrick v6.4 Installation DVD will validate the refered values. Be sure to check if your installed applications, such as Callcenter, iportaldoc, Hotspot, LIVE, etc., are compatible with IPBrick v6.4 (if you re not sure, please contact support.install@ipbrick.com); Request the new IPBrick v6.4 configuration. Send the last IPBrick configuration to support.install@ipbrick.com and request migration to IPBrick v6.4. IMPORTANT!: Please don t forget to wait for our reply! You will receive, as soon as possible, the respective configuration file. It s possible that, for older versions of IPBrick, 5

6 the migration may not be executed directly. You may need to first update to an intermediate version and only then to IPBrick v6.4. In these situations, we will inform you about any restrictions and how to proceed. For any doubts or questions, please contact us: If all previous steps are fulfilled, then you may proceed with the update to IPBrick v Reinstall server and replace configurations Assuming all previous conditions are met (as stated in section Before starting), you may now proceed with the installation of the server using the IPBrick v6.4 installation DVD Reinstall Server Since this is a migration procedure, you should select the Upgrade/Reinstall option on the IPBrick v6.4 Installation DVD Replacing IPBrick Configurations After installing, please follow the next steps: Initial configuration: When the reinstallation is performed on an IPBrick with Slave/ Client/ AD Member authentication type, it s recommended to manually configure the new IPBrick installation with the same IP, name and domain of the IPBrick that is being reinstalled. This operation aims to provide network connection between the IPBrick Slave/ Client/ AD Member and the IPBrick Master/ AD Server during the replacement of configurations. Access to IPBrick s web interface and upload the migrated configuration file that you have received from us by on: Advanced Configurations Disaster Recovery Configurations Upload Replace the configurations for v6.4 by selecting the uploaded file on: Advanced Configurations Disaster Recovery Configurations Replace 7.3 Applications Disaster Recovery Now that you have reinstalled IPBrick and replaced its configurations, you may now start to execute the Applications Disaster Recovery: Go to Advanced Configurations Disaster Recovery Applications Restore; 6

7 Select the respective applications backup and restore it. IMPORTANT NOTE: IPBRICK will REBOOT after the restore procedure is concluded! TIP: You may access to IPBRICK logs on: Advanced Configurations System Monitoring Logs IPBrick Logs This way you will be able to check the restore procedure. Take into consideration that this process may take a while, depending on the amount of information contained in the Databases. 7.4 Upgrade Applications after Disaster Recovery If there s iportaldoc in the IPBrick where this update is going to be installed, it s imperative that iportaldoc is updated to version or greater. 8 Important Notes The following notes regard certain and specific aspects of the migration procedure, and they require your immediate attention. 8.1 VoIP Service In previous IPBrick iterations, the VoIP service had two main ports: 5060 and Since IPBrick v6.1 there is no need for the 5090 port. Needless to say that, if you have a great number of phones using 5090, without auto provisioning, you will not need to reconfigure them manually! They will still be functional by using that same port. But, we strongly advise you to gradually switch to a centralized VoIP service on port 5060 (and 5061, if you wish to use TLS encryption), due to the fact that you will greatly enhance your system s security and operability. 7

8 8.2 UCoIP Page - Video Calls The video call feature on IPBrick is implemented by WebRTC, which is an open-source web-based application technology that allows users to make real time communications using a browser. The supported browsers are Google Chrome (recommended), Firefox and Opera. Due to some security requirements, it s necessary to guarantee the following configurations: IPBrick must have a valid SSL certificate for the services Web Server (HTTPS) and WebRTC (Web Real-Time Communication). This configuration is available on: Advanced Configurations IPBrick Certificates. The web site for UCoIP Pages, ucoip.<domain> must only be set with HTTPS protocol. Check this configuration on: UCoIP Web Server. The default UCoIP Page, ucoip.<domain> must be available on the Internet. For this requirement, the DNS record ucoip.<domain> must be configured on the public DNS. This configuration is necessary to access UCoIP Pages with the URL format which is a requirement when the login of the Users has the special character. (ex: john.smith). A WebRTC Proxy was added on IPBrick to enable external users, behind firewalls with restriction policies, to make video calls using the users UCoIP Page. To enable this feature on the internet, the DNS record webrtcproxy.<domain> must also be configured on the public DNS! For more information on this subject, please consult our wiki page at: VoIP Statistics Management This feature allows to keep calls records on IPBrick. To access it, go to Advanced Configurations Telephony Configurations. In order not to overload the database with unnecessary records, at the time of the installation of update05-v6.1 this option will be enabled and it will operate by default as follows: 8

9 The last 12 months will be kept on VoIP Statistics Database (voipstats) and every record previous to those 12 months will be archived. Please note that the last 12 months of call statistics include the current month plus the previous 11 months. If you wish, you can change the number of months, always taking into account that it will keep the current month plus the previous x months, on database. The job responsible for the database maintenance will run everyday at 5 a.m. searching for records previous to those 12 months. The archive will only be done whenever it finds an entire month of records. If you wish, you may modify the job execution time so it becomes more convenient for your scenario. Archived records, by default, will not be deleted. If you wish there s an option that can be configured to delete archived files older than x months. Remember that this option only allows to delete archived records and not records from the current VoIP Statistics Database. Example: If today is the 12 th of May of 2016, VoIP Statistics Database will have records since the 1 st of June of 2015 until the 12 th of May of The records from June 2015 will only be archived at 5 a.m. of the 1 st of June of 2016, since this feature keeps searching until it finds a whole month of call records statistics to archive. Note: After the installation is completed you may manage these configurations as it better suits your needs Archive and Restore You can also manually archive and restore call records statistics through the option Manual Operations, also available on Advanced Configurations Telephony Configurations. By default, as shown in the image above, the last 12 months of records are present on VoIP Statistics Database (voipstats). You may perform as it follows, regarding to: Archive records: remove the checkbox selection concerning the months you want to archive, click on Modify and the records will be removed from the VoIP Statistics Database and automatically archived. Restore records: select the month(s)/year(s) of the records that you want to restore, click on Modify and they will be automatically restored to the current VoIP Statistics Database (voipstats). 9

10 Note: When accessing to this interface, the selected checkboxes correspond to the records you currently have available on VoIP Statistics Database Server To improve security on the server, a new option was added to the anti-virus to block dangerous attachments. This option is enabled by default! This new feature blocks only attachments with compressed files such as 7z, Rar, Zip, Arj, Cab, whenever they have the following executables inside: ade, adp, bat, chm, cmd, com, cpl, exe, hta, ins, isp, jse, lib, mde, msd, msp, mst, pif, scr, sct, shb, sys, vb, vbe, vbs, vxd, wsc, wsf, wsh. This configuration is available on: Security Relay Anti-Virus ClamAV. 8.5 Character encoding Another important aspect is the change in the file system character encoding set in IPBrick v6.0, v6.1 and v6.2 from ISO-8859 to UTF8. If there is an addition of a new machine to the system and the backup data is copied from the old to the new machine, conflicts may arise from this fact. As stated, IPBrick v6.0, v6.1 and v6.2 default file system character encoding is UTF8. In previous versions of IPBrick, the default encoding was ISO This means that when there s a migration from these older versions, your file system will remain encoded in ISO However, there s a possibility to alter the file system encoding on the graphic user interface of IPBrick. Simply access: Advanced Configurations Support Services File Server And alter the default character encoding to UTF8. NOTE: Take notice that this transition may not be completely error free and that some strange characters may appear due to the different encoding. 10

11 8.6 Software RAID If you have software RAID enabled, before the installation process, you must create another file called system.cfg in the pendrive root path. Next, the structure is presented along with the explanation: CONFIGSOFTRAID=1 -> Activates the software RAID SOFTRAIDHDD[0]="sda" -> It s the disk 1 device SOFTRAIDHDD[1]="sdb" -> It s the disk 2 device SOFTRAIDPARTSUF="p" -> Do not change! RAIDTYPE=1 -> It s the RAID type. Only this raid type is supported! You must know specifically the correct designation of hard drives devices before the file creation, which depends of the used technology: IDE, SCSI, SATA etc. NOTE: RAID installation requires the system.cfg file, available at our eshop on: IPBRICK Installation Manuals. 11