Figure 10.6.2.9.3.3-1 illustrates the case where the procedure to initiate a regroup procedure with multiple MCPTT systems using a preconfigured MCPTT group described in
subclause 10.6.2.9.3.1 commences, but where the request for the regroup is rejected by the partner MCPTT server, for example because one of the groups hosted by the partner MCPTT server is already regrouped by other group regrouping procedures.
In this procedure, any gateway MC servers in the primary or partner MCPTT systems are not shown.
Pre-conditions:
-
MCPTT client 1 is authorized to initiated a preconfigured regroup procedure, and is receiving MCPTT service in the primary MCPTT system of MCPTT client 1.
Step 1.
The authorized user of MCPTT client 1 initiates the regroup procedure as stated in
clause 10.6.2.9.3.1 step 1-4.
Step 2.
The MCPTT server sends the preconfigured regroup requests to the MCPTT server in the partner MCPTT system.
Step 3.
The partner MCPTT server checks the status of any MCPTT groups hosted by that partner MCPTT server, and determines that one or more requested MCPTT groups has already been regrouped by another group regrouping procedure.
Step 4.
The partner MCPTT server sends a preconfigured regroup reject to the primary MCPTT server, indicating the reason for rejection.
Step 5.
The primary MCPTT server sends a preconfigured regroup reject to MCPTT client 1, indicating the reason for rejection.