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

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
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:                     assigned
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-02-27 19:12 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)
====================================================================== 

---------------------------------------------------------------------- 
 (0100942) alecdavis (reporter) - 2009-02-27 19:12
 http://bugs.digium.com/view.php?id=14567#c100942 
---------------------------------------------------------------------- 
After reverting back to 1.6.0-rc6 the directed pickup works as before.
Dialplan code hasn't changed, same phones, same FW in phones.

The dialplan does attempt 3 pickups from 3 contexts, succeeds on the 2nd.
I notice the Grandstream phone now sends **8510 to do the pickup.
Where as with trunk it directly communicates with Asterisk to try to
pickup the 8510 'Hint' in the context 'BLF_Group_1'. There's a clue there!

    -- Executing [**8510 at trusted:1] NoOp("SIP/GXP0009-b779be80", "Directed
call pickup") in new stack
    -- Executing [**8510 at trusted:2] Pickup("SIP/GXP0009-b779be80",
"8510 at incoming") in new stack
[Feb 28 13:58:30] NOTICE[18209]: app_directed_pickup.c:152 pickup_exec: No
target channel found for 8510.
    -- Executing [**8510 at trusted:3] Pickup("SIP/GXP0009-b779be80",
"8510 at trusted") in new stack
    -- SIP/GXP0009-b779be80 answered SIP/8530-b7766420
  == Extension Changed 8510[BLF_Group_1] new state Idle for Notify User
GXP0002
    -- Executing [**8510 at trusted:4] Pickup("SIP/GXP0005-b778ed10<ZOMBIE>",
"8510 at default") in new stack
[Feb 28 13:58:30] NOTICE[18209]: app_directed_pickup.c:152 pickup_exec: No
target channel found for 8510.
    -- Native bridging SIP/8530-b7766420 and SIP/GXP0009-b779be80 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-02-27 19:12 alecdavis      Note Added: 0100942                          
======================================================================