+- Yealink Forums (http://forum.yealink.com/forum)
+-- Forum: IP Phone Series (/forumdisplay.php?fid=4)
+--- Forum: T4x Series (/forumdisplay.php?fid=31)
+--- Thread: T48G Call Pickup Caller ID (/showthread.php?tid=39365)
T48G Call Pickup Caller ID - Sauriel - 11-17-2016 05:19 PM
Hi
Is there a way to get the original caller ID to display on a phone that uses a call pick up code to pick up an incoming call that is ringing another extension?
When picking up a call that is ringing another extension, we only see the extension number of the phone we are picking up the call from.
I have tried all options in "Caller ID Source" setting under Accounts>Advanced
I get this on display:
FROM **530509040 (extension)
PAI **530509040 (extension) for 2sec. than it changes to the name of person working on this phone
PAI-FROM **530509040 (extension) for 2sec. than it changes to the name of person working on this phone
RPID-PAI-FROM **530509040 (extension) for 2sec. than it changes to the name of person working on this phone
PAI-RPID-FROM **530509040 (extension) for 2sec. than it changes to the name of person working on this phone
RPID-FROM **530509040 (extension)
No option fixed my problem, need to get caller number, in my case my GSM number....
FreePBX: 13.0.188.9
Phones T48G firmware: 35.80.9.2
Asterisk 13.5.0
Please let me know if there is a way to correct this.
Thanks in advance for any assistance received.
RE: T48G Call Pickup Caller ID - Karl_Yealink - 11-22-2016 08:42 AM
Please try to provision the string below.
account.x.cp_source = 0, the x mean the detail account, you need to change x to detail account number.
RE: T48G Call Pickup Caller ID - Sauriel - 12-13-2016 11:15 AM
Hi Karl,
my provider fixed the problem in our pbx..
But now we have similar problem like discused in here: http://forum.yealink.com/forum/showthread.php?tid=35619
The monitored user (A) gets a call, the address book lookup on (A) works fine, i pick up the call on (B) and on (B) he address book lookup dont work,
i see only the number which called A.
in the thread abouve it was a firmware bug.. so how is it on T48G ?
T 48G Firmware 35.80.9.4
Tnx Roman