Accepting or rejecting device requests

What it is for

End users can request a Jabber device in the end-user portal. Each request appears in the Requests menu as a row with user, request type and status. There you decide whether the device is created.

On acceptance, EasyUC creates the device for the user. Location, package, template and phone number come from the stored request and cannot be changed in the list. On rejection, only the status is set.

The list also shows requests for pickup groups and hunt groups. These are decided in the end-user portal. The admin interface has no buttons for them.

Prerequisites

• License module cucm.
• On the active CUCM connection, under Administration → CUCM & Provisioning → CUCM Connections in Actions → End-user site, the switches Enable Enduser Local Site and Enduser Device Request are turned on. Without both switches, EasyUC hides the menu item and redirects a direct call of the page to the home page.
• Seeing the menu: ROLE_APP_VIEW_REQUEST_PAGE. Accepting and rejecting: ROLE_APP_UPDATE_REQUEST.
• Location, package and template that the end user selected in the request still exist.
• Administrators with a location restriction see only requests from users of their locations. The requested location must also belong to their locations.

Step by step: enabling requests on the connection

1. Open Administration → CUCM & Provisioning → CUCM Connections. The page is called Manage CUCM Connections.
2. In the row of the connection, click Actions → End-user site. The dialog is called End-user site.
3. Turn on Enable Enduser Local Site. Only then do the further switches appear.
4. Turn on Enduser Device Request.
5. Click Save.
6. Select this connection in the header. The Requests menu item appears in the side menu.

Step by step: reviewing a request and deciding

1. Open EasyUC Cisco → Requests. The page is called Enduser Requests and shows ten requests per page.
2. Narrow down the list. In the Status column, select the filter In pending to see only open requests.
3. If required, filter by a user in the Enduser column or by the type in the Request Type column.
4. In the Request Type column, read the details below the type: Phone number and Name show what is created on acceptance.
5. In the Enduser column, check whether the correct user is making the request. The badge LDAP or local shows the origin of the user.
6. To accept, click Accept. Read the prompt For this enduser will be added a new device with the phone number in brackets and confirm.
7. To reject, click Reject and confirm the prompt No device will be assigned to the enduser
8. Wait until the buttons disappear and the status changes to accepted or rejected.
9. After accepting, open the user profile and check the new device on the Phones & Phone numbers tab.

Fields and options

Check the result and troubleshoot

• You recognize success by the status accepted or rejected and by the entry in the Processed by column. After accepting, the device is listed in the user profile.
• The Requests menu item is missing or the page jumps to the home page: Enable Enduser Local Site or Enduser Device Request is missing on the active connection, or ROLE_APP_VIEW_REQUEST_PAGE is missing.
• The Accept and Reject buttons are missing: the request is no longer pending, it concerns a pickup group or hunt group, the user no longer exists, or ROLE_APP_UPDATE_REQUEST is missing.
• This request was already executed The request has been decided in the meantime or is outside your locations. Reload the list.
• Location not found, Package not found or Template not found The location, package or template stored in the request no longer exists or does not belong to your locations. Reject the request and create the device yourself if required.
• Error updating the enduser request: … Device creation has failed. The text after the colon names the cause, for example a phone number that is in use. The request stays pending. Before a second attempt, check in the user profile whether objects have already been created.
• After a partial failure, check existing objects first before you trigger another creation.