[test-results] [Bamboo] Asterisk - Trunk > Ubuntu Lucid (10.04) > #342 was SUCCESSFUL (with 148 tests). Change made by rmudgett.

[Bamboo]

-----------------------------------------------------------------------
Asterisk - Trunk > Ubuntu Lucid (10.04) > #342 was successful.
-----------------------------------------------------------------------
Code has been updated by rmudgett.
All 2 jobs passed with 148 tests in total.

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


--------------
Code Changes
--------------
rmudgett (307883):

>Merged revisions 307879 via svnmerge from 
>https://origsvn.digium.com/svn/asterisk/branches/1.8
>
>........
>  r307879 | rmudgett | 2011-02-15 10:13:55 -0600 (Tue, 15 Feb 2011) | 37 lines
>  
>  No response sent for SIP CC subscribe/resubscribe request.
>  
>  Asterisk does not send a response if we try to subscribe for call
>  completion after we have received a 180 Ringing.  You can only subscribe
>  for call completion when the call has been cleared.
>  
>  When we receive the 180 Ringing, for this call, its call-completion state
>  is 'CC_AVAILABLE'.  If we then send a subscribe message to Asterisk, it
>  trys to change the call-completion state to 'CC_CALLER_REQUESTED'.
>  Because this is an invalid state change, it just ignores the message.  The
>  only state Asterisk will accept our subscribe message is in the
>  'CC_CALLER_OFFERED' state.
>  
>  Asterisk will go into the 'CC_CALLER_OFFERED' when the SIP client clears
>  the call by sending a CANCEL.
>  
>  Asterisk should always send a response.  Even if its a negative one.
>  
>  
>  The fix is to allow for the CCSS core to notify a CC agent that a failure
>  has occurred when CC is requested.  The "ack" callback is replaced with a
>  "respond" callback.  The "respond" callback has a parameter indicating
>  either a successful response or a specific type of failure that may need
>  to be communicated to the requester.
>  
>  (closes issue #18336)
>  Reported by: GeorgeKonopacki
>  Tested by: mmichelson, rmudgett
>  
>  JIRA SWP-2633
>  
>  (closes issue #18337)
>  Reported by: GeorgeKonopacki
>  Tested by: mmichelson
>  
>  JIRA SWP-2634
>........
>


--------------
Tests
--------------
Fixed Tests (1)
   - AsteriskTestSuite: S/rfc2833 dtmf detect

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