In order for Echo to collect call audio information, it must be installed on a computer that has an additional network card connected to a mirrored port on a local managed network switch.
The primary network card would have its IP configuration set up so that it is visible on the data LAN. This allows playback of recordings by authorised users, as well as remote control of the Echo server, such as Remote Desktop Connection, if required.
The secondary network card would have its IP configuration set up so that it is visible on the SIP/telephone network. This allows mirrored traffic to be sent to it for the purpose of monitoring and recording by the Echo server.
Echo will happily record SIP calls in a virtualised environment such as VMware® or Microsoft® Hyper-V™;.
CPU | Small deployments (<30 channels)Intel Dual-Core i5 2.4Ghz or equivalent Medium deployments (<50 channels)Intel Quad-Core i5 3Ghz or equivalent Large deployments (>50 channels)Intel Xeon (8 cores +) 3Ghz |
Memory | Small deployments (<30 channels)4GB Medium deployments (<50 channels)8GB Large deployments (>50 channels)16GB |
Hard disk | 250GB Hard disk space = 44,000 channel hours 500GB Hard disk space = 88,000 channel hours 700GB Hard disk space = 132,000 channel hours 1TB Hard disk space = 176,000 channel hours |
Network card | 1 x Network card (LAN) 1 x Network card (SIP/Telephony)
Realtek PCI GBE Family Controller D-Link DGE-528T Gigabit Ethernet Adapter Realtek PCIe FE Family Controller, Intel(R) 82566DM-2 Gigabit Network Connection, Intel(R) 82576 Gigabit Dual Port Network TRENDnet, TEG-PCITXR 32-bit 10/100/1000Mbps PCI ADAPTER Intel(R) PRO/1000 PM Network Connection AMD PCNET Family PCI Ethernet Adapter HP NC112i 1-port Ethernet Server Adapter Intel(R) Gigabit CT Desktop Adapter Broadcom NetXtreme Gigabit Ethernet |
Operating system | Windows 7/8/8.1/10 Windows Server 2008 R2/2012/2016 |
Audio codecs | All popular VOIP protocols
|