Created by: Chikeobi Njaka on 11-08-2011 04:34:02 PM Hi Gang, This is part of an earlier thread, but I think it deserves a new posting... Scenario is as follows: 1. CTI Route Point makes a call 2. Call is answered 3. RTP Params are set on the connection 4. Call is redirected to a CTI Port address It seems the redirection "works" in as much as there is no exception thrown. The call is disconnected and a new connection is established (the call observer placed on the redirect destination says as much). The problem is as follows: * Immediately after the call is established, it is promptly disconnected * For the redirect, I indicate that I want it to change the called party to the address of the redirect destination (Cisco's redirect(...) overload). This does not seem to be the case from the values seen in the CallCtlConnEstablishedEv object. Any ideas about redirecting a call that has been answered? JTAPI 1.2 indicates that transfer can only happen if the connection is in the offering state, while Cisco's enhancement indicates that it can be done even when the connection has been established. Any help willbe greatly appreciated.
Subject: RE: CTI Route Point Redirect Disconnect Replied by: Chikeobi Njaka on 11-08-2011 06:36:58 PM The CTI port is registered by the application before it is used to make the first outbound call. I call CiscoMediaTerminal.register on the CTI port after it has been created on by the JTAPI provider (I do dynamic association of devices by calling createTerminal() instead of getTerminal()). So the first outbound call works fine. It's just when I try to redirect a second call (make from a CTI Route Point) to another DN on the CTI port that I get the disconnection. Since CTI port can only have one active call at a time, I don't have to set RTP each time a call comes to it, do I? As for the CTI Route Point, when I make the outbound call from it, I set RTP Params as soon as I get the CiscoMediaOpenLogicalChannelEv gets thrown.
Subject: RE: CTI Route Point Redirect Disconnect Replied by: Abhishek Malhotra on 11-08-2011 05:16:56 PM The redirect destination "CTI Port" - how is it registered? In static mode or dynamic? If it is dynamic, are you setting RTP Parameters on it?
Subject: RE: CTI Route Point Redirect Disconnect Replied by: Abhishek Malhotra on 11-08-2011 06:58:27 PM Application needs to set rtp parameters everytime it gets CiscoMediaOpenLogicalChannelEv For each call, whenever it gets connected you will get this event when application needs to provide rtp parameters so that media can be established.
Subject: RE: CTI Route Point Redirect Disconnect Replied by: Chikeobi Njaka on 12-08-2011 10:35:09 AM Hi Abhishek, So, the problem is that for the redirect from the CTI route Point to the CTI port, the CiscoMediaOpenLogicalChannelEv never gets thrown. The CTI port is initially registered (I guess that's what you call static registration?), while the CTI route point is dynamically registered via the CiscoMediaOpenLogicalChannelEv event. So, same problem. One question: In setting up RTP params on the CTI route point, I don't set the MediaCapabilities. Would that be a problem and if so, how do you set it in the context of the CiscoMediaOpenLogicalChannelEv event?
Subject: RE: CTI Route Point Redirect Disconnect Replied by: Abhishek Malhotra on 13-08-2011 12:24:52 PM
Hi Abhishek, So, the problem is that for the redirect from the CTI route Point to the CTI port, the CiscoMediaOpenLogicalChannelEv never gets thrown. The CTI port is initially registered (I guess that's what you call static registration?), while the CTI route point is dynamically registered via the CiscoMediaOpenLogicalChannelEv event. So, same problem. One question: In setting up RTP params on the CTI route point, I don't set the MediaCapabilities. Would that be a problem and if so, how do you set it in the context of the CiscoMediaOpenLogicalChannelEv event?
If you specifiy InetAddress and port at the time of registration it is referred as static registration, while if you specify these at the time of getting CiscoMediaOpenLogicalChannelEv it is referred as dynamic registration. MediaCapabilities include the supported codecs for the end point as defined on com.cisco.jtapi.extensions.CiscoMediaCapability You need to specify IP Address and port at the time of getting CiscoMediaOpenLogicalChannelEv as part of CiscoRTPParams so as to tell the far end where to stream media packets once the call is answered. If this is not specified call could fail
Subject: RE: CTI Route Point Redirect Disconnect Replied by: Abhishek Malhotra on 20-02-2012 06:01:09 PM You can get RTP handle by using getCiscoRTPHandle() API, once you have rtpHandle, you can invoke getCall() API on CiscoProvider to get corresponding CiscoCall object, this will give you access to corresponding call object from which you get required info.
Subject: RE: CTI Route Point Redirect Disconnect Replied by: Gionata Navarra on 20-02-2012 10:25:55 AM Hi all,
I'm trying to realize multiple redirections on the same CTI Route Point with CUCM 8.6, and it works fine catching CiscoMediaOpenLogicalChannelEv and then setting RTPParams on CTI RP. The problem is when I try to use the same CTI RP with multiple calls ringing (CTI is calling many phones at the same time); I catch CiscoMediaOpenLogicalChannelEv when first phone answers the call, but I'm not able to understand which number answered the call, because from termEv CiscoMediaOpenLogicalChannelEv I can get only number of CTI RP calling, not the number called from it. Is there a way to understand second number involved in the call from that terminal event or from another event binded to CiscoMediaOpenLogicalChannelEv?
Gnav
Subject: RE: CTI Route Point Redirect Disconnect Replied by: Gionata Navarra on 29-02-2012 03:40:31 AM It works. thank you.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:
