Problem handling calls on RP after Unity transfer http://developer.cisco.com/c/message_boards/find_thread?p_l_id=&threadId=12393863 2013-05-22T18:44:13Z 2013-05-22T18:44:13Z Stewart Ponsford http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=12437750 2013-02-27T16:16:58Z 2013-02-27T16:16:58Z

Thanks David.   This is on CUCM 7.1 and we are getting a 9.1 setup tomorrow to do more testing with. Hopefully I will avoid this issue anyway with a better behaved application, if I find anything like this on the newer release I will raise it.

Stewart Ponsford 2013-02-27T16:16:58Z David Staudt http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=12437509 2013-02-27T16:07:54Z 2013-02-27T16:07:54Z

It is important to wait for media to setup before the Redirect, and there have been some fixed issues in this area in past JTAPI/UCM releases.  However I would not expect recent versions to exhibit any confused/unrecoverable behaviour with persistant state-machine discrepencies, such as you describe, even if the Redirect comes early. If you are on a recent UCM version and would like us to investigate the problematic scenario, please open a case with CDN Developer Support and we'll take a look.  

David Staudt 2013-02-27T16:07:54Z Stewart Ponsford http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=12428747 2013-02-27T10:27:58Z 2013-02-27T10:27:58Z

Ok I think I have solved this. It appears my app was a bit too quick to issue the redirect command. I am using the RP as a route terminal, I must set the RTP up before doing the redirect. Even so it seems a little too easy to stuff up jtapi!

Stewart Ponsford 2013-02-27T10:27:58Z Stewart Ponsford http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=12393862 2013-02-26T15:59:54Z 2013-02-26T15:59:54Z

I have found that if I allow a call to flow from Unity to my Route point (unity set to supervised transfer), as long as I let the transfer from Unity complete I can then redirect the call to a phone of my choice.   If I attempt the redirect as soon as the call arrives at the RP, not only does my redirect not work - which may be fair enough as I may have supplied callid/connection details that are out of date as the transfer is occurring but I can it appears stuff up the JTapi call model.   I say this because I get a platform exception in jtapi (attempt to redirect a call that does not exist), I get a CiscoTransferStartEv but not CiscoTransferEndEv and Jtapi from then on reports both the transfer call and final call in the model even after I have cleared the external call down. The Jtapi test tool also shows the 2 hanging calls.   Any ideas? This is on CUCM 7.1

Stewart Ponsford 2013-02-26T15:59:54Z