[asterisk-bugs] [Asterisk 0013891]: "empty" overlap-dial-in doesn't work

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13891 
====================================================================== 
Reported By:                smurfix
Assigned To:                jpeeler
====================================================================== 
Project:                    Asterisk
Issue ID:                   13891
Category:                   Core/PBX
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.1 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-11-12 14:41 CST
Last Modified:              2008-11-12 23:38 CST
====================================================================== 
Summary:                    "empty" overlap-dial-in doesn't work
Description: 
Some PRI callers (like the ancient telephone system we want to replace)
always send an empty SETUP message, and provide the actual number later.

Unfortunately, pbx_find_extension() is set to return NULL if it sees an
empty extension, thus preventing the call from ever completing.

I noticed the problem with DAHDI, but I suspect it's not limited to that.
====================================================================== 

---------------------------------------------------------------------- 
 (0094838) smurfix (reporter) - 2008-11-12 23:38
 http://bugs.digium.com/view.php?id=13891#c94838 
---------------------------------------------------------------------- 
That's exactly the change I applied to get the whole thing working (which
should surprise nobody ;-).

It remains to be seen whether the original problem is affected by this; I
assume that there must have been a reason for that change ... 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-11-12 23:38 smurfix        Note Added: 0094838                          
======================================================================