On Tue, 2009-04-07 at 16:49 +0530, Sathya wrote: > Currently I am working on HA and I have a query regarding > the presence of subscription.xml in the distributed machine. > > When I bring down the Master's Registrar down (pls note > that Distributed Registrar up), the replication of registration.xml > stops on Master. At this stage, all the registrations record > (registration.xml) will be held by Distributed machine as expected. The > registration.xml in the Distributed machine gets updated accordingly > with corresponding expires. But the subscription.xml in distributed > machine does not get replicated once the master registrar goes down. Pls > note that the subscription.xml under the Master got updated with > unexpired subscriptions. IOW the subscriptions continue to exist in the > HA environment even with one of the registrars down. This makes me think > of the reason why subcription.xml need to be present in the distributed > machine. And if at all present what is the use of it, when for all the > transactions the subcription.xml in Master is referred.
registration.xml and subscription.xml are handled very differently. Information about registrations is replicated between the Master and Distributed registrars, so the contents of the two registration.xml files are normally the same. Information about subscriptions is *not* replicated between the Master and Distributed machines. Each subscription served by a particular component on a particular machine is recorded in that machine's subscription.xml. If that component fails, the subscription is not taken over by a component on another machine. Although if that component is restarted on that machine, it will resume serving the subscription. 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
