Information Systems:VoIP LAN configuration - Revision history

Aaront at 20:41, 24 June 2020

2020-06-24T20:41:19Z

Aaront at 22:46, 16 October 2019

2019-10-16T22:46:28Z

Aaront at 22:29, 16 October 2019

2019-10-16T22:29:00Z

Aaront: Created page with "Use this as a reference whenever configuring LAN/SWITCH/INTERFACES for VoIP determine what port the local port is plugged into a the server switch level - here is a link to t..."

2019-10-16T21:16:12Z

Created page with "Use this as a reference whenever configuring LAN/SWITCH/INTERFACES for VoIP determine what port the local port is plugged into a the server switch level - here is a link to t..."

New page

Use this as a reference whenever configuring LAN/SWITCH/INTERFACES for VoIP

determine what port the local port is plugged into a the server switch level
- here is a link to the LAN infrastructure http://elearning.unipharm.local:8080/mediawiki/index.php/Information_Systems:LAN_infrastructure_at_uniPHARM

you can use these tables to navigate to the switches in the network.

← Older revision		Revision as of 20:41, 24 June 2020
Line 22:		Line 22:

	do not place ports into untagged vlans other then vlan 1 , it will become an access port and be unusable.		do not place ports into untagged vlans other then vlan 1 , it will become an access port and be unusable.
		+
		+
		+	When a supported yealink voip phone is plugged into our network it receives and address through DHCP when it is connected to the main VLAN (VLAN1). The DHCP servers are the domain controllers, and yes, they will give out an address in the 172.30.19.x-172.30.20.x range. However, this DHCP server also has Option 132 configured. Which is, when the MAC address of the device requesting an IP address matches a certain pattern (Yealink MACs), it will send Option 132 along with the DHCP response. So the phone gets a response, sets its address to 19., then it interprets Option 132. This one instructs the device to set its VLAN to the value provided VLAN6.

@@ Line 6: / Line 6: @@
 you can use these tables to navigate to the switches in the network.
-switches operate on layer 2 which is mac adresses , so in order to find where your local switch is plugged into the stack switch you need the mac adress of the local switch.
+switches operate on layer 2 which is mac addresses , so in order to find where your local switch is plugged into the stack switch you need the mac adress of the local switch.
 navigate to the unit and check the port that it is plugged into , In the option tree select VLAN and modify

← Older revision		Revision as of 22:29, 16 October 2019
Line 5:		Line 5:

	you can use these tables to navigate to the switches in the network.		you can use these tables to navigate to the switches in the network.
		+
		+	switches operate on layer 2 which is mac adresses , so in order to find where your local switch is plugged into the stack switch you need the mac adress of the local switch.
		+
		+	take the mac ( root ) adress and log into the interface for the stack switch .
		+	in the bridge option tree expand adress database and use the find option to find where it is plugged in.
		+
		+	navigate to the unit and check the port that it is plugged into , In the option tree select VLAN and modify
		+
		+	from here you are looking at VLAN ID and seeing what ports are tagged and untagged with the VLAN IDs that are available.
		+
		+	From here you may see what ports are tagged/untagged and members of which vlan. In the case of tagging a port for VoIP , Tag the port for VLAN 6
		+
		+	do not place ports into untagged vlans other then vlan 1 , it will become an access port and be unusable.