<br><br><div class="gmail_quote">2013/1/23 Dan Journo <span dir="ltr"><<a href="mailto:dan@keshercommunications.com" target="_blank">dan@keshercommunications.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">> We have never experienced that and use realtime with multiple asterisk servers.<br>
<br>
</div>We've only recently started seeing the problem.<br>
<br>
To simplify the issue, assuming we have two servers, Asterisk1 and Asterisk2...<br>
<br>
Asterisk1 is a primary server and Asterisk2 is a backup and used as a failover. Asterisk is running on Asterisk2 to speed up the switch.<br>
Both share the realtime database.<br>
<br>
For some reason, about 5% of sip peers are listed as Registered on Asterisk2 even though there is no way they could discover the IP of Asterisk2 on their own.<br>
They also happen to be registered on Asterisk1 where they are supposed to be.<br>
<br>
SIP Debug has shown that they aren't actually registering with Asterisk2 at all. They are only sending OPTIONS keepalive messages to Asterisk2 since QUALITY=yes something.<br>
They never actually send a REGISTER to Asterisk2 so that server must be picking up the Peer status from the realtime DB.<br>
<div class="HOEnZb"><div class="h5"><br></div></div></blockquote><div><br></div><div>I have multiple asterisk servers with a pure 100% realtime configuration. They are all working together and sharing the same realtime database (not only sipfriends, but queue, voicemail, meetme, musiconhold and others) without any of the problems you have reported. </div>
<div><br></div><div>Maybe you are lacking some of the configuration. These is the relevant part.</div><div><br></div><div><div>rtcachefriends=yes </div><div>rtsavesysname=yes</div><div>rtupdate=yes </div><div>rtautoclear=yes </div>
</div></div>