Hello Giles , The Supported header is used to tell the far end the extensions to SIP that the UAC would like to use during the session. The privacy extension as defined in RFC 3323 and extended to support asserted ids in RFC 3325 defines mechanisms by which various level of privacy can be provided. Privacy is not used to block the callid , but for protection of various header's/fields such as from , contact etc contained in SIP messaging which may give idea about the end user. If the UAC mentions privacy as a supported extension list in the invite , but does not include any privacy header itself on the INVITE , then your B2BUA/Control server should not block the user id. However , many products caller id as a optional service and you may need to actually provision caller id against your MGCP line/endpoint before you can see the caller id displayed on the RQNT/phone display. This is implementation/product dependent. Regards , Sayan
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Everist, Giles Sent: Friday, September 10, 2004 12:34 PM To: [EMAIL PROTECTED] Subject: [Sip-implementors] Supported Header with Privacy Extension All/Anyone, When a UAC sends an INVITE with a Supported header and a Privacy extension do proxy servers in the path have a responsibility to hide information or implement some privacy measures. What I am seeing is a B2BUA/Control Server which is controlling MGCP endpoints not displaying the Calling Party Number in the RQNT even though it is displayed in the >From header in the ingress INVITE (a form of Caller ID blocking). I don't know of any documentation relating to SIP to MGCP interworking but my guess is that it shouldn't be any different from a SIP endpoint. >From what I understand of the Supported header, it is used to tell the UAS what headers it would like to see in the response messaging. The use of the Privacy header may be used for CallID blocking, but I don't think this should be the case with a Supported header with a Privacy extension. I have pasted the header in question below. Any help on this would be greatly appreciated. Supported: privacy Thanks in advance, Giles Everist _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors Confidentiality Notice The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. If you are not the intended recipient, please notify the sender at Wipro or [EMAIL PROTECTED] immediately and destroy all copies of this message and any attachments. _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
