The Cisco Call Control APIs have recently been updated with the latest release of the Add-on. If you have not updated your Add-on I suggest you do that before proceeding. With this update, we have made it much simplier to use these APIs by making the service a system service. If you are currently using the Call Control APIs there is a few changes that need to be made in order for your code to work in releases after 9.2.3 load.

Now to talk about the changes that have been put in place. The bulk of Cisco Telephony Manager has not changed. A huge portion of the methods will be used in the same way but instead of having a handler to get back the Cisco Telephony Manager when it connects, we can instead just call it. Below is a little snippet of code showing how to do just that.


After this is done, you can immediately go into adding call listeners or any other method that you are trying to do on the device. If you want more examples of how this works, feel free to look at the samples that have been included in the Add-on.

Unfortunately, the old way of connecting to the Cisco Telephony Manager using the CiscoTelephonyManager.jar will no longer work in loads after 9.2.3 and this new way will not work in loads before 9.2.3. If for some reason you need it to work in both loads you have two choices. You can either bind to the ICCDevice or use the conversion jar included in the add-on. For more information on how to use the way of binding to the ICCDevice please take a look at the Developer Guide under the Telephony section. If you are wanting to use the conversion jar it is included in the Add-on in the extras folder with a document explaining how to use it.