/mcpEmergency operator call back calls are designated with the priority value of 'emergency'. Hold reversion, park reversion, and call pickup calls are designated as ‘urgent'. All other calls are considered as having a priority of 'normal' and a priority parameter is not provided. gci A unique identifier is passed down to the phone in this parameter. The identifier is the same for all call-legs that belong to a particular call. This identifier can be used by phones to influence the end user interface. Phones can filter out multiple call-legs on the device that belong to a particular call and choose to present a single call-context to the end user. Call-Info-Sent from Endpoint to Unified CM Unified Communications Manager SIP line-side endpoints can pass supplementary feature activation information to Unified CM using the Call-Info header. The following table provides details of what additional parameters apply to each feature. Example/Notes Feature Call-Info: urn:X-cisco-remotecc:callinfo; gci= 1-1039476; mode= silent callinfo The gci parameter is a string which the endpoint obtains from a remotecc initiate call request or monitor call request. The initiated call request is used by the CallBack feature and CTI applications. The monitor call request is used by the CTI-controlled Silent Monitoring feature. The mode parameter provides a signaling mechanism to distinguish between different Monitoring feature modes. The only mode supported in this release is “silent”. Refer to the 'Monitoring' section for further information. Call-Info: urn:X-cisco-remotecc:hold hold Call-Info: urn:X-cisco-remotecc:hold; reason= transfer The reason parameter is optional. Feature holds by itself (that is, simply placing a call on feature hold) does not include a reason (see the 1st example). Values are transfer and conference (see the 2nd example). SIP Line Messaging Guide (Standard Edition) for Cisco Unified Communications Manager 55 SIP Standard Line Interface gci