User's Manual

server. For information on configuring the MLPP service, see Avaya Aura
™
Application Server
5300 Using the Provisioning Client (NN42040-112).
To enable MLPP, DOD_ENABLE must be configured as YES in the device configuration file.
Precedence
Precedence enables an IP Deskphone user to specify the precedence level of each call that
is placed. During call processing, this precedence level is used to assure preferential call
completion of higher precedence calls within the same MLPP service domain, even if that
means preempting lower precedence calls.
The precedence levels are:
• Routine
• Priority
• Immediate
• Flash
• Flash-Override
.A user can initiate a call only with a precedence level equal to or below the authorized
precedence level that has been configured for that user. All calls automatically default to
Routine, unless a higher precedence is chosen.
Once the precedence level for a call has been set, the precedence level for that call cannot be
changed.
Precedence calls cannot be placed to clients that are using SIP software earlier than SIP
3.1.
Precedence level for a call is set either at the IP Deskphone used by the user or through the
World Wide Numbering Plan at the Local Session Controller (LSC) Assured Real-Time
Services-Application Sever (ARTS-AS).
Preemption
Higher precedence calls preempt calls lower in precedence when a user has no free call
appearances.
If an IP Deskphone reaches the maximum call appearance limit and a higher precedence call
is received, then one of the existing calls is preempted in order to present the higher
precedence incoming call. An incoming call with a precedence level less than or equal to the
already-received call precedence levels is not presented.
IM sessions cannot be preempted because they do not count as a call appearance.
Warning:
Emergency 91
1 calls can be preempted when there are no available call appearances and
there is an incoming above-Routine precedence call.
Order of call preemption:
Features
194 SIP Software for Avaya 1100 Series IP Deskphones-Administration November 2012
Comments? [e-mail]