Link redundancy in trunking environment

Is it possible, in a SIP Connect scenario with dynamic registration, to somehow have two entities on the enterprise side, sharing only one trunk, in a way that makes it possible to distribute traffic in the enterprise direction, between the two endpoints? The idea is to have redundancy on two physical links towards the enterprise, and handle fail-over on the SIP level.

 

Basically the next-hop from the registration-cache should point to a session-group instead of an individual address.

 

In a surrogate-agent we can set customer-next-hop to an SAG, and something similar is basically what we want to achieve for a self-registering endpoint.