[asterisk-bugs] [Asterisk 0014652]: [patch] early-dial SIP 484 "incomplete address"

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=14652 
====================================================================== 
Reported By:                vieri
Assigned To:                dvossel
====================================================================== 
Project:                    Asterisk
Issue ID:                   14652
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
Target Version:             1.4.28
Asterisk Version:           1.4.23 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-03-12 04:40 CDT
Last Modified:              2009-09-09 12:55 CDT
====================================================================== 
Summary:                    [patch] early-dial SIP 484 "incomplete address"
Description: 
Calls in which at least one Grandstream GXP2000 or GXP280 is involved, get
dropped after about 20 seconds. This happens only if the Grandstreams are
configured to use "early dial" and Asterisk has pedantic=yes (with
pedantic=no the calls are not dropped).

I really need pedantic=yes to encode the # digits.

Would it be possible to use pedantic=no but make the # digits "work"?
(because I realize this may be a Grandstream firmware bug which I don't
think will be fixed any time soon)


====================================================================== 

---------------------------------------------------------------------- 
 (0110433) dvossel (administrator) - 2009-09-09 12:55
 https://issues.asterisk.org/view.php?id=14652#c110433 
---------------------------------------------------------------------- 
Vieri, sorry it has taken me so long to get back to this issue.  Thank you
for the update.  I've reviewed the log files and I'm still puzzled as to
why this is happening.

For some reason when pedantic=yes, the ACK to the 200 OK indicating call
setup is complete is not processed.  This results in the 200 OK being
retransmitted over and over again until it times out which causes the call
to fail.  There are a few places in the code that could cause a ACK to be
ignored when pedantic=yes, and without debugging I really have no idea what
is causing it.  

I've uploaded a patch that includes some debug output in the form of
WARNING messages for the purpose of determining why the ACK in response to
the 200 OK is not being processed.  If it is possible, please update to the
latest 1.4 code, apply the debug patch, and provide cli output. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-09-09 12:55 dvossel        Note Added: 0110433                          
======================================================================