- Joined
- Aug 24, 2017
- Messages
- 1
- Reaction score
- 2
The new 3CX client app highlights that a call is being recorded and as a previous post has requested, can now comply with PCI-DSS requirements by pausing the recording whilst card details are relayed.
The logical implication and deployment scenario would be to have a dedicated extension for taking card payments with the console settings for that extension set to allow the pausing of recordings.
Currently, the 3CX client app (whether used in CTI or soft-phone mode) allows any end user / extension to stop the recording of any call despite the admin setting in the 3CX being set as 'record all calls for this extension'.
This is a step backwards and possible oversight in what the app can do for PCI-DSS (which is great) but should not allow end users / extensions to be able to override a company wide, global or admin setting.
This is Data protection issue and in some instances a legal or regulatory compliance issue. Can this be looked at as a high priority.
The logical implication and deployment scenario would be to have a dedicated extension for taking card payments with the console settings for that extension set to allow the pausing of recordings.
Currently, the 3CX client app (whether used in CTI or soft-phone mode) allows any end user / extension to stop the recording of any call despite the admin setting in the 3CX being set as 'record all calls for this extension'.
This is a step backwards and possible oversight in what the app can do for PCI-DSS (which is great) but should not allow end users / extensions to be able to override a company wide, global or admin setting.
This is Data protection issue and in some instances a legal or regulatory compliance issue. Can this be looked at as a high priority.