That won't work for us. The reason is that we have LVS fully
"sip-aware" and thus we have many SER routers that are all active at
the same time. This means we don't have the concept of a "primary" sip
router - as the LVS SIP scheduler determines where to route a SIP
message.<br>
<br>
P<br><br><div><span class="gmail_quote">On 5/29/05, <b class="gmail_sendername">Juha Heinanen</b> <<a href="mailto:jh@tutpro.com">jh@tutpro.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;">
Java Rockx writes:<br><br> > * when ser starts up usrloc is "lazy-loaded"<br> > * if a usrloc record is looked up in cache and is __NOT__ found, then MySQL<br> > will be queried. If found in MySQL then the usrloc record will be put in to
<br> > cache for future lookups<br><br>how about changing on the fly the listening address of the secondary ser<br>when primary ser fails? that way there would be no loading delay.<br><br>-- juha<br></blockquote></div>
<br>