cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
439
Views
0
Helpful
0
Comments
cdnadmin
Level 11
Level 11
This document was generated from CDN thread

Created by: Andreas Muenstermann on 14-07-2011 10:53:47 AM
Hello,
 
for a callcenter application we have to implement the following szenario:
 
A calls RP
RP accepts call and plays music
RP calls agent B
Agent B answers the call (Now we have two active calls, both in the Talking Mode)
 
Now we want to redirect or transfer or merge these two calls so that A talks to B directly, that is without beeing dropped or held before. We use the method CallControlCall.transfer(Call) to transfer the calls but we are always getting a CucmException.
 
Any Ideas how to implement this feature? Is this possible with the current JTAPI Implementation?

Subject: Re: New Message from Andreas Muenstermann in Cisco JTAPI (JTAPI) - Cisco JT
Replied by: Joseph Moskie on 14-07-2011 01:04:36 PM
> What exception are you getting? Do you have JTAPI logs for the scenario?

Subject: RE: Re: New Message from Andreas Muenstermann in Cisco JTAPI (JTAPI) - Cisc
Replied by: Abhishek Malhotra on 14-07-2011 01:14:39 PM
I believe RP support only limited set of features and functionalities and do not support feature operations like transfer, conference etc.. and thus the exception.
CTI Ports or end phones should really be used for feature operations.
 
 

Subject: RE: Re: New Message from Andreas Muenstermann in Cisco JTAPI (JTAPI) - Cisc
Replied by: Chikeobi Njaka on 09-08-2011 08:56:15 PM
I believe RP support only limited set of features and functionalities and do not support feature operations like transfer, conference etc.. and thus the exception.
CTI Ports or end phones should really be used for feature operations.
 
 

Following up on this...
I am going down the same path, but a bit differently:
1 CTI Port calls A
2 A answers
3.0 Spawn threads to use CTI RP to make calls to participants:
  3.1 RouteCallback is registered with RouteAddress on CTI RoutePoint
  3.2 CTI RP calls B
  3.3 B answers
  3.4 Route callback RouteSession object selects route
**********
This is where it ends... the RouteCallback does not get called, so the route is not selected. Any idea why the route callback is not executed?

Subject: RE: Re: New Message from Andreas Muenstermann in Cisco JTAPI (JTAPI) - Cisc
Replied by: Abhishek Malhotra on 10-08-2011 06:01:58 AM
As indicated in other thread:


RouteCallback works only for incoming calls on Route Points and not on the calls which are originated from Route Point. You may want to redirect the call on RoutePoint from application to desired CTI port once the call is answered instead of relying on RouteCallBack for outbound calls.
Getting Started

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:

Quick Links