Problem description
In the example section of the subscription API (Both Roaming and Reachability Status), the status for synchronous requests is incorrectly shown as "ACTIVATION_REQUESTED" in the "201" response.

Expected behavior
The example reflects that for synchronous subscription requests, therefore the status should be "ACTIVE" immediately upon successful creation and processing of the subscription.

Alternative solution
NA

Additional context
NA