A file per channel can be useful for playback, interaction graphics, as well as analytic engines such as speech.Ĭalls are recorded directly from their streams as RTP files. Typically this is a channel for the agent and a channel for the customer, but it is not restricted to just two. If extra security is needed or a VPN is not desirable, SRTP can also be used.Įach channel is recorded as a separate file. Just about any system that uses SIP and RTP can be recorded. RTP traffic is also used for audio recording. RTP traffic is then recorded for the audio.Įvents and metadata are gathered using a Cisco SIP Trunk. Metadata and call events are monitored through a Genesys T-Server. Another available option is to use Avaya CVLAN to watch for call events and setup port mirroring directly to a server for audio recording. Avaya TSAPI can be used to gather metadata and monitor call events and DMCC can be used to record audio. Recording can be handled using two different methods. Recordings continue even during network outages and are uploaded as soon as connections are reestablished. The recording solution can be hosted on servers at your organization or traffic can be directed through a VPN tunnel to be recorded on our servers. The audio recording solution can monitor and record off of a number of common telephony platforms as well as any VoIP system or any audio streams using SIP and RTP. Integrated with Avaya, Genesys, Cisco, or any VoIP system. Record audio through your telephony platform or upload directly via APIs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |