--- On Fri, 3/6/09, Vieri <rentorbuy at yahoo.com> wrote:
> I'm having trouble with call pickups.
>
> Suppose ring group is 100 and has extensions 101 and 102.
>
> Someone calls 100, 101 rings and 102 wants to pick the call
> up. If 102 dials **100, call pickup works. If 102 dials
> **101, call pickup fails.
>
> In my dialplan I have:
>
> exten => **101,1,NoOp(pickup extension)
> exten => **101,n,Pickup(101)
> exten => **101,n,NoOp(pickup group)
> exten => **101,n,Pickup(100)
> exten => **101,n,Hangup
>
> When 102 dials **101 I see this on the CLI:
>
> -- SIP/4060-08868de8 is ringing
> Extension Changed 4060 new state Ringing for Notify User
> 4061
> -- Executing NoOp("SIP/4053-0886ba08",
> "pickup extension") in new stack
> -- Executing Pickup("SIP/4053-0886ba08",
> "4060") in new stack
> == Spawn extension (from-internal, **4060, 2) exited
> non-zero on 'SIP/4053-0886ba08'
>
> It does NOT continue and display "pickup group"
> so it just hangs up the call.
> It *should* go on and reach the "Pickup(100)"
> instruction...
>
> Why is it failing?
>
> I've noticed this only after I recently upgraded from
> Asterisk 1.2.30 to 1.2.31.1.
>
> Asterisk 1.4.21.2 does not have this "bug".
>
> Can someone please let me know if the 1.2 branch can be
> fixed (should I file a bug report or will it be ignored
> since 1.2 only has security fixes)?
>
> Thanks
Sorry for the CLI mix-up:
in my original example, 4053 is extension 102 and 4060 is 101.