QMS Configuration

  • Edit the PBX type of the Recording Service to be type "SipRec" (unless using one of the Avaya variants, see the Avaya Configuration section for more information).

  • Enter a Sip Port number for the SIP traffic between the border device and QMS. Default 5060.

  • Enter the Starting Audio Port number where QMS will receive the forked media from the border device.

  • Enter the maximum number of audio ports available for use in the Audio Port Limit field. Each RTP stream occupies two ports as even numbered ports carry the audio and odd numbered ports are reserved for RTCP traffic associated with the media stream on the prior port. Additionally, each call with have at least two RTP streams associated with it so a call will normally occupy 4 ports.

  • QMS defaults to using the UDP protocol for SipRec conversations. If the SBC in the installation prefers to use TCP, SBCEnableTCPSipChannel and SBCTCPSipChannelPort must be configured on any Call Recorder as Advanced Settings on the Recording Service tab. SBCEnableTCPSipChannel is set to TRUE and SBCTCPSipChannelPort names the port number for the TCP traffic.

  • QMS defaults to responding to SipRec messaging on the IP address the messaging was received. If the QMS host has a public and private address and the SBC requests are routed to the private IP but the private IP isn’t addressable, SiprecUsePublicSTUNIp can be enabled in the Advanced Settings on the Recording Service tab. If SiprecUsePublicSTUNIp is set to TRUE the SIP Contact header, SDP origin field and SDP connection field will all reflect the STUN-discovered public IP.

  • Optionally, QMS can be configured to treat SipRec based recordings for a range of Sip URIs as inbound or outbound with respect to the recorded user by defining appropriate trunk groups using SiprecInboundTrunkRanges or SiprecOutboundTrunkRanges in the Advanced Settings section of the Recording Service tab. A trunk group definition is a regular expression to match a Sip user and an optional domain. For example setting SiprecInboundTrunkRanges to "sip:600{1}\d domain:external.net". Would have QMS treat calls arriving for users with Sip URIs 6000 - 6009 @ external.net as inbound calls. Multiple trunk groups can be defined with a | 'pipe' delimiter between each.

  • In some contact center integrations where a recording may be preceded by a consultation call it may be desirable to have the flagging data attached to the consultation call get propagated to the subsequent recording. This behavior is optionally enabled by adding an appSettings line to the CallRecording.exe.config file on the Recording Server. For example, add key="EnableSipRecConsultFlagCopy" value="3" would enable the behavior with a call to the same agent within 3 seconds of the prior call receiving the treatment.

  • Installations involving the Enghouse CC product, MS Teams and Touchpoint create recording duplication in a number of transfer scenarios. Enabling EnableStrictNotAnchorRecording in the Advanced Settings section of the Recording Service tab cures these scenarios. The setting has been tested against a Sonus/Ribbon SBC but would likely be beneficial for a Cisco SBC too. The setting isn’t applicable where the SBC is a Mediant device.

  • Users administered to record at this recording server will require a SIP uri be defined, there is nothing else in QMS administration that’s specific to a SipRec installation. General QMS configuration information is available in the QMS User Guide.