McDewey

Description Method Inteface Filters the events that get delivered to the TerminalObserver. You can call this method at any time, but the typical usage is to set up the terminal events as part of initialization or when a CiscTermCreatedEv indicates that the system created a new terminal. • Example 1—One use might be to turn on the button-pressed events that normally do not get not delivered. Terminal term = provider.getTerminal ( name ); if ( term instanceof CiscoTerm ) { CiscoTerm ciscoTerm = (CiscoTerm)term; CiscoTermEvFilter filter = ciscoTerm.getFilter (); filter.setButtonPressedEnabled ( true ); } term.addObserver ( terminalObserver ) • Example 2—Another use might be turning off events that are not of interest to an application. For example, an application doing pure call control could turn off the media (RTP) events as follows: Terminal term = provider.getTerminal ( name ); if ( term instanceof CiscoTerm ) { CiscoTerm ciscoTerm = (CiscoTerm)term; CiscoTermEvFilter filter = ciscoTerm.getFilter (); filter.setRTPEventsEnabled ( false ); ciscoTerm.setFilter ( filter ); } term.addObserver ( terminalObserver ); term.getAddresses () [0].addCallObserver ( callObserver ) Note Adding a CallObserver (without explicitly setting a filter) turns the RTP events on. This behavior of Cisco JTAPI Release 1.4 and earlier is still preserved. If an explicit setFilter call gets made, the filter settings will take effect. The RTP events will not get delivered for the previous code snippet, but will get delivered for the following example: Terminal term = provider.getTerminal ( name ); term.addObserver ( terminalObserver ); term.getAddresses () [0].addCallObserver ( callObserver ). setFilter(CiscoTermEvFilter terminalEvFilter) void Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 623 Cisco Unified JTAPI Extensions Methods