On Tue, 2010-02-09 at 17:27 -0500, Scott Lawrence wrote: > > In practice, there probably isn't much else we can do in the short run. > > Have we filed a bug report with Polycom in regard to this behavior in > > SA? (I'm pretty sure that the subscription-support code for SA > > subscriptions is different from the subscription-support code for dialog > > events.) > > > > What does Scott have to say about this? He's usually got a sharp eye > > for what can be done practically. Also, Paul Mossman may be able to > > give some insight into how quickly we can get Polycom to fix this. > > Can't we detect when we've lost the subscription (for this or any other > reason) and re-establish it?
Within the signaling that Polycom provides, there is no way to detect the loss of the subscriptions, because Polycom shuts them down passively. (It doesn't send NOTIFY with Subscription-State: termianted like it should.) We could use the trick of, when we receive a 500 and aren't sure whether or not the far end intended to terminate the subscription, immediately sending another NOTIFY and seeing if it receives a 481 response. 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/
