[test-results] [Bamboo] Asterisk Testing > Asterisk Trunk > #288 has FAILED. Change made by jrose and Kinsey Moore.
Bamboo
bamboo at asterisk.org
Thu May 17 16:40:55 CDT 2012
-----------------------------------------------------------------------
Asterisk Testing > Asterisk Trunk > #288 failed.
-----------------------------------------------------------------------
Code has been updated by jrose, Kinsey Moore.
No failed tests found, a possible compilation error.
http://bamboo.asterisk.org/browse/TESTING-ASTERISKTRUNK-288/
--------------
Failing Jobs
--------------
- Asterisk CentOS 6 64-Bit (CentOS 6): No tests found.
--------------
Code Changes
--------------
jrose (366842):
>logger: Adds additional support for call id logging and chan_sip specific stuff
>
>This patch improves the handling of call id logging significantly with regard
>to transfers and adding APIs to better handle specific aspects of logging.
>Also, changes have been made to chan_sip in order to better handle the creation
>of callids and to enable the monitor thread to bind itself to a particular
>call id when a dialog is determined to be related to a callid. It then unbinds
>itself before returning to normal monitoring.
>
>review: https://reviewboard.asterisk.org/r/1886/
>
Kinsey Moore (366843):
>Make the new SIP_CAUSE backend behave more like the original SIP_CAUSE
>
>There was a slight discrepancy in the behaviors of the old SIP_CAUSE and the
>new SIP_CAUSE/HANGUPCAUSE when a channel had been originated and had not yet
>been answered. This caused the noload_res_srtp_attempt_srtp test to fail since
>the SIP_CAUSE variable was never actually set. This behavior has been restored.
>
--
This message is automatically generated by Atlassian Bamboo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/test-results/attachments/20120517/55478e93/attachment-0001.htm>
More information about the Test-results
mailing list