I'm using 3CX v11 SP3, and am having a problem with call forwarding calls which arrive into a queue. I'm asking here in case anyone else has experienced the problem and has a solution or workaround. If I set my 3CX extension to 'out of office' with an action of 'forward to my mobile', then if someone rings my extension directly, the call gets forwarded to my mobile as desired. However, if I am logged into a queue, and someone calls the queue, then the call forwarding doesn't work, even though 3CX is trying. The reason seems to be that if someone calls me directly, then the forwarding uses the 'Extension caller id' (of my 3CX extension) as the SIP FROM address when making the outbound call for forwarding. This works great. However, if someone calls through the queue, then the 3CX forwarding uses the ORIGINAL caller's caller ID as the SIP FROM address when making the outbound call. This causes the SIP trunk (with VoIP Unlimited) to fail, with a '403 Spoofed From-URI Detected' SIP error. What happens now is that 3CX keeps on trying to forward the call out, the caller is left on hold, and lots of errors are logged, but the call goes nowhere. So: - is this what 3CX is meant to do? (use the original caller's caller ID) - if not, any ideas where I may have it set wrong? - if it is meant to do this, is there any way around this? (To get it to use the extension caller ID of the forwarding extensions) As a related issue - is there any way to get a forwarded call from a queue to use a particular outbound rule? I can't use the queue extension number in the test where the call is coming from. As far as I can see it just seems to use the first available rule. The problem with that is that I can't even set up an extra SIP trunk just for forwarded calls with forced FROM SIP header data. Currently, this is causing us problems, as it makes things very hard when calls would have to be taken on a mobile phone or have to be forwarded to a call answering service.