/mcpA sample use case scenario consists of two users in a video call via their Cisco EX90 phones. Each user has the video output of their laptop computer connected to their respective EX90 via HDMI or DVI. During the call, user A on his EX90 decides to share his laptop video with user B. User A presses the "Present" button on the EX90. The EX90s and Unified CM would utilize SIP and BFCP protocols to enable User B to see User A's main video along with the User A's laptop video. BFCP is an SDP-only feature and does not entail any signaling related changes. BFCP is enabled by default for all Cisco TelePresence endpoints. As of Release 9.0(1), other Cisco endpoints that support BFCP can enable the feature in Unified Communications Manager by advertising BFCP capability to Unified CM in the SIP REGISTER message as follows: <optionsind> <bfcp></bfcp> </optionsind> Third-party endpoints that register to Unified Communications Manager can enable features in the Phone Configuration window of the Cisco Unified CM Administration user interface. Multilevel Precedence and Preemption Using Resource Priority Unified Communications Manager supports Multilevel Precedence and Preemption (MLPP) for both Cisco and third-party endpoints, based on the configured device type. Unified CM only supports MLPP for certain models. The Resource Priority header communicates precedence information between the Unified CM and the endpoint. The Unified CM implementation of Resource Priority is compliant with DISA Unified Capabilities Requirements, which go beyond the RFC 4412 standards, particularly with regard to the treatment of the namespace. While RFC 4412 gives no special significance to the presence of a dash in the namespace, the UCR reserves the dash for tokenizing a namespace into network domain and precedence domain. The Unified CM allows the use of the dash in the namespace and determines whether it is simply a part of the namespace or a token delimiter based on whether it is configured as part of the network domain on Unified CM. The preemption function of MLPP is handled by the endpoint, not by the Unified CM. Unified CM overrides the normal busy trigger when MLPP is enabled to present a precedence call to the endpoint. Configurable Non-Preemptable Numbers Configurable Non-Preemptable numbers affect the preemption behavior of the SIP endpoints. If the feature is enabled at the service parameter level, and the SIP endpoint had more than one call on the phone, then the Unified Communications Manager will not present the subsequent incoming call to the SIP phone as the phone does not implement the Non-Preemptable numbers feature. Hence, to prevent the phone from preempting a Non-Preemptable number, Unified Communications Manager rejects the incoming call to the phone which is higher than the busy trigger. For example, if the busy trigger is 2, then Unified Communications Manager will reject the third call. Outgoing Identity and Incoming CLI for SIP Calls The Outgoing Identity and Incoming CLI for SIP calls feature provides the ability to enhance the identity selection, presentation, and restriction on SIP Interfaces. These capabilities are offered via additional configuration fields that you can use for presentation (Identity headers and From headers) on SIP Trunk and on SIP profiles for controlling corresponding SIP phones. SIP Line Messaging Guide (Standard Edition) for Cisco Unified Communications Manager 37 SIP Standard Line Interface Multilevel Precedence and Preemption Using Resource Priority