In order to support reestablishement of subscriptions, I think we are going to have to change the definitions of the "early" and "established" dialog handle values in the callback from SipSubscribeClient to its application.
The previous specification for the callback (from SipSubscribeClient) is that the application gets either the early handle or the established handle, but not both, excepting for one callback when the subscription becomes established, when both are presented (and the application is expected to take note of the change). Because SipSubscribeClient will now be re-creating subscriptions, (I think) we must redefine the "early" handle to be the returned early handle value for the call of addSubscription, and the "established" handle will be the handle of the established subscription, whatever it is. (And so the established handle may not match the early handle.) Implied in this is that calling endSubscription with the early handle will end all subscriptions derived from the matching addSubscription, even ones that are not using the Call-Id in the early handle. As far as I can tell, this change won't affect any of the callers of SipSubscribeClient, despite that it is officially a major change in the interface. Dale _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
