SIP Enforcement Profile and Allowed Methods

For this feature, you use a configuration called an enforcement profile that allows you to configure sets of SIP methods that you want applied to: the global SIP configuration, a SIP interface, a realm, or a SIP session agent. The enforcement profile is a named list of allowed methods that you configure and then reference from the configuration where you want those methods applied.

SIP Enforcement Profile Configuration

To use the enforcement profile, you need configure it with a name and the list of SIP methods you want to designate as allowed. Then you need to configure the global SIP configuration, a SIP interface, a realm, or SIP session agent to use the set.

Setting Up and Enforcement Profile

To set up an enforcement profile:

In Superuser mode, type configure terminal and press Enter.
```
ORACLE# configure terminal
ORACLE(configure)#
```

Type session-router and press Enter.

ORACLE(configure)# session-router
ORACLE(session-router)#

Type enforcement-profile and press Enter.

ORACLE(session-router)# enforcement-profile
ORACLE(enforcement-profile)#

name—Enter the name for the enforcement profile. This parameter has no default, but you must note it so that you can apply this set of allowed SIP headers in: the global SIP configuration, a SIP interface, a realm, or SIP session agent.
```
ORACLE(enforcement-profile)# name EnfProfile1
```
allowed-methods—Enter a list of SIP methods that you want to allow for this set. The default value is none. Valid values are:
- INVITE | REGISTER | PRACK | OPTIONS | INFO | SUBSCRIBE | NOTIFY | REFER | UPDATE | MESSAGE | PUBLISH
  
  To enter multiple methods for the list, type the parameter name followed by a space, then the names of all methods you want to include each separated by a only a comma and in capital letters.
```
ORACLE(enforcement-profile)# allowed-methods INVITE,REGISTER,PRACK
```
Save and activate your configuration.

Applying an Enforcement Profile

You can apply an enforcement profile to: the global SIP configuration, a SIP interface, a realm, or SIP session agent. This section shows you how to do all four. Remember that if you are adding this functionality to a pre-existing configuration, you need to select the configuration you want to edit.

To apply an enforcement profile to the global SIP configuration:

In Superuser mode, type configure terminal and press Enter.
```
ORACLE# configure terminal
ORACLE(configure)#
```

Type session-router and press Enter.

ORACLE(configure)# session-router
ORACLE(session-router)#

Type sip-config and press Enter.

ORACLE(session-router)# sip-config
ORACLE(sip-config)#

enforcement-profile—Enter the name of the enforcement profile you want to apply to the global SIP configuration.
Save and activate your configuration.

To apply an enforcement profile to a SIP interface:
In Superuser mode, type configure terminal and press Enter.
```
ORACLE# configure terminal
ORACLE(configure)#
```

Type session-router and press Enter.

ORACLE(configure)# session-router
ORACLE(session-router)#

Type sip-interface and press Enter.

ORACLE(session-router)# sip-interface
ORACLE(sip-interface)#

enforcement-profile—Enter the name of the enforcement profile you want to apply to this SIP interface.
Save and activate your configuration.

To apply an enforcement profile to a SIP session agent:
In Superuser mode, type configure terminal and press Enter.
```
ORACLE# configure terminal
ORACLE(configure)#
```

Type session-router and press Enter.

ORACLE(configure)# session-router
ORACLE(session-router)#

Type session-agent and press Enter.

ORACLE(session-router)# session-agent
ORACLE(session-agent)#

enforcement-profile—Enter the name of the enforcement profile you want to apply to this session agent.
Save and activate your configuration.

To apply an enforcement profile to a realm:
In Superuser mode, type configure terminal and press Enter.
```
ORACLE# configure terminal
ORACLE(configure)#
```

Type media-manager and press Enter.

ORACLE(configure)# media-manager
ORACLE(media-manager)#

Type realm-config and press Enter.

ORACLE(media-manager)# realm-config
ORACLE(realm-config)#

enforcement-profile—Enter the name of the enforcement profile you want to apply to this realm.
Save and activate your configuration.

Enforcement Profile Configuration with subscribe-event

This section shows you how to configure an enforcement profile with a subscribe-event configuration. Remember that you can set up multiple subscribe-event configurations to correspond with the event types you want to control. It also shows you how to apply these limitations to a realm.

Setting Up Subscribe Dialog Limits

Setting up subscribe dialog limits means setting up an enforcement profile. For the sole purpose of setting up the subscription event limits, you only need to configure the name parameters and then as many subscribe-event configurations as you require. The enforcement profile has other uses, such as SIP SDP address correlation, so only configure the parameters you need.

To configure subscribe dialog limits:

In Superuser mode, type configure terminal and press Enter.
```
ORACLE# configure terminal
ORACLE(configure)#
```

Type session-router and press Enter.

ORACLE(configure)# session-router
ORACLE(session-router)#

Type enforcement-profile and press Enter.

ORACLE(session-router)# enforcement-profile
ORACLE(enforcement profile)#

name—Enter a name for this enforcement profile. You will use this name later when you apply the enforcement profile to a realm; it is the value you enter into the enforcement-profile parameter in the realm configuration.
Still in the enforcement profile configuration, type subscribe-event and press Enter.
```
ORACLE(enforcement profile)# subscribe-event
ORACLE(subscribe-event)#
```
event-type—Enter the SIP subscription event type for which you want to set up limits. You can also wildcard this value (meaning that this limit is applied to all event types except the others specifically configured in this enforcement profile). To use the wildcard, enter an asterisk (*) for the parameter value.

By default, this parameter is blank.

Note:
The value you enter must be configured as an exact match of the event type expected in the SIP messages (except for the wildcard). Further, the value conforms to the event type BNF specified in RFC 3265.
max-subscriptions—Enter the maximum number of subscriptions allowed to a user for the SIP subscription event type you entered in the event-type parameter. Leaving this parameter set to 0 (default) means that there is no limit. You can set this parameter to a maximum value of 65535.
If you are entering multiple subscribe-event configurations, then you save them each by using the ACLI done command and then repeat Steps 6 and 7 to configure a new one. If you do not save each, then you will simply overwrite the first configuration repeatedly.
```
ORACLE(subscribe-event)# done
```
When you finish setting up subscribe-event configurations and have saved them, exit to return to the enforcement profile configuration.
```
ORACLE(subscribe-event)# exit
```
You also need to save the enforcement profile configuration.
```
ORACLE(enforcement profile)# done
```

Applying an Enforcement Profile to a Realm

For the Oracle® Enterprise Session Border Controller to use the limits you have set up, you need to apply them to a realm.

To apply an enforcement profile to a realm:

In Superuser mode, type configure terminal and press Enter.
```
ORACLE# configure terminal
ORACLE(configure)#
```

Type media-manager and press Enter.

ORACLE(configure)# media-manager
ORACLE(media-manager)#

Type realm-config and press Enter. If you are adding this feature to a pre-existing realm configuration, you will need to select and edit your realm.
```
ORACLE(media-manager)# realm-config
ORACLE(realm-config)#
```
enforcement-profile—Enter the name of the enforcement profile you want to apply to this realm. This value corresponds to the name parameter in the enforcement profile configuration. This parameter has no default value.
Save and activate your configuration.