/mcpThe scenario above is an example of how a redirect causes the display orientation to change. There are many more scenarios where this happens. As with the security status, the display orientation will be sent to the endpoint through the Call-Info header. The endpoint should use the SIP dialog orientation as the display orientation if none is specified (in fact, this is what legacy and 3rd party phones do). There are two possible values for the orientation: • from • to Here is an example using the urn feature naming scheme where the feature is Call-Info and the orientation is encoded as a generic parameter. Call-Info: urn:X-cisco-remotecc:callinfo; orientation= to The endpoint is responsible for localizing this information. Call Instance When a call arrives at a phone (or is placed by a phone), a call instance number relative to the line is associated with the call. On the phones, this number is displayed in the call bubble beside the call details. For example, if line 1000 calls line 1001, the call on the phone with line 1001 shows up as '01 from 1000'. If line 2000 then calls 1001, another call bubble appears on 1001. This one indicates '02 From 2000'. The 01 and 02 are the call instance numbers. Here is an example using the urn feature naming scheme where the feature is Call-Info and the call instance information is encoded as a generic parameter. Call-Info: urn:X-cisco-remotecc:callinfo; call-instance= 1 The endpoint is responsible for localizing this information. UI State Two ui-state values are utilized, “ringout” and “busy”. Refer to the Early Attended Transfer, on page 28 section of this document for “ui-state= ringout”. For “ui-state= busy”, see the following information for its usage. Phones that support x-Cisco-callinfo and extended refer do not get a 486 when calling a line that is busy. Unified Communications Manager sends a "183 Session Progress", and then a playtonereq to play the busy tone in a REFER. With the “183 Session Progress”, a Call-info header is included. Within that Call-Info header, “ui-state= busy” is included to indicate the line is busy when calling a busy line. Priority Some types of calls require the endpoint to override is local alerting policy regardless of a user’s alerting preference. For example, an emergency operator (911 callback) must be able to call an originator of an emergency call should the call be disconnected. Unified Communications Manager conveys the urgent nature of the call using the Call-Info header’s Priority parameter. One example where this type of UI policy override is required is when the user has enabled DND with Call Reject as the call treatment. In this case, operator callback, hold reversion, park reversion, and call pickup calls should provide normal alerting to being the users attention to these calls. SIP Line Messaging Guide (Standard Edition) for Cisco Unified Communications Manager 54 SIP Standard Line Interface Call Instance