How to Add LAN Segments to Evolution

This article explains how to add an additional LAN segment to your Evolution PBX

A typical LAN consist of a single Class C Subnet, I.E. 192.168.2.X or 172.30.1.X, where X represents the final octet of the IP Address.

In a more complex networking environment, such as one where a VPN exist between branch offices, or MPLS is present, there may be multiple LAN segments.

A good example of this is demonstrated below:

Here we have 2 phones at a remote site (172.16.31.0 LAN) that are connected via a VPN to the Main Office where the PBX is (172.16.36.0 LAN)

In this scenario, Evolution will be configured so it accepts local traffic from 172.16.36.X.  With the addition of a remote office over a VPN, and hence another LAN segment, you will need to tell the PBX that traffic from 172.16.31.X is also 'local traffic'.

To do that, log into the Evolution GUI and browse to Administration → Node Settings → Select the Appropriate Node.

When the Node settings display, note that the PBX is already configured for the 172.16.36.0 LAN as seen in the 'Local Network' field.

In order to configure Evolution to also accept traffic from the 172.16.31.0 LAN, we need to edit this value using a ~ (tilde) to separate LAN segments.

Multiple similar or dissimilar LAN segments can each be separated by a tilde to accommodate the Local network environment.

How Evolution is configured above/Configured for a single LAN:

172.16.36.0/255.255.255.0

How we need to configure it for both LANs defined in the VPN diagram example above:

172.16.36.0/255.255.255.0~172.16.31.0/255.255.255.0

Additional examples:

172.16.36.0/255.255.255.0~172.16.31.0/255.255.255.0
10.10.10.0/255.255.255.0~192.168.2.0/255.255.255.0~172.16.3.0/255.255.255.0
192.168.1.0/255.255.255.0~192.168.3.0/255.255.255.0

After you have entered the appropriate segments for your subjective installation, be sure to disable 'Self Discovery'.  If this step is missed your changes may be reverted by Evolution's self discovery utility.