Difference between revisions of "MOR API device create"

From Kolmisoft Wiki
Jump to navigationJump to search
Line 17: Line 17:
** hash - 632667547e7cd3e0466547863e1207a8c0c0c549
** hash - 632667547e7cd3e0466547863e1207a8c0c0c549
** description - string
** description - string
** pin - [number. '']. If pin param not send -> random_numbers  
** pin - [number. '']. If pin param not send -> random_numbers . If blank -> pinless
** type - Device type [SIP, IAX2, FAX, Virtual,H323, ZAP, Skype, '']. When is '' -> default device type. If default device type is empty -> 'SIP'
** type - Device type [SIP, IAX2, FAX, Virtual,H323, ZAP, Skype, '']. When is '' -> default device type. If default device type is empty -> 'SIP'
** devicegroup_id - device group ID  
** devicegroup_id - device group ID  

Revision as of 12:02, 8 November 2011

This functionality is available from MOR 11


MOR API Create device






  • Call: /api/device_create
  • Methods: POST, GET(if allowed, not recomended)
  • Params:
    • user_id - User ID in MOR database, whose datas we want to delete. Required.
    • u - username to login. Required.
    • p - password to login. Required.
    • hash - 632667547e7cd3e0466547863e1207a8c0c0c549
    • description - string
    • pin - [number. ]. If pin param not send -> random_numbers . If blank -> pinless
    • type - Device type [SIP, IAX2, FAX, Virtual,H323, ZAP, Skype, ]. When is -> default device type. If default device type is empty -> 'SIP'
    • devicegroup_id - device group ID
  • Returns:
    • Success
      • <status>Device was created</status>
    • Errors:
      • <error>User was not found</error> - User was not found using user_id. Use correct user id.
      • <error>Incorrect hash</error> - Hash was not correct. Check API_Secret_Key and order or params while concatenating hash_string.
      • <error>Dont be so smart</error> - User with UNIQUEHASH not found or params id not send. Enter correct id.
      • <error>Device was not created</error>
        • <message>problem message</message>