Comments
-
Hi @RUnglaube There should be no need to use tagging on the ports connected to the gateways. Thanks for your comment. We're moving away from the core issue of this discussion which is that the Voice VLAN function isn't working. Kind regards Chris
-
Hi @Nebula_Jason This doesn't make any sense. There is no where to specifically configure what VLAn a port should be assigned to from the NCC. Therefore I have to assume that traffic is allocated to a VLAN based on the port settings of Access or Trunk and the PVID. I want port 1 to sit in VLAN1 only and for the switch to…
-
Hi @Nebula_Jason I have added the Admin user account to the organisation "Bishopsgate CF" you requested. Regards Chris
-
Hi @ivers As I have always done the ports are set to access with their PVID = 1 The switch just isn't putting the defined OUI in to the voice VLAN correctly. Using trunk port configuration causes issues with the PCs as they have a chance of picking up an address from the Voice VLAN DHCP server. Thanks, I'm going to have to…
-
Hi @ivers The OUI is correct and when monitoring the client connections the device's MAC is shown in VLAN2, the voice VLAN. Thx
-
I have found a reference to the connectivity requirements. The client device initiates connectivity on TCP port 6667.
-
Morning @Nebula_Dean The MTU of the WAN interface (VDSL) of the SBG3500 is set to the maximum allowed value of 1492 bytes. I'll log a case / support ticket. Thanks Chris
-
Hi @Nebula_Dean The link doesn't clearly define in which direction the ports need to be open. Outbound access from LAN to WAN via the customer firewall is allowed for all protocols. By default you are shown statistics for a 2hr window. Each AP is shown as being Offline for at least 1 minute in each 2hr period; usually a…