Stewart Ponsford:
I thought rather than simply using CTI route points as a device to receive new calls and route to media terminals to provide in queue messaging I could use the route point to do the in queue messaging then perrform a redirect.
I think pure RP routing is flawed in regards of capacity. AFAIR route point can't have more than 20 something calls on it.
the doc stats one app (I presume this really means once provider handle) cannot registerRouteCallback and terminate media?
No, you don't need RouteCallBack. You have to issue CallControlConnection.accept() request "manually" from your java code. There is also CiscoAddress.setAutoAcceptStatus() interface in CUCM 8.x, not sure about 7.
As for media doc states the following:
Terminating media comprises a three-step process.
Step 1 The application registers its media capabilities with this terminal by using the CiscoRouteTerminal.register method.
Step 2 An application adds an observer that implements CiscoTerminalObserver interface by using the Terminal.addObserver method. Step 3 The application must add addCallObserver on CiscoRouteTerminal or on CiscoRouteAddress to receive CiscoCall object from the provider by using CiscoRTPHandle.
Probably you should register with DYNAMIC_MEDIA_REGISTRATION option and follow the procedure - respond to CiscoMediaOpenLogicalChannelEv, set up ip address&port and provide media.
AFAIK static media termination doesn't work for route points.