...
width | 40% |
---|
Panel |
---|
...
title | Table of Contents |
---|
...
Table of Contents |
---|
In this section:
|
...
Info |
---|
...
title | About this Page |
---|
...
...
| ||
Related articles: |
...
Tip |
---|
Requires Sonus SBC1000/2000 Version 2.2 |
...
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.
Create a new
...
Message Rule Table entry and populate the first Message Rule as shown below.
Panel | |||||
---|---|---|---|---|---|
| |||||
|
...
|
...
Create a new
...
Message Rule Table entry and populate the first Message Rule as shown below.
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
|
...
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. |
Add the SMM Table to the desired Signaling Group.
...
borderStyle | none |
---|
...
0 | Figure |
---|---|
1 | Add SMM Table |
...
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. |