Supported Configurations

The following table shows the different MiVoice Office 250 configurations and which are supported by MiVoice Office Call Recorder. Some configurations are only supported by specific recording methods, in these scenarios, recording methods can be mixed so that the customer’s requirements can be met.

 

Configuration	Record-A-Call*	IP/SIP Extension (IP)	IP/SIP Extension (SIP)
Single Node – Local Extensions	Supported*	Supported	Supported
Multi-Node – Same Location	Not Supported	Supported	Supported
Multi-Node – Different Locations	Not Supported	Not Supported	Not Supported
Remote Extensions, 1 per remote location (Port Forwarding)	Supported*	Supported	Supported
Remote Extensions, >1 per remote location (Port Forwarding)	Supported*	Not Supported	Supported
Remote Extensions (MiVoice Border Gateway)	Supported*	Supported	Supported

* Record-A-Call recording is not supported on SIP extensions

 

The following section breaks down each configuration and explains how the MiVoice Office Call Recorder needs to be implemented. Remember, the Supported Features listed in the previous section still applies to all the configurations below.

Single Node – Local Extensions

Record-A-Call – Supported, IP/SIP Extension - Supported

This is a basic setup, both methods are supported. The supported features list needs to be checked. If the customer is going beyond the 8 port Record-A-Call limit or needs to record SIP extensions, a port mirror will need to be configured.

Multiple Networked MiVoice Office 250 Systems (at one location)

Record-A-Call – Not Supported

The Record-A-Call method cannot currently be used to record calls on more than one node at a time. There are some cross-node scenarios (conference) that do not work correctly with RecordA-Call. The Record-A-Call should not be used on networked systems with this release.

IP/SIP Extension - Supported

The IP/SIP Extension method on a single MiVoice Office Application Suite can be used to record calls across multiple nodes. In this scenario, all NICs for all nodes need to be mirrored to the MiVoice Office Application Suite server’s mirror port.

Multiple Networked MiVoice Office 250 Systems (at different locations)

Record-A-Call – No, IP/SIP Extension (IP) – Not Supported

This configuration is not supported at all. Currently a single MiVoice Office Application Suite is required for this type of configuration port mirroring across a WAN is not supported. Future releases of MiVoice Office Application Suite will support networked systems across multiple sites.

Remote Extensions (behind NAT, Port Forwarded through a Firewall)

Record-A-Call – Supported

Any number of remote extensions (remember the 8-concurrent recording limit, you could have more than 8 extensions) can be configured for recording with the Record-A-Call method. There are no restrictions on having more than 1 extension at a remote location so satellite offices can be supported with this setup.

IP/SIP Extension (SIP) – Supported

Any number of remote SIP extensions can be configured for recording with the IP/SIP Extension recording method. The SIP is interpreted by the system to determine what traffic is for which extension.

IP/SIP Extension (IP) – Supported, no more than 1 extension behind each remote IP Address

Remote IP extensions (e.g. 53xx) can be recorded using the IP/SIP Extension method if there is no more than 1 extension behind each remote public IP address. For example, 5 home workers with a single phone each, all presenting different public IP addresses is fine. A remote office with 5 phones however would not work because they would all be presenting the same public IP address. For remote office scenarios like this, use the Record-A-Call method.

Remote Extensions (through MBG)

Record-A-Call – Supported

Any number of remote extensions (remember the 8-concurrent recording limit, you could have more than 8 extensions) can be configured for recording with the Record-A-Call method when connected through an MBG. There are no restrictions on having more than 1 extension at a remote location so satellite offices can be supported with this setup.

IP/SIP Extension (SIP) – Supported

Any number of remote SIP extensions can be configured for recording with the IP/SIP Extension recording source. The SIP is interpreted by the system to determine what traffic is for which extension.

IP/SIP Extension (IP) – Supported, no more than 1 extension behind each remote IP Address **(see note)

Remote IP extensions can be recorded using the IP/SIP Extension method when they are connected through an MBG. A mirror of the MBG’s external network interface is required to record the remote phones.

Mixing Recording Methods

Where required, Record-A-Call and IP/SIP Extension recording methods can be used at the same time to meet a customer’s requirements. For example, if a customer has remote and internal extensions, Record-A-Call could be used to record the remote extensions where IP/SIP Extension recording would not work. IP/SIP Extension recording could be used for the internal extensions ensuring that all calls are recorded

 

 

** Specific IP Extension Remote recording requirements

1. The Minet devices public IP address need to be programmed against the recorded device.
   This cannot be automatically detected as the IP traffic is encrypted between the MBG and the remote phone (this does not happen when an MBG is not involved). If a phone is moved from external to internal (or internal to external) then the IP will need to be updated each time.
2. SRTP must be disabled in the MBG for the device otherwise the audio traffic cannot be decrypted and will playback as static.
3. For both internal and external IP extension call recording to work there needs to be a single mirror port that provides traffic from BOTH the external WAN interface of the MBG and the internal LAN interface of the PBX.
4. The MBG IP address should be configured in the Site Settings -> Phone Systems -> MiVoice Border Gateway section