MOR API did device unassign

MOR API DID unassign Device

Call: /api/did_unassign_device
Methods: POST, GET(if allowed, not recomended)
Params:
- did - DID number to be created Required.
- u - username to login. Required.
- p - password to login. Required.
- hash - SHA1 hash constructed using params and API_Secret_Key ( More described in Constructing hash). Required.
Returns:
- Success
  - <status>Device was unassigned from DID</status>
- Errors:
  - <error>Incorrect hash</error> - Hash was not correct. Check API_Secret_Key and order or params while concatenating hash_string.
  - <error>Don't be so smart</error> - Only Admin, Accountant or Reseller may use API.
  - <error>Device was not found</error> - Enter existing Device ID.
  - <error>You are not authorized to manage DIDs</error> - If Accountant or Reseller is using API, they should have all permissions to perform specified actions.
  - <error>Invalid DID specified</error> - Enter a valid and existing (numeric) DID number.
  - <error>Your are not authorized to use this DID</error> - Specified DID is not available to this user.
  - <error>DID is terminated</error> - DID is terminated and cannot be used.
  - <error>DID is already free</error> - No Device is currently assigned to this DID.
  - <error>DID is assigned to dialplan</error> - DID is assigned to a Dial Plan.
  - <error>Failed to unassign DID</error>

Request

Example:
- We have API Secret Key = secret
- Converted Hash string like "e5e9fa1ba31ecd1ae84f75caaa474f3a663f05f4"
We send:
- http://123.123.123.123/billing/api/device_create/u=admin&p=password&did=123456789&hash=e5e9fa1ba31ecd1ae84f75caaa474f3a663f05f4
We get:

           <page>
                 <status>Device was unassigned from DID</status>
           </page>

           <page>
                 <status>Device was unassigned from DID</status>
           </page>

* Note that username and password are not included in hash