McDewey

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

Page 1551

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

A(referrer) REFERs B(Referee) to C(Refer to target), C is ringing. JTAPI will create Connection/CallControlConnection/TerminalConnection/ CallControlTerminalConnection for C and will drop A's Connection/CallControlConnection on getting CPIC at B, CAUSE_CODE provided will be CAUSE_NORMAL and the new API will provide REASON_REFER. CallInfo at B and C will be as follows: At B: Cgpn = B, Cdpn = C, Lrp = A OCdpn = C At C: Cgpn = B, Cdpn = C, Lrp = A OCdpn = C JTAPI Application observing B will see: getCallingParty() = A getCalledParty() = B getCurrentCallingParty() = B getCurrentCalledParty() = C getLastRedirecting() = A JTAPI Application observing C will see: getCallingParty() = B getCalledParty() = C getCurrentCallingParty() = B getCurrentCalledParty() = C getLastRedirecting() = A Scenario Five A(SIP UA outside cluster) is in a call with B. A(referrer) refers B(Referee) to C(Refer to target), C is ringing but C did not answer the call and has no forward configured. Refer fails, the original Call between A and B is restored. JTAPI will create Connection/CallControlConnection for A again and drops Connection/ CallControlConnection/TerminalConnection/CallControlTerminalConnection for C. CAUSE_CODE provided will be CAUSE_NORMAL and new API will provide REASON_REFER. CallInfo at A and B will be as follows At A: Cgpn = A, Cdpn = B, Lrp = OCdpn = B At B: Cgpn = A, Cdpn = B, Lrp = OCdpn = B JTAPI Application observing A will see: getCallingParty() = A getCalledParty() = B Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 1487 Message Sequence Charts Message Sequence Charts

Page 1551 content