T26 Park Button problem Asterisk v1.8

[Yealink Support]

1. Our researcher can't find enough message from the scenario 1, can you supply the pcap of callee that can accept the parking lot anouncement ? If possible, it would be better to supply video.

2. For the scenario 2, it would be better to supply video too.

Thanks to your cooperation.

[JaredBusch]

Regarding Scenario 1, I do not see how your researcher cannot figure this out.

Take a default Elastix or PBX in a Flash install.
Program any 2 Yealink phones as extensions.
Program a DSS key as "Call Park" with value 70 and label "Park Call"

Now call from phone 1 to phone 2.
Have phone 2 press the "Park Call" button.
The person on phone 2 will be disconnected with no audible announcement of the parking lot the call was sent to.
The person on phone 1 will hear the MoH and be in parking lot 71.

The person on phone 2 can dial 71 to pick up the call from the parking lot.

I have done this with the T32G, T38G, T42G and T46G. All devices have the current firmware.

[Yealink Support]

Hi JaredBusch,

We can reproduce your issue in our phones and we has corrected it in test firmware. But we can't reproduce the issue strabuzano have, we can't know why server send the notify to other phones.
The first thought may be that the server sends the notify message to wrong phones.
However, strabuzano said other brands can work well in the same environment. So we need to compare the trace pcap of them with Yealink phones.

[blistovmhz]

(05-17-2014 12:05 PM)Yealink Support Wrote:  Hi JaredBusch,

We can reproduce your issue in our phones and we has corrected it in test firmware. But we can't reproduce the issue strabuzano have, we can't know why server send the notify to other phones.
The first thought may be that the server sends the notify message to wrong phones.
However, strabuzano said other brands can work well in the same environment. So we need to compare the trace pcap of them with Yealink phones.

Sorta the same issue here with the T46G, and FreePBX.
Using Yealinks DSS keys, both Transfer and Call Park (70), correctly parks the call in the lot, but does not notify the parker of the lot number.
IMO, Call Park should operate as a ... pseudo-semi-attended transfer.
EG:
Call comes in, I answer and press Call Park (70). This should put the caller on hold, play me the parking lot number (71-85), transfer the caller to the lot, and hang up my phone.

According to Schooze/FreePBX, the Call Park button should by default, create a new call to the parking lot, listen to the message (parking lot number), transfer the call and hang up.


*EDIT*
I've found a way (with the T46G, and presumably others) to half fix this problem.
If you set a DSS transfer key to 70, and go to "Features" > "Transfer", you can set the "Transfer Mode Via Dsskey" to "Attended Transfer". This will at least let you hit your DSS key, be notified of the parking lot number, then you just press transfer and it will transfer the call to the lot you just called, and hang up.
This is one extra step that I'm confident my receptionists will never be able to figure out... but oh well. it's something.

[Yealink Support]

Hi blistovmhz,

In order to do more troubleshootings, please supply syslog level 6, config.bin and pcap and send to support@yealink.com or support.usa@yealink.com.

How to Get the Correct Syslog, Config.bin and Trace

[alexgonzalez]

Having same issue with T46G, the type Call Park does not work correctly.

Have a Elastix 2.2/Asterik/FreePBX 2.8.1 PBX system with 20x T46G and 5x T42G phones connected to it.

Set up a DSSsoftkey as Call Park type, value: 70, Labeled Call Park on the T46G phones, firmware version 28.72.0.2.

When we press it to park a call, it announces the parking location to the caller rather than to the person putting into Park Call? This is not useful and we have no clue which parking location the caller is on.

The only work around a vendor suggested was to set it to DTMF, value ##70, label Call Park.

This kind of works, but its lousy and we have to hear tones and the word transfer gets cut off. If you hang up too soon, hangs up on caller also. Not good for busy office front desk.

Has any one found how to fix the Call Park type function so it works properly.

[blistovmhz]

I ended up just using TYPE: Transfer, VALUE: 70, and make sure your phone is setup to do attended transfers (as per my post above).
Works fine. Doesn't play the lot number to the parkee, does play it to the parker.

[alexgonzalez]

(06-09-2014 10:50 AM)Yealink Support Wrote:  Hi blistovmhz,

In order to do more troubleshootings, please supply syslog level 6, config.bin and pcap and send to support@yealink.com or support.usa@yealink.com.

How to Get the Correct Syslog, Config.bin and Trace

FYI: The email given of support@yealink.com does not work, comes back as undeliverable:
----- The following addresses had permanent fatal errors ----- <support@yealink.com>
(reason: 451 4.4.1 reply: read error from mail.yealink.com.)

[alexgonzalez]

(07-18-2014 12:01 PM)blistovmhz Wrote:  I ended up just using TYPE: Transfer, VALUE: 70, and make sure your phone is setup to do attended transfers (as per my post above).
Works fine. Doesn't play the lot number to the parkee, does play it to the parker.

Tried it this morning and this does not work for me. It calls out the parking location to the caller on the phone instead of to us. Acts exactly as the Call Park function does on the TYPES.

[blistovmhz]

Make sure you've set the option " Transfer Mode Via Dsskey" to "attended transfer" (on your phone).

Then, when you hit the "transfer" 70 dss key, it should put the caller on hold, dial 70, play the message to you, and THEN you hit transfer again to connect the caller to the lot and your phone should automatically hang up.