asterisk users - Oct 2013 - multiple parking lot best practice

We are planning to have about 100+ parking lots defined in features.conf , each
with about 4 unique park positions. Asterisk will be handling all the parking
and unparking (we don't exclusively use Park/ParkedCall in the dialplan):

[parkinglot_a]
parkpos => 1-4
context=parked

[parkinglot_b]
parkpos => 5-8
context=parked

As far as I can tell, Asterisk adds/removes extensions to the parking context(s)
dynamically as the calls are parked/unparked.

I'm curious which one is preferred (as far as performance and/or stability)
-  to use one context for all parking lots or to use a separate context for each
one?

Thanks,
Matt
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20131023/7ec3e46c/attachment.html>

My question is not directly related to Asterisk, but I'm hoping users here
might have some insight.

We have SPA504G phones with only Ext1 enabled. We use the other line keys to
pick up parked calls in Asterisk via:

fnc=sd+blf;sub=1234 at proxy

This works smoothly except for one scenario:

When the user presses (by mistake) one of those "unpark" line keys
while in an active call with a customer, this active call and the parked call
from another customer are bridged (and obviously the call is gone from our
phone).

Is there a way to force the Cisco phone to put the active call on Hold before
getting the parked call?

or

Is it possible to somewhat temporarily deactivate/disable the unpark line keys
while there is an active call?

Thanks,
Mert
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20131024/13bf760a/attachment.html>