McDewey

Caveats for Release 6.0.1 This section lists the JTAPI caveats for Release 6.0.1: • Call History Might Get Lost When AAR Routes Over QSIG Trunk, on page 1719 • Different Event Order If Consult Call Initiated on SIP Device, on page 1719 Call History Might Get Lost When AAR Routes Over QSIG Trunk When a call is forwarded due to insufficient bandwidth (Call Forward No Bandwidth - CFNB) to another cluster over a trunk or gateway using QSIG, call history might get lost. If Phone A calls Phone B, which is in a low bandwidth location, with CFNB set to forward calls to Phone C, which is in a different cluster, and the QSIG protocol is used on the trunk/gateway, then the original called party and the last redirecting party might not get passed to the destination party. Different Event Order If Consult Call Initiated on SIP Device Scenario: Terminal A initiates a call to the shared line B/B' and which Initiates a consult call to Terminal C. • If the Shared Line is SIP device then the call events are : • B (active) receives: CallCtlTermConnHeldEv > CiscoTermConnSelectChangedEv > CallActive • B' (remote-in-use) receives: CiscoTermConnSelectChangedEv > CallActive > CallCtlTermConnHeldEv • If the Shared Line is SCCP device then the call events are: • CiscoTermConnSelectChangedEv > CallCtlTermConnHeldEv > CallActive on both the Terminals. Caveats for Release 5.0 This section lists the JTAPI caveats for Release 5.0: • SRTP Support, on page 1720 • Partition Support, on page 1720 • TLS Security, on page 1720 • CiscoFeatureReason, on page 1720 • Unicode Issue in Calls Involving SIP Trunks, on page 1720 • Join Across Lines: Conference Two or More Addresses on Same Terminal, on page 1721 • JTAPI Exposes Incorrect Information with getCallingAddress() and getCalledAddress(), on page 1722 Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 1719 Caveats Caveats for Release 6.0.1