We've had a system running Elastix 1.6 for quite some time now with no problems. We have also had a few systems running Elastix 2.2 with no problems. After migrating the Elastix 1.6 box to a clean install of Elastix 2.2 we came across an issue that was actually happening to all of our Elastix 2.2 boxes. When we go to park a caller, it announces to the caller what parking lot they're on. (For instance I put a call on park and they hear "7" "1" then MOH).

After doing some reasearch, I found that some people are saying that it has to do with the way the phone is handling the park function. We are using Yealink SIP-T28P phones, and have confirmed that this only happens with our Elastix 2.2 systems, not the Elastix 1.6 systems.

Has anyone come across this? I'd be happy just disabling the parked call announcement, but cannot even find how to do that.

Any help would be greatly appreciated.

I don't understand very well what is the issue, how does it should work?

Well, the way it worked before migrating to Elastix 2.2 was that when we put a call on park. The caller only heard the music on hold. Now they are hearing the number for the parking lot they got put on. For instance, if you call into me now and I put you on park, you would hear "seven one" then the music on hold.
We don't want it to annouce the parking lot number, just play the music on hold.

asummerell,

1) What phones are you using?
2) Are you transferring using the Asterisk Transfer or using the transfer function on the phone??
3) what is the steps you are using to transfer the call to the call park?? e.g. XFER 70# {listen for parking lot} XFER

The Call Parking has not changed from the old to the new 2.2, still works the same.

I have just tested it to make sure, and works normally, the caller does not hear the parking lot number, all they hear is MOH from the moment you transfer them to the parking lot.

Regards

Bob

1) What phones are you using?
We are using Yealink SIP-T28P phones.


2) Are you transferring using the Asterisk Transfer or using the transfer function on the phone??
We have a key setup on our phones that is using the 'Call Park' feature on the phone.


3) what is the steps you are using to transfer the call to the call park?? e.g. XFER 70# {listen for parking lot} XFER
It is setup for the key to do 'Call Park' to 70. As a test since you posted XFER 70# XFER. I tried setting the key up to to 'Call Park' 70# instead of just 70, and it disconnected the Yealink phone, but left the caller orphaned on the extension (in FOP) and as the caller at that point, it was just dead air.

As a side note, if I transfer them manually, Hitting Transfer 70# <waiting for the parking lot message> and then transfer. The caller does not hear the parking lot number. Why would this have changed from 1.6 if nothing has changed. No settings on the phone had been changed, only the Elastix box being upgraded to 2.2.

I have a T28 here....will test over the next couple of hours (just stepping out)...

Regards
Bob

Bob wrote:
I have a T28 here....will test over the next couple of hours (just stepping out)...

Regards
Bob

Thank you for helping me get to the bottom of this. I've been pulling my hair out trying to figure it out.

asummerell,

Can you confirm what Freepbx you are running??

As you said, it appears to be an issue with using the call park using the keys on the IP Phone. As you are probably aware, this is not just affecting the Yealink but other phone models as well...

I will have a close look at what is occurring, but it is going to take a while, but not just an Elastix issue either. Most likely a change in the Asterisk handling....

Regards

Bob

asummerell,

I should also note that this is not necessarily a bug with Asterisk.

Call parking was always meant as a Attended or Consultative transfer (where you listen to the announcement.

For instance this feature works fine on the Cisco 504G

The fact that many were performing a blind transfer (using the IP Phone BLF's instead) was more of "undocumented" feature that Asterisk developers were not aware of.

As you can appreciate, when they are doing development or changes to the call park feature (which they appear to have done with Asterisk 1.8) they have not considered that users were doing this, and as such it has "broken" this unique (and useful) feature.

So it might be a while to have this resolved, as the call park functionality is a all in one routine, and not something that Freepbx has the ability to control (e.g. the announcement is integrated within the Asterisk code.

Regards

Bob

Just out of interest, and thank you for pointing out this "feature", I have setup the "undocumented" feature on the lab SPA504G...with Elastix 2.2 (note yum updated to latest on this particular system) but not running Elastix 2.3 beta. I don't think the Yum update had anything worthwhile as Asterisk still on 1.8.7.0 (same as the Elastix ISO).

Basically

5 keys for each parking lot e.g. 71,72,73,74,75
1 Key which speeddials (blind) to Ext 70

I just tested it with several calls at once being picked up by the SPA504g in turn, and I used the speed dial to send each call to the parking lot (which gave no announcement naturally). After each call was parked, each of the lamps lit to show a call was parked.
Finalised the test by picking up each call using the parking lamps/button.

At no time did I hear the announcement, just straight to music on hold for the caller.

So it appears that it may be specifically how the phones manages the transfer using the BLF buttons......Just a suggestion at the moment, is the yealink up to latest firmware release??

I am going to setup the Yealink to perform the same exact function....to save me some time...can you provide your exact settings for your BLF Buttons, so that I can test apples with apples.

Regards

Bob