NICE recorder integration with GVP 8.1.5

[Kubig]

Option "recordingclient.recmediactl" has two possible values (as I know yet):
[list]
[li]fixed,1 - mono(customer's and agent's stream in one leg[/li]
[li]fixed,2 - stereo(separate leg for each stream)[/li]
[/list]
Option(s) "recordingclient.recdest(2)":
[list]
[li]Only recordingclient.recdest - RTP stream is sent to one LRG(one recorder),you can specify RM ip address or direct ip address of recorder,if you have only one recserver[/li]
[li]recdest & recdest2 - RTP stream is replicated to two LRG, you have to specify IP address of one recorder server from each LRG[/li]
[/list]

Currently,GQM can determine parameter recdest itself,may be NICE can it also.

[quote author=EdPater link=topic=7686.msg33209#msg33209 date=1361825782]
Also I had to configure the Extension DN with "record=true" in the TServer section of the annex.
[/quote]

I am not sure,if it is still active recording,when you have configured record parameter on extension object. In that configuration is recording started by SIP server or I am wrong? So,in GQM it is.

[Kubig]

Option "recordingclient.recmediactl" has two possible values (as I know yet):
[list]
[li]fixed,1 - single SIP session for both stream[/li]
[li]fixed,2 - single SIP session for each stream[/li]
[/list]
Option(s) "recordingclient.recdest(2)":
[list]
[li]Only recordingclient.recdest - RTP stream is sent to one LRG(one recorder),you can specify RM ip address or direct ip address of recorder,if you have only one recserver[/li]
[li]recdest & recdest2 - RTP stream is replicated to two LRG, you have to specify IP address of one recorder server from each LRG[/li]
[/list]

Currently,GQM can determine parameter recdest itself,may be NICE can it also.

[quote author=EdPater link=topic=7686.msg33209#msg33209 date=1361825782]
Also I had to configure the Extension DN with "record=true" in the TServer section of the annex.
[/quote]

I am not sure,if it is still active recording,when you have configured record parameter on extension object. In that configuration is recording started by SIP server or I am wrong? So,in GQM it is.

[EdPater]

Thanks for the info Kubig, I haven't tested the functionality without the recdest with I'll do it as soon as I can.
About the record=true I guess it has to be with the NICE configuration because in any other way NICE will see the Logger channels in observation failure. As I said it may be something in the nice configuration.
In the GQM deployment they use this configuration to avoid the need of the TPrivateRequest from the recordingserver.

[bublepaw]

Some comments:

- Verint will be supported in near future - it is up to Verint to modify their software to work with Media Server
- record = true - works with Nice correctly and it is still active recording because RTP is duplicated in "active" way to recording device
- recmediactl controls how SDP is delivered to recording server - recording is always in stereo
  - 1 - one INVITE with two SDP inside (only for NICE)
  - 2 - two INVITE each with one SDP (GQM and Verint)
- in LRG containing VRSP You have to select "parallel forking" as monitoring method otherwise failure of VRSP won't be handled correctly
- recdest(2) parameters are used for HA only for GQM - adding recdest2 parameter into profile will cause Media Server to send same RTP to two different recording devices
- 8.1.6 release added support for inserting beep during recording. Beep is controlled through parameters in profile
- Nice has some limitations when working with active recording - please check for most current list with Nice team
- there are some additional parameters on MCP which might effect recording - for example with default parameters if NICE is not sending RTCP packets system will stop recording after 60 sek or will be restarting recording process
- for proper geo-location support for active recording request You have to use proper version of RM/MCP/SIPS. Also default setting in RM for geo-location support will cause SIPS to reject recording request if there are not MCP's with proper geo-location
- on commercial side this integration requires new license called "Active recording connector"

[Kubig]

Bublepaw,thx for detailed description. And sorry for my "hoax" with mediactl (now I know it :-))

[EdPater]

Bubblepaw, also thanx for the information. Could you give more info about this

[quote author=bublepaw link=topic=7686.msg33221#msg33221 date=1361886448]
- there are some additional parameters on MCP which might effect recording - for example with default parameters if NICE is not sending RTCP packets system will stop recording after 60 sek or will be restarting recording process
[/quote]

Cuz I just realize that my system has this issue.

[bublepaw]

Please set rtp.multichantimeout to 0

[Kubig]

And what about option "rtp.timeout",I configured it to value 0 too

[AndreK]

This was great help thanks guys

[huseyin.aksu]

Hello Experts,

I have a quick question about integration between Nice & Genesys Pure Engage.

In order to integrate Nice Call Recorder with Genesys PureEngage, how I could create a recording service on Genesys side ? Could you please tell me step by step ?

Many thanks,

[Kubig]

Quick question requires quick answer : so, read and follow documentation for GVP (or GMS - aka Genesys Media Server) as was previously recommended within other topic

In short you have to:

- Install, deploy and configure Genesys SIP, RM and MCP
- Configure DNs for recording (Extensions, VoIP service, etc.)
- Create and configure IVR profile
- Create and configure LRGP