McDewey

Table 44: Application Issues the Play Tone Request (with Unsupported Tone) When the Call Is Established Between Customer and Agent. PlayToneDirection – Local Expected events Action LineDevSpecific (start PlayTone) request fails with error LINEERR_OPERATIONFAILED. LineInitialize. LineOpen on A,B A calls B; B answers the Call B issues LineDevSpecific (start PlayTone) request with agent callid and ZIP Tone as input Application Issues the Play Tone Request on a CTI Port with PlayToneDirection -Local/Remote Configuration A (Customer/Remote) is SCCP Phone. B (Agent/local) is a CTIport/Route Point Table 45: Application Issues the Play Tone Request on a CTI Port with PlayToneDirection – Local/Remote Expected events Action LineDevSpecific (start PlayTone) request fails with error LINEERR_OPERATIONUNAVAIL. Zip Tone is played at A. Line_DevSpecific (dwparam1 = SLDSMT_CALL_TONE_CHANGED, dwParam2 = CTONE_ZIP, dwParam3 = 0(local)) is fired for A indicating Zip Tone has been played on A And also Line_DevSpecific (dwparam1 = SLDSMT_CALL_TONE_CHANGED, dwParam2 = CTONE_ZIP, dwParam3 = 1(remote) is fired for B LineInitialize. LineOpen on A,B The CallToneChangedEvent message flag is Enabled using SLDST_SET_STATUS_MESSAGES request for Line A. A calls B;B answers the Call B issues the LineDevSpecific (start PlayTone) request with agent callid and ZIP Tone as input, and direction as local. B issues the LineDevSpecific (start PlayTone) request with agent callid and ZIP Tone as input, and direction as remote. Application Issues the Play Tone Request When the Call Is Established Between Customer and Agent (Shared Line). PlayToneDirection -Local Configuration SCCP phones: A (Customer/ Remote), B, B’ (Agent/Local) Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 473 Message Sequence Charts Application Issues the Play Tone Request on a CTI Port with PlayToneDirection -Local/Remote