McDewey

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

Page 963

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

Scenario Thirteen DND is enabled on the terminalA. Terminal A comes IN_SERVICE, DND status is currently true in phone/admin. Application tries to set the same value i.e. invokes setDNDStatus(true). Call info Events Action N.A InvalidStateException is caught: DND status with value true is already set No CiscoTermDNDStatusChangedEv is received. DND is enabled on the terminal A. Terminal A comes IN_SERVICE.DND status is currently true in phone/admin.Application tries to set the same value i.e. invokes setDNDStatus(true). DND-R Scenario One Application adds Terminal observer to terminal A using Terminal.addObserver (). DND-R is enabled on the terminal B via the Admin page or the Common profile page. Call info Events Action N.A NEW META EVENT_________ META_CALL_STARTING CallActiveEv for callID = GC1 Cause: CAUSE_NEW_CALL ConnCreatedEv for A Cause: CAUSE_NORMAL ConnConnectedEv for A Cause: CAUSE_NORMAL CallCtlConnInitiatedEv for A Cause: CAUSE_NORMAL ConnFailedEv B Cause:. Cause: CAUSE_USERBUSY. Application adds terminal observers to terminal A and B. DND-R is enabled on the terminal B through phone or admin page. A issues Call.connect to B with the feature Priority = 1 (Normal) Scenario Two Application adds Terminal observer to terminal A using Terminal.addObserver (). DND-R is enabled on the Terminal B via the Admin page or the Common profile page. Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 899 Message Sequence Charts DND-R

Page 963 diagram