CTI: Blind Transfer failing after upgrading the Avaya version
User has upgraded Avaya SDK version from 18.104.22.1684 to 22.214.171.124. After the upgrade, the blind transfer functionality has been behaving incorrectly.
The same behavior is seen using OOTB portal (casysadmin). When user blind transfers the call, and check for pyApplicationdata tag in the xml, it must provide old callid details, however the old call id is not being populated.
No error messages, but the old Call id is not being populated.
Steps to Reproduce
Blind transfer the call and check for pyApplicationdata tag in the xml.
This is an Avaya defect that surfaced after moving to 126.96.36.199 SDK on Pegacall 188.8.131.52.