Authorization User used for registration but not as authuser

[Scapal]

The 'Authorization User' parameter in the Askozia interface is indeed used as authentication user for the registration but not during the INVITE Digest that goes back using the defaultname as authentication username.

[Michael]

Any suggestions for a fix or better configuration generation?

[Scapal]

Conventions

• Name beween square brackets reference Askozia SIP Provider settings
• Names between curly brackets reference Asterisk sip.conf settings

On Askozia : [Username], [Authorization User], [From User], [From Domain]
There is a mix between: [Username], [Authorization User], [From User]

Proposed solution
[Username] and [Extension] would be better imho:
Generates the Registration: [Extension]:[Username]:[Password]@[From Domain]/[Extension]
And [Username] being used on INVITE challenge.
{Username} = [Username]
{FromUser} being set to [Extension] if [Extension] if a [Username] is specified.

instead of the current
[Username]:[Authorization User]:[Password]@[From Domain]/[Extension]
And [Username] being used on INVITE challenge.
As you see, the [Authorization User] isn't used in the current model.