[FEATURE]More choice of algorithms in topology hiding

[CzyerChen]

Is your feature request related to a problem? Please describe.

No.

Describe the solution you'd like

At present, the generation of callee callid uses word64 (base64), and the final length depends on the upstream callid, usually the design of the upstream and downstream systems may have the length of the callid within 64 characters, but after base64 expansion, the downstream system may have to be modified due to risks.

For example, use hash at the end to make the final output of the same length, is this possible?

Implementation

• Component: topology hiding
• Type: word64decode , word64encode
• Name:

Describe alternatives you've considered

Additional context

[github-actions]

Any updates here? No progress has been made in the last 15 days, marking as stale. Will close this issue if no further updates are made in the next 30 days.

[razvancrainea]

Unfortunately using a hash is not possible, as the resulted CallID has some encrypted information in it - if we hash it, we would loose that information, and we rely on it to identify the dialog.
On the other hand, I find having different algorithms for generating a new callid useful - as an example, when you just want to change the callid (not necessarily hide anything), you could simply add a prefix to it.