Author Topic: RM Active-Active configuration for GQM Recording  (Read 9482 times)

Offline rkd

  • Newbie
  • *
  • Posts: 35
  • Karma: 0
RM Active-Active configuration for GQM Recording
« on: July 07, 2014, 03:59:33 PM »

Can some one help me understand how GQM Call recording works with the RM Active-Active(without VIP IP)?

When I configure both RM IPs in IVR default profile and sip.routeset(vrm recorder section in MCP), its taking both IPs rather than selecting one.

But treatment MCPs worked fine with sip.routeset(sip section of MCP) with  configuring both RM IPs.

2014-07-01 10:58:20.746 DBUG 00000000-00000000 4912 09900500 SessionFactory.cxx:323 SIP Message sent (1000): INVITE sip:record=00IKPDMAFG9R5F9DCGULHJTAES000002@207.88.61.100:5070,sip:207.88.61.101:5070;CallUUID=00IKPDMAFG9R5F9DCGULHJTAES000002;recordDN=59022;DN=7045576045 SIP/2.0

Via: SIP/2.0/UDP 207.88.61.103:8090;branch=z9hG4bK000000001B133F90b2da9c

From: <sip:Genesys@207.88.61.103:8090>;tag=FF41CF5A-A81E-45B5-7BBA-C9B65EF82CCC

To: sip:record=00IKPDMAFG9R5F9DCGULHJTAES000002@207.88.61.100:5070,sip:207.88.61.101:5070;CallUUID=00IKPDMAFG9R5F9DCGULHJTAES000002;recordDN=59022;DN=7045576045

Max-Forwards: 70

CSeq: 1 INVITE

Call-ID: 725D7D7C-0596-442D-CEB9-20247F5E4D9E-8090@207.88.61.103

Contact: <sip:Genesys@207.88.61.103:8090>

Content-Length: 162

Content-Type: application/sdp

Route: <sip:207.88.61.101:5070;lr>,<sip:207.88.61.100:5070;lr>

X-Genesys-GVP-Session-ID: BF565000-EF30-41D5-5C7A-4503E2A2EB7B

Supported: timer, uui

 

v=0

o=- 0268448726 0 IN IP4 207.88.61.103

s=phone-call

c=IN IP4 207.88.61.103

t=0 0

m=audio 5038 RTP/AVP 0

a=rtpmap:0 pcmu/8000

a=maxptime:20

a=sendonly


Offline Kubig

  • Hero Member
  • *****
  • Posts: 2752
  • Karma: 44
Re: RM Active-Active configuration for GQM Recording
« Reply #1 on: July 07, 2014, 07:41:23 PM »
sip.routeset within MCP for active-active mode should be configured in following format:
<sip:IP_of_one_of_RM:port;lr>
together with transport.staticroutelist:
RM1_IP,RM2_IP
within IVR profile the recdest can be configured as IP:PORT of GQM recorder or IP:PORT of one of RMs (if you are using media stream replication there will be option recodingclient.recdest2 as well)

With this configuration the MCP will choose IP of active RM for current call(recording)-session and fill it to the outgoing SIP messages to the GQM recorder(s)

Offline rkd

  • Newbie
  • *
  • Posts: 35
  • Karma: 0
Re: RM Active-Active configuration for GQM Recording
« Reply #2 on: July 07, 2014, 07:58:38 PM »
Hi Kubig

Thanks for your response.

I have multiple recorders and so I need to configure RM IPs in IVR profile so that It will load balance between the recorders.

How can I make sure requests are load balanced between both RMs to select  recorders?

I have 6 call recorders and 8 recording MCPs in our environment. and both these places,  currently the RM VIP IP is used (currrently RMs are Active-stnadby)

Offline Kubig

  • Hero Member
  • *****
  • Posts: 2752
  • Karma: 44
