Caller ID on attended transfer

[tcarter@teklinks.com]

Hello,

I have an issue with caller ID not being passed on attended transfer. It works fine on blind transfer. The phones are T42G,T46G,T48G running XX.80.193.130 firmware. It also does the same on T46S running 66.81.193.110.

Example: Inbound caller to ext 101 receives call from John Doe @ 222-222-2222, transfers (attended) to ext 102, ext 102 receives the call but the display only shows Station 101 as the caller ID. Blind transfer displays the caller ID as John Doe 222-222-2222.

Any ideas?

Thanks,

Tim

[Aishion_Yealink]

(08-30-2017 08:39 PM)tcarter@teklinks.com Wrote:  Hello,

I have an issue with caller ID not being passed on attended transfer. It works fine on blind transfer. The phones are T42G,T46G,T48G running XX.80.193.130 firmware. It also does the same on T46S running 66.81.193.110.

Example: Inbound caller to ext 101 receives call from John Doe @ 222-222-2222, transfers (attended) to ext 102, ext 102 receives the call but the display only shows Station 101 as the caller ID. Blind transfer displays the caller ID as John Doe 222-222-2222.

Any ideas?

Thanks,

Tim

Dear Tim,

Do you mean after transfer when ext102 are talking with John Doe, the screen on ext102 display ext101 instead of John Doe 222-222-2222, if so, please kindly set below auto provision parameter:

account.x.refresh_remote_id.enable = 1
features.save_init_num_to_history.enable = 1

For more information about auto provision, please refer to below guide:

http://download.support.yealink.com/down...V81_70.pdf

If the issue still exist, please kindly reproduce the issue and offer us trace files about ext102 for further analysis as below:

a. Level 6 syslog
b. PCAP trace
c. Config.bin

You can get the guide from this link to see how to export the issue data:

http://support.yealink.com/faq/faqInfo?id=311

Any misunderstandings, please feel free to contact us.

Best Regards
Aishion

[tcarter@teklinks.com]

Thank you Aishion! That did correct the issue. Have a great day!

[Aishion_Yealink]

(09-01-2017 02:07 PM)tcarter@teklinks.com Wrote:  Thank you Aishion! That did correct the issue. Have a great day!

Dear Tim,

Gald to hear that and my pleasure. It's my honor to work with you.

​If you have another question, please feel free to create a new ticket to contact us.
-----------------------------------------Important Notification May Need Your Attention------------------------------------------------------------
Dear Yealink Cusotmer,
 
