Speakerbus
- Kiss, Mate
- Hina Kouser
Overview
The Speakerbus iSeries recorder integration relies on individual iSeries devices being responsible for the transmission of audio and call event information. The solution can essentially be split into 3 distinct areas.
Audio: Each iSeries device is able to transmit one or more simultaneous audio streams (VoIP) as encoded RTP (Real Time Protocol) over UDP (User Datagram Protocol). The codecs that are supported are G.711 (A-Law or μ-Law), G.729 (Annex A or Annex AB) and G.722.
Call Data Records (CDR): Each iSeries device is responsible for transmitting Call Data Records (CDR) that relate to events happening on that individual device.
iManager Call Data Service (iCDS): iCDS is a supervisory application that runs as a service on Microsoft Server operating systems. It acts as a multiplexer that receives CDR information from multiple iSeries devices and multiplexers the CDR information into a single stream that can be sent to multiple 3rd party devices / applications.
Speakerbus recording features
Certified Speakerbus recording solution
2N recorder configurations
Compatible with trader voice recording data model
Support for VAD (voice activity detection) and media segmentation for long calls
All types of recording mix layouts are supported
Version support
Speakerbus Switch Name & Model | Speakerbus |
|---|---|
Supported Turret Types | iD808, iE801, iD712, SE 708 |
Supported iCDS Versions | 2.1 or later |
If you are on a different version, contact your Speakerbus representative for more information.
Features not available
Silent monitoring only available for Media-Only records
Full / Always-on, Do-not-record, Never-record recording modes only (no On-demand, no Controlled)
Desktop Screen Capture is not available
No support for turret based playback
Configuration
For configuring the system for Speakerbus recording, see Configuring Speakerbus recording.
Speakerbus metadata
The system captures the following metadata specific to Speakerbus calls when CTI messages are available. These fields are available through the standard and the Speakerbus specific custom metadata template.
Metadata Field | Description | Template | Available | Available in | Available in |
|---|---|---|---|---|---|
Start Date | Start date of the conversation | Standard | Yes | Yes | Yes |
Start Time | Start time on the conversation | Standard | Yes | Yes | Yes |
End Date | End date of the conversation | Standard | Yes | Yes | Yes |
End Time | End time of the conversation | Standard | Yes | Yes | Yes |
Duration | Length of the conversation | Standard | Yes | Yes | Yes |
User | Name of the recorded user | Standard | Yes | Yes | Yes |
From | From address | Standard | Yes | Yes | No |
From Info | From name | Standard | Yes | Yes | No |
To | To address | Standard | Yes | Yes | No |
To Info | To name | Standard | Yes | Yes | No |
Direction | Direction of the call from the system perspective, requires configuring internal number/domain patterns | Standard | Yes | Yes | No |
Direction (User) | Direction of the call from the recorded user perspective | Standard | Yes | Yes | No |
From (Verba) | Name of the Verba user associated with the calling party | Standard | Yes | Yes | Yes |
To (Verba) | Name of the Verba user associated with the called party | Standard | Yes | Yes | Yes |
Location | Hostname of the recording server | Standard | Yes | Yes | Yes |
End Cause | Normal, Hold, Transfer, Conference, Device Change | Standard | Yes | Yes | Yes |
Audio Codec | Audio codec of the recorded streams | Standard | Yes | No | Yes |
Video codec | Video codec of the recorded streams | Standard | No | No | No |
Platform Call ID | Unique conversation identifier received from the recorded platform | Standard | Yes | Yes | Yes |
Silence Ratio | Only for media-only records | Standard | No | No | No |
Talkover Ratio | Only for media-only records | Standard | No | No | No |
Longest Silence | Only for media-only records | Standard | No | No | No |
User ID / Agent ID | Trader ID | Standard | Yes | Yes | Yes |
From Device | Recorded turret ID | Standard | Yes | Yes | Yes |
To Device | Recorded turret ID | Standard | Yes | Yes | Yes |
Dialed Number | Original dialed number | Standard | No | No | No |
From IP | IP address of the media source | Standard | Yes | Yes | Yes |
To IP | IP address of the media source | Standard | Yes | Yes | Yes |
From Proxy IP | IP address of the proxy server associated with the calling party | Standard | No | No | No |
To Proxy IP | IP address of the proxy server associated with the called party | Standard | No | No | No |
Source Platform | Speakerbus | Standard | Yes | Yes | Yes |
Conversation Type | Voice | Standard | Yes | Yes | Yes |
Forward Reason | Forward reason for the conversation (e.g. forwarded, transferred, team call, delegated, etc.) | Standard | No | No | No |
Recording failed | Only for media-only records | Standard | No | No | No |
Media Length | Only for media-only records | Standard | Yes | No | Yes |
Media Error | Only for media-only records | Standard | Yes | No | Yes |
Voice Quality | Only for media-only records | Standard | Yes | No | Yes |
Record Type | CDR-Only, Media-Only | Standard | Yes | Yes | Yes |
2N Source | In case of duplicate (2N) recording, records are marked as primary or secondary | Standard | Yes | Yes | Yes |
Device | Handset 1, Handset 2, Handsfree 1, Handsfree 2, Intercom Handsfree, Bridged Handsets | Speakerbus |
| Yes | Yes |
Conference Join/Leave | Conference join/leave events (phone number or Trader ID (display name)) | Marker |
| Yes | No |