User's Manual

Figure 25: Call states and corresponding Presence icons
Resource List URI
The SIP-specific event notification mechanism allows the subscriber to request to be notified
of changes in the state of a particular resource. Users often subscribe to multiple resources;
without an aggregating mechanism, the user would have to generate a SUBSCRIBE request
for each resource they monitor.
A resource list is identified by a URI, and it represents a list of zero or more URIs (SIP
endpoints). Each URI is an identifier for an individual resource to which the user can subscriber.
The configuration of URI is done on the server and an IP Deskphone requires only to be
configured with the desired Resource List URI; the URI can even be configured automatically
if the server supports auto-generation. For more information, refer to RFC 4662.
If BLF_ENABLE = YES , then use BLF_RESOURCE_LIST_URI to configure the Resource List
URI. You must use the URI provided by the proxy when you configure the user for BLF.
If BLF_ ENABLE = SCS|SIPX, the Resource List URI auto generates in the following format:
~~rl~C~<username>@<domain></domain></username>
BLF call pickup
The Call Pickup feature allows a user to pick up a call by pressing the corresponding speed
dial key when the indicator for a monitored line flashes. The IP Deskphone must send an
INVITE with the Replaces header. Target uri, call-id, to-tag and from tag in the Replaces
header are taken from the NOTIFY message. The Replaces header is specified in RFC
3891.
Use the MAX_BLFCALLS parameter to configure this feature. This parameter specifies the
maximum number of available BLF(picked up) calls on an IP Deskphone. The actual value of
MAX_BLFCALLS correlates with the value of MAX_APPEARANCE, which specifies the maximum
number of available calls of any type. MAX_BLFCALLS must always be less than or equal to
Busy Lamp Field
SIP Software for Avaya 1100 Series IP Deskphones-Administration November 2012 177