T46G transfer with Caller ID

[hackin8]

We have several different systems and want to be able to transfer calls using the T46G, using multiple DSS keys to save having to type in the VOIP extension number to transfer.

We have several DSS keys set up as follows:
Type: "Speed dial"
Value: "123456" (The VOIP extension number)
Label: "Fred" (Extension Owners name)
Line: "Line 1"

Currently the T46G operator answers the call, places it on hold. Presses the DSS key, which dials the VOIP extension. Then they can talk to the recipient and transfer the call by hanging up. This works perfectly, except the CallerID is not transferred - the recipient sees the VOIP extension number of the T46G.

I have tried using "BLF", "Forward", "transfer" in place of "Speed Dial" but they don't appear to work.

Am I missing something - help appreciated.

[Kevin_Yealink]

(11-18-2016 10:22 AM)hackin8 Wrote:  We have several different systems and want to be able to transfer calls using the T46G, using multiple DSS keys to save having to type in the VOIP extension number to transfer.

We have several DSS keys set up as follows:
Type: "Speed dial"
Value: "123456" (The VOIP extension number)
Label: "Fred" (Extension Owners name)
Line: "Line 1"

Currently the T46G operator answers the call, places it on hold. Presses the DSS key, which dials the VOIP extension. Then they can talk to the recipient and transfer the call by hanging up. This works perfectly, except the CallerID is not transferred - the recipient sees the VOIP extension number of the T46G.

I have tried using "BLF", "Forward", "transfer" in place of "Speed Dial" but they don't appear to work.

Am I missing something - help appreciated.

Dear,

This is Kevin from Yealink support team, nice to know you.

For your question, the recipient also use T46G, right?

You can use the syntax 'account.x.refresh_remote_id.enable=' to do a auto provision.
NOTE: you should change the X to the corresponding line. Such as if the recipient use line 1, then you should change X to 1.
For the value, please set it to 1 to test again.

Please let me know if any update. if the issue still exist, please send the pacp,syslog,config.bin files to me. For how to get them, you can refer to the FAQ:http://support.yealink.com/faq/faqInfo?id=311

NOTE:you should reproduce the whole process, so that you can get useful files to me.

BR
Kevin

[hackin8]

Before I try auto provisioning I should clarify. All incoming calls are answered on the T46G. Some of the extensions use Yealink W52P, some use Yealink T19P and some use various other makes of phone. (some in office, some home workers). That is why we use the VOIP extension number to transfer the calls.
Would your suggestion still give the desired result?

(If T46G is not available and T19P answers and then transfers - the caller ID is passed through)

Thanks

(11-22-2016 12:39 PM)Kevin Wrote:  

(11-18-2016 10:22 AM)hackin8 Wrote:  We have several different systems and want to be able to transfer calls using the T46G, using multiple DSS keys to save having to type in the VOIP extension number to transfer.

We have several DSS keys set up as follows:
Type: "Speed dial"
Value: "123456" (The VOIP extension number)
Label: "Fred" (Extension Owners name)
Line: "Line 1"

Currently the T46G operator answers the call, places it on hold. Presses the DSS key, which dials the VOIP extension. Then they can talk to the recipient and transfer the call by hanging up. This works perfectly, except the CallerID is not transferred - the recipient sees the VOIP extension number of the T46G.

I have tried using "BLF", "Forward", "transfer" in place of "Speed Dial" but they don't appear to work.

Am I missing something - help appreciated.

Dear,

This is Kevin from Yealink support team, nice to know you.

For your question, the recipient also use T46G, right?

You can use the syntax 'account.x.refresh_remote_id.enable=' to do a auto provision.
NOTE: you should change the X to the corresponding line. Such as if the recipient use line 1, then you should change X to 1.
For the value, please set it to 1 to test again.

Please let me know if any update. if the issue still exist, please send the pacp,syslog,config.bin files to me. For how to get them, you can refer to the FAQ:http://support.yealink.com/faq/faqInfo?id=311

NOTE:you should reproduce the whole process, so that you can get useful files to me.

BR
Kevin

[Kevin_Yealink]

(12-01-2016 07:59 AM)hackin8 Wrote:  Before I try auto provisioning I should clarify. All incoming calls are answered on the T46G. Some of the extensions use Yealink W52P, some use Yealink T19P and some use various other makes of phone. (some in office, some home workers). That is why we use the VOIP extension number to transfer the calls.
Would your suggestion still give the desired result?

(If T46G is not available and T19P answers and then transfers - the caller ID is passed through)

Thanks

(11-22-2016 12:39 PM)Kevin Wrote:  

(11-18-2016 10:22 AM)hackin8 Wrote:  We have several different systems and want to be able to transfer calls using the T46G, using multiple DSS keys to save having to type in the VOIP extension number to transfer.

We have several DSS keys set up as follows:
Type: "Speed dial"
Value: "123456" (The VOIP extension number)
Label: "Fred" (Extension Owners name)
Line: "Line 1"

Currently the T46G operator answers the call, places it on hold. Presses the DSS key, which dials the VOIP extension. Then they can talk to the recipient and transfer the call by hanging up. This works perfectly, except the CallerID is not transferred - the recipient sees the VOIP extension number of the T46G.

I have tried using "BLF", "Forward", "transfer" in place of "Speed Dial" but they don't appear to work.

Am I missing something - help appreciated.

Dear,

This is Kevin from Yealink support team, nice to know you.

For your question, the recipient also use T46G, right?

