McDewey

3XX Redirection – Contact Within Cisco Unified Communications Manager Cluster Configured with Call Forward JTAPI application monitors 1000@ccm.cisco.com Cisco Unified Communications Manager user1000 initiates a call to 333555@aaa.com CTI reports NewCallNotify and CtiCallStateNotify (Dialtone/Dialing) based on INVITE. JTAPI reports CallActiveEv and connection and terminalConnection events for 1000 CTI reports CtiCallStateNotify (Proceeding) JTAPI reports CallCtlConnEstablishedEv for 1000 SIP proxy reports a 302 for 333555@aaa.com. Based on the 302 the Cisco Unified Communications Manager initiates a call to the first contact in the Target list based on the q value to 2000@ccm.cisco.com. A 486 user busy response is reported by 2000@ccm.cisco.com. 2000 has Call Forward busy configured so the Cisco Unified Communications Manager initiates a call to 3000@ccm.cisco.com. The Cisco Unified Communications Manager also starts the RNAR timer. CallPartyInfoChange event is reported to application based on the SIPAlertInd from the Cisco Unified Communications Manager if the called party information is changed. JTAPI reports connection created event for 3000 3000 does not answer and RNAR timer expires and based on this expiration the Cisco Unified Communications Manager initiates a call to 555888@cisco.com. CallPartyInfoChange event is reported to application based on the SIPAlertInd/CcNotifyReq from the Cisco Unified Communications Manager if the called party information is changed. JTAPI destroys connection for 3000 and creates connection for 555888 CTI also reports CtiCallStateNotify (Connected). JTAPI reports CallCtlConnEstablishedEv for 555888 Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 1496 Message Sequence Charts Message Sequence Charts