Avaya 9608 Administrator's Manual page 32

Network Requirements
Using general Avaya enhancements for rich telephony presence, as follows:
●
<xsd:choice>
<xsd:element name="unknown" />
<xsd:element name="onhook" />
<xsd:element name="do-not-disturb" />
<xsd:element name="on-a-call" type="avp:Participants" />
<xsd:element name="on-a-conference" type="avp:Participants" />
<xsd:any namespace="##other" maxOccurs="unbounded"
</xsd:choice>
Using the subscription to the SIP resource list event package, as follows:
●
- RFC 4662 - A Session Initiation Protocol (SIP) Event Notification Extension for Resource
Lists.
- The identifier for the resource list for a user xxx@yyy.com is list-xxx@yyy.com.
- The phone supports non-hierarchical resource lists corresponding to UPM Contact Lists.
When subscribing to list, the phone will specify the SIP URI sip: + list- +
user@domain.com, in other words the regular SIP URI with list- inserted before the
username.
- If the deskphone has subscribed to the Presence.winfo and Resource.list events, it
accepts the following presence information and passes it to the user interface for further
processing: unknown, onhook, on-a-call, do-not-disturb, on-a-conference and Away.
WINFO SUBSCRIBE is used to allow or block a presence subscription in response to a
●
pending watcher. When the deskphone receives a NOTIFY for watcher info with the
watcher status of "pending" it PUBLISHes a (custom) presauth.winfo event package with
the event "approved" for all the watchers.
If the PRESENCE_SERVER
●
replace the domain on the Request-URI header of any outbound presence-related
messages with this IP address. The To header will remain intact in the form
user@domain.tld.
Support for configuration of a port number for the presence server. Using a port number
●
allows the presence server to run multiple SIP servers on a single host to enable it to
achieve its target scale of 20k users (and approximately 60k communication addresses,
10 presence changes and 10 messages per user per hour).
See Presence tracking is managed by the presence server. In SIP software release 6.0.1, SP1,
identity mapping for presence is based on the contact's enterprise phone number. Presence
administration is dependent on your operating environment, for example, the servers and
software in place. For information about administering presence in specific environments
32 Deskphone SIP 9608, 9611G, 9621G, 9641G Administrator Guide Release 6.0.1
processContents="lax" />
parameter is set and contains an IP address, the phone will