Emergency Services
131
EMERGENCY SERVICES
Emergency services such as 911 are available from most phone devices according to how the
class of service and restrictions for the phone are set. The default is to enable 911 emergency
service access.
Currently, the following devices do not fully support Enhanced 911 (E911) operation:
•
Hot Desk users
•
IP consoles
•
Teleworker Solution users
•
MiCollab Client and MiCollab Client Softphone users
•
Any other mobile IP phones or phones that are carried from location to location.
LOCATION INFORMATION
MiVoice IP Phones report network connectivity information. This information can be used to
provide location information to the Emergency Services database. When an IP phone is moved
to a new physical location the phone reports the new location information to the ICP and the
CESID directory is automatically updated.
IP phone move detection is accomplished by analyzing data reported from the Spanning Tree
Protocol/Rapid Spanning Tree Protocol or the Cisco Discovery Protocol.
NETWORK CONFIGURATION
E911 support and Location Change Indication is provided in the IP network by identifying the
L2 port MAC address to which the IP phone is connected and cross-referencing it to a physical
location stored in the Emergency Responder database.
The IP phones determine the MAC addresses of the L2 ports to which they are connected by
using Spanning Tree Protocol (STP)/Rapid Spanning Tree Protocol (RSTP), or Cisco Discovery
Notes:
1.
Emergency call routing in a Teleworker environment is supported provided specific
conditions are met. For details see “Teleworker devices” on page 133.
2.
For mobile phones (which do not fully support E911 operation) it is necessary to
keep the system administrator informed and the location database current when the
phone is moved if emergency services are required.
3.
Subsequent to UCA Server Release 4.0, all
MiCollab Client
clients and
MiCollab Client
Softphones will work exclusively through the
MiCollab Client
Server to establish calls.
This will enhance operation of applications on the server and reduce information
transfer and loading on the ICP. This configuration does not provide resiliency
operation for the
MiCollab Client
and
MiCollab Client
Softphone. Therefore, if resilient
operation is required it is recommended that hard physical phones be used in parallel
with a
MiCollab Client
. When
MiCollab Client
Softphones are used in a system, steps
should be taken to ensure that there is adequate access to devices that can still
establish external emergency calls. Follow local country or administration guidelines
for percentage of phones that require external access.
Summary of Contents for MiVOICE BUSINESS
Page 1: ...Mitel MiVoice Business RELEASE 7 2 ENGINEERING GUIDELINES ...
Page 15: ...Chapter 1 ABOUT THIS DOCUMENT ...
Page 16: ......
Page 22: ...Engineering Guidelines 8 ...
Page 23: ...Chapter 2 SYSTEM OVERVIEW ...
Page 24: ......
Page 28: ...Engineering Guidelines 14 ...
Page 29: ...Chapter 3 TYPICAL CONFIGURATIONS ...
Page 30: ......
Page 73: ...Chapter 4 PHONES AND VOICE APPLICATIONS ...
Page 74: ......
Page 95: ...Phones and Voice Applications 81 Figure 9 ICP Connection Paths and Limitations ...
Page 100: ...Engineering Guidelines 86 ...
Page 101: ...Chapter 5 POWER ...
Page 102: ......
Page 128: ...Engineering Guidelines 114 ...
Page 129: ...Chapter 6 PERFORMANCE ...
Page 130: ......
Page 135: ...Chapter 7 APPLICATIONS ...
Page 136: ......
Page 142: ...Engineering Guidelines 128 ...
Page 143: ...Chapter 8 EMERGENCY SERVICES ...
Page 144: ......
Page 151: ...Chapter 9 IP NETWORKING ...
Page 152: ......
Page 167: ...Chapter 10 LICENSING ...
Page 168: ......
Page 183: ...Chapter 11 BANDWIDTH CODECS AND COMPRESSION ...
Page 184: ......
Page 209: ...Chapter 12 NETWORK CONFIGURATION CONCEPTS ...
Page 210: ......
Page 244: ...Engineering Guidelines 230 ...
Page 245: ...Chapter 13 NETWORK CONFIGURATION SPECIFICS ...
Page 246: ......
Page 309: ...Appendix A CAT 3 WIRING ...
Page 310: ......
Page 315: ...CAT 3 Wiring 301 Figure 55 CX MX MXe AX and LX Minimum Cable Standard ...
Page 316: ...Engineering Guidelines 302 ...
Page 317: ...Appendix B INSTALLATION EXAMPLES ...
Page 318: ......
Page 335: ...Appendix C LLDP AND LLDP MED CONFIGURATION EXAMPLES ...
Page 336: ......
Page 347: ...Appendix D VOIP AND VLANS ...
Page 348: ......
Page 353: ...Appendix E VOIP SECURITY ...
Page 354: ......
Page 381: ... ...