> -----Original Message-----
> From: Worley, Dale AVAYA (BL60:9D30)
> Sent: Wednesday, February 10, 2010 10:47 AM
> To: Lawrence, Scott AVAYA (BL60:9D30)
> Cc: Beeton, Carolyn AVAYA (CAR:9D60); [email protected]
> Subject: Re: [sipX-dev] Terminating subscriptions when we
> receive500Internal Server Error
>
> On Tue, 2010-02-09 at 17:27 -0500, Scott Lawrence wrote:
> >
> > 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
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!)
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...)
_______________________________________________
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/
