Configure the Generic SIPREC Adapter

Create a Generic SIPREC Adapter and associate a Verint data source to deliver real-time updates from the Recorder to your preferred application.

For MS Teams using SIPREC, you need to create an adapter for each type of communication and associate it with the Data Source configured in Enterprise Manager.

The SIPREC adapter can be deployed under both Recorder Integration Service (RIS) and Recorder Adapter Proxy Service (RAPS) roles:
- Deploy on RIS to centralize session control and metadata handling.
- Deploy on RAPS to offload media traffic and support horizontal scaling in high-volume environments.

Before you begin 

  • A Phone Data Source for Microsoft Teams SIPREC audio must be created in Enterprise Manager.

  • The RIS and RAPS nodes must be installed and operational.

  • The Session Border Controller (SBC) must be configured to route SIPREC sessions to both the RIS and RAPS nodes.

Procedure 

  1. In Recorder Manager, go to General Setup.

  2. Under Integration Service, click Settings.

  3. Click Create, then select Generic SIPREC Adapter.

  4. Enter the following settings:

    Field

    Description
    Settings

    Adapter Name

    Type a unique name for this adapter. Do not use any special characters or characters that truncate xml. This field is not case-sensitive.

    Description

    Optional: Type a description of the adapter.

    Adapter Type

    A read-only field that lists the adapter selected above.

    Startup Type

    Select a startup type: Automatic, Manual, or Disabled.

    DataSource

    Select the Phone data source you created previously.
    SIPRec Device Type Specify the far-end SIPREC device being used for this integration, such as, AudioCodes.
    General Settings
    SIP Protocol

    Select a protocol for the SIP Proxy adapter:

    • SIP over UDP—User Datagram Protocol (UDP) allows applications to send messages to hosts on an IP network. UDP has a lower overhead because it assumes that error checking is either not required or that this processing is done elsewhere.

    • SIP over TCP—Transmission Control Protocol (TCP) is best for applications (such as email and file transfer) that require a reliable data stream service.

    • SIP over TLS—Transport Layer Security (TLS) is designed to secure client/server communications over a network. It operates on segments of network connections above the Transport Layer.

    • SIP over TLS with System Certificate— Choose this option to use the local HTTPS certificate on the server to encrypt external connections over the trunk for server-side and client-side communication. The adapter loads the local server certificate for the SIP interface, uses the local server “HTTP Alias” for the SIP Contact header, and uses the IP address of the NIC on Recorder server for the Session Description Protocol (SDP) media lines.
    Listen at IP Address Specify the IPv4 address for the adapter to bind the SIP trunk and receive traffic. The address must be a valid IPv4 address on one of the network interfaces of the local system. When the adapter starts, if the Listen at IP address field is empty, the adapter listens to each network interface with a valid IPv4 address. The adapter starts only when the IPv4 address can be located.
    Port Type the listen port for the IP address specified earlier. If Telephony Playback Server is installed on the Integration Service machine, you must use a port other than 5060.
    Supported Codecs From the Supported Codecs, select a supported codec from the list of those available.
    TLS Parameters
    KeyStore Filename Enter the path to keystore file. This files can be generated using a command: keytool -importkeystore -srckeystore svr_cert_key.p12 -srcstoretype PKCS12 -destkeystore carbyne.jks
    Password Type the password for the KeyStore File.
    File format Select either JKS or PKCS as the keystore format. JKS is the default.
    Security Profile From the Security Profile list, select Server Site.
    SIP Statistics
    Enable SIP Statistics Gathering Select the checkbox labeled Enable SIP Statistics Gathering to activate SIP data collection.
    Statistics logging period Specify the duration (in minutes) for which SIP statistics should be collected in the Statistics logging period box. The default value is 15 minutes.

  5. Click Save.

Related topics 

Configure Verint to capture Audio from Microsoft Teams using SIPREC