EasyUC
4.8.7

EasyUC for Cisco

Restarting a CUCM service

Restart the Cisco IP Voice Media Streaming App service immediately or with a delay.

EasyUC · Version 4.8.7

In EasyUC: EasyUC Cisco → Administration → CUCM & Provisioning → CUCM Services

What it is for

The CUCM service Cisco IP Voice Media Streaming App provides music on hold (MOH), annunciator announcements and software conference bridges. New or changed MOH audio sources are often played on a server only after this service has been restarted.

On the CUCM Service Restarts page you trigger the restart from EasyUC without signing in to Cisco Unified Serviceability. You select the servers and either an immediate start or a delay of 1 to 24 hours. EasyUC performs the restart per server through the Serviceability interface of the CUCM and logs the result per server.

In this version only this one service is available for selection.

Prerequisites

  • The CUCM module is active. The menu item is in Administration and is visible to administrators.
  • The CUCM connection is set up and active. Its user may control services through Serviceability in the CUCM.
  • The CUCM servers concerned are reachable from the appliance.
  • An agreed maintenance window.

Step by step

  1. Select EasyUC Cisco at the top and check the CUCM connection in the header.
  2. Open Administration → CUCM & Provisioning → CUCM Services. The page is called CUCM Service Restarts.
  3. Click Restart Service at the top. The Restart CUCM Service window opens.
  4. Under Service Name, select the entry Cisco IP Voice Media Streaming App.
  5. Under Nodes, select one or more CUCM servers.
  6. Under Restart In, select either Now for immediately or +1 hours to +24 hours.
  7. Click Save. The job appears in the list.
  8. To cancel a scheduled restart, click Stop under Actions in the row. This is only possible while the job is still pending.

Fields and options

Fields and options
Field / actionMeaning and use
Service NameService to be restarted. Only choice: Cisco IP Voice Media Streaming App.
NodesCUCM servers of the cluster on which the service is restarted. Multiple selection.
Restart InNow or a delay of 1 to 24 hours in steps of one hour. Default: Now.
NameColumn of the list: name of the service.
Restart StatusOverall status of the job: Pending, Running, Success, Success Partial, Error or Restart Stopped. After completion, Node, Status, Timestamp and, in case of an error, the error text are shown per server below it.
Restart In/AtScheduled time. For immediate jobs, the time the job was created.
StopCancels a pending job.

Check the result and narrow down errors

  • Success: Restart Status shows Success and, per server, the status Success with a timestamp. Then check with a test call put on hold whether music on hold is playing.
  • Success Partial: the restart failed on at least one server. The row of the server names the reason under Error.
  • Error on all servers: check that the servers are reachable and that the user of the CUCM connection has the permission for Serviceability.
  • Restart Stopped: the job was cancelled with Stop before it was executed.
  • A job stays on Pending although the time has been reached: check the background jobs of the appliance.
  • A service restart is not a first measure for unclear AXL, CTI or network errors.

Related chapters