Suppress Flowroute Tech Prefix Displaying In History

[uptime1]

In the Android client, the Flowroute Tech Prefix (which is required in SIP settings in order to outbound a call), unfortunately and problematically displays as the beginning part of the phone number called in the Android Recent Call History.

This causes four bad problems:
1) The number display is abnormal, odd and confusing
2) The number doesn't match any contact records
3) The number can't be redialed because it contains the tech prefix, and double appending the tech prefix violates all dialing pattern call rules and won't be interpreted properly
4) And, most concerning, Flowroute, unfortunately, uses that tech prefix for authentication, so it's appearance is a big security hole and creates security vulnerabilities.

Can the Flowroute Tech Prefix be hidden from appearing to eliminate the problems, please?

 

[SweetAction]

Hello and welcome to the party:

Remove Prefix digits from 3CX Client and Call Reports

https://www.reddit.com/r/3CX/comments/mlcwh3

I even opened a ticket with Flowroute about this a while back.

The only way to solve is to do register based instead of IP based

 

[NickD_3CX]

In ever really understood why this prefix exists (or needs to exist), but regardless, Flowroute has been successfully tested with 3CX as Register-based as we point out in Supported SIP Trunks page and in the template.

I'd suggest switching to that.

 

[SweetAction]

In ever really understood why this prefix exists (or needs to exist), but regardless, Flowroute has been successfully tested with 3CX as Register-based as we point out in Supported SIP Trunks page and in the template.

I'd suggest switching to that.

It boils down to 2 reasons for most people:

1) Less secure (my first link to the 3cx idea page goes into that deeper)
2) Better call control. Flowroute can send calls to multiple destinations on a per DID basis - useful if you have many PBXes tied into 1 Flowroute account. For IP authenticated trunks it's easy - send a DID to the specific IP/port and done. For Register based trunks Flowroute can only send to all trunks at the same time and first one to reply (even if the reply is not an answer) gets it.