FreePBX / Yealink t42s / call park configuration best practice ...



  • What's the best practice / recommended way to configure call park keys on a yealink t42s on freePBX?

    I initially created a dsskey with a type of "call park" and value of the parking lot extension as a way to park a call and then had a few BLF keys to pickup parked calls. I had a lot of weird behavior under this configuration though. It seemed like a single extension could only park if the lot was empty. It never seemed to be able to park a second call into the next available slot. The display on the yealink would read "a call is already parked in that slot" if I tried to park a second call.

    Eventually I stumbled on changing the dsskey from type of "call park" to transfer with a value of the parking lot extension. This worked as I wanted even with multiple pakred calls with the exception that the parking lot slot was not announced to the person putting the call on hold.

    I was able to have the parking lot slot announced by going to the t42s configuration page Features->Transfer and changing "Transfer Mode via Dsskey" from blind to attended.

    While this is the behavior I want out of the system, unfortunately the FreePBX endpoint manager overwrites the "transfer mode via dsskey" value and sets it back to blind when a configuration is updated.

    What is the recommended way to configure call park functionality? Is using the dsskey transfer type functionality the best way to implement or was I doing something wrong with using the "call park" type dsskey?



  • @BraswellJay said in FreePBX / Yealink t42s / call park configuration best practice ...:

    unfortunately the FreePBX endpoint manager overwrites the "transfer mode via dsskey" value and sets it back to blind when a configuration is updated.

    Maybe something is set there in the EPM?



  • The best use of parking is simply blind transfer via DSS key directly to a specific slot.

    No one wants to waste time and a button with a park key that you then need to wait for an announcement to know where the call went.

    So here, a user simply presses the button labeled Park 1, Park 2, or Park 3 to park a call or retrieve a parked call. Light is red when parked and green when not.

    Parking lot setup

    fcc641cb-2d6f-4a96-9694-0ac958ac9e1b-image.png

    Endpoint Manager setup

    b817c853-2887-48b0-8bee-cec26762bceb-image.png



  • @scottalanmiller said in FreePBX / Yealink t42s / call park configuration best practice ...:

    @BraswellJay said in FreePBX / Yealink t42s / call park configuration best practice ...:

    unfortunately the FreePBX endpoint manager overwrites the "transfer mode via dsskey" value and sets it back to blind when a configuration is updated.

    Maybe something is set there in the EPM?

    Correct. EPM uses similar defaults to what the phones have natively.

    47f422a1-0dc0-42c0-bd40-6e1734f7986f-image.png



  • But to answer the question of how to update it. You go into basefile edit

    56b86ad7-fc56-4174-8d19-a1f25cff61c4-image.png

    You then click on the setting. As you can see it is 2 by default, same as the phone.

    bd5d9f5f-2ca2-4be2-9a52-a930612686d6-image.png

    Change it to 1

    b935eb21-91e5-4113-92e3-d1b985f62d5e-image.png

    It will then show up in red at the bottom of the list. Save here, then go out to the extensions list and rebuild them all.

    5658db0d-0421-41c9-957c-74cca9179c07-image.png



  • These are some common basefile edits that I seem to do often.

    ab39d7ec-4add-494e-a382-470f2ac5d9b7-image.png



  • @JaredBusch said in FreePBX / Yealink t42s / call park configuration best practice ...:

    The best use of parking is simply blind transfer via DSS key directly to a specific slot.

    No one wants to waste time and a button with a park key that you then need to wait for an announcement to know where the call went.

    That makes much more sense. I think I put the blinders on and focused too much on replicating the old system without thinking if there was a better way.