T27G - Fall Back issues - Successive setting [Solved]

[BobBluePackets]

Just posting back now that I have a reason and a solution.....Thank you for all the posts.

As mentioned, in a simple setup (Lab) the fail over function works and works as expected.

To resolve this issue, I completely built up a complete working replica of what we had setup in a production environment (sans as many phones).

Again, with the simple setup, it worked as was the expectation....

However with this setup, I went further and performed the manual sync we do on the production systems. As soon as I completed this, the issue appeared. Phones appear to be registered on both systems.

After a lot of debugging and at least some clearer direction of what could be the possible cause....

Found that the restore of the Primary PBX to the Secondary PBX, is also restoring the Asterisk database. This database contains the Registration states of all the phones, which is naturally carried across the to the Secondary PBX.

Now I have not had time to look at further, but from what I can see, the PBX is sending a keep alive to the phone, getting a response, keeping the record/state in play, and when a phone goes to make a call, it appears to be randomly selecting which PBX to make the call out on...(which could be based on registration refresh vs Qualify timings)..probably something to research on the next rainy weekend.

Anyhow.....the fix is when restoring the database, perform

database deltree registrar/contact on the secondary PBX

This will clear the registrations.....

After this all testing worked perfectly. Killed the primary server, phones started registering with the secondary. Bring the primary back online, phones deregister on the secondary and re-register on the primary - perfect.

Hope it helps someone....

Regards

Bob