Re: RM Active-Active configuration for GQM Recording
« Reply #3 on: July 07, 2014, 08:16:56 PM »
Be sure, I have configured like that several deployments. Within IVR profile define the recdest option point to the IP of one of RMs (almost the "primary" RM). As I wrote MCP will choose the IP dynamically according to the current request/session.

Offline rkd

  • Newbie
  • *
  • Posts: 35
  • Karma: 0
Re: RM Active-Active configuration for GQM Recording
« Reply #4 on: August 01, 2014, 03:21:27 PM »
Hi

I have configured Active Active in Production and so many calls are having one way audio/no audio/call recording issues.

We are seeing the below error a lot in RM frm MCPs.

2014-08-01 07:12:44.007 DBUG 00A4013D-10190201 2348 01B00000 MSMLSession.cxx:485 MSMLSession::ProcessRequests: enter
2014-08-01 07:12:44.007 DBUG 00A4013D-10190201 2348 01B00000 MSMLSession.cxx:506 MSMLSession::ProcessRequests: element response 1
2014-08-01 07:12:44.007 DBUG 00A4013D-10190201 2348 01B00000 MSMLSession.cxx:556 Send response: code=430, mark=, description=Object does not exists: conn:16027FA0-7CF1-485C-6E85-12C769EAB92C
2014-08-01 07:12:44.007 DBUG 00A4013D-10190201 2348 01B00000 AppCallLeg.h:195 Call Leg send network event response
2014-08-01 07:12:44.007 DBUG 00A4013D-10190201 2348 01B00000 MSMLSession.cxx:1092 MSMLSession::CanDelete() - m_bDestroyed=false, m_nReqState=0, m_VXMLDialogMap.size()=0, m_MSMLDialogSet.size()=0, m_setConfsClearHandler.size()=0
2014-08-01 07:12:44.007 DBUG 00000000-00000000 3604 01C00000 CMMsgBase.h:183 cmapi.msg:  CM_MSG_CALLLEG_NETWORKEVENTRESPONSE - CallObjID == 00A4013D-10190201; Binding State == 1
2014-08-01 07:12:44.007 DBUG 00A4013D-10190201 3616 02800000 LMCallSIP.C:2958 NetworkEventResponse nResponse=200
2014-08-01 07:12:44.007 DBUG 00A4013D-10190201 3616 02800000 LMCallSIPStack.C:203 LMCallSIP::SendResponse for ID Headers
2014-08-01 07:12:44.007 DBUG 00A4013D-10190201 3616 02800000 LMCallSIPStack.C:225 LMCallSIP::SendResponse - X-Genesys-GVP-Session-ID: 83565000-CB44-9338-242C-4166B5019B99;gvp.rm.datanodes=2|1;gvp.rm.tenant-id=101_IVRAppDefault
2014-08-01 07:12:44.007 DBUG 00000000-00000000 3616 08500000 VGSIPTransportMgr.cxx:3464 VGSIPTransportMgr::ResolveDNS for 56.120.98.109:5060
2014-08-01 07:12:44.007 DBUG 00000000-00000000 3616 08500000 VGSIPTransportMgr.cxx:3575 VGSIPTransportMgr::ResolveDNS nResult 2
2014-08-01T07:12:44.007 Trc 33009 INFO 00000000-00000000 3616 02800FA1 Response sent: SIP/2.0 200 OK
Via: SIP/2.0/UDP 56.120.98.109:5060;branch=z9hG4bK0x2aaab6009410db843cabcdef09
Via: SIP/2.0/UDP 56.120.98.137:5060;branch=z9hG4bK00924DE8-71DD-13D8-B291-87627838AA77-2448594
From: <sip:9712504273@56.120.98.137:5060>;tag=00924DDE-71DD-13D8-B291-87627838AA77-468732
To: <sip:msml=53d874e400021d08@56.120.98.109:5060;dn=53297;record;tenant-dbid=101;media-service=record>;tag=6CA98394-6A24-44EE-029B-6BC73A7D2E3B
CSeq: 2 INFO
Call-ID: 00924DCA-71DD-13D8-B291-87627838AA77-391235@56.120.98.137
Content-Length: 194
Content-Type: application/vnd.radisys.msml+xml
X-Genesys-bypass-resource-list: sip:Genesys@56.120.98.117:5070
Min-SE: 90
X-Genesys-GVP-Session-Data: callsession=83565000-CB44-9338-242C-4166B5019B99;2;1;;;;Resources;IVRAppDefault;
X-Genesys-GVP-Session-ID: 83565000-CB44-9338-242C-4166B5019B99;gvp.rm.datanodes=2|1;gvp.rm.tenant-id=101_IVRAppDefault

