[test-results] [Bamboo] No agents to build plan Asterisk - 1.8 - FreeBSD 8.1 - i386

[Bamboo]

-------------------------------------------------------------------------------
AST18-FREEBSD81-I386-140 has been queued, but there's no agent capable of building it.
-------------------------------------------------------------------------------

http://bamboo.asterisk.org/browse/AST18-FREEBSD81-I386/log

--------------
Code Changes
--------------
lmadsen (309349):

>Blocked revisions 309348 via svnmerge
>
>........
>  r309348 | lmadsen | 2011-03-03 14:13:11 -0600 (Thu, 03 Mar 2011) | 5 lines
>  
>  Update PickupChan documentation.
>  The PickupChan uses the ampersand as the argument separator.
>  (closes issue #18905)
>  Reported by: vmikhnevych
>  Tested by: vmikhnevych
>........
>

diruggles (309403):

>Merged revisions 309356 via svnmerge from 
>https://origsvn.digium.com/svn/asterisk/branches/1.6.2
>
>................
>  r309356 | diruggles | 2011-03-03 19:42:28 -0500 (Thu, 03 Mar 2011) | 16 lines
>  
>  Merged revisions 309355 via svnmerge from 
>  https://origsvn.digium.com/svn/asterisk/branches/1.4
>  
>  ........
>    r309355 | diruggles | 2011-03-03 19:34:13 -0500 (Thu, 03 Mar 2011) | 9 lines
>    
>    fix small memory leak
>    
>    fix small memory leak caused by a string allocation that wasn't freed
>    
>    (closes issue #18907)
>    Reported by: andy11
>    Patches: 
>          asterisk_trunk-app_externalivr-leak.patch uploaded by andy11 (license 1224)
>  ........
>................
>

rmudgett (309445):

>Get real channel of a DAHDI call.
>
>Starting with Asterisk v1.8, the DAHDI channel name format was changed for
>ISDN calls to: DAHDI/i<span>/<number>[:<subaddress>]-<sequence-number>
>
>There were several reasons that the channel name had to change.
>
>1) Call completion requires a device state for ISDN phones.  The generic
>device state uses the channel name.
>
>2) Calls do not necessarily have B channels.  Calls placed on hold by an
>ISDN phone do not have B channels.
>
>3) The B channel a call initially requests may not be the B channel the
>call ultimately uses.  Changes to the internal implementation of the
>Asterisk master channel list caused deadlock problems for chan_dahdi if it
>needed to change the channel name.  Chan_dahdi no longer changes the
>channel name.
>
>4) DTMF attended transfers now work with ISDN phones because the channel
>name is "dialable" like the chan_sip channel names.
>
>For various reasons, some people need to know which B channel a DAHDI call
>is using.
>
>* Added CHANNEL(dahdi_span), CHANNEL(dahdi_channel), and
>CHANNEL(dahdi_type) so the dialplan can determine the B channel currently
>in use by the channel.  Use CHANNEL(no_media_path) to determine if the
>channel even has a B channel.
>
>* Added AMI event DAHDIChannel to associate a DAHDI channel with an
>Asterisk channel so AMI applications can passively determine the B channel
>currently in use.  Calls with "no-media" as the DAHDIChannel do not have
>an associated B channel.  No-media calls are either on hold or
>call-waiting.
>
>(closes issue #17683)
>Reported by: mrwho
>Tested by: rmudgett
>
>(closes issue #18603)
>Reported by: arjankroon
>Patches:
>      issue17683_18603_v1.8_v2.patch uploaded by rmudgett (license 664)
>Tested by: stever28, rmudgett
>


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