Has anyone ever seen the save_memory() function in the registrar module?<br>
<br>
I'm wondering exactly what this does. Assuming I have two (2) SER
servers connected to the __same__ MySQL server, it seems like something
like this should be legal:<br>
<br>
listen=<a href="http://10.255.15.1">10.255.15.1</a><br>
modparam(&quot;usrloc&quot;, &quot;db_mode&quot;, 2)<br>
<br>
route {<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp; if (method==&quot;REGISTER&quot;) {<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; if (src_ip==<a href="http://10.255.15.1">10.255.15.1</a>) {&nbsp; # ip of peer SER proxy<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; save_memory();<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; } else {<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; save(&quot;location&quot;);<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
t_replicate(&quot;<a href="http://10.255.15.2">10.255.15.2</a>&quot;, 5060);<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; };<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; };<br>
}<br>
<br>
<br>
What I don't know, however, is will <a href="http://10.255.15.2">10.255.15.2</a> attempt to write to the location table.<br>
<br>
Does anyone know about this?<br>
<br>
Regards,<br>
Paul<br>
<br>
<br><br><div><span class="gmail_quote">On Apr 6, 2005 1:55 AM, <b class="gmail_sendername">Greger V. Teigre</b> &lt;<a href="mailto:greger@teigre.com">greger@teigre.com</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">You have a cluster and you want to do replication in SER?&nbsp;&nbsp;Do your SER<br>servers have one or several databases in mysql? You cannot do both<br>replication and have one DB.&nbsp;&nbsp;The problem of using a cluster is that SER<br>will write back everything to the database, but there is no &quot;refresh&quot; when<br>looking up a location, so you cannot be sure that SER B will pick up what<br>SER A stored.<br>g-)<br><br>AJ Grinnell wrote:<br>&gt; So I can get replication working, but I constantly am getting errors<br>&gt; about receiving SERs usrloc not being able to insert into the<br>&gt; database. My guess is because the contact is already there by the<br>&gt; originating SER. I have a MySQL cluster that both SERs are using. My<br>&gt; question is this, how can I save the contact in the SER that is<br>&gt; receiving the contact, without SER trying to write the contact to the<br>&gt; DB?<br>&gt;<br>&gt; _______________________________________________<br>&gt; Serusers mailing list<br>&gt; <a href="mailto:serusers@lists.iptel.org">serusers@lists.iptel.org</a><br>&gt; <a href="http://lists.iptel.org/mailman/listinfo/serusers">http://lists.iptel.org/mailman/listinfo/serusers</a><br><br>_______________________________________________<br>Serusers mailing list<br><a href="mailto:serusers@lists.iptel.org">Serusers@iptel.org</a><br><a href="http://lists.iptel.org/mailman/listinfo/serusers">http://lists.iptel.org/mailman/listinfo/serusers</a><br></blockquote></div><br>