SIP Header Removal

Last Updated : Jan 23, 2017 |

Avaya Aura® Session Manager customers can use the Adaptation Modules to remove specific headers from SIP messages. The administrator defines sets of headers to be removed in the ingress (message entering Session Manager) and egress (messages leaving Session Manager) directions. As part of the Adaptation Module processing, Session Manager removes the specified headers from the messages.

A customer could inadvertently include some of the mandatory and/or required headers in the list of headers to be removed. Session Manager will not remove any mandatory SIP headers, even if the headers are included in the set of exempted headers in adaptations.

The header removal feature does not change the adaptation module selection criteria.

Note:

The SIP Header Removal feature only removes headers. The feature does not remove parameters to decrease the header size. Session Manager removes the headers that are either Avaya proprietary or deemed excessive and unnecessary for non-Avaya elements.

The administrator defines a list of SIP headers to be removed during adaptation module processing on the Adaptation Details page. The list of headers to be removed are defined as name-value pairs, with multiple headers separated by a comma. The header names in the list are case-insensitive. The maximum length of the Value field for the headers list is 1024 characters.

The administrator uses the parameters, eRHdrs (egress Remove Headers) and iRHdrs (ingress Remove Headers). The eRHdrs parameter identities the headers to be removed in messages going in the egress direction (messages leaving Session Manager). The iRHdrs parameter identifies the headers to be removed in messages going in the ingress direction (messages entering Session Manager).

As an example: There are two headers: P-Charging-Vector and P-Location headers. To remove these headers from the SIP messages, perform the following:

Note:

If the header removal feature deletes the SIP header Priority: emergency, emergency calls may fail in some cases. Also, if the feature removes the headers such as End Point View and Correlation-ID , some call transfers may fail.