Features/Mass Deployment/Setting Files/XML/Function Keys/XmlSubTags/subscription

From Snom User Wiki

Jump to: navigation, search

The subscription tree is used to tie a key to an subscription.

Subscription tags have the the following attributes:

  • type, these values are allowed:
    • presence a subscription of event-type presence will be initiated to the uri defined in the uri-attribute
    • dialog a subscription of event-type dialog will be initiated to the uri defined in the uri-attribute
    • dialog_list a subscription of event-type dialog will be initiated to the uri defined by stk_user_event_list_uri
    • registration a subscription of the event-type reg defined by RFC-3680 (since 8.9.3.26.103)
    • ua-profile a subscription of the event-type ua-profile defined by RFC-6080 (since 8.9.3.26.103)
  • for, defines what to subscribe for (will appear as request-uri in the subscription)
  • to, defines where to subscribe to (will appear as to-field in sip-message of the subscription)

Subscription trees have the following subtrees:

  • NotifyParsingRules of the following types:
    • applies (required)
    • state (required)
    • variable (optional since 8.7.2, multiple tress possible (before 8.7.2 not valid at all))
  • route the route tag contains in it's body the routing information of where to send the subscription to, eg: <route>sip:blf.server.intern;lr</route>
    • since 8.7.2 (optional, multiple tress possible), please always add the lr-parameter
Personal tools
Interoperability