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.
I think that before the SipRefreshManager retries a failed subscription, it should offer it to the application and see it should retry... or perhaps this auto-retry should be a parameter of the subscription... or can someone suggest a better mechanism? Carolyn
_______________________________________________ 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/
