- 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
2. Network Configuration
MiaRec uses port mirroring function on a network switch to capture voice packet related to the agents' IP phones and softphones. MiaRec server needs to have two Network Interface Cards (NICs), one of which is used for port mirroring (capturing voice) and another is used for regular network connection. The first NIC doesn't need to have TCP/IP stack enabled (see Network adapter configuration)
Port mirroring function has to be configured on a network switch in the following way:
- Ports of the C-LAN and MedPro cards should be configured as sources for port mirroring session
- MiaRec capturing port should be configured as a destination for port mirroring session
Below is an example of port mirroring configuration on Extreme Networks Summit X250e-24p network switch.
For other models please refer to Port Mirroring Configuration.
Assuming that:
- C-LAN card is connected to Port 1 of the Summit X250e
- MedPro card is connected to Port 2 of the Summit X250e
- MiaRec capturing NIC is connected to Port 24 of the Summit X250e
In this case you need to execute following commands on the switch:
enable mirroring port 24 mirroring add port 1 mirroring add port 2
Save configuration into permanent memory (NVRAM) otherwise port mirroring settings will be lost after switch reboot:
save config