IWF Privacy for Business Trunking

The Oracle® Enterprise Session Border Controller supports IWF Privacy: Caller Privacy on Unsecure Networks and IWF Privacy: Caller Privacy on Secure Connections, but IWF Privacy for Business Trunking, supports the case where SIP and H.323 PBXs are connected to the core IMS system. Traffic originated at the IP PBXs terminates either at other PBXs or at the PSTN, and includes the possibility of accepting incoming traffic from the PSTN. CLIP and CLIR must be supported for calls in either direction for calls that require interworking between SIP and H.323. Unlike the two features described above, this new feature supports the fact that only a network-based application server has sufficient privilege to assert the identity of the calling party.

Thus, for this feature, the Oracle® Enterprise Session Border Controller does not force privacy. Instead, the implemented feature assumes that the H.323 session agent is an IP PB X, and the Oracle® Enterprise Session Border Controller only indicates to the SIP core that privacy is being requested. In other words, the Oracle® Enterprise Session Border Controller is not required to interwork the H.323 presentation indicator parameter to RFC 3325 by including the P-Asserted-Identity header. The indication to the SIP core that privacy is being requested excludes identity assertion.

You configure this feature using two session agent options:

• allowCPN—Set in the egress H.323 session agent, allows the Oracle® Enterprise Session Border Controller to send the calling party number information element (IE), even when the presentation indicator is set to restricted.
• NoPAssertedId—Set in the ingress H.323 session agent; when the incoming SETUP message has the presentation indicator is set to restricted, instructs the Oracle® Enterprise Session Border Controller to send a Privacy header without the P-Asserted-Identity and not to make the From header anonymous.