/mcpCTI Redirect to Voice Mail Wont Work with QSIG When applications redirect a call to voice mail through a QSIG trunk, voice mail will not play the voice prompt of the redirecting party. A generic prompt asking the user to enter the voice mail box is played. This is due to the fact that CTI redirect doesn't pass correct original called party and redirecting party to the voice mail system. Applications can work around this by using a SIP trunk. Phone A calls Phone B (CUCILYNC in Deskphone mode). Toast popup of "envelope" appears for incoming call. User clicks on the envelope, redirecting the call across an H.323 trunk with QSIG tunneling. Unity/Unity Connection won't recognize original called party, so call will not go to user's voice mailbox. This is because Re-direct/Original Called Party information not carried across the trunk when CTI redirect is used. CiscoAddress.getForwarding() Returns Correct Value Only for In-Service Addresses Although the Sun JTAPI 1.2 specification does not specify any preconditions for CallControlAddress.getForwarding(), the implementation of this method in Cisco JTAPI will return a correct value only if the address is in service. When invoked on an out of service address this method will just return a NULL value. Unsupported CTI Events for SIP Phones The following CTI events are not generated for SIP phones. Third party applications that expect these call events should use SCCP phones: • CallOpenLogicalChannelEvent • CallRingEvent • DeviceLampModeChangedEvent • DeviceModeChangedEvent • DeviceDisplayChangedEvent • DeviceFeatureButtonPressedEvent • DeviceKeyPressedEvent • DeviceLampModeChangedEvent • DeviceRingModeChangedEvent Caveats for Release 9.1(1) This section lists the JTAPI caveats for Release 9.1(1). • Connection for Park DN While UnPark, on page 1713 Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 1712 Caveats CTI Redirect to Voice Mail Wont Work with QSIG