Deactivate policy rule
Deactivates policy rules.
GET /sponsordata/sds/campaigns/deactivate?{requestParametersGoHere}
accept: application/JSON/XML
The SDGW, upon the OCSG accepting the activation request, schedules a trigger for the deactivation (Tango to OCSG) on the endDateTime specified
|
Request parameters table
All parameters are mandatory. |
Parameter | Description | ||
---|---|---|---|
|
Integer that identifies the method to be executed. So, when you need to deactivate a policy rule, this is the request parameter for that. values
|
||
|
A string that denotes the name of the sponsor. Who is this bodacious benefactor?
|
||
|
Integer that uniquely identifies the campaign. Important stuff here!
|
||
|
A mandatory parameter which represents the auto-generated ID which comes from the [Add or Activate a Policy Rule] operation response.
|
||
|
A string that names the campaign. |
||
|
A string that contains details (meta-data) about the campaign. |
||
|
List of server-side IP addresses for which access is sponsored. This is comma-separated.
|
Response parameters table
Once you have deactivated a policy rule, the response will contain the parameters as outlined in the table and sample below.
Parameter | Description | ||
---|---|---|---|
|
Integer showing the result of the operation. <div class="ulist"> <ul> <li> <p><code>0</code> = Success.</p> </li> <li> <p><code>-1</code> = Failure.</p> </li> <li> <p><code>-2</code> = The campaign already exists.</p> </li> <li> <p><code>-3</code> = An <a href="https://www.oracle.com/industries/communications/products/services-gatekeeper/" target="_blank" rel="noopener">OCSG</a> connection failure occurred</p> </li> <li> <p><code>-4</code> = Campaign expiration failure.</p> </li> <li> <p><code>-5</code> = The campaign contains invalid dates.</p> </li> <li> <p><code>-6</code> = The campaign does not exist.</p> </li> </ul> </div> |
||
|
A text string that describes the result of the operation.
|
||
|
An auto-generated ID that uniquely identifies the command in the system log. |