Yealink Forums
Number shown in call history - Printable Version

+- Yealink Forums (http://forum.yealink.com/forum)
+-- Forum: IP Phone Series (/forumdisplay.php?fid=4)
+--- Forum: T4x Series (/forumdisplay.php?fid=31)
+--- Thread: Number shown in call history (/showthread.php?tid=36438)



Number shown in call history - cjtrevor - 11-07-2016 02:30 PM

We have a problem with this scenario -

External caller "A" calls the office.
Receptionist "B" inside the office answers the call.
"B" makes an attended transfer to employee "C" to deal with the caller.

"C" wants to see the caller number of "A" in their call history.
But, at the moment they see "B" in their history and can not find the number of "A" to call them back.

We have set the line in our provisioning -
features.save_init_num_to_history = 0

We are using T46G telephones with firmware 28.80.1.110 and 3CX for Windows PBX.

Is there a solution to the problem please?


RE: Number shown in call history - Lucia_Yealink - 11-14-2016 07:46 AM

Hi Sir,

About your issue, please use the parameter below to do auto provision:

account.X.cid_source=4
account.x.refresh_remote_id.enable = 1
# Please note the X stand for the account that you want to use

If the problem still exist, please kindly provide the level 6 syslog, config.bin and pace trace when you reproduce the issue. About how to get the three files, please refer to the FAQ below:http://support.yealink.com/faq/faqInfo?id=313

Please not update the latest firmware version before you reproduce the issue.

How many phones you have in total? And how many of them have the issue?

You can send the files to Lucia@yealink.com.

Best Regards,
Lucia


RE: Number shown in call history - Lucia_Yealink - 12-21-2016 01:22 AM

Thank you for your reply.

The problem is a know problem. And we have solve it in the latest firmware.

Please refer to the link below to download the firmware and test again:
http://download.support.yealink.com/download?path=upload%2Fattachment%2F2016-12-19%2F6%2F55fce51d-020b-49ee-9082-25d70b61dd40%2FT46-28.81.0.25.zip

Regards,
Lucia


RE: Number shown in call history - cjtrevor - 03-24-2017 07:05 PM

Hello, we have now upgraded to firmware 21.81.0.60 (we use 3CX so have to use version provided by it)

I have added the provisioning lines as above, but still have the same problem.

The caller ID of the outside caller is correctly displayed on the phone during the call, so I know that caller ID is working through the system. It is just that the phone history does not retain the outside caller number, it retains the internal receptionist number that transferred the call through.

With the 3CX firmware 21.81.0.60 is this still a known issue, or is there another line of provisioning required to save the number to phone history please?


RE: Number shown in call history - complex1 - 03-24-2017 08:26 PM

(03-24-2017 07:05 PM)cjtrevor Wrote:  Hello, we have now upgraded to firmware 21.81.0.60 (we use 3CX so have to use version provided by it)

I have added the provisioning lines as above, but still have the same problem.

The caller ID of the outside caller is correctly displayed on the phone during the call, so I know that caller ID is working through the system. It is just that the phone history does not retain the outside caller number, it retains the internal receptionist number that transferred the call through.

With the 3CX firmware 21.81.0.60 is this still a known issue, or is there another line of provisioning required to save the number to phone history please?

Have you take notice of this thread on the 3CX forum?
https://www.3cx.com/community/threads/forwared-calls-with-originating-callerid.48249/


RE: Number shown in call history - cjtrevor - 03-27-2017 12:57 PM

Hi Frank

We had this working perfectly with 3cx and Yealink, until a firmware update by Yealink broke this functionality.

I am hoping that with the new Yealink Firmware supported by 3CX v15 SP5 that we can get this feature working again, as Yealink say that this is fixed in their last firmware.

I am in contact with Yealink support to see if we can resolve it.