Yealink Forums

Yealink/Users
Hoping there is something we can do for this.
What i got is a customer that has at time a very high call volume at times. Those calls being placed on shared parks and then an announcement being made over the PA that you have a call on XYZ park.

What is happening is when 2 people press Park1 at the same time one of them gets it and the other will get a transfer failed.

It issue is the users are answering,parking, paging so fast they are not paying attention. So the user who does not get the park will see a "Trnasfer Failed" on there phone. But not noticing the transfer failed they will hit the DSS Key for the paging which ends up transferring the call to paging and the end resolute is a customer is connected to the overhead paging. They are having this happen multiple times a day.

To me it would appear that on the yealink phone if you try parking a call on a busy line the park indeed does fail but the initiated transfer is still active. Is there any way to have that initiated transfer fail along with the attempted park so that they wouldn't be running into this issue of accidentally transferring customers to the paging system?

What i have is a 3CX phone system on v12sp6.1
Yealink T46 phones. Currently running beta version 73beta2 but have tested on V72/V71 which have the same results.

(10-24-2014 01:24 PM)tsukraw Wrote: [ -> ]Yealink/Users
Hoping there is something we can do for this.
What i got is a customer that has at time a very high call volume at times. Those calls being placed on shared parks and then an announcement being made over the PA that you have a call on XYZ park.

What is happening is when 2 people press Park1 at the same time one of them gets it and the other will get a transfer failed.

It issue is the users are answering,parking, paging so fast they are not paying attention. So the user who does not get the park will see a "Trnasfer Failed" on there phone. But not noticing the transfer failed they will hit the DSS Key for the paging which ends up transferring the call to paging and the end resolute is a customer is connected to the overhead paging. They are having this happen multiple times a day.

To me it would appear that on the yealink phone if you try parking a call on a busy line the park indeed does fail but the initiated transfer is still active. Is there any way to have that initiated transfer fail along with the attempted park so that they wouldn't be running into this issue of accidentally transferring customers to the paging system?

What i have is a 3CX phone system on v12sp6.1
Yealink T46 phones. Currently running beta version 73beta2 but have tested on V72/V71 which have the same results.

Not sure I can help with the Yealink side, but we have paging with 3CX too and had a lot of pain initially, with the same craziness you mention of inbound call connected to paging. We made some changes and it works good now.
If you describe your paging setup and how it's configured in 3CX, maybe I can offer some pointers.

What we have is a snom PA1 unit programmed with a single extension
Then on the phones we have a DSS key programmed as speed dial to the snoms extension.
Fairly simply configuration we have right now

Yeah, that's identical to how we do it, except we are using a Linksys gateway to the paging unit instead of your Snom. Sorry, can't help more with your original question.

Off topic, but I would be interested in seeing your Snom config. I have the PA1 too but wasn't able to get it configured properly.

Yealink support do you have any input on this?

888VOIP support figured it out. under Features/Transfer/Transfer Mode Via Dsskey.
By default it was set to Blind Transfer. Which as it sounds means when you are on a call and press a DSS key it blind transfers the call to that.

We changed the value to New Call. So when the user does not park there call and mistakenly presses the paging they get a new call to it instead of transferring the customer there.