[Solved] Genesys GIR question

General Discussion
1

Hey folks

I have a question, in the Genesys GIR suite as per the design MCP will send the metadata to RPS.
there are no connections/dependencies are established. its working as designed now.

I am trying to find the link between these two apps, how is the data transfer occur?

RPS logs says the metadata has been received, but it doesn’t tell where its coming from, i mean which MCP ( if you have multiple)
same goes with MCP ,it doesn’t show any where the data is sent to.

Have anyone faced this issue?

2

RPS has a WS where MCP sends the data in JSON format.
The MCP depends on the Tenant that is the user recorded from.
The RPS is the address you configure at the Voice Profile for that Tenant.

3

Thanks for the reply

So we have gir voice profile, in the settings i see httpd configuration with the link
are you saying mcp will send the meta data to here?

RPS apps address is no where in the voice profile

or do RPS gets details from the httpd somehow
i would like to know how mcp is sending the data to WS /RPS

4

please
Refer to installation documentation

https://docs.genesys.com/Documentation/CR/latest/Solution/RPS#t-14

5

SIPServer is sending tenant and IVR Profile name with INVITE when it is establishing MSML session with Media Server (MCP).

MCP is reading option which can be found in GAX - Voice Platform Profile - Recording tab - “Recording Processor URI” (or “recordingclient.callrec_dest” if we look into Configuration Manager - Annex tab of the IVR Profile).

This is the URL where to send metadata.

6

Thanks for the response

here is onething i didn’t understood

so MCP will send the data to Recording processfor URI (fixed,http://xyz.bz/interactionreceiver/)and RPS will collect it from there?

In the mCP logs as i mentioned earlier i am not seeing any reference about RPS and VIce versa

7
  1. You have to enable DEBUG (verbose=all) level logging for your MCP;
  2. You have to look into the log file of the right MCP which is doing recording :);

It should look like this one:

2019-01-09 09:03:40.013 DBUG 008301C3-10005171-00000362-008301C3-10005171 3025054016 01F00000 FMThreadQueue.cxx:1273 Processing POST request, URL: http://gir.adventus.lv/rp/api/contact-centers//recordings/