________________________________________ From: Beeton, Carolyn (Carolyn) > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Dale Worley > > I think we can fix this by adding the following logic: If > reg events for a resource show a new contact URI for the > resource, the RLS/SAA should suspect that one of the other > contacts may be obsolete. It can fix that problem by > ordering all of the existing subscriptions for the existing > contacts to re-SUBSCRIBE immediately. (We may have to add a > method to SipSubscribeClient to order immediate re-subscription.)
I think this means that every registration to an SAA resource (sip:[email protected]) will cause all existing subscriptions to be kicked. This will cause a lot of noise on startup... _______________________________________ It won't be a problem on SAA startup, because it will received all of the contacts in the first reg event it receives. But it could be quite noisy during startup of all of sipXecs, if the various phones are registering one after another. And if the build power is restored... We could restrict the re-subscribes to: - contacts that have currently active dialogs - contacts that have been known for more than a minimum time period (e.g., 2 minutes) 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/
