Skip to main content
  • Products
    • Overview
    • Features
    • Screen Capture
    • Agent evaluation / score cards
    • Speech Analytics
    • Recording Announcement
    • Videos
    • Online demo
    • Quote
    • Download
  • Solutions
    • Businesses
    • Contact centers
    • Financial institutions
    • Healthcare
    • MiFID II compliance
    • Telecom service providers
    • Traders
  • Compatibility
    • AudioCodes
    • Avaya
    • BroadSoft
    • Cisco
    • Genband
    • IPC
    • Metaswitch
    • Oracle AcmePacket
    • SIPREC recording
    • Sonus
  • Documentation
    • User Guide
    • Administration Guide
    • Developer Guide
    • MiaRec v.3 (old) documentation
    • Resource library
    • Videos
  • Support
    • Submit a request
    • Check your existing requests
    • TeamViewer QuickSupport
  • Blog
  • Company
    • About MiaRec
    • Contact us
    • Our clients
    • Become a partner
    • News
    • Careers
    • Events

Table of Content

  • Administration Guide
    • Hardware requirements
      • Overview
      • All-in-one server
      • Decoupled architecture
      • Decoupled with GEO-redundancy
      • Disk space requirements
    • Installation
      • Ansible-based installation on Linux
        • Overview
        • 1. Prepare controller host
        • 2. Prepare target hosts
        • 3. Configure deployment
        • 4. Run playbooks
        • 5. Verify MiaRec operation
      • 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
        • Install MiaRec software
    • Update
      • Ansible-based update on Linux
      • Migrate from manual to Ansible-based setup
    • Post-installation tasks
      • Firewall configuration
      • Enable HTTPS for MiaRec Web portal
        • Setup free SSL certificate for MiaRec using Let's Encrypt (Ubuntu 14.04)
        • Setup free SSL certificate for MiaRec using Let's Encrypt (Centos 6/7)
        • Setup SSL certificate for MiaRec Web portal on Centos
    • Phone system integration
      • Avaya Aura call recording
        • Avaya TSAPI DMCC recording
          • 1. Introduction
          • 2. Configure Avaya Communication Manager
          • 3. Configure Avaya Application Enablement Services
          • 4. Configure MiaRec Call Recording System
          • 5. Verification and Troubleshooting
          • 6. Additional references
        • Avaya TSAPI passive recording
          • 1. Introduction
          • 2. Network Configuration
          • 3. Configure Avaya Communication Manager
          • 4. Configure Avaya Application Enablement Services
          • 5. Configure MiaRec Call Recording System
          • 6. Verification
          • 7. Additional references
      • 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
        • Broadsoft SIPREC recording
      • Cisco CUBE SIPREC call recording
        • Cisco CUBE SIPREC configuration
        • MiaRec SIPREC configuration
      • Cisco UCM call recording
        • Cisco active recording (Built-in-Bridge)
          • Overview
          • Cisco phones supporting Built-in-Bridge feature
          • Configure CUCM
            • Create SIP profile for recorder
            • Create SIP Trunk Security Profile
            • Create a SIP Trunk that points to the recorder
            • Create a recording profile
            • Create a route pattern/group for the recorder
              • Single server configuration
              • Multiple servers configuration
            • Enable Built-in-Bridge for all phones (optional)
            • Codecs configuration
          • Configure phones
            • Enable Built-in-Bridge on per-phone basis
            • Enable recording for a line appearance
          • Configure MiaRec
          • Configure firewall
          • Optional configuration
            • Configure tones for recording (optional)
            • [Howto] Configure SIP/TLS for SIP Trunk (optional)
        • Cisco phone services
      • Cisco UCM recording announcement
        • Overview
        • Installation guide
          • 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
          • Controller - Configuration
      • Metaswitch call recording
        • Metaswitch SIPREC configuration
        • MiaRec configuration for Metaswitch call recording
        • Ignore Metaswitch internal redirect numbers
        • Automatic user provisioning
        • High availability configuration
          • SIPREC auto-failover configuration
            • Configure SIPREC auto-failover for a CFS-Perimeta-MiaRec connection
            • Configure SIPREC auto-failover for a direct CFS-MiaRec connection
        • Softkey integration with Polycom VVX (Metaswitch platform)
        • User authentication using Metaswitch CommPortal
      • Soft key integration with phones
        • Overview - Soft keys on IP phones
        • Configure MiaRec phone services
        • Integration with Cisco SPA and 3PCC series phones
        • Integration with Mitel/Aastra phones
        • Integration with Polycom VVX series phones
        • Integration with Yealink phones
        • Softkey integration with Cisco 7900, 7800 and 8800 series phones
          • Overview
          • Create MiaRec IP Phone Service
          • Subscribe each phone to MiaRec phone service
    • User management
      • Understanding user roles and permissions
      • Roles
      • Groups
      • Users
      • Associating calls with users
      • Configuring LDAP integration
      • Multi-tenancy
        • Enable multi-tenancy in MiaRec
        • Understanding multi-tenancy
        • Add tenant
    • Storage management
      • Audio file encryption
        • File encryption overview
        • Configuration check-list
        • Create new encryption key
        • Import encryption key
        • Export encryption key
        • Grant access to encryption key
        • Enable file encryption
        • Export of the encrypted files
      • Audio settings
      • Backup and restore
        • Backup call recordings
        • Restore call recordings
      • Location for audio files
        • File name format
        • Time formatting inside file name
      • Replication
        • MiaRec multi-master asynchronous replication
        • Use cases for replication
        • Configuring target server (recipient)
        • Configuring replication server (sender)
      • Retention policy
    • Customization
      • Calls list layout
      • Timezone settings
      • Translate MiaRec to other language
    • Maintenance
      • Troubleshooting
        • Log files
        • MiaRec recorder trace
      • Increase/expand an EXT4 filesystem in RHEL 6 / CentOS 6
      • Increase/expand an XFS filesystem in RHEL 7 / CentOS 7
      • License
      • Performance Monitoring
    • Speech Analytics
      • How it works - Speech Analytics
      • Set up Google Cloud Speech API
      • Create Google Cloud Storage bucket
      • MiaRec configuration
    • MiaRec Architecture
    • Screen Recording
      • How it works
      • Configure licensing
      • Configure storage
      • Configure screen recording settings
      • Generate secure token
        • A single-tenant configuration - generate token
        • A multi-tenant configuration - generate token
      • Install client application
      • Authorize new workstations
      • Configure users for screen recording
      • Verify screen recording
      • Troubleshooting
        • Troubleshooting on client side
        • Troubleshooting on server side
      • Deploy Screen Capture Client with Windows Group Policy
        • Create a Transform (MST) file
        • Put the MSI and MST files in a file share
        • Create a new GPO
    • Security
      • PCI scanners and false positives
      • Security hardening for Apache web server
    • High availability
      • Overview
      • High availability for BroadWorks SIPREC recording
      • High availability for Cisco Built-in-bridge recording
