I just tested the save_memory() function and it works as I suspected.<br>
<br>
The only bug in my example is that save_memory() should be save_memory("location")<br>
<br>
Regards,<br>
Paul<br><br><div><span class="gmail_quote">On Apr 6, 2005 9:28 AM, <b class="gmail_sendername">AJ Grinnell</b> <<a href="mailto:ajgrinnell@gmail.com">ajgrinnell@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">That is exactly what I would need.<br><br>On Apr 6, 2005 9:05 AM, Java Rockx <<a href="mailto:javarockx@gmail.com">javarockx@gmail.com</a>> wrote:<br>> 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<br>> connected to the __same__ MySQL server, it seems like something like this<br>> should be legal:<br>><br>> listen=<a href="http://10.255.15.1">10.255.15.1</a><br>> modparam("usrloc", "db_mode", 2)<br>><br>> route {<br>><br>> if (method=="REGISTER") {<br>><br>>
if (src_ip==<a href="http://10.255.15.1">10.255.15.1</a>) { # ip of peer SER proxy<br>><br>> save_memory();<br>><br>> } else {<br>><br>> save("location");<br>> t_replicate("<a href="http://10.255.15.2">10.255.15.2</a>",
5060);<br>><br>> };<br>> };<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<br>> location table.<br>><br>> Does anyone know about this?<br>><br>> Regards,<br>> Paul<br>><br>><br>><br>><br>> On Apr 6, 2005 1:55 AM, Greger V. Teigre <<a href="mailto:greger@teigre.com">greger@teigre.com</a>> wrote:<br>> ><br>> > You have a cluster and you want to do replication in SER? Do your SER<br>> > servers have one or several databases in mysql? You cannot do both<br>> > replication and have one DB. The problem of using a cluster is that SER<br>> > will write back everything to the database, but there is no "refresh" 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>> > > So I can get replication working, but I constantly am getting errors<br>> > > about receiving SERs usrloc not being able to insert into the<br>> > > database. My guess is because the contact is already there by the<br>> > > originating SER. I have a MySQL cluster that both SERs are using. My<br>> > > question is this, how can I save the contact in the SER that is<br>> > > receiving the contact, without SER trying to write the contact to the<br>> > > DB?<br>> > ><br>> > > _______________________________________________<br>> > > Serusers mailing list<br>> > > <a href="mailto:Serusers@iptel.org">serusers@lists.iptel.org</a><br>> > > <a href="http://mail.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@lists.iptel.org</a><br>> > <a href="http://lists.iptel.org/mailman/listinfo/serusers">http://lists.iptel.org/mailman/listinfo/serusers</a><br>> ><br>><br>><br></blockquote></div><br>