The Role of Local Policy
You must configure local policies (and local policy attributes, if necessary) in order for translations between SIP and H.323 to take place. These local policies determine what protocol is used on the egress side of a session. Local policy and local policy attribute configurations make routing decisions for the session that are based on the next hop parameter that you set. The next hop can be any of the following:
- IPv4 address of a specific endpoint
- Hostname or IPv4 address of a session agent
- Name of a session agent group
You can use the application protocol parameter in the local policy attributes configuration as a way to signal the Oracle® Enterprise Session Border Controller to interwork the protocol of an ingress message into a different protocol as it makes its way to its egress destination (or next hop).
For example, if you set the application protocol parameter to SIP, then an inbound H.323 message will be interworked to SIP as it is sent to the next hop. An inbound SIP message would travel to the next hop unaffected. Likewise, if you set the application protocol parameter to H.323, then an incoming SIP message will be interworked to H.323 before the Oracle® Enterprise Session Border Controller forwards it to the next hop destination.
The following example shows a configured local policy and its attributes used for IWF traffic.
local-policy from-address * to-address 444 source-realm * state enabled last-modified-date 2004-04-20 17:43:13 policy-attribute next-hop sag:sag_internal realm internal replace-uri disabled carrier start-time 0000 end-time 2400 days-of-week U-S cost 0 app-protocol SIP state enabled media-profiles