Feature Impact On Configuration Tasks - Avaya 1230 Administration

E911_PASSWORD
E911_TXLOC
Important:
You must add a set of numbers (regular expressions) marked as "emergency" to the
IP Deskphone dialing plan. Only these numbers are allowed for emergency calls that do not
require logon.

Feature impact on configuration tasks

1. Configuring the SIP Proxy
• The IP Deskphone must have an emergency user in order to make an emergency call
without a user logon.
• The IP Deskphone must have the necessary configurations values for automatic
REGISTER of the emergency user (if you choose this implementation method).
• You must add the emergency user to the proxy.
2. Adding the emergency user to the IP Deskphone config file
• The IP Deskphone must have E911_USERNAME, E911_PROXY, and
E911_PASSWORD configured for making emergency calls.
• The IP Deskphone must have a specified proxy that contains a user record with the
specified user name and password.
• The IP Deskphone must have these values for automatic REGISTER of the emergency
user (if you choose this way of implementation).
• You must add specified variables to the IP Deskphone config file.
3. Adding an emergency number
• You must specify an emergency number for emergency calls to:
- define the numbers that you can use for an emergency call that does not require
logging on.
- trigger emergency functionalities, such as the inability of an emergency call originator to
hold or hang up the call after the call is established.
March 2015
If E911_PROXY does not match the value defined
by these five variables, or the variable E911_PROXY
is not defined, the value of SIP_DOMAIN1 is used as
the emergency proxy.
The password for emergency username that is used
for making an emergency call that does not require
login. The proxy must be configured with the same
password, otherwise the emergency call fails.
The variable that describes location information that
must be sent with the REGISTER SIP message, or
with the INVITE SIP message.
SIP Software for Avaya 1200 Series IP Deskphones-Administration
Comments? infodev@avaya.com
Feature impact on configuration tasks
219