VLAN ID Discovery over DHCP - Revision history

Hans.zeiner: /* VLAN Discovery */

2024-01-16T08:49:05Z

‎VLAN Discovery

Hans.zeiner: /* Example configuration for Vendor Classes */

2024-01-16T08:48:00Z

‎Example configuration for Vendor Classes

Hans.zeiner: /* Example configuration for Option 43 */

2024-01-16T08:46:16Z

‎Example configuration for Option 43

Hans.zeiner at 08:45, 16 January 2024

2024-01-16T08:45:25Z

Hans.zeiner: /* VLAN Discovery */

2024-01-16T08:41:59Z

‎VLAN Discovery

Bhuertgen: /* Example configuration for Vendor Classes */

2017-03-27T12:24:15Z

‎Example configuration for Vendor Classes

Bhuertgen: /* Example configuration for Vendor Classes */

2017-03-27T12:16:56Z

‎Example configuration for Vendor Classes

Sven: /* Example configuration for Option 43 */ removed unnecessary fill bytes in tag 1 and fillbytes after tag 2. Replaced screenshot to match the new description. Now wiki is showing the same information as admin documentation

2012-05-25T06:37:46Z

‎Example configuration for Option 43: removed unnecessary fill bytes in tag 1 and fillbytes after tag 2. Replaced screenshot to match the new description. Now wiki is showing the same information as admin documentation

Sven: /* Example configuration of an Cisco Switch */ removed unnecessary fill bytes in tag 01

2012-05-25T06:30:13Z

‎Example configuration of an Cisco Switch: removed unnecessary fill bytes in tag 01

Sven: /* DHCP Option 43 tags */ removed unnecessary fill bytes for tag 01: Siemens. Wiki now shows the same information as admin documentation

2012-05-25T06:28:02Z

‎DHCP Option 43 tags: removed unnecessary fill bytes for tag 01: Siemens. Wiki now shows the same information as admin documentation

@@ Line 40: / Line 40: @@
 == VLAN Discovery ==
-The feature '''VLAN ID Discovery''' allows OpenStage, Desk Phone IP and Desk Phone CP phones to automatically determine the Voice VLAN ID using DHCP. This is accomplished by the standard '''DHCP Option 43''', Vendor Specific Info.
+The feature '''VLAN ID Discovery''' allows optiPoint, OpenStage, Desk Phone IP and Desk Phone CP phones to automatically determine the Voice VLAN ID using DHCP. This is accomplished by the standard '''DHCP Option 43''', Vendor Specific Info.
 After the Voice VLAN ID is acquired, the phone will then use 802.1Q tagging to connect to this VLAN. Unify phones use DHCP by default to determine the Voice VLAN. This way, a phone set to the factory default settings should start up on the network with a DHCP delivered IP address and with the correctly configured Voice VLAN automatically straight out of the box.

@@ Line 128: / Line 128: @@
 Untagged Subnet is 172.16.133.0 and tagged (with [[VLAN]] ID 200) it is 192.168.133.0.
-The optiPoint 420 should get the VLAN ID 200 via VLAN Discovery.
+The phone should get the VLAN ID 200 via VLAN Discovery.
-Please make sure that the untagged packets of the first DHCP Discover cycle reach the DHCP server that provides the vendor specific options for the optiPoint. Most likely you will have to use Relay Agents/DHCP Helper.
+Please make sure that the untagged packets of the first DHCP Discover cycle reach the DHCP server that provides the vendor specific options for the phone. Most likely you will have to use Relay Agents/DHCP Helper.
 The options for the 172.16.133.0 subnet have to contain

@@ Line 107: / Line 107: @@
 * The Unify phone should get the VLAN ID 10 via VLAN Discovery.
-Please make sure that the untagged packets of the first DHCP Discover cycle reach the DHCP server that provides the vendor specific options for the optiPoint. Most likely you will have to use Relay Agents/DHCP Helper.
+Please make sure that the untagged packets of the first DHCP Discover cycle reach the DHCP server that provides the vendor specific options for the phone. Most likely you will have to use Relay Agents/DHCP Helper.
 The options for the 192.1.22.0 subnet have to contain the option 43.

@@ Line 1: / Line 1: @@
-{{Breadcrumb|0|0|{{dev-en}}|optiPoint}}
+{{Breadcrumb|0|0|{{dev-en}}|OpenScape Desk Phone CP}}
 With the introduction of the feature '''VLAN ID Discovery''' the following changes have to be made, if you want to use this feature on [[DHCP]].
