Outbound Caller ID Number

[Skeelkat]

I am running a multitenant FusionPBX and it seems the behavior of the Outbound Caller ID Number has changed in recent upgrades.
I could always manually enter my Outbound Caller ID in the Extension configuration for example e.g. +264840000000. (My upstream SBC requires me sending the +

Since the last upgrade I have done (currently on 4.5.21 15fa026856ad83e6a0f0cb3e5b6aa90cf14be718). I see that the Oubound Caller ID Number is now taken from the Destinations. This is all fine and good, but I cannot add the number as +264..... it strips it to 264 only as soon as I enter it in the Field.

Any ideas how I can change the behavior of this field to allow me the +?

I have done a Regex ReWrite on the Outbound Route - effective_caller_id_number=${regex(${caller_id_number}|^26484000000(.*)$|+26484000000%1)} that adds the +, but this is not a solution as I would have to add this string to all tenenants manually on the node... It would be a much more elegant solution to allow me to simply add the + in the Outbound Caller ID Field under Destinations.

 

[Adrian Fretwell]

Just check what you have in terms of permissions in the extension category for the superuser.

Because the master branch is a moving target, I can't say what all the permission may be at this moment in time, but you may want to uncheck "outbound_caller_id_select" and make sure that "/effective/outbound/outbound_caller_id_*" are checked. Example screenshot below:

 

[Skeelkat]

Thanks a Million... everything back to way It's expected to be.