Aastra Telecom 41-001343-02 manual Precedence, Sub Description Rule Option/Code, 4095

Network Settings

•If Line 2 is configured with a valid outbound proxy, the phone will retain the configured Line 2 outbound proxy and ignore the Global SIP profile. This allows for Line 2 to be registered to another service with another outbound proxy if required.

•If Line 2 is configured for another service but no outbound proxy is wanted/required, administrators should not leave the outbound proxy as undefined (i.e. 0.0.0.0) as the phone will use the outbound proxy located in the Global SIP pro- file. Instead, administrators should specify the proxy/registrar’s address as the outbound proxy.

•If the parameter is enabled, but the server does not have an outbound proxy configured, DHCP Option 120 is ignored and the phone will behave as if the parameter is disabled.

•As Option 120 does not support port numbers directly, if a non-standard port (i.e. other than 5060) is required, this must be set using the configuration parameter “sip outbound proxy port” or by the use of DNS SRV in which case “sip outbound proxy port” must be set to 0.

Enabling/Disabling DHCP Option 120 Using the Configuration Files

Use the following procedure to enable/disable DHCP Option 120 using the configuration files.

Configuration Files

For specific parameters you can set in the configuration files, see Appendix A, the section, “DHCP Option Settings” on page A-12.

Using Option 132 (802.1P VLAN ID) and Option 43 to Transfer VLAN ID Assignment Using DHCP

There are now two ways of transporting the VLAN ID parameter in the Dynamic Host Configuration Protocol (DHCP):

•By DHCP Option 43 (vendor specific information)

•By DHCP Option 132 (802.1P VLAN ID)

When the phone receives the VLAN ID from the DHCP and the value is different from the one used by the phone to trigger the DHCP request, the phone reboots and then sends a new DHCP request in the new VLAN. The phone will remember the VLAN ID obtained by DHCP options so that on a reboot, the phone will send a DHCP request using the correct VLAN.

If using DHCP Option 43 to transfer VLAN ID assignment the following sub-options are utilized. Additionally, the corre- sponding rules must be followed:

Sub-	Description	Rule
Option/Code

08ID string to enable the use of the VLAN identity in sub-option/code 09. Must be specified to avoid conflict with other vendors.

Must be the 16-byte character string “Aastra{space}Telecom{space}{space}” (i.e. Aastra Telecom followed by two space characters).

16-byte hex equivalent: 4161737472612054656c65636f6d2020

09	VLAN ID value	Must be 4 bytes, whereas the first and second byte must be 0x00, and the third
		and fourth bytes encompass the VLAN ID. The valid range of the VLAN ID is 1 -
		4095.

For example, a VLAN ID of 100 (in dec) is 00 00 00 64 in hex.

Alternatively, administrators can use the “dhcp option 132 vlan id enabled” parameter to enable the VLAN ID assign- ment transfer using DHCP feature. Option 132 provides the same functionality as Option 43 but the data format of the VLAN ID value must be 2 bytes, whereas the first and second bytes encompass the VLAN ID (the valid range of the VLAN ID being 1 - 4095).

Precedence

•LLDP values should have precedence over the DHCP

•DHCP values should have precedence over the configuration files

•DHCP should have precedence over the Local values (configured by the Local MMI of the phone)

•DHCP Option 43 should have precedence over DHCP Option 132

41-001343-02 REV04 – 05.2014 4-9