To Provide better technical support Service and best support experience, Yealink decide to open Yealink Ticket system service (https://ticket.yealink.com )to Yealink customers. and glad to inform you it’s ready now!
At the same time, Yealink plan to redefine the role of email support@yealink.com that after 2017-9-17, the mail will be only for Ticket login problems report or Case follow-up (Please provide ticket case ID), for technical case open and submit,  Please use Yealink Ticketing system. Hope your understanding.
 
How to get Yealink Ticket account? And what’s benefit? Here you go:
Yealink ticketing system (https://ticket.yealink.com ), is powerful, record-able and traceable system which definately brings value-add service to Yealink customers. Please following this guide http://support.yealink.com/faq/faqInfo?id=678 to Register and enjoy Yealink Ticketing Service with below valued-added benefit:
l Open & Manage & Trace case easily
l Communicate with Yealink technical support team directly to get latest update
l Check the status of your opened cases and review closed cases
The Ticket account also can be used for:
l Apply Skype for Business license for Yealink SFB phones.
l Login Yealink support website & forum to get more support resource about Yealink products
 
Best Regards
Yealink Technical Support Team
​----------------------------------------------------------------------------------------------------------------------------------------------------------------

[Catherine33]

I am having this same problem with T56A and T58A phones..

I tried your suggestion of
account.x.refresh_remote_id.enable = 1
features.save_init_num_to_history.enable = 1

uploading it manually through Settings -> Configuration -> Upload File

Here are the entries I added to the configuration file I downloaded:

account.1.refresh_remote_id.enable = 1
account.2.refresh_remote_id.enable = 1
account.3.refresh_remote_id.enable = 1
account.4.refresh_remote_id.enable = 1
account.5.refresh_remote_id.enable = 1
account.6.refresh_remote_id.enable = 1
account.7.refresh_remote_id.enable = 1
account.8.refresh_remote_id.enable = 1
account.9.refresh_remote_id.enable = 1
account.10.refresh_remote_id.enable = 1
account.11.refresh_remote_id.enable = 1
account.12.refresh_remote_id.enable = 1
account.13.refresh_remote_id.enable = 1
account.14.refresh_remote_id.enable = 1
account.15.refresh_remote_id.enable = 1
account.16.refresh_remote_id.enable = 1

features.save_init_num_to_history.enable = 1

Then I uploaded it with the additional lines.

But no success!

Please tell me how to fix this!

(08-31-2017 02:30 PM)Aishion_Yealink Wrote:  

(08-30-2017 08:39 PM)tcarter@teklinks.com Wrote:  Hello,

I have an issue with caller ID not being passed on attended transfer. It works fine on blind transfer. The phones are T42G,T46G,T48G running XX.80.193.130 firmware. It also does the same on T46S running 66.81.193.110.

Example: Inbound caller to ext 101 receives call from John Doe @ 222-222-2222, transfers (attended) to ext 102, ext 102 receives the call but the display only shows Station 101 as the caller ID. Blind transfer displays the caller ID as John Doe 222-222-2222.

Any ideas?

Thanks,

Tim

Dear Tim,

Do you mean after transfer when ext102 are talking with John Doe, the screen on ext102 display ext101 instead of John Doe 222-222-2222, if so, please kindly set below auto provision parameter:

account.x.refresh_remote_id.enable = 1
features.save_init_num_to_history.enable = 1

For more information about auto provision, please refer to below guide:

http://download.support.yealink.com/down...V81_70.pdf

If the issue still exist, please kindly reproduce the issue and offer us trace files about ext102 for further analysis as below:

a. Level 6 syslog
b. PCAP trace
c. Config.bin

You can get the guide from this link to see how to export the issue data:

http://support.yealink.com/faq/faqInfo?id=311

Any misunderstandings, please feel free to contact us.

Best Regards
Aishion

[Scott311]

Hi Aishion,

We have this same issue, I have added those parameters but the caller ID is still not handed off during the transfer.

I followed the steps to gather the PCAP, Config.bin and SYSLOG.

Can I send those two you,. I did reboot the T48S prior to the test. Thanks.

---

(09-01-2017 02:07 PM)tcarter@teklinks.com Wrote:  Thank you Aishion! That did correct the issue. Have a great day!

What Firmware version are you using? Thanks.

[PC112 Köln-Süd]

In our Case the Issue also had not been fixed by adding the Parameters.
Maybe it only works with a specific FW Version?
Or did we made an mistake applying this fix?
We just uploaded the two Parameter lines in an CFG File using the
autprov. Function.
Was it right?
Or anything else to do?
Erol
PC112.de

[tcarter@teklinks.com]

(12-21-2017 04:41 PM)Scott311 Wrote:  Hi Aishion,

We have this same issue, I have added those parameters but the caller ID is still not handed off during the transfer.

I followed the steps to gather the PCAP, Config.bin and SYSLOG.

Can I send those two you,. I did reboot the T48S prior to the test. Thanks.

---

(09-01-2017 02:07 PM)tcarter@teklinks.com Wrote:  Thank you Aishion! That did correct the issue. Have a great day!

What Firmware version are you using? Thanks.

66.81.193.110

[PC112 Köln-Süd]

We would be very pleased if Support would answer.

Our Customer forces us to replace all the Yealink phones if this issue could not be fixed[/align] soon.

[CEPM Nate]

PC112, did you confirm that the lines are actually added to the config? (Export config file to check)