<?xml version="1.0" encoding="UTF-8"?>
<msml version="1.1">
<result response="430">
<description>Object does not exists: conn:16027FA0-7CF1-485C-6E85-12C769EAB92C</description>
</result>
</msml>

Could you please advise.

Thanks
RK

Offline rkd

  • Newbie
  • *
  • Posts: 35
  • Karma: 0
Re: RM Active-Active configuration for GQM Recording
« Reply #5 on: August 01, 2014, 05:51:01 PM »
Hi

When we did more analysis on error "Object doesnt exist". .

For the two call legs (one with customer and one with Agent), SIP server selects different RMs and RMs are selecting different MCPs. So the first MCP doesnt know about the second call leg and second MCP doesnt know about the first call leg. So both are failing and sending the Object Not Found error.

How can we make sure the SIP server selects the same RM for the same and RM selects the same Recording MCP for the same call?



Call-ID: 00924DCA-71DD-13D8-B291-87627838AA77-393519 for DN 51099 agent leg
Call-ID: 00924DCA-71DD-13D8-B291-87627838AA77-393520 for customer 5408903553 leg.


07:20:45.957: SIPTR: Received [0,UDP] 1090 bytes from 56.120.98.110:5060 <<<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 56.120.98.137:5060;branch=z9hG4bK00924DE8-71DD-13D8-B291-87627838AA77-2461758
From: <sip:9712504273@56.120.98.137:5060>;tag=00924DDE-71DD-13D8-B291-87627838AA77-471232
To: <sip:msml=53d874e4000220e7@56.120.98.109:5060;dn=51099;record;tenant-dbid=101;media-service=record>;tag=0FA5F991-76A3-4AF9-93A4-4D5109D67E93
CSeq: 1 INVITE
Call-ID: 00924DCA-71DD-13D8-B291-87627838AA77-393519@56.120.98.137
Contact: sip:Genesys@56.120.98.116:5080
Content-Length: 147
Content-Type: application/sdp
Record-Route: <sip:0x20823b60@56.120.98.110:5060;lr;gvp.rm.datanodes=1%7C2;confinstid=53d874e4000220e7;idtag=00000B38>
Min-SE: 90
X-Genesys-GVP-Session-Data: callsession=83565000-344E-07C0-F5DE-4093B331687B;1;2;;;;Resources;IVRAppDefault;
X-Genesys-GVP-Session-ID: 83565000-344E-07C0-F5DE-4093B331687B;gvp.rm.datanodes=1|2;gvp.rm.tenant-id=101_IVRAppDefault
Session-Expires: 1800;refresher=uac
Require: timer

v=0
o=- 268524855 1 IN IP4 56.120.98.116
s=phone-call
c=IN IP4 56.120.98.116
t=0 0
m=audio 24076 RTP/AVP 0
a=rtpmap:0 pcmu/8000
a=inactive


