GVP 8.1 encrypt the entries via a DTMF input

Hello

How can you encrypt the entries in the log have been made ​​over a DTMF input?

Hi,

I’m not aware of any configuration allowing you to hide/remove DTMF input from MCP/Media Server log (debug level). However, I’ve heard this feature may be introduced in upcoming GVP release…

Why do you need it?

R.

It is a banking application. There it is forbidden to log any data from customers.

Hi,

The following will mask the dtmf digits. Although, I don’t know if this is exactly what you want - you could also have a look at the VoiceXML 2.1 reference guide for more information.

Kind Regards,
IF

1 Like

My problem is that when the customer enters his password via DTMF, it will appear in the log. This must not occur in debug mode.

Sailer

1 Like

Did you found a solution ?

We are facing same scenario.

As TheSailer mentioned

com.genesyslab.private property or gvp:private attribute (in tags that support it)
1 Like

can you not just scrub the logs for personal data to be compliant…..

[log-filter-data]
Password = hide

This would give the below in the logs (password would be starred out)

message RequestSetCallInfo
AttributeConsultType 3
AttributeOriginalConnID 008b012ece62c8be
AttributeUpdateRevision 2752651
AttributeUserData [111] 00 27 01 00
‘DNIS’ ‘8410’
‘PASSWORD’ ‘****’
‘RECORD_ID’ ‘8313427’
AttributeConnID 008b012ece62c922

So you would just add in the other KVP that you want to hide such as

‘Memorable Name’ ‘Santa’
‘Memorable Place’ ‘Stringfellows’
‘Address4’ ‘Nelson Mandela Towers, Peckham’
‘Customer Risk Group’ ‘HIGHRISK’
‘Customer Name’ ‘MR Magoo’

I am not sure about your statement, Tambo. I think, you mean masking on T-Lib level, but he means hiding data within MCP log (there is no T-Lib) generally

I suspect that the question relates to PCI compliance and everybody forgets that if you are not using SRTP then the DTMF digits can be reconstructed from SIP and RTP sniffing anyway … thus logging of DTMF digits is the least of your worries to keep a PCIM QSA happy!

Regards

  1. Composer: com.genesyslab.private property or gvp:private attribute just for DTMF input
  2. CME app: log-filter-data for Tlib messaging
  3. MFSINK: custom verbosity per module (tricky, however, most advanced option): https://genesyspartner.force.com/customercare/pkb_Home?id=kA0U00000004TcSKAU&l=en_US&fs=Search&pn=1

Fra

2 Likes

Nice :smiley:
As well as Greg observation.

This article defines option #1 from Fra
https://genesyspartner.force.com/customercare/pkb_Home?id=kA3U00000000C9iKAE