McDewey

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

Page 79

↗ View in doc context
page
79
source
cucm/v15/tapi-dev-guide/tapi-dev-guide.md
chunk_id
cucm::v15::tapi-dev-guide::tapi-dev-guide::60

Beginning with Unified Communications Manager Release 10.01, applications can use lineMakeCall to create a Persistent Call or Announcement Call. For a Persistent Call or Announcement Call, the relevant data is provided in the LINECALLPARAMS structure pointed to by the lpLineCallParams parameter. All other lineMakeCall parameters are ignored in these cases. • See Announcement Events, on page 406. Message Sequence See Announcement Call, on page 476. Backward Compatibility This enhancement is backward compatible and existing applications are not affected by the introduction of this enhancement. NuRD (Number Matching for Remote Destination) Support In CUCM 10.0, the existing "Cisco Extend and Connect" feature includes number matching for remote destination support. When users directly call a number that is configured as a remote destination for CTI Remote Device (CTI RD), and that remote destination is set to be active, the call is offered on the CTI Remote Device and extended to the remote destination. The called party is presented to the application as the CTI RD. If active remote destination is not set, when users call a remote destination number, a direct call between the caller and the remote destination occurs. This scenario also applies to a remote destination making a call to an enterprise directory number. If the remote destination is set to be active, from an application perspective, the CTI RD appears to initiate the call to the enterprise dn. If the active remote destination is not set, when the remote destination calls an enterprise dn, it is a direct call between the remote destination and the enterprise dn. For those calls from and to a remote destination number, all existing features allowed on CTI RD can be performed. Interface Changes There are no interface changes for this feature. Use Cases See NuRD (Number Matching for Remote Destination) Support, on page 896. Backward Compatibility This feature can change the existing expected behavior in regards to calls to and from remote destination numbers directly. Applications that do not want to leverage this NuRD feature can keep the cluster-wide service parameter "Reroute Remote Destination Calls to Enterprise Number" set to false. Enabling it will enable the NuRD features. This parameter by default is set to false. Mobility Interaction Support The "Cisco Extend and Connect" feature includes mobility interaction. Users can specify remote destinations that are shared between the CTI Remote Device (CTI RD) and the Remote Destination Profile (RDP). When both the CTI RD and the RDP are configured for the same user, and if the application is active (active rd is Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 47 Features Supported by TSP NuRD (Number Matching for Remote Destination) Support