McDewey

LineHold Enhancement Prerequisites Pre-conditions to all persistent call use cases, unless specified otherwise: • Device A (IP Phone, Line A1 (dn: 1000)) • Device B (IP Phone, Line B1 (dn: 2000)) • The content id corresponding to VoH stream is contentID1 • User1 has in its control list: Devices A and B. All devices and lines are observed • Provider is opened ( lineInitializeEx successfully executed) • All relevant lines are opened with Extension version 0x000D0000 and in service Table 136: Basic Case - Hold with ContentID to Be Played TAPI Structures TAPI Messages Action CallInfo on A: CallerID: 1000 CalledID: 2000 ConnectedID: 2000 At A: LINE_CALLSTATE dwParam1 = 0x00000100 ( CONNECTED) At B: LINE_CALLSTATE dwParam1 = 0x00000100 ( CONNECTED) Create Call: LineMakeCall() on Line-A w ith DestAddress="DN of B" and B answers the Call At A: LINE_CALLSTATE dwParam1 = 0x00000400 (LINECALLSTATE_ONHOLD) Application issues CCiscoLineDevSpecificHoldEx with ContentID = contentID1 on hCall1(call on A1) *** Call will be placed on Hold and VoH stream selected is played to B. Whisper Coaching Setup Customer Phone – IP Phone A Agent Phone – IP Phone B Supervisor Phone – IP Phone C Application monitoring all lines on all devices New extension is negotiated when application opens lines Application Initiates a Whisper Coaching Session Service Parameter Setting: Observed Target = false, Observed Connected Parties = true Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 1012 Message Sequence Charts LineHold Enhancement