Question: In a RANflex configuration with group call redundancy, what action does the GCR take when the VMSC does not belong to the group call serving MSC redundancy pool and the group call serving MSC redundancy pool is the anchor MSC redundancy pool?
Option 1: The GCR provides the group call reference directly to the VMSC for call establishment.
Option 2: The GCR provides the group call reference plus routing information to the requesting MSC, which then routes the call to a different MSC within the same redundancy pool.
Option 3: The GCR denies the request due to the VMSC not being part of the serving MSC redundancy pool.
Option 4: The GCR provides the group call reference to the requesting group call serving MSC, which adds routing information identifying the anchor MSC redundancy pool and passes it to the VMSC.
Explanation: In a RANflex configuration with group call redundancy, when the VMSC is not part of the group call serving MSC redundancy pool but this pool acts as the anchor MSC redundancy pool for the group call, the GCR facilitates routing by providing necessary information to the appropriate entity within the redundancy pool. The GCR provides the group call reference to the requesting MSC (within the pool), which adds routing details (identifying the anchor MSC redundancy pool) before forwarding to the VMSC, ensuring seamless voice group call routing and management across different MSCs in a redundant configuration.