Session Agent Group Configuration

To configure session agent groups:

  1. Access the session-agent-group configuration element.
    ORACLE# configure terminal
    ORACLE(configure)# session-router
    ORACLE(session-router)# session-group
    ORACLE(session-agent-group)# 
    
  2. group-name—Enter a unique name for the session agent group in Name format.
  3. description—Optional. Enter descriptive information about the session agent group.
  4. state—Enable or disable the session agent group on the Oracle® Enterprise Session Border Controller. The default value is enabled. Valid values are:
    • enabled | disabled

  5. application-protocol—Indicate the signaling protocol you want to use with the session agent group. The default value is SIP. The valid values are:
    • SIP | H.323

  6. strategy—Indicate the session agent allocation strategy you want to use. The strategy you chose selects the session agents that will be made available by this session agent group. The default value is hunt. The valid values are:
    • hunt—Selects session agents in the order in which they are listed. For example, if the first agent is online, working, and has not exceeded defined constraints, all traffic is sent to the first agent. If the first agent is offline or if it exceeds a defined constraint, the second agent is selected. If the first and second agents are offline or exceed defined constraints, the third agent is selected. And so on through the list of session agents.

    • roundrobin—Selects each session agent in the order in which they are listed in the destination list, selecting each agent in turn, one per session.

    • leastbusy—Selects the session agent that has the fewest number of sessions relative to the maximum sessions constraint (for example, lowest percent busy) of the session agent element. The Least Busy Calculation is the result of dividing the number of active calls for a session agent by the max-sessions parameter within the session-agent element configuration. If the default max-session parameter value issued for a session agent (0), the result of the Least Busy Calculation will be 0. The Least Busy SAG Strategy will route a session to the session agent with the lowest resulting Least Busy Calculation percentage. If multiple session agents have the lowest percentage, the foremost session agent in the Session Agent Group dest parameter will be used.

    • propdist—Based on programmed, constrained session limits, the Proportional Distribution strategy proportionally distributes the traffic among all of the available session agents. Sessions are distributed among session agents based on the max-outbound-sessions value in each session agent. The sum of max-outbound-sessions for every session-agent within a session group equates to 100% and the max-outbound-sessions value for each session-agent represents a % that total. Sessions are proportionally allocated to session agents based on their individual session agent max-outbound-sessions value, as a % of the total max-outbound-sessions for the group.

    • lowsusrate—The Lowest Sustained Rate strategy routes to the session agent with the lowest sustained rate of session initiations/invitations (based on observed sustained session request rate).

  7. destination—Identify the destinations (session agents) available for use by this session agent group.

    A value you enter here must be a valid IP address or hostname for a configured session agent.

  8. trunk-groupEnter trunk group names and trunk group contexts to match in either IPTEL or custom format. If left blank, the Oracle® Enterprise Session Border Controller uses the trunk group in the realm for this session agent group. Multiple entries are surrounded in parentheses and separated from each other with spaces.

    Entries for this list must one of the following formats: trgp:context or trgp.context.

  9. sag-recursion—Enable this parameter if you want to use SIP SAG recursion for this SAG. The default value is disabled. Valid values are:
    • enabled | disabled

  10. stop-sag-recurse—Enter the list of SIP response codes that terminate recursion within the SAG. Upon receiving one of the specified response codes, such as 401 unauthorized, or upon generating one of the specified response codes internally, such as 408 timeout, the Oracle® Enterprise Session Border Controller returns a final response to the UAC and stops trying to route the message. This includes not attempting to contact higher-cost SAs.
    You can enter the response codes as a comma-separated list or as response code ranges.
  11. Type done to save your configuration.