Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

CTI: Blind Transfer failing after upgrading the Avaya version

SA-17812

Summary



User has upgraded Avaya SDK version from 5.2.0.454 to 6.3.3.26. 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.


Error Messages



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.


Root Cause



This is an Avaya defect that surfaced after moving to 6.3.3.26 SDK on Pegacall 7.1.3.1.

Resolution



Apply HFix-24743.

 

Suggest Edit

Published January 31, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us