Metaswitch Configuration for CallCabinet Atmos Call Recording as a Service - Call Recording

Metaswitch Configuration for CallCabinet Atmos Call Recording as a Service

Multi-tenant call recording solutions Metaswitch

Atmos is a multi-tenant call recording solution for service providers, using Metaswitch to offer hosted telephony services. Atmos allows service providers to quickly deploy and offer profitable mission-critical call recording functionality as a part of their service offerings.

Atmos includes a full set of service provider management functions allowing user auto-provisioning and single sign-on for seamless user experience. Atmos also includes a wide range of advanced features, enabling service providers to offer advanced contact center functionality such as Agent Evaluation, Screen Capture, Compliance, Voice and Call Analytics.

Service Providers using Metaswitch platforms benefit from fully a functional, reliable and advanced call recording solution at a competitive price point and a low total cost of ownership.

Metaswitch call recording

This guide describes the configuration procedures required for Atmos call recording and interoperability with Metaswitch MetaSphere CFS and/or Perimeta SBC.

Requirements:

    • Metaswitch CFS v.9.0.10 or higher
    • SIPREC recording interface is supported in Metaswitch CFS starting from v.9.0.10
    • A Service Provider hosted VM in their data center, connected to the Metaswitch system with remote access available for CallCabinet to install the call collector software and the ability to have calls flow from the Metaswitch system to the VM, while allowing the VM to connect to an outside network (Atmos) via an outbound only Firewall setting.
      The Virtual Machine is responsible for recording and does not require space for storage.
      Windows Server 2016 (or similar) 64 bit or higher
      12 Core 2.5 GHz or higher
      16 GB RAM
      256 GB SATA 7200 RPM HDD
      Gigabit NIC

Service impact

The step to enable call recording on MetaSphere CFS, by modifying the global Application Servers object, requires you to disable this object briefly in order to make configuration changes. This means that any other services provided to MetaSphere CFS by Application Servers will be unavailable for a short period, typically no more than five minutes. It is recommended to do this step during a maintenance window or when call usage is low.

Apart from a brief outage in services provided to MetaSphere CFS by Application Servers, as described above, this procedure has no impact on service.

Network Architecture

Metaswitch system uses the established SIPREC link to send call details (caller/called phone number, service provider id etc.) and audio RTP stream to the Atmos Call Collector.

Metaswitch-Installation-Notes

Step 1. Create the Configured SIP Binding

  1. Import the Media Gateway Model which can be downloaded from: https://www.callcabinet.com/Downloads/SIPRec/MediagatewayModel.txt and add it using the following instructions:
    1. Log in to MetaView Explorer.
    2. Select Object tree and views. Expand the tree until you can see the Network Element object corresponding to your MetaSphere CFS.
    3. Locate and expand the Controlled Networks object, then the Remote Media Gateway Models object below it.
    4. In the Import – file field, type the name of the Remote Media Gateway Model import file. Click apply to confirm your changes.
    5. The status should change to Succeeded, if not review the Import – log correlator field, and click on the go to log button next to this field to jump to the MetaView Explorer log viewer window, this will show a summary log describing the import action you have just taken. If there were problems with the import, you can follow the links within the log viewer to see the earlier logs relating to this problem. Take any action recommended by these logs and retry the import.
  2. In MetaView Explorer, select Object tree and views. Expand the tree until you can see the Network Element object corresponding to your MetaSphere CFS. Expand this object.
  3. Locate and expand the Controlled Networks object, then the Configured SIP Bindings object below it.
  4. Click on the add sub-component button and choose Configured SIP Binding.
  5. Fill in the fields as follows. Any fields not listed below can be left with their default values.
      1. Name: fill in a name that will help you to associate this binding with the recording server. For example, “Atmos recorder”
      2.  Usage : set to Application Server
      3. Use DN for identification: set to True
      4.  SIP authentication required: set to False
      5. IP address match required: set to True
      6. Contact address scheme: set to IP address and port or Domain name SRV lookup (auto fail-over)
      7. Contact IP address and Contact IP port: set to the address and port of the Atmos recording server (if the “Contact address scheme” is “IP address and port”)
      8. Contact domain name: set to the DNS SRV domain name of the Atmos recording servers (if the “Contact address scheme” is “DNS SRV”) see:
        https://www.callcabinet.com/knowledge-base/metaswitch-recording-failover-redndancy/
      9. Proxy IP address and Proxy IP port: set to the IP address and port used to communicate with the proxy or leave blank if a proxy is not being used
      10. Trusted: set to True
      11. Media Gateway model: select the model that you imported earlier in this procedure
      12. Maximum call appearances: set this to the maximum concurrent calls for the recording service. Enabling Call Recording on large numbers of lines will increase the resources used by the service, particularly Media Gateway resources. Ensure that you have enough capacity to handle the expected level of recorded calls. If the Atmos recorder server is located in a separate network, make sure that appropriate bandwidth is available for the anticipated recording data network traffic.
      13. Poll peer device: set to True.
  6. Click apply to confirm your changes

