The MiVoice Office Call Recorder provides an IP/SIP Extension recording source that provides recording for MiNET handsets and generic SIP base devices (including Phone Manager Desktop and Mobile softphones).
This method of recording calls uses a network port mirror to capture the call audio. It can scale a lot larger than the Record-A-Call recording source and is the only way to record calls made on SIP based extensions.
To configure an MCS server to record this IP/SIP traffic, the following must be configured:
Any RTP audio and SIP traffic that gets passed to the MCS down the mirror port can be recorded.
Once the mirror port(s) have been plugged into the MCS server, the following configuration must be completed to begin recording:
It may be necessary to port mirror multiple network connections in order for the MCS server to receive all the required information.
If a MiVoice Office 250 has a PS-1 server installed then the network connections for both the Base Server and the PS-1 server need to be mirrored to the MCS.
If the MCS is recording calls for extensions on more than one PBX then each PBX's network connection(s) needs to be mirrored to the MCS on a single mirror port.
If there is more than one telephone system then multiple mirror ports need to be mirrored to one port that can be plugged into the MCS server.
Remote extensions (extensions that are not on the same LAN segment as the telephone system) can be recorded by the MCS server using IP/SIP Extension recording, but only in certain circumstances.
SIP Extensions can always be recorded using the IP/SIP Extension recording source, no matter where they are located.The MCS interprets the SIP traffic between the telephone system and the extension to identify the extension involved in the telephone call. This is true even for SIP extensions that are connecting through a MiVoice border Gateway.
This applies to Phone Manager Softphones, both desktop and Mobile.
IP extensions that are connecting through a firewall/router or MiVBG can be recorded as long as each extension has a unique IP Address that can be seen by the MCS server. If there are multiple IP extensions connecting from the same remote location, the MCS server will only be able to see a single IP Address and will not be able to tell the extensions apart.
A mirror of the MBG’s external network interface is required to record the remote IP (not SIP) phones. Ensure that the mirror port on the server is not given an IP address.
If remote IP extensions are connecting through a MiVoice Border Gateway, the MCS must be told about the internal IP Address of the gateway. See the MiVoice Border Gateway section for more information.
Examples:
50 IP Extensions on a separate VLAN | Supported | The MCS will be able to see the IP address of each of the extensions. |
10 IP Extensions home workers, each a different locations | Supported | The MCS server will see a different external IP Address for each extension. |
10 IP Extensions at a remote office | Not Supported | MCS will see the same external IP address for all extensions. |
A home worker with 2 IP Extensions | Not Supported | MCS will see the same external IP address for all extensions. |