Having some trouble with FusionPBX 5.3 and CallerID with remote call forwarding. Caller ID is set on each extension and works well locally and outbound to the SIP provider O.K.
However, when forwarding using the Call Forward app in Fusion, there is a problem when the forward is remote. So when someone calls from outside and then call forward is set to go back out, like someone calls from a cell phone from outside and the call forward then forwards to someone else's cellphone, Fusion takes the CallerID from the Originating call and passes it all the way through back out. The SIP provider then rejects the call as the CallerID is not authorized (in my case Twilio).
So in the older versions of FusionPBX I had resolved this by setting the default_caller_id in the dialplan to a fixed number for the organization that was authorized for the SIP provider. This only seemed to affect the CallerID of any extension where the CallerID setting was not filled in, and then for Call Forward it also would set this outbound when someone called remotely and then the call forwarded back out. Not perfect but at least calls would always work.
But recently I did a clean install of Fusion 5.3 and then set it up from scratch again as so many things had changed. I found the way the dialplan works in 5.3 is substantially different in especially these areas. Setting the default_caller_id does not appear to affect call forwarding as before. However, there are now settings in the dialplan under call-forward-all that were not there in the older versions that seem to be able to do what is needed. In the lower section of call_forward_all if I set outbound _caller_id_number to a specific number as I had done before for default_caller_id it works. Not sure if this is the intended way to do this or the best, but it works. Ideally I would think it better to set outbound_caller_id_number to the caller ID setting of the extension, but I don't know how to do that (any suggestions welcome!).
However, when forwarding using the Call Forward app in Fusion, there is a problem when the forward is remote. So when someone calls from outside and then call forward is set to go back out, like someone calls from a cell phone from outside and the call forward then forwards to someone else's cellphone, Fusion takes the CallerID from the Originating call and passes it all the way through back out. The SIP provider then rejects the call as the CallerID is not authorized (in my case Twilio).
So in the older versions of FusionPBX I had resolved this by setting the default_caller_id in the dialplan to a fixed number for the organization that was authorized for the SIP provider. This only seemed to affect the CallerID of any extension where the CallerID setting was not filled in, and then for Call Forward it also would set this outbound when someone called remotely and then the call forwarded back out. Not perfect but at least calls would always work.
But recently I did a clean install of Fusion 5.3 and then set it up from scratch again as so many things had changed. I found the way the dialplan works in 5.3 is substantially different in especially these areas. Setting the default_caller_id does not appear to affect call forwarding as before. However, there are now settings in the dialplan under call-forward-all that were not there in the older versions that seem to be able to do what is needed. In the lower section of call_forward_all if I set outbound _caller_id_number to a specific number as I had done before for default_caller_id it works. Not sure if this is the intended way to do this or the best, but it works. Ideally I would think it better to set outbound_caller_id_number to the caller ID setting of the extension, but I don't know how to do that (any suggestions welcome!).
