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