Directed call pickup

yes its called directed call pickup.. it can be made into a feature code.. in MTE *8 becomes a bad idea because callgroups are limited to values of 0-63 so they don't work when the tenant ID is greater than 63.

I make a feature code _*8. that picks up whatever extension procedes *8 (*8102 to pick up 102)

Is that code available to download and try it?, could you send it to me? in what file should I do it? fetaures.conf?
Please advice,
Thank you.
Roque.

its in thirdlane, check the available scripts when creating a feature code.

Hi, we tested it and didn't work. We get this log:

[May 27 18:20:01] NOTICE[16678] app_directed_pickup.c: No target channel found for 621-netline.

Any idea what is happening?

the call arrived into a script that didnt set PICKUPMARK ?

as of right now only

macro-tl-userexten
macro-tl-stdexten
macro-tl-multidevice-exten

have directed call pickup

was extension 621 called directly?
was 621 in the ringing state when you tried to do the pickup?

I have an analog phone for my home phone and was wondering why I couldn't get this to work. Its because macro-tl-stdexten-dahdi didn't set PICKUPMARK. I setup a feature code *8. to use macro-tl-directed-call-pickup just like Erik said and it works like a charm.
Thanks
FSD

Hi

We are using MTE, and having trouble with the directed call pickup.

I have added the feature code _*8. like above.
When I try to pickup a ringing extension (ex dial *81005)

I get the following:
-- Executing [*81005@from-inside-redir-ClearVoice1:1] Macro("SIP/1001-ClearVoice1-b57720f8", "tl-directed-call-pickup|2") in new stack
-- Executing [s@macro-tl-directed-call-pickup:1] PickUp("SIP/1001-ClearVoice1-b57720f8", "1005-ClearVoice1@PICKUPMARK") in new stack
[Jul 22 14:33:06] WARNING[11864]: channel.c:4399 ast_get_group: Ignoring invalid group 1005 (maximum group is 63)
-- No channel found 0.
== Spawn extension (macro-tl-directed-call-pickup, s, 1) exited non-zero on 'SIP/1001-ClearVoice1-b57720f8' in macro 'tl-directed-call-pickup'
== Spawn extension (macro-tl-directed-call-pickup, s, 1) exited non-zero on 'SIP/1001-ClearVoice1-b57720f8'
-- SIP/1005-ClearVoice1-08a74d68 is ringing

It looks like its setting the variable when i dail it from ext 1002:
Executing [s@macro-tl-userexten:2] Set("SIP/1002-ClearVoice1-b55b8c70", "__PICKUPMARK=1005-ClearVoice1") in new stack

This also doesn't work if the call comes from an external number.

Is there something I am missing here?

Thanks for the help,
Heinrich

Hello,

I have the exact same problem with my SNOM 320 phone:

-- Executing [**1200@from-inside-iptelefonibolaget:1] Macro("SIP/1103-iptelefonibolaget-092c60d8", "tl-set-variables2|from-inside-redir-iptelefonibolaget|iptelefonibolaget") in new stack
-- Executing [s@macro-tl-set-variables2:1] Set("SIP/1103-iptelefonibolaget-092c60d8", "__tenant=iptelefonibolaget") in new stack
-- Executing [s@macro-tl-set-variables2:2] Set("SIP/1103-iptelefonibolaget-092c60d8", "CDR(userfield)=iptelefonibolaget") in new stack
-- Executing [s@macro-tl-set-variables2:3] Set("SIP/1103-iptelefonibolaget-092c60d8", "__FROM_INSIDE=1") in new stack
-- Executing [s@macro-tl-set-variables2:4] Set("SIP/1103-iptelefonibolaget-092c60d8", "__MOH=default-iptelefonibolaget") in new stack
-- Executing [s@macro-tl-set-variables2:5] GotoIf("SIP/1103-iptelefonibolaget-092c60d8", "1 ?setmoh") in new stack
-- Goto (macro-tl-set-variables2,s,7)
-- Executing [s@macro-tl-set-variables2:7] SetMusicOnHold("SIP/1103-iptelefonibolaget-092c60d8", "default-iptelefonibolaget") in new stack
-- Executing [s@macro-tl-set-variables2:8] Goto("SIP/1103-iptelefonibolaget-092c60d8", "from-inside-redir-iptelefonibolaget|**1200|1") in new stack
-- Goto (from-inside-redir-iptelefonibolaget,**1200,1)
== Channel 'SIP/1103-iptelefonibolaget-092c60d8' jumping out of macro 'tl-set-variables2'
-- Executing [**1200@from-inside-redir-iptelefonibolaget:1] Macro("SIP/1103-iptelefonibolaget-092c60d8", "tl-directed-call-pickup|") in new stack
-- Executing [s@macro-tl-directed-call-pickup:1] Pickup("SIP/1103-iptelefonibolaget-092c60d8", "**1200-iptelefonibolaget@PICKUPMARK") in new stack
[Aug 17 12:36:33] NOTICE[4602]: app_directed_pickup.c:159 pickup_exec: No target channel found for **1200-iptelefonibolaget.
-- Executing [s@macro-tl-directed-call-pickup:2] Playback("SIP/1103-iptelefonibolaget-092c60d8", "privacy-incorrect") in new stack
-- Playing 'privacy-incorrect' (language 'se')
Extension Changed 1103[local-extensions-iptelefonibolaget] new state InUse for Notify User 1103-iptelefonibolaget
Extension Changed 1103[local-extensions-iptelefonibolaget] new state InUse for Notify User 1102-iptelefonibolaget (queued)
Extension Changed 1103[local-extensions-iptelefonibolaget] new state InUse for Notify User 1601-iptelefonibolaget
-- Executing [s@macro-tl-directed-call-pickup:3] Hangup("SIP/1103-iptelefonibolaget-092c60d8", "") in new stack
== Spawn extension (macro-tl-directed-call-pickup, s, 3) exited non-zero on 'SIP/1103-iptelefonibolaget-092c60d8' in macro 'tl-directed-call-pickup'
== Spawn extension (from-inside-redir-iptelefonibolaget, **1200, 1) exited non-zero on 'SIP/1103-iptelefonibolaget-092c60d8'
-- Executing [h@from-inside-redir-iptelefonibolaget:1] Hangup("SIP/1103-iptelefonibolaget-092c60d8", "") in new stack

