PDF(5.3 KB) View with Adobe Reader on a variety of devices
ePub(84.7 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(70.5 KB) View on Kindle device or Kindle app on multiple devices
Updated:May 10, 2019
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The Client Application Protocol (CAP) interface has been removed from Release 22.0. CAP is no longer supported in 22.0 and up and thus this must be disabled post upgrade to 22.0 to prevent connection attempt and OCS errors, illustrated by alarms such as “A CAP connection has been terminated between the Open Client Server and Application Server 220.127.116.11” or bwOpenClientServerASConnFailed".
After upgrading the Application Server and Xtended Services Platform to 22.0 there may be CAP alarms displayed on both the AS and XSP.
XSP_CLI/Applications/OpenClientServer/CAPProxy> set enabled false *** Warning: BroadWorks needs to be restarted for the changes to take effect ***
After the change has been applied the server will require OpenClientServer to be restarted. If CAPProxy is disabled prior to the upgrade OpenClientServer does not need to be restarted as it will be restarted during the upgrade.