<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=us-ascii" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.18943"></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=331053919-26082010><FONT color=#0000ff
size=2 face=Arial>After the bug fix in <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><FONT
color=#000000> </FONT><FONT color=#0000ff>the default 'pickup' behaviour in
the 1.6.2 branch (and better) is restored.</FONT></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=331053919-26082010><FONT color=#0000ff
size=2 face=Arial><FONT color=#0000ff>To enable 'magic pickup' set
notifycid=yes in sip.conf.</FONT></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=331053919-26082010><FONT color=#0000ff
size=2 face=Arial><FONT color=#0000ff></FONT></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=331053919-26082010><FONT color=#0000ff
size=2 face=Arial><FONT color=#0000ff>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 <A
href="https://issues.asterisk.org/view.php?id=17823">https://issues.asterisk.org/view.php?id=17823</A></FONT></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=331053919-26082010><FONT color=#0000ff
size=2 face=Arial><FONT color=#0000ff></FONT></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=331053919-26082010><FONT color=#0000ff
size=2 face=Arial><FONT color=#0000ff>Alec.</FONT></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=331053919-26082010><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left>
<HR tabIndex=-1>
</DIV>
<DIV dir=ltr align=left><FONT size=2 face=Tahoma><B>From:</B>
asterisk-dev-bounces@lists.digium.com
[mailto:asterisk-dev-bounces@lists.digium.com] <B>On Behalf Of </B>Bryant
Zimmerman<BR><B>Sent:</B> Thursday, 26 August 2010 11:51 a.m.<BR><B>To:</B>
Asterisk Developers Mailing List<BR><B>Subject:</B> Re: [asterisk-dev] Call
Pickup Issues v1.6.2.11<BR></FONT><BR></DIV>
<DIV></DIV><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> </BODY></HTML>