01-27-2015, 03:52 AM
Hello,
I am curious to get other people's thoughts on the Speed Dial keys and whether they should globally affected by the transfer.dsskey_deal_type parameter. When one presses a Speed Dial key, you would expect that it only dials the number that is configured on the speed dial. However, I have observed, that this behaviour is affected by what value you set for the transfer.dsskey_deal_type parameter. If the parameter is not defined or set to be attended or blind, the following scenario occurs:
Assume: linekey.2 is defined as a speed dial ala:
linekey.2.line = 1
linekey.2.value = 15555551212
linekey.2.type = 13
linekey.2.label = John Q Public
linekey.2.extension =
linekey.2.xml_phonebook =
1. Call Account 1 on a Yealink T4x
2. Answer the call
3. Press the hold softkey
4. Press the linekey.2's configured speed dial contact.
The call is transferred either blind or attended depending on what the transfer.dsskey_deal_type parameter is set to. This is contrary to what a speed dial is, or how I would think most people interpret the function to be. I.E. the call that was previously on hold is transfer somehow as opposed to staying on hold while the speed dial contact is called.
The real question is why the key is doing a transfer when its purpose is to not transfer callers in the first place? Does anyone have a suggestion as to a work around for getting speed dials to work as a Speed Dial Key that actually speed dials while leaving the transfer.dsskey_deal_type parameter set to attended or blind?
Thanks,
Robert
P.S - I tried this on the latest firmware rev for a T48 and it was the same symptoms.
I am curious to get other people's thoughts on the Speed Dial keys and whether they should globally affected by the transfer.dsskey_deal_type parameter. When one presses a Speed Dial key, you would expect that it only dials the number that is configured on the speed dial. However, I have observed, that this behaviour is affected by what value you set for the transfer.dsskey_deal_type parameter. If the parameter is not defined or set to be attended or blind, the following scenario occurs:
Assume: linekey.2 is defined as a speed dial ala:
linekey.2.line = 1
linekey.2.value = 15555551212
linekey.2.type = 13
linekey.2.label = John Q Public
linekey.2.extension =
linekey.2.xml_phonebook =
1. Call Account 1 on a Yealink T4x
2. Answer the call
3. Press the hold softkey
4. Press the linekey.2's configured speed dial contact.
The call is transferred either blind or attended depending on what the transfer.dsskey_deal_type parameter is set to. This is contrary to what a speed dial is, or how I would think most people interpret the function to be. I.E. the call that was previously on hold is transfer somehow as opposed to staying on hold while the speed dial contact is called.
The real question is why the key is doing a transfer when its purpose is to not transfer callers in the first place? Does anyone have a suggestion as to a work around for getting speed dials to work as a Speed Dial Key that actually speed dials while leaving the transfer.dsskey_deal_type parameter set to attended or blind?
Thanks,
Robert
P.S - I tried this on the latest firmware rev for a T48 and it was the same symptoms.