Ring Central Eventide NexLog DX

General - Call recording via Ring Central Eventide NexLog DX

Recording for Ring Central is a non-traditional (Non-Standard) configuration.

Ring Central Spans their own traffic through a port and then to the recorder.

We start with the Configuration of the Capture NIC.

Verify and confirm the IP to be assigned to the Ring Central Capture NIC.

Due to the non-traditional (Non-Standard) delivery of the call flows, we will create the NIC using a static IP.

The following screen shots are an example of NIC Configuration.

We will navigate to the Networking>Network Interfaces Tab.




As we have already configured the Recorder IP via the first NIC, we now select another “Downstream” NIC (In this exampled eth2).

Set the NIC Type to “Static”.


Add the IP that Ring Central has configured to send the traffic to the Address field.

(In this example 10.30.128.81)

The Netmask will be the same as the Recorder Address Netmask.

(In this example 255.255.255.0)

The Gateway will be filled in with 0.0.0.0 as the recorder can only have one Gateway.

(We will be configuring a route add to direct traffic to the appropriate board)

The Broadcast address should have been given to us previously, however if we have not received it, we can easily obtain the correct broadcast address by utilizing an online Broadcast Calculator.

It is a good idea to check any Broadcast address provided to us to confirm it is correct.

(In this example we have used 10.30.128.255)

 

Once you have configured the Capture NIC be SURE to select Save.

 

 

Recording Board Configuration

 

For Ring Central we will navigate to the Recording>Recording Interfaces Tab.

We should have already confirmed the number of available channels by reviewing the System>License Keys Tab, therefore we will select “Add Virtual Recording Interface”, this will open the “ADD INTERFACE” Tab.

Fill in the appropriate number of channels in the Channel Count field.

In the IP Recording field, select the “Down Arrow” to browse the available Virtual Recording Interfaces available. We will select “Generic SIP Phones (SPAN)” Template.

The Generic SIP Phone SPAN Template will appear, and should be displaying the “Template” Tab.

(If the Template TAB is not selected, please select it)

 





We will configure the following fields:

Ethernet Device = The eth number of the Capture NIC we configured above. Also, by default the NIC’s “Internal Name” will populate along with its corresponding eth number.

(In this example we see that eth2 is the Capture NIC we have previously configured, and enp6s0f0 has auto populated as it signifies the recorders “Internal Name”.

 

Multiple Conversations field will be set to “Record RTP Streams for Active SIP CallID Only.”

 

As previously mentioned, Ring Central utilizes a non-standard configuration, therefore we will now

Configure the “SIP Port” filed with 5090.

(The usual default port for SIP is 5060, however this will not work, so be sure to confirm you have used 5090)

Next, we configure the “RTP Ports” field with the range of 5090-65535. This is the port range we expect to see the appropriate traffic.

The “Stream Recording Mixing Mode” will be set to “Mix Together”.

As previously mentioned, Ring Central SPANS their traffic to a single port which then carries the traffic to the Capture NIC via a single RJ45 CAT 4 or 5 cable. Due to the nature of this procedure, we cannot utilize IP addresses for each channel, as often the IP’s may be “Stripped” from the Traffic. Therefore, we will utilize the MAC Addresses of each Channel (Phone).

(Since we are aware of Ring Centrals Non-Standard configuration and delivery, we should have discussed this with the customer and obtained the correct MAC addresses via the Project Workbook)

At the bottom of the “Template” page you will see the following instructions:

“For Each Channel, Enter the IP Address (eg xxx.xxx.xxx.xxx) or MAC Address (eg xx:xx:xx:xx:xx:xx) of the phone to record”

Take care to verify that we have used a colon in between MAC Address Octets as using a “Dot” will not work in Linux. (Example: 64:16:7f:a3:cf)

We are finished with the configuration of the “Template” Tab.

Next select the “EDIT BOARD” Tab, which will reveal the Board Edit page.



For Channel Count we should see that the same number we have used in the “Add Virtual Interface” step will be populated in its field.

(In this example the Channel Count is 24)

 

We can skip the next two fields: Recording Interface Alias, and Configuration Text.

(These Fields would be used in more advanced or complex configurations, however in this article we will not be covering it.)

Next, we will populate the “Inactivity Timeout(mins) field. The usual default setting will be 120.

Be sure to “check” the box for “Enable”.

You will notice a notification box to the right side of the section Titled “IP Recording Interface Configuration” with the following message:

“These values are populated by the template They only need to be modified here for advanced usage to modify template defaults. Note that if the template is reapplied, some of these settings may be reset to default values and need to be modified again.”

Based upon this information, we should not need to make any changes or additions to this section. We should however review for accuracy.

PCAP Devices = Should be populated with the “eth” number (in this example eth2) corresponding to the Capture Nice we Configured in the first section.

PCAP Ports = We should see the Non-Standard port of 5090, followed by the port range we previously configured on the “Template” Tab. (In this example: 5090,5090-65535.)

PCAP Defragment = Should have a checkmark

PCAP VLan = Should have the default selection of “Record Non-VLAN Tagged Traffic”

Packet Filtering = Should normally default to “Kernel Performs MAC, IP, and Port Filtering.

TCP Packet Filtering = Should normally be the default “Do Not Discard TCP Packets”

IP Version = Should normally be set to IPv4 Only

TCP Segment Reordering = Should normally Include a Check Mark.

Advanced = This field will normally be left blank.

 

We should now Select the “SAVE Button” or else you will need to start over.

Congratulations, you have now completed the Configurations needed to Record Ring Central!

 

Although we have completed our configuration, we will need to test our work by partnering with the appropriate person(s) to initiate test calls.

Prior to initiating these test calls, we should first confirm that we have placed a check mark in the “Enable Recording Interface” filed on the “Edit Board” Tab of our “Generic SIP Phone SPAN Template” and navigate to Utilities>Packet Capture and configure this utility to match our Capture Nic to initiate a Capture Sequence. Upon completion of our test calls we may need this capture to confirm or troubleshoot our results.

 

Final Congratulations!  If we have followed the above steps accurately, we should now see Recorded Test Calls within MediaWorks!