0

Call Parking Feature *6 not working

Fred Berumen

February 17, 2018 01:34

None

Follow

I am going to sound a bit dramatic, but we have rolled out many Yeastar S20 IPPBX. Leaving everything default out of the box, with latest firmware upgrade, The Call Park feature (*6) has never worked for us. We tried many different yealink T48G, T46S, Grandstream phones, Polycom and many other.

We configure the DSS key on the yealink phone as the following:

Call type: Call Park

Value: *6

Label: Call Park

Line 1

When testing all we get is called failed call bounces right back to us.

We have then figure out to simply do the following:

Type: BLF

value: 6900

Label Line 6900

Line 1

Extension: 6900

and similar DSS keys for 6901, 6902, 6903, 6904, etc.

when using this we simply click on a DSS key we would like to park the call on- one click.

Is it me or this the new way of call parking? We have tested by switching the call Parking code to 70, 700 (Grandstream's default) and doesn't work either. I am out of clues on this one Yeastar. But until we figure this out, i believe we are not rolling out these units. 

Our clients with Yeastar MyPBX U100 have no issue call parking out of the box.

Any help is appreciate it.

Regards,

Fred From Texas..

 

• Facebook
• Twitter
• LinkedIn

1 comment

• 0
  
  Larry Neblett February 17, 2018 15:32

  There are generally two ways to park calls, but it depends largely on the endpoint as well as how one wants the function to work given their environment. You failed to mention if your manually configured the phone with this function or if using auto-provisioning.  

  You are setting the call park function in the Yealink as "call park" and then *6 as the code. However, consider, what one might do if using an analog phone on an ATA, how would they accomplish this? They have no such setting. Change the Yealink setting to use DTMF with *6. Or, to test, call the T4X phone and while in the call simply press *6. The system upon seeing the code will park the call and then inform of the park slot. This is "call park". The user must remember the announced spot in order to retrieve same. 

  The other method you mentioned, when using the BLF, is commonly referred to as "directed call park". This is also a valid method, but instead of letting the system manage the slots, you are "directing" the system to park a call in a given spot whereupon the condition of the slot is visible to all others who are using the same BLF function and slots and subscribe. This is a SIP function. The downside is that it uses BLF keys and one may not have enough on all phones to get the desired number of spots. The upside is that it is a BLF and visible. 

  If you used auto-provision, then I would need to look at a capture and see how the provisioning file is populating the field and then how sent to the UCM when engaged. 

  Try the DTMF as a test and see. I have seen a number of errors in the implementation of Yeastar's auto-provisioning function and have reported some of these. These were on Grandstream phones, but I suppose that nothing precludes some on the Yealink or others as well.