/mcpdeclarative attributes need to be passed to the egress leg. The configuration for this feature on the SIP Profile applies all registered SIP endpoints and SIP trunks using that SIP Profile. Note that a reset of all devices using this SIP Profile is needed for any changes to take affect. There are exceptions, however, for when the feature will take effect. The feature does not apply to the following situations: • One or more of the following apply on the egress leg: • One or more Media Termination Points (MTPs) that does not support pass through has been allocated • One or more Trusted Relay Points (TRPs) that does not support pass through has been allocated • The use of the RSVP feature • The use of a transcoder • “Media Termination Point Required” is selected • The ingress call leg is using Delayed Offer while the egress call leg is using Early Offer • The media line has been rejected (the port is set to 0). Note that in this situation, it may be possible to see certain attributes in the media line. Any attribute on a rejected media line should be ignored and solutions must not rely on this feature to send attributes on rejected media lines. Doing so is strictly not supported. • Either call leg uses any protocol other than SIP This feature supports the passing of attributes that follow the grammar prescribed in RFC 4566. Any attribute that deviates from this grammar is not guaranteed to pass correctly. However, best effort is made to pass the attribute in these situations. Unified Communications Manager Version in User-Agent and Server Headers This feature adds a new field to the common section of the SIP profile called "Version in User Agent and Server Header". There are 5 possible values and each specifies a portion of the installed build version that will be used as the value of these headers in SIP requests. Previously, Unified Communications Manager always used a value representing the major and minor version (for example "Cisco-CUCM9.0") as the User-Agent value in outgoing SIP requests. The Server header was not previously sent in SIP responses, except as part of the feature for passthrough of User-Agent and Server headers. When the passthrough feature is not in use (for example if the value of the SIP profile parameter "User-Agent and Server header information" is "Send Unified CM Version Information as User-Agent Header"), this feature will populate the User-Agent and Server headers as specified in the following table, given an example build version of "10.0.1.98000-19". Example string value in the User-Agent and Server header Value specified for SIP profile parameter "Version in User Agent and Server Header" Cisco-CUCM10.0 Major and Minor Cisco-CUCM10 Major Cisco-CUCM10.0.1 Major, Minor And Revision SIP Line Messaging Guide (Standard Edition) for Cisco Unified Communications Manager 41 SIP Standard Line Interface Unified Communications Manager Version in User-Agent and Server Headers