In this section:

A SIP Filter profile is a collection of configurable filter settings for supported SIP headers. Depending on the filter setting for a header, the SBC either relays the SIP messages without parsing the header or parses the header.

For every SIP message associated with the ingress leg of the call, the SBC checks the filter setting for each known type of SIP header. If the filter setting for the header is set to Disabled (default), the header is parsed by the SBC. If a parsing error occurs, the SBC terminates a call. However, if the filter setting for a known header is set to Enabled, the SBC does not parses the header, even if parsing for the header is supported by the SBC. Additionally, all known filtered headers and unknown headers can be transparently relayed without parsing, if the unknown header transparency is Enabled in IP signaling profile.

A SIP Filter profile is not used for the egress leg of a call. The SIP header of the egress leg is populated on the basis of the configuration in the IP Signaling profile and the Transparency profile. For more information on Transparency Profile and SIP header transparency, refer to Transparency Profile and SBC SIP Transparency Implementation Guide respectively.

  • The SBC supports assigning a customized SIP Filter profile to a SIP trunk group. If no alternative SIP Filter profile is configured for a SIP trunk group, the default SIP filter profile applies.
  • Even if the filter setting for an unknown header is set to Disabled, the SBC transparently relays the SIP messages containing that header in the following cases:
    • The flexible header transparency indicates that the particular header should be transparently relayed.
    • The IP Signaling Profile indicates that the particular header should be transparently relayed. To transparently pass all unknown headers, set the transparency of the unknown headers to Enabled in the IP Signaling Profile.

Note
A filtered header of a call in a Gateway-Gateway (GW-GW) scenario is not passed to the egress gateway if that header is known to the egress gateway, even if the "unknown" header transparency is enabled.
 
For example, the P-Asserted-Identity (PAI) header is not passed transparently if the following events occur simultaneously:
  • the PAI is filtered on the ingress
  • the "unknown" header transparency is enabled on the egress gateway
  • the PAI header is known to the egress gateway.
 
To pass the PAI header transparently on the egress gateway, enable transparency for the PAI header through a SIP Filter Profile.

To View SIP Filter Profiles

On the SBC main screen, navigate to All > Profiles > Signaling > SIP Filter Profile

The SIP Filter Profile window opens.

SIP Filter Profile window

To Create a New SIP Filter Profile

To create a new SIP Filter Profile, first create and name the object on this window. After creating and saving the object, you must go to the SIP Filter Profile - Header window to specify the SIP header filter settings within the profile.

  1. Click New SIP Filter Profile. The Create New SIP Filter Profile window opens. 

    Create New SIP Filter Profile window

     

  2. Enter a name for the profile of up to 23 characters.
  3. Click Save.
  4. Go to the SIP Filter Profile - Header window to configure the profile to specify which SIP headers to filter.

To Delete a SIP Filter Profile

To delete a SIP Filter profile:

  1. Click to select the row of the SIP Filter profile you want to delete.
  2. Click the Delete icon (X) at the end of the row.
  3. Confirm the deletion when prompted.

  • No labels