[asterisk-bugs] [Asterisk 0017449]: App Dial "crashes" when received a 484 (Address Incomplete) from a SIP Trunk

[Asterisk Bug Tracker]

The following issue has been CLOSED 
====================================================================== 
https://issues.asterisk.org/view.php?id=17449 
====================================================================== 
Reported By:                juliomoretti
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17449
Category:                   Core/PBX
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     closed
Asterisk Version:           1.6.2.7 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 open
Fixed in Version:           
====================================================================== 
Date Submitted:             2010-06-02 16:17 CDT
Last Modified:              2010-06-02 16:40 CDT
====================================================================== 
Summary:                    App Dial "crashes" when received a 484 (Address
Incomplete) from a SIP Trunk
Description: 
I'm trying to make a call over a SIP Trunk (oferred by one Voip Company).
All works fine, but when I put a invalid (not expected number), the SIP
Trunk come back with a 484 "Address Incomplete" from the SIP Trunk.
And at this time, the DIALPLAN comes out of any extension and priority,
junst reporting:

   -- Got SIP response 484 "Address Incomplete" back from X.X.X.X
  == Everyone is busy/congested at this time (1:0/0/1)
  == Spawn extension (macro-dial-external, s, 5) exited non-zero on
'SIP/10000-00000000' in macro 'dial-external'
  == Spawn extension (Rota_Inicial, 02125405285, 3) exited INCOMPLETE on
'SIP/10000-00000000'
[2010-06-02 14:59:28.784] WARNING[4068]: pbx.c:4358 __ast_pbx_run: Channel
'SIP/10000-00000000' sent into invalid extension '02125405285' in context
'Rota_Inicial', but no invalid handler

I tried the same in a very simple DIALPLAN, something like (JUST AN
EXAMPLE):
exten => _X., 1, Noop(Hello)
exten => _X., 2, Answer
exten => _X., 3, Dial(SIP/mysiptrunk/${EXTEN},300)
exten => _X., 4, Noop(${DIALSTATUS})

The result is allways the same: when calling a valid (expected) number,
works fine including the "4" priority (in this example). When calling a non
expected number for the sip trunk, never comes to the 4 priority, ending
before, receiving the messages above.

Below comes all the real configuration of the situation exaplaned. But is
just for illustration, because it occurs too in a simple way, like the
example above.
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-06-02 16:40 pabelanger     Status                   new => closed       
======================================================================