- Administration Guide
- Hardware requirements
- Installation
- Ansible-based installation on Linux
- VMWare OVA template-based installation
- Deploying MiaRec on Amazon AWS (up to 2,000 users)
- 1. Network architecture
- 2. Create VPC
- 3. Create EC2 instances
- 4. Configure Elastic IP address
- 5. Install MiaRec software on EC2 instance
- 6. Configure Route 53 DNS Failover for web traffic
- 7. Configure DNS SRV for SIPREC traffic
- 8. Configure SIPREC recording
- 9. Configure automatic file relocation to Amazon S3
- 10. Configure MiaRec replication
- 11. Configure HTTPS for web server
- 12. Configure CloudWatch monitoring
- 13. Disaster recovery plan
- Installation on Windows
- Update
- Post-installation tasks
- Phone system integration
- Avaya Aura call recording
- Avaya SBCE SIPREC call recording
- 01. How it works
- 02. Access Avaya SBCE web interface
- 03. Add Server Configuration Profile
- 04. Add Routing Profile for Recording Server
- 05. Define Application Rules
- 06. Define Media Rules
- 07. Configure UCID
- 08. Define End Point Policy Group
- 09. Define Session Policies
- 10. Define Session Flows
- 11. Define Server Flows
- 12. Configure MiaRec SIPREC recordging interface
- Broadsoft call recording
- Cisco CUBE SIPREC call recording
- Cisco UCM call recording
- Cisco active recording (Built-in-Bridge)
- Overview
- Cisco phones supporting Built-in-Bridge feature
- Configure CUCM
- Configure phones
- Configure MiaRec
- Configure firewall
- Optional configuration
- Cisco phone services
- Cisco active recording (Built-in-Bridge)
- Cisco CUBE Network-Based Recording
- Cisco UCM recording announcement
- Overview
- Installation guide
- Announcement Player - Configuration
- CUCM - SIP profile
- CUCM - SIP Trunk Security Profile
- CUCM - SIP Trunk
- CUCM - Route pattern
- CUCM - Built-in-Bridge (system level)
- CUCM - TAPI user
- Controller - Cisco TAPI TSP driver
- Controller - Verify TAPI configuration
- Cisco TAPI - Configuration
- Default recording announcement rules
- Per-user announcement configuration
- Metaswitch call recording
- Metaswitch SIPREC configuration
- MiaRec configuration for Metaswitch call recording
- Ignore Metaswitch internal redirect numbers
- Automatic user provisioning
- High availability configuration
- Softkey integration with Polycom VVX (Metaswitch platform)
- Softkey integration with Yealink phones (Metaswitch platform)
- User authentication using Metaswitch CommPortal
- Soft key integration with phones
- User management
- Storage management
- Customization
- Maintenance
- Speech Analytics
- MiaRec Architecture
- Screen Recording
- Security
- High availability
VMWare OVA template-based installation
MiaRec OVA template is a pre-installed virtual machine with operating system (Centos 7.3 64-bit) and MiaRec call recording software.
This OVF template is ideal solution for trial. It is easy to import it into VMWare ESX/ESXi or VMWare Workstation.
1. Request URL to OVA template
Fill the download form to request URL to OVA template.
You need this URL for the next step.
2. Installation instructions for VMWare ESXi
Login to ESXi via VMWare vCenter Client.
From the menu select File -> Deploy OVF Template...
Inside the opened dialog enter the URL to OVA file, which you received from the MiaRec representative.
Choose a name for this VM, select the desirable disk format (we commend "Thin provisioning" for trial and "Thick provisioning" for production deployment) and click "Finish" to start deploying of the virtual machine.
3. Console/ssh access to the MiaRec server
Login to console as a root user. A default password is miarec
It is highly recommended to change a root password as soon as possible. Login to the system as a root and type the following command to change own password:
passwd
4. Determining the MiaRec ip-address (when using DHCP)
Login to MiaRec virtual machine as root and execute:
ip a
It will show the ip-address assigned to the first network interface. User that ip-address to access MiaRec web-portal or SSH.
5. MiaRec web portal access
You need to know the ip-address of virtual machine (see the above step).
Type in the web-browser the URL http://VM-IP-ADDRESS
You will be asked to create the admin account if you access the web portal the first time.
6. Trial license
You need to request 30-day trial license for MiaRec call recorder. Open MiaRec web-portal and go to menu Administration -> Maintenance -> Recording License. Click on "Edit license" link. You will see "Computer Id" value. Send it to support@miarec.com to receive a trial license code.
7. Multi-tenant mode [optional]
Navigate to menu Administration -> Customization -> Multitenancy to enable multi-tenancy in MiaRec.
8. Configure network
By default, the MiaRec OVA template is configured with DHCP. For testing purposes, you can keep using DHCP-based network configuration. For a production environment, we recommend to configure static ip-address as described below.
Assign static ip-address (if not using DHCP)
By default MiaRec virtual machine is configured to obtain own ip-address from DHCP server. If you would like to use static ip-address for MiaRec VM, then edit file /etc/sysconfig/network-scripts/ifcfg-ens33
vi /etc/sysconfig/network-scripts/ifcfg-ens33
Change BOOTPROTO=dhcp to BOOTPROTO=none and add the following lines to this file:
IPADDR=x.x.x.x
GATEWAY=y.y.y.y
DNS1=8.8.8.8
DNS2=8.8.4.4
Replace x.x.x.x and y.y.y.y with desired machine ip-address and gateway.
Restart network interface:
service network restart
Test the network connection:
ping 8.8.8.8
Update /etc/hostname and /etc/hosts
If you would like to access MiaRec web-portal via dns name rarther than ip-address, then edit files /etc/hostname and /etc/hosts.
Example of /etc/sysconfig/network
HOSTNAME=miarec.example.com
Example of /etc/hosts
127.0.0.1 miarec.example.com localhost
Restart network:
service network restart
Restart MiaRec recorder service
If the network configuration is updated, then you need to restart miarec recorder service:
service miarec restart