Home › Administration Guide › Phone system integration › Soft key integration with phones ›
 

Integration with Mitel/Aastra phones

MiaRec integrates with Mitel 6800 series phones (previously known as Aastra) to provide on-demand and pause/resume recording control using softkey.

The photos below show Mitel 6867i phone integrated with MiaRec XML application in action.

Mitel MiaRec softkey

Mitel 6871i / MiaRec softkey integration

Users can press Record / No Record softkey buttons during a call to selectively record some calls (on-demand recording).

The following photo demonstrates "Recording" state. User can press "No Record" to disable recording.

Mitel on-demand recording softkey

The following photo demonstrates "Not Recording" state. User can press "Record" to enable recording.

Mitel on-demand recording softkey

Additionally, MiaRec supports pause/resume recording for PCI Compliance. Users can press Pause and Resume softkey buttons to temporary mute recording, for example, when customer speaks credit card number.

Mitel pause/resume recording softkey

Configuration of Mitel phone

The MiaRec XML application can be configured in Mitel phone using:

  • Phone web interface
  • Generic provisioning server (recommended).
  • Metaswitch SIP Provisioning Server (recommended)

Option 1. Configuration of phone using web interface

Open web interface to Mitel phone and navigate to Softkeys and XML->Top Keys.

Choose one of available line keys and set:

  • Type to XML
  • Label to the preferred title, for example, MiaRec or Record
  • Value should point to MiaRec web server. Format is the following:

    https://miarec.example.com/api/aastra?login={LOGIN}&password={PASSWORD}
    

    Where:

    • {LOGIN} is a web access login configured on user's profile in MiaRec web portal
    • {PASSWORD} is either Phone Services PIN or web access password depending on phone services configuration in MiaRec.
    • miarec.example.com should replaced with your MiaRec server address

Mitel softkey configuration

HTTP vs HTTPS?

The URL for XML application supports both http:// and https://. For quick testing purposes you can use HTTP (non-encrypted) protocol for XML application, but for production, it is required to use HTTPS as it provides encryption. The user's login/password has to be sent to MiaRec server during authentication, so, encryption is required to protect this data from man-in-middle attacks.

Your MiaRec web server can be deployed with a self-signed certificate (not recommended for production) or with a SSL certificate signed by such providers like Verisign, DigiCert, GoDaddy, etc.

