<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Oct 15, 2014, at 10:40 AM, Ben Langfeld <<a href="mailto:ben@langfeld.me">ben@langfeld.me</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On 15 October 2014 11:32, Juha Heinanen <span dir="ltr"><<a href="mailto:jh@tutpro.com" target="_blank">jh@tutpro.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto; "><span class="">Ben Langfeld writes:<br>
<br>
> I figure at this point it may be simpler to separate the registrar and the<br>
> proxy rather than attempt to debug this further, though if you have any<br>
> other suggestions to avoid that I'd love to hear them.<br>
<br>
</span>one possibility is that both of your combined proxy/registrars have<br>
their own location tables and you forward registrations from one to the<br>
other.<br></blockquote><div><br></div><div>The problem with that is horizontal scalability brings noise. If I have 10 of these things, the SIP replication alone would be flooding the network.</div></div></div></div></blockquote><div><br></div>If you are running in an environment where you can use multicast it might be an option for you. Multicast the registrations from the edge proxy to the registrar cluster. If not maybe you can get the registrars to replicate to each other on a separate interface from the interface facing the edge proxy.</div><div><br></div><div><br></div><div>--FC</div><div><br></div><br></body></html>