Non deterministic single-step-transfer with internal addresses

[snu]

Hi,

I'm trying to apply a single step transfer to a call and I'm experiencing non deterministic results while several internal terminals involved. 

I'm simply invoke the "transfer" method on a call and I'm getting randomly different behavior when another internal address involved. When two external addresses involved it work every time.

As I'm triggering the transfer method of a call and the only parameter is destination address, I don't get what I'm missing here.
Note : The other internal address is a real externally accessible address in international number format.

Is there any other way to trigger single step transfer or choose to appropriate surviving source address ?

Thank for your support !

PS: I'm using CUCM v12.5

[Alex Stevenson]

Hello @snu,

I've found the Troubleshooting Guide for Cisco Unified Communications Manager, Release 12.5(1) has troubleshooting for handling transfers under the Call Park section.

By the way, your question was very clear and the image and version number are really helpful!

Hope this helps!

[snu]

Hi @Alex Stevenson,

Thank you for your reply.
Unfortunately it didn't help as there nothing related to my case in the troubleshooting documentation.

The issue occur when using single step transfer.

Can you explain the behavior of JTAPI Api ?

One additional information is the software who control the transfer request has control over the two terminals.

Can you elevate this to the development team ?

Thank you in advance !

[dstaudt]

Can you provide some details about the observed vs. expected behaviours in working vs. non-working scenarios?  Please be as specific as possible about phone models, DNs involved, gateways/trunks in the scenario, call leg steps and JTAPI objects/methods/events called/anticipated at each step.
Not sure it should matter, but can you elaborate more on the target internal address that is 'really an external address?'