TCP/TLS register with md5secret

I have the following configuration working:

transport=udp
defaultuser=XXX
md5secret=YYY
callbackextension=s

My server can successfully register with my provider and receive calls.
Now I want to switch to TCP or TLS (both supported on provider side).

Changing transport in a peer definition will not help - Asterisk will keep using UDP for registrations.
So, I have to use a legacy ‘register=’ statement and specify transport there:
register=tcp://XXX:ZZZ@proxy.domain

This actually will work, but I don’t want to use a clear text password (ZZZ) there. My goal is to keep using md5secret like with UDP, but I cannot guess the right ‘register=’ syntax.
Can anybody advise on this?
Thanks!

1 Like