What is the drawback of configuring Policy-Based Realm Bridging (PBRB) without the assistance of Header Manipulation Rules (HMRs)?
Click on the arrows to vote for the correct answer
A. B. C. D. E.C.
Policy-Based Realm Bridging (PBRB) is a feature in Oracle Communications Session Border Controller (SBC) that enables communication between different SIP domains, or realms, by mapping SIP messages from one realm to another. When configuring PBRB, Header Manipulation Rules (HMRs) can be used to modify the SIP headers in the messages to ensure correct routing.
The drawback of configuring PBRB without the assistance of Header Manipulation Rules (HMRs) is that topology hiding is incomplete. Topology hiding is a feature in SBCs that ensures that the internal network topology of the SIP domains is not exposed to external networks. Without HMRs, PBRB may not be able to fully mask the internal topology of the SIP domains, making them vulnerable to attacks such as SIP scanning and reconnaissance.
Additionally, configuring PBRB without HMRs may require a home realm to be defined, which can make privacy harder to achieve. A home realm is the realm that is used to authenticate users and devices within a SIP domain. Defining a home realm can reveal information about the internal topology of the SIP domain, which can compromise privacy.
Enabling SIP-NAT bridging may also be required when configuring PBRB without HMRs. SIP-NAT bridging is a complex process that involves modifying the SIP headers in messages to enable communication between SIP domains with different IP addresses. This can lead to configuration errors and performance issues if not implemented correctly.
In summary, the drawback of configuring PBRB without the assistance of HMRs is that topology hiding is incomplete, which can compromise the security and privacy of the SIP domains. The configuration may also require defining a home realm and enabling SIP-NAT bridging, which can be complex and prone to errors.