[asterisk-bugs] [Asterisk 0014567]: [patch] app_directed_pickup: No target channel found for extension, Worked on 1.6.0-rc6

[Asterisk Bug Tracker]

The following issue requires your FEEDBACK. 
====================================================================== 
http://bugs.digium.com/view.php?id=14567 
====================================================================== 
Reported By:                alecdavis
Assigned To:                file
====================================================================== 
Project:                    Asterisk
Issue ID:                   14567
Category:                   Applications/app_directed_pickup
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!): 178446 
Request Review:              
====================================================================== 
Date Submitted:             2009-02-27 04:35 CST
Last Modified:              2009-03-02 08:19 CST
====================================================================== 
Summary:                    [patch] app_directed_pickup: No target channel found
for extension, Worked on 1.6.0-rc6
Description: 
Before upgrade from 1.6.0-rc6 to trunk. Directed pickup worked well.

Now we are getting:
[Feb 27 22:06:51] NOTICE[27187]: app_directed_pickup.c:255 pickup_exec: No
target channel found for 8510.

After replacing pickup_by_exten with function from tag 1.6.0.6-rc6 I was
able to find that the dialcontext and context were never going to match.

some debug below: with 1.6.0-rc6 version of pickup_by_exten 

[Feb 27 22:39:20] NOTICE[1465]: app_directed_pickup.c:273 pickup_exec:
context=BLF_Group_1.
[Feb 27 22:39:20] NOTICE[1465]: app_directed_pickup.c:217 pickup_by_exten:
macroexten= exten=8510 dialcontext= context=BLF_Group_1 canpickup=1
[Feb 27 22:39:20] NOTICE[1465]: app_directed_pickup.c:217 pickup_by_exten:
macroexten= exten=8510 dialcontext=trusted context=BLF_Group_1 canpickup=1
[Feb 27 22:39:20] NOTICE[1465]: app_directed_pickup.c:217 pickup_by_exten:
macroexten=8510 exten=s dialcontext= context=BLF_Group_1 canpickup=0
[Feb 27 22:39:20] NOTICE[1465]: app_directed_pickup.c:282 pickup_exec: No
target channel found for 8510.
  == Extension Changed 8520[BLF_Group_1] new state Idle for Notify User
GXP0009 (queued)
====================================================================== 

---------------------------------------------------------------------- 
 (0100984) file (administrator) - 2009-03-02 08:19
 http://bugs.digium.com/view.php?id=14567#c100984 
---------------------------------------------------------------------- 
This all really makes no sense... subscribecontext is only used when a
subscription comes in. I've looked at the code and confirmed it. The only
reason I can think of is if the Grandstream sends the call using the same
dialog as the subscription, thus the context is set to subscribecontext.
Can you please upload *complete* console output of the incoming call and
then attempt to pick it up. A sip debug is also needed to see what the
Grandstream is doing. Thanks. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-03-02 08:19 file           Note Added: 0100984                          
2009-03-02 08:19 file           Status                   assigned => feedback
======================================================================