![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||
Solution Type Technical Instruction Sure Solution 1598791.1 : How is Source Based Routing is Implemented within Oracle AP Session Border Controller
In this Document
Applies to:Net-Net 3810 - Version S-Cx6.0.x and laterAcme Packet 3820 - Version S-Cx6.0.x and later Acme Packet 4500 - Version S-Cx6.0.x and later Information in this document applies to any platform. GoalThis document explains how "Source Based Routing" is implemented within an Oracle AP Session Border Controller (SBC). SolutionThe SBC's way of implementing source-based routing (SBR) is as follows: When the SBC needs to route a packet, it consults the route table ('show routes' will provide that info). If the route lookup results in a match that associates with the interface wancom0, wancom1, or wancom2, then the packet is sent using that interface. If the route lookup returns any other resultant interface (i.e., a media interface), then the SBC performs a second query based on the source IP of the packet to determine which egress interface to use. When source-based routing is used, the default gateway (under the system-config) must exist on a front media interface. If the default-gateway is configured to be the gateway associated with wancom0, SBR will be disabled. All lookups that have destinations that are not on the local network of a media interface will result in an association with wancom0. Thus, the packet is sent out using wancom0. SBR is required for TCP based signaling and can be manually enabled on the SD as follows:
Attachments This solution has no attachment |
||||||||||||||
|