[asterisk-dev] Park patch to silence slot number

Wed Oct 4 02:56:57 CDT 2017

Hi Bryant,

That's good to know. Thank you, I appreciate your detailed reply on this!

On 4 October 2017 at 15:14, Bryant Zimmerman <BryantZ at zktech.com> wrote:

> You can create dynamic lots with different contexts in the fly. You are
> actually parking at a context you just use an extension to identify access
> to the slot. If you have any identifying unique account info. Each lot is
> based on a parking lot context as a template. The lot name is dyanmically
> unique per lot. When you first create it. We use unified dialplan contexts
> for parking. We just augment our lots based on the account number for each
> client (prkAcctNumLotNum.SlotNym).  It is very flexible you can pass in all
> the parameters on the fly using a combination of special channel dynamic
> variables and options in the park and parked command. We even specify
> dynamic ring back contexts with parameters in them so ring backs can be
> directed correctly. And accounts can only ever pickup their lots.  We have
> customers with multiple parking lots all on the same account and the
> parking extensions are set in a database. The only limitation is you can't
> change the parking template context or shrink it once a lot is created
> without a restart of Asterisk. You can grow the number of parking slots
> dyanmically.
>
>
>
> The way we do this when you park directly on a slot the ring back time can
> be specified on a per slot basis as well. Customers love this.
>
>
>
> Sent from my Windows 10 phone
>
>
>
> *From: *David Cunningham <dcunningham at voisonics.com>
> *Sent: *Tuesday, October 3, 2017 6:46 PM
> *To: *Asterisk Developers Mailing List <asterisk-dev at lists.digium.com>
> *Subject: *Re: [asterisk-dev] Park patch to silence slot number
>
>
> Hi Byrant,
>
> Thank you for the reply (and voicemail). Are you referring to the patch by
> Igor Goncharovsky? We had issues because it requires a different context
> for each overlapping parking slot, and our multi-tenant environment doesn't
> use a different context per tenant. What he said is below. However, we've
> just noticed that Asterisk 13 has an 's' option on the Park command to
> silence the slot number, so sorry for the trouble!
>
> "It is the how parking works in core of asterisk. When call parked,
> asterisk automatically put extensions for call park and for taking a call
> from park. I.e. when you want to park two calls at same extension and same
> context asterisk unable to do it, because unable to insert second time same
> extension in dialplan. I see no problem in using different extensions range
> for all parking lots in same context of using different contexts for all
> users"
>
>
> On 3 October 2017 at 16:23, Bryant Zimmerman <BryantZ at zktech.com> wrote:
>
>> You don't need a patch this is possible with the current tools if you
>> keep track of parks pickups and ring backs. We use the current system to do
>> dynamic parks all of the time in multi tenant environment . We create
>> dynamic lots per tenant and address them per sub account. This allows for
>> each tenent to have parking slots with any number even when others use the
>> same.  I paid part of the bounty to get the original dynamic parking system
>> working.
>>
>>
>>
>> Sent from my Windows 10 phone
>>
>>
>>
>> *From: *David Cunningham <dcunningham at voisonics.com>
>> *Sent: *Monday, October 2, 2017 11:09 PM
>> *To: *asterisk-dev at lists.digium.com
>> *Subject: *[asterisk-dev] Park patch to silence slot number
>>
>>
>> Hello,
>>
>> We'd like to get a patch written for Asterisk's Park command, so that
>> with a given option it won't play the parking slot number. The idea is that
>> we can allow multiple calls to be parked on the same apparent slot number
>> by playing the apparent slot number ourselves, and parking calls on a
>> different actual slot number. For example we'd play 701 but actually park
>> the call on 123701.
>>
>> Does anyone know of someone who'd be willing to write this patch, and
>> submit it for inclusion in Asterisk? We will of course pay a bounty. If I'm
>> asking in the wrong place then apologies and please let me know the right
>> one.
>>
>> Thanks in advance,
>>
>> --
>> David Cunningham, Voisonics Limited
>> http://voisonics.com/
>> USA: +1 213 221 1092 <+1%20213-221-1092>
>> Australia: +61 (0) 2 8063 9019 <+61%202%208063%209019>
>>
>> --
>> _____________________________________________________________________
>> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>>
>> asterisk-dev mailing list
>> To UNSUBSCRIBE or update options visit:
>>    http://lists.digium.com/mailman/listinfo/asterisk-dev
>>
>
>
>
> --
> David Cunningham, Voisonics Limited
> http://voisonics.com/
> USA: +1 213 221 1092 <+1%20213-221-1092>
> Australia: +61 (0) 2 8063 9019 <+61%202%208063%209019>
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-dev
>

-- 
David Cunningham, Voisonics Limited
http://voisonics.com/
USA: +1 213 221 1092
Australia: +61 (0) 2 8063 9019
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20171004/c8351271/attachment-0001.html>