For more information about SNMP and MIBs, see the IETF website. The Avaya Custom MIB
for the deskphones is a part of the software distribution file available for download on the
Avaya support site at http://www.avaya.com/support.
Ping and traceroute
All 9600 Series IP Deskphones respond to a ping or traceroute message sent from the call server
switch or any other network source. The call server can also instruct the phone to originate a ping
or a traceroute to a specified IP address. The phone carries out that instruction and sends a
message to the call server indicating the results. For more information about administering an IP
telephone system on Communication Manager, see Administering Avaya Aura
®
Communication
Manager.
IP address and settings reuse
After you successfully register the phone with a call server, the phone saves the IP address and
the parameter values in the non-volatile memory of the phone. The phone can reuse the saved
parameters if the DHCP or HTTP/HTTPS server is not available for any reason after a restart. The
setting for the DHCPSTD parameter indicates whether to keep the IP address if no response is
received for lease renewal. If set to 1 (No) the phone strictly follows the DHCP standard with
respect to giving up IP addresses when the DHCP lease expires. If set to 0 (Yes) the phone
continues using the IP address until it detects reset or a conflict.
Quality of Service (QoS)
For more information about the extent to which your network can support any or all the QoS
initiatives, see your LAN equipment documentation. For information about QoS implications for the
9600 Series IP Deskphones, see Administering QoS on page 41.
All 9600 Series IP Deskphones provide some detail about network audio quality. For more
information, see Network Audio Quality Display on page 30.
IEEE 802.1D and 802.1Q
For more information about IEEE 802.1D and IEEE 802.1Q and the 9600 Series IP Deskphones,
see Administering IEEE 802.1Q on page 41 and Administering a VLAN on page 102. Three bits
of the 802.1Q tag are reserved for identifying packet priority to set any one of the following eight
priorities to a specific packet.
• 7: Network management traffic
• 6: Voice for traffic with less than 10 ms latency and jitter
• 5: Video traffic with less than 100 ms latency and jitter
• 4: Controlled-load traffic for critical data applications
• 3: Traffic meriting extra-effort by the network for prompt delivery, for example, executive email
• 2: Reserved for future use
• 0: The default priority for traffic meriting the best-effort for prompt delivery of the network
• 1: Background traffic such as bulk data transfers and backups
Network requirements
March 2018 Administering Avaya 9608/9608G/9611G/9621G/9641G/9641GS IP Deskphones H.
323 29
Comments on this document? infodev@avaya.com
To Next Page
Loading...
