Rajesh,
Ah, Thank you. I specify the trigger param "To" and now it finally
triggers the app.
Sou
From: Rajesh Vargheese (rvarghee) mailto:rvarghee@cisco.com
Sent: Friday, January 30, 2009 2:17 PM
To: Sou Vang; cuae-developers@developer.cisco.com
Subject: RE: [Cuae-developers] Metreos.CallControl.IncomingCall for
conferencing?
Sou, You define the trigger for your application as
Metreos.CallControl.IncomingCall. Since the call comes to you through
the CTI route point, your application will be triggered.
In addition, you can specify a trigger param 'To' if you want to be
restrictive.
Thanks,
Rajesh
________________________________
From: Sou Vang mailto:svang@midwave.com
Sent: Friday, January 30, 2009 2:11 PM
To: Rajesh Vargheese (rvarghee); cuae-developers@developer.cisco.com
Subject: RE: [Cuae-developers] Metreos.CallControl.IncomingCall for
conferencing?
Rajesh,
That's exactly what I want to do. I already have the CTI routepoint
setup and ready to go. The question is, when Phone A dials 6xxxx, how
does it trigger my app in CUAE? What steps do I need to take for my app
to be trigger?
Thanks,
Sou
From: Rajesh Vargheese (rvarghee) mailto:rvarghee@cisco.com
Sent: Friday, January 30, 2009 2:05 PM
To: Sou Vang; cuae-developers@developer.cisco.com
Subject: RE: [Cuae-developers] Metreos.CallControl.IncomingCall for
conferencing?
Sou, If you want to use 1st party call control, in this case you would
have to do some extra work. Let me pick a scenario and explain.
You have configured Phone A (1000), Phone B (1001) and a route pattern
6xxxx. You would have to create an application that does in-out calls
(in through your CTI routepoint and out using a CTI port) (or equivalent
in other protocols)
In this case, instead of dialing 1001 from Phone A, you would have to
dial 61001. Since it matches your pattern, it will be route to the CUAE
and you application will be triggered. In you application, you would
strip out the leading digit and use to make an outbound call. Now,
Phone B will start ringing.
Let me know if you have any questions.
Thanks,
Rajesh
________________________________
From: Sou Vang mailto:svang@midwave.com
Sent: Friday, January 30, 2009 1:58 PM
To: Rajesh Vargheese (rvarghee); cuae-developers@developer.cisco.com
Subject: RE: [Cuae-developers] Metreos.CallControl.IncomingCall for
conferencing?
Rajesh,
I have decided to go instead with using CallControl.IncomingCall instead
of JTapi.JTapiIncomingCall.
I have define a route patter and already associated with a trunk. Also
define a CTI routepoint and I verify that it is registered in CUAE so
CUAE is able to see it.
When I call the end phone (i.e. 7000) still, how does that trigger the
my app? Where do I set that setting?
Thanks,
Sou
From: Rajesh Vargheese (rvarghee) mailto:rvarghee@cisco.com
Sent: Tuesday, January 27, 2009 3:15 PM
To: Sou Vang; cuae-developers@developer.cisco.com
Subject: RE: [Cuae-developers] Metreos.CallControl.IncomingCall for
conferencing?
Sou, I see your point of confusion now. When Phone A calls Phone B (and
is not monitored), CUAE is not at all involved in it. CUCM takes care of
routing the call between the phones. Since it doesnot come to the CUAE,
your app will not be triggered. To bring the call to CUAE, you can use
more than one method.
Define a route pattern and associate it with a trunk.
Defined a CTI routepoint and make the call to that endpoint. (something
like an in-out call)
Add the terminating end phone in a monitored device pool. (You will get
a JTapiIncomingCall)
Let me know if you need further information.
Thanks,
Rajesh
________________________________
From: Sou Vang mailto:svang@midwave.com
Sent: Tuesday, January 27, 2009 3:03 PM
To: Rajesh Vargheese (rvarghee); cuae-developers@developer.cisco.com
Subject: RE: [Cuae-developers] Metreos.CallControl.IncomingCall for
conferencing?
Thanks Rajesh that makes more sense of the 2 different triggers.
Right now I am not getting anything in the log files because it seems
like the app is not triggering.
So right now, I am using CallControl.IncomingCall as the triggering
event and my app is very simple with only one method and right now
it's not reaching this method.
@Override
public void incomingCall(String sessionId, IncomingCallOptions
options)
{
System.out.println("Inside incomingCall() callId : " +
options.getCallId());
}
I have two phones that I want to test (PhoneA & Phone
. When PhoneA
calls PhoneB, how does that trigger the CallControl.IncomingCall event
to run the app?
My plan is that once incomingCall() gets called, I can grab the callId
and create a conference then join the two phones in the conference.
Does that sound correct to creating a conference call?
Sou
From: Rajesh Vargheese (rvarghee) mailto:rvarghee@cisco.com
Sent: Tuesday, January 27, 2009 2:34 PM
To: Sou Vang; cuae-developers@developer.cisco.com
Subject: RE: [Cuae-developers] Metreos.CallControl.IncomingCall for
conferencing?
Sou, Here are the answers to your questions
1. What is the difference between CallControl.IncomingCall &
JTapi.JTapiIncomingCall?
CallControl.IncomingCall is a first party call control API. It can be
used with protocols like skinny, H323, SIP, JTAPI (first party)
JTapi.JTapiIncomingCall is a third party call control API. Only
supported by JTAPI.
2. In what situation would you use CallControl.IncomingCall or
JTapi.JTapiIncomingCall?
If you want to monitor (listen to events as a 3rdparty) a call, you
would be using JTapi.JTapiIncomingCal. If you want to do first party
call control and want to have the choice of protocols, you can use
CallControl.IncomingCall
3. If using CallControl.IncomingCall, what device pool would be
created to add the ip phone's MAC address in to monitor?
If you are using CallControl.IncomingCall, you are doing first party
call control, you dont have add any device to the monitored device pool.
You can use CTI ports to make first party calls. You add them to device
pool.
You can create a conference app with the CallControl.IncomingCall. Can
you let us know the specifics (log files) of the problem that you are
facing.
Thanks,
Rajesh
________________________________
From: cuae-developers-bounces@developer.cisco.com
mailto:cuae-developers-bounces@developer.cisco.com On Behalf Of Sou
Vang
Sent: Tuesday, January 27, 2009 2:26 PM
To: cuae-developers@developer.cisco.com
Subject: [Cuae-developers] Metreos.CallControl.IncomingCall for
conferencing?
Hello,
I have a few questions about this triggering event and hopefully get
some help.
1. What is the difference between CallControl.IncomingCall &
JTapi.JTapiIncomingCall?
2. In what situation would you use CallControl.IncomingCall or
JTapi.JTapiIncomingCall?
3. If using CallControl.IncomingCall, what device pool would be
created to add the ip phone's MAC address in to monitor?
I'm trying to create a conference app using java but can't find any
resources except an example in Designer. I am trying to follow the
Designer example and implementing in java but am running into some
difficulties because it seems like the app is not triggering. In the
example, it uses CallControl.IncomingCall as a triggering event and I
have a method override incomingCall() with a print statement but it
seems like it never made it in there.
Can someone tell me if I'm in the right direction of creating a
conference app or heading the wrong direction?
Thanks,
Sou
_______________________________________________
Cuae-developers mailing list
Cuae-developers@developer.cisco.com
Attachment not added (content type not allowed): "att1.html"
Cisco Unified Application Environment Developer Forums 
