H.323 Alternate Routing Configuration

This section describes how to enable H.323 alternate routing. There is a new parameter, and the behavior of the pre-existing response-tmo and connect-tmo parameters change when you enable this feature on your system.

To enable this feature, you need to set the new alternate-routing parameter in the global H.323 configuration to recur. The other option for this parameter is proxy, which means that the Oracle® Enterprise Session Border Controller performs in the way it did prior to Release 4.1, i.e. try only the first matching local policy next hop that it finds.

You configure H.323 alternate for the global H.323 configuration.

To enable H.323 alternate routing:

1. In Superuser mode, type configure terminal and press Enter.

   ORACLE# configure terminal

2. Type session-router and press Enter.

   ORACLE(configure)# session-router

3. Type h323 and press Enter.

   ORACLE(session-router)# h323

4. alternate-routing—Enable or disable H.323 alternate routing. If you want to keep the pre-4.1 behavior where the Oracle® Enterprise Session Border Controller only tries one matching local policy next hop, leave this parameter set to its default value proxy. Valid values are:

   • recur | proxy

5. response-tmo—Enter the time in seconds for the response time-out (or T303 timer). This is the amount of time allowed to elapse during which the Oracle® Enterprise Session Border Controller should receive a response to its Setup message. If the first response to the Oracle® Enterprise Session Border Controller’s Setup is a callProceeding, then the Oracle® Enterprise Session Border Controller should receive an Alerting or Connect message before this timer (now T303*2) elapses.

   The default for this parameter is 4. The valid range is:

   • Minimum—0

   • Maximum—999999999

6. connect-tmo—Enter the time in seconds for the connect time-out (or T301 timer). This is the amount of time allowed to elapse during which the Oracle® Enterprise Session Border Controller should receive a Connect message.

   For alternate routing, this parameter is also used to limit the number of next hops that are tried and the length of time they are tried in case the first next hop fails. The call needs to be established before this timer expires; the call will fail after maximum of 5 retries.

   The default for this parameter is 32.

   • Minimum—0

   • Maximum—999999999