zero (0)—If you enter zero (0), the Oracle Communications Session Border Controller will not initiate communication with this session agent (although it will accept calls).

1025 through 65535

The default value is 5060.

enabled | disabled

SIP | H.323

H.323-GW—gateway

H.323-GK—gatekeeper

UDP—Each UDP header carries both a source port identifier and destination port identifier, allowing high-level protocols to target specific applications and services among hosts.

UDP+TCP—If the system determines that routes over TCP and UDP are both available, it initially uses UDP as the transport method. If a failure or timeout occurs in response to the UDP INVITE, the system uses TCP. When you select this transport method, the system always sends INVITEs via UDP as long as it receives a response.

If the available route(s) only use one transport, either UDP or TCP, the system uses that transport method.

DynamicTCP—Dynamic TCP connections are the transport method for this session agent. A new connection must be established for each session originating outbound from the SBC to the session agent. This connection is torn down at the end of a session.

StaticTCP—Static TCP connections are the transport method for this session agent. Once a connection is established, it will remain and not be torn down.

StaticSCTP—SCTP is used as the transport method.

DynamicTLS—Dynamic TLS connections are the transport method for this session agent. A new connection must be established for each session originating outbound from the SBC to the session agent. This connection is torn down at the end of a session.

StaticTLS—Static TLS connections are the transport method for this session agent. Once a connection is established, it will remain and not be torn down.

ANY—support all transport methods .

no value: the egress realm is used unless the local policy dictates otherwise

asterisk (*): keep the egress realm based on the Request URI

enabled | disabled

none—Carrier information will not be added to the outgoing message.

uri-param—Adds a parameter to the Request-URI. For example, cic-XXX.

prefix—Adds the carrier code as a prefix to the telephone number in the Request-URI (in the same manner as PSTN).

proxy—If the Oracle Communications Session Border Controller is a Session Router, the system will proxy the request coming from the session agent and maintain the session and dialog state. If the Oracle Communications Session Border Controller is a Session Director, the system behaves as a B2BUA when forwarding the request.

redirect—The system sends a SIP 3xx reDIRECT response with contacts (found in the local policy) to the previous hop.

proxy—The SIP proxy passes the response back to the previous hop; based on the pfoxy mode of the original request.

recurse—The SIP proxy serially sends the original request to the list of contacts in the Contact header of the response (in the order in which the contacts are listed in the response). For example, if the first one fails, the request will be send to the second, and so on until the request succeeds or the last contact in the Contact header has been tried.

enabled | disabled

When the SIP NAT route home proxy parameter is enabled, the Oracle Communications Session Border Controller looks for a session agent that matches the home proxy address and checks the loose routing value. If loose routing is enabled, a Route header is included in the outgoing request in accordance with RFC 3261. If loose routing is disabled, the Route header is not included in the outgoing request (in accordance with strict routing procedures defined in RFC 2543).

The loose routing value is also checked when the local policy’s next hop value matches a session agent. If loose routing is set to enabled, the outgoing request retains the original Request-URI and Route header with the next hop address.

enabled | disabled

Minimum: 0

Maximum: 999999999

The Oracle Communications Session Border Controller only sends the ping if no SIP transactions (have occurred to/from the session agent within the time period you enter here.

You use a plus sign (+) to add single or multiple trunk groups to the session agent’s list.

When you add a single trunk group, simply use the plus sign (+) in front of the trunk group name and context. Do not use a Space between the plus sign and the trunk group name and context.

For example, you might have already configured a list of trunk groups with the following entries: tgrpA:contextA, tgrpB:contextB, and tgrpC:contextC. To add tgrp1:context1, you would make the following entry:

ORACLE(session-agent)# trunk-group +tgrp1:context1

Your list would then contain all four trunk groups.

When you add multiple trunk groups, simply enclose your entry in quotation marks () or in parentheses (()). While you put spaces between the trunk group name and context entries, you do not use spaces with the plus sign, parentheses or quotation marks.

ORACLE(session-agent)# trunk-group +tgrp1:context1 tgrp2:context2 tgrp3:context3

You use a minus sign (-) to delete single or multiple trunk groups from the session agent’s list.

When you remove a single trunk group, simply use the minus sign (-) in front of the trunk group name and context. Do not use a Space between the minus sign and the trunk group name and context.

For example, you might have already configured a list of trunk groups with the following entries: tgrpA:contextA, tgrpB:contextB, tgrpC:contextC, and tgrp1:context1. To delete tgrp1:context1 from the list, you would make the following entry:

ORACLE(session-agent)# trunk-group -tgrp1:context1

Your list would then contain: tgrpA:contextA, tgrpB:contextB, and tgrpC:contextC.

When you add multiple trunk groups, simple enclose your entry in quotation marks () or in parentheses (()). While you put spaces between the trunk group name and context entries, you do not use spaces with the plus sign, parentheses or quotation marks.

ORACLE(session-agent)# trunk-group -tgrp1:context1 tgrp2:context2

You overwrite (replace) the entire list of a session agent’s trunk groups by entering a list that does not use either the plus (+) or the minus (-) sign syntax.

feature=<value feature>

enabled | disabled

The system performs error checking on your values and prevents you from entering an invalid port number. Enabling this feature requires that you reboot the SBC.

enabled | disabled

SIP | H.323

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).

enabled | disabled

enabled | disabled

The Oracle Communications Session Border Controller also supports the asterisk as part of the From address you configure in your local policies.

This means that for the from-address parameters of a local policy configuration, you can enter values in which an asterisk appears and match them accordingly. You might enter a value that resemble the following example:

The system also supports the asterisk as part of the To address you configure in your local policies.

This means that for the to-address parameters of a local policy configuration, you can enter values in which an asterisk appears and match them accordingly. You might enter a value that resembles the following example:

You can also configure a next hop that has an address of 0.0.0.0, thereby creating a null route. Different from not having a local policy configured (which would trigger Oracle Communications Session Border Controller local policy recursion), this terminates local policy recursion and immediately fails the request. In these cases, the system responds a request with a 404 Not Found.

You can enter a range of values separated by a hyphen, for example U-S. And you can enter multiple values separated by commas, for example M,W,F. You cannot use spaces as separators.

The following route selection action occurs:

The local policy route that corresponds to the a=rtpmap:0 PCMU/8000 attribute is selected because the payload type of 0 in the attribute line matches the first payload type of 0 listed in the m= line. The codec value of PCMU indicated in this selected attribute is used to find the local policy with the media profiles attribute that includes PCMU in the list.

Because the value you enter here is matched against the codec values included in the actual passed SDP, it must correspond to accepted industry-standard codec values.

The following example shows a local policy with a next hop value of the session agent group called gw-sag2.

local-policy
        from-address
                                       *
        to-address
                                       192.168.1.10
        source-realm                   *
        activate-time                  2005-01-20 20:30:00
        deactivate-time                N/A
        state                          enabled
        last-modified-date             2005-01-10 00:36:29
policy-attribute
        next-hop                       SAG:gw-sag2
        realm
        replace-uri                    enabled
        carrier
        start-time                     0000
        end-time                       2400
        days-of-week                   U-S
        cost                           0
        app-protocol
        state                          enabled
        media-profiles

enabled | disabled