Installation Instructions for the Phone Push CRS (IPCC Express) Step
-----------------------------------------------------------------------

For detailed information on custom CRS Steps, download the CRA (also known as CRS and IPCC Express) SDK 
from the Cisco Developer Support site:

             http://www.cisco.com/go/developersupport

Just as with this IP Phone Services SDK, you will need to login with a cisco.com account in order
to gain access to the download.

Follow the instructions in the SDK document for integrating custom Steps and Subsytems into the CRS Editor and Engine.


The exact details may vary by CRS (IPCC Express) version, but in general, you will do the following:

1) Merge the entries from the provided customeditor_changes.xml and customengine_changes.xml files into
   the customeditor.xml and customengine.xml files in your CRS \wfavvid directory. This applies to both
   the Editor (client) and Engine (server) installs.
2) Copy the ipphoneservices.properties, CiscoIPPhoneSDK.jar and CiscoIPPhoneSDK_WFAPI.jar files to the 
   same \wfavvid directory
3) Edit the ipphoneservices.properties file and fill in the necessary config info.
4) Stop and restart the CRS Engine - you should now see a Subsystem named 'IP Phone Services'. 
   Assuming your properties file is correct, you'll see the Subsystem go IN_SERVICE.
5) Open up the Workflow Editor and you'll see a new category called "IP Phone Services" which contains
   a new step called PhonePush. The step will allow you to push to a phone by either devicename (SEPxxxxx)
   or by extension and is configurable by going into the step properties.
6) In order for push by extension to work, you must have meet requirement (A), and in order for push by extension to work
   you must meet requirments (A) and (B):
   A) All users have their phones configured as Associated Devices (each User should only have one phone associated)
   B) All users have a Primary Extension defined under Associated Devices and multiple users must NOT have the same 
      Primary Extension. This is necessary because the subsystem derive's the destination phone by mapping
      Primary Extension -> User -> Controlled Devices.


A sample script, test.aef, using the PhonePush Step is included for testing purposes.