Multiple connection id’s on a conversation

In AACC 6.3 SP10 when a inbound call (queued to skillset) is answered by an agent we have two connection id’s. I am attaching bellow a soap request-response to have a more clear view on what i am referring to:

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<ns2:GetConnectionsRequest xmlns:ns2="http://www.nortel.com/soa/oi/cct/types/ContactService" xmlns="http://www.nortel.com/soa/oi/cct/types" xmlns:ns3="http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-BaseFaults-1.2-draft-01.xsd" xmlns:ns4="http://schemas.xmlsoap.org/ws/2003/03/addressing" xmlns:ns5="http://www.nortel.com/soa/oi/cct/notification" xmlns:ns6="http://www.nortel.com/soa/oi/cct/faults">
<ns2:ssoToken>
<token>7a980703-2104-47ce-bd6f-fedcc0c2becf</token>
</ns2:ssoToken>
<ns2:contact>
<contactId>9fb15681-58c4-4c88-8ff0-cc4e0c554bc8</contactId>
</ns2:contact>
</ns2:GetConnectionsRequest>
</soap:Body>
</soap:Envelope>


<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<ns2:GetConnectionsResponse xmlns:ns2="http://www.nortel.com/soa/oi/cct/types/ContactService" xmlns="http://www.nortel.com/soa/oi/cct/types" xmlns:ns3="http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-BaseFaults-1.2-draft-01.xsd" xmlns:ns4="http://schemas.xmlsoap.org/ws/2003/03/addressing" xmlns:ns5="http://www.nortel.com/soa/oi/cct/faults">
<ns2:connection>
<connectionId>1fcd7e35-a367-4f4a-a2a7-70a320c4c8d0</connectionId>
</ns2:connection>
<ns2:connection>
<connectionId>936c8510-2b46-4932-8731-572d83342c58</connectionId>
</ns2:connection>
</ns2:GetConnectionsResponse>
</soap:Body>
</soap:Envelope>


1fcd7e35-a367-4f4a-a2a7-70a320c4c8d0 -> This connection id is the client (<addressType>OUT_OF_PROVIDER</addressType>)
936c8510-2b46-4932-8731-572d83342c58 -> This connection id is the agent (<addressType>AGENT</addressType>)


In AACC 7.x we have 4 connection id’s in a conversation between a client and an agent. This is generating problems in our CTI implementation. I am attaching bellow details to have a more clear view on what i am referring:


<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<ns2:GetConnectionsRequest xmlns:ns2="http://www.nortel.com/soa/oi/cct/types/ContactService" xmlns="http://www.nortel.com/soa/oi/cct/types" xmlns:ns3="http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-BaseFaults-1.2-draft-01.xsd" xmlns:ns4="http://schemas.xmlsoap.org/ws/2003/03/addressing" xmlns:ns5="http://www.nortel.com/soa/oi/cct/notification" xmlns:ns6="http://www.nortel.com/soa/oi/cct/faults">
<ns2:ssoToken>
<token>1f8d0f1b-d91a-45ad-ab88-3cbabc9e18b3</token>
</ns2:ssoToken>
<ns2:contact>
<contactId>d3f18ad0-afa6-4744-b8ab-c1a6941718ac</contactId>
</ns2:contact>
</ns2:GetConnectionsRequest>
</soap:Body>
</soap:Envelope>


<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<ns2:GetConnectionsResponse xmlns:ns2="http://www.nortel.com/soa/oi/cct/types/ContactService" xmlns="http://www.nortel.com/soa/oi/cct/types" xmlns:ns3="http://docs.oasis-open.org/wsrf/2004/06/wsrf-WS-BaseFaults-1.2-draft-01.xsd" xmlns:ns4="http://schemas.xmlsoap.org/ws/2003/03/addressing" xmlns:ns5="http://www.nortel.com/soa/oi/cct/faults">
<ns2:connection>
<connectionId>33316221-6b7a-4140-b6d6-340ff9b853df</connectionId>
</ns2:connection>
<ns2:connection>
<connectionId>63813c6f-4818-44ff-9c83-3b690897745e</connectionId>
</ns2:connection>
<ns2:connection>
<connectionId>6fb7bb09-85c6-457d-9abd-7685fea632d1</connectionId>
</ns2:connection>
<ns2:connection>
<connectionId>112c6656-469f-4a59-b5f4-6246e1fa21e1</connectionId>
</ns2:connection>
</ns2:GetConnectionsResponse>
</soap:Body>
</soap:Envelope>


6fb7bb09-85c6-457d-9abd-7685fea632d1 -> This connection id is the agent (<addressType>AGENT</addressType>)
112c6656-469f-4a59-b5f4-6246e1fa21e1 -> This connection id is the client (<addressType>OUT_OF_PROVIDER</addressType>)
33316221-6b7a-4140-b6d6-340ff9b853df -> This connection id is the route point(<addressType>ROUTE_POINT</addressType>), something that we don’t have in AACC 6.3 SP10
63813c6f-4818-44ff-9c83-3b690897745e -> This connection id is the treatment (<addressType>TREATMENT</addressType>), also not present in AACC 6.3 SP10.

The question here is if this additional connections id’s are mandatory or if there is a configuration that can be made on AACC 7.x side in order to have similar data/information available as in AACC 6.3 SP10?

That's a little involved for me to tackle as a forum question; I'd need to look into the variables involved. I don't expect those to enumerate differently on the two versions and thus, my initial speculation is that we have a difference in the deployments that is causing it. My off-the-cuff response would be, we don't specify what the connections will be for any particular contact and thus, it is unsuitable to depend on any specific arrangement of them.

Open a support ticket if you need more and we can look at the details.