There were some extra entries in the default pjsip profile which were the culprit. The entries were there since quite a few versions back and hadn't caused any sort of issue with the trunks until we updated yesterday. Even after reverting to the previous working version, the trunks wouldn't get properly created until I found the extra entries and removed them. After that, the endpoints are created and the trunks are up once again.
@JaredBusch The device is tied to the numeric extension, it lets you set the device's username to whatever you want.
The better question is why are you even thinking this is a good idea?
What benefit are you thinking you are gaining by using a non-standard approach?
All this does is complicate things by putting a random value in a place that is normally something that matches the extension. This is a 1 to 1 tie between this informaiton and the extension. There is no benefit to this.
Only after you've pigeon-holed yourself into that 1 to 1 relationship.
No, it is a 1 to 1 relationship regardless of if you use the extension or a name or a fuck01.
That auth name is 100% tied 1 to 1 to the extension.
@JaredBusch fair enough, I haven't used the product itself as of yet and wasn't aware it had whitelisting inside the product, if this was specific to just fail2ban then that method would be suitable, but in this case I agree with you, my mistake.