Hi All,

Section 3.2 of RFC 3265 states that

"3.2. Description of NOTIFY Behavior

   NOTIFY messages are sent to inform subscribers of changes in state to
   which the subscriber has a subscription.  Subscriptions are typically
   put in place using the SUBSCRIBE method; however, it is possible that
   other means have been used.
   If any non-SUBSCRIBE mechanisms are defined to create subscriptions,
   it is the responsibility of the parties defining those mechanisms to
   ensure that correlation of a NOTIFY message to the corresponding
   subscription is possible."

I was wondering if sipxtapi has any support for any non-SUBSCRIBE mechanisms 
to create implicit
subscriptions.

Any pointers in this regard would be appreciated.

Thanks,
Anshuman

_______________________________________________
sipxtapi-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/

Reply via email to