Share via

1.3.1.5 Self SUBSCRIBE

  • Article

Publishers need the ability to subscribe to their own data and to be notified when there are changes. Self SUBSCRIBE is a single SIP SUBSCRIBE dialog that is used for this purpose. It is possible to subscribe to four different sets of data through this dialog:

  • Categories: A publisher is notified of changes to the published data in its containers when the publisher is subscribed to self category data. Each notification contains the container number, changed category, instance number, version, expiration information, and the data of the changed or new publication. The initial NOTIFY or the piggyback 200 OK contains all publications of the user from all containers. Subsequent change notifications include all the publications of the same category from containers that were affected by the change, such as batch publications. When the last publication of a category in a container is deleted, an empty notification is generated.

  • Containers: Publishers are notified of changes to the membership of their containers when they are subscribed to "containers". Each notification contains the identity of the container whose membership has changed, along with the complete new membership of the container. The initial notification contains all membership information for all containers. Subsequent change notifications include all the members of containers that were affected by the change, such as batch setContainerMember operations.

  • Subscribers: Publishers are notified of changes to their subscriber list when they are subscribed to "subscribers". Each notification contains the full subscriber list.

  • Delegates: Publishers are notified of changes to their delegate list when they are subscribed to "delegates". Each notification contains the full delegate list in addition to the current version of this document.

These sets of data define the scope of a self subscription dialog. The self SUBSCRIBE SIP request has an XML body that allows the SIP protocol client to modify the scope. Details of the request and notifications are described in section 2.2.2.3 and section 3.3.