FAQ

Some answers to some common questions

How does this work technically?

The Oseyus Gateway captures the calls locally using SPAN and performs the role as a Session Recording Client (SRC) when connected to a Session Recording Server (SRS), usually a cloud-based recording solution. 

There are lots of VoIP phone systems that cannot take advantage of Cloud Recording natively. The Oseyus Gateway bridges that gap.

What are the advantages of SIPREC ?

Call recordings are often stored in the cloud. Being offsite, this technology can form part much larger plan of disaster recovery. Using a cloud-based solution allows the aggregation of recordings over different sites and to be stored centrally.

Is Oseyus really free ?

Absolutely Free.

What are the system requirements?

We recommend a minimum of 2 CPU cores and 2GB RAM.

Does Oseyus collect any data?

No. Oseyus does not collect nor share any data.

How many concurrent calls can be processed ?

This depends on the server specification and the multi-queue network cards installed in the system. If Oseyus starts to reach 100% CPU, a buffer alarm will be apparent in the syslog of the server.  We have tested up to around 450 calls @ 10cps in a virtualised environment on an Intel i9 CPU.

I have downloaded the Virtual Machine version of Oseyus. What next?

This is the VMware version. You will need to deploy the OVA into an ESXi or VMware Workstation environment. 

Can Oseyus be used behind a NAT firewall ?

Yes. In fact we highly recommend you secure Oseyus from all but essential endpoints such as the Session Recording Server (SRS).

What CODECs are supported ?

Oseyus retains any CODEC using passthrough. If SRTP is being used then the RTP payload is encrypted but the CODEC is still retained. 

How can I use Oseyus with Asterisk ?

Option #1. Have Oseyus connected via a SPAN capable switch (preferred). 

Option #2. Install Oseyus on the same server as Asterisk and ensure the RTP ports for Oseyus and Asterisk are different. Set Oseyus SIP Protcol type TCP or TLS so that the two applications do not suffer from port overlap.