mirror of
https://github.com/asterisk/asterisk.git
synced 2026-05-04 20:33:53 +00:00
app_queue: Add option to not log Restricted Caller ID to queue_log
Add a queue option log-restricted-caller-id to strip the Caller ID when storing the ENTERQUEUE event
in the queue log if the Caller ID is restricted.
Resolves: #765
UpgradeNote: Add a new column to the queues table:
queue_log_option_log_restricted ENUM('0','1','off','on','false','true','no','yes')
to control whether the Restricted Caller ID will be stored in the queue log.
UserNote: Add a Queue option log-restricted-caller-id to control whether the Restricted Caller ID
will be stored in the queue log.
If log-restricted-caller-id=no then the Caller ID will be stripped if the Caller ID is restricted.
(cherry picked from commit 192a848311)
This commit is contained in:
committed by
Asterisk Development Team
parent
835d12ead2
commit
8a09a6ca6d
@@ -51,6 +51,13 @@ monitor-type = MixMonitor
|
||||
;
|
||||
;log_membername_as_agent = no
|
||||
;
|
||||
; log-restricted-caller-id controls whether the Restricted Caller ID will be stored
|
||||
; in the queue log.
|
||||
; If log-restricted-caller-id=no then the Caller ID will be stripped if the Caller ID
|
||||
; is restricted.
|
||||
; Default is 'yes', which means the Caller ID is always stored.
|
||||
;log-restricted-caller-id = yes
|
||||
;
|
||||
; force_longest_waiting_caller will cause app_queue to make sure callers are offered
|
||||
; in order (longest waiting first), even for callers across multiple queues.
|
||||
; Before a call is offered to an agent, an additional check is made to see if the agent
|
||||
|
||||
Reference in New Issue
Block a user