Got it. Thanks Wilson for your response.
This would mean I cannot use anything involving AES (AES Connector) related nodes in my application - since I have SIP based integration.
Here's our call flow scenario:
Environment:
AAEP 7.2
AAOD 7.0
Party 1: Caller
Party 2: IVR # 1 application
Party 3: Live Agent
Party 4: IVR # 2 application
There is also a requirement to pass uui data to the agent during call transfer.
Call scenario:
1. IVR # 1 and caller - only two parties active on the call
2. IVR # 1 dials (conferences) to the live agent - remember also pass uui data to this agent.
At this point (assuming transfer successful), we have 3 parties in conference:
(Caller) - (IVR # 1 application) - (Live Agent)
3. IVR # 1 adds another party to this conference call - IVR # 2 application
4. As soon as IVR # 2 application is hit, IVR # 1 application ends.
At this point (assuming all conference/transfer successful), we have 3 parties in conference:
(Caller) - (Live Agent) - (IVR # 2 application)
5. Once IVR # 2 application is finished, it simply ends and drops from the conference
6. Finally, only two parties remain on the call:
Caller and the LIVE Agent
For such a requirement to implement (without AES connector), the other alternative I see is via CCXML (custom code) that will help in conference call as well as passing uui data to the agent. --- Is this right?
OR is there any other alternative to achieve this in plain AOD?
Appreciate your inputs on this topic,
Thanks for your support.
Warm regards,
Jaydeep Hatekar
|