diff options
| author | Matthew Jordan <mjordan@digium.com> | 2013-06-17 03:00:38 +0000 |
|---|---|---|
| committer | Matthew Jordan <mjordan@digium.com> | 2013-06-17 03:00:38 +0000 |
| commit | 6258bbe7bd1885ac5dec095ed0c4490c83a99f44 (patch) | |
| tree | ff2794f730ca55903a09b9fe7f73f45169a71386 /cel | |
| parent | 67e35c7b4748c3cef954820a2b182e2a5edf8d98 (diff) | |
Update Asterisk's CDRs for the new bridging framework
This patch is the initial push to update Asterisk's CDR engine for the new
bridging framework. This patch guts the existing CDR engine and builds the new
on top of messages coming across Stasis. As changes in channel state and bridge
state are detected, CDRs are built and dispatched accordingly. This
fundamentally changes CDRs in a few ways.
(1) CDRs are now *very* reflective of the actual state of channels and bridges.
This means CDRs track well with what an actual channel is doing - which
is useful in transfer scenarios (which were previously difficult to pin
down). It does, however, mean that CDRs cannot be 'fooled'. Previous
behavior in Asterisk allowed for CDR applications, channels, and other
properties to be spoofed in parts of the code - this no longer works.
(2) CDRs have defined behavior in multi-party scenarios. This behavior will not
be what everyone wants, but it is a defined behavior and as such, it is
predictable.
(3) The CDR manipulation functions and applications have been overhauled. Major
changes have been made to ResetCDR and ForkCDR in particular. Many of the
options for these two applications no longer made any sense with the new
framework and the (slightly) more immutable nature of CDRs.
There are a plethora of other changes. For a full description of CDR behavior,
see the CDR specification on the Asterisk wiki.
(closes issue ASTERISK-21196)
Review: https://reviewboard.asterisk.org/r/2486/
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@391947 65c4cc65-6c06-0410-ace0-fbb531ad65f3
Diffstat (limited to 'cel')
| -rw-r--r-- | cel/cel_manager.c | 2 | ||||
| -rw-r--r-- | cel/cel_radius.c | 2 | ||||
| -rw-r--r-- | cel/cel_tds.c | 2 |
3 files changed, 3 insertions, 3 deletions
diff --git a/cel/cel_manager.c b/cel/cel_manager.c index e1d0dc148..245c7800d 100644 --- a/cel/cel_manager.c +++ b/cel/cel_manager.c @@ -129,7 +129,7 @@ static void manager_log(const struct ast_event *event, void *userdata) record.application_name, record.application_data, start_time, - ast_cel_get_ama_flag_name(record.amaflag), + ast_channel_amaflags2string(record.amaflag), record.unique_id, record.linked_id, record.user_field, diff --git a/cel/cel_radius.c b/cel/cel_radius.c index 0edf57f4c..9067a0491 100644 --- a/cel/cel_radius.c +++ b/cel/cel_radius.c @@ -150,7 +150,7 @@ static int build_radius_record(VALUE_PAIR **send, struct ast_cel_event_record *r return -1; } /* AMA Flags */ - amaflags = ast_strdupa(ast_cel_get_ama_flag_name(record->amaflag)); + amaflags = ast_strdupa(ast_channel_amaflags2string(record->amaflag)); if (!rc_avpair_add(rh, send, PW_AST_AMA_FLAGS, amaflags, strlen(amaflags), VENDOR_CODE)) { return -1; } diff --git a/cel/cel_tds.c b/cel/cel_tds.c index df2b573bf..1bb4d517e 100644 --- a/cel/cel_tds.c +++ b/cel/cel_tds.c @@ -206,7 +206,7 @@ retry: ciddnid_ai, exten_ai, context_ai, channel_ai, app_ai, appdata_ai, start, (record.event_type == AST_CEL_USER_DEFINED) ? record.user_defined_name : record.event_name, - ast_cel_get_ama_flag_name(record.amaflag), uniqueid_ai, linkedid_ai, + ast_channel_amaflags2string(record.amaflag), uniqueid_ai, linkedid_ai, userfield_ai, peer_ai); if (erc == FAIL) { |