McDewey

Comments Supported in Unified Communications Manager SIP Headers Supported only for the namespaces used in the context of MLPP. ETS and WPS are not supported. Yes Resource-Priority Send it but ignore receiving it. Yes Retry-After — Yes Route — Yes Server — No Subject — Yes Supported — Yes Timestamp — Yes To — Yes Unsupported — Yes User-Agent — Yes Via — Yes Warning — Yes WWW-Authenticate Proprietary and Nonstandard SIP Headers and Identification Services Table 5: Proprietary or Nonstandard SIP Header Fields, on page 10 lists the proprietary and nonstandard header fields for the standard SIP line-side interface. Refer to Remote-Party-ID Header, on page 11 for additional information. Table 5: Proprietary or Nonstandard SIP Header Fields Comments Supported in Unified Communications Manager SIP Headers Used for RDNIS information. If it is present, it always presents the Original Called Party information. The receiving side of this header always assumes it is the Original Called Party info if present. In case of chained-forwarding to a VM, the message gets left to the Original Called Party. Yes Diversion SIP Line Messaging Guide (Standard Edition) for Cisco Unified Communications Manager 10 SIP Standard Line Interface Proprietary and Nonstandard SIP Headers and Identification Services