topic JTAPI event order in Call Control

JTAPI event order

derrickgunter — Tue, 30 Jun 2015 20:00:35 GMT

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:

CallCtlTermConnHeldEv B on orig call
ConnCreatedEvent B on consult call
CallCtlConnOfferedEv C on consult call

But sometimes we get:

CallCtlConnOfferedEv C on consult call
CallCtlTermConnHeldEv B on orig call
ConnCreatedEvent on B on consult call

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

Thanks!

Re: JTAPI event order

mpotluri — Tue, 30 Jun 2015 22:27:48 GMT

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.

Re: JTAPI event order

derrickgunter — Wed, 01 Jul 2015 17:54:07 GMT

Thanks Mohan!