[asterisk-bugs] [Asterisk 0014005]: Pickup() can't pickup calls to some SIP devices

[Asterisk Bug Tracker]

The following issue has been set as RELATED TO issue 0018825. 
====================================================================== 
https://issues.asterisk.org/view.php?id=14005 
====================================================================== 
Reported By:                ddl
Assigned To:                jcolp
====================================================================== 
Project:                    Asterisk
Issue ID:                   14005
Category:                   Applications/app_directed_pickup
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     closed
Asterisk Version:           Older 1.4 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2008-12-01 18:28 CST
Last Modified:              2011-05-27 09:13 CDT
====================================================================== 
Summary:                    Pickup() can't pickup calls to some SIP devices
Description: 
I've observed that when a SIP device responds to an INVITE with a 183
without
ever sending a 180 the outgoing channel remains in the Down state rather
than
moving to Ring[ing].  This prevents Pickup() from picking up the call.  I
did
some extensive Google searching to try to understand the Pickup() failures
and
generally found a lot of reports where Pickup() seemed to work in some
cases
but not in others.  I wonder if this could be the root cause of some of
the
confusion.

By adding AST_STATE_DOWN to the test in app_directed_pickup.c I was able
to
get Pickup() to work with SIP devices (in this case the FXS port on a
Cisco
router) that behave as above; however, I have no idea what collateral
damage
this might cause.  It feels like there should be some other state for
call
progressing.

I am using 1.4.11 as provided in the FreeBSD 6.3 port.  I apologize if
this
has already been addressed in a newer version.  I checked 1.4.22 and the
code appeared the same.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0018825 [patch] Add a group to the channel on a...
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-05-27 09:13 lmadsen        Relationship added       related to 0018825  
======================================================================