We are using Thirdlane MTE and Asterisk 1.4.24.1

you didnt fill out your invoking feature code length ya moron :-) your script thinks the extension you are trying to pick up is **1200

Haha Erik!!

You were right as always :D I had forgotten the lenght. Now it works really good.

wait till you see what we're going to do in 1.8, it might show up early since it can technically work in 1.6.2.x

Cool, can you tell us something about it?

theres going to be a new way of doing groups.. one that isnt limited by technology (before sip couldnt retrieve dahdi or iax2 and vice versus). Each tenant will be able to have multiple groups.

Good good good!

Looking forward to the release

the code has been released in the latest PBX manager. While its configurable by anyone, it will only actually function for 1.6.2 and 1.8 installations. I have a post in announcements about example feature codes to utilize it.

Does any one know on what version of Asterisk Business Edition will work?

none of them. the last version of ABE was C, which is asterisk 1.4. There is no longer ABE development.

#1 Why is the retail version of Asterisk Business Edition no longer available?

 
Asterisk Business Edition was created to meet a particular need at a time when open source was not well-received by typical commercial users. In recent years, many organizations in both public and private sectors have explicitly accepted open source software for production use. Also, many of the support entitlements around Asterisk Business Edition have become available around open source Asterisk by way of Digium's open source support subscriptions. This offers the flexibility of choosing the best open source release of Asterisk for your needs, with the assurance of Digium's Technical Support team ready to assist you.

Erik,

I am having trouble finding this announcement, can you direct me so i may educate myself on this new feature?

Michael

the code has been released in the latest PBX manager. While its configurable by anyone, it will only actually function for 1.6.2 and 1.8 installations. I have a post in announcements about example feature codes to utilize it.

Erik Smith
CTO
BluegrassNet Voice
dCAP

you mean this announcement?

http://www.digium.com/en/products/software/abe.php

My bad, thought tje announcement was about this:

theres going to be a new way of doing groups.. one that isnt limited by technology (before sip couldnt retrieve dahdi or iax2 and vice versus). Each tenant will be able to have multiple groups.

well its a little limited by technology but only in the way that the UI will write the dialplan..

the group makes a dialplan list that looks a bit like a huntlist, in fact we recycled a lot of that code to build it. It executes the PickupChan application the way you would run Dial() and list a bunch of phones.

PickupChan(SIP/101-tenant,SIP/102-tenant,SIP/108-tenant)

I am having a similar issue that dbenders was having where I get the error message "app_directed_pickup.c: No target channel found". I have a feature code setup as _8X. for the directed call pickup script with the invoking length being 2. In a testing environment, I had extension 9997 call 9998 and sure enough when I press the pickup softkey on my Polycom 650 at ext 9999 (that I altered to use the string *8Ext #.) it picks up the call just fine. However, when I call our clients main number and set the Polycoms soft key to *8200 it will not pickup the call. I am using for ext 200. Erik, I see you talk about PICKUPMARK above as well as from reading from this link:http://www.voip-info.org/wiki/view/Asterisk+cmd+Pickup that I may need to setup PICKUPMARK as a variable?