cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1154
Views
0
Helpful
2
Replies

Transferring calls on CTI RoutePoint

stephan.steiner
Spotlight
Spotlight

Given that CTI Routepoints can answer calls, even terminate media, how would you then connect such an inbound answered call to another call? When I try to transfer an inbound call in hold state with an outbound state in active state I'm getting the following error:

 

CTIERR_COMMAND_NOT_IMPLEMENTED_ON_DEVICE Internal callprocessing error :Device does not support the command com.cisco.jtapi.PlatformExceptionImpl: Internal callprocessing error :Device does not support the command

 

2 Replies 2

dstaudt
Cisco Employee
Cisco Employee

Generally 'route' is the operation you use to get calls from a RP to another DN, see Routing in the JTAPI dev guide.
The guide mentions redirect() is also supported for CTI RPs. Non-support for consult/transfer/conference sounds right....if you need those operations, use a CTI Port

What I’m trying to do is really routing - well forking but also plain routing (dynamically deciding on the fork destinations) to be precise. I need parallel call distribution where targets can change if the pub is down (which removes Huntgroups from the running).
CTI Ports are limited to one active call per the DEV Guide, so you’d have to have a whole group of CTI Ports, one for each forked leg. While technically doable, increased complexity generally goes right along with higher propensity to fail. Plus, to have the right caller info you’d have to chain two RPs as we previously discussed.

I think I ran into this Wall before a whopping 15 years ago. Too bad things haven’t evolved :(