Switching VoIP WAN from Access to Trunk

[Guest]

Hello,

We are a customer using a licensed 1+1 installation of FreeSBC operating as Hearst Connect.

Our SBC is v3.0.101, on VMWare ESXi 6.5.

We have multiple Ethernet interfaces: Ctrl0, Ctrl1, Management, VoIP_LAN (internal) and VoIP_WAN (external).

Currently, these are all untagged, with the tagging being done via the hypervisor. We need to add a new interface for a direct link to a provider, and we are looking at doing so by VLAN.

When switching our existing VoIP_WAN from untagged to tagged, is there a preferred order of change?

In ESXi, we should be able to change the port from access to trunk without stopping the VM.

In FreeSBC:

- Should the MTU be changed from 1500 if using tagged?

- When applying a new VLAN, does it take effect immediately or only when doing a configuration activate command?

Anything else we should be aware of?

Regards,

[Guest]

Hi,

- When switching our existing VoIP_WAN from untagged to tagged, is there a preferred order of change?

>> You need to change the vmware configuration first, then when you start the SBC, it will get you back to the original port configuration and you can select the MAC vs interfaces.

- Should the MTU be changed from 1500 if using tagged?

>> I have not seen any issues with this.

- When applying a new VLAN, does it take effect immediately or only when doing a configuration activate command?

>> You need to activate the configuration.

Thanks.