Hi Roy,
There is a bit of a registration process to obtain stir / shaken certificates from the STI-CA as a service provider, and it probably makes sense to do that if you know the real identity of the SIP trunk customers that own numbers you host on their behalf.
If you want to offer SIP trunking from sipX it probably makes sense to add the required Stir / Shaken Identity header (RFC 8224) to the built in SBC / sipXbridge module. There is no admin or SIP logic for that in sipXbridge at the moment, but it should be straightforward enough to add an admin or config interface for the STI keys and the corresponding logic to add a signed JWT to the SIP Identity header.