McDewey

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

Page 167

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

getMediaConnectionMode() Returns CiscoMediaConnectionMode int public interface CiscoRTPInputStoppedEv getMediaConnectionMode() Returns CiscoMediaConnectionMode int public interface CiscoRTPOutputStoppedEv getMediaConnectionMode() Returns CiscoMediaConnectionMode int Hold Reversion The Hold Reversion feature provides applications with a notification when Cisco Unified Communications Manager notifies an address about the presence of a held call, when the call has been ONHOLD for a certain amount of time. Applications receive this notification as the CiscoCallCtlTermConnHeldReversionEv call control terminal connection event on their call observers on the particular address that has put the call ONHOLD. This notification is provided only once for the applications for the held call. The event is sent only to the terminal connection of the terminal where the call was put on hold. If the address represents a shared line address, other terminal connections of the shared line address will not receive the event. To receive this event, applications must add a call observer to the address. The cause for this event will be CAUSE_NORMAL. If the call observer is added after the hold reversion timer has expired and the notification has already been sent to the phone, applications will receive CiscoCallCtlTermConnHeldReversionEv with cause CAUSE_SNAPSHOT. For more information, see CiscoCallCtlTermConnHeldReversionEv, on page 352. Hunt List This feature enables the JTAPI application to observe addresses and terminals that are HuntList LineGroup members. Calls can arrive at these addresses either by another address calling it directly or through HuntPilot. When a call is made to HuntPilot, JTAPI creates a CiscoHuntConnection to represent HuntPilot and provides a Call Model that gives applications the information that the call is routed through HuntPilot. When a call is routed through HuntPilot and is connected to LineGroup Member, JTAPI call has three connections, two regular connections for calling and called addresses, and one CiscoConnection to HuntPilot through which that call was routed. HuntPilot is not an observable address. The address representing Hunt Pilot is created when a call is made to a Hunt Pilot and is removed when the call is over. Applications cannot receive the Hunt Pilot address from the provider by using the getAddress() method. Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 103 Features Supported by Cisco Unified JTAPI Hold Reversion