McDewey

Events, requests and responses Action At 1002: the request is successful Application receives LineCallDevSpecific (SLDSMT_MEDIA_TO_BIB_STARTED) event At 5555: CONNECTED, dwreason = LINECALLREASON_UNKNOWN (unknown) ExtendedCallReason = CtiReasonSendMediaToBIB Calling = CgpnToIVR Called = 5555 Connected = CgpnToIVR CallAttributeBitMask = ServerCall bit will be set At 5555: CONNECTED, dwreason = LINECALLREASON_UNKNOWN (unknown) ExtendedCallReason = CtiReasonSendMediaToBIB Calling = 5555 Called = 5555 Connected = CallAttributeBitMask = ServerCall bit will be set Media event sent to application (StartTransmissionEvent) Application issues CCiscoLineDevSpecificStartSendMediaToBIBRequest on 1002 (CM feature creates server call to IVR1 5555, 5555 answers call) Server-IVR call is redirected to BIB IVR1 selects/plays agent’s greeting At 1002: Application receives LineCallDevSpecific (SLDSMT_MEDIA_TO_BIB_ENDED,0,0) event Call will go on hold With StopReception and StopTransmission event At 5555: Call goes IDLE 1002 put call on hold At 1002: Call will go CONNECTED with StartTransmission and StartReception. 1002 Unhold scenario Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 465 Message Sequence Charts Message Sequence Charts