/mcpIf the incoming anonymous call arrives from a SIP device such as a phone or trunk, Unified CM rejects the call with SIP response 433 Anonymity Disallowed. The 433 response will also carry a Reason header with Q.850 cause value 21 (call rejected). The following example shows a SIP 433 response sent to the anonymous caller. SIP/2.0 433 Anonymity Disallowed Via: SIP/2.0/TLS 172.18.199.91:50486;branch=z9hG4bK3584db90 From: "Connected6005" sip:6005@10.81.54.224;tag=f0257279babd003850ae8c99-11653498 To: sip:\*@10.81.54.224;tag=32638~078d0a52-bf48-420d-b77b-7737bebdf89b-18845479 Date: Mon, 11 Jun 2012 16:39:40 GMT Call-ID: f0257279-babd0004-0c6a0894-727311e0@172.18.199.91 CSeq: 101 INVITE Allow-Events: presence Reason: Q.850; cause=21 Content-Length: 0 For other protocols, calling leg gets rejected with Q.850 cause = 21 (call rejected). SDP Transparency for Declarative Attributes This feature allows the administrator to specify declarative SDP attributes that are not natively supported to be passed from the ingress call leg to the egress call leg. The administrator also has the option of configuring all unrecognized attributes to the egress leg. If the Unified Communications Manager is not configured to pass all unrecognized attributes transparently and it receives attributes that are not explicitly identified by the administrator to send to the egress leg, then the Unified Communications Manager will drop the attribute from the outgoing SDP similar to previous releases of Unified Communications Manager. Note that for the purposes of identifying which attributes are passed to the egress leg, comparisons are both case sensitive and white space is considered. The administrator is allowed to identify attributes that will be sent to the egress leg in multiple ways. In addition to passing all unrecognized attributes, he or she has the option to choose to specify all property attributes with a particular name, all value attributes with a particular name, or all value attributes with a specific name and specific value. The configuration is done at the level of the SIP Profile by associating an SDP Transparency Profile specifying which attributes should be passed transparently or picking the pre-configured SDP Transparency Profile named "Pass all unknown SDP attributes" to indicate all unrecognized SIP Line Messaging Guide (Standard Edition) for Cisco Unified Communications Manager 40 SIP Standard Line Interface SDP Transparency for Declarative Attributes