On Mon, 2009-11-09 at 12:57 -0500, Carolyn Beeton wrote: > The IE draft for shared appearances requires that the subscription > time be shortened while a line is "seized", so that it can be freed > more quickly if the set which seized it dies. After recent > restructuring of the SipSubscribeClient, I think that the 408 Request > timeout now just causes a refresh of the subscription, without the > application being aware that anything has gone wrong. I think this > subverts this part of the SAA code, and it is not able to free the > "seized" line. This is reported in > http://track.sipfoundry.org/browse/XX-6945.
If I understand you, the problem is that while the SAA shortens the resubscribe interval to 60 seconds so that the application code gets prompt notification if the notifier becomes inaccessible, the SipSubscribeClient's "retry" code takes considerably longer than 60 seconds to give up attempting to re-SUBSCRIBE and notify the application of subscription failure. It seems to me that a good fix for the problem is to revise the "retry" process so that it gives up on re-SUBSCRIBE when the subscription times out, even if the normal re-SUBSCRIBE retry schedule takes longer than the remaining time of the subscription. This approach would (should!) solve the SAA's problem without requiring the application code to manage the process. I will look at the code to see if the code has the problems that I think it does. 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/
