[test-results] [Bamboo] Asterisk - 1.6.2 > Mac OS X Tiger (10.4) > #17 > Power PC has FAILED. Change made by jpeeler.

[Bamboo]

-------------- next part --------------
----------------------------------------------------------------------------
Asterisk - 1.6.2 > Mac OS X Tiger (10.4) > #17 > Power PC failed.
----------------------------------------------------------------------------
Code has been updated by jpeeler.
No failed tests found, a possible compilation error.

http://bamboo.asterisk.org/browse/AST162-TIGER-PPC-17/        


--------------
Code Changes
--------------
jpeeler (297073):

>Merged revisions 297072 via svnmerge from 
>https://origsvn.digium.com/svn/asterisk/branches/1.4
>
>........
>  r297072 | jpeeler | 2010-12-01 11:50:09 -0600 (Wed, 01 Dec 2010) | 23 lines
>  
>  Fix not stopping MOH when transfered local channel queue member is answered.
>  
>  The problem here is only present when local channels are used with the MOH
>  passthru option as well as no optimization (/nm). I will describe the slightly
>  bizarre scenario that was used to test, where phones B and C are queue members:
>  
>  Phone A dials into a queue with two members using local channels and the above
>  options. Phone B answers. Phone A blind transfers phone B into the same queue.
>  Phone A hangs up. Phone C answers, but phone B didn't stop playing MOH.
>  
>  In this scenario, the unhold frame that should have gotten to phone B never
>  arrived due to the masquerade from the blind transfer. This is usually fine
>  since app_queue manages the starting and stopping of MOH. However, with the
>  passthrough option enabled when app_queue attempts to stop MOH it tries to do
>  so on the local channel rather than the real channel. The easiest solution
>  was to just make sure to send an unhold frame during the transfer since it
>  wouldn't make sense to have MOH playing after a transfer anyway. This only
>  modifies SIP transfers, but the other transfers did not seem to be a problem.
>  If DTMF based transfers were a problem it might be okay to add ast_moh_stop
>  to finishup, but I didn't want to have to add that unless required.
>  
>  ABE-2624
>........
>


--------------
Error Summary
--------------
   Package gmime-2.0 was not found in the pkg-config search path.
   Perhaps you should add the directory containing `gmime-2.0.pc'
   to the PKG_CONFIG_PATH environment variable
   No package 'gmime-2.0' found
   Package gmime-2.2 was not found in the pkg-config search path.
   Perhaps you should add the directory containing `gmime-2.2.pc'
   to the PKG_CONFIG_PATH environment variable
   No package 'gmime-2.2' found
   Package gtk+-2.0 was not found in the pkg-config search path.
   Perhaps you should add the directory containing `gtk+-2.0.pc'
   to the PKG_CONFIG_PATH environment variable
   No package 'gtk+-2.0' found
   Package gtk+-2.0 was not found in the pkg-config search path.
   Perhaps you should add the directory containing `gtk+-2.0.pc'
   to the PKG_CONFIG_PATH environment variable
   No package 'gtk+-2.0' found
   No such process
   asterisk.c line 315 (ast_register_file_version): Error obtaining write lock: Invalid argument
   asterisk.c line 317 (ast_register_file_version): Error releasing rwlock: Invalid argument
   asterisk.c line 315 (ast_register_file_version): Error obtaining write lock: Invalid argument
   asterisk.c line 317 (ast_register_file_version): Error releasing rwlock: Invalid argument
   asterisk.c line 315 (ast_register_file_version): Error obtaining write lock: Invalid argument
   asterisk.c line 317 (ast_register_file_version): Error releasing rwlock: Invalid argument
   asterisk.c line 315 (ast_register_file_version): Error obtaining write lock: Invalid argument
   asterisk.c line 317 (ast_register_file_version): Error releasing rwlock: Invalid argument
   asterisk.c line 315 (ast_register_file_version): Error obtaining write lock: Invalid argument
   asterisk.c line 317 (ast_register_file_version): Error releasing rwlock: Invalid argument
   asterisk.c line 315 (ast_register_file_version): Error obtaining write lock: Invalid argument
   asterisk.c line 317 (ast_register_file_version): Error releasing rwlock: Invalid argument
   asterisk.c line 315 (ast_register_file_version): Error obtaining write lock: Invalid argument
   asterisk.c line 317 (ast_register_file_version): Error releasing rwlock: Invalid argument
   asterisk.c line 315 (ast_register_file_version): Error obtaining write lock: Invalid argument
   asterisk.c line 317 (ast_register_file_version): Error releasing rwlock: Invalid argument
   Workaround Bonjour: Unknown error: 0


--
This message is automatically generated by Atlassian Bamboo

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/test-results/attachments/20101201/821e3301/attachment.htm