- 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 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
- Softkey integration with Yealink phones (Metaswitch platform)
- MiaRec configuration for Metaswitch call recording
- Ignore Metaswitch internal redirect numbers
- Automatic user provisioning
- High availability configuration
- Softkey integration with Polycom VVX (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
11. Define Server Flows
The End Point Server Flows allow calls to be recorded by MiaRec when they are passing through Avaya SBCE to the Service Provider’s SIP Trunk. Navigate to Device Specific Setting -> End Point Flows -> Server Flows.
Create two Server Flows for MiaRec, one to record calls coming in from Service Provider’s SIP Trunking service and another for calls coming in from Session Manager.
Server flow 1. SIP Trunk -> Session Manager, i.e. inbound calls
Configure:
- For Server Configuration select the one created in Step 3.
- For Received Interface select the one used towards Service Provider for SIP Trunk
- For Signaling Interface select the one used towards Session Manager for SIP signaling
- For Media Interface select the one used towards Session Manager for RTP media
- For Endpoint Policy Group select the one created in Step 8
- For Routing Profile select default i.e. Routing profile without any IP address
- For Topology Hiding select None. The SBC will send the same information it sends to SM based on the TH set in the SM server flow.
Server flow 2. Session Manager -> SIP Trunk, i.e. outbound calls
This server flow is similar to the previous one, but for reverse call direction, outbound call through Service Provider's SIP Trunk. The Received Interface, Signaling Interface and Media Interface are reversed.
Configure:
- For Server Configuration select the one created in Step 3.
- For Received Interface select the one used towards Session Manager for SIP signaling
- For Signaling Interface select the one used towards Service Provider for SIP signaling
- For Media Interface select the one used towards Service Provider for RTP media
- For Endpoint Policy Group select the one created in Step 8
- For Routing Profile select default i.e. Routing profile without any IP address
- For Topology Hiding select None. The SBC will send the same information it sends to SM based on the TH set in the SM server flow.
Server flow 3. Remote worker calls.
If Remote Workers connect to SBCE via external network interface different from the Service Provider's SIP Trunk, then an additional server flow is required to record Remote Worker calls:
- For Server Configuration select the one created in Step 3.
- For Received Interface select the one used towards Remote Workers
- For Signaling Interface select the one used towards Session Manager for SIP signaling
- For Media Interface select the one used towards Session Manager for RTP media
- For Endpoint Policy Group select the one created in Step 8
- For Routing Profile select default i.e. Routing profile without any IP address
- For Topology Hiding select None. The SBC will send the same information it sends to SM based on the TH set in the SM server flow.