![]() ![]() ![]() ![]() ![]() ![]() |
The following chapter describes the Parlay X 2.1 Presence communication service in detail:
The Presence communication service implements the watcher aspect of the Parlay X 2.1 Presence set of interfaces. For the exact version of the standard these communication services support, see “Appendix A: Standards and Specifications” in Concepts and Architectural Overview, another document in this set.
Presence information is a collection of data on an end user’s status, including such things as current activity, environment, available communication means, and contact addressees. Using the Presence functionality, an application can function as a client in two modes: as a watcher or as a presentity. A watcher is a client that is interested in consuming presence information. A presentity is a client that allows its presence information to be delivered to watchers. WebLogic Network Gatekeeper currently supports the watcher functionality.
An application acting as a watcher can:
Possible attribute types include:
Non-attribute notification parameters can include:
Off the shelf, the Presence communication service is configured to support the following network protocol:
Communication services share many common features, covered in the “Introducing Communication Services” chapter of Concepts and Architectural Overview, but each one has a few characteristics that are specific only to that service. This section describes those specific features for the Presence communication service, including:
There are two Presence/SIP specific CDRs. They are generated when the following criteria are met:
A Presence CDR contains the standard information with this additional information in the additional_info field for a notification call:
The following is a list of EdrIds
created by the Presence/SIP communication service. This list does not include EDRs created when exceptions are thrown. For more information, see Events, Alarms, and Charging..
The table below outlines the correlation between the methods being invoked from either the application (in application-initiated requests) or the telecom network (in network-initiated requests) and the transaction type collected by the statistics counters in Network Gatekeeper for the Parlay X 2.1 Presence/SIP communication service:
Note: | Method names for network-initiated requests are specified by the internal Gatekeeper name, which is not necessarily the same as the message from the network. |
The Parlay X 2.1 Presence/SIP communication service supports the tel:
address scheme.
![]() ![]() ![]() |