About
These variables are used in various modules related to CDR and accounting:
Module name |
---|
mod_cdr_csv |
mod_cdr_sqlite |
mod_xml_ldap |
mod_nibblebill |
accountcode
Account code is mostly an arbitrary value that you can assign on a per leg basis. An important feature of accountcode is that if its value matches one of the CDR CSV templates defined in cdr_csv.conf.xml then that CDR template will be used when generating a CSV CDR.
Usage:
<action application="set" data="accountcode=custom"/>
Implemented By:
Module Name | Source File | Last Revised |
mod_cdr_csv | mod_cdr_csv.c | 6564 |
cdr_csv_base
Description needed! Please contribute one.
Usage:
Example needed! Please contribute one.
Implemented By:
Module Name | Source File | Last Revised |
mod_cdr_csv | mod_cdr_csv.c | 6542 |
copy_xml_cdr
Copy's the other leg's XML CDR into this leg's CDR. For example, the A leg's CDR will contain a variable named b_leg_cdr whose contents are the URL-encoded XML CDR data from the B leg. This variable must be set on the B leg, so use {copy_xml_cdr=true} in the dialstring or use export instead of set.
Usage:
<action application="bridge" data="{copy_xml_cdr=true} user/${dialed_extension}@${domain_name}"/>
Implemented By:
Module Name | Source File | Last Revised |
core | switch_ivr_bridge.c | 8955 |
failed_xml_cdr_prefix
If you set that on the A leg and any and all failed B originates generate a full XML CDR report and set it as a variable, this includes during a forked dial.
So say you try to call sofia/profile/a@xxxxxxx,sofia/profile/b@xxxxxxx
And it fails completely, before you make the call you set failed_xml_cdr_prefix to "bad_call"
Then you end up with ${bad_call_1} and ${bad_call_2} which are each a full XML report including all the vars etc.
Usage:
<action application="set" data="failed_xml_cdr_prefix=failinggw" />
See also:
- Maillist message [1]
Implemented By:
Module Name | Source File | Last Revised |
core | switch_ivr_originate.c | 8730 |
process_cdr
Indicates how to process CDR records.
Can be undefined or set to "false", "true", "a_only", "b_only"
- false - indicates to not process the record.
- true - or undefined indicates the default behavior which is to process all CDR records.
- a_only - indicates to only process CDR records on the inbound leg of a call.
- b_only - indicates to only process CDR records on the outbound leg of a call.
This variable is unconditionally exported
Usage:
<action application="set" data="process_cdr=a_only"/>
Implemented By:
Module Name | Source File | Last Revised |
core | switch_core_session.c | 7214 |
core | switch_core_state_machine.c | 7212 |
skip_cdr_causes
This is a list of call hangup causes that should not trigger cdr processing.
Implemented By:
Module Name | Source File | Last Revised |
---|---|---|
mod_sofia | sofia.c | 2012-09-19, git commit 3cf238fc9a1370a45d362c2193b8d3634ccd1d11 |
xml_cdr_base
Description needed! Please contribute one.
Usage:
Example needed! Please contribute one. |
Implemented By:
Module Name | Source File | Last Revised |
mod_xml_cdr | mod_xml_cdr.c | 6708 |
1 Comment
Ryan Harris
The variables on this document have been reconciled into the Variables Master List.