Security - Different contexts for inbound/outbound?

Hi guys.
Do you think for security reasons it makes sense to have 2 endpoint definitions for one trunk, which could be just one definition? The “trick” shall be to declare an inbound and an outbound endpoint. The outbound endpoint should have a context named “unspecified” which later in the dialplan should be referenced and should be empty (no extension at all) to force suspicious calls which made it up to there to be thrown away because of missing handling in the dialplan? Is this a security consideration?

Besides, do you think it is a good concept to separate a trunk in an inbound and an outbound endpoint not even for security reasons?

Thanks
_fuz

It’s always a good security practice to limit where incoming calls can terminate in my opinion.

Thanks, John.
Do you have an opinion about the “unspecified” context for outbound calls also?

Thanks
_fuz