|Summary:||ASTERISK-16239: [patch] know the context of the parking call|
|Reporter:||Clod Patry (junky)||Labels:|
|Date Opened:||2010-06-13 19:31:25||Date Closed:||2011-12-14 15:12:39.000-0600|
|Environment:||Attachments:||( 0) M17503.diff|
|Description:||When using the comebacktoorigin option in features.conf, when a call times out in the park, you can do whatever with your call, since you can set it to whatever you want.|
However, there's no way to know what was the context which parked that call.
That patch just set a chan var called PARKEDCONTEXT.
****** ADDITIONAL INFORMATION ******
So if you have many parking context, when a parked call timeouts, you can know it was parked from the marketing or accounting departement.
|Comments:||By: Leif Madsen (lmadsen) 2010-06-14 10:56:04|
Thanks for the patch Claude!
By: Leif Madsen (lmadsen) 2010-06-23 15:39:09
WHAT?! NO DOCUMENTATION?!?!?! FAIL!
By: Jonathan Rose (jrose) 2011-12-14 14:21:33.658-0600
Hey, this doesn't actually write the context of the parking lot the call was in, it writes the name the parking lot was in. This is an important distinction for a couple of reasons... probably not the least of which being that multiple parking lots can share a single context while the parking lot name is uniquely identifying. Since that's the case, I'm renaming the variable to PARKEDLOT.
This change will only go into trunk. It probably isn't in any way dangerous, but technically it's a new feature, so ehhhhh. Actually, I'm a little concerned about both this and the PARKINGSLOT variable that is already being set because there is basically no documentation of that variable anywhere. I'm going to go ahead and add the fact that these variables are being added at timeout in the sample config.