/mcpDescription Restriction The iDivert detects a busy condition on the voicemail ports, when iDivert reaches a voicemail system over a local or SCCP connection. Note Immediate Divert cannot divert a call to a busy voicemail port; voicemail ports can exist as members of a route or hunt list. The call cannot divert to a busy voicemail system, but the original call gets maintained. The phone displays “Busy” message on which iDivert was invoked to indicate that the call was not diverted. When a voicemail system is reached over a QSIG or SIP trunk, iDivert can be detected, but the call does not get maintained. When the Allow QSIG During iDivert clusterwide service parameter is set to True, or the Use Legacy Immediate Divert clusterwide service parameter is set to False, Immediate Divert supports access to voicemail systems that can be reached over QSIG or SIP trunks. When the Allow QSIG During iDivert clusterwide service parameter is set to False, and the Use Legacy Immediate Divert clusterwide service parameter is set to True, Immediate Divert does not support access to voicemail systems over QSIG or SIP trunks. Busy Voicemail System System does not support using Malicious Caller ID and Immediate Divert features together. Malicious Caller ID A race condition in connection with the Forward No Answer Timeout exists when you press the iDivert softkey. For example, if a manager presses the iDivert softkey immediately after the Forward No Answer timeout, call forward forwards the call to a preconfigured directory number. However, if the manager presses the iDivert softkey before the Forward No Answer timeout, immediate divert diverts the call to the voice-messaging mailbox of the manager. Forward No Answer Timeout The calling parties and called parties can divert the call to their voice mailboxes if both simultaneously press the iDivert softkey. Calling Parties and Called Parties When one participant in a conference presses the iDivert softkey, all remaining participants receive an outgoing greeting of the participant who pressed iDivert. Conference types include Meet-Me, Ad Hoc, cBarge, and Join. Conference Types If the last action on a call was Auto Pickup, Call Transfer, Call Park, Call Park Reversion, Conference, Meet-Me Conference, or any application that performs a split or join operation, enhanced iDivert does not present a screen to a called party to choose the voice mailbox. Instead, enhanced iDivert immediately diverts the call to the voice mailbox that is associated with the called party. Split or Join Operation Feature Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs 215 Voice Messaging Features Immediate Divert Restrictions