That’s likely to be normal unless you obtained the compiled kernel module from your Linux distributor, or you signed it yourself, and have provided the relevant key.
It’s going to be tainted because of not being in the official buld, even if you resolve the signing issue. In principle, you would need to generate your own signing key, make the corresponding certificate available to the kernel, and sign the module when you build it. However, I’ ve never done this, so there are probably some missing steps.
Alternatively, you can rebuild the kernel with modules signing checks disabled.
I imagine to avoid the out of tree warning, you would need get the Linux source code, merge dahdi into the source tree and adjust the makefiles, but, again, I’ve never done this, and even if you did it, the kernel would really be tainted, but you would have hidden the fact, so why bother.