" /> Hide AttachedData - Genesys CTI User Forum

Author Topic: Hide AttachedData  (Read 2295 times)

Offline raza990

  • Full Member
  • ***
  • Posts: 214
  • Karma: 5
Hide AttachedData
« on: June 16, 2016, 08:49:07 AM »
Advertisement
[b]Hi Guys,[/b]

I have an query regarding Masking AttachedData from X-Genesys- in SIP Server,RM and MCP logs.

[u]For Example:[/u]

12:03:38.493: SIPTR: Received [0,UDP] 2286 bytes from 10.XXX.XXX.XX:5075 <<<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.XXX.XXX.XX:5060;branch=z9hG4bK53CCCB1D-EC6C-4867-8499-884768AE7CDE-58118
From: <sip:90556205934@10.240.176.82:5060>;tag=91E03825-0C72-4278-B857-86B5CA4331FB-21321
To: <sip:Resources@10.XXX.XXX.XX:5060>;tag=CB1DB24B-CA47-44F9-E88D-7F47163AE81A
CSeq: 1 INVITE
Call-ID: 26FFF0FB-C887-4CAB-84AB-6F5550411EF8-20846@10.XXX.XXX.XX
Contact: sip:Genesys@10.XXX.XXX.XX:5070
Content-Length: 203
Content-Type: application/sdp
Record-Route: <sip:1C786BA0@10.XXX.XXX.XX:5075;lr;gvp.rm.datanodes=1;idtag=00002894>
X-Genesys-gsw-session-dbid: 136
X-Genesys-gsw-predictive-call: on
X-Genesys-gsw-ivr-profile-id: 148
X-Genesys-GSW_PHONE: 0556205934
X-Genesys-MobNumber: 0556205934
X-Genesys-Call Result: 0
X-Genesys-GSW_FROM: 32400
X-Genesys-GSW_TZ_OFFSET: 14400
X-Genesys-Language: ENG
[b][color=navy]X-Genesys-Customer: Raza Ur Rehman [/color][/b]

Where, I want to hide [b]X-Genesys-Customer[/b] from both SIP Server,RM & MCP logs.

Offline Kubig

  • Hero Member
  • *****
  • Posts: 2755
  • Karma: 44
Re: Hide AttachedData
« Reply #1 on: June 16, 2016, 08:51:52 AM »
My opinion -> this is not possible at this moment.

Offline Raja Sekhar

  • Jr. Member
  • **
  • Posts: 72
  • Karma: -1
  • Genesys Routing Applciation developer
Re: Hide AttachedData
« Reply #2 on: July 18, 2016, 06:18:47 AM »
i agree with Kubig.

But if there is a better of development involved in this application, then this is completely possible.

For Example:

You can design your application with  all variables with any standard prefix like CTI_dbid,CTI_PHONE.
Similary decalre different prefix of Confidential data , like CONF_CUSTOMER.

And you can configure the prefix in user data map filter option in msml, there the data with prefix CTI* should be allowed, so that CONF prefix data will never be communicated.