Cisco Actions

Cisco has 3 different types of Actions:

1. Phone Services

2. Phone Services Dialer

3. Dial Monitor

4. Call Manager

Get Cisco Actions

Retrieve all Cisco actions by issuing a GET on the below URL

This will return a collection of Actions objects which could be a mix of the above-mentioned Action types.

The above will return a specific Action with Id.

[Note: Query filters may be applied on the Actions object. Refer to Query Methods portion of the document for more information]

The following API calls are deprecated and redirected to a different URL as specified below

 

Add or Update Cisco Actions

Phone Service Actions Object

Name (required)	The name of action you are creating.
Site	Provide a Site (name) to associate the action. A null or empty string for Site defaults the action to AllSites, i.e. The action will be available to all Sites configured in Revolution.
URL	This is not a create or update property but will be provided on all GET of an action. This is a dynamically generated callback URL to trigger this action.

 

Actions may be added/updated in collections of Actions objects.

Example Request

• This POST request adds one new PhoneService and updates another existing PhoneService (Note: the object with ‘Id’)

Example Response

 

Phone Service Dialer Actions Object

Name (required)	The name of action you are creating.
Site	Provide a Site (name) to associate the action. A null or empty string for Site defaults the action to AllSites, i.e. The action will be available to all Sites configured in Revolution.
Extension	Dial an extension directly
URL	This is not a create or update property but will be provided on all GET of an actions. This is a dynamically generated callback URL to trigger this action.

Actions may be added/updated in collections of Actions objects.

Follow the same example as provided for PhoneService

 

Cisco Dial Monitor Actions Object

Name (required)	The name of action you are creating.
Site	Provide a Site (name) to associate the action. A null or empty string for Site defaults the action to AllSites, i.e. The action will be available to all Sites configured in Revolution.
MonitoredNumber (required)	Enter specific number to monitor or use ? and * wildcards (?11 matches 911 and 411; 2* matches any number dialed beginning with 2)
CallingDNPattern	Enter specific phone to call from or use ? and * wildcards (207? matches monitored number dialed from phones in 207x range; 20* matches monitored number dialed from phones beginning with 20). Leave blank to include all.
CallingSearchSpace	Only monitor numbers called from this search space. Leave blank to include all.
Partition	Only monitor numbers called from this partition. Leave blank to include all.
DevicePool	Only monitor numbers called from this device pool. Leave blank to include all.

Actions may be added/updated in collections of Actions objects.

Follow the same example as provided for PhoneService

Cisco Call Manager Action Objects

Name (required)	The type of action you are creating. (See below for list of valid actions.)
IPAddress (required)	IP address for the CUCM.
Username (required)	Username for the CUCM account.
Password (required)	Password for the CUCM account.
Version (required)	Call Manager Version number.
PreferenceOrder (optional)	Preference order for the CUCM.

One or more Cisco call managers may be added using the URL below.

Example Request

• This POST request adds two Cisco Call Managers.

Delete Cisco Actions

Delete Cisco Actions by sending a collection of Ids of actions that need to be deleted. The Ids could be a collection of mix of the above mentioned types of Cisco Actions.

Example Request

• This POST deletes actions with below IDs.