[test-results] [Bamboo] Asterisk - 1.6.2 - Linux - x86_64 build 110 has FAILED (1 tests failed, no failures were new). Change made by dvossel

[Bamboo]

-------------- next part --------------
-----------------------------------------------------------
AST-162-110 failed.
-----------------------------------------------------------
Code has been updated by dvossel.
1/59 tests failed.

http://bamboo.asterisk.org/browse/AST-162-110/        


--------------
Code Changes
--------------
dvossel (285567):

>Merged revisions 285566 via svnmerge from 
>https://origsvn.digium.com/svn/asterisk/branches/1.4
>
>........
>  r285566 | dvossel | 2010-09-08 17:07:31 -0500 (Wed, 08 Sep 2010) | 2 lines
>  
>  In retrans_pkt, do not unlock pvt until the end of the function on a transmit failure.
>........
>

dvossel (285563):

>Fixes interoperability problems with session timer behavior in Asterisk.
>
>CHANGES:
>1. Never put "timer" in "Require" header.  This is not to our benefit
>and RFC 4028 section 7.1 even warns against it.  It is possible for one
>endpoint to perform session-timer refreshes while the other endpoint does
>not support them.  If in this case the end point performing the refreshing
>puts "timer" in the Require field during a refresh, the dialog will
>likely get terminated by the other end.
>
>2. Change the behavior of 'session-timer=accept' in sip.conf (which is
>the default behavior of Asterisk with no session timer configuration
>specified) to only run session-timers as result of an incoming INVITE
>request if the INVITE contains an "Session-Expires" header... Asterisk is
>currently treating having the "timer" option in the "Supported" header as
>a request for session timers by the UAC.  I do not agree with this.  Session
>timers should only be negotiated in "accept" mode when the incoming INVITE
>supplies a "Session-Expires" header, otherwise RFC 4028 says we should
>treat a request containing no "Session-Expires" header as a session with
>no expiration.
>
>Below I have outlined some situations and what Asterisk's behavior is.
>The table reflects the behavior changes implemented by this patch.
>
>SITUATIONS:
>-Asterisk as UAS
>1. Incoming INVITE: NO  "Session-Expires"
>2. Incoming INVITE: HAS "Session-Expires"
>
>-Asterisk as UAC
>3. Outgoing INVITE: NO  "Session-Expires". 200 Ok Response HAS "Session-Expires" header
>4. Outgoing INVITE: NO  "Session-Expires". 200 Ok Response NO  "Session-Expires" header
>5. Outgoing INVITE: HAS "Session-Expires".
>
>Active   - Asterisk will have an active refresh timer regardless if the other endpoint does.
>Inactive - Asterisk does not have an active refresh timer regardless if the other endpoint does.
>XXXXXXX  - Not possible for mode.
>______________________________________
>|SITUATIONS | 'session-timer' MODES  |
>|___________|________________________|
>|           | originate  |  accept   |
>|-----------|------------|-----------|
>|1.         |   Active   | Inactive  |
>|2.         |   Active   |  Active   |
>|3.         | XXXXXXXX   | Active    |
>|4.         | XXXXXXXX   | Inactive  |
>|5.         |   Active   | XXXXXXXX  |
>--------------------------------------
>
>
>(closes issue #17005)
>Reported by: alexrecarey
>
>


--------------
Tests
--------------
Failed Tests (1)
   - AsteriskTestSuite: Callparking (Existing)


--------------
Error Summary
--------------
   find: `/home/russell/.texmf-config': No such file or directory
   find: `/home/russell/texmf': No such file or directory
   compiling asterisk.tex...
   compiling asterisk.tex...
   compiling asterisk.tex...


--
This message is automatically generated by Atlassian Bamboo

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