Avaya Configuration

There are two hybrid QMS SipRec variants that are available on Avaya IPO platforms.

Avaya IP Office (TAPI) with SipRec

This solution has call control delivered from an Avaya TSP (TAPI Service Provider) and audio delivered from a border device via SipRec.

  • Edit the PBX type of the Recording Service to be type "SipRec TAPI".

  • Enter the Sip Port, Starting Audio Port and Audio Port Limit using the information in the SipRec QMS Configuration section.

  • Install the Avaya TSP on the QMS Recording Server. Refer to the Avaya IP Office Configuration section for more information.

Refer to the Avaya IP Office Integration Guide for more information about this platform.

Avaya IP Office Web Services with SipRec

This solution has call control delivered from Avaya IP Office Web Services and audio delivered from a border device via SipRec.

  • Edit the PBX type of the Recording Service to be type "SipRec using Avaya IP Office Web Services".

  • Enter the Sip Port, Starting Audio Port and Audio Port Limit using the information in the SipRec QMS Configuration section.

  • Enter the PBX Host Name, API Port, Username and Password fields using the information in the Avaya IP Office Web Services QMS Configuration section.

Refer to the Avaya IP Office Web Services Integration Guide for more information about this platform.

Optional Configuration

These two integrations have audio being delivered by an SBC and call control being delivered by either Tapi or IPO Web Services eventing. Audio streams are matched to calls by comparing the metadata delivered by the SBC to the metadata contained in the call control eventing. In some environments the metadata from a source may have prefixed data that the other source doesn’t. For example, the metadata delivered by the SBC may carry a country code where the metadata from the call control layer doesn’t have the country code, this difference prevents QMS from matching the audio to the call control. QMS can optionally be configured to ignore named prefixes when matching audio streams to call control events.

Ignored prefixes can be configured by adding an appSettings line to the CallRecording.exe.config file on the Recording Server. For example:

  • add key="IgnoredMetadataPrefixesKeyName" value="041, 88"

This setting would have QMS ignore prefixes "041" and "88". Any changes to IgnoredMetadataPrefixesKeyName require a Call Recording Service restart to take effect.