SIP SDP Address Correlation

SIP SDP address correlation ensures that when the Oracle Communications Session Border Controller receives a request containing SDP, the L3 source address of the request is compared against the address in the c-line of the SDP. When the addresses match, the session proceeds as it normally would. If there is a mismatch, the call is rejected with the default 488 status code. You can also configure the code you want to use instead of 488.

This functionality works only with non-HNT users. The value c=0.0.0.0 is an exception and is always processed.

SIP SDP Address Correlation Configuration Address Checking

The sdp-address-check, in the enforcement-profile element can be set to enable the SDP address correlation.

To enable SDP address checking:

1. In Superuser mode, type configure terminal and press Enter.

   ORACLE# configure terminal
   ORACLE(configure)#

2. Type session-router and press Enter.

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

3. Type enforcement-profile and press Enter. The system prompt changes to let you know that you can begin configuring individual parameters.

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

4. Use the ACLI select command so that you can work with the enforcement profile configuration to which you want to add this parameter.

   ORACLE(enforcement-profile) select

5. sdp-address-check—Enable or disable SDP address checking on the Oracle Communications Session Border Controller. The default for this parameter is disabled.

   ORACLE(enforcement-profile)# sdp-address-check enabled

6. Save and activate your configuration.

   If a mismatch occurs and you want to reject the call with a status code other than 488, you set the code you want to use in the local response code map entries.

SIP SDP Address Correlation Configuration Mismatch Status Code

To apply a new status code to a SDP address correlation mismatch:

1. In Superuser mode, type configure terminal and press Enter.

   ORACLE# configure terminal
   ORACLE(configure)#

2. Type session-router and press Enter.

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

3. Type local-response-map and press Enter. The system prompt changes to let you know that you can begin configuring individual parameters.

   ORACLE(session-router)# local-response-map
   ORACLE(local-response-map)#

4. Type entries and press Enter. The system prompt changes to let you know that you can begin configuring individual parameters.

   ORACLE(local-response-map)# entries
   ORACLE(local-response-map-entry)#

   From here, you can view the entire menu for the local response map entries configuration by typing a ?.

5. local-error—Enter sdp-address-mismatch for which to apply the new status code.
6. sip-status—Set the SIP response code to use.
7. sip-reason—Set the SIP reason string you want to use for this mapping.

   ACMEPACKET(local-response-map-entry)# local-error sdp-addressmismatch
   ACMEPACKET(local-response-map-entry)# sip-status 403
   ACMEPACKET(local-response-map-entry)# sip-reason sdp address mismatch

8. Save and activate your configuration.

SIP SDP Address Correlation Configuration Enforcement Profile

To apply an enforcement profile to a realm:

1. In Superuser mode, type configure terminal and press Enter.

   ORACLE# configure terminal
   ORACLE(configure)#

2. Type media-manager and press Enter.

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

3. Type realm-config and press Enter. The system prompt changes to let you know that you can begin configuring individual parameters.

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

4. enforcement-profile—Enter the name of the enforcement profile you want to apply to this realm.

   ORACLE(realm-config)# enforcement-profile profile1

5. Save and activate your configuration.