McDewey

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

Page 1555

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

JTAPI Application observing C will see: getCallingParty() = B getCalledParty() = C getCurrentCallingParty() = C getCurrentCalledParty() = D getLastRedirecting() = B Scenario Eleven B is in a call with D, B consults to A(SIP UA in cluster/in control). A(Referrer) REFERs B(Referee) to C(Refer to target), C is ringing, B completes the transfer. REFER would fail. Call at A will be dropped, transfer is successful, D is getting RingBack, C is ringing. JTAPI Disconnect/Drops A’s Connect/CallControlConnection/TerminalConnection/ CallControlTerminalConnection. CAUSE_CODE provided will be CAUSE_NORMAL and the new API would provide REASON_REFER, Application will not know if REFER failed. For C, Connect/CallControlConnection/TerminalConnection/CallControlTerminalConnection will move to Alerting/Alerting/Ringing/Ringing state. CallInfo at D and C would be as follows: At D: Cgpn = D, Cdpn = C, Lrp = B OCdpn = C At C: Cgpn = D, Cdpn = C, Lrp = B OCdpn = C JTAPI Application observing D will see: getCallingParty() = B getCalledParty() = D getCurrentCallingParty() = D getCurrentCalledParty() = C getLastRedirecting() = B JTAPI Application observing C will see: getCallingParty() = B getCalledParty() = C getCurrentCallingParty() = D getCurrentCalledParty() = C getLastRedirecting() = B OutOfDialog Refer SIP-UA A REFERs B(Referee) to C (Refer To Target) Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 1491 Message Sequence Charts OutOfDialog Refer

Page 1555 content