Step 2. Create the Application Server

  1. In MetaView Explorer, navigate to Call Feature Server -> Call Services -> Global Application Servers.
    1. Click on the add sub-component button and choose Application Server.
    2. Fill in the fields as follows.
    3. Directory number: select a free telephone number within one of the numbers ranges owned by the CFS (see Note 1)
    4. Configured SIP Binding: select the binding that you created in the previous step
    5. Server type: select Recording and leave all the other values unselected
  2. Click apply to confirm your changes.

Note 1. The Directory number setting is rather critical. It is important to select a phone number that is treated as local in respect to the recorded users. Otherwise, if it is treated by routing rules as an external, then Metaswitch CFS may send SIPREC signaling packets through a SIP Trunk, which is wrong. This issue is easily detectable by looking at SIP messages call flow in SAS tool.

Step 3. Enable call recording service on MetaSphere CFS

This step requires you to disable the global Application Servers object briefly in order to make configuration changes. This means that any other services provided to MetaSphere CFS by Application Servers will be unavailable for a short period, typically no more than five minutes. If you are running this MOP on a live system, you are recommended to do this step during a maintenance window or when call usage is low.
  1. In MetaView Explorer, navigate to Call Feature Server -> Call Services -> Application Servers.
  2. Click on disable to disable the object so that you can modify it.
  3. Set Recording service support to Configured.
  4. Set Recording service – default subscribed setting and Recording service – default enabled setting according to the desired behavior.
  5. In Recording service – default server, select the Application Server that you added earlier in this procedure.
  6. Click apply to confirm your changes, then enable to re-enable the Application Servers object. Check that it becomes active and no alarms are shown.

Step 4. Enable recording individually for each user in Metaswitch CFS.

This step is not required if you have enabled Call Recording on all lines by default.
  1. You can use either MetaView Web or MetaView Explorer for this step. Repeat it for each line that you will use for testing Call Recording.
    1. If you are using MetaView Web :
    2. Search for the Business Group Line, MLHG, MADN or PBX DID Number using its directory number, or search for the PBX using its name.
    3. Go to the Configuration tab and expand the Advanced section to show the Recording Service fields.
    4. Ensure that the service is both subscribed and enabled and that the server is set to the new server you added earlier in this procedure.
    5. Click apply to confirm your changes.
  2. If you are using MetaView Explorer :
    1. Use the Find option on the left-hand menu to find the line.
    2. Then find the Application Servers child object below it. For a PBX DID Number, the equivalent child object is DID Number Call Services.
    3. Ensure that the service is both subscribed and enabled and that the server is set to the new server you added earlier in this procedure.
    4. Click apply to confirm your changes.

Step 5. Enable recording of intra-Business Group calls, if required

To record internal calls between subscribers within the same Business Group, enable the corresponding option in the Business Group settings:

Metaswitch-Installation-Notes-step-5

Step 6. Enable a recording announcement, if required

Metaswitch platform can generate a periodical beep tone when recording is enabled.

This option is configurable on the Business Group level:

Metaswitch-Installation-Notes-step-6

Step 7. Disable media bypass in Perimeta SBC for all recorded users

Subscribers behind Perimeta that have call recording enabled should not be allowed to use SBC media bypass, as this has been found to cause problems in the media path (one-way or no-audio issue for some call scenarios, including attended call transfer, hold/resume and 3-party conference). To disable it, on the adjacency facing the subscriber, type ‘call-media-policy’ and then ‘media-bypass-policy forbid’.

Step 8. Make a test call and verify the recording

Make a call to or from one of the test lines on which Call Recording has been enabled. Check the recording on Atmos.
If recording is not available, use MetaView Service Assurance Server to confirm that the call is being handled correctly
Detailed procedure:

  1. Log in to the MetaView Service Assurance Server Web GUI.
  2. Click Search.
  3. On the Number tab, enter the number of the Business Group Line to or from which you made the test call.
  4. Find the call that you made to or from the test number and check the MetaView Service Assurance Server output to confirm that a SIP INVITE message was sent from MetaSphere CFS to the Atmos recording server for this call.