Hi all,
I think I ran into a bug with the “From User” field on PJSIP trunks and would like to confirm whether it’s known.
Environment:
- VitalPBX: 4.5.3 R5
- O.S. Debian 12
Context:
I have a PJSIP trunk to a provider (italian) that validates the user-part of the From URI against the authenticated SIP account. If the From user-part does not match the account username, the provider rejects the outbound INVITE with “403 Authentication Username Mismatch” (Asterisk reports Hangup Cause 21 / CHANUNAVAIL). To satisfy this, the user-part of the From header must equal the auth username, so I set it through the trunk’s “From User” field.
Problem:
When I set or modify “From User” on an existing trunk and then Save + Apply Changes, the value is NOT written to the generated PJSIP endpoint. “pjsip show endpoint myendpointname” shows from_user empty. A manual “core reload” / “module reload res_pjsip.so” makes no difference.
Workaround that worked:
Deleting and recreating the trunk from scratch, entering the same “From User” value, writes from_user correctly. It then appears in “pjsip show endpoint” and the From header goes out as expected (the provider accepts the INVITE and the call reaches 180 Ringing).
So it looks like “From User” is only persisted to the endpoint on trunk creation, not when editing an existing trunk.
Questions:
- Is this a known issue, or already fixed in a newer release?
- Can edits to “From User” (and similar identity fields) be made to propagate on Save + Apply Changes, without having to recreate the trunk?
This seems to be the same class of issue reported previously where contact_user was not written to the endpoint. For reference, adding from_user / contact_user manually via pjsip_custom.conf (appending to the endpoint section) also works as a workaround.
Thanks!