Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Create a NOTIFY body indicating the state of the resource being monitored.
  2. Save the body on the subscription (possibly using a datastore, though we may end up adding a field to ast_sip_subscription to hold the body instead).
  3. Set a flag on the subscription (possibly using the same datastore the body is stored in indicating that this subscription has had a state change).
  4. Call Determine how to finish.
    1. If this NOTIFY is being created as a result of the notify_required callback, then just return.
    2. If this NOTIFY is being created as a result of a resource changing state, then call ast_sip_subscription_notify on the parent list subscription.

From here, the duty to create the NOTIFY has been passed up the chain to the list subscription.

...