McDewey

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

Page 1458

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

Event Action No. Before the PR feature replaces the path, the application will see two calls: GC1 with connections to A and B (external) and GC2 with connections to C and B (external). In this case, the application will not see any transfer start events. When PR feature replaces the path, it updates the display of A and C and path gets replaced, resulting in a GCID change. Assuming A's GCID is changed and made the calling party, the following JTAPI events occur: GC1: CiscoCallChangedEv (GC1 to GC2) GC1: CallCtlConnDisconnected for A GC1: CallCtlConnDisconnected for C GC1: CallInValid GC2: ConnCreatedEv A GC2: ConnConnectedEv A GC2: TermConnTalkingEvent for TerminalA cause = CAUSE_QSIG_PR Trombone case: A registered to CM1, B registered to CM2, and C registered to CM1. B calls A and transfers the call to C. Path replacement connects A and C, bypassing CM2. Application observes both A and C. (The calling party transfers the call.) 4 Path replacement gets abandoned. A registered to CM1, B registered to CM2, and C registered to CM1. A calls B; B transfers the call to C. C answers and before path replacement completes, C invokes a feature (park, redirect, and so on). 5 JTAPI: Exception will be thrown from JTAPI for feature requests. In some conditions, call processing ignores feature requests (redirect, park, transfer, and so on). This happens when a setup request is sent out, and the local CM is waiting for connect from the other end. 6 No events JTAPI Apps: Hang up the call In some cases, the application could receive dead air when CM goes down when the PR feature is trying to switch the RTP path. This could happen to a previously connected call. 7 Recording Use Cases Expose ClusterID in CiscoProvider Interface Call Info Events Actiions Start application and initialize JTAPI ProvInServiceEv Add provider observer JTAPI returns 'StandAloneCluster' Application calls ciscoProvider.getClusterID() Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 1394 Message Sequence Charts Recording Use Cases