/mcp• ObjectDistributionListObjectId • ObjectGlobalUserObjectId • ObjectPersonalGroupObjectId Cisco Unity Connection Provisioning Interface (CUPI) API -- User Import LDAP Import A GET of an LDAP user will have a phone number. When a user is imported, an LDAP import must specify a dtmfAccessId in the payload (this is often based on the phone number). In this document, <type> in a URI refers to ldap value. Initial Configuration Before any LDAP users can be imported, the LDAP synchronization has to be set as described in the LDAP Directory Integration with Cisco Unity Connection 10.x chapter of Design Guide for Cisco Unity Connection Release 10.x available at https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/10x/design/guide/ 10xcucdgx.html. GET a List of Users That Can Be Imported GET http://<server>/vmrest/import/users/<type> Only users that are eligible for import are returned; users that are already imported are not in this list. Offset and Limit Parameters Can Be Part of the ldap Query http://<server>/vmrest/import/users/<type>?offset=x&limit=y Note the following: • Either parameter can be specified individually • If the offset exceeds the number of entries, the response is an empty list • If no limit is specified and more than 2000 results are returned, the response is an error Filter and Sort To put constraints on search results, LDAP requests support the CUPI standard filter and sort parameters. Example GET /vmrest/import/users/ldap?limit=5 HTTP/1.1 Accept: application/json User-Agent: Java/1.6.0_20 Host: cuc-install-69.cisco.com Connection: keep-alive Authorization: Basic Y2NtYWRtaW5pc3RyYXRvcjplY3NidWxhYg== Cisco Unity Connection Provisioning Interface (CUPI) API 219 Cisco Unity Connection Provisioning Interface (CUPI) API for User Account Settings Cisco Unity Connection Provisioning Interface (CUPI) API -- User Import