@@ Line 105: / Line 105: @@
 * Untagged Subnet is ''192.1.22.0'' and tagged (with [[VLAN]] ID 10) it is ''10.1.22.0''.
-* The optiPoint 420 should get the VLAN ID 10 via VLAN Discovery.
+* The Unify phone should get the VLAN ID 10 via VLAN Discovery.
 Please make sure that the untagged packets of the first DHCP Discover cycle reach the DHCP server that provides the vendor specific options for the optiPoint. Most likely you will have to use Relay Agents/DHCP Helper.
@@ Line 133: / Line 133: @@
 The options for the 172.16.133.0 subnet have to contain
 * vendor class '''OptiPoint''' (ASCII Value '''OptiPoint''') with option 1 & 2 for OptiPoint 410/420
-* vendor class '''OptiIpPhone''' (ASCII Value '''OptiIpPhone''') with option 1 & 2 for OpenStage
+* vendor class '''OptiIpPhone''' (ASCII Value '''OptiIpPhone''') with option 1 & 2 for OpenStage, Desk Phone IP and Desk Phone CP
 The data format of the vendor classes is following:
@@ Line 143: / Line 143: @@
 For DLS Use the options for the 192.168.133.0 tagged VLAN subnet have to contain
-* vendor class '''OptiIpPhone''' option 1 & 3 for OpenStage
+* vendor class '''OptiIpPhone''' option 1 & 3 for OpenStage, Desk Phone IP and Desk Phone CP
 * Option Code 01: String   '''Siemens'''
 * Option Code 03: String   '''sdlp://172.16.180.211:18443''' (DLS IP Address)

@@ Line 40: / Line 40: @@
 == VLAN Discovery ==
-The feature '''VLAN ID Discovery''' allows optiPoint and OpenStage phones to automatically determine the Voice VLAN ID using DHCP. This is accomplished by the standard '''DHCP Option 43''', Vendor Specific Info.
+The feature '''VLAN ID Discovery''' allows OpenStage, Desk Phone IP and Desk Phone CP phones to automatically determine the Voice VLAN ID using DHCP. This is accomplished by the standard '''DHCP Option 43''', Vendor Specific Info.
-After the Voice VLAN ID is acquired, the phone will then use 802.1Q tagging to connect to this VLAN. Siemens optiPoint phones use DHCP by default to determine the Voice VLAN. This way, a phone set to the factory default settings should start up on the network with a DHCP delivered IP address and with the correctly configured Voice VLAN automatically straight out of the box.
+After the Voice VLAN ID is acquired, the phone will then use 802.1Q tagging to connect to this VLAN. Unify phones use DHCP by default to determine the Voice VLAN. This way, a phone set to the factory default settings should start up on the network with a DHCP delivered IP address and with the correctly configured Voice VLAN automatically straight out of the box.
-Because VLAN ID Discovery requires DHCP, it is not available when using a static IP address configuration on the phone.  When an optiPoint phone has been configured to use DHCP for VLAN Discovery (the default setting), the following process occurs:
+Because VLAN ID Discovery requires DHCP, it is not available when using a static IP address configuration on the phone.  When an Unify phone has been configured to use DHCP for VLAN Discovery (the default setting), the following process occurs:
 * First the Application sends out a DHCP Discover message to find out if there is a DHCP server available.

@@ Line 147: / Line 147: @@
 * Option Code 03: String   '''sdlp://172.16.180.211:18443''' (DLS IP Address)
 It must be possible to connect from the VLAN 200 to the DLS Server.
 <gallery mode="traditional">
@@ Line 155: / Line 154: @@
- To do the above automatically, execute it at your Windows 2008 R2 DHCP Server.
+To do the above automatically, execute it at your Windows 2008 R2 DHCP Server.
+<pre>
 netsh Dhcp Server Add Class "OptiIpPhone" "Unify OptiIpPhone VoIP Options" 4f707469497050686f6e65 1 b
@@ Line 166: / Line 164: @@
 netsh Dhcp Server Add Optiondef 3 "DLS Server" STRING 0 vendor="OptiIpPhone" comment="DLS Server" sdlp://172.16.180.211:18443
-</code>
+</pre>

@@ Line 148: / Line 148: @@
 It must be possible to connect from the VLAN 200 to the DLS Server.
-[[Image:Vendorclass-DHCP-Option3.jpg|left|thumb|300px|Values for Vendor Classes using a German Windows 2003 R2 DHCP server, as described in the configuration example.]]
+<gallery mode="traditional">
 Additional Screenshots on english Windows Server 2003 R2 with VLAN ID 504:
-[[Image:DHCP_Vendor_Class_OptiPoint_Code01.PNG|left|thumb|200px]]
+ To do the above automatically, execute it at your Windows 2008 R2 DHCP Server.
-[[Image:DHCP_Vendor_Class_OptiPoint_Code02.PNG|left|thumb|200px]]
-[[Image:DHCP_Vendor_Class_OptiPoint.PNG|thumb|200px]]
+<code>
-[[Image:DHCP_Vendor_Class_Scope.PNG|thumb|250px]]
+netsh Dhcp Server Add Class "OptiIpPhone" "Unify OptiIpPhone VoIP Options" 4f707469497050686f6e65 1 b
 == References ==

@@ Line 104: / Line 104: @@
 === Example configuration for Option 43 ===
-* Untagged Subnet is ''192.1.22.0'' and tagged (with [[VLAN]] ID 20) it is ''10.1.22.0''.
+* Untagged Subnet is ''192.1.22.0'' and tagged (with [[VLAN]] ID 10) it is ''10.1.22.0''.
-* The optiPoint 420 should get the VLAN ID 20 via VLAN Discovery.
+* The optiPoint 420 should get the VLAN ID 10 via VLAN Discovery.
 Please make sure that the untagged packets of the first DHCP Discover cycle reach the DHCP server that provides the vendor specific options for the optiPoint. Most likely you will have to use Relay Agents/DHCP Helper.
@@ Line 114: / Line 114: @@
 * Option Code for the first encapsulated option: '''01''' (always)
-* Length of the first data field: '''0A''' (always 10 Byte)
+* Length of the first data field: '''07''' (always 7 Byte)
-* Encapsulated data for option code 1: '''53 69 65 6D 65 6E 73 00 00 00''' (always Siemens plus 3 Fill bytes)
+* Encapsulated data for option code 1: '''53 69 65 6D 65 6E 73''' (always Siemens)
 * Option Code for the second encapsulated option: '''02''' (always)
 * Length of the first data field: '''04''' (always 4 Bytes)
-* Encapsulated data for option code 2 (VLAN ID): '''00 00 00 14''' (Example for VLAN ID 20)
+* Encapsulated data for option code 2 (VLAN ID): '''00 00 00 0A''' (Example for VLAN ID 10)
 If this data format for option 43 is not matching or not send by the DHCP server the phone will start with the manual configured VLAN ID, if Layer 2 QoS is enabled. If Layer 2 QoS is not enabled the phone will start without using a VLAN ID.
-[[Image:dhcp-option43.gif|300px|Values for option 43 using a German Windows 2000 DHCP server, as described in the configuration example.]]
+[[Image:dhcp-option43-neu.png|300px|Values for option 43 using a German Windows 2000 DHCP server, as described in the configuration example.]]
 === Example configuration for Vendor Classes ===

@@ Line 95: / Line 95: @@
     network 192.168.37.0 255.255.255.224
     default-router 192.168.37.1
-    option 43 hex 010a.5369.656d.656e.7300.0000.0204.0000.0065.031a.7364.6c70.3a2f.2f39.332e.3132.322e.3131.342e.3936.3a31.3834.3433.ff
+    option 43 hex 0107.5369.656d.656e.7302.0400.0000.6503.1a73.646c.703a.2f2f.3933.2e31.3232.2e31.3134.2e39.363a.3138.3434.33ff
+!
 ip dhcp pool de-msr-Voice

@@ Line 63: / Line 63: @@
   '''Tag''' '''Len''' '''Content (Example)'''
-  0a  '''5369656d656e73'''000000
+  07  '''5369656d656e73'''
   04  000000'''65'''
   1a  73646c703a2f2f3'''9'''3'''3'''2E3'''1'''3'''2'''3'''2'''2E3'''1'''3'''1'''3'''4'''2E3'''9'''3'''6'''3a3138343433
@@ Line 72: / Line 72: @@
 * Tag 01 specifies the vendor (here: ''Siemens'')
-** Tag: '''01'''; Length: '''0a'''; Value: '''Siemens'''; Three fill bytes '''000000''' (Hex)
+** Tag: '''01'''; Length: '''07'''; Value: '''Siemens'''
 * Tag 02 specifies VLAN ID of Voice VLAN (here: ''101'')
 ** Tag: '''02'''; Length: '''04'''; Value: '''65''' (Hex)