Type a unique name for the member group.

Type a description for this extension group (optional).

Select one of the following:

• Recorder Controlled–The Recorder controls recording of the extensions or trunks, and implements the default recording modes. In this case the Integration Service is used for segmentation, stitching, and tagging purposes.

• Full Delivery (External Controlled)–Recording is used in compliance delivery recording and is controlled by a 3rd party application, which redirects audio to the Recorder. For use with Cisco DMS (where the Recording Option of the line has been set to Automatic Call Recording), Genesys SIP full Delivery, and NEC NEAX.

• CTI Controlled–Used in environments with interception recording, where the Integration Service will tell the Recorder when to start and stop recording.

• Selective Delivery (Duplicate Streamed)–Used in selective delivery recording. Specifically, in environments where the Integration Service issues requests to start recording to a 3rd party application. For use with SAP switches, and Avaya DMCC, Avaya NES DMS, and Cisco Call Recording, where the Recording Option of the line is set to Application Invoked Call Recording.

Select one of the following:

• None—A single recorder records all calls and no load balancing will occur.

• Media Only—Multiple recorders are used to record the calls and all recorders will be aware of signaling (both call control and media control messages) for all calls. Only one of the recorders will be aware of the audio. Example deployments are:

  • Using a load balancing device or link protector to manage the traffic.

  • Using IP Analyzer to control a group of recorders.

• Media with Signaling—Multiple recorders are used to record the calls. Use only in Recorder Controlled environments where one of the recorders will be aware of the call (that is, call control and media control messages + audio), while other recorders are not aware of this call. Do not use this option in CTI controlled environments. An example deployment would be the use of Acme Packet SBC to load balance the traffic.

• Shared Interception—Multiple recorders are used to record the calls. All recorders will be aware of all the calls (that is, call control and media control messages + audio). The Integration Service load balances call recording by enabling and disabling available resources. Use this for deployments in which multiple recorders have the same network SPAN.

• Dedicated Interception—Available only if the Recorder Control Type is Recorder Controlled. Multiple recorders are used to record the calls and all recorders will be aware of all the calls (that is, call control and media control messages + audio). Enterprise Manager controls load balancing of call recording by distributing the extension list to all recorders with which this Member Group is associated.

Select one of the following:

• Never (Application)—If CTI is disconnected, no audio or screen recording will occur. If CTI is up, CTI segments will be retained.

• On CTI Disconnection (Performance)—If CTI is disconnected, audio recording continues (VOX-detected segments will be retained), but screen recording does not. If CTI is up, only CTI segments with recorded audio are retained; if we receive CTI for a call but no audio (for any reason), recording will not occur. VOX segments (not associated to CTI calls) will be discarded. You can set a Rollback Period in the phone data source Third-party systems that provide data to the system, including employee and device states, and data change events. Typical data sources are phone switches, PBXs, or LANs. to specify the length of time preceding a disconnection for which recordings will be held.

• Always (Liability)—If CTI is disconnected, audio recording continues (VOX-detected segments will be retained), but screen recording does not. If CTI is up, both CTI- and VOX- detected segments will be retained. (If a signalling protocol is configured, it will be used before VOX to record the call.)

You can use this setting only in Avaya DMCC SSC/SO or Shared Interception environments.

This setting allows individual calls to be directed to the recorder associated with this member group based on specific call data (for example, the call’s trunk group).

Select an Attribute from the dropdown list, then type a value in the Expression field. If the call data matches the expression, the call will be recorded by this recorder.

The Recorder Selection Expression is limited to one hundred (100) characters.

If you are using a custom attribute, you must first add this attribute to the system, under Recording Management > Custom Data—see Create, edit or delete an attribute.

You must also select either LineFirst or LineExclusive as the Recording Resource Allocation Behavior—see Create a phone data source.

• Network - Select this type to assign all phones on a subnet to the member group. Complete these additional fields:

  • Network - Enter the IP address that identifies the network on which the phones reside.

  • Mask - Specify the subnet mask applicable to the network on which the phones reside.

    Specifying a subnet mask of 255.255.255.255 is the same as specifying an individual IP address.

• Host IP - Select this type to assign a phone to the member group using the phone IP address.

  In the Network setting, enter the IP address of the phone.

• Host Name - Select this type to assign a phone to the member group using the phone host name.

In the Network setting, enter the host name of the phone.

This is a read-only field that appears only when the Recorder Load Balancing Type is Dedicated Interception.

Use this section to associate one or more Recorders with this Member Group.

A Recorder Adapter Proxy Service (RAPS) server role association Relationship between server roles, where one server role relies on the configuration and functionality of another server role to perform its tasks. is valid only when either Selective Delivery (Duplicate Streamed) or Full Delivery (External Controlled) is selected as the Recorder Control Type. A RAPS server role Entity that contains a logical, predefined set of components (system software or certified third-party software) deployed in the Data Center and Site Zones that provide specific functionality for the system. association is mandatory to support SIP scaling. If you have a legacy SIP deployment, and do not want to support SIP scaling, it is not necessary to associate a RAPS server role to the member group.

Use the Key and Value fields to enter the advanced parameters required for your system. Only add advanced parameters in consultation with Verint Support or Field Engineers.