Mitel phone by default trusts only certificates that are signed by fullowing providers: Comodo (EssentialSSL and 4096-bit RSA), CyberTrust, DigiCert, Entrust, GoDaddy, GeoTrust, Mitel MBG, Symantec (Class 3 Secure Server CA - G4), Thawte, TrustZone and Verisign.

If your SSL certificate is signed by other provider, then it is necessary to download provider's CA certificate to the phone as a trusted SSL certificate. Check the Mitel SIP Phones Administration Guide for details (chapter HTTPS Client/Server Configuration).

Option 2. Configuration of phone using a generic provisioning server

Add the following lines to your phone's configuration file:

topsoftkeyX type: xml
topsoftkeyX label: MiaRec
topsoftkeyX value: https://miarec.example.com/api/aastra?login={LOGIN}&password={PASSWORD}

Where:

  • X is a number from 1 to 10 (depending on phone model).
  • {LOGIN} is a web access login configured on user's profile in MiaRec web portal
  • {PASSWORD} is either Phone Services PIN or web access password depending on phone services configuration in MiaRec.
  • miarec.example.com should replaced with your MiaRec server address

Option 3. Configuration of phone using Metaswitch SIP Provisioning Server

If you are a Metaswitch service provide using Metaswitch SIP Provisioning Server, then you can automate provisioning of MiaRec to all users using custom Endpoint Pack with the following settings:

topsoftkeyX type: xml
topsoftkeyX label: MiaRec
topsoftkeyX value: https://miarec.example.com/api/aastra?login=${userData.directoryNumber}&pat=${userData.commportalPAT}

Where:

  • X is a number from 1 to 10 (depending on phone model).
  • miarec.example.com should replaced with your MiaRec server address

The value ${userData.directoryNumber} will be replaced automatically with the extension of subscriber.

The value ${userData.commportalPAT} will be replaced with subscriber's Persistent Authentication Token (PAT).

Requirements for CommPortal-based authentication

  • CommPortal-based user authentication should be enabled in MiaRec (see menu Administration -> User Authentication -> Metaswitch CommPortal Authentication
  • Phone services authentication type on Tenant's profile should be set to Authenticate users using the web access password (see menu Administration -> User Management -> Tenants -> Tenant Profile -> Phone Services
  • Authentication type on User's profile should be set to CommPortal (see menu Administration -> User Management -> Users -> User Profile).

How MiaRec integrates with Metaswith CFS / CommPortal

Below diagram shows how MiaRec phone services are integrated with Metaswitch platform.

  1. The phone loads a custom made EndPoint Pack from Metaswitch SIP Provisioning server. This endpoint pack includes configuration of softkeys as well as HTTPS trust certificate (if necessary). The CommPortal Persistent Authentication Token (PAT) is generated for user and injected into the configuration file.

  2. User makes/receives call from Metaswitch CFS

  3. Upon pressing the pre-configured softkey, the phone loads XML application from MiaRec web server. The MiaRec server receives user's login and CommPortal Persistent Authentication Token (PAT) in the request, and passes those values to Metaswitch CommPortal for validation. After user credentials verification, the recording control buttons are displayed on phone's screen.

MiaRec Phone Services

Troubleshooting

MiaRec System Log

Navigate in MiaRec web portal to Administration -> Maintenance -> System Log and check if there are any warnings/errors.

Use your web browser to simulate a hardware phone

Open in your web browser the same link as you configured in the Mitel configuration file, for example:

https://miarec.example.com/api/aastra?login=123456&password=secret

You should be able to see XML formatted page like:

<?xml version="1.0" encoding="utf-8"?>
  <AastraIPPhoneFormattedTextScreen
    destroyOnExit="yes"
    LockIn="no"
    Beep="no"
  >

  <TopTitle>Recording controls</TopTitle>
  <Line>
     From: 551200159 
  </Line>
  <Line>
     To: 300 
  </Line>
  <Line>
     NOT RECORDING
  </Line>

  <SoftKey index="1">
      <Label>Record</Label>
      <URI>https://miarec.example/api/aastra/calls/...</URI>
  </SoftKey>

  <SoftKey index="2">
        <Label>Pause</Label>
        <URI>https://miarec.example/api/aastra/calls/...</URI>
  </SoftKey>

‹ Integration with Cisco SPA and 3PCC series phones up Integration with Polycom VVX series phones ›
Tags:
  • Aastra
  • mitel
  • Printer-friendly version
MiaRec, Inc. © 2020. All Rights Reserved. | Terms of Use | Privacy Statement | Cancellation Policy