+- Yealink Forums (http://forum.yealink.com/forum)
+-- Forum: IP Phone Series (/forumdisplay.php?fid=4)
+--- Forum: General topics (/forumdisplay.php?fid=15)
+--- Thread: Call forward (/showthread.php?tid=42152)
Call forward - shane.caznet - 10-10-2018 04:14 AM
Hi
We use the T46S and T48S connected to FreePBX and we have a problem with forwarded calls.
If the handset users sets their handset to forward calls, the handset sends the original caller ID instead of its own on the forwarded call. We need it to always send its own Caller ID.
For example:
Incoming call from 123456 gets sent to Extension 2000 which is a T46S.
Extension 2000 forwards call to external telephone number 987654321.
External third party (987654321) sees caller id 123456 because the handset has sent that CID.
Why does the handset attempt to send a CID rather than just letting the PBX do it?
RE: Call forward - jolouis - 10-10-2018 06:16 PM
(10-10-2018 04:14 AM)shane.caznet Wrote: Incoming call from 123456 gets sent to Extension 2000 which is a T46S.Huh? That sounds like how a call forward is supposed to work. External callerID is 123456 in your example. So if Extension 2000 forwards to third party, the logic is that the third party should see the callerID of the person actually calling... in that case, that is 123456 as you stated. That has nothing to do with the phone sending a CID, and in fact it's probably being handled by your PBX anyway.
Extension 2000 forwards call to external telephone number 987654321.
External third party (987654321) sees caller id 123456 because the handset has sent that CID.
Why does the handset attempt to send a CID rather than just letting the PBX do it?
Now, if you were to say that when 987654321 rang it showed callerID of "2000" instead of the actual caller that would be far more unusual...
So what's the problem here?