[test-results] [Bamboo] Asterisk - Team Branches > Pimp My SIP > #416 has FAILED. Change made by root.

Bamboo bamboo at asterisk.org
Sun Jun 16 22:21:46 CDT 2013


-----------------------------------------------------------------------
Asterisk - Team Branches > Pimp My SIP > #416 failed.
-----------------------------------------------------------------------
Code has been updated by root.
1/2 jobs failed, with 0 failing tests.

http://bamboo.asterisk.org/browse/ASTTEAM-PIMPMYSIP-416/


--------------
Failing Jobs
--------------
  - Asterisk 1.8 CentOS 6 32-Bit (CentOS 6): No tests found.



--------------
Code Changes
--------------
root (391950):

>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/
>........
>
>Merged revisions 391947 from file:///srv/subversion/repos/asterisk/trunk
>



--
This message is automatically generated by Atlassian Bamboo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/test-results/attachments/20130616/d4af451e/attachment-0001.htm>


More information about the Test-results mailing list