Custom Headers for the Calls Page

You can define custom header fields in which the field string is searched across all SIP messages, to parse and extract the values and display the headers as a new field in the Calls table.

Note:

Starting with Release 5.2, the Custom Headers Addon has been removed from Platform Setup Application and Mediation Engine.
Defining custom headers enables custom monitoring of calls and filtering calls based on your requirements. This feature supports parsing of messages of only SIP protocol. Messages of other protocols like ISUP, ENUM, MEGACO, DIAMETER, MGCP etc are not supported. SIP messages belonging to Calls only are supported, messages related to other functionalities like Registrations, Subscriptions are not supported.
The SIP messages of a call are parsed and searched for the custom header values in the following order. Note that the body of a SIP message is not used to search for custom headers.
  1. All INVITE messages of the call are parsed and if the custom header has been configured, then the header value is saved in the message structure. If the value is not found in INVITE, only then the 180 Ringing/183 Session Progress messages.
  2. 180 Ringing/183 Session Progress messages of the call are parsed and if the custom header is present, the value is saved in the message structure. If the value is not found in 180 or 183 response codes, then the 200 OK is parsed
  3. Finally, the 200 OK (in reply to the INVITE message) is parsed and the corresponding custom header value is saved in the message structure.

Custom headers are displayed in the following pages:

  • Dashboard
  • Calls
  • Devices
  • User Tracking
  • IP Tracking

Note:

By default, the custom header columns are displayed on all Calls panels except the Dashboard. To view on the Dashboard, add the columns manually using the Set Columns option.