On Wed, 2010-02-10 at 11:46 -0500, Beeton, Carolyn AVAYA (CAR:9D60) wrote: > We should really be sending NOTIFY with subscription-state=terminated if > we do terminate the subscription (that is what we're complaining about > Polycom not doing, but we don't do it either!)
Uh, yes, I can't argue with you there. And it's possible that if the Polycom sees us terminate the subscription, it will re-establish it. > We could do > > send NOTIFY(active) => > 200 ok: do nothing > 481: send NOTIFY(terminated) and terminate subscription > > on receipt of 500. (It may be easier said than done, as the Publish > manager doesn't send NOTIFYs if nothing has changed, and we have to keep > the cseqs going up or we get ourselves in trouble all over again...) I'm mucking around with that code right now. Let me look to see if that can be fixed. The "interesting" thing is to make sure that we don't get caught in a loop of sending NOTIFY-terminated because we're terminating a subscription because we received an error when sending NOTIFY-terminated... 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/
