[asterisk-bugs] [Asterisk 0019234]: SIP stack stops working if a Dial command if forwarded by a SIP physical phone

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=19234 
====================================================================== 
Reported By:                tiziano
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   19234
Category:                   Applications/app_dial
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.8.3.3 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2011-05-05 07:49 CDT
Last Modified:              2011-05-24 07:32 CDT
====================================================================== 
Summary:                    SIP stack stops working if a Dial command if
forwarded by a SIP physical phone
Description: 
If you enable the call forward feature on a registered SIP phone  - I've
tried with two different SNOM models a a Cisco/Linksys SPA9xx - when a call
reach the phone you'll see (on asterisk CLI):

 Got SIP response 302 "Moved Temporarily" back from (PHONE IP:PORT)
 Now forwarding SIP/(CHANNEL) to 'Local/....@(CONTEXT)' (thanks to
SIP/(FORWARDING PHONE CHANNEL)
 Not accepting call completion offers from call-forward recipient
Local/... at ....

then all SIP activity ceased, both incoming and outgoing calls, while
asterisk remains up and running
====================================================================== 

---------------------------------------------------------------------- 
 (0135330) tiziano (reporter) - 2011-05-24 07:32
 https://issues.asterisk.org/view.php?id=19234#c135330 
---------------------------------------------------------------------- 
Leif, while setting up a system for generating backtrace and so, I've
stumbled upon a very strange (for me) thing:
normally, when I compile some C code without optimization, the result
executable(s) is bigger then the one with optimization enabled. So, imagine
my surprise when, compiling asterisk 1.8.4 with DONT_OPTIMIZE flag selected
i got an executable of 20367186 bytes while the regular compilation gives
an executable of 23110097 bytes (this is thue for about all modules, not
only for asterisk executable). I understand that this is not the same
issue, but I think that the question is important because, if my
development environment is "not sane", we have nothing to talk about. So,
please, could you or someone confirm that this behavior (DONT_OPTIMZE
executable is thinner than regular one) is expected?
Thanks 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-05-24 07:32 tiziano        Note Added: 0135330                          
======================================================================