Directed Pickup then Parking

try it on asteerisk 1.8.4 during your down time and let me know if the bug persists. 1.8.4 adds a new feature that updates endpoints after a transfer is conducted. Its definitely an asterisk bug, but if its working in 1.8.4 digium isnt going to give a shit about fixing it in 1.6.2

Is 1.8.4 support by the latest STE? When attempting to install the webmin module i get:

pragma: no-cache Expires: Thu, 1 Jan 1970 00:00:00 GMT Cache-Control: no-store, no-cache, must-revalidate Cache-Control: post-check=0, pre-check=0 Content-type: text/html; Charset=iso-8859-1

It hangs at that screen and nothing seems to happen on the back end.

Michael

your bug lies somewhere else.. i just built two pbx's using 1.8.4-rc3 and had no problem with the webmin modules. the only 1.8.4 <--> thirdlane bug I've found is the gui does not correctly realize mysql logging is enabled because the name of the module changed.

ok, ill start looking around and see what i find.

I setup a lab box running 1.8.4 and tested. It worked almost perfect. The system announced the park zone to me on my cell phone. From my cell I heard it announce 7-0-1 and then went to MOH.

I ended up finding a difference between my lab and the customers site other than the Asterisk version, the phone firmware at the customers site was a revision prior to mine. I asked her to upgrade and now hers works as well.

So it sounds to me like it was a phone firmware issue.

I also had the customer test and she hears the park announcement on the IP handset and not the cell phone.

So all in all the customer is happy but im wondering if this is a bug in 1.8.4 or something in my config?

Scratch that, on the 1.6.2.11 system it did not announce the park zone at all. Neither the IP handset or the cell phone heard the announcement.

In our testing we've found a ton of problems with multi-tenant parking in asterisk 1.8.4 and SVN:

* ParkAndAnnounce - can't retrieve parked call https://issues.asterisk.org/view.php?id=19307

* Park - parks call to wrong parking lot when using multiple parking lots
https://issues.asterisk.org/view.php?id=18553

* Blind Transfer to parking lot says parking position on caller channel instead of parking channel
https://issues.asterisk.org/view.php?id=18345

* Blind Transfer to parking lot says parking position on caller channel instead of parking channel
https://issues.asterisk.org/view.php?id=18345

according to the bug tracker, this is not a bug, but a stupid user issue. You're not supposed to be blind transfering calls to the parking extension. It also says non-issue when using parkexten of features.conf which is how TL expects you to park calls (ie dialing 700 as the entension). This should also address item #1 on your list as we arent using parkandannounce in the TL dialplan.

I do not know anyway to do one button call parking without using either blind transfer or parkandannounce, both of which are not interoperating with asterisk 1.8.4 correctly. Our customers will not use call parking that takes more than one button to exercise.

Digium is asserting that blind transfer to the parking lot is not supported, however it works in 1.6.2.9 and it enables one button call parking so they can call it whatever they like... when it breaks customers aren't happy.. so its a bug to me.

eeman do you support one button call parking?

on which phone?

one button parking on a polycom

efk.efklist.2.mname="callpark"
efk.efklist.2.status="1"
efk.efklist.2.label="Call Park"
efk.efklist.2.action.string="$FTransfer$$FDialpad7$$FDialpad0$$FDialpad0$$Cpause4$Changup$"
softkey.2.label="Park"
softkey.2.action="!callpark"
softkey.2.enable="1"
softkey.2.precede="1"
softkey.2.use.active="1"
softkey.2.use.alerting="0"
softkey.2.use.dialtone="0"
softkey.2.use.hold="1"
softkey.2.use.idle="0"
softkey.2.use.proceeding="0"
softkey.2.use.setup="0"

yes! that is exactly what we are doing for polycoms so we are on the same page.

however for cisco phones we are currently using blind transfer which is working fine on 1.6.2.9.
(303G, 504G, etc..)


Disabled
Park
shared
fnc=sd;ext=700@$PROXY


Forgive my naïvety, but what would a blind transfer to parking actually do? "blind transfer" means that the person doing the transferring does not remain on the call for the transfer to complete, correct? Seems to me like ParkAndAnnounce would be kinda useless on a blind transfer as the transferrer would not be on the line to hear the announcement about which parking slot the call was placed in. Seems like a normal Park would be required for that situation where the phone picks the slot to park it in itself before transferring it to parking.

ParkAndAnnounce calls the parking extension (transferrer) back to announce the spot.
And as an optimization you can configure ParkAndAnnounce so that when it calls the parking extension(transferrer) auto-answer is enabled, so the transferrer need not even answer the call.

parking in 1.8 branch now has a working workaround ..

https://www.thirdlane.com/forum/1-8-multi-tenant-parking-solved