Dear Sir,

Currently we are testing multi-cluster CTI system and we got a problem when a call is transferred from cluster-1 to cluater-2.
OCI is missing in cluster 2 events while all events in cluster 1 have OCIs. Is OCI lost over cluster?
Here is a digested log and an attached file contains full log.
CallFlow is
09065693055(outside line number)-->4991302112(VDN)-->91302112(cluster 1 extension number)--<Consult call>-->90504400(cluster 2 extension number)

>>>>>>>>>>>>>>>>>>> CLUSTER 1 Event Log <<<<<<<<<<<<<<<<<<<<<<<<<<<<

------- connectionAlerting( CallControlConnectionEvent.CALLCTL_CONNECTION_ALERTING )
eventConnectionAddress= 91302112 1, RINGING (97)
event Terminal Name = 91302112
CallControlEvent.CAUSE_REDIRECTED
Event.CAUSE_NORMAL
UCID = 10002119801711444329, TsapiCallID = 11980
callingAddress = 09065693055 1
calledAddress = 4991302112 null
lastRedirectedAddress = 4991302112 null
V7CallInfo UCID = 10002119801711444329
DistributingAddress = 4991302112 null
DistributingVDNAddress= 4991302112 null

------- connectionEstablished( CallControlConnectionEvent.CALLCTL_CONNECTION_ESTABLISHED )
eventConnectionAddress= 91302112 1, TALKING (98)
event Terminal Name = 91302112
CallControlEvent.CAUSE_NORMAL
Event.CAUSE_NORMAL
UCID = 10002119801711444329, TsapiCallID = 11980
callingAddress = 09065693055 1
calledAddress = 4991302112 null
lastRedirectedAddress = 4991302112 null
V7CallInfo UCID = 10002119801711444329
DistributingAddress = 4991302112 null
DistributingVDNAddress= 4991302112 null

******** CONSULT CALL HERE 91302112(Cluster 1) ---> 90504400(Cluster 2) *********

------- connectionEstablished( CallControlConnectionEvent.CALLCTL_CONNECTION_ESTABLISHED )
eventConnectionAddress= 91302112 2, HELD (99), TALKING (98)
event Terminal Name = 91302112
CallControlEvent.CAUSE_NORMAL
Event.CAUSE_NORMAL
UCID = 01004000481711444353, TsapiCallID = 11982
callingAddress = 91302112 2, HELD (99), TALKING (98)
calledAddress = 90504400 null
lastRedirectedAddress = null
OCI UCID = null, null
OCI UUI type = null
OCI reason = OR_CONSULTATION (1)
OCI callingDevice = 09065693055 1
OCI calledDevice = 4991302112 null

>>>>>>>>>>>>>>>>>>> CLUSTER 2 Event Log <<<<<<<<<<<<<<<<<<<<<<<<<<<<

------- connectionAlerting( CallControlConnectionEvent.CALLCTL_CONNECTION_ALERTING )
eventConnectionAddress= 90504400 1, RINGING (97)
event Terminal Name = 90504400
CallControlEvent.CAUSE_NORMAL
Event.CAUSE_SNAPSHOT
UCID = 01004000481711444353, TsapiCallID = 12784
callingAddress = 91302112 1
calledAddress = 90504400 1, RINGING (97)
lastRedirectedAddress = null

------- connectionEstablished( CallControlConnectionEvent.CALLCTL_CONNECTION_ESTABLISHED )
eventConnectionAddress= 90504400 1, TALKING (98)
event Terminal Name = 90504400
CallControlEvent.CAUSE_NORMAL
Event.CAUSE_NORMAL
UCID = 01004000481711444353, TsapiCallID = 12784
callingAddress = 91302112 1
calledAddress = 90504400 1, TALKING (98)
lastRedirectedAddress = null

Thank you for your help in advance.
Best regards,

Is a "cluster" equivilent to an Application Enablement Services server, and cluster 1 and 2 use different AE Services servers?

I don't know the answer, but by enabling TSAPI tracing, you could observe the information coming from CM to AES and get a better understanding of what is occurring. I would not be surprised to find out that OCI information is something that AE Services maintains, and by switching AE Services servers during the transfer the second AES is unaware of the OCI information that AES 1 had.

[url]https://www.devconnectprogram.com/site/global/products_resources/avaya_aura_application_enablement_services/support/faq/tsapi/index.gsp?tab=general&accordion=faq-5-collapse
[/url]

Hi John,

Thank you for your quick response and help.

Yes, cluster means AES server and I believe that both cluster 1 and 2 are the same AES servers.

Best regards,

I feel it is important to better understand what a cluster is, and then if a single AES is managing both call flows I suggest opening a ticket where we can examine the full AES TSAPI g3 and csta traces. It may be to get OCI information there is a requirement that the application was sent information about the original call, and in the tranfer to cluster 2 it never was informed about the original call, and thus OCI information is not sent, because the second cluster is not expected to be able to take advantage of it. This really requires a deeper investigation if a single AES is involved.