JTAPI event order

I have a call between to parties A and B.  B consults to a route point C.  Sometimes we get what jtapi events out of order.  We get CallCtlConnOfferedEv on the route point before we even get Held on the main call.

We expect this order, more or less:

1. CallCtlTermConnHeldEv B on orig call
2. ConnCreatedEvent B on consult call
3. CallCtlConnOfferedEv C on consult call

But sometimes we get:

1. CallCtlConnOfferedEv C on consult call
2. CallCtlTermConnHeldEv B on orig call
3. ConnCreatedEvent on B on consult call

Is this acceptable behavior from CUCM/JTAPI?  Under what type of circumstance might this unusual order occur?

Answer:

Though the first event set is desirable, we do see the second event set due to distributed nature of CUCM. Some of the causes are:

1. Location of nodes where B and C are registered relative to the CTIManager node where application is connected.

2. Load on the nodes and latency between the nodes.