07:20:45.996: SIPTR: Received [0,UDP] 1104 bytes from 56.120.98.109:5060 <<<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 56.120.98.137:5060;branch=z9hG4bK00924DE8-71DD-13D8-B291-87627838AA77-2461760
From: sip:5408903553@207.158.173.13;tag=00924DDE-71DD-13D8-B291-87627838AA77-471233
To: <sip:msml=53d874e4000220e7@56.120.98.109:5060;dn=5408903553;record;tenant-dbid=101;media-service=record>;tag=CBEAA090-5780-4A8D-90BA-0BB9DFFAF83A
CSeq: 1 INVITE
Call-ID: 00924DCA-71DD-13D8-B291-87627838AA77-393520@56.120.98.137
Contact: sip:Genesys@56.120.98.119:5070
Content-Length: 162
Content-Type: application/sdp
Record-Route: <sip:0x33483b50@56.120.98.109:5060;lr;gvp.rm.datanodes=2%7C1;confinstid=53d874e4000220e7;idtag=00000B5E>
Min-SE: 90
X-Genesys-GVP-Session-Data: callsession=83565000-CB44-74FB-E0C0-5A84BA257AB1;2;1;;;;Resources;IVRAppDefault;
X-Genesys-GVP-Session-ID: 83565000-CB44-74FB-E0C0-5A84BA257AB1;gvp.rm.datanodes=2|1;gvp.rm.tenant-id=101_IVRAppDefault
Session-Expires: 1800;refresher=uac
Require: timer

v=0
o=- 268524939 1 IN IP4 56.120.98.119
s=phone-call
c=IN IP4 56.120.98.119
t=0 0
m=audio 24170 RTP/AVP 0
a=rtpmap:0 pcmu/8000
a=maxptime:20
a=inactive


07:20:45.997: Sending  [0,UDP] 1409 bytes to 56.120.98.110:5060 >>>>>
INFO sip:Genesys@56.120.98.116:5080 SIP/2.0
From: <sip:9712504273@56.120.98.137:5060>;tag=00924DDE-71DD-13D8-B291-87627838AA77-471232
To: <sip:msml=53d874e4000220e7@56.120.98.109:5060;dn=51099;record;tenant-dbid=101;media-service=record>;tag=0FA5F991-76A3-4AF9-93A4-4D5109D67E93
Call-ID: 00924DCA-71DD-13D8-B291-87627838AA77-393519@56.120.98.137
CSeq: 2 INFO
Content-Length: 706
Content-Type: application/vnd.radisys.msml+xml
Via: SIP/2.0/UDP 56.120.98.137:5060;branch=z9hG4bK00924DE8-71DD-13D8-B291-87627838AA77-2461762
Contact: <sip:51099@56.120.98.137:5060>
Max-Forwards: 67
Route: <sip:0x20823b60@56.120.98.110:5060;lr;gvp.rm.datanodes=1%7C2;confinstid=53d874e4000220e7;idtag=00000B38>

<?xml version="1.0" encoding="UTF-8"?>
<msml version="1.1">
<createconference name="53d874e4000220e7_record" term="false">
<gvp:recorder>
<gvp:params>
<gvp:param name="id">028SAJJHRK9THCKHGTH7GE5AES002BUG</gvp:param>
<gvp:param name="recordDN">51099</gvp:param>
</gvp:params>
</gvp:recorder>
<audiomix/>
<videolayout>
<selector method="confrole"/>
</videolayout>
</createconference>
<join id1="conn:0FA5F991-76A3-4AF9-93A4-4D5109D67E93" id2="conf:53d874e4000220e7_record">
<stream media="audio"/>
<stream media="video"/>
</join>
<join id1="conn:CBEAA090-5780-4A8D-90BA-0BB9DFFAF83A" id2="conf:53d874e4000220e7_record"> -----------------------
<stream media="audio"/>
<stream media="video"/>
</join></msml>

Offline Kubig

  • Hero Member
  • *****
  • Posts: 2752
  • Karma: 44
Re: RM Active-Active configuration for GQM Recording
« Reply #6 on: August 04, 2014, 06:55:26 AM »
Check SIP server logs why the other RM was choosed.