Configuring SIP Ports

To configure SIP ports:

From sip-interface, type sip-ports and press Enter. The system prompt changes to let you know that you can begin configuring individual parameters.
```
ORACLE(sip-interface)# sip-ports
ORACLE(sip-port)#
```
address—Enter the IP address of the host associated with the sip-port entry on which to listen. For example:
```
192.168.11.101
```
port—Enter the port number you want to use for this sip-port. The default is 5060. The valid range is:
- Minimum—1025
- Maximum—65535
transport-protocol—Indicate the transport protocol you want to associate with the SIP port. The default is UDP. The valid values are:
- TCP—Provides a reliable stream delivery and virtual connection service to applications through the use of sequenced acknowledgment with the retransmission of packets when necessary.
- UDP—Provides a simple message service for transaction-oriented services. 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.
- TLS—See the Security chapter for more information about configuring TLS.
allow-anonymous—Define the allow anonymous criteria for accepting and processing a SIP request from another SIP element.

The anonymous connection mode criteria includes admission control based on whether an endpoint has successfully registered. Requests from an existing SIP dialog are always accepted and processed. The default is all.

The following table lists the available options.
- all—All requests from any SIP element are allowed.
- agents-only—Only requests from configured session agents are allowed. The session agent must fit one of the following criteria:
  - Have a global realm.
  - Have the same realm as the SIP interface
  - Be a sub-realm of the SIP interface’s realm.
    When an agent that is not configured on the system sends an INVITE to a SIP interface, the Oracle® Enterprise Session Border Controller:
  - Refuses the connection in the case of TCP.
  - Responds with a 403 Forbidden in the case of UDP.
- realm-prefix—The source IP address of the request must fall within the realm’s address prefix or a SIP interface sub-realm. A sub-realm is a realm that falls within a realm-group tree. The sub-realm is a child (or grandchild, and so on) of the SIP interface realm.
  
  Only realms with non-zero address prefixes are considered. Requests from session agents (as described in the agents-only option) are also allowed.
- registered—Only requests from user agents that have an entry in the registration cache (regular or HNT) are allowed; with the exception of a REGISTER request. A REGISTER request is allowed from any user agent.
  
  The registration cache entry is only added if the REGISTER is successful. Requests from configured session agents (as described in the agents-only option) are also allowed.
- register-prefix—Only requests from user agents that have an entry in the Registration Cache (regular or HNT) are allowed; with the exception of a REGISTER request. A REGISTER request is allowed only when the source IP address of the request falls within the realm address-prefix or a SIP interface sub-realm. Only realms with non-zero address prefixes are considered.
  
  The Registration Cache entry is only added if the REGISTER is successful. Requests from configured session agents (as described in the agents-only option) are also allowed.