H.323 Interfaces
You need to configure H.323 interfaces for inbound and outbound traffic. When you configure H.323 interfaces, you can set:
- Identity and state
- Realm and H.323 interface associations
- H.323 interface settings for the interface’s IPv4 address, RAS and Q. 931 ports, maximum number of Q.931 ports to allow, and any Annex E support you need
- H.323 system resource allocation
H.232 Interfaces Configuration
These are the ACLI parameters that you set:
name Name of the stack
state State of the stack
isgateway Enable the stack to run as a gateway
terminal-alias List of aliases for terminal
ras-port Listening port for RAS request
gk-identifier Gatekeeper's identifier
q931-port Q.931 call signalling port
alternate-transport Alternate transport addresses/ports
q931-max-calls Maximum number of Q.931 calls
max-calls Stack's maximum number of calls
max-channels Maximum number of channels per channel
To access the H.323 interface (h323-stack) and service mode parameters:
Identity and State
To set the identity and state of the H.323 interface:
- name—Enter a name for the H.323 interface using any combination of characters entered without spaces. For example: InternalGK1.
- state—Enter the state of this H.323 interface. The default value is enabled. Valid values are:
-
enabled | disabled
-
Realm and Interface Associations
To link this H.323 interface to a realm and to an outgoing H.323 interface:
- realm-id—Enter the identifier for the realm served by this H.323 interface. This parameter must be configured with a valid identifier value from a realm configuration.
- assoc-stack—Enter the name of the outgoing H.323 interface that you want to associate with the H.323 interface you are configuring. To use realm bridging with static routing, you need to set the outgoing H.323 interface. If you do not enter a name, the Oracle Communications Session Border Controller uses dynamic, policy-based selection using the local policy.
H.323 Signaling Interface Settings
You can set the following parameters to define basic settings for your H.323 interface. This is where you set the IPv4 address for opening sockets, the RAS and Q.931 ports, and the maximum number of Q.931 calls that you want to allow.
This is also where you establish Annex E alternate transport. Annex E supports multiplexed call signaling over UDP so that call volume and performance are potentially enhanced. If you do not configure Annex E support, then this H.323 interface does not listen for Annex E requests.
To configure H.323 interface settings:
- local-ip—Enter the IPv4 address that the H.323 interface uses when opening sockets; this is the default H.323 interface IPv4 address. You must use a valid IPv4 address. For example: 192.168.2.5. The default value is 0.0.0.0.
- ras-port—Enter the number of the port on the local IPv4 address (local-ip) on which the
Oracle Communications Session Border Controller listens for RAS requests. We recommend that you set this parameter to its default, the well-known port
1719. The valid range is:
-
Minimum—0
-
Maximum—65535
If you set this parameter to 0, the Oracle Communications Session Border Controller uses a port assigned by the operating system.
-
- q931-port—Enter the number for the port on the local IP address for the Q.931 call signaling port. We recommend that you leave this parameter set to its default,
1720. The valid range is:
-
Minimum—0
-
Maximum—65535
-
- q931-max-calls—Enter the maximum number of concurrent Q.931 calls you want to allow. The default value is
200; however, this value should be less than the maximum number of calls you set when configuring H.323 features. The valid range is:
-
Minimum—0
-
Maximum—65535
If the number of received Q.931 calls exceeds this number, the H.323 interface returns a busy state.
-
- alternate-transport—Enter a list of one or more Annex E IPv4 address and port combinations for alternate transport. If you do not configure this list, then the Oracle Communications Session Border Controller does not listen for incoming Annex E requests. You must enter the IPv4 address and port combination in the following format, where the two are separated by a colon: IPv4Address:Port.
H. 323 System Resource Allocation
You can set the following parameters to determine how many concurrent calls and concurrent channels you want to allow for each H.323 interface.
To allocate H.323 system resources:
- max-calls—Enter the maximum number of concurrent calls allowed on this H.323 interface. The default value is
200. The valid range is:
-
Minimum—0
-
Maximum—4294967295
-
- max-channels—Enter the maximum number of concurrent channels allowed for each call associated with this H.323 interface. The default value is
6. The valid range is:
-
Minimum—0
-
Maximum—4294967295
The Oracle Communications Session Border Controller checks this parameter on initialization to reserve the appropriate network resources.
-