[test-results] [Bamboo] Asterisk - Trunk > Ubuntu Lucid (10.04) > #775 has FAILED (1 tests failed). Change made by kmoore.

Bamboo bamboo at asterisk.org
Tue Jul 19 23:53:35 CDT 2011


-----------------------------------------------------------------------
Asterisk - Trunk > Ubuntu Lucid (10.04) > #775 failed.
-----------------------------------------------------------------------
Code has been updated by kmoore.
1/136 tests failed.

http://bamboo.asterisk.org/browse/ASTTRUNK-LUCID-775/


--------------
Failing Jobs
--------------
  - i386 (Default Stage): 1 of 136 tests failed.


--------------
Code Changes
--------------
kmoore (328825):

>Merged revisions 328824 via svnmerge from 
>https://origsvn.digium.com/svn/asterisk/branches/1.10
>
>................
>  r328824 | kmoore | 2011-07-19 13:05:21 -0500 (Tue, 19 Jul 2011) | 18 lines
>  
>  Merged revisions 328823 via svnmerge from 
>  https://origsvn.digium.com/svn/asterisk/branches/1.8
>  
>  ........
>    r328823 | kmoore | 2011-07-19 12:57:18 -0500 (Tue, 19 Jul 2011) | 11 lines
>    
>    RTP bridge away with inband DTMF and feature detection
>    
>    When deciding whether Asterisk was allowed to bridge the call away from the
>    core, chan_sip did not take into account the usage of features on dialed
>    channels that require monitoring of DTMF on channels utilizing inband DTMF.
>    This would cause Asterisk to allow the call to be locally or remotely bridged, 
>    preventing access to the data required to detect activations of such features.
>    
>    (closes 17237)
>    Review: https://reviewboard.asterisk.org/r/1302/
>  ........
>................
>

kmoore (328772):

>Merged revisions 328771 via svnmerge from 
>https://origsvn.digium.com/svn/asterisk/branches/1.10
>
>................
>  r328771 | kmoore | 2011-07-19 10:46:54 -0500 (Tue, 19 Jul 2011) | 18 lines
>  
>  Merged revisions 328770 via svnmerge from 
>  https://origsvn.digium.com/svn/asterisk/branches/1.8
>  
>  ........
>    r328770 | kmoore | 2011-07-19 10:43:32 -0500 (Tue, 19 Jul 2011) | 11 lines
>    
>    MeetMe requests a PIN twice in some circumstances
>    
>    If a call to MeetMe includes both the dynamic(D) and always request PIN(P)
>    options, MeetMe will ask for the PIN two times: once for creating the
>    conference and once for entering the conference.  This behavior was introduced
>    in rev 311616 when adding the CONFFLAG_ALWAYSPROMPT option to the logic branch
>    controlling PIN entry for joining a conference.
>    
>    (closes AST-601)
>    Review: https://reviewboard.asterisk.org/r/1305/
>  ........
>................
>


--------------
Tests
--------------
New Test Failures (1)
   - AsteriskTestSuite: S/channels/ s i p/sip tls call

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


More information about the Test-results mailing list