[asterisk-dev] Call Pickup Issues v1.6.2.11

[Alec Davis]

After the bug fix in  <https://issues.asterisk.org/view.php?id=17633>
https://issues.asterisk.org/view.php?id=17633 the default 'pickup' behaviour
in the 1.6.2 branch (and better) is restored.
To enable 'magic pickup' set notifycid=yes in sip.conf.
 
But beware, with Grandstream GXP20x0 phones (firmware 1.2.3.5), currently
after you've done a 'magic pickup' of a call, you cannot put it on hold or
transfer, see https://issues.asterisk.org/view.php?id=17823
 
Alec.
 
  _____  

From: asterisk-dev-bounces at lists.digium.com
[mailto:asterisk-dev-bounces at lists.digium.com] On Behalf Of Bryant Zimmerman
Sent: Thursday, 26 August 2010 11:51 a.m.
To: Asterisk Developers Mailing List
Subject: Re: [asterisk-dev] Call Pickup Issues v1.6.2.11


Mark

The bug issue  <https://issues.asterisk.org/view.php?id=17633>
https://issues.asterisk.org/view.php?id=17633 is the exact issue I am
having. I will try the new rc build to fix this issue.  How would I code to
use the magic pickup? My extension numbers and hints are in different
contexts and my extension numbers also do not match my peer names I use a 10
digit plus the four digit extension for multi tenant usage. Exp..
6168310000.6000  I can't find any concrete examples of the magic pickup I
would like to document this on the wiki so no one else goes through this
confusion.

Thanks
Bryant



On Wed, 2010-08-25 at 18:15 -0500, Mark Michelson wrote:
> On Wed, 2010-08-25 at 18:54 -0400, Bryant Zimmerman wrote:
> > Hi all now that I am on 1.6.2.11 I am running into call pickup
> > issues. 
> > 
> > 
> > 
> > What changed between asterisk 1.6.1.20 and 1.6.2.11 with call pickup.
> > I can not find anything in the change log that would indicate why our
> > call pickup ability broke. 
> > 
> > 
> > 
> > Grandstream phones send a prefix to the extension on call pickup so
> > say a user tries to pickup extension 6168551030.6001 the grand stream
> > phone would send **6001 our dial context for extensions would send a
> > pickup for SIP/6168551030.6001 
> > 
> > 
> > 
> > Exp:
> > 
> > 
> > 
> > [macro-SBussniessMSIP-Operator]
> > exten => s,1,Set(_PICKUPMARK=ext6168551030.OPERATOR)
> > 
> > [macro-Core_ExtFlow]
> > exten => s,1,NoOp(${ARG3})
> > .......
> > 
> > exten => _NXXX,1,Set(_PICKUPMARK=DOcp
> > ${sitePickupGroupEXT}${siteExtPrefix}${l_Ext})
> > exten => _NXXX,n,NoOp(${CALLERID(num)})
> > 
> > exten => _**NXXX,1,Set(l_Exten=${EXTEN:2})
> > 
> > exten => _**NXXX,n,Goto(DoPickup,1)
> > 
> > 
> > 
> > exten => DoPickup,1,Pickup(ext6168551030.${l_Exten}@PICKUPMARK) 
> > 
> > exten => DoPickup,n,Pickup(ext6168551030.OPERATOR at PICKUPMARK) 
> > 
> > 
> > 
> > This worked grate. But when we went to asterisk version 1.6.2.11
> > they system no longer goes to the **6001 extension in our dial
> > context. The cli shows the following
> > 
> > 
> > 
> > [Aug 25 13:04:38] NOTICE[9272]: chan_sip.c:19964
> > handle_request_invite: Trying to pick up 6001 at 6168551030-sbm-blf
> > 
> > [Aug 25 13:04:38] NOTICE[9272]: chan_sip.c:19964
> > handle_request_invite: Trying to pick up 6001 at 6168551030-sbm-blf
> > 
> > == Extension Changed 6003[6168551030-sbm-blf] new state InUse for
> > Notify User 6168551030.6001
> > 
> > 
> > 
> > After doing some packet captures it apears that some how asterisk
> > version 1.6.2.11 is flagging the phone and grandstream is sending the
> > call without the **Exten but the Invite header has somthing about
> > pickup in the Contact and asterisk is trying to look in my
> > subscribecontext=6168551030-sbm-blf
> > 
> > Message Header
> > Contact: <sip:6168551030.2032 at 192.168.40.126:44668;transport=udp> 
> > 
> > Replaces: pickup-ec475d2a488a2601 at 192.168.40.126
> > Supported: replaces, timer, path
> > 
> > When I dial the **6001 to do the pickup and do not push the flashing
> > blf they the pickup works like it use to.
> > 
> > 
> > 
> > Any ideas or direction? Who has changed the pickup code so they could
> > tell me what has changed and how to override it back to the old
> > behavior.
> > 
> > 
> > 
> > The Grandstream guys are going crazy with this one their engineer is
> > trying to help me figure out what is causing their phone to change
> > it's behavior and not send the **
> > 
> > 
> > Thanks
> > 
> > Bryant
> 
> See these issue reports:
> https://issues.asterisk.org/view.php?id=17633
> https://issues.asterisk.org/view.php?id=14567
> https://issues.asterisk.org/view.php?id=17671
> 
> They were fixed on August 13, so likely after the release of 1.6.2.11.
> If you try using the current tip of the 1.6.2 branch, do you still have
> the issue?
> 
> Mark Michelson
> 
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-dev/attachments/20100827/c4fa223c/attachment.htm