You can use the syntax 'account.x.refresh_remote_id.enable=' to do a auto provision.
NOTE: you should change the X to the corresponding line. Such as if the recipient use line 1, then you should change X to 1.
For the value, please set it to 1 to test again.

Please let me know if any update. if the issue still exist, please send the pacp,syslog,config.bin files to me. For how to get them, you can refer to the FAQ:http://support.yealink.com/faq/faqInfo?id=311

NOTE:you should reproduce the whole process, so that you can get useful files to me.

BR
Kevin

Dear,

Any update about the issue? Please kindly let me know.

BR
Kevin

[anonymous1714223051383]

Try and ask the operator to do unattended (cold transfer) transfer instead.
Had the same issue, call entered on (ie) extension 102, if 102 called me on extension 104, speaks with me then transfer the call, I would always see 102 on my phone.
We tried another method to see. If 102 called me, said the client's name or whatevery, hang up with me to get back with the client, then "cold" transfer the client to 104, i would see my client's number.

[Kevin_Yealink]

(01-19-2017 12:25 AM)fraukas Wrote:  Try and ask the operator to do unattended (cold transfer) transfer instead.
Had the same issue, call entered on (ie) extension 102, if 102 called me on extension 104, speaks with me then transfer the call, I would always see 102 on my phone.
We tried another method to see. If 102 called me, said the client's name or whatevery, hang up with me to get back with the client, then "cold" transfer the client to 104, i would see my client's number.

Dear,

Thanks for your information.

To help you to solve the issue well, can you tell me how you operator 'code transfer'. We only have blind transfer, semi-attended transfer and attended transfer.

i need to double check with for the scenario:
1. 102 call you(104), then 104 press TRAN button, then input client(such as 105), then press TRAN again, then you will talk with client(105), but the phone just display 102 not 105, right?
2. 102 call you(104), tell you 105 will talk with you, then hang up the call. 102 talk with 105, and press TRAN, then input your number, then press TRAN again, you will receive a call from 105, and the phone will display 105,right?

Please kindly tell me if any misunderstand.

For the issue, please add the syntax 'account.x.refresh_remote_id.enable=1' into the provision file, let me know if any update.
NOTE: you should change the X to the corresponding line. Such as if the recipient use line 1, then you should change X to 1.

For how to auto provision, i upload the guide to the link:
http://ftp.yealink.com/?ShareToken=9CB79...5778501A6A

If it can't help you, please tell me the phone model and the phone firmware. Please also send the pacp,syslog,config.bin files to me. For how to get them, please refer to the FAQ:
http://support.yealink.com/faq/faqInfo?id=313

BR
Kevin

[anonymous1714223051383]

(01-19-2017 03:00 AM)Kevin Wrote:  

(01-19-2017 12:25 AM)fraukas Wrote:  Try and ask the operator to do unattended (cold transfer) transfer instead.
Had the same issue, call entered on (ie) extension 102, if 102 called me on extension 104, speaks with me then transfer the call, I would always see 102 on my phone.
We tried another method to see. If 102 called me, said the client's name or whatevery, hang up with me to get back with the client, then "cold" transfer the client to 104, i would see my client's number.

Dear,

Thanks for your information.

To help you to solve the issue well, can you tell me how you operator 'code transfer'. We only have blind transfer, semi-attended transfer and attended transfer.

i need to double check with for the scenario:
1. 102 call you(104), then 104 press TRAN button, then input client(such as 105), then press TRAN again, then you will talk with client(105), but the phone just display 102 not 105, right?
2. 102 call you(104), tell you 105 will talk with you, then hang up the call. 102 talk with 105, and press TRAN, then input your number, then press TRAN again, you will receive a call from 105, and the phone will display 105,right?

Please kindly tell me if any misunderstand.

BR
Kevin

That is 100% explained for the situation #2
Blind transfer is the way to go.
Attended and semi-attended never gave me the caller-id source. Only the person transfering me the call.

[Kevin_Yealink]

(01-19-2017 03:24 AM)fraukas Wrote:  

(01-19-2017 03:00 AM)Kevin Wrote:  

(01-19-2017 12:25 AM)fraukas Wrote:  Try and ask the operator to do unattended (cold transfer) transfer instead.
Had the same issue, call entered on (ie) extension 102, if 102 called me on extension 104, speaks with me then transfer the call, I would always see 102 on my phone.
We tried another method to see. If 102 called me, said the client's name or whatevery, hang up with me to get back with the client, then "cold" transfer the client to 104, i would see my client's number.

Dear,

Thanks for your information.

To help you to solve the issue well, can you tell me how you operator 'code transfer'. We only have blind transfer, semi-attended transfer and attended transfer.

i need to double check with for the scenario:
1. 102 call you(104), then 104 press TRAN button, then input client(such as 105), then press TRAN again, then you will talk with client(105), but the phone just display 102 not 105, right?
2. 102 call you(104), tell you 105 will talk with you, then hang up the call. 102 talk with 105, and press TRAN, then input your number, then press TRAN again, you will receive a call from 105, and the phone will display 105,right?

Please kindly tell me if any misunderstand.

BR
Kevin

That is 100% explained for the situation #2
Blind transfer is the way to go.
Attended and semi-attended never gave me the caller-id source. Only the person transfering me the call.

Dear,

Thanks for your information. Do you try with the syntax then test again?

If it can't help you, please send the pacp,syslog,config.bin files to me, then i can do more troubleshooting.

May i know how many phones do you have? How many phones have such issue.

BR
Kevin