McDewey

Multi-vendor documentation library · semantic search · MCP endpoint at /mcp

Page 1548

↗ View in doc context
page
1548
source
cucm/v15/jtapi-dev-guide/jtapi-dev-guide.md
chunk_id
cucm::v15::jtapi-dev-guide::jtapi-dev-guide::1552

Events at C Events at B Events at A Scenario SN GCID with reason REPLACES and Cgpn = B, Cdpn = C, Lrp = D, OCdpn = C JTAPI Events: CiscoCallChangedEv (GC2 -GC1) ConnDisconnectedEv -D CallCtlConnDisconnectedEv -D ConnDisconnectedEv -C CallCtlConnDisconnectedEv -C CallInvalid -GC2 CallActive -CG1 ConnCreatedEv –C -GC1 ConnConnectedEv –C -GC1 CallCtlConnEstablishedEv -C -CG1 ConnCreatedEv –B –GC1 ConnConnectedEv –B -GC1 CallCtlConnEstablishedEv -B -CG2 Cause = CAUSE_NORMAL CiscoFeatureReason = REASON_REPLACES JTAPI CallInfo: Calling = C, Called = C, CurrentCalling = B, CurrentCalled = C, LastRedirecting = D CPIC with reason REPLACES and Cgpn = B, Cdpn = C, Lrp = D OCdpn = C JTAPI Events: ConnDisconnectedEv –A -GC1 CallCtlConnDisconnectedEv -A -GC1 ConnCreatedEv –C -GC1 ConnConnectedEv –C –GC1 CallCtlConnEstablishedEv -C -GC1 Cause = CAUSE_NORMAL CiscoFeatureReason = REASON_REPLACES JTAPI CallInfo: Calling = A, Called = B, CurrentCalling = B, CurrentCalled = C, LastRedirecting = D CSCE -Idle at Dialog1 with reason REFER and at Dialog3 with reason REPLACES JTAPI Events: ConnDisconnectedEv –A –GC1 CallCtlConnDisconnectedEv -A -GC1 ConnDisconnectedEv –B -GC1 CallCtlConnDisconnectedEv -B -GC1 CallInvalidEv -GC1 Cause = CAUSE_NORMAL CiscoFeatureReason = REASON_REFER Event at D: ConnDisconnectedEv –D –GC2 CallCtlConnDisconnectedEv -D -GC2 ConnDisconnectedEv –C -GC2 CallCtlConnDisconnectedEv -C -GC2 CallInvalidEv -GC2 Cause = CAUSE_NORMAL CiscoFeatureReason = REASON_REPLACES REFER request with REPLACE Dialog: When REPLACE Dialog is in a Cisco Unified Communications Manager Cluster. A is in call with B (REFEREE) Dailog1, and Dialog2 (GC1) D is in Call with C (REFER TO TARGET) Dialog3 and Dialog4 (GC2) A sends REFER B on Dialog1 to C with REPLACES Dialog3 B and C in final call. 7. SIP REFER The following section describes the scenarios that might be encountered during a SIP REFER. There are two categories of REFER scenarios: IN-Dialog and OutOfDialog. IN-Dialog REFER Scenario There are 11 scenarios (A through K) described in the sections that follow for IN-Dialog REFERs. Scenario One A (SIP UA in cluster/in control) is in a call with B. A (referrer) REFERs B (Referee) to C (Refer to target), C is Ringing. Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 1484 Message Sequence Charts SIP REFER