Logging-Tag

The Logging-Tag header may be specified by an application during SET-PARAMS and GET-PARAMS requests.

This optional header can be used to assign an application specified tag, or string, to an individual session.

Reasons for specifying or using such a tag is not defined with the MRCP specification, however typically this is commonly used within logs to identify a specific session, since MRCP session identifiers may not be the same as identifiers used for other sessions associated with ASR and TTS sessions - in other words, the Session IDs for ASR and TTS resources are often different than those used by a related telephony platform call, so using Logging-Tag can assist in determining which sessions are related.

This Logging-Tag header is available within both MRCPv1 and MRCPv2 sessions and can contain strings or numeric characters as needed.

Logging-Tag within CDR Logs

A new feature of Call Detail Record logging was introduced with LumenVox version 15.0, which records a number of attributes for each Media Server session. Among these is the optional Logging-Tag attribute that may be specified by applications within the MRCP session. Having these values logged out to the CDR log allows users the option of more readily identifying which sessions are associated with Logging-Tag values.