CUCM API's to Replace CUAE Trigger on JTapiCallEstablished in CUAE

Document created by cdnadmin on Jan 25, 2014
Version 1Show Document
  • View in full screen mode
This document was generated from CDN thread

Created by: Tracy Laughton on 06-03-2013 10:14:31 AM
Hello,
 
We have a CUAE application that we need to replace since the CUAE is end of life.  We have been told by Cisco that we can use Call Manager API's to replace the functionality in our application, but we are not sure how to proceed.
 
Our CUAE trigger application does the following:
  - Triggers on Metreos.Providers.JTapi.JTapiCallEstablished
  - Triggers when "to" number (defined in Trigger Parameters) is a specific 5 digit number
When jTapiCallEstablished is called, the following information is extracted from JTapiCallEstablishedOptions and passed to another application:
        To
        JTapiCallId
        DeviceName (for mac number)
        From
   
Does anyone have any suggestions for how to replace this using Call Manager API's, or which API's to look at?
 
Thanks,
Tracy.

Subject: RE: CUCM API's to Replace CUAE Trigger on JTapiCallEstablished in CUAE
Replied by: Nabhonil Sinha on 06-03-2013 10:16:48 PM
Hi Tracy, You can write a simple JTAPI based Java application to achieve the similar thing. I would suggest to look into the following developer forum for JTAPI. http://developer.cisco.com/web/jtapi/home Thanks Nabhonil  
Tracy Laughton:
Hello,   We have a CUAE application that we need to replace since the CUAE is end of life.  We have been told by Cisco that we can use Call Manager API's to replace the functionality in our application, but we are not sure how to proceed.   Our CUAE trigger application does the following:   - Triggers on Metreos.Providers.JTapi.JTapiCallEstablished   - Triggers when "to" number (defined in Trigger Parameters) is a specific 5 digit number When jTapiCallEstablished is called, the following information is extracted from JTapiCallEstablishedOptions and passed to another application:         To         JTapiCallId         DeviceName (for mac number)         From     Does anyone have any suggestions for how to replace this using Call Manager API's, or which API's to look at?   Thanks, Tracy.


Subject: RE: CUCM API's to Replace CUAE Trigger on JTapiCallEstablished in CUAE
Replied by: Peter Gits on 07-03-2013 12:57:00 AM
Tracy Laughton:
Hello,
 
We have a CUAE application that we need to replace since the CUAE is end of life.  We have been told by Cisco that we can use Call Manager API's to replace the functionality in our application, but we are not sure how to proceed.
 
Our CUAE trigger application does the following:
  - Triggers on Metreos.Providers.JTapi.JTapiCallEstablished
  - Triggers when "to" number (defined in Trigger Parameters) is a specific 5 digit number
When jTapiCallEstablished is called, the following information is extracted from JTapiCallEstablishedOptions and passed to another application:
        To
        JTapiCallId
        DeviceName (for mac number)
        From
   
Does anyone have any suggestions for how to replace this using Call Manager API's, or which API's to look at?
 
Thanks,
Tracy.

 
Nabhonil is correct, I did this last month where I had started with the CUAE and migrated quickly over to the JTAPI interface after learning it was going away.  There is an example application that allows you to monitor - be an observer of a call, there are two steps you must follow, one is configuring the call manager to allow your "application" to have access as an observer, the second is making sure that the JTAPI service is running.  I would assume that it is already running.
You will need to configure this application as a daemon process, if you need further guidance on how to do this I am happy to provide additional guidance, you are looking for makecall.java which you can piece together to get working properly.  I believe this is in the sample apps under the JTAPI directory.  Even though it allows you to make calls, it also allows you to listen to other calls.
 
Cheers,
 
Peter Michael Gits
pgits@geekgaps.com 
 
 

Attachments

    Outcomes