Network Configuration Specifics
249
DHCP LEASE TIME
To allow users to move off the local subnet, or to let new users join a subnet, a method is needed
to give up an IP address and to obtain a new address. If a phone is disconnected, it obviously
cannot talk to the DHCP server, so another method is needed to free up unused addresses.
DHCP lease time clears out unused IP addresses and makes them available for new requests.
The timer can be set from a few minutes to months. The default is set to
8 hours
, which
keeps
the amount of checking to see if an IP address is still in use to a reasonable level while providing
adequate recovery time to free up any unused addresses.
The exact lease time to use depends upon the system requirements. If there are plenty of spare
addresses, then the lease can be extended. Some users will specify up to a week to allow a
system to maintain the same IP addresses over a long weekend when power is removed. If
addresses are less available, and phones are more mobile, shorter times are preferred.
3300 TFTP SERVER
The 3300 ICP internal TFTP server is used to provide the IP phones with application software.
This section provides information about the interaction that takes place between the IP phones
and the 3300 TFTP server.
The 3300 TFTP server can handle 400 sessions (this is configurable) simultaneously. If a
particular phone can’t get access to the TFTP server, it will try repeatedly for a number of
seconds, after which it will re-boot and start again.
Some time-out values of interest are:
•
Phones will attempt to access the TFTP server three times before rebooting. Attempts to
access the TFTP server will be made at intervals of 15-30 seconds. This interval is random
to even out the loading on the TFTP server, and to avoid a situation where multiple sets
are attempting to access the TFTP server simultaneously.
•
Inter-packet timeout can be up to four seconds. More reliable transmissions will cause the
inter-packet time to lessen and the transmission of acknowledgement packets and any
retries that might occur will speed up.
•
Phones will attempt to complete the TFTP download in 20 minutes.
When a phone is setting up a TFTP session with the 3300 ICP's internal TFTP server or an
external TFTP server there is an "auto-negotiation" process that they go through to establish
the block size.
The devices will try to establish the block transfer size at 4096 bytes, then they try 2048 bytes,
then they try 1024 bytes and finally they try 512 bytes.
Note:
It is possible to run out of IP addresses with permanent leases, so Mitel
recommends minimizing use of these addresses. For example, a laptop user who roams
from office to office plugs in the laptop, receives a permanent address, and then
disconnects the device. The IP address is never released by the user, and the address
is never handed out to another user because the lease never expires. Eventually the
server can run out of addresses.
Содержание MiVOICE BUSINESS
Страница 1: ...Mitel MiVoice Business RELEASE 7 2 ENGINEERING GUIDELINES ...
Страница 15: ...Chapter 1 ABOUT THIS DOCUMENT ...
Страница 16: ......
Страница 22: ...Engineering Guidelines 8 ...
Страница 23: ...Chapter 2 SYSTEM OVERVIEW ...
Страница 24: ......
Страница 28: ...Engineering Guidelines 14 ...
Страница 29: ...Chapter 3 TYPICAL CONFIGURATIONS ...
Страница 30: ......
Страница 73: ...Chapter 4 PHONES AND VOICE APPLICATIONS ...
Страница 74: ......
Страница 95: ...Phones and Voice Applications 81 Figure 9 ICP Connection Paths and Limitations ...
Страница 100: ...Engineering Guidelines 86 ...
Страница 101: ...Chapter 5 POWER ...
Страница 102: ......
Страница 128: ...Engineering Guidelines 114 ...
Страница 129: ...Chapter 6 PERFORMANCE ...
Страница 130: ......
Страница 135: ...Chapter 7 APPLICATIONS ...
Страница 136: ......
Страница 142: ...Engineering Guidelines 128 ...
Страница 143: ...Chapter 8 EMERGENCY SERVICES ...
Страница 144: ......
Страница 151: ...Chapter 9 IP NETWORKING ...
Страница 152: ......
Страница 167: ...Chapter 10 LICENSING ...
Страница 168: ......
Страница 183: ...Chapter 11 BANDWIDTH CODECS AND COMPRESSION ...
Страница 184: ......
Страница 209: ...Chapter 12 NETWORK CONFIGURATION CONCEPTS ...
Страница 210: ......
Страница 244: ...Engineering Guidelines 230 ...
Страница 245: ...Chapter 13 NETWORK CONFIGURATION SPECIFICS ...
Страница 246: ......
Страница 309: ...Appendix A CAT 3 WIRING ...
Страница 310: ......
Страница 315: ...CAT 3 Wiring 301 Figure 55 CX MX MXe AX and LX Minimum Cable Standard ...
Страница 316: ...Engineering Guidelines 302 ...
Страница 317: ...Appendix B INSTALLATION EXAMPLES ...
Страница 318: ......
Страница 335: ...Appendix C LLDP AND LLDP MED CONFIGURATION EXAMPLES ...
Страница 336: ......
Страница 347: ...Appendix D VOIP AND VLANS ...
Страница 348: ......
Страница 353: ...Appendix E VOIP SECURITY ...
Страница 354: ......
Страница 381: ... ...