[asterisk-bugs] [Asterisk 0018534]: if fastStart is enabled, Progress message is sent when it shouldn't

[Asterisk Bug Tracker]

The following issue has been SUBMITTED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18534 
====================================================================== 
Reported By:                under
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18534
Category:                   Channels/chan_h323
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.0 - SECURITY ONLY! Test 1.6.2 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-12-27 03:16 CST
Last Modified:              2010-12-27 03:16 CST
====================================================================== 
Summary:                    if fastStart is enabled, Progress message is sent
when it shouldn't
Description: 
If fastStart is enabled, Asterisk sends H.323 Progress message immediately
when incoming call arrives. H.323 Progress message contains media channel
capabilities (RTP info: codec, port, IP address).

After this some originating equipment "thinks" Asterisk has established a
voice path to the called party (because Asterisk presents RTP info). But
Asterisk might not have done this (for example no route configured in
dialplan). After this Asterisk migh execute Hangup and send H.323
ReleaseComplete message. And after this originating party "thinks" : "This
terminator (Asterisk) has established a voice path, but cleared the call. I
won't try next route in my hunting table, because we had a voice path
established.". 

This is faulty situation because originating company has problems in
delivering calls in this case.
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-12-27 03:16 under          New Issue                                    
2010-12-27 03:16 under          Asterisk Version          => 1.6.0 - SECURITY
ONLY! Test 1.6.2
2010-12-27 03:16 under          Regression                => No              
2010-12-27 03:16 under          SVN Branch (only for SVN checkouts, not tarball
releases) => N/A             
======================================================================