You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: