McDewey

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

Page 1156

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

Scenario Eight—Incoming Call From PSTN Number (Local) to JTAPI Observed Terminal Who Transfers to Another JTAPI Observed Terminal Call info Events Action After Transfer: Calling: A (55555555) Called: B (2222) getModifiedCallingAddress (): A (+140855555555) getModifiedCalledAddress (): B (2222.) getCurrentCalledAddress(): B (2222) getCurrentCalledPartyInfo(): B (2222) getGlobalizedCallingParty: A +140855555555 getCurrentCallingPartyInfo NumberType(). getNumberType() would return: Subscriber After Transfer: GC1: CiscoTransferStartEv ConnCreatedEv for B ConnConnectedEv for B CallCtlConnEstablishedEv for B TermConnDroppedEv for X ConnDisconnectedEv for X CallCtlConnDisconnectedEv for X CiscoTransferStartEv GC2: CiscoTransferStartEv TermConnDroppedEv for X ConnDisconnectedEv for X CallCtlConnDisconnectedEv for X CiscoTransferStartEv A call is offered from a PSTN Number [55555555] A & the Number type is [Subscriber] through a San Jose gateway to a JTAPI observed Terminal [1111] X which transfers the call to another JTAPI Observed Terminal [2222] B Click to Conference A, B, C and D are addresses and TermA, TermB, TermC and TermD are corresponding terminals. Call info Events Action callingAddress = unknown calledAddress = C CurrentCalling = unknown CurrentCalled = C GC2: CallActiveEv Cause: CAUSE_NEW_CALL CiscoFeatureReason: REASON_CONFERENCE GC2: ConnCreatedEv C CiscoFeatureReason = REASON_CONFERENCECause: CAUSE_NORMAL GC2: ConnInProgressEv C CiscoFeatureReason = REASON_CONFERENCECause: CAUSE_NORMAL A and B are in a call GC1 created using click-to-call. User adds C to the conference call. GC2 is the initial call at C. Application is observing only C GC2: CallCtlConnOfferedEv C CiscoFeatureReason = REASON_CONFERENCECause: CAUSE_NORMAL Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 1092 Message Sequence Charts Click to Conference

Page 1156 diagram