Directed Call Pickup possible with Kazoo

[Arne van Balgoijen]

Dear reader,

The Group pick callflow is working like a charm!

But now people ask me if a Directed Call Pickup is also possible?

Is anything in the works for that, or did I not search hard enough and is it already possible?

Br

Arne

[Luis Azedo]

Hi,

its already implemented. take a look at the comments in https://github.com/2600hz/kazoo/blob/master/applications/callflow/src/module/cf_group_pickup_feature.erl

you can make it work with direct call pickup.

there are also other callflow actions that may be used for this like cf_intercept ?

--
You received this message because you are subscribed to the Google Groups "2600hz-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to 2600hz-dev+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Arne van Balgoijen]

Luis,

After I entered the question I also found: https://2600hz.atlassian.net/wiki/display/docs/Group+Pickup which states it is alreay possible to choose users and devices next to groups.

And I saw in 3.18 that next to groups it is now possible in KazooUI to choose devices and users.

What is missing is a way to create a user adressable way, like dial *7xxxx were xxxx is the extension of the user you want to pickup. 

But I guess a custom call flow module based on f_group_pickup_feature.erl

could do that. 

BR

Arne

[James Aimonetti]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The cf_group_pickup_feature will inspect the callflow extension
captured in the regex to see if the first element is a user, device,
or ring_group and route to cf_group_pickup using the
device/user/ring_group.

So in your example, you'd create a callflow with pattern "*7(\\d{4})"
to capture four digits after *7 and pickup a ringing device from that
device/user/ring_group list (assuming the four digits point to a
callflow with device/user/ring_group as the first module in the "flow").

Le 2014-10-13 14:09, Arne van Balgoijen a écrit :
> Luis,
>
> After I entered the question I also found:
> https://2600hz.atlassian.net/wiki/display/docs/Group+Pickup which
> states it is alreay possible to choose users and devices next to
> groups. And I saw in 3.18 that next to groups it is now possible in
> KazooUI to choose devices and users.
>
> What is missing is a way to create a user adressable way, like dial
> *7xxxx were xxxx is the extension of the user you want to pickup.
> But I guess a custom call flow module based on
> f_group_pickup_feature.erl

> <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2F2600hz%2Fkazoo%2Fblob%2Fmaster%2Fapplications%2Fcallflow%2Fsrc%2Fmodule%2Fcf_group_pickup_feature.erl&sa=D&sntz=1&usg=AFQjCNFOA589DBcqAZbfHNxd15wJAh2z2Q>

>
>
could do that.
>
> BR
>
> Arne
>
> On Monday, October 13, 2014 7:14:22 PM UTC+2, Luis Azedo wrote:
>>
>> Hi,
>>
>> its already implemented. take a look at the comments in
>> https://github.com/2600hz/kazoo/blob/master/applications/callflow/src/module/cf_group_pickup_feature.erl
>>
>>
>>
you can make it work with direct call pickup.
>> there are also other callflow actions that may be used for this
>> like cf_intercept ?
>>
>> On Mon, Oct 13, 2014 at 10:03 AM, Arne van Balgoijen
>> <ar...@firmtel.com <javascript:>> wrote:
>>
>>> Dear reader,
>>>
>>> The Group pick callflow is working like a charm! But now people
>>> ask me if a Directed Call Pickup is also possible?
>>>
>>> Is anything in the works for that, or did I not search hard
>>> enough and is it already possible?
>>>
>>> Br
>>>
>>> Arne
>>>
>>> -- You received this message because you are subscribed to the
>>> Google Groups "2600hz-dev" group. To unsubscribe from this
>>> group and stop receiving emails from it, send an email to

>>> 2600hz-dev+...@googlegroups.com <javascript:>. For more
>>> options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>


- --
James Aimonetti
Lead Systems Architect / Impressionable Scallywag
"I thought I fixed that"

2600Hz | http://2600hz.com
sip:ja...@2600hz.com
tel:415.886.7905
irc:mc_ @ freenode
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJUPEyyAAoJENTKa+JPXCVgwZQIAI6gbjtA2XsO6hvJ6mZWyri1
IryPBaVMHR4LSYh2Sc9IceJn6EAZ97xAkT8QFbRjj2YRcnMtakDB7AMbKivrOJ2G
LC0EK1V79y4sX5UEhfEq+2YuSuzog1Vg/xjR5QLZMc37lWwtjHaWHyAA2Vfgow6K
LD+JcJfFrGRo27jzisBjYYXUJgSnhlN0iP5XT5bFVRN2FZuNZ4TYJjQ+Bv4WOKg4
OfbUAbYwDSvN30JGT/Sl8nDHFSe6ZCtHPjJmDynFBt53ouM6cRcvvMVMXhndDlD6
e7CDz7DIoXHL9V8eTRCY6rvNyhfrGsuwmZeaPUFUh8fMYxRGqnt1rssC4xRP/FU=
=MxHI
-----END PGP SIGNATURE-----

[Ludovic Gasc]

FYI, we handle this use case with Pivot, small Python+AsyncIO daemons, and HAproxy, to have the same redundancy as Kazoo.
But simpler to handle and customize for devs, compare to patch Erlang source code ;-)