96 lines
3.2 KiB
Plaintext
96 lines
3.2 KiB
Plaintext
[general]
|
|
|
|
; resolution: keyword: Resolution for time representation: sec, msec or usec
|
|
;resolution=msec
|
|
|
|
; guardtime: int: Time in ms to remember hungup channels to avoid race conditions
|
|
;guardtime=5000
|
|
|
|
; updates: bool: Emit call cdr message when call status has changed
|
|
;updates=true
|
|
|
|
; status: bool: Emit call cdr status messages for the call duration
|
|
;status=false
|
|
|
|
; status_interval: int: The time interval in seconds to emit call cdr status messages
|
|
; Note: If status is set to false this interval will be ignored
|
|
; If this interval is set to 0 a single cdr status is emitted at answer time
|
|
; Default 60s
|
|
; Min 60s
|
|
; Max 600s
|
|
;status_interval=60
|
|
|
|
; status_answer: bool: Emit cdr status message immediately when the call is answered
|
|
; If set to false the first cdr status is sent after status_interval
|
|
;status_answer=true
|
|
|
|
; ring_on_progress: bool: Start ring timer when processing call.progress
|
|
; This parameter can be overridden in call.progress message by a 'ringing' parameter
|
|
;ring_on_progress=no
|
|
|
|
|
|
[parameters]
|
|
; Each line consists of name=bool where name is the name of the parameter being
|
|
; monitored while bool allows or disallows subsequent overwrites of the initial
|
|
; non-empty value
|
|
; You can add your own monitored parameters that will appear in "call.cdr"
|
|
|
|
; The following parameters are handled by default but you can change their
|
|
; overwrite behaviour
|
|
;billid=true
|
|
;reason=true
|
|
;address=false
|
|
;caller=false
|
|
;called=false
|
|
;calledfull=false
|
|
;username=false
|
|
|
|
; The following parameters are handled internally and cannot be changed:
|
|
; time, chan, operation, cdrwrite, cdrtrack, cdrcreate, cdrid, runid,
|
|
; direction, status, duration, billtime, ringtime
|
|
|
|
|
|
; Special section for time formatting
|
|
; Formatting rules
|
|
; YYYY | %Y -> Year (2012)
|
|
; YY | %y -> Year, last two digits (00-99)
|
|
; MM | %m -> Month as a decimal number (01-12)
|
|
; DD | %d -> Day of the month (01-31)
|
|
; HH | %H -> Hour in 24h format (00-23)
|
|
; mm | %M -> Minute (00-59)
|
|
; SS | %S -> Second (00-60)
|
|
; Note the value is rounded
|
|
; UTC -> If present the time will represent the UTC time. If is missing
|
|
; the time will represent local time zone
|
|
; N*u -> Milliseconds and Microseconds.
|
|
; Note! The value is rounded
|
|
; EG: time: 1.123456
|
|
; s.u -> 1.1
|
|
; s.uu -> 1.12
|
|
; s.uuu -> 1.123
|
|
; s.uuuu -> 1.1234
|
|
; s.uuuuu -> 1.12346
|
|
; s.uuuuuu -> 1.123456
|
|
; Other formats may me used but they must correspond with C strftime method formats
|
|
; Important! If duplicate formats are ignored!
|
|
; Eg: date : 09 14 2012
|
|
; YYYY YY DD DD mm DD-> 2012 YY 14 DD 09 DD
|
|
|
|
;[formatted-timers]
|
|
; Append the call start time in call cdr message with the given format
|
|
; Eg: call_start_time=YY/MM/DD HH:mm:SS.uuuuuu UTC
|
|
;call_start_time=
|
|
|
|
; Append the call answer time in call cdr message with the given format
|
|
; Eg: call_answer_time=YY/MM/DD HH:mm:SS.uuuuuu UTC
|
|
;call_answer_time=
|
|
|
|
; Append the call hangup time in call cdr message with the given format
|
|
; Eg: call_hangup_time=YY/MM/DD HH:mm:SS.uuuuuu UTC
|
|
;call_hangup_time=
|
|
|
|
; Append the call duration in call cdr message with the given format
|
|
; Allowed formats: HH mm SS N*u
|
|
; Eg: HH:mm:SS.uuu
|
|
;duration_call=
|