Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Panel

In this section:

...

width40%

...

Table of Contents

...

Info

...

titleAbout this Page

...

  • This document details removing the SBC's User Agent or Server Header before transmitting a SIP Message.
  • This document details the removal of a header using the Add Header selection.
  • This Header Manipulation document utilizes the Token function.
iconfalse

Related articles:

...

...

Prerequisites

...

 

...

Requires

Spacevars
0company
SBC1000/2000 Version 2.2

Summary

In certain circumstances, in order to increase network security it may be desirable to remove the UX's User Agent/Server Header before transmitting SIP packets to a downstream peer.

This document detail using the SIP Message Manipulation feature to remove the User Agent/Server header from SIP packets before they are transmitted.

Configure the SBC1000/2000 Header Manipulation

  1. Create a new

...

  1. Message Rule Table entry and populate the first Message Rule as shown below.

    Panel
    borderStylenone

    Caption
    0Figure
    1

...

  1. Create Message Rule Table

...

  1. Image Added

  2. Create a new

...

  1. Message Rule Table entry and populate the first Message Rule as shown below.

    Panel
    borderStylenone

    Caption
    0Figure
    1Remove SERVER Header

...

  1. Image Added

    Tip

    If you wish to also remove any packets with the Server header, create an additional Message Rule entry and select Server from the Header Name pulldown.

  2. Add the SMM Table to the desired Signaling Group.

...

borderStylenone

...

0Figure
1Add SMM Table

...

Important Notes

Info

The SIP Header feature cannot generate a new SIP packet. Only arriving or leaving SIP packets changed via the SIP Header function.

Warning

Care must be exercised when modifying incoming SIP packets, especially with respects to the TO, FROM and RURI headers. Modifying tags, IDs or any other items that define the dialogue or transactions, will likely cause calls to not complete.