Configuring Session Agents

You configure session agents with:

payload type the Oracle® Enterprise Session Border Controller wants to use for RFC 2833 packets while interworking 2833 and UII.
The default value for this attribute is 0. When this value is zero, the global rfc2833-payload configured in the h323-configuration element will be used instead. For SIP session agents, the payload defined in the SIP interface is used, if the SIP interface is configured with the preferred RFC 2833 mode.
2833 mode
A value of transparent or preferred for the session agent’s 2833 mode will override any configuration in the h323-stack configuration element.

To configure session agents:

In Superuser mode, type configure terminal and press Enter.
```
ORACLE# configure terminal
```
Type session-router and press Enter to access the system-level configuration elements.
```
ORACLE(configure)# session-router
```
Type session-agent and press Enter. The system prompt changes to let you know that you can begin configuring individual parameters.
```
ORACLE(session-router)# session-agent
ORACLE(session-agent)#
```
rfc2833-mode—Set the RFC 2833 mode you want the session agent to use. The default value is none. Valid values are:
- none—RFC 2833 to UII interworking is based on the H.323 stack configuration.
- transparent—The RFC 2833 or UII negotiation is transparent to the Oracle® Enterprise Session Border Controller. This overrides the H.323 stack configuration, even if the stack is configured for preferred mode.
- preferred—RFC 2833 for DTMF transfer is preferred, which is signaled in the TCS. If the endpoint supports 2833, 2833 is used. If not, the H.323 stack configured as preferred will revert back to using UII. This overrides any configuration in the h323-stack even if the stack is configured for transparent mode.
  
  For SIP INFO—RFC 2833 conversion, you can choose:
- none—The 2833-SIP INFO interworking will be decided based on the sip-interface configuration.
- transparent—The session agent behaves the same as it did without the SIP INFO—RFC 2833 conversion feature. The SIP INFO and RFC 2833 translation is transparent to the Oracle® Enterprise Session Border Controller.
- preferred—The RFC 2833 transfer method is the preferred method for sending DTMF, and a telephone event is inserted in the SDP of the outgoing offer. The actual method of transfer, however, depends on the SDP offer/answer exchange that occurs between the Oracle® Enterprise Session Border Controller and remote endpoint. If the remote endpoint supports RFC 2833, the Oracle® Enterprise Session Border Controller performs SIP INFO—RFC 2833 conversion.
- dual—The Oracle® Enterprise Session Border Controller behaves the same as it does when set to preferred mode, and it forwards both the original DTMF mechanism and the translated one to the remote endpoint.
rfc2833-payload—Enter a number that indicates the payload type the session agent will use for RFC 2833 packets while interworking 2833 and UII. The default value is 0. The valid range is:
- Minimum—0, 96
- Maximum—127