Hi,<br>
I had posted this query to the SIP
implementors mailing list . So for those who have not read this
let me summarise the problem.<br>
<br>
<p style="font-style: italic;"><span style="font-size: 10pt; font-family: Arial;">"I wanted to
know if there is a mechanism where registration information could be shared
among SIP proxies.wrt to SER . This is helpful in a farm that is being loadbalanced.<br>
</span></p>
<p style="font-style: italic;"><span style="font-size: 10pt; font-family: Arial;">The topology is a vserver that has two SER proxies S1 and S2 on UDP. <br>
</span></p>
<p><span style="font-size: 10pt; font-family: Arial;"><span style="font-style: italic;">A client
'A' sends a register request to the loadbalancer vip/vserver and the load balancer chooses
a service S1 tied on the vip/vserver . The client is registered at the server S1. Now a new call comes for this client, hits
the vip and the call hashes to the other service S2 bound to the vip.
If S1 and S2 are not sharing the same DB or are not talking to the same
registrar we will have a problem. "</span><br>
</span></p>
<p><span style="font-size: 10pt; font-family: Arial;"> As a solution Dale R. Worley from pingtel suggested that </span>A SIP registrar can actively duplicate its information into another SIP<br>
registrar by doing third-party REGISTERs to it <br>
.<br>
</p>
<p> <span style="font-weight: bold;"> So my question is how do I
set up this third party Registration mechanism in SER so that a
client registers with one proxy and inturn the proxy transfers this
registration info to other participating proxies? </span><br>
</p>
<p style="font-style: italic;">thanks,<br>
sandeep <br>
</p>
<p style="font-style: italic;"><span style="font-size: 10pt; font-family: Arial;"> </span><span style="font-size: 10pt; font-family: Arial;"><span style="font-style: italic;"></span><br>
</span></p>
<br>